This section describes the function of making a backup of management information (e.g., databases) from just one Managed Server or Management Server.
With a package backup of management information, you can make a backup of management information for all Managed Servers and Management Server from just one Managed Server or Management Server. Executing a package backup of management information runs backup commands (making backups of backup management resources and databases) for the databases of other Managed Servers and Management Server, and collects the backup data and management information created by these backup commands.
The server on which you can execute a package backup of management information is called the "package-backup-of-the-management-information execution server". The servers whose data is to be backed up are called the "package-backup-of-the-management-information target servers".
Figure 7.1 Management Server and Managed Server
Assume that the package backup of management information function has been used to back up the management information on a Management Server, Managed Server A, and Managed Server B onto Managed Server B in the diagram above. In this case, Managed Server B is the backup execution server. The Management Server, Managed Server A, and Managed Server B are the backup target servers. That is, Managed Server B operates as both the backup execution server and backup target server.
The following table shows the types of management information that is handled in a package backup of management information.
Function | Type of data |
|---|---|
Database |
|
Registry |
|
Backup management |
|
Replication management |
|
Package backup of management information |
|
Note
Managed Server management information created by Softek AdvancedCopy Manager Version 10.3 (V10.0L40) or earlier cannot be handled by the package backup of management information function. To create a backup, back up each management information component individually as described in "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" applicable to the Managed Server.
Before creating a package backup of management information, you must perform the following:
Determine the management information package backup target servers and the types of management information to be backed up.
Determine the management information package backup execution server.
Create a directory where the management information package backup execution server will store the backup data. The size of the directory must not be less than the total of the following sizes:
The required size for a database is the size of the database backup data multiplied by 1.2.
For the backup data size, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the Management Server.
The required size for the registries is the total of the data sizes of the registry backup data on the management information package backup target servers.
For the backup data size, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the management information package backup target server.
The required size for backup management is the total of the sizes below for each management information package backup target server:
For the size of each component of backup data, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the management information package backup target server.
Size of the backup data for the backup management lists (size of the backup data for the backup management lists plus the size of the backup data for the recovery control files) multiplied by 1.2
Size of the pre-processing and post-processing scripts for backup management
Size of the transaction volume locking specification file for backups for backup management
Size of the backup volume locking specification file for backups for backup management
Size of the backup-restored volume locking specification file for backup management
The required size for replication management is the total of the following sizes for each management information package backup target server:
Size of the pre-processing and post-processing scripts for replication management
Size of the copy-source volume locking specification file for replication management
Size of the copy-destination volume locking specification file for replication management
Check the size of the working directory for the management information package backup target servers (or the shared disk for shared data for AdvancedCopy Manager in a clustered system). The sizes described below are needed only when a package backup of management information is being created. Use the largest value of the sizes of the databases to be backed up from the management information package backup target servers. The required sizes are as follows:
The required size for the databases is the size of the database backup data multiplied by 2.2.
For the backup data size, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the Management Server.
The required size for backup management is the size of the backup data for the backup management lists (size of the backup data for the backup management lists plus the size of the backup data for the recovery control files) multiplied by 2.2.
For the backup data size, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the management information package backup target server.
The working directory does not require any space for registry, replication management, and policy file backups.
Execute the stgmgrinfoset command as described in stgmgrinfoset (Management information package backup server registration/deletion command), on the management information package backup execution server (determined in step 2).
Create a policy file on the management information package backup execution server.
Management information package backup execution server | Policy file path | |
|---|---|---|
OS | Operation type | |
Windows | Non-cluster | <Environment directory>\etc\stgmgrinfo_policy.ini |
Cluster | <AdvancedCopy-Manager-shared-data>:\etc\opt\swstorage\etc\stgmgrinfo_policy.ini | |
Solaris, | Non-cluster | /etc/opt/FJSVswstf/stgmgrinfo_policy.ini |
Cluster | /etc/opt/FJSVswstf/<logical-node-name>/stgmgrinfo_policy.ini | |
Note
Do not specify more than one Managed Server as a management information package backup execution server.
When this server is used for executing transactions on the Managed Server in a clustered system, create a directory for storing backup data on a shared disk.
For databases and backup management, backup commands are executed on the corresponding management information package backup target servers. In addition, for database backups and backup management (ie, backup management lists) backups, a temporary capacity that is approximately 2.2 times greater than the total size of the backups is required to save the backup data in an archive file.
Section | Key | Description | Whether specifiable on | |
|---|---|---|---|---|
Management | Managed | |||
Server | DBData | Specifies whether to make a backup of the database. Yes: Make a backup of the database. | A | C |
BkupData | Specifies whether to make a backup of the backup management. Yes: Make a backup of the backup management. | B | B | |
ReplData | Specifies whether to make a backup of the replication management. Yes: Make a backup of the replication management. | B | B | |
A: Specifiable
B: Specifiable only when the applicable function is operating on the server
C: Unspecifiable
Note: If this key is not specified or if "Yes" is not in the form "Y" (uppercase) + "es" (lowercase), then "No" is set.
Example
Set up a policy file as follows:
The Management Server named ACMMGR creates backups for the database and backup management.
The Managed Server named ACMAGT1 creates backups for backup management.
The Managed Server named ACMAGT2 creates backups for replication management.
[ACMMGR] DBData=Yes BkupData=Yes [ACMAGT1] BkupData=Yes [ACMAGT2] ReplData=Yes
Note
Create a policy file only if it will be used.
The policy file cannot include any settings for backups of registries and of the policy file for management information package backup.
Executing stgmgrinfobkup (Management information package backup command) on the management information package backup execution server stores the backup data in the directory under the following structure:
Directory | Data type | |||
|---|---|---|---|---|
*1 | Server | DBData |
| |
RegiData |
| |||
BkupData | FJSVswsts |
| ||
Scripts |
| |||
data |
| |||
ReplData | Scripts |
| ||
data |
| |||
MgrInfoData |
| |||
*1 is the backup data storage directory specified by stgmgrinfoset (Management information package backup server registration/deletion command).
When *1 is /ACMBkupData and the server name is ACMAGT1, the pre-processing and post-processing scripts for backup management are put in the following directory:
/ACMBkupData/ACMAGT1/BkupData/Scripts |
Initial operations
The policy file backup operations are described below. Backup of registries which are not included in the backup targets when a policy file is used to perform backup are also detailed. The initial operations are as follows:
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make backups of the registries on all of the Managed Server.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the policy file.
Normal-use operations
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server when you need to make backups of the target data.
For the timing of the backups, refer to "Maintaining a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the applicable operating system.
Operations when a server is added or deleted
On the management information package backup execution server, set up a policy for the added Managed Server in the policy file.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the registry of the added Managed Server.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the policy file.
On the management information package backup execution server, delete the information about the Managed Server that was deleted from the policy file.
In the backup data directory on the management information package backup execution server, delete the directory containing the name of the deleted Managed Server.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the policy file.
Operations when a server name is changed
On the management information package backup execution server, delete the information for the Managed Server from the policy file.
In the backup data directory on the management information package backup execution server, delete the directory containing the name of the Managed Server.
On the management information package backup execution server, set up a policy for the renamed Managed Server in the policy file.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the registry of the renamed Managed Server.
Execute stgmgrinfobkup (Management information package backup command) on the management information package backup execution server to make a backup of the policy file.
This section describes how to use the backup data created by stgmgrinfobkup (Management information package backup command) to execute restoration.
Perform the operations below as a root user or with an account that belongs to the Administrators group.
Restoring a registry
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On the management information package backup execution server, copy the registry backup to the following directory:
<Directory-determined-in-step1>\<server-whose-registry-to-be-restored>\RegiData
<Directory-determined-in-step1>/<server-whose-registry-to-be-restored>/RegiData
Transfer the registry backup that was copied in step 2 to the target server in binary mode.
Restore the registry on the server. For details on restoring a registry, refer to "Restoring a registry" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the target server.
Restoring a database
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On the management information package backup execution server, copy the backup of the database to the following directory:
<Directory-determined-in-step1>\<management-server-name>\RegiData
<Directory-determined-in-step1>/<management-server-name>/RegiData
Transfer the backup of the database that was copied in step 2 to the Management Server in binary mode.
On the Management Server, expand the database backup transferred in step 3.
On the Windows version Management Server:
Expand the database backup using the stgarcext (Backup data expansion command) in the "ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows)".
On a Solaris/Linux version Management Server:
Expand the database backup by using the tar command supported by the operating system.
On the Management Server, restore the database.
For details on restoring a database, refer to "Restoring a database" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the Management Server.
The backup data storage directory specified for database restoration is the directory expanded in step 4.
Specify "RDB Dictionary, DSI(LOAD Mode)" for the Windows version as a recovery mode. Specify "0" for other versions.
Restoring a backup management list, or backup management list and recovery control file
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the backup of the backup management list or the backups of the backup management list and the recovery control file to the following directory:
<Directory-determined-in-step1>\<server-whose-list/file-to-be-restored>\BkupData\FJSVswsts
<Directory-determined-in-step1>/<server-whose-list/file-to-be-restored>/BkupData/FJSVswsts
Transfer the backup of the backup management list or the backups of the backup management list and the recovery control file copied in step 2 to the target server in binary mode.
Expand the backup of the backup management list or the backups of the backup management list and recovery control file transferred in step 3 on the target server.
On a Windows version server:
Expand the backup of the backup management list using the stgarcext (Backup data expansion command) in the "ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows)".
On a Solaris/Linux/HP-UX/AIX version server:
Expand the backup of the backup management list or the backups of the backup management list and recovery control file by using the tar command supported by the operating system.
Restore the backup management list, or the backup management list and recovery control file on the target server. For details on restoring, refer to "Restoring a backup management list" or "Restoring a backup management list and recovery control file" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the target server. The Backup-Directory specified in the resource restoration command is the directory expanded in step 4.
Restoring the backup management pre-processing/post-processing scripts
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the backups of the backup management pre-processing/post-processing scripts for backup management to the following directory:
<Directory-determined-in-step1>\<server-whose-scripts-to-be-restored>\BkupData\Scripts
<Directory-determined-in-step1>/<server-whose-scripts-to-be-restored>/BkupData/Scripts
Transfer the backups of the backup management pre-processing/post-processing scripts copied in step 2 to the target server in binary mode.
Transfer the backups of the backup management pre-processing/post-processing scripts copied in step 3 to the directory in which the scripts will be executed on the target server in binary mode. For the directory in which the pre-processing and post-processing scripts for backup management are executed (that is, the directory to which the scripts are to be copied), refer to "Pre-processing and post-processing for backup/restoration" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the target server.
On a Solaris/Linux/UP-UX/AIX-version server, change the access permission assigned to the pre-processing and post-processing scripts for backup management copied in step 4 on the target server by using the chmod command supported by the operating system. Set execution permission for the root user, which is the owner.
Restoring locking specification files for backup management
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the backups of the locking specification files for backup management to the following directory:
<Directory-determined-in-step1>\<server-whose-files-to-be-restored>\BkupData\data
<Directory-determined-in-step1>/<server-whose-files-to-be-restored>/BkupData/data
Transfer the backups of the locking specification files for backup management copied in step 2 to the target server in binary mode.
Copy the backups of the locking specification files for backup management transferred in step 3 to the target server. For the directory in which the locking specification files for backup management are used (that is, the directory to which the files are to be copied), refer to "Appendix A Pre-processing and Post-processing of Backup and Restoration" in the "ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows)".
Restoring pre-processing and post-processing scripts for replication management
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the backups of the pre-processing and post-processing scripts for replication management to the following directory:
<Directory-determined-in-step1>\<server-whose-scripts-to-be-restored>\ReplData\Scripts
<Directory-determined-in-step1>/<server-whose-scripts-to-be-restored>/ReplData/Scripts
Transfer the backups of the pre-processing and post-processing scripts for replication management copied in step 2 to the target server in binary mode.
Copy the backups of the pre-processing and post-processing scripts for replication management transferred in step 3 to the directory in which the scripts will be executed on the target server. For the directory in which the pre-processing and post-processing scripts for replication management are executed (that is, the directory to which the scripts are to be copied), refer to "Pre-processing and post-processing of replication" in the "ETERNUS SF AdvancedCopy Manager Operation Guide" for the operating system running on the target server.
On a Solaris/Linux/UP-UX/AIX-version server, change the access permission assigned to the pre-processing and post-processing scripts copied in step 4 on the target server by using the chmod command supported by the operating system. Set execution permission for the root user, which is the owner.
Restoring locking specification files for replication management
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the backups of the locking specification files for replication management to the following directory:
<Directory-determined-in-step1>\<server-whose-files-to-be-restored>\ReplData\data
<Directory-determined-in-step1>/<server-whose-files-to-be-restored>/ReplData/data
Transfer the backups of the locking specification files for replication management copied in step 2 to the target server in binary mode.
Copy the backups of the locking specification files for replication management transferred in step 3 to the target server. For the directory in which the locking specification files for replication management are used (that is, the directory to which the files are to be copied), refer to "Pre-processing and Post-processing of Replication" in the "ETERNUS SF AdvancedCopy Manager Operation Guide (for Windows)".
Restoring a policy file for management information package backup
Execute stgmgrinfoset (Management information package backup server registration/deletion command) on the management information package backup execution server to determine which directory contains the backup data.
On this server, copy the policy file located in the following directory to the policy file for the management information package backup command:
<Directory-determined-in-step1>\<server-whose-file-to-be-restored>\MgrInfoData
<Directory-determined-in-step1>/<server-whose-file-to-be-restored>/MgrInfoData
For information on the directory for the policy file for the management information package backup command, refer to step 6 in the "7.1.2.1 Preliminaries".
