Defining a backup strategy
Defining a backup strategy before creating your backups ensures that you have backups to successfully restore your databases. SnapManager provides flexible granular backup schedule to meet your Service Level Agreement (SLA).
|For SnapManager best practices, see TR 3761.
What mode of SnapManager backup do you need?
SnapManager supports two modes of backups:
Creates a backup of the database when the database is in online state. This backup mode is also called a hot backup.
Creates a backup of the database when the database is either in a mounted or shutdown state. This backup mode is also called a cold backup.
What type of SnapManager backup do you need?
SnapManager supports three types of backups:
Creates a backup of the entire database, which includes all the datafiles, control files, and archive log files.
Creates a backup of selected datafiles, control files, tablespaces, and archive log files
Archive log-only backup
Creates a backup of only the archive log files.You must select Backup Archivelogs Separately while creating the profile.
What type of database profile do you need?
SnapManager creates backups based on whether the database profile separates the archive log backups from the data file backups.
A single database profile for combined backup of data files and archive logs
Allows you to create:
Separate database profiles for archive log backups and data file backups
Allows you to create:
What naming conventions should be used for Snapshot copies?
Snapshot copies created by backups can follow a custom naming convention. Custom text or built-in variables such as the profile name, the database name, and the database SID provided by SnapManager can be used to create the naming convention. You can create the naming convention while creating the policy.
|You must include the smid variable in the naming format. The smid variable creates a unique Snapshot identifier.
The Snapshot copy naming convention can be changed during or after the creation of a profile. The updated pattern applies only to Snapshot copies that have not yet been created; existing Snapshot copies retain the previous pattern.
How long do you want to retain backup copies on the primary storage system and the secondary storage system?
A backup retention policy specifies the number of successful backups to retain. You can specify the retention policy while creating the policy.
You can select hourly, daily, weekly, monthly, or unlimited as the retention class. For each retention class, you can specify the retention count and retention duration, either together or individually.
Retention count determines the minimum number of backups of a particular retention class that should be retained.
For example, if backup schedule is daily and retention count is 10, then 10 daily backups are retained.
The maximum number of Snapshot copies that Data ONTAP allows you can retain is 255. After it reaches the maximum limit, by default the creation of new Snapshot copies fail. However, you can configure the rotation policy in Data ONTAP to delete older Snapshot copies.
Retention duration determines the minimum number of days for which the backup should be retained.
For example, if backup schedule is daily and retention duration is 10, then 10 days of daily backups are retained.
If you set up SnapMirror replication, the retention policy is mirrored on the destination volume.
|For long-term retention of backup copies, you should use SnapVault.
Do you want to verify backup copies using the source volume or a destination volume?
If you use SnapMirror or SnapVault, you can verify backup copies using the Snapshot copy on the SnapMirror or SnapVault destination volume rather than the Snapshot copy on the primary storage system. Using a destination volume for verification reduces the load on the primary storage system.