ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option 13.0 -Microsoft(R) Windows(R) 2000/Microsoft(R) Windows Sever(TM) 2003-, -Solaris-, -HP-UX-, -Linux-, -AIX-

Contents Index

Chapter 9 Operation Maintenance

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

9.1 Maintenance of Database

The Tape Backup of 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 9.1 Databases on Storage Management Server]

Type	When backup to be made	Backup method (reference)	Size
Database	A Storage Server has been added, the configuration information has changed as a result of loading of new device information or for some other reason, or the information about the backup management or replication management operation has changed.	Saving a database, or Making a package backup of databases	Refer to Saving a database.
Authentication management list	Authenticated data has been set.	Backing up an authentication management list, or Making a package backup of databases	Refer to Backing up an authentication management list.
Registry	DB setup has been performed on a Storage Management Server (a transaction on a Storage Management Server has been created in a cluster system) or the Storage Management Server information (server name, IP address, or port number) has changed.	Backing up a registry, or Making a package backup of databases	Refer to Backing up a registry.

[Table 9.2 Databases on Storage Server]

Type	When backup to be made	Backup method (reference)	Size
Registry	A Storage Server has been added or Storage Management Server information (server name, IP address, or port number) has changed.	Backing up a registry, or Making a package backup of databases	Refer to Backing up a registry.
Backup management list	A backup transaction has been completed.	Backing up a backup management list, or Making a package backup of databases	Refer to Backing up a backup management list.
Preprocessing and postprocessing scripts for backup management	A preprocessing or postprocessing script has changed.	Saving a database by using the copy command, or Making a package backup of databases	Check the size of the preprocessing and postprocessing script file for backup management.
Preprocessing and postprocessing scripts for tape copy	A preprocessing or postprocessing script has changed.	Saving a database by using the copy command, or Making a package backup of databases	Check the size of the preprocessing and postprocessing script file for tape copy.
Policy file for management information package backup	The policy file has changed.	Saving a database by using the copy command, or Making a package backup of databases	Check the size of the policy file for management information package backup.

[Table 9.3 Databases on Tape Server]

Type	When backup to be made	Backup method (reference)	Size
Registry	A Tape Server has been added or Storage Management Server information (server name, IP address, or port number) has changed.	Backing up a registry, or Making a package backup of databases	Refer to Backing up a registry.
Tape management information	After end of backup operation.	Tape management information backup command, or Making a package backup of databases	See the description about tape management information backup.

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 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, see "Resource backup command (swstresback)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.

+Backup data size of backup management list

For details, see "Maintenance of Database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.

9.1.1.1.2 Restoring a backup management list

A backup management list is restored.
For details, see "Resource restore command (swstresrest)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.

9.1.1.2 Maintaining a database

This describes maintaining a database used by a Storage Management Server.

9.1.1.2.1 Saving a database

Execute the database save command (stgdbdmp) to save a database space. Execute its command on the Storage Management Server.
For details, see "Saving a database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

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.

+Backup data size of database

Calculate the size with the following formula.
60 + (number of devices to be managed x 0.001) bytes

9.1.1.2.2 Finding an error in a database

Refer to 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" to determine the recovery mode.
For details of the pathname of RDBSWSTF.log file and the explanation of qdb messages, see "Finding an error in a database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

9.1.1.2.3 Recovering a database

Execute the database recovery command (stgdbrcv) for database recovery if an input-output error occurs in a database space. Execute its command on the Storage Management Server.
For details, see "Recovering a database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

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

After the database recovery command ends normally, acquire the latest save data using the "Saving a 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".

9.1.1.3 Maintaining authentication management list

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

9.1.1.3.1 Backing up an authentication management list

On the Storage Management Server, execute the /opt/FJSVswssc/bin/smmkbat command to extract authentication management information. The root user must execute this command.
For details, see "Backing up an authentication management list" in the "AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

+Backup data size of authentication management list

Calculate the size with the following formula.
400 + (length of the account name with an access permission assigned + 29 (*1) ...) bytes

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

9.1.1.3.2 Restoring an authentication management list

For details the restoring an authentication management list, see "Restoring an authentication management list" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

9.1.1.4 Maintaining a registry

This describes maintaining a registry. Perform this procedure on the Storage Management Server or the Storage Server.

9.1.1.4.1 Backing up a registry

Back up the registry file by executing the cp command.
For details, see "Backing up a registry" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server and Storage Server.

