ETERNUS SF AdvancedCopy Manager Operator's Guide 13.0 -Solaris-

Contents Index

Chapter 9 Operation Maintenance

This chapter describes maintaining a database, performing troubleshooting, and changing the operation information.

9.1 Maintenance of Database

AdvancedCopy Manager holds various repositories and management information as employment information. They are named generically and it is called a database in this chapter. A database is important information. You are recommended to periodically back up a periodical database, when the capacity of repositories becomes insufficient by long-time running and employment changed from the first time plan, in preparation for the unexpected accident. (It differs from the database used for the transaction of the database of ORACLE etc.)

The following table lists instances when the acquisition timing is needed.

[Table: Databases on a storage management server]

[Table: Databases on a storage server]

[Table: Databases on a tape server]

You can make 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.

9.1.1 Making individually backup of databases 

9.1.1.1 Maintaining a backup a management list

This chapter describes maintenance of a backup management list. A backup management list is maintained on the server that performs the backup operation.

9.1.1.1.1 Backing up a backup management list

A backup management list is backed up.

For details, please refer to "Resource backup command (swstresback)."

+Backup management list backup data size

Check the size that the subordinate of the following directory has.

/etc/opt/FJSVswsts/data

In the cluster environment, check the size that the subordinate of the following directory has.

/etc/opt/FJSVswsts/<logic node name>/data

When you reuse a directory used before to save the data, the size of said directory must be three times greater than the size indicated above.

9.1.1.1.2 Restoring a backup management list

A backup management list is restored.

For details, please refer to "Resource restore command (swstresrst)."

9.1.1.2 Maintaining a replication management list 

This chapter describes maintenance of a replication management list.

9.1.1.2.1 Backing up a replication management list

To back up a replication management list, back up the repository of the storage management server. For information about backing up a repository, see "Database save command (saving a database)."

• Operation information for replication management is saved in a repository.

• It is recommended that a replication management list be backed up when operation information for replication management is changed with the replication volume information setting command (swsrpsetvol) or the replication volume information deletion command (swsrpdelvol).

9.1.1.2.2 Restoring a replication management list 

Take the following steps to restore a replication management list.

1. Restore the repository on the storage management server. For information about restoring a repository, see "Database recovery command (recovering a database)."

2. On the storage server, execute the resource adjustment command (swsrprecoverres) with the r option specified. For details of the resource adjustment command, see "Resource adjustment command(swsrprecoverres)".

• When the procedure above is performed, operation information for replication management of a repository is copied to a storage server, where it is available for use.

• When the operation information for replication management in the repository does not need to be changed and only the operation information for replication management on the storage server is incorrect for some reason, perform the procedure above.

9.1.1.3 Maintaining a database 

This chapter describes maintaining a database used by a storage management server.

9.1.1.3.1 Saving a database

Execute the database save command to save a database space.

Execute this command on the Storage management server.

• To execute the database save command, log in as a root user.

• Use the locale specified at storage management server installation (or at Symfoware installation if Symfoware has already been installed).

• Processing may not end normally if a window operation is used or another command is executed while this executed command is being processed. In this event, retry processing after waiting for a short period of time.

• If no data is saved by this command, the respective database cannot be recovered with the database recovery method if an error such as an input-output error occurs in the database space.

• When the storage management server is in cluster operation, you should prepare directories into which data is saved on shared disks.

1. Specification

   # /opt/swstorage/bin/stgdbdmp -d Backup-Directory [ -y ]

   
   

2. Explanation of options

   Option	Explanation
   -d	Specify the name of the directory in which to save a database space. This directory must be created in advance.
   -y	If saved contents remain in the specified directory, they are overwritten when the database space is saved. If this option is omitted and saved contents remain in the specified directory, processing ends without saving the database space.

3. End status

   = 0: Normal end

   > 0: Abnormal end

4. Execution example

   # /opt/swstorage/bin/stgdbdmp -d /storage/dmpdir -y ////// AdvancedCopy Manager database save ////// ================================================================== DB data will be saved. ================================================================== Editing of the work file used for save processing is complete. . Update of the DB space is suppressed. Forced switching of archive log files is complete. ......................... Save processing of DSI data is complete. Archive log files have been completely discarded. Save processing of RDB dictionary data is complete. Suppression of DB space updates has been completely canceled. ================================================================== Save processing of DB data is complete. ================================================================== Database save processing ended normally. #

• Use this save method only when configuration information is changed due to an addition of a storage server or fetching of device information. You are recommended to periodically save a database, for example, once a day.

• To prepare for an input-output error in an external file while save data is being acquired, you are recommended to keep at least two generations of save data.

+Database backup data size

Calculate the size with the following formula:

9.1.1.3.2 Finding an error in a database

Refer to the following file, and beginning from the last line, search for any message with "rdb: ERROR: qdgXXXXX-" in its contents (also check the messages output at the same time). Then, obtain the value of "qdgXXXXX" to determine the recovery mode.

(For non-cluster operation) /var/opt/FJSVswstf/log/RDBSWSTF.log

(For cluster operation) /var/opt/FJSVswstf/logical-node-name/log/RDBSWSTF.log

Table9.1 Relationships between the qdg message and recovery mode

• If multiple errors occur simultaneously, recovery using recovery modes 1 to 5 may not be possible. To restore a database to its state when it was last saved, re-create the database and execute the database save command in recovery mode 0. (Data reflected after the last time the database was saved cannot be recovered.)

• At this point, execute the resource match command (see "Resource match command") with option -x on all the storage servers on which the backup operation is performed. Moreover, execute the resource adjustment command (see "Resource adjustment command") with option -r on all the storage servers on which the replication operation is performed.

9.1.1.3.3 Recovering a database

Execute the database recovery command for database recovery if an input-output error occurs in a database space.

Execute this command on the Storage management server.

• To execute the database recovery command, log in as a root user.

• Use the locale specified at storage management server installation (or at Symfoware installation if Symfoware has already been installed).

• After the database recovery command ends normally, acquire the latest save data using the saving database. Fujitsu recommends using a different save data storage directory than the save data storage directory used by the recovery command.

• After the database recovery command ends normally, restart (start after stopping) the AdvancedCopy Manager daemons. For an explanation on restarting the daemons, see "Starting and Stopping Daemons."

1. Specification

   # /opt/swstorage/bin/stgdbrcv -m mode [-d Backup-Directory]

   
   

2. Explanation of options

   Option	Explanation
   -m	Specify a recovery mode based on the type of error that occurred in a database space. For the relationship between types of errors and recovery modes, see Table 9.1.
   -d	Specify the name of the directory storing the saved data. This option is required if 0, 1, 2, or 4 is specified in the -m option.

3. End status

   = 0: Normal end

   > 0: Abnormal end

4. Execution example

   # /opt/swstorage/bin/stgdbrcv -m 1 -d /storage/dmpdir ////// AdvancedCopy Manager database recovery ////// ================================================================== DSI recovery (FW mode) will start. ================================================================== Editing of the work file used for recovery is complete. DSI access inhibition is complete. ......................... DSI data recovery is complete. ================================================================== DSI recovery (FW mode) is complete. ================================================================== Database recovery ended normally. #

9.1.1.4 Maintaining authentication management list

This chapter describes maintenance of the authentication feature. Execute the command on the server (storage server) where the authentication feature is implemented.

9.1.1.4.1 Backing up an authentication management list

On a storage management server, execute the /opt/FJSVswssc/bin/smmkbat command to extract authentication management information. The root user must execute this command.

# /opt/FJSVswssc/bin/Smmkbat -f definition-information-output-shell-script-name

Example: /opt/FJSVswssc/bin/smmkbat -f acldata.sh

The definition information output shell script is extracted as a shell script in which the command example for reflecting definition information is described.

+Authentication management list backup data size

Calculate the size with the following formula:

*1 Add the lengths of all accounts with an access permission assigned.

9.1.1.4.2 Restoring an authentication management list

Execute the definition information output shell script. The root user must execute the script.

9.1.1.5 Maintaining a registry 

This chapter describes maintaining a registry. Perform this procedure on a storage management server or a storage server.

9.1.1.5.1 Backing up a registry

Back up the following file by executing the cp command.

1. File names

   In the case of a non-cluster

   /etc/opt/swstorage/swnode.ini

   In the case of a cluster

   /etc/opt/swstorage/Logic node name/swnode.ini

2. Execution example

   Save it in the /backup directory.

   # cp /etc/opt/swstorage/swnode.ini /backup

+Registry backup data size

Check the size of the file to be backed up.

9.1.1.5.2 Restoring a registry

Restore the following file by executing the cp command:

1. File names

   In the case of a non-cluster

   /etc/opt/swstorage/swnode.ini

   In the case of a cluster

   /etc/opt/swstorage/Logic node name/swnode.ini

2. Execution example

   Restore the following file saved in the /backup directory:

   # cp /backup/swnode.ini /etc/opt/swstorage

9.1.2 Making a package backup of databases

This section describes the function for making a backup of management information (e.g., databases) for AdvancedCopy Manager from just one storage server, storage management server, or tape server.

With a package backup of management information, you can make a backup of management information for all storage servers, storage management servers, and tape servers from just one storage server, storage management server, or tape server. Executing a package backup of management information on one storage server, storage management server, or tape server runs backup commands (making backups of backup management resources and databases) for the databases of other storage servers, storage management servers, and tape servers, and collects the backup data and management information created by said backup commands.

