| ETERNUS SF AdvancedCopy Manager Operator's Guide 13.0 -Solaris- |
|
Contents
Index
|
This chapter provides notes on the operations of AdvancedCopy Manager.
This chapter provides notes on backup and replication.
This chapter provides general notes on backup and replication.
The following devices must be backed up or replicated:
Device on which the system is stored
Device on which AdvancedCopy Manager has been installed
Device on which the resource files of AdvancedCopy Manager exists
Device whose volume has been entirely defined
|
Data in transaction volume |
Maintenance of data integrity |
Operation |
|---|---|---|
|
Oracle database space being used |
Linkage with Oracle is required. |
Use a sample script designed for linkage with Oracle. For details on sample scripts, refer to "Sample Scripts", in this manual. |
|
File system |
A AdvancedCopy Manager command unmounts the file system to maintain the integrity. |
See "Preprocessing and Postprocessing of Backup and Restoration", and "Preprocessing and Postprocessing of Replication". |
|
Other than the above |
The data integrity must be maintained in operations. |
Take appropriate action, such as stopping transactions during execution of backup or replication. |
Before starting the backup or replication operation, fetch device information managed by all the storage servers on the Web window of AdvancedCopy Manager. This time taken to complete this operation depends on the total number of devices defined on the selected storage servers. If many devices are involved, perform this operation while the CPU load or I/O load is low.
As a guide, about 0.5 seconds are required per device (partition) under a no-load condition.
Slices containing VTOC (cylinder 0) cannot be registered as transaction volumes or backup volumes.
This restriction does not apply if there are separate operations for each physical disk that makes up the VxVM disk group.
SynfinityFILE file systems consisting of multiple slices cannot be handled.
To back up or restore a SynfinityFILE file system consisting of multiple slices, handle the multiple slices simultaneously while the file system is unmounted.
Note the following points about backup, restoration, and replication of the SynfinityFILE/Global file system and Global File Services shared file system.
The target file system must be unmounted in advance.
Execute the operations on all partitions comprising the target file system.
The file system is unmounted as follows.
SynfinityFILE/Global file system: Stopping of services
Global File Services shared file system: Unmounting in all nodes
Before backup, restoration, or replication of a volume that can be mounted from multiple servers, cancel mounting from the other servers.
For disks that do not need to be mounted from other servers, prevent multiple servers from detecting or accessing the same logical disk by setting up appropriate hardware, such as devices in the ETERNUS storage system and Fibre Channel switches.
For a copy operation targeted at a file system, unmount the applicable volume to prevent data access and maintain the data integrity.
If backup/restoration and replication are performed without unmounting the volume, an error occurs, since a volume in use cannot be unmounted.
Note the following points about the processing in circumstances in which unmounting is enabled:
Another application is not using the volume. If another application is using it, suspend the application temporarily.
Users are not using the volume. If users are using it, prohibit them from using it temporarily.
Another volume is not mounted on the volume. If it is mounted, unmount it temporarily.
The volume is not shared with NFS sharing (for Solaris/HP-UX/Linux). If it is shared, stop sharing it temporarily.
Unmounting is required only during command execution. Operation can be resumed after command execution.
This chapter provides notes on the snapshot high-speed backup.
The snapshot high-speed backup requires as many backup volumes as the number of specified generations. Thus, the snapshot backup is disabled if:
All the specified number of generations have been backed up, and
No new volume exists which can be used as a backup volume.
Performing the snapshot high-speed backup continuously with the same transaction volume specified will perform the backup operation in parallel.
If you perform the snapshot high-speed backup continuously more often than the number of saved generations, the backup operations will be cancelled, starting from the oldest one. In other words, you cannot simultaneously perform the backup operation more often than the specified number of generations.
This chapter includes some notes on synchronous high-speed backup.
The backup command cannot be executed before the transaction and backup volumes have enter the equivalency holding state.
Backup policies can be set if the number of registered backup volumes is enough for snapshot-type high-speed backup operation, even if it is not enough for synchronous high-speed backup. In this event, high-speed backup may not be possible.
This chapter provides notes on restoration.
If data on a transaction volume has been rewritten since the latest backup data was collected to a backup volume, until restoration is performed the rewritten data is not guaranteed to be accurate.
Note the following points about backing up SDX objects.
A volume in a disk group to which the transaction volume belongs cannot be registered as a backup volume.
A volume in a single disk to which the transaction volume belongs cannot be registered as a backup volume.
A volume in a disk group to which an associated backup volume belongs cannot be registered as the transaction volume.
A volume in a single disk to which an associated backup volume belongs cannot be registered as the transaction volume.
In the following cases, backup synchronous processing of a GDS transaction volume cannot be started. In these cases, take appropriate action according to [System administrator's action] in the output message.
The volume structure of the transaction volume is changed.
The transaction volume is set as a proxy object.
A backup volume cannot be stopped.
The slices that make up the transaction volume include a temporarily separated slice or a slice being copied.
In the following cases, backup synchronous processing with EC cannot be started:
An SDX object that does not support the EC function is specified.
All available backup volumes are in a mirroring structure.
The transaction volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
In these cases, only software-copy with GDS is available. To use the software-copy function of GDS, specify the -Xgds-softcopy option.
If a backup volume satisfies any of the following conditions, it is not selected as the backup destination because it cannot be used as a proxy object of the transaction volume. Even if it is specified as the backup destination, it cannot be used.
The backup volume is not the same class as the transaction volume.
The slices that make up the backup volume include a temporarily separated slice or a slice that is being copied.
The backup volume is set as the master object associated with another proxy of GDS.
The backup volume is mounted.
The backup volume is a logical volume whose size is different to that of the transaction volume.
The backup volume is in a mirroring structure (excluding cases where -Xgds-softcopy or -Xgds-selectcopy is specified).
No disk is connected directly to the backup volume (excluding cases where -Xgds-softcopy or -Xgds-selectcopy is specified).
The backup volume enters the invalid data state (INVALID) if synchronous processing is cancelled at the following time during the backup of an SDX object:
When the synchronous processing is not in the equivalency maintain state or copy established state
Perform synchronous processing or snapshot processing again, and the volume enters the stop state (STOP), which automatically clears the data invalid state.
To restore the state using another method, refer to Section F.1.3, "Errors Related to Volume States," in the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating System)," and take appropriate action.
In the following cases, backup of a GDS transaction volume cannot be performed. In these cases, take appropriate action according to [System administrator's action] in the output message.
The volume structure of the transaction volume is changed.
The transaction volume is set as a proxy object.
A backup volume cannot be stopped.
The slices that make up the transaction volume include a temporarily separated slice or a slice being copied.
An SDX object that does not support the OPC function is specified.
All available backup volumes are in a mirroring structure.
The transaction volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
If a backup volume satisfies any of the following conditions, it is not selected as the backup destination because it cannot be used as a proxy object of the transaction volume. Even if it is specified as the backup destination, it cannot be used.
The backup volume is not the same class as the transaction volume.
The slices that make up the backup volume include a temporarily separated slice or a slice being copied.
The backup volume is set as the master object associated with another proxy of GDS.
The backup volume is mounted.
The backup volume is a logical volume whose size is different to that of the transaction volume.
The backup volume is in a mirroring structure.
No disk is connected directly to the backup volume.
In the following cases, backup with the output destination backup volume specified cannot be performed:
An ordinary volume is specified as the transaction volume and a GDS logical volume as the backup volume.
A GDS logical volume is specified as the transaction volume and an ordinary volume as the backup volume.
In the following cases, backup cannot be performed. In these cases, take appropriate action according to [System administrator's action] in the output message.
An SDX object does not satisfy the following conditions:
The state of the mirror volume is ACTIVE.
The state of the SDX disk is ENABLE.
The state of the mirror slice is ACTIVE or TEMP.
In the following case, the preprocessing and postprocessing scripts are not executed:
The state of the SDX object slice is TEMP.
In the following cases, a GDS transaction volume cannot be restored. In these cases, take appropriate action according to [System administrator's action] in the output message.
When restoring a transaction volume, the backup volume is not the proxy object of the transaction volume.
When restoring a transaction volume, the transaction volume cannot be stopped.
When restoring a transaction volume, the target backup volume cannot be stopped.
In the following cases, restoration with OPC cannot be performed for a GDS transaction volume.
A GDS logical volume that does not support the OPC function is specified.
The backup volume belongs to a mirror group connected to any subordinate group.
An SDX object is in the root class.
In these cases, only software-copy is available. To use the software-copy function of GDS, specify the -Xgds-softcopy option.
If the restore command (swstrestore) using the software-copy function of GDS is suspended, (such as for a forced termination), the started software-copy processing continues. In such cases, wait for the software-copy processing to finish, and then execute the resource match command (swstsrsemtch).
If the transaction volume is a slice of an SDX object and it is not a single volume, restoration using this command cannot be performed. This is because advanced copy cannot be performed on a mirror volume.
To restore the transaction volume of an SDX object, perform the following steps:
Confirm the backup volume by using the backup history list view/history information display command.
For restoration, use the dd command to copy data to the volume.
Note the following about the replication operation of SDX objects.
If any of the following is true, replication volume information for the replication operation of an SDX object cannot be set:
An SDX object and slice, or an SDX object and a volume of another OS are specified.
A logical volume and the n option are specified.
The original volume and replica volume belong to different classes.
The original volume and replica volume belong to the same group; alternatively, in operation of single volumes, they belong to the same single disk.
If the original volume and replica volume are bound, or if they are separated when a copy session exists, the replication volume information cannot be deleted.
If any of the following is true, the replication start command cannot be executed to replicate an SDX object:
The copy source volume and copy destination volume are in the master-proxy relationship when synchronous processing is started.
The copy source volume and copy destination volume have not been separated from their master-proxy relationship when synchronous processing is resumed.
The copy source volume and copy destination volume belong to different classes when synchronous processing is started.
The copy source volume and copy destination volume belong to the same disk group or single disk.
Any of the following is true for the copy source volume:
The volume contains any temporarily separated slice or slice that is being copied.
The copy source volume is a proxy object when synchronous processing is started.
Copy processing with another volume is in progress.
Any of the following is true for the copy destination volume:
The volume is in a mirroring structure and the Xgds-softcopy or Xgds-selectcopy option is not specified when synchronous processing is started. The volume cannot be stopped.
The volume is a master volume when synchronous processing is started.
The volume contains any temporarily separated slice or slice that is being copied.
The volume is a proxy of another master.
The hardware copy function is not available (excluding cases when -Xgds-softcopy or -Xgds-selectcopy is specified). The typical causes are:
EC/REC of the disk array unit is not properly set.
The copy source volume belongs to a mirror group connected to any subordinate group.
The copy destination volume is in a mirroring structure.
The volume is in the root class.
When replicating an SDX object registered with the replication function, do not use the sdxproxy command directly to change the state of the SDX object. The sdxproxy command may create an inconsistency between the management information of the replication function and the actual object state. In such cases, use the replication cancellation command (swsrpcancel) 4 to cancel the replication operation.
Note the following points for replicating an SDX object:
If the copy destination volume is an SDX object that is not a single volume, replication using this command cannot be performed. Therefore, if either the original volume or replica volume is an SDX object that is not a single volume, you can perform replication only from an SDX object to a non-SDX object.
To copy data to a volume that is an SDX object but not a single volume, use the dd command.
If any of the following is true, replication in the replication operation of an SDX object cannot be created:
The copy source volume and copy destination volume are in the master-proxy relationship in snapshot replication.
The copy source volume and copy destination volume belong to different classes in snapshot replication.
The copy source volume and copy destination volume belong to the same disk group or a single disk in snapshot replication.
Any of the following is true for the copy source volume:
The volume contains any temporarily separated slice or slice that is being copied, in snapshot replication.
The copy source volume is a proxy object in snapshot replication.
Copy processing with another volume is in progress.
Any of the following is true for the copy destination:
The volume is in a mirroring structure in snapshot replication.
The volume could not be stopped in snapshot replication.
The volume is a master volume in snapshot replication.
The volume contains any temporarily separated slice or slice that is being copied, in snapshot replication.
The volume is a proxy of another master in snapshot replication.
The OPC/ROPC function is not available for snapshot replication. The typical causes are:
OPC/ROPC of the disk array unit is not properly set.
EC/REC in the equivalency maintain state or suspended state is between the specified copy source volume and another proxy. However, advanced copy can be set in units of mirror slices. This means you can set advanced copy for as many copy destination volumes as the number of mirror slices at the same time. Therefore, this error occurs as the result of an attempt to set advanced copy for a greater number of copy source volumes than the number of mirror slices.
The copy source volume belongs to a mirror group connected only to subordinate groups but not directly to a disk. The copy source volume belongs to a mirror group connected to any subordinate group.
The copy destination volume is in a mirroring structure.
The volume is in the root class.
In the replication operation of an SDX object registered with the replication function, do not use the sdxproxy command directly to change the state of the SDX object. The sdxproxy command may create an inconsistency between the management information of the replication function and the actual object state. In such cases, use the replication cancellation command (swsrpcancel) to cancel the replication operation.
In the following cases, replication cannot performed:
The copy source volume is an SDX object for replication of an SDX object, and the SDX object is not in the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or TEMP.
The state of the SDX disk is ENABLE.
The copy source volume is an SDX object, and the SDX object is not in the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or STOP.
If the copy destination volume is an SDX object that is not a single volume for the replication operation for an SDX object, replication using this command cannot be performed. Therefore, if either the original volume or replica volume is an SDX object that is not a single volume, you can perform replication only from an SDX object to a non-SDX object.
To copy data to a volume that is an SDX object but not a single volume, use the dd command.
In the following cases, preprocessing of the copy source volume is not performed:
The state of the slice of the SDX object is TEMP.
If any of the following is true, replication of an SDX object cannot be cancelled:
The pair of the target replication volume used for replication cancellation is in the equivalency maintain state, and copy processing between the copy source volume and another volume is in progress.
The copy destination volume enters the invalid data state (INVALID)if replication is cancelled at either of the following times during replication of an SDX object:
When snapshot replication is neither in the equivalency maintain state nor copy established state
When data copy processing of snapshot processing is in progress
Perform synchronous processing or snapshot processing again, and the volume enters the stop state (STOP), which automatically clears the data invalid state.
To restore the state using another method, refer to Section F.1.3, "Errors Related to Volume Statuses," in the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating System)," and take appropriate action.
In the following cases, synchronous processing in the equivalency maintain state cannot be stopped:
The copy source volume is an SDX object, and the SDX object is in any of the following states:
The state of the mirror volume is either ACTIVE or STOP.
The state of the mirror slice is either ACTIVE or TEMP.
The state of the SDX disk is ENABLE.
If the mirror slice is in the TEMP state, preprocessing of the original volume is not performed.
The file system is mounted in an environment where the copy source volume or copy destination volume makes up a SynfinityFILE of a multi-volume structure. In such cases, unmount the file system, and process all of the volumes that make up the SynfinityFILE.
Note the following general points on cluster operation:
Do not make a SWSTGNODE registration that configures an environment variable to the entire system.
AdvancedCopy Manager does not monitor daemons composing a transaction. If the daemon of a transaction stops for some reason, AdvancedCopy Manager does not automatically restart it, so you must restart it manually. Moreover, the stopping of a transaction-oriented daemon of AdvancedCopy Manager does not cause the userApplication to fail over.
For details on the daemons composing AdvancedCopy Manager transactions and how to start these daemons, see "Starting and Stopping Daemons" in this manual.
For a storage server transaction (storage management server transaction) operating together with a transaction in scalable operation, note the following points that do not apply to regular operation or cluster operation:
For a storage management server transaction, note that the logical IP address you specify in the cluster setup command must be the logical IP address of the storage management server transaction. Specifying the physical or logical IP address of a transaction in scalable operation will result in an incorrect setting.
Do not register any userApplication resource of a transaction in scalable operation as a userApplication cluster resource of a storage server transaction (storage management server transaction).
In Step 2 of "Configuring the authentication-related file" in the ETERNUS SF AdvancedCopy Manager User's Guide, note that the IP address to be edited is the logical IP address of the storage management server transaction. Editing this address as a physical or logical IP address of a transaction in scalable operation will result in an incorrect setting.
On the [Add Server] dialog shown in "Registering a Server" in the ETERNUS SF AdvancedCopy Manager User's Guide, enter the logical IP of the storage server transaction in the IP address field. Entering a physical or logical IP address of a transaction in scalable operation will result in an incorrect setting.
On the [Add Server] dialog shown in "Registering a Server" in the ETERNUS SF AdvancedCopy Manager User's Guide, in the port number field enter the port number that was registered when the storage server transaction was customized and dedicated to the transaction-intended communication daemon (stgxfws_logical-node-name). Entering a different port number will result in an incorrect setting.
On the [Check Device Information] dialog shown in "Registering Device Information" in the ETERNUS SF AdvancedCopy Manager User's Guide, add a transaction volume and backup volume for the transaction in scalable operation to be placed in backup/replication operation
You can make a backup or replication on a node operating a storage server transaction (storage management server transaction). You cannot make a backup or replication on any standby node of a storage server transaction (storage management server transaction).
If a transaction (in scalable operation) running on a node operating a storage server transaction (storage management server transaction) stops for some reason, you must manually fail the storage server transaction (storage management server transaction) over to a node operating transactions in scalable operation. Storage server transactions (storage management server transactions) do not link with scalable operation, thus stopping scalable operation does not cause a storage server transaction (storage management server transaction) to fail over.
For backup operation in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a backup command, you must ensure consistency by using the resource adjustment command as a recovery measure.
You must perform backup operation on the active system of the cluster service (userApplication) because AdvancedCopy Manager is placed in the cluster service (userApplication) and operates as part of the cluster service (userApplication).
You cannot make a backup from a standby node or another cluster service (userApplication).
Note the following points if a file system has been created on a transaction volume and the file system has been registered as a cluster resource:
Change the backup preprocessing so that the transaction volume is not unmounted. Refer to "Preprocessing of backup" in this manual for information about changing backup preprocessing.
It is not possible to restore data using the restore execution command during transaction operations. To restore data on the volume, either copy the data using the dd command, or mount the backup volume and copy the necessary data. Alternatively, perform the procedure described in "Making a backup and restoration during stoppage of a cluster service".
If a file system has been created on a transaction volume, and the file system has been registered as a cluster resource, use the following procedure to back up and restore data.
Perform snapshot backups and restorations using the following procedure:
Switch the userApplication to Maintenance mode.
# hvutil -m on userApplication # |
Execute the backup or restoration.
# /opt/FJSVswsts/bin/swstbackup Device-Name Device-Name swstbackup completed # |
Turn Maintenance mode off for the userApplication.
# hvutil -m off userApplication # |
Execute synchronized backups using the following procedure.
Start synchronous processing.
# /opt/FJSVswsts/bin/swststartsync Device-Name Device-Name swststartsync completed # |
Check equivalency maintenance state.
Switch the userApplication to Maintenance mode.
# hvutil -m on userApplication # |
Execute the backup.
# /opt/FJSVswsts/bin/swstbackup Device-Name Device-Name swstbackup completed # |
Turn Maintenance mode off for the userApplication.
# hvutil -m off userApplication # |
For backup operation in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a backup command, you must ensure consistency by using the resource adjustment command as a recovery measure.
To use synchronous high-speed backup, do not register a backup to any cluster transaction.
You must perform backups on the active system of the service group because AdvancedCopy Manager is placed into the service group and operates as a part of it.
You cannot make a backup from a standby node or another service group.
To perform backup/restoration using AdvancedCopy Manager, you usually must unmount transaction volumes beforehand and mount the volumes later.
If the mount point of transaction volumes have been registered to a cluster transaction, set the mount point resource online or offline from the cluster transaction instead of mounting or unmounting the volumes. Alternatively, modify the backup/restoration preprocessing and postprocessing scripts so that the transaction volumes are set offline or online instead of being unmounted or mounted.
Moreover, the Volume is actually after doing offline/online of mount point resource and there will be a time difference by the time mount/unmount is done. Therefore, please add the processing (The Result of sleep and the df Command is observed) meets until mount/unmount is actually done after the location where the success or failure of offline/online is judged.
For details and examples on the preprocessing and postprocessing scripts, see "Backup/Restoration Preprocessing/Postprocessing" in this manual. For details on the commands used to set resources offline and online, see the relevant cluster system manual.
When a cluster service (userApplication) to which AdvancedCopy Manager belongs is operating, backup operation is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for backup operation, and backup is, therefore, disabled. Likewise, if the cluster service (userApplication) has been stopped, the environment is not ready and disables backup operation.
However, backup is temporarily enabled when the cluster service (userApplication) has been stopped.
When transactions in scalable operation are handled together, ensure that you only stop cluster services (userApplications) in scalable operation; do not stop cluster services (userApplications) for storage (management) server transactions.
Enabling backup operation disks (transaction volume and backup volume to operate) allows you to perform backups in the same way as for regular operations.
If a backup operation disk cannot be enabled, you cannot do backups while stopping a cluster service (userApplication) in scalable operation.
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), backup operation is disabled:
Shared disk for AdvancedCopy Manager shared data
Backup operation disk (transaction volume/backup volume to operate)
The following operations are not allowed in backup operation:
Backup/restoration through GUI
Manipulation for backup operation from a storage management server (host specification with the -h option)
Addition or deletion of a transaction volume/backup volume, or change in policy
To execute a display command for backup management to a storage management server transaction that also functions as a storage server transaction, you must specify options for the command. For details on the display command for backup management, see the "Commands for Backup Management" in this manual.
Perform backup operation during stoppage of a cluster service (userApplication) by performing the following steps:
Confirm that the cluster service (userApplication) has been stopped on both nodes.
For details on how to stop a cluster service (userApplication), see the SynfinityCLUSTER or PRIMECLUSTER manual.
Log in (for example, through Telnet) to the node on which you want to make a backup.
You cannot use the logical IP address. Use a node that is operable via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the transaction volume is a file system, mount it.
Be sure to enable the shared disk from either node. Do not enable the shared disk from both nodes.
Perform backup.
You can perform the backup in the same way as for regular operations in a cluster environment.
You can use the restore command to perform a restoration.
Release all the shared disks you enabled in Step 3.
Unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the cluster service (userApplication).
Start the cluster service (userApplication), if necessary.
For details on how to start a cluster service (userApplication), see the SynfinityCLUSTER or PRIMECLUSTER manual.
When a service group to which AdvancedCopy Manager belongs is operating, backup is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for backup operation, thus and backup is, therefore, disabled. Likewise, if the service group has been stopped, the environment is not ready and disables backup operation.
However, backup is temporarily enabled when the service group has been stopped.
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), backup is disabled:
Shared disk for AdvancedCopy Manager shared data
Backup operation disk (transaction volume/backup volume to operate)
The following operations are not allowed in backup:
Backup/restoration through GUI
Manipulation for backup operation from a storage management server (host specification with the -h option)
Addition or deletion of a transaction volume/backup volume, or change in policy
To execute a display command for backup management to a storage management server transaction that also functions as a storage server transaction, you must specify options for the command. For details on the display command for backup management, see "Commands for Backup Management" in this manual.
If the service group has been stopped, perform a backup by taking the following steps:
Confirm that the service group has been stopped on both nodes.
For details on how to stop a service group, see the VERITAS Cluster Server manual.
Log in (for example, using Telnet) to the node on which you want to make a backup.
You cannot use the logical IP address. Use a node that is operable via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the transaction volume is a file system, mount it.
Be sure to enable the shared disk from either node. Do not enable the shared disk from both nodes.
Perform the backup.
You can perform the backup in the same way as for regular operations in a cluster environment.
You can use the restore command to perform restoration.
Release all the shared disks you enabled in Step 3.
Unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the service group.
Start the service group, if necessary.
For details on how to start a service group, see the VERITAS Cluster Server manual.
For replication in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a replication command, you must ensure consistency by using the Resource adjustment command as a recovery measure.
You must perform replication operation on the active system of the cluster service (userApplication) because AdvancedCopy Manager is placed in the cluster service (userApplication) and operates as a part of it (userApplication).
You cannot perform replication from a standby node or another cluster service (userApplication).
Note the following points if a file system has been created on a copy source volume and the file system has been registered as a cluster system resource.
Change the preprocessing and postprocessing for replication so that the copy source volume is not unmounted.
Set up a RAW partition on the copy destination volume.
Data cannot be restored from the copy destination volume to the copy source volume using the replication creation command during transaction operations. To restore data on the volume, either copy the data using the dd command, or mount the copy destination volume and copy the necessary data. Alternatively, perform the procedure described in "Making a replication during stoppage of a cluster service".
Note the following points if a file system has been created on a copy source volume and the file system has been registered as a cluster system resource.
Set up a RAW partition on the copy destination volume.
Execute snapshot replications using the following procedure.
Switch the userApplication to Maintenance mode.
# hvutil -m on userApplication # |
Execute the replication.
# /opt/FJSVswsrp/bin/swsrpmake From-Volume-Name To-Volume-Name FROM=From-Volume-Name TO=To-Volume-Name swsrpmake completed # |
Turn Maintenance mode off for the userApplication.
# hvutil -m off userApplication # |
Execute synchronized replication using the following procedure.
Start synchronous processing.
# /opt/FJSVswsrp/bin/swsrpstartsync From-Volume-Name To-Volume-Name FROM=From-Volume-Name TO=To-Volume-Name swsrpstartsync completed # |
Check equivalency maintenance state.
Switch the userApplication to Maintenance mode.
# hvutil -m on userApplication # |
Execute the replication.
# /opt/FJSVswsrp/bin/swsrpmake From-Volume-Name To-Volume-Name FROM=From-Volume-Name TO=To-Volume-Name swsrpmake completed # |
Turn Maintenance mode off for the userApplication.
# hvutil -m off userApplication # |
For replication in a cluster system, note the following points that do not apply to regular operation:
If failover occurs while running a replication command, you must ensure consistency by using the resource adjustment command as a recovery measure.
When you use synchronous replication, do not register any destination volumes to a cluster transaction.
You must perform replication on the active system of the service groups because AdvancedCopy Manager is placed in the service groups and operates as a part ofit.
You cannot perform replication from a standby node or another service group.
To perform replication, you must unmount original/source volumes beforehand and mount the volumes later for some commands.
If the mount points of original/source volumes have been registered to a cluster transaction, set the mount point resources online or offline from the cluster transaction instead of mounting or unmounting the volumes. Alternatively, modify the unmount and mount processes in the replication preprocessing and postprocessing scripts to offline and online processes, respectively.
Moreover, the Volume is actually after doing offline/online of mount point resource and there will be a time difference by the time mount/unmount is done. Therefore, please add the processing (The Result of sleep and the df Command is observed) meets until mount/unmount is actually done after the location where the success or failure of offline/online is judged.
For details and examples on the types of commands that require the volumes to be unmounted and mounted, and the preprocessing and postprocessing scripts, see "Preprocessing and Postprocessing of Replication" in this manual. For details on the commands used to set resources online and offline, see the relevant cluster system manual.
When a cluster service (userApplication) to which AdvancedCopy Manager belongs is operating, replication is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for replication operation, and replication is, therefore, disabled. Likewise, if the cluster service (userApplication) has been stopped, the environment is not ready and disables replication operation.
However, replication is temporarily enabled when the cluster service (userApplication) has been stopped.
When transactions in scalable operation are handled together, ensure that you only stop cluster services (userApplications) in scalable operation; do not stop cluster services (userApplications) for storage (management) server transactions.
Enabling replication operation disks (source volume/destination volume to operate) allows you to perform replication in the same way as for regular operations.
If a replication operation disk cannot be enabled, you cannot perform replication while cluster services (userApplications) in scalable operation are stopped.
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), replication is disabled.
Shared disk for AdvancedCopy Manager shared data
Replication operation disks (source volume/destination volume to operate)
The following operations are not allowed in replication:
Manipulation for replication from a storage management server (host specification with the -h option)
Addition or deletion of an original/replica volume
Inter-server replication without the -m option specified
To execute a display command for replication management to a storage management server transaction that also functions as a storage server transaction, you must specify options for the command. For details on the display command for replication management, see "Commands for Replication Management" in this manual.
Perform replication during stoppage of a cluster service (userApplication) by taking the following steps:
Confirm that the cluster service (userApplication) has been stopped on both nodes.
For details on how to stop a cluster service (userApplication), see the SynfinityCLUSTER or PRIMECLUSTER manual.
Log in (for example, through Telnet) to the node on which you want to perform replication.
You cannot use the logical IP address. Use a node that is operable via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the original volume and replica volume have been mounted as file systems for operation, mount the volumes.
Be sure to enable the shared disk from either node. Do not enable the shared disk from both nodes.
Perform replication.
You can perform replication in the same way as for regular operations in a cluster environment.
You can also perform restoration from the replica volume to the original volume.
Release all the shared disks you enabled in Step 3.
Unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the cluster service (userApplication).
Start the cluster service (userApplication), if necessary.
For details on how to start a cluster service (userApplication), see the SynfinityCLUSTER or PRIMECLUSTER manual.
When a service group to which AdvancedCopy Manager belongs is operating, replication is enabled only on the active node. The standby node environment is not ready (to provide necessary resources) for replication, and replication is, therefore, disabled. Likewise, if the service group has been stopped, the environment is not ready and disables replication.
However, replication is temporarily enabled when the service group has been stopped.
If any of the following types of shared disks cannot be enabled (i.e., set online or mounted in a system), replication is disabled.
Shared disk for AdvancedCopy Manager shared data
Replication operation disks (source volume/destination volume to operate)
The following operations are not allowed in replication:
Manipulation for replication from a storage management server (host specification with the -h option)
Addition or deletion of an original/replica volume
Inter-server replication without the -m option specified
To execute a display command for replication management to a storage management server transaction that also functions as a storage server transaction, you must specify options for the command. For details on the display command for replication management, see "Commands for Replication Management" in this manual.
Perform replication during stoppage of the service group by taking the steps below.
Confirm that the service group has been stopped on both nodes.
For details on how to stop a service group, see the VERITAS Cluster Server manual.
Log in (for example, through Telnet) to the node on which you want to perform replication.
You cannot use the logical IP address. Use a node that is operable via the physical IP address.
Enable the shared disk.
Start (set online) the shared disk.
Mount the shared disk for AdvancedCopy Manager shared data.
When the original volume and replica volume have been mounted as file systems for operation, mount the volumes.
Be sure to enable the shared disk from either node. Do not enable the shared disk from both nodes.
Perform replication.
You can perform replication in the same way as for regular operations in a cluster environment.
You can also perform restoration from the replica volume to the original volume.
Release all the shared disks you enabled in Step 3.
Unmount the file systems you mounted.
Stop (set offline) the shared disk.
Start (set online) the service group.
Start the service group, if necessary.
For details on how to start a service group, see the VERITAS Cluster Server manual.
For notes on the Web screen environment, see "Setting up a client" in the ETERNUS SFAdvancedCopy Manager User's Guide.
|
Contents
Index
|