+Backup data size of registry

Check the size of the registry file to be backed up.
For details of the registry file to be backed up, see "Backing up a registry" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server and Storage Server.

9.1.1.4.2 Restoring a registry

Restore the registry file by executing the cp command.
For details, see "Restoring a registry" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server and Storage Server.

9.1.1.5 Maintaining a tape management information

This describes maintaining a tape management information. Perform this procedure on the Tape Server.

9.1.1.5.1 Backing up a tape management information

Back up the tape management information. Tape management information includes a TSM database. Execute the tape management information backup command after following the procedure explained below.
For details of the command, see "Tape management information backup command (tboresback)".

+Editing the TSM environment file to be backed up

To back up information on the environment files of the TSM database, back up the files specified in the backup target TSM environment file (/etc/opt/FJSVswstm/conf/tsmbkfile).
If the database location has been changed from the default, the file must be edited.
Edit the file as follows: By default, the following information is specified in the /etc/opt/FJSVswstm/conf/tsmbkfile file.
/opt/tivoli/tsm/server/bin/dsmserv.opt
/opt/tivoli/tsm/server/bin/dsmserv.dsk
/opt/tivoli/tsm/server/bin/nodelock
/opt/tivoli/tsm/server/bin/volhist.out
/opt/tivoli/tsm/server/bin/devconfig.out
/opt/tivoli/tsm/client/ba/bin/dsm.sys
/opt/tivoli/tsm/client/ba/bin/dsm.opt

If the database location has been changed, change the paths of the dsmserv.opt, dsmserv.dsk, and nodelock files.
If the contents of the following keys in the dsmserv.opt file have been modified, change the paths of the volhist.out and devconfig.out files. The contents of the keys are the paths specified in tsmbkfile.

Key name

File name

VOLUMEHistory

volhist.out

DEVCONFig

Devconfig.out

Key name	File name
VOLUMEHistory	volhist.out
DEVCONFig	Devconfig.out

+Backup data size of tape management information

Check the size under the following directory.
/etc/opt/FJSVswstm/data/ctrl

In cluster operation mode, check the size under the following directory.
/etc/opt/FJSVswstm/<logical node name>/data/ctrl

Check also the sizes below as the free space of the TSM database.
Size of the files specified in /etc/opt/FJSVswstm/conf/tsmbkfile
30% of size of the DB names specifled in /opt/tivoli/tsm/server/bin/dsmserv.dsk

9.1.1.5.2 Restoring a tape management information

Restore tape management information.
For details, see "Tape management information restore command (tboresrst)".

Because the tboresrst command overwrites the existing TSM database and log file, Fujitsu recommends saving these files in advance.
The procedure to save files is as follows.

Check the file names.

# cat /opt/tivoli/tsm/server/bin/dsmserv.dsk
/opt/tivoli/tsm/server/bin/log.dsm              <-  Log file
/opt/tivoli/tsm/server/bin/db.dsm               <-  Database
#

Copy the files to any directory.

# cp -p /opt/tivoli/tsm/server/bin/log.dsm /work/tsm_bkup
# cp -p /opt/tivoli/tsm/server/bin/db.dsm /work/tsm_bkup
#

9.1.2 Making a package backup of databases

AdvancedCopy Manager management information (including databases) can be backed up using one Storage Server, Storage Management Server, or Tape Server. This operation is referred to as a package backup of management information.
For details of the package backup method for management information, see "Making a package backup of databases" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the Server on which a package backup is made.

9.2 Troubleshooting

9.2.1 Troubleshooting for insufficient free space in a repository

For details, see "Troubleshooting for insufficient free space in a repository" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

9.2.2 Collecting maintenance information

9.2.2.1 Collecting information using a Web window

Collect information as follows:

Start the Java Plug-in control panel.
Start the Java Plug-in control panel as follows:
Select [Settings] - [Control Panel] - [Java Plug-in].
Make the startup setting of the Java console.
Start the Web window of AdvancedCopy Manager.
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

Login to the Storage Management Server, the Storage Server, and the Tape Server. Collect the following information. If one Server is also used as another type of Server, collect information on all Server types.

