This scenario is mostly used when you have centralized IT and you have very stable connections between HQ and your branch offices. The backup copy job will then copy the data to the remote location. Local backups will be made locally but scheduled by the remote location. You will have a source proxy and a source repository.
![veeam backup copy job veeam backup copy job](https://vccbook.io/Images/5-backup1.png)
Veeam backup copy job install#
In the pull strategy, you will install the Veeam B&R Management Server on the remote location (or HQ in a ROBO design). However, connection outages won't result in backups not running locally. Since every location is running their own Management Server, you will have to install multiple Windows servers for each WAN accelerator instance. One disadvantage about this scenario is that you can not share WAN accelerators between management servers in v7. This is mostly used when your IT staff is working on the source location. Then the backup copy job will send the data to the remote location. Backups will be made by a source proxy to a source repository. In the push strategy, you will install the Veeam B&R Management Server on the source location. Actually there are 2 ways you can get your backups of site. Best of all, you no longer require somebody to manually export the tapes and take them home everyday so that your corporate data is safe.īut what about those off-site copies? Getting your restore points off-site is the easy part. Now you can get your backups off-site via very small connections.
Veeam backup copy job manual#
People were using of course scripts to RSYNC & Robocopy to get the backups shipped to a second location but didn't always liked how much bandwidth this required or the manual actions they had to take. People were trying to get there backups off-site with previous versions but maybe not always in the most successful way. Lastly WAN acceleration is now built into the product. It forces people to think about tiering in combination with GFS to slow disks, so that you still have a (limited) amount of fast restore points to do Instant VM Recovery and Surebackup. I like that GFS is only available on the backup copy job. Second of all, you can now apply GFS like retention policies. Start by creating fast backups on fast disks with a limited amount of restore points, then use the backup copy job to copy the data to slower disks for a longer retention. Why? Well it solves one of the most important challenges Veeam users were having with backup policies.įirst of all you can now do tiering of your backups. For me personally the most interesting feature in Veeam v7 would be the backup copy job.