I am aware that resizing a disk of a VM within a replication job will cause all previous snapshots/restore points to be purged thus starting the chain over. RE: http://forums.veeam.com/vmware-vsphere- ... 10667.html
I realize this issue is due to the inability of VMware to have a disk resized while a snapshot exists.
I would like to know what the best practice or recommendation from Veeam is regarding the ability to access or store the 'purged' restore points for at least a handful of days.
-
- Novice
- Posts: 5
- Liked: 1 time
- Joined: Aug 14, 2012 6:46 pm
- Full Name: David Williams
- Contact:
-
- VeeaMVP
- Posts: 6165
- Liked: 1971 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
- Contact:
Re: Veeam Recommendations for Resizing Disks on Replica Jobs
I never tried it, but what if you de-register the replica VM from the target vSphere environment, and for example you modify the replica job with a different name for the replica VM? Maybe it could do the trick and leave the old VM in place so you can then delete it once you have enough restore points of the new one...
Luca.
Luca.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam Recommendations for Resizing Disks on Replica Jobs
Also, cloning/copying replica VM files to temporarily store them on another datastore could help.
Who is online
Users browsing this forum: Bing [Bot], Erwin Linker, MarioZ, Semrush [Bot] and 160 guests