Thank you. I take it to delete all the replays though, I am going to have to set the "allow replay to coalesce into active replay". Because surely the compellent will not let you just "delete" a replay without it being able to move that data somewhere. Once all the blocks are in an active replay---I believe the UNMAP should take care of it. Of course I could just whack the volume---but I dont want to go through all the mess of removing it from all my esx clusters and re-adding it.
They will be "freed" by VMFS but if there are blocks that are needed by a historical Replay/Snapshot to recover to that point in time, they will be kept around until that snapshot is expired or deleted.
If you want to get back all of those blocks ASAP and do not need any Replay/Snapshot history, then just do both processes, run UNMAP and delete all Replays associated to that volume prior to running UNMAP.
rutager
44 Posts
0
June 29th, 2014 09:00
Thank you. I take it to delete all the replays though, I am going to have to set the "allow replay to coalesce into active replay". Because surely the compellent will not let you just "delete" a replay without it being able to move that data somewhere. Once all the blocks are in an active replay---I believe the UNMAP should take care of it. Of course I could just whack the volume---but I dont want to go through all the mess of removing it from all my esx clusters and re-adding it.
BVienneau
115 Posts
1
June 29th, 2014 09:00
They will be "freed" by VMFS but if there are blocks that are needed by a historical Replay/Snapshot to recover to that point in time, they will be kept around until that snapshot is expired or deleted.
If you want to get back all of those blocks ASAP and do not need any Replay/Snapshot history, then just do both processes, run UNMAP and delete all Replays associated to that volume prior to running UNMAP.