Hi
If I'm doing restore testing for random VMs, either the manual way or using SureBackup, is it best to do it from the last Copy Job restore point or from the primary job?
I'm presuming if the latest restore point from the copy job is fine, then the primary job would also be fine. My thinking is, if I do testing only from the primary job, then the copy job (which might be more important in the event of DR) could still be bad. I really don't want to have to test both primary and copies going forward, that would be a double pain.
Thanks
-
- Veteran
- Posts: 385
- Liked: 39 times
- Joined: Oct 17, 2013 10:02 am
- Full Name: Mark
- Location: UK
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Restore Testing question
Hi Mark, the recommended approach is to use SureBackup to verify that your primary backups are recoverable (still, using backup copy jobs in SureBackup is a bit tricky). Backup copy job has built-in integrity check to ensure data is bit-identical, so provided the backup on source is recoverable, you always can restore the required VM state from another location.
Who is online
Users browsing this forum: Bing [Bot], Regnor and 56 guests