AdvancedCopy Manager holds various repositories of management information on the usage of its functions. They are named generically and are referred to as a database in this chapter.
A database is important information. You are recommended to periodically back up a database that is frequently updated, when the space available for repositories becomes insufficient after long-time usage of the database that is different from originally planned, as a safeguard against running out of space. (Note that it differs from other types of databases such as ORACLE etc.)
The following table lists instances when backup of the database is needed.
Type | When a backup to be created | Backup method | Size |
|---|---|---|---|
Database | A Managed Server has been added. The configuration information has changed as a result of loading of new device information or for some other reason. The information on backup management or the replication management operation has changed. | "11.1.1.4.1 Saving a database" | Refer to "11.1.1.4.1 Saving a database". |
Registry | DB setup has been performed on a Management Server (a Management Server transaction has been created in a clustered system), or the storage management information (server name, IP address or port number) has changed. | "11.1.1.5.1 Backing up a registry" | Refer to "11.1.1.5.1 Backing up a registry". |
Type | When a backup to be created | Backup method | Size |
|---|---|---|---|
Registry | A Managed Server has been added or Management Server information (server name, IP address, or port number) has changed. | "11.1.1.5.1 Backing up a registry" | Refer to "11.1.1.5.1 Backing up a registry". |
Backup management list | A backup transaction has been completed. | "11.1.1.1.1 Backing up a backup management list and recovery control file" | Refer to "11.1.1.1.1 Backing up a backup management list and recovery control file". |
Pre-processing and post-processing scripts for backup management | A pre-processing or post-processing script has changed. | Saving a database by using the copy command | Check the size of the pre-processing and post-processing script file for backup management. |
Transaction volume locking specification file for backups | The transaction volume locking specification file for backups has changed. | Saving a database by using the copy command | Check the size of the transaction volume locking specification file for backups. |
Backup volume locking specification file for backups | The backup volume locking specification file for backups has changed. | Saving a database by using the copy command | Check the size of the backup volume locking specification file for backups. |
Backup-restored volume locking specification file | The backup-restored volume locking specification file has changed. | Saving a database by using the copy command | Check the size of the file to be backed up. |
Replication management list | A replication transaction has been completed. | "11.1.1.2.1 Backing up a replication management list" | Refer to "11.1.1.2.1 Backing up a replication management list". |
Pre-processing and post-processing scripts for replication management | A pre-processing or post-processing script has changed. | Saving a database by using the copy command | Check the size of the pre-processing and post-processing script file for replication management. |
Copy-source volume locking specification file | The copy-source volume locking specification file has changed. | Saving a database by using the copy command | Check the size of the copy-source volume locking specification file. |
Copy-destination volume locking specification file | The copy-destination volume locking specification file has changed. | Saving a database by using the copy command | Check the size of the copy-destination volume locking specification file. |
Policy file for management information package backup | The policy file has changed. | Saving a database by using the copy command | Check the size of the policy file for management information package backup. |
Symfoware database information file | The database information has changed for Symfoware backup server operation. | Check the size of the file to be backed up. | |
Target directory for output of the recovery control file | The backup has been performed for Symfoware backup server operation. | "11.1.1.7.1 Backing up a target directory for output of the recovery control file" | Check the size of the file to be backed up. |
Point
You can create backups of databases either individually or as a whole.
If a Managed Server also operates as a Management Server, the Managed Server contains a database for the Management Server as well as for the Managed Server.
Note
If you make backups of databases individually, perform the operations with an account that belongs to the Administrators group.
If you make backups of databases individually, do it so that the file ownership and access right at restore time are the same as backup time.
