This is an archive version of the document. To get the most up-to-date information, see the current version.VM Backup to Tape
To back up data to tape, you need to create and run tape jobs. The backup to tape job is a dedicated job that archives to tape Veeam backups that were produced by Veeam backup jobs.
When a backup to tape job runs, it does not create new backups: it locates already existing backups and copies them from backup repository to tape. You need to set the source of the tape job: jobs and/or backup repositories.
Jobs as Source
You can add backup, backup copy and/or Endpoint jobs as source to tape job. When the tape job starts on it's schedule, it picks the restore points that were produced by the source backup jobs in period since the last tape job run. If you change the configuration of the source backup jobs, the tape job is updated automatically: it adds new VMs to the list of VMs to archive or stops archiving VMs that were removed from backup jobs.
The source jobs may use any backup method:
To back up the forever forward incremental chains to tape, the tape job uses the virtual full. The virtual full creates a synthetic full backup on tape regularly (for example, once a week) and splits the chain into short series of tapes which is more convenient for restore. For more information, see Virtual Full Backup.
The source backup chain must contain 4 or more restore points.
If the source job is backup copy job, keep in mind that the last restore point of the backup copy job stays active until the next restore point is created. The tape job does not copy such active points, because they may be updated. For this reason, the backup chain on tape will be always one restore point shorter than on disk.
When the tape job backs up the forward incremental chain to tape, it creates a copy of the disk backup chain.
The source backup chain must contain 2 or more restore points.
The last backup in the reverse incremental backup chain is always the full backup. If the source backup chain is reverse incremental, the tape job will copy the full backup each time the tape job runs. The increments are skipped.
The source backup chain may contain any number of restore points.
Backup Repositories as Source
When you add a repository as source to tape job, the tape job constantly scans the selected repository (or repositories) and writes the newly created backup files to tape. The tape job monitors the selected repository in a background mode. You can set explicit backup windows for the tape job. In this case, the tape job will start on the set time and archive all new restore points that were created in period since the last job run.
If you create or remove backup jobs that use this repository, or if you change the configuration of such backup jobs, you do not need to reconfigure the tape job that archives the repository.
Mixed Jobs
To one tape job, you can link an unlimited number of source jobs and/or source repositories. The source jobs can be of different type (backup and backup copy), and can belong to different platform (VMware, Hyper-V or Endpoint).
You can add the following sources to the same tape job:
- VMware backup jobs
- Hyper-V backup jobs
- VMware backup copy jobs
- Hyper-V backup copy jobs
- Endpoint backup jobs
- Repositories
|
The tape job looks only for the Veeam backups that are produced by backup jobs running on your console. Other files will be skipped. |
Note that to back up files, you need to configure file to tape job. For more information, see File to Tape Jobs.
Linking Source Jobs
You can add source jobs to tape jobs at any moment: when you create a tape job, or later. Adding sources is not obligatory when you create a tape job: you can create an "empty" job and use it as a secondary destination target. When you link jobs, the tape job processes them in the same way as the jobs added with the Tape Job Wizard. For more information, see Linking Backup Jobs to Backup to Tape Jobs.
Related Topics