This section describes how to make a change to the operational configuration in cluster operation.
Change the IP address of a Storage Management Server transaction by taking the following steps:
Check if the target Storage Management Server transaction is also used for Storage Server transactions.
If it is also used for Storage Server transactions and replication management functions were used to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings. Refer to "8.6.2 Deleting a source volume or replica volume" for the method for deleting the copy source or copy destination volume settings.
Stop the Storage Management Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
Change the IP address resource.
For details on how to change an IP address resource, refer to the relevant cluster software manual.
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, refer to the relevant cluster software manual.
On the node on which the Storage Management Server transaction is running, create a server information change instruction file, then execute the server information change command with the -f option specified to change the IP address. Refer to "stgxfwcmmodsrv (Server information change command)" for details of the server information change command.
Restart the Storage Management Server transaction.
For details on how to stop and start it, refer to the relevant cluster software manual.
On the Storage Management Server transaction operating node, use the environment information display command to check that the IP address for GUI connections is correct. If required, use the GUI connection information setting command to change the IP address for GUI connections. Refer to "stgenvdisp (Environment information display command)" and "stgguiipset (GUI connection information setting command)" for details on these commands.
If the replication management functions are used, reconstruct the replication management environment (perform the "8.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Point
In the following cases, the IP address for GUI connection needs to be changed in Step 7:
If multiple network cards are mounted in the Storage Management Server, and the IP addresses used for communication with Storage Servers (IP addresses specified during database creation when the Storage Management Server was installed) are separate from the IP addresses specified for GUI client use
In other cases, if stgguiipset (GUI connection information setting command) is executed to explicitly set the IP addresses for GUI connection
Note
The IP address displayed by the cluster setup command that is executed to delete the cluster environment of the Storage Management Server transaction is not the IP address that has been newly specified, but is the IP address specified by the cluster setup command.
Change the IP address of a Storage Server transaction by performing the following steps:
If replication management functions were used to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings.
Refer to "8.6.2 Deleting a source volume or replica volume" for the method for deleting the copy source or copy destination volume settings.
Stop the Storage Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
Change the IP address resource.
For details on how to change an IP address resource, refer to the relevant cluster software manual.
Start the Storage Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
On the Storage Management Server that manages the Storage Server transactions, create a server information change instruction file, then execute the server information change command with the -f option specified to change the IP address. Refer to "stgxfwcmmodsrv (Server information change command)" relevant to the OS running the Storage Management Server for details of the server information change command.
If the replication management functions are used, reconstruct the replication management environment (perform the "8.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Change the port number of a Storage Management Server transaction or Storage Server transaction by performing the following steps:
If replication management functions were used by the target Storage Management Server or Storage Server to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings. Refer to "8.6.2 Deleting a source volume or replica volume" for the method for deleting the copy source or copy destination volume settings.
Stop the Storage Management Server transaction or Storage Server transaction.
For details on how to stop it, refer to the relevant cluster software manual.
On the primary node and secondary node of the target Storage Management Server transaction or Storage Server transaction, change the port number of the AdvancedCopy Manager communication daemon (stgxfws_logical-node-name) specified in /etc/services.
Start the targeted Storage Management Server transaction or Storage Server transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Create a server information change instruction file at the Storage Management Server transaction operating node if the change target is the Storage Management Server transaction. If the change target is a Storage Server transaction, create the file at the Storage Management Server that manages the Storage Server. Then, execute the server information change command with the -f option specified to change the port number. Refer to "stgxfwcmmodsrv (Server information change command)" for details on this command.
If the replication management functions are used, reconstruct the replication management environment (perform the "8.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Change the server name of a Storage Management Server transaction or Storage Server transaction by performing the steps below.
If replication management functions were used by the target Storage Management Server or Storage Server to define it as a copy source or copy destination volume, delete the copy source or copy destination volume settings.
Refer to "8.6.2 Deleting a source volume or replica volume" for the method for deleting the copy source or copy destination volume settings.
Create a server information change instruction file at the Storage Management Server transaction operating node if the change target is the Storage Management Server transaction. If the change target is a Storage Server transaction, create the file at the Storage Management Server that manages the Storage Server.
Execute the server information change command with the -f option specified (specify the created file) to change the server name. Refer to "stgxfwcmmodsrv (Server information change command)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" that is applicable to the operating system of the Storage Management server for details on this command.
If the replication management functions are used, reconstruct the replication management environment (perform the "8.4.5 Configuring the source volume and replica volume" task and subsequent tasks).
Make a change to a user's access to a repository by performing the following steps:
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, refer to the relevant cluster software manual.
Make a change to a repository accessible user.
For details about how to make a change to a repository accessible user, refer to "9.5.7 Change of password or deletion of the user who was specified as the repository access user" .
Change the logical node name of a Storage Management Server transaction or Storage Server transaction by performing the following steps:
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, refer to the relevant cluster software manual.
For a Storage Management Server transaction, check whether it also functions as a Storage Server transaction.
If this is the case, go to Step 3. Otherwise, go to Step 4.
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 do this, refer to "4.6.2 Deleting a device".
When it is defined as a source or replica volume by using the replication control function, delete the source/replica volume configuration. For details on how to perform this, refer to "8.6.2 Deleting a source volume or replica volume".
Save the data.
For a Storage Management Server transaction, save the following data:
Repository
Make a backup of the repository.
For details on how to do this, refer to "9.2.1.1 Database backup".
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 do this, refer to "9.1.1.4 Maintaining an authentication management 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 the directory /opt/swstorage/java/data. Also save /etc/opt/FJSVswssc/data/security/root.ini on both nodes.
The Storage Server transaction or a Storage Management Server transaction that also functions as a Storage Server transaction, save the following data:
Pre-processing/post-processing scripts
Save the pre-processing and post-processing 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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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.
Delete the cluster environment of the target transaction.
For details about how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Deletion on VERITAS Cluster Server for Solaris" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Create the cluster environment of the target transaction.
For details on how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
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" or Step 32 in "Details of the steps for customization" on VERITAS Cluster Server for Solaris).
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
For a Storage Management Server transaction, restore the following data:
Repository
Restore the repository.
For details on how to do this, refer to "9.2.1.2 Database restoration" .
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 do this, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Restore the screen files.
On the node on which the Storage Management Server transaction is running, restore the files under the directory /opt/swstorage/java/data. 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:
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing 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 about the policy file path, refer to "9.1.2.1 Preliminaries".
Change the server name.
Perform the procedure described in "9.5.8.4 Changing the server name of a Storage Management Server transaction or Storage Server transaction".
To use the backup management or replication control function, rebuild the backup management or replication control environment. (For backup management, perform the "Display backup management screen" task and subsequent tasks. For replication control, perform the "Setting copy source volume and copy destination volume" task and subsequent tasks.)
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 server.
Change the name of an AdvancedCopy Manager transaction by performing the following steps:
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 about how to start it up, refer to the relevant cluster software manual.
Save the AdvancedCopy Manager data.
For a Storage Management Server transaction, save the following data:
Repository
Create a backup of the repository.
For details on how to make a backup of the repository, refer to "9.2.1.1 Database backup".
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, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Create a backup of the screen files.
On the node on which the Storage Management Server transaction is running, save the files under the directory /opt/swstorage/java/data. 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 about how to do this, refer to "9.1.1.1.1 Backing up a backup management list".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing 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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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.
Delete the cluster environment of the target transaction.
For details on how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Deletion on VERITAS Cluster Server for Solaris" in the Operator's Guide for cluster environment.
On the cluster system, change the cluster service name (SafeCLUSTER/PRIMECLUSTER for Solaris) or the user service group name (VERITAS Cluster Server for Solaris).
For details on how to do this, refer to the relevant cluster software manual.
Create the cluster environment of the target transaction.
For details on how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
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 or 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.
Start the target transaction.
For details on how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
For a Storage Management Server transaction, restore the following data:
Repository
Restore the repository.
For details on how to do this, refer to "9.2.1.2 Database restoration".
Authentication management list
On the node on which the Storage Management Server transaction is running, restore the authentication management list.
For details about how to do this, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Restore the screen files.
On the node on which the Storage Management Server transaction is running, restore the files under the directory /opt/swstorage/java/data. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.
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.
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 about how to do this, refer to "9.1.1.1.2 Restoring a backup management list".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
When using the replication control function, restore the environment by using swsrprecoverres (Resource adjustment command).
Specify the "-r" option for the resource adjustment command. For details about this, refer to "swsrprecoverres (Resource adjustment command)".
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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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 server.
Change a shared disk that is used for AdvancedCopy Manager shared data (e.g., name of a mount point of a physical disk or shared disk) by performing the following steps:
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 about how to start it up, refer to the relevant cluster software manual.
Save the AdvancedCopy Manager data.
For a Storage Management Server transaction, save the following data:
Repository
Create a backup of the repository.
For details about how to do this, refer to "9.2.1.1 Database backup".
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 about how to do this, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Create a backup of the screen files.
On the node on which the Storage Management Server transaction is running, save the files under the directory /opt/swstorage/java/data. 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 about how to do this, refer to "9.1.1.1.1 Backing up a backup management list".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing 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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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.
Delete the cluster environment of the target transaction.
For details about how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Deletion on VERITAS Cluster Server for Solaris" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Create the cluster environment of the target transaction.
For details about how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
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" or Step 32 in "Details of the steps for customization" on "VERITAS Cluster Server for Solaris").
Start the target transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
For a Storage Management Server transaction, restore the following data:
Repository
Restore the repository.
For details about how to do this refer to "9.2.1.2 Database restoration".
Authentication management list
On the node on which the Storage Management Server transaction is running, restore the authentication management list.
For details about how to do this, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Restore the screen files.
On the node on which the Storage Management Server transaction is running, restore the files under the directory /opt/swstorage/java/data. Also restore /etc/opt/FJSVswssc/data/security/root.ini on both nodes.
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.
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 about how to restore do this, refer to "9.1.1.1.2 Restoring a backup management list".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
When using the replication control function, restore the environment by using swsrprecoverres (Resource adjustment command). Specify the "-r" option for the resource adjustment command.
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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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 server.
Change the shared disk for the AdvancedCopy Manager repository by g performing the following steps:
Check whether the target Storage Management Server transaction is operating.
If the transaction is not operating, start it up.
For details on how to do this, refer to the relevant cluster software manual.
Save the AdvancedCopy Manager data.
Save the following data:
Repository
Make a backup of the repository.
For details about how to do this, refer to "9.2.1.1 Database backup".
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 do this, refer to "9.1.1.4 Maintaining an authentication management 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 the directory /opt/swstorage/java/data. 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 about how to do this, refer to "9.1.1.1.1 Backing up a backup management list".
Pre-processing/post-processing scripts
Save the pre-processing and post-processing 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, refer to "9.1.2.1 Preliminaries".
Delete the cluster environment of the target transaction.
For details on how to do this, refer to "Deleting a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
Do not perform Step 1 (deleting the server) described in "Detailed steps for deletion" in "Deletion on PRIMECLUSTER for Solaris" or "Deletion on VERITAS Cluster Server for Solaris" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Create the cluster environment of the target transaction.
For details about how to do this, refer to "Customizing a Storage Management Server transaction or Storage Server transaction" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment".
Note
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" or Step 32 in "Details of the steps for customization" on "VERITAS Cluster Server for Solaris").
Start the target transaction.
For details about how to start it up, refer to the relevant cluster software manual.
Restore the AdvancedCopy Manager data.
Restore the following data:
Repository
Restore the repository.
For details about how to do this, refer to "9.2.1.2 Database restoration".
Authentication management list
On the node on which the Storage Management Server transaction is running, restore the authentication management list.
For details about how to do this, refer to "9.1.1.4 Maintaining an authentication management list".
Screen files
Restore the screen files.
On the node on which the Storage Management Server transaction is running, restore the files under the directory /opt/swstorage/java/data. 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.
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 about how to do this, refer to "9.1.1.1.2 Restoring a backup management list".
Pre-processing/post-processing scripts
Restore the pre-processing and post-processing scripts for backup management and replication control.
When using the replication control function, restore the environment by using swsrprecoverres (Resource adjustment command).
Specify the "-r" option for the resource adjustment command.
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 about the policy file path, refer to "9.1.2.1 Preliminaries".
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 server.
