You should follow certain recommendations when using SnapVault for NetBackup.
Recommendations for grouping policies: When you assign policies to DSUs, you should group these policies based on similar backup schedules, that is, the frequency of backups and retention periods.
A policy's frequency of backups combined with its retention period determines the number of Snapshot copies that will be consumed. A maximum of 250 Snapshot copies can exist at a time on a NearStore volume, so it is essential that Snapshot copy consumption is carefully managed.
Recommendation for snap reserve setting: You should set the Snapshot reserve space on each SnapVault for NetBackup volume to 0 to ensure that maximum disk space is available for backups. You can change the Snapshot reserve space using the snap reserve command.
Recommendation for snap sched setting: SnapVault for NetBackup manages all Snapshot copies on SnapVault for NetBackup volumes. If Snapshot copies are also scheduled using the snap sched command, unnecessary Snapshot copies are created and stored. You should turn off Snapshot copy scheduling on each SnapVault for NetBackup volume to avoid creating unnecessary Snapshot copies. You can disable regular Snapshot copy scheduling using the snap sched command (snap sched volume_name 0 0).
Recommendation for using separate DSUs: To avoid possible language and naming issues, you should use separate SnapVault for NetBackup DSUs for Windows NetBackup clients and UNIX NetBackup clients.
Likewise, separate SnapVault for NetBackup DSUs should be used for NetBackup clients configured for different language settings. You can view language settings using the vol lang command.