Best practices: NetBackup naming conventions
Use a consistent name convention on all NetBackup primary servers. Use lower case for all names. Case-related issues can occur when the installation comprises UNIX and Windows primary and media servers.
Table:
Object to name | Guidelines for naming |
|---|
Policy | One good naming convention for policies is platform_datatype_server(s).
Example 1: w2008_filesystems_trundle
This policy name designates a policy for a single Windows 2008 server doing file system backups.
Example 2: w2008_sql_servers
This policy name designates a policy for backing up a set of Windows 2008 SQL servers. Several servers may be backed up by this policy. Servers that are candidates for being included in a single policy are those running the same operating system and with the same backup requirements. Grouping servers within a single policy reduces the number of policies and eases the management of NetBackup. |
Schedule | Create a generic scheme for schedule names. One recommended set of schedule names is daily, weekly, and monthly. Another recommended set of names is incremental, cumulative, and full. This convention keeps the management of NetBackup at a minimum. It also helps with the implementation of Vault, if your site uses Vault.
|
Storage unit and storage group | A good naming convention for storage units is to name the storage unit after the media server and the type of data being backed up.
Two examples: mercury_filesystems and mercury_databases
Where "mercury" is the name of the media server, and "file systems" and "databases" identify the type of data being backed up. |