The storage server, storage management server, or tape server on which you can execute a package backup of management information is called the package-backup-of-the-management-information execution server. The storage servers, storage management servers, and tape servers whose data is to be backed up are called the package-backup-of-the-management-information target servers.

Example: Assume that the package backup of management information function has been used to back up the management information on a storage management server, storage server A, and storage server B onto storage server B in the diagram above. In this case, storage server B is the management information package backup execution server. The storage management server, storage server A, and storage server B are the management information package backup target servers. That is, storage server B operates as both the management information package backup execution server and a management information package backup target server.

The following table shows the types of management information handled in a package backup of management information.

Storage server management information created by Softek AdvancedCopy Manager 10.3 (V10.0L40) or earlier cannot be handled by the package backup of management information function. To make a backup, back up each management information component individually as described in "Maintaining a database" in the Operator's Guide applicable to the storage server.

9.1.2.1 Preliminaries

Before making a package backup of management information, you must do the following:

1. Determine the management information package backup target servers and the types of management information to be backed up.

2. Determine the management information package backup execution server.

3. 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 Operator's Guide for the operating system running on the storage management server.

   • The required size for an authentication management list is the size of the authentication management list backup data.
     For the backup data size, refer to "Maintaining a database" in the Operator's Guide for the operating system running on the storage 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 Operator's 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 backup data, refer to "Maintaining a database" in the Operator's 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 preprocessing and postprocessing scripts for backup management

     • Sizes of the preprocessing and postprocessing scripts for tape-copy

     • 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

     • Size of the backup volume locking specification file for backups for tape copy

   • The required size for replication management is the total of the following sizes for each management information package backup target server:

     • Size of the preprocessing and postprocessing 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

   • The required size for the policy file for package backup of management information is the size of the policy file backup.

   • The size required for tape management information is 1.2 times the size of backup of the tape management information.
     For details on the size of tape management information, see the section titled "Maintaining Databases" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option.

4. Check the size of the work directory for the management information package backup target servers (or the shared disk for shared data for AdvancedCopy Manager in a cluster system). The sizes described below are needed only when a package backup of management information is being done. 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 Operator's Guide for the operating system running on the storage management server.

   • The required size for the authentication management list is the size of the authentication management list backup data.
     For the backup data size, refer to "Maintaining a database" in the Operator's Guide for the operating system running on the storage 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 Operator's Guide for the operating system running on the management information package backup target server.

   • The work directory does not require any space for registry, replication management, and policy file backups.

   • The size required for tape management information is 2.2 times the size of the backup of tape management information.
     For details on the size of tape management information, see the section titled "Maintaining Databases" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option.

5. Execute the stgmgrinfoset command as described in "Management information package backup server registration/deletion command (stgmgrinfoset)", on the management information package backup execution server (determined in step 2).

6. Create a policy file on the management information package backup execution server.

   Policy file

   Management information package backup execution server		Policy file path
   OS	Operation type
   Windows	Non-cluster	environment-setting-directory\etc\stgmgrinfo_policy.ini
   	Cluster	<AdvancedCopy-Manager-shared-data>:\etc\opt\swstorage\etc\stgmgrinfo_policy.ini
   Solaris HP-UX Linux AIX	Non-cluster	/etc/opt/FJSVswstf/stgmgrinfo_policy.ini
   	Cluster	etc/opt/FJSVswstf/<logical-node-name>/stgmgrinfo_policy.ini

   
   

• Do not specify more than one storage server as a management information package backup execution server.

• When the management information package backup execution server is used for executing transactions on the storage server in a cluster system, create a directory for storing backup data on a shared disk.

• For databases, backup management, authentication management lists, and tape backup management, backup commands are executed on the respective management information package backup target servers. In addition, for database backups, backup management (backup management lists) backups, and tape backup management information backups, a temporary capacity that is approximately 2.2 times greater than the total size of the backups is required to put the backup data in an archive file.

Policy file format:

A: Specifiable, B: Specifiable only when the applicable function is operating on the server, C: Unspecifiable

Example: Set up a policy file as follows:

• The storage management server named ACMMGR creates backups for the database, the authentication feature, and backup management.

• The storage server named ACMAGT1 creates backups for backup management.

• The storage server named ACMAGT2 creates backups for replication management.

• The tape server (name: ACMTAPE) makes a tape backup management backup.

  [ACMMGR] DBData=Yes AuthData=Yes BkupData=Yes [ACMAGT1] BkupData=Yes [ACMAGT2] ReplData=Yes [ACMTAPE] TapeData=Yes

  
  

• 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.

9.1.2.2 Backup operations

Executing the management information package backup command (stgmgrinfobkup) on the management information package backup execution server stores the backup data in the directory under the following structure:

*1 is the backup data storage directory specified by the management information package backup server registration/deletion command (stgmgrinfoset).

Example: When *1 is /ACMBkupData and the server name is ACMAGT1, the preprocessing and postprocessing scripts for backup management are put in the following directory:

/ACMBkupData/ACMAGT1/BkupData/Scripts

+Initial operations

The initial operations are as follows:

1. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make backups of the registries on all of the storage servers.

2. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the policy file.

+Normal-use operations

The normal-use operations are as follows:

1. Execute the management information package backup command (stgmgrinfobkup) 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 Operator's Guide for the applicable operating system.

+Operations when a server is added or deleted

[Operations when server added]

1. On the management information package backup execution server, set up a policy for the added storage server in the policy file.

2. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the registry of the added storage server.

3. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the policy file.

[Operations when server deleted]

1. On the management information package backup execution server, delete the information about the storage server deleted from the policy file.

2. In the backup data directory on the management information package backup execution server, delete the directory having the name of the deleted storage server.

3. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the policy file.

+Operations when server name changed

1. On the management information package backup execution server, delete the information for the storage server from the policy file.

2. In the backup data directory on the management information package backup execution server, delete the directory having the name of the storage server.

3. On the management information package backup execution server, set up a policy for the renamed storage server in the policy file.

4. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the registry of the renamed storage server.

5. Execute the management information package backup command (stgmgrinfobkup) on the management information package backup execution server to make a backup of the policy file.

9.1.2.3 Restore operations

This section describes how to use the backup data created by the management information package backup command (stgmgrinfobkup) to execute restoration.

Perform the operations below as a root user or with an account that belongs to the administrators group.

+Restoring a registry

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the registry backup to the following directory:

   Windows version:
   directory-determined-in-step1\<server-whose-registry-to-be-restored>\RegiData

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-registry-to-be-restored>/RegiData

3. Transfer the registry backup copied in step 2 to the target server in binary mode.

4. Restore the registry on the server. For details on restoring a registry, refer to "Restoring a registry" in the Operator's Guide for the operating system running on the target server.

+Restoring a database

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backup of the database to the following directory:

   Windows version:
   directory-determined-in-step1\<storage-management-server-name>\RegiData

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/< storage-management-server-name>/RegiData

3. Transfer the backup of the database copied in step 2 to the storage management server in binary mode.

4. On the storage management server, expand the database backup transferred in step 3. On the Windows version storage management server, expand the database backup by using the expand backup data command. For the backup data expansion command, refer to the section "Backup data expansion command (stgarcext)" in this manual. On a Solaris/Linux-version storage management server, expand the database backup by using the tar command supported by the operating system.

5. On the storage management server, restore the database. For details on restoring a database, refer to "Restoring a database" in the Operator's Guide for the operating system running on the storage management server. The backup data storage directory specified for database restoration is the directory expanded in step 4.

+Restoring an authentication feature

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backup of the authentication management list to the following directory:

   Windows version:
   directory-determined-in-step1\<storage-management-server-name>\AuthData

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<storage-management-server-name>/AuthData

3. Transfer the backup of the authentication management list copied in step 2 to the storage management server in binary mode.

4. On a Solaris/Linux-version storage management server, change the access permission assigned to the backup of the authentication management list transferred in step 3 by using the chmod command supported by the operating system. Set execution permission for the root user, which is the owner.

5. On a Windows-version storage management server, copy the backup of the authentication management list transferred in step 3 to -AdvancedCopy-Manager-program-directory\bin.

6. On the storage management server, restore the authentication management list. For details on restoring the authentication management list, refer to "Restoring an authentication management list" in the Operator's Guide for the operating system running on the storage management server. A definition output batch file and a definition output shell script are the backup data of the authentication management list handled in steps 4 and 5.

+Restoring a backup management list, or backup management list and recovery control file

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution 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:

   Windows version:
   directory-determined-in-step1\<server-whose-list/file-to-be-restored>\BkupData\FJSVswsts

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-list/file-to-be-restored>/BkupData/FJSVswsts

3. 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.

4. 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 by using the expand backup data command. For the backup data expansion command, refer to the section "Backup data expansion command (stgarcext)" in this manual. 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.

5. 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 Operator's 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 preprocessing/ postprocessing scripts and tape-copy preprocessing/postprocessing scripts

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backups of the backup management preprocessing/ postprocessing scripts and tape-copy preprocessing/postprocessing scripts to the following directory:

   Windows version:
   directory-determined-in-step1\<server-whose-scripts-to-be-restored>\BkupData\Scripts

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-scripts-to-be-restored>/BkupData/Scripts

3. Transfer the backups of the backup management preprocessing /postprocessing scripts and tape-copy preprocessing/postprocessing scripts copied in step 2 to the target server in binary mode.