Type	Storage Management Server	Storage Server	Tape Server
System log	Must be collected.	Must be collected.	Must be collected.
Trace log	See "Collecting error survey information" in the " AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.	See "Collecting error survey information" in the " AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.	Acquire the files under the following directory: /var/opt/FJSVswstc/trc In addition, acquire the file when the following file exists: /tmp/f3cvtrc.log
Backup management list	Need not be collected.	See "Collecting error survey information" in the " AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.	Acquire the files under the following directory: /etc/opt/FJSVswstm /etc/opt/FJSVswstu/log (*1) /var/opt/FJSVswstm/adm In addition, acqire the execution results of TSM commands. For information on the commands to be executed, see "Collecting TSM survey information" below.
Common information	See "Collecting error survey information" in the " AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.	See "Collecting error survey information" in the " AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.	Acquire the files under the following directory: /var/opt/FJSVswstf (2) /etc/opt/swstorage (2)

*1: If the symptom is reproducible, follow the procedure below and collect information under /etc/opt/FJSVswstu/log.
The procedure to save files is as follows.

Change the trace log level to 2.

# /opt/FJSVswstm/bin/tbomodlog 2
#
Reproduce the symptom.
Change the trace log level back to 1.

# /opt/FJSVswstm/bin/tbomodlog 1
#

*2: In cluster operation mode, a backup management list and common information area allocated to a shared disk and a symbolic link is set. When collecting information, therefore, collect also information on the shared disk as shown below.

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

+Collecting TSM survey information

Collect the output results of the dsmadmc command. This command needs to be executed several times by changing arguments. For this reason, set the command name as an environment variable as shown below.

[In the case of csh]
# set DSMCOM="dsmadmc -id=<TSM user ID> -password=<TSM user password> -outfile=<information output directory>"[In the case of sh or ksh]
# DSMCOM="dsmadmc -id=<TSM user ID> -password=<TSM user password> -outfile=<information output directory>"

Execute the dsmadmc command. Use the shell variable that was set in step 1.

# $DSMCOM/query_status.txt query status
# $DSMCOM/query_library.txt query library F=D
# $DSMCOM/query_drive.txt query drive F=D
# $DSMCOM/query_path.txt query path F=D
# $DSMCOM/query_devclass.txt query devclass F=D
# $DSMCOM/query_stgpool.txt query stgpool F=D
# $DSMCOM/query_domain.txt query stgpool F=D
# $DSMCOM/query_policyset.txt query policyset F=D
# $DSMCOM/query_mgmtclass.txt query mgmtclass F=D
# $DSMCOM/query_copygroup.txt query copygroup F=D
# $DSMCOM/query_copygroup_archive.txt query copygroup type=archive F=D
# $DSMCOM/query_node.txt query_node F=D
# $DSMCOM/query_libvol.txt query libvol F=D
# $DSMCOM/query_db.txt query libvol F=D
# $DSMCOM/query_log.txt query log F=D
# $DSMCOM/query_admin.txt query admin F=D
# $DSMCOM/query_dbvol.txt query dbvol F=D
# $DSMCOM/query_vol.txt query vol F=D
# $DSMCOM/query_license.txt query license
# $DSMCOM/query_system.txt query system F=D
# $DSMCOM/query_process.txt query process
# $DSMCOM/query_session.txt query session
# $DSMCOM/query_request.txt query request
# $DSMCOM/query_mount.txt query mount
# $DSMCOM/query_filespace.txt query filespace F=D
# $DSMCOM/query_actlog2.txt query actlog BEGINDate=today-30
# $DSMCOM/query_session.txt query session
# $DSMCOM/query_process.txt query process
# $DSMCOM/show_txnt.txt show txnt
# $DSMCOM/show_dbtxnt.tx show dbtxnt
# $DSMCOM/show_locks.tx show locks
# $DSMCOM/show_dbv.txt show dbv
# $DSMCOM/show_csv.txt show csv
# $DSMCOM/show_deadlock.txt show deadlock
# $DSMCOM/show_sss.txt show sss

Collect the file under "information output directory" on the command line as survey information.

9.2.3 Troubleshooting for a failure in access to a repository database

For details of finding a cause for a failure in access to a repository database and what to do in such a case, see "Troubleshooting for a failure in access to a repository database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.

9.3 Troubleshooting for a Hardware Error, etc. occurring during backup

This section 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 (acmsyncstat) displays "failed" in the Status column.
The restoration execution status display command (swstreststat) displays "failed" in the Status column.
The history information display command (acmhistdisp) displays "failed" in the Status column.
The tracking status display command (acmtrkstat) 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 Advanced Copy 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 (acmsyncstat) displays "halt" in the Status column.
The restoration execution status display command (swstreststat) displays "halt" in the Status column.
The history information display command (acmhistdisp) 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 transaction volume, please perform the repair work of an obstacle according to the following procedures.

