When planning and implementing your deployment project, follow the recommendations below:

How to deploy a tape library and use it with Veeam This blog post provides advice and considerations that will help you create a robust tape archival infrastructure. With Veeam, IT administrators can use flexible options to create copies of backups and store them on a different media, following the 3-2-1 Rule for the backup and disaster recovery. Additionally, it’s offline when not in a tape loader. It is cheap, reliable and offers protection against crypto viruses and hacker attacks. One of the most popular choices for backup archival is tape.

Remove backups of production VMs (those not to be archived), from moved Copy jobs files that will retain data to be archived.Additionally, with many new features of Veeam, the tape support now includes putting vSphere, Hyper-V, Agent (Nutanix AHV, Windows, Linux etc.) and NAS backups on tape.

Remove production VMs to archive from originals Backup and Copy jobs (with repos rescan et backups re-maping).

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.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.Move all my backups and backups-copy files to those new repositories, then launch rescan on them.Create new repositories 'Archives' (only new folders on same storage) on each sites, to split things for monitoring purpose.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. Our goal is to kept a part of our production VMs for archive purpose, with maintaining protection for all of our production VMs. Both server have proxy and repository roles, and both are running one job to backup all production VMs of on-site ESXis.Īlso, they are both running Copy jobs to move and retain all backups on local and distant site (GFS retention policy enabled). I have two sites, one hosting the Veeam Management Server, the other hosting a Proxy.

Veeam backup job best practices