4. Transfer the backups of the backup management preprocessing/postprocessing scripts and tape-copy preprocessing/postprocessing 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 preprocessing and postprocessing scripts for backup management are executed (that is, the directory to which the scripts are to be copied), refer to "Preprocessing and postprocessing for backup/restoration" in the Operator's Guide for the operating system running on the target server.

5. On a Solaris//Linux/UP-UX/AIX-version server, change the access permission assigned to the preprocessing and postprocessing 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

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backups of the locking specification files for backup management to the following directory:

   Windows version:
   directory-determined-in-step1\<server-whose-files-to-be-restored>\BkupData\data

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-files-to-be-restored>/BkupData/data

3. Transfer the backups of the locking specification files for backup management copied in step 2 to the target server in binary mode.

4. 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,"Preprocessing and Postprocessing of Backup and Restoration", in this manual.

+Restoring preprocessing and postprocessing scripts for replication management

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backups of the preprocessing and postprocessing scripts for replication management to the following directory:

   Windows version:
   directory-determined-in-step1\<server-whose-scripts-to-be-restored>\ReplData\Scripts

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-scripts-to-be-restored>/ReplData/Scripts

3. Transfer the backups of the preprocessing and postprocessing scripts for replication management copied in step 2 to the target server in binary mode.

4. Copy the backups of the preprocessing and postprocessing 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 preprocessing and postprocessing scripts for replication management are executed (that is, the directory to which the scripts are to be copied), refer to "Preprocessing and postprocessing of replication" in the Operator's Guide for the operating system running on the target server.

5. On a Solaris//Linux/UP-UX/AIX-version server, change the access permission assigned to the preprocessing and postprocessing 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

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the backups of the locking specification files for replication management to the following directory:

   Windows version:
   directory-determined-in-step1\<server-whose-files-to-be-restored>\ReplData\data

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-files-to-be-restored>/ReplData/data

3. Transfer the backups of the locking specification files for replication management copied in step 2 to the target server in binary mode.

4. 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 Appendix C,"Preprocessing and Postprocessing of Replication", in this manual.

+Restoring a policy file for management information package backup

1. Execute the management information package backup server registration/deletion command (stgmgrinfoset) on the management information package backup execution server to determine which directory contains the backup data.

2. On the management information package backup execution server, copy the policy file located in the following directory to the policy file for the management information package backup command:

   Windows version:
   directory-determined-in-step1\<server-whose-file-to-be-restored>\MgrInfoData

   Solaris, Linux, HP-UX, or AIX version:
   directory-determined-in-step1/<server-whose-file-to-be-restored>/MgrInfoData

   For the directory for the policy file for the management information package backup command, refer to step 6 in the section "Preliminaries" in this manual.

+Restoring the tape management information

1. On the package-backup-of-the-management-information execution server, execute the management information package backup server registration/deletion command (stgmgrinfoset) to check the directory that contains the backup data.

2. On the package-backup-of-the-management-information execution server, copy the backup data of the tape management information from the directory indicated below:

   For the Windows version: directory-checked-at-step-1\<name-of-the-target-server-of-restoration>\TapeData

   For the Solaris/Linux/HP-UX/AIX version: directory-checked-at-step-1/<name-of-the-target-server-of-restoration>/TapeData

3. Transfer the backup data of the tape management information copied in Step 2 to the target server in binary mode.

4. Expand the tape management information transferred in Step 3 on the target server. If the target server is the Solaris or Linux version, expand the tape management information by using the OS tar command.

5. On the target server, restore the tape management information. For details on how to restore it, see the section titled "Restoring the tape management information" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option.

9.2 Troubleshooting

9.2.1 Troubleshooting for insufficient free space in a repository

This chapter describes what to do if there is insufficient free space in a repository used by a storage management server.

Perform this procedure on a storage management server.

You can use this troubleshooting method when there is insufficient free space in a repository and if the operation status is significantly different from the initial installation time to prevent the occurrence of insufficient free space in the repository.

Extend the repository space as follows:

1. Backup of the registry of a Storage management server (See "backing up a registry")

2. Stored data save processing (see chapter "Database backup")

3. Releasing a repository (See "Database unsetup," of the Installation Guide.)

4. Re-estimating the database size (see "Estimating the database space," of the Installation Guide).

5. Re-creating partitions (See "Creating directory," of the Installation Guide.)

6. Creating a repository (See "Database setup," of the Installation Guide.)

7. Starting of a RDB daemon (see "Starting and stopping the RDB Daemon")

8. Save data restore processing (see "Database restoration")

9. Restoration of the registry of a Storage management server (See "Restoring a registry")

9.2.1.1 Database backup

This chapter describes saving data stored in a database to the specified directory collectively.

This method is mainly used for converting data. To save normal operation data, use the method described in "Saving a database."

• A directory in which data will be saved must be created in advance.

• To start the database backup, log in as a root user.

• Use the locale specified at storage management server installation (or at Symfoware installation if Symfoware has already been installed).

Back up a database as follows:

1. Start database backup.

   Enter the following command to start database backup:

   # /opt/swstorage/bin/stgdbbackup

   
   

2. Confirm to continue processing.

   Enter "y" to continue processing or "n" to stop processing.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database backup //////////////////////////////////////////////////////////////////// +----------------------------------------------------------------+ | | | All of the stored data will be saved in an external file. | | | | [Notes] | | Prepare a directory for storing the data to be saved. | | | +----------------------------------------------------------------+ Do you want to continue with processing? [y/n] ==> y

3. Enter the name of the data storage directory the data will be saved in.

   Using an absolute pathname, enter the name of the directory in which to store save data.

   

   If the data has already been saved in the directory the processing is not performed.

   Delete the save data in the directory or specify another directory, and then retry processing.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database backup //////////////////////////////////////////////////////////////////// Enter the absolute path name of the directory for storing the data to be saved. Enter ==> /storage/backdir

4. To continue with database backup processing, enter a final confirmation.

   Enter "y" to continue with database backup processing or "n" to stop it.

   If "y" is entered, the window display returns that of step 2.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database backup //////////////////////////////////////////////////////////////////// Directory containing the saved data : /storage/backdir Do you want to continue with processing? [y/n] ==> y

5. Database backup copies are created.

   Database backup copies are created, and execution results are displayed on the window as necessary. An example of such execution results is shown below.

   ////// AdvancedCopy Manager database backup ////// ================================================================== DB data backup will start. ================================================================== .... Unloading of data is complete.(base) ... Unloading of data is complete.(backup) . Unloading of data is complete.(repl) ================================================================== Backup of DB data is complete. ================================================================== Database backup ended normally. #

9.2.1.2 Database restoration

This chapter describes restoring data that has been saved as described in "Database backup" to a database collectively.

• Data currently stored in a database will be lost in this processing because it will be overwritten by save data.

• To start the database restoration, log in as a root user.

• Use the locale specified at storage management server installation (or at Symfoware installation if Symfoware has already been installed).

When the database restoration is normally completed, the database is saved.

Restore a database as follows:

1. Start database restore processing.

   Enter the following command to start database restore processing:

   # /opt/swstorage/bin/stgdbrestore

   
   

2. Confirm to continue processing.

   Enter "y" to continue processing or "n" to stop processing.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database restore //////////////////////////////////////////////////////////////////// +----------------------------------------------------------------+ | | | All of the saved data will be restored to database. | | | | [Notes] | | Check the directory containing the saved data. | | | +----------------------------------------------------------------+ Do you want to continue with processing? [y/n] ==> y

3. Enter the name of the data storage directory where the data has been saved.

   Using an absolute pathname, enter the name of the directory in which the data is saved.

   

   If any part of saved data in the directory is missing, processing is not performed because data consistency may not be maintained.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database restore //////////////////////////////////////////////////////////////////// Enter the absolute path name of the directory in which the saved data is stored. Enter ==> /storage/backdir

4. To continue with database restore processing, enter the final confirmation.

   Enter "y" to continue with database restore processing or "n" to stop it.

   If "n" is entered, the window display returns to that of step 2.

   //////////////////////////////////////////////////////////////////// AdvancedCopy Manager Storage management server ( kiku ) Database restore //////////////////////////////////////////////////////////////////// Directory containing the saved data : /storage/backdir Do you want to continue with processing? [y/n] ==> y

5. Database restore processing is performed.

   Database restore processing is performed, and execution results are displayed on the window as necessary. An example of such execution results is shown below.

   ////// AdvancedCopy Manager database restore ////// ================================================================== DB data will be restored. ================================================================== .... Loading of data is complete.(base) .... Updating of the optimal information is complete.(base) ... Loading of data is complete.(backup) ... Updating of the optimal information is complete.(backup) . Loading of data is complete.(repl) . Updating of the optimal information is complete.(repl) ================================================================== DB data has been completely restored. ================================================================== Database restore processing ended normally. #

9.2.2 Collecting maintenance information

9.2.2.1 Collecting information using a Web window 

Collect information as follows:

1. Start the Java Plug-in control panel.

   Start the Java Plug-in control panel as follows:

   Select [Settings] - [Control Panel] - [Java Plug-in].

2. Make the startup settings of the Java console.

   On the Java control panel, access the [Basics] tag, mark the [Display Java Console] check box, click the [Apply] button, and exit the Java Plug-in control panel.