Cancel the processing in which the error occurred.
- If an error occurred during backup (OPC) physical copy: acmhistdel command
- If an error occurred during synchronous processing (EC): acmcancelsync command
- If an error occurred during restoration (OPC) physical copy: swstcancelrest command
- If an error occurred during tracking processing (QuickOPC): acmcanceltrk command
- Execute the execution status display commands (swstbackstat, acmsyncstat, swstreststat, acmtrkstat) and history information display command (acmhistdip) to verify that no other errors are found.
Remove the hardware error for the transaction volume.
Execute the Restoration execution command (acmrestore) 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.

Cancel the processing in which the error occurred.
- If an error occurred during backup (OPC) physical copy: acmhistdel command
- If an error occurred during synchronous processing (EC): acmcancelsync command
- If an error occurred during restoration (OPC) physical copy: swstcancelrest command
- If an error occurred during tracking processing (QuickOPC): acmcanceltrk command
- If the processing cannot be canceled by using the command, use GRmgr to cancel it.
Execute the resource match command (swstsrsemtch).
Cancel the processing in which the error occurred. At this point, the execution status display commands (swstbackstat, swstreststat) and history information display command (acmhistdisp) 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: acmhistdel command
- If an error occurred during restoration (OPC) physical copy: swstcancelrest command
Execute the execution status display commands (swstbackstat, acmsyncstat, swstreststat, acmtrkstat) and history information display command (acmhistdisp) to verify that no other errors are found.
Use the device information setting command (acmdevinfoset) to delete the backup volume in which the error occurred.
Use the device information setting command (acmdevinfoset) 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.
Reexecute the processing in which the error occurred.

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

Remove the hardware error.
The suspended copy processing is reexecuted.

9.3.2.4 Troubleshooting for a hardware error, etc. on a tape media

If a hardware error occurs on tape, follow the procedure below for troubleshooting.

Prevent the tape media, on which an error occurred, from being used for subsequent backup operations. To do so, use the TSM "update volume" command.
tsm> update volume <volume name> access=readonly
Check in an alternate tape. For details, see "Loading a Tape (CHECKIN)".
If expiration dates have been set, the backup histories for the data stored on the tape media in step 1 are deleted sequentially until they are all deleted. After all data is deleted from the tape, check out the tape. For details, see "Deleting a Tape from Storage Pool".

9.4 Changing the Operating Environment

9.4.1 Changing the IP address of 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 7. Otherwise, perform all steps.

It checks whether the Storage Management Server for change serves as the Storage Server. When serving and you define by the Storage Management 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" for the operating system of the target Storage Management Server.
On the Storage Management Server, change the system IP address.
On the Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.
On the Storage Management Server, restart the damons of AdvancedCopy Manager. For information on restarting daemons, see "Starting and Stopping Daemons".
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 "Settings of 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.

For information on changes in cluster operation, see "Changing the IP address of Storage Management Server transaction".

9.4.2 Changing the IP address of 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.

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" for the operating system of the target Storage Server.
On the Storage Server, stop daemons of AdvancedCopy Manager. For information on stopping daemons, see "Starting and Stopping Daemons".
On the Storage Server, change the system IP address.
On the Storage Server, restart the damons of AdvancedCopy Manager. For information on restarting daemons, see "Starting and Stopping Daemons".
On the Storage Management Server, change the IP address by using the server information change command. For details of the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server, execute the server information change report command to reflect the change of the IP address to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.

For information on changes in cluster operation, see "Changing the IP address of Storage Server transaction".

9.4.3 Changing the IP address of Tape Server

Change the IP address of a Tape Server as follows.

Follow the procedure below according to the Tape Server operating mode.
When the Tape Server is also operated as a Storage Management Server, see "Changing the IP address of Storage Management Server".
When the Tape Server is also operated as a Storage Server, see "Changing the IP address of Storage Server".
When the Tape Server is used only for its own intended use, the procedure is the same as that for the Storage Server. See "Changing the IP address of Storage Server".
Execute the Storage Server configuration information setting command on all Storage Servers that are associated with the relevant Tape Server to update the Tape Server association information. For details of the Storage Server configuration information setting command, see "Storage Server configuration information setting command (acmsvrset)".

