Equipment/Device: a stand-alone drive or tape library with small-to-medium capacity, tapes are ejected/inserted manually or automatically
Amount of data to record: medium-size organization, plenty of VMs
Policy: tapes should be ejected after each backup session
A backup session starts with each run of a backup job linked to tape backup job; if multiple backup jobs are linked to a single tape job, backup session starts with the first backup job start, and ends with the last backup job end. In this case, it is recommended to schedule tape job so that it starts a new media set when the first linked job starts.
Automation: Best practices for tape libraries recommend that tape should be ejected from the drive and placed into slot; if you have a stand-alone drive, the Eject option will indicate job completion.
Then you can set up recording of tape archives with the following settings:
•Retention for media pools: Protect data for [period_after_which_tape_is_ejected] (e.g., for 6 days)
•Retention for media set: Automatically create new media set for every backup session
•Job settings: Use Eject media once the job finishes option (except for the case when you want to eject the tape manually from your stand-alone drive)
This scenario can be of use for mid-size organizations; sample workflow may include:
1.Forward Incremental backups to disk (with optional transform)
2.On weekdays - daily incremental backups archiving to “Incremental” Tape Media Pool
3.Once a week - full backup archiving to “Full” Tape Media Pool “(use Protect data for 35 days option)
4.Once a month - export one of the full tapes for offsite storing (safe, bank deposit box, bunker)