3. Start the Web window of AdvancedCopy Manager.

4. The Java console will be started and a message will be output. Save the message to a file, and attach the file to your report.

9.2.2.2 Collecting error survey information 

Log into the storage management server and the storage server. Collect the following information. (When the storage management server is also the storage server, collect resources from both the storage management server and storage server.)

1. When an error occurs during backup management

   Type	Storage management server	Storage server
   System log	Must be collected.	Must be collected.
   Trace log	Acquire the files under the following directory: /var/opt/FJSVswtrc/trc/ Acquire the file when the following file exists. /tmp/f3cvtrc.log	Acquire the files under the following directory: /var/opt/FJSVswtrc/trc/ Acquire the file when the following file exists. /tmp/f3cvtrc.log
   Backup management list	Need not be collected.	Acquire the files under the following directory: /etc/opt/FJSVswsts (Note)
   Common information	Acquire the files under the following directory: /var/opt/FJSVswstf/cluster (Note) /var/opt/FJSVswstf/cmdevs (Note) /var/opt/FJSVswstf/daemon (Note) /var/opt/FJSVswstf/log (Note) /etc/opt/swstorage (Note)	Acquire the files under the following directory: /var/opt/FJSVswstf (Note) /etc/opt/swstorage (Note)

   Note: When cluster operation is performed, the backup management list and the common information are located on the shared disk, where a symbolic link is set. Therefore, when collecting the information, also collect the data on the shared disk as follows.

   # cd /etc/opt # tar -cvfh /tmp/FJSVswsts_node1.tar FJSVswsts swstorage

2. When an error occurs during replication management

   Type	Storage management server	Storage server
   System log	Must be acquired.	Must be acquired.
   Trace log	Get the files under the following directory: /var/opt/FJSVswtrc/trc/ Acquire the file when the following file exists. /tmp/f3cvtrc.log	Get the files under the following directory: /var/opt/FJSVswtrc/trc/ Acquire the file when the following file exists. /tmp/f3cvtrc.log
   Replication management list	Replication management list	Get the files under the following directory: /etc/opt/FJSVswsrp (Note)
   Common information	Get the files under the following directory: /var/opt/FJSVswstf/cluster (Note) /var/opt/FJSVswstf/cmdevs (Note) /var/opt/FJSVswstf/daemon (Note) /var/opt/FJSVswstf/log (Note) /etc/opt/swstorage (Note)	Get the files under the following directory: /var/opt/FJSVswstf (Note) /etc/opt/swstorage (Note)

   Note: When cluster operation is performed, the replication management list and the common information are located on the shared disk, where a symbolic link is set. Therefore, when collecting the information, also collect the data on the shared disk as follows.

   # cd /etc/opt # tar -cvfh /tmp/FJSVswsrp_node1.tar FJSVswsrp swstorage

9.2.3 Troubleshooting for a failure in access to a repository database 

This chapter describes finding a cause for a failure in access to a repository database and what to do in such a case.

Perform this procedure on the storage management server.

1. Check whether the RDB daemons have not stopped.

   [Check method]

   Execute the following command to check for any processing related to the RDB daemons.

   # ps -ef | grep RDBSWSTF | grep -v grep

   [Required action]

   If no processing related to the two RDB daemons exists, retry processing after restarting (start after stopping) the daemons. For an explanation on restarting the daemons, see "Starting and stopping the RDB daemons."

   

   When Symfoware 6.x has been introduced before AdvancedCopy Manager is introduced, the process related to the existing RDB daemon becomes three.

2. Check that there is sufficient free space as required to update a repository database.

   [Check method]

   Execute the following command to check the usage ratio of space required to update a repository.

   # /opt/swstorage/bin/stgdbloginf

   [Required action]

   If the usage ratio is 100%, save the database space according to "Saving a database". (Consequently, there will be sufficient free space required to update a repository.)

   After using the database save method, restart (start after stopping) the RMI daemon. For an explanation on restarting the daemon, see "Starting and stopping the RMI daemon".

   Then, perform this step again.

3. Check whether the database save processing is in progress.

   [Check method]

   Execute the following command to check for any processing related to the database save command.

   # ps -ef | grep stgdbdmp | grep -v grep

   [Required action]

   If processing related to the database save command exists, retry processing after waiting for the end of the database save command.

4. It checks whether the capacity of repository is insufficient.

   [Check method]

   A /var/opt/FJSVswstf/log/RDBSWSTF.log file (at the time of cluster employment, they are /var/opt/FJSVswstf / logic node name / log/RDBSWSTF.log) is referred to sequentially from the last line, and it is "rdb. : ERROR : Please check whether the message described to be qdgXXXXXX-" is searched and "JYP5019E" or "JYP5045E" exists in a message.

   [Required action]

   If it exists, please extend repository capacity with reference to "Troubleshooting for insufficient free space in a repository" of this manual. Then, please re-perform processing.

5. Check whether an input-output error or any other error has occurred in the database space.

   [Check method]

   Refer to the /var/opt/FJSVswstf/log/RDBSWSTF.log file (in cluster operation, /var/opt/FJSVswstf/logical-node-name/log/RDBSWSTF.log file), and beginning from the last line, search for any message with "rdb: ERROR: qdgXXXXX-" in its contents (also check the messages output at the same time). Then, obtain the value of "qdgXXXXX," and check for it in Table 9.1.

   [Required action]

   If "qdgXXXXX" is in the table, examine the target according to the error description corresponding to the qdg messages in Table 9.1, and determine if there is a problem. If a problem is found, take steps to solve the problem, and specify the appropriate settings. Then, recover the database space by using the database recovery method.

   After the database recovery command ends normally, acquire the latest save data by using the database save method.

   Then, restart (start after stopping) the AdvancedCopy Manager daemons. For an explanation on restarting the daemons, see "Starting and stopping the AdvancedCopy Manager daemons".

   Retry processing.

   

   If the database recovery command is executed with 0 specified for option -m, execute the resource consistency command specified with option -x (see "Resource match command") on all Storage servers in a backup operation.

   Moreover, please attach and perform option-r to a resources adjustment command (see "Resource adjustment command") on all the Storage servers that are performing replication employment.

   

   If an error such as an input-output error occurs in a database space, a file required for analyzing the cause of the error may be created in /SWSTFDB/core. If the corresponding recovery ends normally, delete the file in this directory.

6. Collect the files in /var/opt/FJSVswstf/log, and contact a Fujitsu SE.

9.3 Troubleshooting for a hardware error, etc. occurring during backup

This chapter describes what to do for a hardware error, etc. occurring during a backup using AdvancedCopy Manager.

9.3.1 Overview 

If a hardware error occurs during backup operation, the following symptoms are generated:

• The backup execution status display command (swstbackstat) displays "failed" in the Status column.

• The synchronous backup operation status display command (swstsyncstat) displays "failed" in the Status column.

• The restoration execution status display command (swstreststat) displays "failed" in the Status column.

• The history information display command (swsthistdisp) displays "failed" in the Status column.

• The tracking status display command (swsttrkstat) displays "failed" in the Status column.

• Code swst0634, swst0719, or swst0902 is displayed during command execution.

If the execution status display command and history information display command display "failed" in the Status column, a hardware error has occurred during physical copying, and the copy processing has failed.

If swst0634, swst0719, or swst0902 is output during command execution and the same error occurs even if the command is reexecuted, a hardware error has occurred, causing AdvancedCopy to fail.

If a hardware error occurs during remote copying, the following symptoms may be generated:

• The backup execution status display command (swstbackstat) displays "halt" in the Status column.

• The synchronous backup operation status display command (swstsyncstat) displays "halt" in the Status column.

• The restoration execution status display command (swstreststat) displays "halt" in the Status column.

• The history information display command (swsthistdisp) displays "halt" in the Status column.

If the execution status display command and history information display command display "halt" in the Status column, a hardware error has occurred during physical copying, and the remote copy processing has failed.

If these symptoms are generated, a hardware error may have occurred in the transaction volume or backup volume. Check the hardware status, and if a hardware error is found, remove the cause of the error, and reexecute the processing.

9.3.2 Troubleshooting 

9.3.2.1 Troubleshooting for a hardware error, etc. on a transaction volume

When a hardware obstacle occurs in operating volume, please perform the repair work of an obstacle according to the following procedures.

1. If an error occurred during physical copying, cancel the the processing in which the error occurred.

   • If an error occurred during backup (OPC) physical copy: swsthistdel command

   • If an error occurred during synchronous processing (EC): swstcancelsync command

   • If an error occurred during restore (OPC) physical copy: swstcancelrest command

   • If an error occurred during tracking processing (QuickOPC): swstcanceltrk command

2. Execute the execution status display commands (swstbackstat,swstsyncstat,swstreststat,swsttrkstat), and history information display command (swsthistdisp) to verify that no other errors are found.

3. Remove the hardware error of the transaction volume.

4. Execute the restoration execution command (swstrestore) to restore the transaction volume.

9.3.2.2 Troubleshooting for a hardware error, etc. on a backup volume

When a hardware obstacle occurs in backup volume, please perform repair work, such as an obstacle, according to the following procedures.

1. Cancel the processing in which the error occurred.

   • If an error occurred during backup (OPC) physical copy: swsthistdel command

   • If an error occurred during synchronous processing (EC): swstcancelsync command

   • If an error occurred during restoration (OPC) physical copy: swstcancelrest command

   • If an error occurred during tracking processing (QuickOPC): swstcanceltrk command

