SUPPLEMENT to NetBackup 6.5.2 Documentation Updates

Starting in NetBackup 6.5.2: The Multiple Copy Synthetic Backups feature introduces the capability to read remote, non-primary source images to produce a second synthetic copy in remote storage.

This feature provides the following benefits:
■ This feature eliminates the bandwidth cost of copying synthetic full backups to another site. Instead of duplicating a local synthetic full backup to a remote site to produce a second copy, it is more efficient to produce the second copy by using data movements only at the remote site.
■ This feature provides an efficient method to establish a dual-copy disaster recovery scheme for NetBackup backup images.

Clarification & Limitation:
- This feature produces a "SECOND COPY" synthetic backup at remote storage unit as part of a typical synthetic backup operation. To use this feature copies of the regular FULL & INC images are required at the destination storage unit. These copies will then be used to create a Second Copy Synthetic backup.

- At the current time, this is the ONLY additional synthetic copy can be configured through this feature. For additional copies use bpduplicate, VAULT or DSSU methods.
 

- Note: Synthetic backup images are not duplicated by Storage Lifecycle Policies (SLP).
 

Usage & Example:
 

See TN339323 in the related section.
 

Configuring Multiple Copy Synthetic Backups
To configure a multiple copy synthetic backup, create a configuration file on the master server for each synthetic backup policy for which a second copy is to be produced.
The configuration file is a text file named after the policy and schedule: multi_synth.policy.schedule

Location:
On UNIX: /usr/openv/netbackup/db/config/multi_synth.policy.schedule
On Windows: install_path\VERITAS\NetBackup\db\config\multi_synth.policy.schedule

Simple configuration example
The following multiple copy synthetic configuration example takes advantage of default values to produce the second synthetic copy.

TARGET_STU=disk_stu
=> Specifies the storage unit name or storage unit group name where the second copy synthetic backup is to be written. Use the special identifier __ANY__ to indicate that Any Available storage unit can be used that is not configured to be on demand only. Note that there are two underscores before and after ANY: