New forum, who dis!
Looking for some community help here...
I am currently doing backups from storage snaps to a local repo, then a copy job from the local repo to a cloud repo. Currently, we are doing a health check monthly on the cloud repo, but it isn't sustainable. It takes days and make all pending jobs fail, as you I'm sure are aware.
If I do a health check on the local repo instead - will that consistency/integrity check be carried over to the cloud inherently? I'm assuming this local repo check will finish quicker.
Finally, I'm considering moving to a SureBackup and doing away with the health check altogether, but I want to see how others approach this. SueBackups sound great, but they seem time consuming as well given the number of VM's we would need to verify.
Thank you!
-
- Enthusiast
- Posts: 66
- Liked: 3 times
- Joined: Mar 24, 2020 6:36 pm
- Full Name: M.S.
- Contact:
-
- Veeam Software
- Posts: 21166
- Liked: 2149 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Where to do health check? Local Repo or Cloud Repo?
Doing health check on the local repo would anyway be good to ensure that what is currently stored there hasn't changed since the moment it was written and that you're copying good data. But this doesn't prevent such a change from occurring on the cloud repository.
Who is online
Users browsing this forum: No registered users and 16 guests