2. If the processing cannot be canceled by using the command, use GRmgr to cancel it.

3. Execute resource match command (swstsrsemtch)

4. Cancel the processing in which the error occurred. At this point, the execution status display commands (swstbackstat, swstreststat) and history information display command (swsthistdisp) display "succeeded" in the Status column. However, because the copy processing is suspended, be sure to cancel the commands. If an error occurred in the synchronous processing (EC), the command has already been canceled, so no response is required.

   • If an error occurred during backup (OPC) physical copy: swsthistdel command

   • If an error occurred during restoration (OPC) physical copy: swstcancelrest command

5. Execute the execution status display commands (swstbackstat,swstsyncstat,swstreststat,swsttrkstat) and history information display command (swsthistdisp) to verify that no other errors are found.

6. Use the device information setting command (swstdevinfoset) to delete the backup volume in which the error occurred.

7. Use the device information setting command (swstdevinfoset) to register a new backup volume. If the backup volume in which the error occurred is repaired and reused, execute [Collect or reflect the information for a specific device] from the initial window and store the information again in the backup volume.

8. Reexecute the processing in which the error occurred.

9.3.2.3 Troubleshooting for an error (halt) on a remote copy processing 

1. Remove the hardware error.

2. The suspended copy processing is reexecuted.

9.4 Troubleshooting for a Hardware Error or Other Error Occurring during Replication 

This chapter describes the corrective action for hardware or other error occurring during AdvancedCopy Manager replication.

9.4.1 Overview 

If a hardware error occurs during replication operation, the following symptoms are generated:

• The operation status display command (swsrpstat) displays "failed" or "?????"in the Status column.

• Code swsrp2606 is output during command execution.

• Code swsrp0634, swsrp0719, or swsrp0902 is output during command execution.

If the operation status display command displays "failed" in the Status column, and swsrp2606 is output during command execution, a hardware error has occurred during physical copying, and the copy processing has failed.

If swsrp0634, swsrp0719, or swsrp0902 is output during command execution, and the same error occurs even if the command is reexecuted, a hardware error has occurred, causing AdvancedCopy to fail.

If a hardware error occurs during remote copying, the following symptoms may be generated:

• The operation status display command (swsrpstat) displays "halt" in the Status column.

• Code swsrp2648 is output during command execution.

If the operation status display command displays "halt" in the Status column, and swsrp2648 is output during command execution, a hardware error has occurred during physical copying, and the remote copy processing has failed.

If these symptoms are generated, a hardware error may have occurred in the original or replica volume. Check the hardware status, and if a hardware error is found, remove the cause of the error and reexecute the command.

9.4.2 Troubleshooting 

9.4.2.1 Troubleshooting for a hardware error on a replication volume 

When a hardware obstacle occurs in duplicate volume, please perform the repair work of an obstacle according to the following procedures.

1. Use the operation cancel command (swsrpcancel) to cancel the processing in which the error occurred. If the processing cannot be canceled from the operator server when interserver replication is performed, cancel it from a nonoperator server.

2. If the processing cannot be canceled by using the command, use GRmgr to cancel it.

3. Execute the resource adjustment command (swsrprecoverres)

4. Execute the operation status display command (swsrpstat) to verify that no other errors are found.

5. Use the replication volume information deletion command (swsrpdelvol) to delete the replication volume in which the error occurred.

6. Use the replication volume information setting command (swsrpsetvol) to register a new replication volume. If the replication volume in which the error occurred is repaired and reused, execute [Collect or reflect the information for a specific device] from the initial window and store the information again in the replication volume.

7. Reexecute the processing in which the error occurred.

9.4.2.2 Troubleshooting for an error (halt) on a remote copy processing 

1. Remove the hardware error.

2. The suspended copy processing is reexecuted.

9.5 Changing the Operating Environment

9.5.1 Changing the IP address of a storage management server

Change the IP address of a storage management server as follows:

If only a physical IP address should be changed and the storage management server uses a logical IP address, then perform only steps 2 and 6. Otherwise, perform all steps.

1. It checks whether the Storage management server for change serves as the Storage server. When serving and you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to "Deleting an original volume or replica volume" in the ETERNUS SF AdvancedCopy Manager Operator's Guide.

2. On the storage management server, change the system IP address.

3. On the storage management server, execute the server information change command. For more information on the server information change command, see "Management server information change command (stgcmmodnode)".

4. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see "Management server information change command (stgcmmodnode)".

5. On the storage management server, restart the damons of AdvancedCopy Manager. For information on restarting a damons, see "Starting and Stopping a Daemons".

6. If the storage management server uses a logical IP address, use the Web screen to change the settings of authentication-related files.
   Change the definition part of the logical IP address to a new logical IP address when the logical IP address is changed, while referring to the section called "Downloading authentication-related files" in the ETERNUS SF AdvancedCopy Manager User's Guide. This operation can also be applied to a physical IP address when it is changed.

About change by cluster operation, see "Changing the IP address of a storage management server transaction".

9.5.2 Changing the IP address of a storage server 

Change the IP address of a storage server as follows:

This step is unnecessary if only a physical IP address should be changed and the storage server uses a logical IP address.

For more information on the Web window, see "Changing the IP address of a storage server" of the "ETERNUS SF AdvancedCopy Manager User's Guide".

1. When you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to "Deleting an original volume or replica volume" in the ETERNUS SF AdvancedCopy Manager Operator's Guide.

2. On a target storage server, stop daemons of AdvancedCopy Manager. For more information on stopping a service, see "Starting and Stopping a Daemons".

3. On the storage server, change the system IP address.

4. On the storage server, start daemons of AdvancedCopy Manager. For more information on starting a service, see "Starting and Stopping a Daemons".

   Later, follow steps 5 and 6 if the address is changed by using the Web screen, and follow step 7 if the address is changed by using a command.

5. On the server list view on the initial window of AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window.

6. On the [Change of server] window, change the IP address and click the [OK] button.

7. Change the IP address by using the server information change command on the Web server. Refer to "Server information change command(stgxfwcmmodsrv)," for details on the server information change command.

About change by cluster operation, see "Changing the IP address of a storage server transaction".

9.5.3 Changing the port number of a storage management server

Change the port number of a storage management server as follows:

1. It checks whether the Storage management server for change serves as the Storage server. When serving and you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to "Deleting an original volume or replica volume" in the ETERNUS SF AdvancedCopy Manager Operator's Guide.

2. The port number of the communication daemon (stgxfws) of AdvancedCopy Manager indicated by /etc/services by the Storage management server is changed.

   When the storage management server is being operated on the cluster, change the port number of the communication daemon (stgxfws_logic node name) of Storage management server transaction.

3. On the storage management server, execute the server information change command. For more information on the server information change command, see "Management server information change command (stgcmmodnode)".

4. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see "Management server information change command (stgcmmodnode)".

5. On the storage management server, restart the daemons of AdvancedCopy Manager. For information on restarting a service, see "Starting and Stopping a Daemons".

About change by cluster operation, see "Changing the port number of a storage management server transaction".

9.5.4 Changing the port number of a storage server 

Change the port number of a storage server as follows:

For more information on the Web window, see "Changing the port number of a storage server" of the " ETERNUS SF AdvancedCopy Manager User's Guide".

1. When you define by the Storage server used as the candidate for change as a replication source or replication destination volume using a replication management function, please delete a setup of an original / replica volume with reference to "Deleting an original volume or replica volume" in the ETERNUS SF AdvancedCopy Manager Operator's Guide.

2. On a target storage server, stop services of AdvancedCopy Manager. For more information on stopping a deamon, see "Starting and Stopping a Daemons".

3. On the storage server, change the port number of the communications daemon (stgxfws) of AdvancedCopy Manager.

   When the storage server is being operated on the cluster, change the port number of the communication daemon (stgxfws_logic node name) of Storage server transaction.

4. On the storage server, start daemons of AdvancedCopy Manager. For more information on starting a daemon, see "Starting and Stopping a Daemons".

   Later, follow steps 5 and 6 if the address is changed by using the Web screen, and follow step 7 if the address is changed by using the command.

5. On the server list view on the initial window of AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window.

6. On the [Change of server] window, change the port number and click the [OK] button.

7. Change the IP address by using the server information change command on the Web server. Refer to "Server information change command(stgxfwcmmodsrv)," for details on the server information change command.

About change by cluster operation, see "Changing the port number of a storage server transaction".

9.5.5 Changing the server name of a storage management server

Change the server name of a storage management server as follows:

For more information on the Web window, see "Changing the server name of a storage management server" of the "ETERNUS SF AdvancedCopy Manager User's Guide".

1. Check whether the target storage management server serves also as a storage server. If it does, do as described in "Changing the server name of a storage server". Then, please perform Procedure 5.

   Later, follow steps 2 and 3 if the address is changed by using the Web screen, and follow step 4 if the address is changed by using the command. Later, follow step 5.

2. On the server list view on the initial window of AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window.

3. On the [Change of server] window, change the server name and click the [OK] button.

4. Change the server name by using the server information change command on the Storage server. Refer to " Server information change command(stgxfwcmmodsrv)"for details on the server information change command.
   Later, follow step 5.

5. Execute the server information change command on all Storage servers managed by the Storage management server. Refer to "Manager server information change command(stgcmmodnode) ," for details on the server information change command.

