Unsolved
5 Posts
0
893
May 2nd, 2020 06:00
Recover-only LUN for VMware VMs
Hi,
I created a volume that will be used exclusively for recover tests, on our all-SSD SC4020. I configured it to write directly to RAID5 because I don't need performance for that and the storage can handle it (low load). Any other recommendations for this kind of use?
Thanks,
No Events found!
Origin3k
4 Operator
•
2.3K Posts
0
May 2nd, 2020 07:00
Hmmmm...... no.
Keep in mind that SCOS is thinprovisioning and when ever you place data on that Recovery Datastore/LUN/Volume it increase the space usage on your SC.
If you migrate a VM from the recovery Datastore back to a production Datastore this step will increase space usage a lot from SCOS perspective, because you create new data and new Data for the production Datastore/LUN/Volume means most likely RAID10 depending on the selected storage profile. So watch your space usage and enable a custom threshold alarm withing DSM Datacollector.
Regards,
Joerg
ugob
5 Posts
0
May 4th, 2020 13:00
Thanks,
I was trying to avoid having to run SCSI unmap.
I'll take your recommendations into consideration, but why should I delete and recreate the LUN frequently?
ugob
5 Posts
0
May 4th, 2020 14:00
Ok, no the goal is only to perform automatic recover tests. Recover in datastore (LUN), delete VM, SCSI unmap, start again in one week.
Origin3k
4 Operator
•
2.3K Posts
0
May 4th, 2020 14:00
If you restore a VM to that recovery volume and move the VM later back to production volume you leave "used" blocks behind on the SCOS. For sure the Datastore is empty from a ESXi perspective but not from SAN.
If you dont have to take care of space usage you can create the recovery volume completely prealocated. Its a option in the adv. setting when you create a volume on the SC so no thinprovisionin as normal. This also guarantee that there is space available for emergency restore.
Regards,
Joerg