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 | Backup method | Size |
|---|---|---|---|
Database | A Storage 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. | 10.1.1.3.1 Saving a database | Refer to 10.1.1.3.1 Saving a database. |
Authentication | Authenticated data has been set. | 10.1.1.4 Maintaining an authentication management list | Refer to 10.1.1.4 Maintaining an authentication management list. |
Registry | DB setup has been performed on a Storage Management Server (a transaction on a Storage Management Server has been created in a cluster system), or the storage management information (server name, IP address, or port number) has changed. | 10.1.1.5.1 Backing up a registry | Refer to 10.1.1.5.1 Backing up a registry. |
Type | When a backup to be created | Backup method | Size |
|---|---|---|---|
Registry | A Storage Server has been added or Storage Management Server information (server name, IP address, or port number) has changed. | 10.1.1.5.1 Backing up a registry | Refer to 10.1.1.5.1 Backing up a registry. |
Backup | A backup transaction has been completed. | 10.1.1.1.1 Backing up a backup management list | |
Device information used | The device configuration has changed. | 10.1.1.1.3 Saving of device information used by backup management | None |
Pre-processing and | 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. |
Pre-processing and | A pre-processing or post-processing script has changed. | Make a backup using the copy command individually | Check the size of the pre-processing and post-processing script files for tape-copy. |
Transaction volume | 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 | 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 | 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. |
Backup volume | A change is made to the tape-copy backup volume-locking file. | Saving a database by using the copy command | Check the size of the file for which you make a backup. |
Replication | A replication transaction has been completed. | 10.1.1.2.1 Backing up a replication management list | Refer to 10.1.1.2.1 Backing up a replication management list. |
Device information used | The device configuration has changed. | 10.1.1.2.3 Saving of device information used by replication management | None |
Pre-processing and | 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 | 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 | 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 | 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. |
Type | When a backup to be created | Backup method | Size |
|---|---|---|---|
Registry | A tape server has been added or Storage Management Server information (server name, IP address, or port number) has changed. | 10.1.1.5.1 Backing up a registry | Refer to 10.1.1.5.1 Backing up a registry. |
Tape management list | A tape-backup transaction has been completed. | Backing up a tape management list |
Point
You can create backups of databases either individually or as a whole.
If a Storage Server also operates as a Storage Management Server, the Storage Server contains a database for the Storage Management Server as well as for the Storage Server.