About change by cluster operation, see "Changing the server name of a storage management server transaction".

9.5.6 Changing the server name of a storage server

Change the server name of a storage server as follows:

For more information on the Web window, see "Changing the server name of a storage server" of the "ETERNUS SF AdvancedCopy Manager User's Guide".

1. In the Storage server used as the candidate for change, when the definition is given as a original or replica volume using a replication management function, please delete a setup of a original/ replica volume with reference to "Deleting an original volume or replica volume" in the ETERNUS SFAdvancedCopy Manager Operator's Guide.

   Later, follow steps 2 and 3 if the address is changed by using the Web screen, and follow step 4 if the address is changed by using the command.

2. On the server list view on the initial window of AdvancedCopy Manager, select a server with information to be changed, select [Change of server] from the [Operation] menu, and display the [Change of server] window.

3. On the [Change of server] window, change the server name and click the [OK] button.

4. Change the server name by using the server information change command on the Storage server. Refer to " Server information change command(stgxfwcmmodsrv)"for details on the server information change command.

About change by cluster operation, see "Changing the server name of a storage server transaction".

9.5.7 Changing the device configuration

Changing the device configuration refers to any of the following:

• Mount name change

• Change from File System operation to RawDevice operation

• Capacity change of partitions (mainly for re-creation of LUN mapping)

• Start position for change of partitions (mainly for re-creation of LUN mapping)

9.5.7.1 Backup management 

Change the device configuration in the following procedure. This processing is executed for all volumes on the disk where the volume whose device configuration is to be changed is located.

1. Check whether there is a transaction volume on the target disk that needs to be backed up. If it does, delete the transaction volume. For information on deleting a transaction volume, see "Deleting a transaction volume".

2. Check whether a backup volume exists in the target disk. If it does, delete the backup volume. For information on deleting a backup volume, see "Deleting a backup volume".

3. Change the device configuration.

4. Because the postchange device configuration needs to be reflected in the AdvancedCopy Manager data set, execute device information change processing for AdvancedCopy Manager. Refer to "Fetching device information on a storage server," for details on changing the device information.

5. Set a deleted transaction volume or backup volume again in the backup operation. Refer to "Setting the operation type for a device," for details on adding the transaction volume or backup volume.

If the device configuration is changed (step 3) before the transaction volume and backup volume are deleted (steps 1 and 2), history information cannot be deleted and synchronized backup processing cannot be cancelled, thereby possibly disabling deletion of the transaction volume and backup volume.
In this event, set the emergency operation mode, and delete history information or cancel synchronized backup processing.
For details on the emergency operation mode, see the section describing the history information deletion command (swsthistdel) and the synchronized backup processing cancel command (swstcancelsync).

9.5.7.2 Replication management 

Change the device configuration as shown below. When executed, this processing applies to all the volumes on a disk on which a volume whose device configuration to be changed is stored.

1. Check whether there are any replication volumes on the target disk. If there are, delete them. For information about deleting a replication volume, see "Deleting a replication source volume and replication destination volume".

2. Change the device configuration.

3. Because the postchange device configuration needs to be reflected in the AdvancedCopy Manager data set, execute device information change processing for AdvancedCopy Manager. Refer to "Fetching device information from a storage server," for details on changing the device information.

4. Set a deleted replica volume again in the replication operation. Refer to "Setting the original volume and replica volume," for details on adding the replica volume.

If the device configuration is changed (step 2) before the replication volumes are deleted (steps 2), replication processing cannot be cancelled, thereby possibly disabling deletion of the replication volumes.
In this event, set the emergency operation mode, cancel replication processing.
For details on the emergency operation mode, see the section describing the Replication volume information deletion command (swsrpdelvol).

9.5.8 Changing the IP address for GUI connection of a Storage management server 

The Storage management server is equipped with two or more network cards, and in order to divide and employ the IP address specified in case the IP address (IP address specified when it was the database creation at the time of Storage management server introduction) and Web screen with a Storage server which communicate are used, the IP address for GUI connection is changed using a GUI connection information setting command.

Please refer to GUI connection information setting command and "GUI connection information setting command (stgguiipset)."

When the storage management server has multiple network cards, you must configure the cards on the client side.

For an explanation on how to specify the settings, see "Setting of authentication-related files," in the ETERNUS SF AdvancedCopy Manager User's Guide.

9.5.9 Change of deletion/password of the user who specified it as the repository access user

When a user is deleted on OS about the "repository access user" who specified by the setup of repository at the time of manager introduction of AdvancedCopy Manager, or when the password to the specified user name is changed on OS, the information of a "repository access user" is re-set up using a repository access user change command.

Please refer to "Repository access user change command (stguserset)" about a repository access user change command.

About change by cluster operation, see "Deleting a repository accessible user or changing a repository accessible user's password".

9.5.10 About change of the employment environment in cluster employment 

This section describes how to make a change to the operational configuration in cluster operation.

9.5.10.1 Changing the IP address of a storage management server transaction

Change the IP address of a storage management server transaction by taking the following steps:

1. Check whether the target storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Check whether the target storage management server transaction also functions as a storage server transaction. When it also functions as a storage server transaction, and defined as an original/replica volume by the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. Stop the storage management server transaction.
   For details on how to stop it, see the relevant cluster software manual.

4. Change the IP address resource.
   For details on how to change an IP address resource, see the relevant cluster software manual.

5. Check whether the storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

6. On the node on which the storage management server transaction is running, execute the management server information change command (stgcmmodnode).
   For details on the management server information change command, see "Commands" in this manual.

7. On all storage servers managed by the storage management server transaction, execute the management server information change command.
   For details on the management server information change command, see the chapter titled "Commands" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the operating system on which each respective storage server is running.

8. Restart the storage management server transaction.
   For details on how to stop and start it, see the relevant cluster software manual.

9. Edit the authentication-related file (swstorage.policy).
   When using Web screens, make a change to the authentication-related file configuration. Change the logical IP address to the new logical IP address in the authentication-related file on all terminals that use Web screens by referencing the description in "Configuring the authentication-related file" in the ETERNUS SF AdvancedCopy Manager User's Guide.
   When the physical IP address must be changed too, also change the physical IP address to the new physical IP address in the file.

10. To use the replication control function, rebuild the replication control environment.

The IP address displayed by the cluster setup command executed to delete the cluster environment of the storage management server transaction is not the IP address newly specified, but the IP address specified by the cluster setup command.

9.5.10.2 Changing the IP address of a storage server transaction

Change the IP address of a storage server transaction by taking the following steps:

1. Check whether the target storage server transaction is operating.
   If the transaction is not operating, start the storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. When it is defined as an original or replica volume by using the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. Stop the storage server transaction.
   For details on how to stop it, see the relevant cluster software manual.

4. Change the IP address resource.
   For details on how to change an IP address resource, see the relevant cluster software manual.

5. Start the storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

6. On the server list shown on the AdvancedCopy Manager's initial screen, select the storage server transaction whose information is to be changed, and then select [Change Server] from the [Operation] menu to display the [Change Server] window. On the [Change Server] window, change the IP address, and then click the [OK] button.
   Alternatively, on the storage management server, use the server information change command (stgxfwcmmodsrv) to change the IP address. For details on the server information change command, see the chapter titled "Commands" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the operating system on which the respective storage management server is running.

7. To use the replication control function, rebuild the replication control environment.

9.5.10.3 Changing the port number of a storage management server transaction

Change the port number of a storage management server transaction by taking the following steps:

1. Check whether the target storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Check whether the target storage management server transaction also functions as a storage server transaction. When it also functions as a storage server transaction, and defined as an original/replica volume by the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. Stop the storage management server transaction.
   For details on how to stop it, see the relevant cluster software manual.

4. On the primary node and secondary node, change the port number of transaction-intended communication daemon of AdvancedCopy Manager (stgxfws_logical-node-name) specified in /etc/services.

5. Start the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

6. On the primary node, execute the management server information change command (stgcmmodnode).
   For details on the management server information change command, see "Commands" in this manual.

7. On all storage servers managed by the storage management server transaction, execute the management server information change command. For details on the management server information change command, see the chapter titled "Commands" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the operating system on which each respective storage server is running.

8. Restart the storage management server transaction.
   For details on how to stop and start it, see the relevant cluster software manual.

9. To use the replication control function, rebuild the replication control environment.

9.5.10.4 Changing the port number of a storage server transaction

Change the port number of a storage server transaction by taking the following steps:

1. Check whether the target storage server transaction is operating.
   If the transaction is not operating, start the storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. When it is defined as an original or replica volume by using the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. Stop the storage server transaction.
   For details on how to stop it, see the relevant cluster software manual.

4. On the primary node and secondary node, change the port number of transaction-intended communication daemon of AdvancedCopy Manager (stgxfws_logical-node-name) specified in /etc/services.

5. Start the storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

6. On the server list shown on the AdvancedCopy Manager's initial screen, select the storage server transaction whose information is to be changed, and then select [Change Server] from the [Operation] menu to display the [Change Server] window. On the [Change Server] window, change the port number, and then click the [OK] button.
   Alternatively, on the storage management server, use the server information change command (stgxfwcmmodsrv) to change the port number. For details on the server information change command, see the chapter titled "Commands" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the operating system on which the respective storage management server is running.

