Happy new year all.
Quick show of hands, are backup copy jobs generally the more common jobs for Veeam Cloud Connect jobs, or are actual backup jobs?
I went with separate backup jobs because my thought was it's going to be a unique backup as opposed to a copy of an existing backup, which at the time made sense in my head.
Now I'm not so sure, as the VCC on on prem jobs potentially clash and need to run at different times.
Is there any real advantage or reason not to switch to a VCC backup copy instead?
-
- Enthusiast
- Posts: 76
- Liked: 3 times
- Joined: Mar 22, 2013 11:01 am
- Full Name: Alan Thompson
- Contact:
-
- Product Manager
- Posts: 14716
- Liked: 1703 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: VCC - backup jobs or backup copies?
Hello Alan,
It depends on the infrastructure possibilities. If customer has enough space on the local repository to keep several restore points for fast recovery, backup copy is good way to go (worth mentioning that customer will have a two copies of the data and if one copy is lost customer still can recover the data from another copy).
If customer does not need secondary copy or does not have enough space on the local repo to fit the backup, direct backup to Cloud Connect will work. Cheers!
It depends on the infrastructure possibilities. If customer has enough space on the local repository to keep several restore points for fast recovery, backup copy is good way to go (worth mentioning that customer will have a two copies of the data and if one copy is lost customer still can recover the data from another copy).
If customer does not need secondary copy or does not have enough space on the local repo to fit the backup, direct backup to Cloud Connect will work. Cheers!
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot], Gosfather and 91 guests