Backup File Naming Conventions in Operations Manager 2007
Updated: May 22, 2009
Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1
Proper use of naming conventions for backup files can help you distinguish between them. Backups will be unique based on the management group that they are a backup of and the time that the backup was created. Consistent use of a standard naming convention can help you avoid the unintentional restoration of a backup to the wrong management group or restoring a backup that is from the wrong time.
Database File Naming Conventions
There might be multiple management groups in your System Center Operations Manager 2007 environment; therefore, be sure to include the management group name or some distinguishing name in the database backup file names.
You can also include other information in the file name, such as the database name, date, and type of backup. For example, a file name might be formatted as follows: OpsMgrDB_DIFFERENTIAL_<management group name>_11_01_2007 or REPORTING_FULL_<management group name>_11_01_2007.
Custom Management Pack Naming Conventions
If your monitoring infrastructure consists of multiple management groups, it is highly likely that the configuration of management packs and their overrides will vary across those management groups. Therefore, implementing a standard naming convention for custom management packs will help prevent the same problems as having a standard naming convention for databases does.
Include the management group name or some distinguishing name in the XML file name for these backups. Also include the version of the sealed management pack that the custom management pack contains overrides for. You can also include other information in the file name, such as the date. For example, a file name might be in the following format: <management group name>_<Management pack name>_<Management pack version>_11_01_2007.xml.