7. To use the replication control function, rebuild the replication control environment.

9.5.10.5 Changing the server name of a storage management server transaction

Change the server name of a storage management server transaction by taking the steps below. To continue operation by setting the same logical node name as the server name (and also changing the logical node name), perform the steps described in the section "Changing the logical node name" in this manual.

1. Check whether the target storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Check whether the target storage management server transaction also functions as a storage server transaction. When it also functions as a storage server transaction, do the following:
   When it is defined as an original or replica volume by using the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. On the server list shown on the AdvancedCopy Manager's initial screen, select the storage management server transaction whose information is to be changed, and then select [Change Server] from the [Operation] menu to display the [Change Server] window. Change the server name on the [Change Server] window, and then click the [OK] button.
   Alternatively, on the storage management server transaction, use the server information change command (stgxfwcmmodsrv) to change the server name. For details on the server information change command, see "Commands" in this manual.

4. On all storage servers managed by the storage management server transaction, execute the management server information change command (stgcmmodnode). For details on the management server information change command, see the chapter titled "Commands" in the ETERNUS SF AdvancedCopy Manager Operator's Guide for the operating system on which each respective storage server is running.

5. To use the backup management or replication control function, rebuild the backup management or replication control environment, respectively.

9.5.10.6 Changing the server name of a storage server transaction

Change the server name of a storage server transaction by taking the steps below. To continue operation by setting the same logical node name as the server name (and also changing the logical node name), perform the steps described in the section "Changing the logical node name" in this manual.

1. Check whether the target storage server transaction is operating.
   If the transaction is not operating, start the storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Delete the configuration of the storage server transaction.
   When it is defined as an original or replica volume by using the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

3. On the server list shown on the AdvancedCopy Manager's initial screen, select the storage server transaction whose information is to be changed, and then select [Change Server] from the [Operation] menu to display the [Change Server] window. Change the server name on the [Change Server] window, and then click the [OK] button.
   Alternatively, on the storage management server, use the server information change command (stgxfwcmmodsrv) to change the server name. For details on the server information change command, see the chapter titled "Commands" in the ETERNUS SFAdvancedCopy Manager Operator's Guide for the operating system on which the respective storage management server is running.

4. To use the backup management or replication control function, rebuild the backup management or replication control environment, respectively.

9.5.10.7 Deleting a repository accessible user or changing a repository accessible user's password

Make a change to a repository accessible user by taking the following steps:

1. Check whether the target storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Make a change to a repository accessible user.
   For details on how to make a change to a repository accessible user, see "Deleting a repository accessible user or changing a repository accessible user's password" in this manual.

9.5.10.8 Changing the logical node name

Change the logical node name of a storage management server transaction or storage server transaction by taking the following steps:

1. Check whether the target storage management server transaction or storage server transaction is operating.
   If the transaction is not operating, start the storage management server transaction or storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. For a storage management server transaction, check whether it also functions as a storage server transaction.
   When it also functions as a storage server transaction, go to Step 3.
   Otherwise, go to Step 4.

3. Delete the configuration of the storage server transaction.
   When using the backup management function, delete the transaction volume and backup volume. For details on how to delete a transaction volume/backup volume, see "Deleting a device" in this manual.
   When it is defined as an original or replica volume by using the replication control function, delete the original/replica volume setting. For details on how to delete an original/replica volume setting, see "Deleting an original/replica volume" in this manual.

4. Save the AdvancedCopy Manager data.
   For a storage management server transaction, save the following data:

   • Repository
     Make a backup of the repository.
     For details on how to make a backup of the repository, see "Making a backup of a database" in this manual.

   • Authentication management list
     On the node on which the storage management server transaction is running, make a backup of the authentication management list.
     For details on how to make a backup of an authentication management list, see "Making a backup of an authentication list."

   • Screen files
     Make a backup of the screen files.
     On the node on which the storage management server transaction is running, save the files under /opt/swstorage/java/data by the directory. Also save /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   In the storage server transaction or storage management server transaction that also functions as a storage server transaction, save the following data:

   • Preprocessing/postprocessing scripts
     Save the preprocessing and postprocessing scripts for backup management and replication control.

   For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:

   • Policy file for package backup of the management information
     For details on the policy file path, see "Preliminaries" in this manual.

5. For a storage server transaction (except a storage management server transaction that also functions as a storage server transaction), delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.

6. Delete the cluster environment of the target transaction.
   For details on how to delete a cluster environment, see "Deleting a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Detailed steps for deletion" in "Deletion on VERITAS Clister Server for Solaris" in the Operator's Guide for cluster environment.

7. Create the cluster environment of the target transaction.
   For details on how to create a cluster environment, see "Customizing a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • For the -n option of the cluster setup command, specify the name of the new logical node.

   • Do not perform the steps described in "Creating a storage management server transaction or storage server transaction environment" in "Detailed steps for customization" on creating a cluster environment (particularly Step 33 in "Details of the steps for customization" on PRIMECLUSTER for Solaris, Step 32 in "Details of the steps for customization" on VERITAS Cluster Server for Solaris).

8. Start the target transaction.
   For details on how to start it up, see the relevant cluster software manual.

9. Restore the AdvancedCopy Manager data.
   For a storage management server transaction, restore the following data:

   • Repository
     Restore the repository.
     For details on how to restore a repository, see "Restoring a database" in this manual.

   • Authentication management list
     On the node on which the storage management server transaction is running, restore the authentication management list.
     For details on how to restore an authentication management list, see "Restoring an authentication list" in this manual.

   • Screen files
     Restore the screen files.
     On the node on which the storage management server transaction is running, restore the files under /opt/swstorage/java/data by the directory. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   In the storage server transaction or storage management server transaction that also functions as a storage server transaction, restore the following data:

   • Preprocessing/postprocessing scripts
     Restore the preprocessing and postprocessing scripts for backup management and replication control.

   For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:

   • Policy file for package backup of the management information
     For details on the policy file path, see "Preliminaries" in this manual.

10. Change the server name.
    For a storage management server transaction, perform Step 3 and Step 4 in "Changing the server name of a storage management server transaction" in this manual.
    For a storage server transaction, perform Step 3 in "Changing the server name of a storage server transaction" in this manual.

11. To use the backup management or replication control function, rebuild the backup management or replication control environment, respectively.

12. For the package-backup-of-the-management-information execution server of AdvancedCopy Manager, execute the package-backup-of-the-management-information server registration/deletion command to register the package-backup-of-the-management-information execution server.

9.5.10.9 Changing the service name

Change the name of an AdvancedCopy Manager transaction by taking the following steps:

1. Check whether the target storage management server transaction or storage server transaction is operating.
   If the transaction is not operating, start the storage management server transaction or storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Save the AdvancedCopy Manager data.
   For a storage management server transaction, save the following data:

   • Repository
     Make a backup of the repository.
     For details on how to make a backup of the repository, see "Making a backup of a database" in this manual.

   • Authentication management list
     On the node on which the storage management server transaction is running, make a backup of the authentication management list.
     For details on how to make a backup of an authentication management list, see "Making a backup of an authentication list" in this manual.

   • Screen files
     Make a backup of the screen files.
     On the node on which the storage management server transaction is running, save the files under /opt/swstorage/java/data by the directory. Also save /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   Regardless of the type of transaction (storage management server transaction or storage server transaction), save the following data:

   • AdvancedCopy Manager management file
     On the node operating the transaction, save /etc/opt/swstorage/logical-node-name/swnode.ini.

   In the storage server transaction or storage management server transaction that also functions as a storage server transaction, save the following data:

   • Backup management list
     Make a backup of the backup management list.
     For details on how to make a backup of a backup management list, see "Making a backup of backup management list" in this manual.

   • Preprocessing/postprocessing scripts
     Save the preprocessing and postprocessing scripts for backup management and replication control.

   For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:

   • Policy file for package backup of the management information
     For details on the policy file path, see "Preliminaries" in this manual.

3. For a storage server transaction (except a storage management server transaction that also functions as a storage server transaction), delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.

4. Delete the cluster environment of the target transaction.
   For details on how to delete a cluster environment, see "Deleting a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Detailed steps for deletion" in "Deletion on VERITAS Cluster Server for Solaris" in the Operator's Guide for cluster environment.

5. On the cluster system, change the name of the userApplication.
   For details on how to change the name of a userApplication, see the relevant cluster software manual.

6. Create the cluster environment of the target transaction.
   For details on how to create a cluster environment, see "Customizing a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform the steps described in "Creating a storage management server transaction or storage server transaction environment" in "Detailed steps for customization" on creating a cluster environment (particularly Step 33 in "Details of the steps for customization" on PRIMECLUSTER for Solaris, Step 32 in "Details of the steps for customization" on VERITAS Cluster Server for Solaris).

   • Do not change any information other than the name of a transaction by using the cluster setup command.

7. Start the target transaction.
   For details on how to start it up, see the relevant cluster software manual.

