Best Practices, layer storage creep, orphaned .vhds.

[Darin McClain]

When I clean up layers, or versions of layers I no longer need, the .vhds can be left behind if they are locked in use.

 

Is there any scripts or something I can run to give me a report on which .vhd files are no longer needed and just got left behind?

 

Then I can unlock the files for manual deletion at least.

 

Darin

[Rob Zylowski]

I just checked with engineering.  The way its supposed to work is that if you delete a layer version the next time we do maintenance on the share (which runs every 4 hours) that version layer file should be deleted.  If the file were locked we will try every time during that maintenance until the file is deleted.

 

But that does require that the layer version is deleted not just unassigned.  If you just unassign it we assume you may use it again.

 

Does this make sense with what you are seeing?  If not just to be sure you don't have more than one appliance pointed to the same share do you?

[Darin McClain]

Oh cool, that makes sense. So when a .vhd eventually becomes unlocked (boy do users love to stay logged in for weeks at a time) then the next maintenance window will be able to delete it even if a month has passed by after I originally deleted the layer? Only one appliance here too.

 

Darin

[Rob Zylowski]

Yes that's how they explained it.  I have not ever noticed the files being locked so long :) and I know some folks expect it to be removed when they unassign it.

[Darin McClain]

Yeah, I had deleted one today, and one user still had it open. I closed the file and deleted it manually. Good to know I don't have to worry about storage creep! Thanks Rob!