A description of what an "Archive" is in NetVault: Backup, why a saveset might be one, how to identify it and what consequences this has.
For more information on this topic, please see the Administration Module 2-Basic Operation of NetVault Backup-Web-based Training
An archive is a stand-alone backup, even though it might be based on a selection set. Backups produced in this way are not utilised when running further jobs based on this selection set. Therefore, incremental backups or datacopy jobs based on this set will still fail saying that they can't find data for this saveset, even though there is an "Archive" saveset for this set present.
Archives are mainly used to produce independent backups that can be removed for off-site storage without affecting full and incremental backup cycles.
You can end up with savesets that have the "Archive" flag set in two ways:
- By selecting the radio button "Archive" in the "Backup Life" frame under "Advanced Options" instead of leaving the default of "Backup" for a full backup. This will grey out "Discard after X Full Backups" option and flags the backup as archive. Incremental backups can never be archives.
- Datacopies of existing backups that are performed with the default option of "Copy a full backup to produce a new independent copy of the data" are always flagged as archives.
Archives have a flag of "Archive - yes" set in Media Management. This is how you can identify them, and you can also report on them for example in a historic job report.
Standalone datacopy jobs cannot copy savesets based on a set name that have the "archive" flag set. This does not affect Phase 2 duplications, i.e. you can run a backup job with the "archive" flag set, and have a "Duplication" set on its advanced option set. Phase 2 duplications don't have the archive bit set, and further incrementals CAN be based on them. They can also be copied with a datacopy job.
There are two options you can set on datacopy jobs themselves that result in similar behaviour:
1) "Copy a full backup to produce a new independent copy of the data" will result in a new saveset that reflects the data copy job's name and job ID. This is always an Archive on which no further backups can be based, no matter what you set on "Advanced Options". This option can only to be used for full backups.
2) "Duplicate a backup (duplicated backups will need their full backup for restore)" creates a copy with the original job name and job ID, and will be listed as another piece of media for the same saveset. This won't have the "Archive" flag set, no matter what you select on "Advanced Options".
SFDC solution number:
English version available ID 2465
Version française disponible ID
Deutsche Version verfügbar ID
Prepared by: Nils Krumrey