8. Restore the AdvancedCopy Manager data.

   1. For a storage management server transaction, restore the following data:

      • Repository
        Restore the repository.
        For details on how to restore a repository, see "Restoring a database" in this manual.

      • Authentication management list
        On the node on which the storage management server transaction is running, restore the authentication management list.
        For details on how to restore an authentication management list, see "Restoring an authentication list" in this manual.

      • Screen files
        Restore the screen files.
        On the node on which the storage management server transaction is running, restore the files under /opt/swstorage/java/data by the directory. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   2. Regardless of the type of transaction (storage management server transaction or storage server transaction), restore the following data:

      • AdvancedCopy Manager management file
        On the node operating the transaction, restore /etc/opt/swstorage/logical-node-name/swnode.ini.

   3. In the storage server transaction or storage management server transaction that also functions as a storage server transaction, restore the following data:

      • Backup management list
        Restore the backup management list.
        For details on how to restore a backup management list, see "Restoring the backup management list" in this manual.

      • Preprocessing/postprocessing scripts
        Restore the preprocessing and postprocessing scripts for backup management and replication control.

      • When using the replication control function, restore the environment by using the resource adjustment command (swsrprecoverres).
        Specify the "-r" option for the resource adjustment command. For details on the resource adjustment command, see "Resource adjustment command (swsrprecoverres)" in this manual.

   4. For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:

      • Policy file for package backup of the management information
        For details on the policy file path, see "Preliminaries" in this manual.

9. For the package-backup-of-the-management-information execution server of AdvancedCopy Manager, execute the package-backup-of-the-management-information server registration/deletion command to register the package-backup-of-the-management-information execution server.

9.5.10.10 Changing a shared disk for shared data

Changing a shared disk for AdvancedCopy Manager shared data (e.g., name of a mount point of a physical disk or shared disk) by taking the following steps:

1. Check whether the target storage management server transaction or storage server transaction is operating.
   If the transaction is not operating, start the storage management server transaction or storage server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Save the AdvancedCopy Manager data.
   For a storage management server transaction, save the following data:

   • Repository
     Make a backup of the repository.
     For details on how to make a backup of the repository, see "Making a backup of a database" in this manual.

   • Authentication management list
     On the node on which the storage management server transaction is running, make a backup of the authentication management list.
     For details on how to make a backup of an authentication management list, see "Making a backup of an authentication list" in this manual.

   • Screen files
     Make a backup of the screen files.
     On the node on which the storage management server transaction is running, save the files under /opt/swstorage/java/data by the directory. Also save /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   Regardless of the type of transaction (storage management server transaction or storage server transaction), save the following data:

   • AdvancedCopy Manager management file
     On the node operating the transaction, save /etc/opt/swstorage/logical-node-name/swnode.ini.

   In the storage server transaction or storage management server transaction that also functions as a storage server transaction, save the following data:

   • Backup management list
     Make a backup of the backup management list.
     For details on how to make a backup of a backup management list, see "Making a backup of backup management list" in this manual.

   • Preprocessing/postprocessing scripts
     Save the preprocessing and postprocessing scripts for backup management and replication control.

   For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:

   • Policy file for package backup of the management information
     For details on the policy file path, see "Preliminaries" in this manual.

3. For a storage server transaction (except a storage management server transaction that also functions as a storage server transaction), delete /etc/opt/swstorage/logical-node-name/swnode.ini on the node operating the transaction.

4. Delete the cluster environment of the target transaction.
   For details on how to delete a cluster environment, see "Deleting a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Detailed steps for deletion" in "Deletion on VERITAS Cluster Server for Solaris" in the Operator's Guide for cluster environment.

5. Create the cluster environment of the target transaction.
   For details on how to create a cluster environment, see "Customizing a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • To change the name of a mount point, specify the new mount point name in the -m option of the cluster setup command.

   • To change a physical disk, specify the new physical disk when you mount it.

   • Change the configuration of a shared disk in the cluster system.

   • Do not perform the steps described in "Creating a storage management server transaction or storage server transaction environment" in "Detailed steps for customization" on creating a cluster environment (particularly Step 33 in "Details of the steps for customization" on PRIMECLUSTER for Solaris, Step 32 in "Details of the steps for customization" on VERITAS Cluster Server for Solaris).

6. Start the target transaction.
   For details on how to start it up, see the relevant cluster software manual.

7. Restore the AdvancedCopy Manager data.

   1. For a storage management server transaction, restore the following data:

      • Repository
        Restore the repository.
        For details on how to restore a repository, see "Restoring a database" in this manual.

      • Authentication management list
        On the node on which the storage management server transaction is running, restore the authentication management list.
        For details on how to restore an authentication management list, see "Restoring an authentication list" in this manual.

      • Screen files
        Restore the screen files.
        On the node on which the storage management server transaction is running, restore the files under /opt/swstorage/java/data by the directory. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   2. Regardless of the type of transaction (storage management server transaction or storage server transaction), restore the following data:

      • AdvancedCopy Manager management file
        On the node operating the transaction, restore /etc/opt/swstorage/logical-node-name/swnode.ini.

   3. In the storage server transaction or storage management server transaction that also functions as a storage server transaction, restore the following data:

      • Backup management list
        Restore the backup management list.
        For details on how to restore a backup management list, see "Restoring the backup management list" in this manual.

      • Preprocessing/postprocessing scripts
        Restore the preprocessing and postprocessing scripts for backup management and replication control.

      • When using the replication control function, restore the environment by using the resource adjustment command (swsrprecoverres).
        Specify the "-r" option for the resource adjustment command. For details on the resource adjustment command, see "Resource adjustment command (swsrprecoverres)" in this manual.

   4. For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:

      • Policy file for package backup of the management information
        For details on the policy file path, see "Preliminaries" in this manual.

8. For the package-backup-of-the-management-information execution server of AdvancedCopy Manager, execute the package-backup-of-the-management-information server registration/deletion command to register the package-backup-of-the-management-information execution server.

9.5.10.11 Changing the repository shared disk

Change the shared disk for the AdvancedCopy Manager repository by taking the following steps:

1. Check whether the target storage management server transaction is operating.
   If the transaction is not operating, start up the storage management server transaction.
   For details on how to start it up, see the relevant cluster software manual.

2. Save the AdvancedCopy Manager data.
   Save the following data:

   • Repository
     Make a backup of the repository.
     For details on how to make a backup of the repository, see "Making a backup of a database" in this manual.

   • Authentication management list
     On the node on which the storage management server transaction is running, make a backup of the authentication management list.
     For details on how to make a backup of an authentication management list, see "Making a backup of an authentication list" in this manual.

   • Screen files
     Make a backup of the screen files.
     On the node on which the storage management server transaction is running, save the files under /opt/swstorage/java/data by the directory. Also save /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

   • AdvancedCopy Manager management file
     On the node operating the transaction, save /etc/opt/swstorage/logical-node-name/swnode.ini.

   When the storage management server transaction also functions as a storage server transaction, save the following data:

   • Backup management list
     Make a backup of the backup management list.
     For details on how to make a backup of a backup management list, see "Making a backup of backup management list" in this manual.

   • Preprocessing/postprocessing scripts
     Save the preprocessing and postprocessing scripts for backup management and replication control.

   For the execution server of the package backup of the management information of AdvancedCopy Manager, save the following data:

   • Policy file for package backup of the management information
     For details on the policy file path, see "Preliminaries" in this manual.

3. Delete the cluster environment of the target transaction.
   For details on how to delete a cluster environment, see "Deleting a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" "Detailed steps for deletion" in "Deletion on VERITAS Cluster Server for Solaris" in the Operator's Guide for cluster environment.

4. Create the cluster environment of the target transaction.
   For details on how to create a cluster environment, see "Customizing a storage management server transaction or storage server transaction" in the Operator's Guide for cluster environment.

   

   • Do not perform the steps described in "Creating a storage management server transaction or storage server transaction environment" in "Detailed steps for customization" on creating a cluster environment (particularly Step 33 in "Details of the steps for customization" on PRIMECLUSTER for Solaris, Step 32 in "Details of the steps for customization" on VERITAS Cluster Server for Solaris).

5. Start the target transaction.
   For details on how to start it up, see the relevant cluster software manual.

6. Restore the AdvancedCopy Manager data.

   1. Restore the following data:

      • Repository
        Restore the repository.
        For details on how to restore a repository, see "Restoring a database" in this manual.

      • Authentication management list
        On the node on which the storage management server transaction is running, restore the authentication management list.
        For details on how to restore an authentication management list, see "Restoring an authentication list" in this manual.

      • Screen files
        Restore the screen files.
        On the node on which the storage management server transaction is running, restore the files under /opt/swstorage/java/data by the directory. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.

      • AdvancedCopy Manager management file
        On the node operating the transaction, restore /etc/opt/swstorage/logical-node-name/swnode.ini.

   2. When the storage management server transaction also functions as a storage server transaction, restore the following data:

      • Backup management list
        Restore the backup management list.
        For details on how to restore a backup management list, see "Restoring the backup management list" in this manual.

      • Preprocessing/postprocessing scripts
        Restore the preprocessing and postprocessing scripts for backup management and replication control.

      • When using the replication control function, restore the environment by using the resource adjustment command (swsrprecoverres).
        Specify the "-r" option for the resource adjustment command. For details on the resource adjustment command, see "Resource adjustment command (swsrprecoverres)" in this manual.

   3. For a package-backup-of-the-management-information execution server of AdvancedCopy Manager, restore the following data:

      • Policy file for package backup of the management information
        For details on the policy file path, see "Preliminaries" in this manual.

7. For the package-backup-of-the-management-information execution server of AdvancedCopy Manager, execute the package-backup-of-the-management-information server registration/deletion command to register the package-backup-of-the-management-information execution server.

Contents Index