I have two sites, one hosting the Veeam Management Server, the other hosting a Proxy. Both server have proxy and repository roles, and both are running one job to backup all production VMs of on-site ESXis. Also, they are both running Copy jobs to move and retain all backups on local and distant site (GFS retention policy enabled).
Our goal is to kept a part of our production VMs for archive purpose , with maintaining protection for all of our production VMs.
I plan to re-organize our backup jobs and repositories, because the actual plan is consuming nearly all of our storage on repositories : all of our production VMs are kept with GFS retention policy.
So my plan is :
- Create new repositories "Archives" (only new folders on same storage) on each sites, to split things for monitoring purpose.
- Move all my backups and backups-copy files to those new repositories, then launch rescan on them.
- Create new Backup jobs, with only part of our VMs which we want to archive, set the repository to our new "Archives" repos, then map moved backups to those jobs.
- Create new Copy jobs for newly created backup jobs, with GFS retention enabled, and set 0 restore points to keep, retain backup locally and on the other site, set repository to our new "Archives" repos, then map moved backups-copy files to those jobs.
- Remove production VMs to archive from originals Backup and Copy jobs (with repos rescan et backups re-maping).
- Remove backups of production VMs (those not to be archived), from moved Copy jobs files that will retain data to be archived.
Does have I made mistakes, or forgot any step to clean original backups from data that we not want to archive ?