9.4.4 Changing the port number of Storage Management Server

Change the port number of a Storage Management Server as follows.

It checks whether the Storage Management Server for change serves as the Storage Server. When serving and you define by the Storage Management 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" for the operating system of the target Storage Management Server.
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 environment, change the port number of the communication daemon (stgxfws_<logic node name>) of Storage Management Server transaction.
On the Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.
On the Storage Management Server, restart the damons of AdvancedCopy Manager. For information on restarting daemons, see "Starting and Stopping Daemons".

For information on changes in cluster operation, see "Changing the port number of Storage Management Server transaction".

9.4.5 Changing the port number of Storage Server

Change the port number of a Storage Server as follows.

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" for the operating system of the target Storage Server.
On the Storage Server, stop daemons of AdvancedCopy Manager. For information on stopping daemons, see "Starting and Stopping Daemons".
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 environment, change the port number of the communication daemon (stgxfws_<logic node name>) of Storage Server transaction.
On the Storage Server, restart the damons of AdvancedCopy Manager. For information on restarting daemons, see "Starting and Stopping Daemons".
On the Storage Management Server, change the port number by using the server information change command. For details of the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server, execute the server information change report command to reflect the change of the port number to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.

For information on changes in cluster operation, see "Changing the port number of Storage Server transaction".

9.4.6 Changing the port number of Tape Server

Change the port number of a Tape Server as follows.

Follow the procedure below according to the Tape Server operating mode.
When the Tape Server is also operated as a Storage Management Server, see "Changing the port number of Storage Management Server".
When the Tape Server is also operated as a Storage Server, see "Changing the port number of Storage Server".
When the Tape Server is used only for its own intended use, the procedure is the same as that for the Storage Server. See "Changing the port number of Storage Server".
Execute the Storage Server configuration information setting command on all Storage Servers that are associated with the relevant Tape Server to update the Tape Server association information. For details of the Storage Server configuration information setting command, see "Storage Server configuration information setting command (acmsvrset)".

9.4.7 Changing the server name of Storage Management Server

Change the server name of a Storage Management Server as follows.

Check whether the target Storage Management Server is also operated as a Storage Server. If it does, do as described in "Changing the server name of Storage Server". Then, please perform step 3 and 4.
On the Storage Management Server, change the server name by using the server information change command. For details of the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.

For information on changes in cluster operation, see "Changing the server name of Storage Management Server transaction".

9.4.8 Changing the server name of Storage Server

Change the server name of a Storage Management Server as follows.

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" for the operating system of the target Storage Server.
On the Storage Management Server, change the server name by using the server information change command. For details of the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server, execute the server information change report command to reflect the change of the server name to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.

For information on changes in cluster operation, see "Changing the server name of Storage Server transaction".

9.4.9 Changing the server name of Tape Server

Change the server name of a Tape Server as follows.

Follow the procedure below according to the Tape Server operating mode.
When the Tape Server is also operated as a Storage Management Server, see "Changing the server name of Storage Management Server".
When the Tape Server is also operated as a Storage Server, see "Changing the server name of Storage Server".
When the Tape Server is used only for its own intended use, the procedure is the same as that for the Storage Server. See "Changing the server name of Storage Server".
Execute the Storage Server configuration information setting command on all Storage Servers that are associated with the relevant Tape Server to update the Tape Server association information. For details of the Storage Server configuration information setting command, see "Storage Server configuration information setting command (acmsvrset)".

9.4.10 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)

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.

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".
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".
Change the device configuration.
Because the postchange device configuration needs to be reflected in the AdvancedCopy Manager data set, execute device information change processing for AdvancedCopy Manager. For details on changing the device information, see "Fetching device information on a Storage Server".
Set a deleted transaction volume or backup volume again in the backup operation. For details on adding the transaction volume or backup volume, see "Setting the operation type for a device".

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 "History information delete command (acmhistdel)" and "Backup synchronous processing cancel command (acmcancelsync)".

9.4.11 Changing the IP address for GUI connection of 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 the GUI connection timformation setting command.
For details on the GUI connection information setting command, see "GUI connection information setting command (stgguiipset)".

If the Storage Management Server is equipped with two or more network cards, the settings must be defined on the client side. For details how to set, see "Settings of authentication-related files" in the "ETERNUS SF AdvancedCopy Manager User's Guide" for the operating system of the target client.

