If our terms are that the daily backups are deleted at the end of their respective weeks, are they needed to exist in order for the weekly backup job to properly run? I have the same question when it comes to maintaining all of the weekly jobs at the end of the month when the monthly job runs. I've set our backup copy retention to allow for seven daily, four weekly, 12 monthly, seven yearly. Would we gain anything in terms of compression rate? Is there a benefit to running the backup, and/or backup copy, jobs to have multiple servers contained within? The servers all backup on the same schedule. Backup copy jobs are done to mirror these servers.

We currently run separate jobs for each server, including all file servers separately. I'm hoping to get some guidance for the following All servers are VMware, save one domain controller. We did recently upgrade our environment to version 8 and run NetApp SANs for our storage environment. I've noticed over the last year of using backup copy jobs, as well as using them to maintain our backup retention for archival purposes, that the disc space used grows quite large, quite fast. I would like to configure our environment in the most efficient methodology as possible. We have three office locations and use replications and backup copy jobs to keep available versions in our other offices, instead of having to partner with a third-party host. We currently only use backup copy jobs for a few of our servers, basically our most critical file and application servers. I'd like to start the new year with a newly created backup topology.

Veeam backup copy gfs best practices