9.4.12 Deleting the user who specified it as the repository access user, and changing the password

When a user is deleted on operating system 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 operating system, the information of a "repository access user" is re-set up using the repository access user change command.
For details on the repository access user change command, see "Repository access user change command (stguserset)".

For information on changes in cluster operation, see "Deleting the user who specified it as the repository access user, and changing the password".

9.4.13 Changing the operating environment of the cluster operating

This sub-section explains the changing the operating environment of the cluster operating.

9.4.13.1 Changing the IP address of Storage Management Server transaction

Change the IP address of a Storage Management Server transaction as follows.

Check the operation of Storage Management Server transaction.
When having stopped, Storage Management Server transaction is started.
For the starting method, refer to the cluster software manuals.
Check whether the Storage Management Server transaction is also operated a Storage Server transaction. When serving and you define 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" for the operating system of the target Storage Management Server.
Stop Storage Management Server transaction.
For the stopping method, refer to the cluster software manuals.
Change IP address resource.
For the method of changing IP address resource, refer to the cluster software manuals.
Check the operation of Storage Management Server transaction.
When having stopped, start Storage Management Server transaction.
For the starting method, refer to the cluster software manuals.
On the Storage Management Server transaction, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.
Restart Storage Management Server transaction.
For the method of a stop and starting, refer to the cluster software manuals.
Edit authentication-related file (swstorage.policy).
From the Web screen, change authentication-related file settings. For details, see "Settings of authentication-related files" in the "ETERNUS SF AdvancedCopy Manager User's Guide". Then, change the logical IP addresses of authentication-related files of all terminals that use the Web screen to new logical IP addresses.
If physical IP addresses are changed at the same time, then they must be also changed to new ones in the same file.
When using the replication operation, set the environment of replication operation again.

The IP address displayed by the cluster unsetup command is the address specified by the cluster setup command. It is not a value after IP address change.

9.4.13.2 Changing the IP address of Storage Server transaction

Change the IP address of a Storage Server transaction as follows.

Check the operation of Storage Server transaction.
When having stopped, Storage Server transaction is started.
For the starting method, refer to the cluster software manuals.
When you define 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" for the operating system of the target Storage Server.
Stop Storage Server transaction.
For the stopping method, refer to the cluster software manuals.
Change IP address resource.
For the method of changing IP address resource, refer to the cluster software manuals.
Check the operation of Storage Server transaction.
When having stopped, start Storage Server transaction.
For the starting method, refer to the cluster software manuals.
On the GUI of AdvancedCopy Manager, select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the IP address and select [OK] on the "Change of server" dialog.
Or, an IP address is changed by the server information change command on Storage Management Server. For the details on the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server transaction, execute the server information change report command to reflect the change of the server name to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.
When using the replication operation, set the environment of replication operation again.

9.4.13.3 Changing the port number of Storage Management Server transaction

Change the port number of a Storage Management Server transaction as follows.

Check the operation of Storage Management Server transaction.
When having stopped, Storage Management Server transaction is started.
For the starting method, refer to the cluster software manuals.
Check whether the Storage Management Server transaction is also operated a Storage Server transaction. When serving and you define 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" for the operating system of the target Storage Management Server.
Stop Storage Management Server transaction.
For the stopping method, refer to the cluster software manuals.
On primary node and secondary node, change the port number of the communications daemon for Storage Management Server transaction (stgxfws_<logical node name>) described at /etc/services.
Check the operation of Storage Management Server transaction.
When having stopped, start Storage Management Server transaction.
For the starting method, refer to the cluster software manuals.
On the Storage Management Server transaction, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.
Restart Storage Management Server transaction.
For the method of a stop and starting, refer to the cluster software manuals.
When using the replication operation, set the environment of replication operation again.

9.4.13.4 Changing the port number of Storage Server transaction

Change the port number of a Storage Server transaction as follows.

Check the operation of Storage Server transaction.
When having stopped, Storage Server transaction is started.
For the starting method, refer to the cluster software manuals.
When you define 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" for the operating system of the target Storage Server.
Stop Storage Server transaction.
For the stopping method, refer to the cluster software manuals.
On primary node and secondary node, change the port number of the communications daemon for Storage Server transaction (stgxfws_<logical node name>) described at /etc/services.
Check the operation of Storage Server transaction.
When having stopped, start Storage Server transaction.
For the starting method, refer to the cluster software manuals.
On the GUI of AdvancedCopy Manager, select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the port number and select [OK] on the "Change of server" dialog.
Or, a port number is changed by the server information change command on Storage Management Server. For the details on the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server transaction, execute the server information change report command to reflect the change of the server name to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.
When using the replication operation, set the environment of replication operation again.

9.4.13.5 Changing the server name of Storage Management Server transaction

Change the server name of a Storage Management Server transaction as follows. When you make a server name and a logical node name into the same name (when you also change a logical node name), see "Changing the logical node name".

Check the operation of Storage Management Server transaction.
When having stopped, start Storage Management Server transaction.
For the starting method, refer to the cluster software manuals.
Check whether the Storage Management Server transaction is also operated a Storage Server transaction. When serving and you define 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" for the operating system of the target Storage Management Server.
On the GUI of AdvancedCopy Manager, select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the server name and select [OK] on the "Change of server" dialog.
Or, the server name is changed by the server information change command on Storage Management Server. For the details on the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On all the Storage Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
On all the Tape Servers managed by the concerned Storage Management Server, execute the management server information change command. For details of the management server information change command, see "Management server information change command (stgcmmodnode)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Tape Server.
When using the backup operation, set the environment of backup operation.
When using the replication operation, set the environment of replication operation.

9.4.13.6 Changing the server name of Storage Server transaction

Change the server name of a Storage Server transaction as follows. When you make a server name and a logical node name into the same name (when you also change a logical node name), see "Changing the logical node name".

Check the operation of Storage Server transaction.
When having stopped, start Storage Server transaction.
For the starting method, refer to the cluster software manuals.
Delete the environment of Storage Server transaction.
When you define 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" for the operating system of the target Storage Server.
On the GUI of AdvancedCopy Manager, select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the server name and select [OK] on the "Change of server" dialog.
Or, the server name is changed by the server information change command on Storage Management Server. For the details on the server information change command, see "Server information change command (stgxfwcmmodsrv)" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server.
On the Tape Server that is associated with the relevant Storage Server transaction, execute the server information change report command to reflect the change of the server name to the Tape Server management information. For details of the server information change report command, see "Server information change report command (tbomodsrv)". The "Storage Server configuration information display command (acmsvrdisp)" can be used to check which Tape server is associated with the Storage Server.
When using the backup operation, set the environment of backup operation.
When using the replication operation, set the environment of replication operation.

9.4.13.7 Deleting the user who specified it as the repository access user, and changing the password

Change the repository access user as follows.

Check the operation of Storage Management Server transaction.
When having stopped, start Storage Management Server transaction.
For the starting method, refer to the cluster software manuals.
Change the repository access user. For the details how to change the repository access user, see "Deleting the user who specified it as the repository access user, and changing the password".

9.4.13.8 Changing the logical node name

For the details how to change the logical node name of Storage Management Server transaction or Storage Server transaction, see "Changing the logical node name" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the operating system of the target Servers.
However, change the description involving "Change server name." in the procedure explained there to the following.
For a Storage Management Server transaction, follow steps 3 to 5 in "Changing the server name of Storage Management Server transaction".
For a Storage server application, follow steps 3 and 4 in "Changing the server name of Storage Server transaction".

9.4.13.9 Changing the transaction name

For the details how to change the transaction name of Storage Management Server transaction or Storage Server transaction, see "Changing the service name" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the operating system of the target Servers.

Add the following to the data to be backed up and restored.

Preprocessing and postprocessing scripts
Preprocessing and postprocessing scripts for tape copying

9.4.13.10 Changing the shared disk for AdvancedCopy Manager shared data

For the details how to change the shared disk for AdvancedCopy Manager (the mount point name of the physical disk or the shared disk for shared data), see "Changing the shared disk for AdvancedCopy Manager shared data" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the operating system of the target Servers.

Add the following to the data to be backed up and restored.

Preprocessing and postprocessing scripts
Preprocessing and postprocessing scripts for tape copying

9.4.13.11 Changing the shared disk for AdvancedCopy Manager repository

For the details how to change the shared disk for AdvancedCopy Manager, see "Changing the shared disk for AdvancedCopy Manager repository" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment" for the operating system of the target Servers.

Add the following to the data to be backed up and restored.

Preprocessing and postprocessing scripts
Preprocessing and postprocessing scripts for tape copying

Contents Index