| ETERNUS SF AdvancedCopy Manager Operator's Guide 13.0 -Solaris- |
|
Contents
Index
|
This chapter explains backup operations for normal transaction volumes of AdvancedCopy Manager.
This chapter describes the backup and restore functions of AdvancedCopy Manager.
AdvancedCopy Manager performs high-speed backup between volumes, regardless of the volume capacities, using the advanced copy function (OPC or EC function) of a disk array unit.
Backup that uses the One Point Copy (OPC) or Remote One Point Copy (ROPC) function of a ETERNUS storage system disk array unit is called snapshot fast backup. Backup that uses the Equivalent Copy (EC) or Remote Equivalent Copy (REC) function is called synchronized high-speed backup.
Automatic snap shot backup can be scheduled without first estimating the time required because it does not require backup synchronous processing. Note, however, that when the save number is 1, a state in which there is no backup data may occur, because a snap shot backup deletes the history prior to copy processing.
Because synchronized high-speed backup deletes the history after the completion of backup processing, there is no status in which backup data does not exist even though the generation number is 1. However, synchronized high-speed backup requires one more backup volume than snapshot fast backup. Synchronized high-speed backup also requires synchronized backup processing before the backup execution command is entered. Therefore, execution of automatic synchronized high-speed backup must be scheduled so that the time required for synchronized processing is estimated in advance. Synchronized backup processing is then started based on the estimated time, and the backup execution command is entered after equivalency maintain status has been achieved.
When backing up an Oracle database, it is combining with the sample script which AdvancedCopy Manager's offers, and on-line backup can be performed.
AdvancedCopy Manager automatically manages and selects a medium to be used for backup (a backup volume).
AdvancedCopy Manager also manages the backup carriers and generations and allows you to restore data from the latest or other past generations.
The OPC (One Point Copy) /ROPC (Remote One Point Copy) function of the disk array unit ETERNUS storage system is used to copy data from a transaction volume to an unused backup volume.
The snapshot fast backup performs processing as follows:
Execute the backup execution command ((1) in Figure 4.2). The following processing will be performed:
If backup volumes under generation management exist for all the generations, the oldest backup volume will be assumed as an unused backup volume.
An unused backup volume will be acquired from the unused backup volume management area.
Data on the transaction volume will be copied to the acquired unused backup volume ((2) to (4) in Figure 4.2).
Backup carrier information will be set.
The snapshot fast backup is completed as soon as you specify to execute backup. The actual data copying will be internally performed by the OPC function of the disk array unit ETERNUS storage system.
Using the QuickOPC function in the snapshot high-speed backup, physically copying only the difference data from the start of the previous backup can create a complete snapshot image, which can greatly reduce the time taken for physical copying.
For information on the QuickOPC function, see "Backup Operation by the QuickOPC Function."
If all generations of backup volumes are managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created.
Backup using ROPC/REC is limited to disk array devices within the same Storage Server that support ROPC/REC.
The Equivalent Copy (EC) or The Remote Equivalent Copy (REC) function of the ETERNUS storage system of disk array units is used to copy data from a transaction volume to an unused backup volume.
Synchronized high-speed backup performs processing as follows:
Execute the backup synchronized processing start command ((1) in Figure 4.3). An unused backup volume having the same capacity as the transaction volume is selected from the unused backup management area, and the synchronized backup processing starts.
The transaction and backup volumes are both placed in equivalence status. From this point on, equivalence between the transaction volume and backup volume is maintained. This status is referred to as equivalency maintain status ((3) in Figure 4.3).
Execute the backup execution command ((4) in Figure 4.3). The backup synchronization processing stops and the backup history information is set.
If the backup data exceeds the number of generations when backup has been completed, the oldest backup volume is treated as an unused backup volume.
The backup execution command cannot be executed before the transaction and backup volumes have become equivalent.
During synchronous high-speed backup using the Suspend/Resume function, the equivalency maintain status of EC can be set to Suspend or Resume. Consequently, the synchronous backup process can be made faster because the function can create a differential copy from the Suspend state.
For information on the Suspend/Resume function, see "Backup Operation That Uses the Suspend/Resume Function."
If all generations of backup volumes are managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created.
Backup using ROPC/REC is limited to disk array devices within the same Storage Server that support ROPC/REC.
This chapter describes restoring data on AdvancedCopy Manager.
The restoration operation refers to restoring data from a backup volume managed by the backup carrier information to a transaction volume.
The restoration operation from a backup volume refers to using the OPC function provided by the disk array unit to restore data from a backup volume to a transaction volume.
If the data on a backup volume under carrier management is restored to a transaction volume, the carrier management information will not change.
Note that data will be restored to a transaction volume that is the backup source. However, you can change the restoration destination.
If transaction volume contents are rewritten in the period between collection of the latest backup volume and a subsequent restore operation, rewritten data is not assured.
This chapter describes the backup operation on AdvancedCopy Manager.
Design a backup operation as follows:
Determine the server that will be used to perform backup.
The following servers can be used to perform backup:
Storage management server
Multiple storage servers are unified and operated centrally. The storage management server can also be used as a storage server.
Storage server
AdvancedCopy Manager operations are performed.
The locale of the internal code system (code system specified when installing AdvancedCopy Manager on the Storage management server) used by AdvancedCopy Manager must be installed on all Storage servers.
AdvancedCopy Manager backs up data in units of slices. A slice that stores work data is called a transaction volume. A transaction volume to be backed up must be placed on the disk array unit ETERNUS storage system.
For the supported units, refer to "Managing a Device on AdvancedCopy Manager".
For information on setting up a transaction volume, see "Setting the operation type for a device".
Slices must be allocated for transaction volumes in the following manner:
Create slices so that no VTOC is contained in them.
No slice may be duplicated on the same disk.
For backup targets, do not select slices in which a system is stored or AdvancedCopy Manager is installed.
For any slice that defines an entire volume, do not register it as a transaction volume.
No file system of SynfinityFILE consisting of multiple slices can be processed. When backing up or restoring a file system of SynfinityFILE consisting of multiple slices, handle the multiple slices at the same time while they are unmounted.
Refer to "General notes" of this manual as a point which it is careful of when deciding the candidate for backup.
Exclusion from Backup Targets or Replication Targets
Slice containing VTOC
To setup a backup policy on a transaction volume, set the following items:
The number of preservation generations refers to how many generations of backup data should be kept.
The snapshot fast backup first releases the oldest generation from the generation management. If a system failure or any other failure occurs while the backup is running, there may not be as many generations of backup data as required. In such a case, you are recommended to perform backup immediately again.
By snapshot type high-speed backup, when employing the number of preservation generations as 1, we recommend you also backup data to a tape.
A synchronous high-speed backup operation releases the oldest generation from generation management after backup of the latest generation is completed. Thus, backup volumes for (number of backup generations + 1) are necessary.
The interval days refers to an interval at which backup should be performed.
The delay of backup is displayed if more days than the specified number of interval days have passed after the last backup date.
Note that backup is not performed periodically even if you have specified the interval days.
For information on setting a backup policy, see "Setting a backup policy".
Prepare the backup volume.
The backup unit of AdvancedCopy Manager is a slice. In AdvancedCopy Manager, the slice in which the transaction data used as the candidate for backup is stored is called transaction volume. A backup volume must be placed on the disk array unit ETERNUS storage system.
The backup volume size must be equal the transaction volume size. The number of backup volumes used for snapshot-type high-speed buffer operations and that for synchronous high-speed buffer operations are listed below:
|
Backup |
Number of required backup volumes |
|---|---|
|
For snapshot fast backup |
Number of backup generations |
|
For synchronized high-speed backup |
Number of backup generations + 1 |
When backup policies have already been set for multiple transaction volumes, the registration of a backup policy for a newly registered transaction volume requires that the following number of backup volumes be registered beforehand:
|
Backup |
Number of required backup volumes |
|---|---|
|
For snapshot fast backup |
Total number of backup generations in the registered backup policies + number of generations in the new backup policy being set |
|
For synchronized high-speed backup |
Total number of backup generations in the registered backup policies + number of registered transaction volumes + number of generations in the new backup policy being set + 1 |
Slices must be allocated for backup volumes in the following manner:
Create slices so that no VTOC is contained in them.
No slice may be duplicated on the same disk. In a backup volume, there is no need to create a slice that indicates a whole volume, such as slice2.
For backup volumes, do not select disks in which a system is stored or AdvancedCopy Manager is installed.
For information on setting a backup volume, see "Setting the operation type for a device".
If the number of backup volumes that can be prepared in synchronized high-speed backup is only the number of preservation generations, the backup operation can be carried out by saving the backup volumes to secondary media, such as tapes.
In such cases, follow the procedure below.
Start backup synchronization.
Confirm the equivalency maintain status.
Execute backup.
Save the backup volumes to secondary media.
Delete history information.
Return to step 1.
If the history information is deleted, the restore execution command cannot be used for restoration of data of the period beginning from the time of deletion until the time of the next backup is completed. In this event, the data must be restored directly from the secondary media.
The backup operation of AdvancedCopy Manager can be automated using SystemWalker Operation Manager, etc.
Automatic snapshot fast backup can be executed in one of the following two ways.
Start the backup command in a job net of a batch job every time when a backup should be collected.
Start the backup command at the specified time.
For synchronized high-speed backup, the transaction and backup volumes must have maintained equivalency status at the scheduled time for backup.
For this reason, if synchronized high-speed backup is automated, the backup synchronous processing start command and the backup execution command must be started separately, as described below.
At first, theoretically calculate the time required for the synchronized backup processing. Execute the backup synchronous processing start command by specifying the time obtained by subtracting that theoretical time or more from the time that the backup execution command is to start. The transaction and backup volumes will then have maintained equivalency status when backup is executed.
The time between the start of synchronized backup processing and the transition to equivalency status being maintained depends on the capacity of the volume to be copied.
Use either of the following methods to automatically execute the backup execution command:
Start the backup execution command in a job net of a batch job at the same time at which the backup data is to be collected.
If there are other jobs (jobs A and B in the figure) to be executed before the backup execution command in the job net, the start time of the backup execution command cannot be determined. Assume that the start time of the backup execution command is the time obtained by adding the shortest time required for jobs A and B to the job net start time. Determine the start time of the backup synchronous processing start command by subtracting the estimated time from the start time of the backup execution command.
Start the backup execution command with the time specified.
The following shows the flow of backup operation on a regular transaction volume.
The following preparations are required before the backup operation is started.
Before the backup operation is started, the daemons of AdvancedCopy Manager must be started on the storage management server and the Storage servers. Normally, these daemons are automatically started up when the system is started. If the startup of a daemon fails for some reason or if a daemon has been stopped, you need to start the daemon on each server. For information on starting a daemon, see "Starting and Stopping a Daemons ".
When performing backup employment from a backup management screen, an access permission of each operation of a backup management screen is set up. For details of the Setting Method, see "Security Operation Using Authentication Feature".
When only a command performs backup employment, a setup of access permission is not required.
Specify the following URL to start the initial window of AdvancedCopy Manager. In cluster operation, URL is different. For details, please refer to "Initial Window," in the ETERNUS SF AdvancedCopy Manager User's Guide."
|
http://storage-management-server-address(:port-number)/swstorage/index.html |
The following GUI (server list view) will be started.
When applying only by the command, without using GUI, it is not necessary to perform this operation.
When the storage management server is in cluster operation
When the storage management server is in cluster operation, you must configure an authentication-related file (according to "Configuring the authentication-related file" in the ETERNUS SF AdvancedCopy Manager User's Guide) to use Web screens.
The Storage management server registers the Storage server to be managed. When the Storage server is operated as a Storage management server the server does not need to be added.
Select the [Operation] menu; select [Add Server]. The following window will be displayed.
For a storage server to be added, specify a server name, IP address, and port number required for communications. The port number is specified as the "communications service port number", when Agent of AdvancedCopy Manager was installed.
In cluster operation, specify the logical IP address of the Storage server as IP address. And specify the port number registered at the time of the cluster setup of Storage server transaction.
The [OK] button is pushed after inputting the above item, and additional processing of a Storage server is carried out.
In addition, this processing can be carried out also by the server information addition command (stgxfwcmaddsrv).
Before the backup management can be performed, device information on a storage server must be temporarily stored to the repository. To acquire information on a device on the storage manager server, the [Operation] menu, select [Refresh Server]. The following window will be displayed.
Check the server from which device information should be acquired and then press the [Yes] button.
After device information is acquired from each server, the following dialog will be displayed.
The new devices detected will be displayed in the uppermost list box. Move a device to be managed to the list box on the left. The second list box displays devices currently under management but not detected. Move a device that you no longer want to manage to the list box on the right. The lowermost list box displays devices whose device information has been updated (e.g., the mount point name has been changed).
After performing the above operations, press the OK button to reflect the configuration information.
In addition, this processing can be carried out also by the device information collection/reflection command (stgxfwcmsetdev).
The time required for this operation is proportional to the total number of devices defined on the Storage server. If the number of devices is large, perform this operation while the CPU load and I/O load are low.
As a guideline for reference, each operation takes about 0.5 s per device (partition) in a state without load.
On the server list view, select the [File] menu and then [Backup Management]. The server list view for the backup management will be displayed.
Set the environment for each storage server. From the server list view, select backup management in the tree displayed on the left side. Then, select the storage server in a list panel displayed on the right side of the window. Finally, select [Set Storage Server Configuration Information] from the [Operation] menu. The following setup window will be displayed.
If the target Storage server is Solaris or Linux and the Symfoware database exists in the Storage server, a recovery control file output place directory and a work directory are inputted. When a Symfoware database does not exist in a Storage server, or when a Storage server is HP-UX or AIX, this input item cannot serve as a half-tone display, and cannot be inputted.
After completing the input of necessary items, click the [OK] button.
You need to make this environment setting also on the storage management server if it serves also as a storage server. This step is not required if the environment setting has already been made on the storage servers.
You can also make this environment setting also using the storage server configuration information setting command.
For operation only with commands, the storage server configuration information setting command must be executed as part of startup operations.
Set up the following device operation type, before backing up in a storage server. The operation type is as follows:
Define the volume to be backed up as a transaction volume.
Prepare backup volumes. Prepare as many partitions, each of which has the same size as the transaction volume, as the number required for the backup type, and define them as the backup volumes:
|
Backup |
Number of required backup volumes |
|---|---|
|
Snapshot fast backup |
Number of backup generations |
|
Synchronized high-speed backup |
Number of backup generations + 1 |
Set an operation type on the server list view. On the server list view, select a storage server and select the [Operation] menu and then [Set Device Information]. The following setup window will be displayed.
A volume displayed in "Other volume" field has no specified device operation type. Set a device operation type as follows:
Setting as a "transaction volume"
After selecting a target volume, click the [<] button on the "Transaction volume" side. The target volume will be moved to the "Transaction volume" field.
Setting as a "backup volume"
After selecting a target volume, click the [<] button on the "Backup volume" side. The target volume will be moved to the "Backup volume" field.
After making settings for all the volumes, click the [OK] button.
You can make this setting also using the device information setting command (swstdevinfoset).
For any slice that defines an entire volume, do not register it as a transaction volume.
To change the configuration of a partition (slice) registered as the transaction volume or backup volume, take the following steps. First, delete the registered configuration, and then change the configuration. Next, try to fetch the device information on the storage server. Lastly, register the information by executing the device information setting command(swstdevinfoset).
Backup volume needs to be the same size as operating volume.
Backup is not supported for the system disk or the disk where AdvancedCopy Manager is installed.
The mounted device cannot be set to backup volume. (It is possible to set it to the transaction volume. )
You can check what has been registered as follows:
Checking on a GUI window
You can view information on a transaction volume on the transaction volume list view or information on a backup volume on the backup volume list view. For more information on each of these views, see the "ETERNUS SF AdvancedCopy Manager User's Guide".
Checking using a command
You can view information on a registered transaction volume or backup volume using the device usage status display command.
Set options when performing backup to a backup volume in a cabinet that is not the same as the cabinet containing the transaction volume.
Disk array devices must support the REC or ROPC function.
Both cabinets must be connected to an FCRA (FC Remote Adapter).
Since data flows only from the INIT side to TARG side through an FCRA connection, FCRA connections must be established in minimum sets of two.
In a backup operation involving a disk array device that does not support the ROPC function (and only the REC function can be used), backing up data to a backup volume in a cabinet containing no transaction volume is impossible since the backup operation uses the ROPC function during restoration.
Create the following files to set options:
|
For normal operation (non-cluster) /etc/opt/FJSVswsts/data/DEFAULT/check.ini For cluster operation /etc/opt/FJSVswsts/logical-node-name(*1)/data/DEFAULT/check.ini |
(*1) Logical node name of AdvancedCopy Manager specified during setting up of a cluster.
Code as follows:
|
[check] RemoteCopy=Yes |
If the option settings file is changed after operation starts, backup may not be able to continue. For this reason, do not change the option settings file after the start of operation.
To change the option settings file, you must set the backup policy again.
For a transaction volume registered on a storage server, set the following backup policy:
Number of preservation generations
Means how many generations of backup data should be kept.
Interval days
Means the number of days before next backup should be performed. If the specified number of days is exceeded, you will be prompted to perform backup on the GUI window of AdvancedCopy Manager.
Specify the backup policy settings from the Transaction Volume List view. Select "Transaction Volume" of the storage server from the tree to display the transaction volume list. After selecting a transaction volume for which you want to set a backup policy, click the right mouse button. From the popup menu, select [Set Backup Policy]. The following setup window will be displayed.
On this window, specify the number of interval days and the number of preservation generations and click the [OK] button. Perform this procedure on all the transaction volumes. You can set a backup policy also using the backup policy setting command (swstbkpolset).
Even if the number of interval days has been specified, AdvancedCopy Manager does not automatically collect backup. This value is used only to prompt the user to perform backup when the number of backup interval days is exceeded.
When you set a backup policy, there must be as many registered backup volumes as required to perform backup according to the specified backup policy. For information on the necessary number of backup volumes, see "Preparing a backup volume".
Even though the number of backup volumes required for the backup may not have been registered beforehand when backup policies for synchronized high-speed backup were set, the number required can be set if the number of backup volumes that are required for snapshot fast backup have been registered. However, synchronized high-speed backup may not be able to be executed.
You can check what has been defined as follows:
Checking on a GUI window
You can view information on a backup policy on the transaction volume list view. For more information on the view, see the "ETERNUS SF AdvancedCopy Manager User's Guide".
Checking using a command
You can view information on a defined backup policy using the backup policy display command (swstbkpoldisp).
In AdvancedCopy Manager, backup or restore processing must be performed while transaction volumes are unmounted. Therefore, when backup or restore is executed, mount and unmount processing of the transaction volume is done by using the preprocessing and postprocessing script.
The backup or restore processing is not executed when the transaction volume can not be unmounted.
For details of the preprocessing and postprocessing script , refer to "Preprocessing and Postprocessing of Backup and Restoration."
In the case of one of the two operations explained below, the backup preprocessing and postprocessing scripts need to be customized.
When, because of an operational reason, you want to avoid unmount/mount processing for a transaction volume where a file system is constructed
When you want to add special preprocessing and postprocessing to the preprocessing and postprocessing scripts
Refer to "Preprocessing and Postprocessing of Backup and Restoration," for details on the customization.
When AdvancedCopy Manager is upgraded
The script after upgrade may be updated.
Therefore, customize the script after upgrade rather than reusing the script which was being used by the previous version.
In the backup operation on AdvancedCopy Manager, a backup volume with the same capacity as a transaction volume is automatically selected from the registered backup volumes.
If the backup volume is recognized in a "Device map file", i.e., a file defining the correspondence between transaction and backup volumes, it must be created.
Create a device map file anywhere on the storage server that performs backup. If you specify this file while performing backup, an operation in recognition of the backup destination is enabled.
To manage multiple generations, multiple device map files must be prepared.
Moreover, the device map file which can be used when backing up or starting synchronous processing should meet either of the following requirements.
An unused backup volume is specified.
The backup volume used in the history deleted by this backup is specified.
Therefore, it is necessary to use the device map file properly according to the situation of the backup volume at operation which uses two or more backup volumes.
If the number of backup volumes that can be prepared in synchronized high-speed backup is only the number of preservation generations, the backup operation can be carried out by saving the backup volumes to secondary media, such as tapes, and then deleting history information.
In such cases, the device map file that is subsequently specified at the start of backup synchronous processing is the device map file specifying the backup volumes that become unused because of the last deletion of history information.
The following shows a description example of a device map file.
The following lists rules for creating a device map file.
Describe a transaction volume and a corresponding target backup volume in one line. Separate a transaction volume and a backup volume with one or more "half-size blank or tab characters". One or more "half-size blank or tab characters" may be included between the beginning of a line and a transaction volume name or between the end of a backup volume name and the end of a line (newline character).
A blank line ("half-size blank or tab characters") may be included in a file.
The portion from the symbol "#" to the end of a line is assumed as a comment.
You cannot specify more than one target backup volumes for one work disk in one device map file. In such a case, the information in the line first found will be valid. While a device map file is read, the system will not detect such a redundant line.
A device map file may include descriptions of transaction volumes other than the processing target. (See the description example provided in the beginning of this chapter.)
This chapter describes the backup operation on AdvancedCopy Manager.
Before performing the backup operation, make environment settings required for the backup operation according to "Preparations".
AdvancedCopy Manager has two kinds of backup operation as follows.
Snapshot fast backup operations
Synchronous high-speed backup operations
Perform the snapshot fast backup as follows:
Before backing up a general file system, stop work.
Display the transaction volume list view and select a volume to be backed up.
From the [Operation] menu, select [Backup] to display the following window.
Check the displayed server names and transaction volume names and perform the following:
To use a volume automatically selected by AdvancedCopy Manager a backup volume:
Click the [OK] button.
To use a specific volume as a backup volume:
Specify a device map file created on the storage server that performs backup (e.g., /home/usr1/devmap1) and then click the [OK] button.
After the backup is completed, the following window will be displayed. Click the [OK] button and you will be sent back to the transaction volume list view.
This completes backup. Now you can restart work. At this point, however, the physical copying of a volume is not completed at the back end. To check the status of physical copying, do as follows:
Display the transaction volume list view and check the [Status] field of a target transaction volume. You can check the current copying status because this field displays the progress status of copying processing.
To check the latest copying status, either:
Click the [PF5] key, or
Select [Refresh] from the View menu.
If you have stopped work in Step 1, restart the work.
You can perform backup also using the backup execution command.
You can check the backup status also using the backup execution status display command.
When the QuickOPC function is used for snapshot high-speed backup, the operations listed below cannot be performed from the Transaction Volume List view. Enter the appropriate command for each operation.
Execute the backup command with -T specified (swstbackup).
Execute the tracking cancel command (swstcanceltrk).
Perform the synchronized high-speed backup for a transaction volume as follows:
Display the transaction volume list view and select a volume to be backed up.
On the [Operation] menu, select [Start Synchronization processing] to display the following window.
Check the displayed server name and transaction volume name, and perform one of the following operations:
To use a volume automatically selected by AdvancedCopy Manager as a backup volume:
Click the [OK] button.
To use a specific volume as a backup volume:
Specify a device map file name created on the storage server (e.g., /home/usr1/devmap1) for which backup will be performed and then click the [OK] button.
When the synchronized backup processing is completed, the window shown below appears. Click the [OK] button to return to the transaction volume list view.
Physical copying from the transaction volume to backup volume now starts. To check the status of the physical copying, do the following:
Display the transaction volume list view and check the [Status] field of the target transaction volume. This field displays the progress of the coping processing. Use it to check the current status of the copying.
To check the latest copying status, perform one of the following operations:
Click the [PF5] key.
Select [Refresh] from the View menu.
The transaction and backup volumes have obtained equivalency status when the [Status] field indicates [Backup Preparation Completed].
To create a backup history, select the target transaction volume from the transaction volume list view and select [Backup] from the [Operation] menu. The following window appears.
Check the displayed server name and transaction volume name, and click the [OK] button.
When the backup is completed, the window shown below appears. Click the [OK] button to return to the transaction volume list view.
The backup execution command causes an error if it is executed before the transaction and backup volumes have entered equivalence status.
The device map cannot be specified during backup.
Backup synchronous processing is started with Backup synchronous processing start command.
A backup synchronous processing state is checked with Backup synchronous processing progress display command.
Backup can also be executed with the backup execution command.
The backup status can also be checked with the backup execution status display command.
When the Suspend/Resume function is used for synchronous high-speed backup, the operations listed below cannot be performed from the Transaction Volume List view. Enter the appropriate command for each operation.
Execute the backup command with -suspend specified (swstbackup).
If one transaction volume has multiple synchronous processing (EC sessions), then specify the backup volume and cancel only the specified EC session (swstcancelsync).
This chapter describes restoring a volume or data that has been backed up.
Restore all the data in a volume, which has been backed up in the snapshot fast backup as follows:
Stop work if you want to perform restoration on a general file system.
Display the transaction volume list view. Select a volume to be restored.
From the [Operation] menu, select [Restore] to display the following window. Restoration is carried out from the backup volume managed for the newest generation's backup history.
Check the name of volume to restore.
As the name of volume to restore, a transaction volume name selected in the transaction volume list view will be displayed. Click the [OK] button to restore data to this transaction volume. To change the restore destination, mark the Name of volume to restore checkbox, and then click the [...] button. The following window will be displayed.
Select a volume to which you want to restore data and then click the [OK] button. You will be sent back to the restore window.
Check that the name of volume to restore is correct and then click the [OK] button on the [Restore Window].
The following window will appear when the restoration is completed. Click the [OK] button and you will be sent back to the transaction volume list view.
This completes restoration. Now you can restart the work. At this point, however, the physical copying of a volume is not completed at the back end. To check the status of physical copying, do as follows:
Display the transaction volume list view and check the [Status] field of a target transaction volume. You can check the current restoration (physical copying) status because this field displays the progress status of copying processing.
To check the latest information, either:
Click the [PF5] key, or
Select [Refresh] from the View menu.
If the transaction was stopped in 1, restart it.
You can perform restoration also using the restore execution command.
You can check the restore status also using the restore execution status display command (swstreststat).
See the ETERNUS SF AdvancedCopy Manager User's Guide for restoration in which absolute generations and relative generations are indicated in the backup data that is subject to history management. (For absolute generations, 1 is assigned to the data backed up first and the number increases sequentially. For relative generations, 1 is assigned to the latest data, and the number increases as the data becomes older.)
Restore an individual file as shown below. Note that you cannot restore an individual file on the GUI window.
Mount backup volume. To check backup volume by the history list view or executing history information display command.
Copy files to restore by the cp command.
Unmount backup volume.
Display backup history information to check backup volume names, backup date, etc. of backup data under generation management for a transaction volume.
Backup history information is used to manage only information stored on a backup volume.
Any backup history information exceeding the number of preservation generations defined in a backup policy will be automatically deleted.
You can display a backup history on the backup history list view. To display the backup history list view, first access the server list view, display a storage server in a tree view, and select a transaction volume on the storage server.
You can display a backup history also using the history information display command.
Delete a backup history on the server list view. If you display a storage server in a tree view on the server list view, a list of transaction volumes on this storage server will be displayed. After selecting a transaction volume history for which you want to delete a backup history, click the right mouse button and, from the popup menu, select [Delete History]. The following setup window will be displayed.
Carefully check the displayed server name and transaction volume name and click the [OK] button.
You can delete a backup history also using the history information delete command.
You need to change the setting information of AdvancedCopy Manager if any change is made on a storage server or device used in the backup operation. This chapter describes changing the setting information when various changes are made.
After a device is added to any storage server, incorporate it in the backup operation of AdvancedCopy Manager as follows:
Display the initial window. For more information, see "Starting the initial window".
Fetch all the device information for a storage server. When device information is fetched, a newly added device will be detected. Move it to the [Device to be added] field. For information on fetching device information, see "Fetching device information on a storage server".
Display the backup management window. For more information, see "Displaying the backup management window".
Set the operation type for a device that has been added. For more information, see "Setting the operation type for a device".
If the added device has been defined as a transaction volume, set a backup policy for it. For more information, see "Setting backup policies".
This chapter describes deleting a device depending on the device type.
To delete a transaction volume, follow the steps shown below. Please be sure to do this work before removing the operating volume for deletion.
Display the backup management window. For more information, see "Displaying the backup management window".
Delete a backup history for the transaction volume to be deleted. For more information, see "Deleting a backup history".
Delete a backup policy for the transaction volume to be deleted.
If you display a storage server in a tree view, a list of transaction volumes on this storage server will be displayed. After selecting the transaction volume for which you want to delete, select delete backup policy. You can click the right mouse button or from the popup menu, select [Delete backup policy]. The following setup window will be displayed.
Carefully check the displayed server name and transaction volume name and click the [OK] button.
Delete device information for a transaction volume to be deleted.
After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed.
Move a target transaction volume displayed in the "Transaction Volume" field to the "Other Volume" field. Click the [>] button to move a transaction volume.
You can execute this processing also using the history information delete command, backup policy deletion command, or device information setting command.
To delete a backup volume follow the steps as shown below. Please be sure to do this work before removing the operating volume for deletion.
Display the backup management window. For more information, see "Displaying the backup management window".
Send the backup volume to be deleted into the unused status.
When a volume is unused, this volume does not exist in a backup history. If the volume exists in a backup history, delete the backup history. If the volume is already unused, skip to the next step.
Delete device information for the backup volume to be deleted.
After selecting a storage server, select [Set Device Information] from the [Operation] menu. Then, the following setup window will be displayed.
Move a target backup volume displayed in the "Backup Volume" field to the "Other Volume" field. Click the [>] button to move a backup volume.
If a backup volume is deleted, an already defined backup policy may no longer be met (e.g., the number of backup volumes is less than the number of preservation generations). In such a case, the backup operation can no longer be continued. To avoid such a status, be sure to check already defined backup policies before deleting a backup volume.
If only an insufficient number of backup volumes exist as described earlier, first register a backup volume and then delete the target backup volume.
You can execute this processing also using the history information delete command, or device information setting command.
Add a storage server to the backup operation as follows:
Display the initial window. For more information, see "Starting the initial window.
Register a storage server. For more information, see "Registering a storage server".
Fetch all the information of devices connected to the added storage server. For more information, see "Fetching device information on a storage server".
Display the backup management window. For more information, see "Displaying the backup management window".
Set the information for the storage server. For more information, see "Setting the environment for a backup operation server".
Set the operation type for a device whose information has been fetched in Step 3. For more information, see "Setting the operation type for a device".
Set a backup policy for all the transaction volumes registered in Step 5. For more information, see "Setting backup policy".
To delete a storage server follow the steps as shown below. Please be sure to do this work before removing the operating volume for deletion.
Display the backup management window. For more information, see "Displaying the backup management window".
Delete the backup history for all the transaction volumes on the storage server to be deleted. For more information, see "Deleting a backup history".
Delete the backup policy for all the transaction volumes on the storage server to be deleted.
If you display a storage server in a tree view, a list of transaction volumes on this storage server will be displayed. After selecting a transaction volume for which you want to delete, delete the backup policy. Click the right mouse button and from the popup menu, select [Delete backup policy]. The following setup window will be displayed.
Carefully check the displayed server name and transaction volume name and click the [OK] button.
Delete device information on the storage server to be deleted.
After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed.
Move all the volumes displayed in the "Transaction Volume" and "Backup Volume" fields to the "Other Volume" field. Click the [>] button to move volumes.
Display the initial window. For more information, see "Starting the initial window".
Delete a storage server.
Select a storage server and select [Delete Server] from the Operation menu. The following window will be displayed.
Carefully check the server name and click the [Yes] button.
You can delete a server information also using the server information deletion command (stgxfwcmdelsrv).
To stop a backup operation, stop daemons on the Storage server. Normally, they are automatically stopped when the system stops.
You can stop an individual daemon if you need to do so for some reason. For more information, see "Starting and Stopping Daemons".
When the daemons stop, all functions of AdvancedCopy Manager running on the storage server stop.
Stop daemons on a storage management server only after checking that all the storage servers that it manages are stopped.
This section describes the backup and restore operations of SDX objects.
A good understanding of the basic operation of normal volumes is required for these operations.
For details on GDS, refer to the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating Environment)."
There are two types of the operations (with different copy units for each type):
Backup operation in units of logical volumes (method with GDS Snapshot)
Backup operation in units of slices (method without GDS Snapshot)
For details on how to confirm and select the type of operation, refer to "Setting the unit of SDX object operations."
The two types of operation cannot be performed on a single Storage server.
The unit of SDX object operations is normally set as follows:
When PRIMECLUSTER GDS Snapshot has been included PRIMECLUSTER GDS 4.1A30 or later - Units of logical volumes
Others - Units of slices
For operation in units of slices in an environment with PRIMECLUSTER GDS 4.1A30 or later installed, use the command described in "SDX object management unit setting command (stgxfwcmsetsdx)," and then set operation in units of slices by taking action as described in "Fetching device information from a Storage server."
If PRIMECLUSTER GDS has already been upgraded from version 4.1A20 or earlier to 4.1A30 or later, follow the procedure below to change the setting to operation in units of logical volumes.
Refer to "Deleting the Storage server," and delete the Storage server.
Use the command described in "SDX object management unit setting command (stgxfwcmsetsdx)," to specify management in units of logical volumes.
Take action as described in "Registering the Storage server," and perform the subsequent operations.
For operation in units of slices as before, the above procedure need not be followed.
If AdvancedCopy Manager has been upgraded from version 10.3 or earlier in an environment that includes PRIMECLUSTER GDS 4.1A30 or later, the operation described in "Fetching device information from a Storage server" results in a change to the unit of SDX object operations and detection of a change to a managed device.
To keep operation in units of slices, abort the fetching operation without accepting the detected change, use the command described in "SDX object management unit setting command (stgxfwcmsetsdx)," " to set operation in units of slices, and then specify necessary values again.
Operation in units of logical volumes is possible with operation in linkage with GDS Snapshot.
The physical structure of the logical volumes need not be considered.
To specify a GDS logical volume in the AdvancedCopy Manager command, specify the GDS logical volume name.
dev/sfdsk/class-name/dsk/volume-name
Configuration and conditions of unsupported SDX objects
AdvancedCopy Manager does not support the following SDX objects (volumes):
Volume of a shadow class
Stripe volume
Switch volume
Volume in a concatenation group
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
If the total number of the slices that make up the transaction volume and slices that make up all backup volumes associated with the transaction volume at the start of synchronous processing or snapshot-type backup processing is 33 or greater, copying cannot be processed.
Also, if the source volume (the transaction volume for backup processing or the backup volume for restore processing) is in the invalid state, copying cannot be processed.
To confirm the type of volume being used, which is single, mirror, stripe, concatenation, or switch, execute "sdxinfo -e long" and see the volume type attribute that is displayed (the value in the TYPE column on the line indicated for the volume in the OBJ column).
[Volume object type attributes]
single : Single volume (supported)
mirror : Mirror volume (supported)
stripe : Stripe volume (not supported)
concat : Volume in a concatenation group (not supported)
switch : Switch volume (not supported)
Note the following about performing the backup operation.
For backup with the function in linkage with GDS Snapshot, AdvancedCopy Manager processes binding, separation, and release of volumes by using the GDS Snapshot function.
Therefore, an SDX object used by AdvancedCopy Manager must be set to a state in which the object can operate as a master object or proxy object.
A transaction volume operates as a master object, and a backup volume as a proxy object.
Specify the GDS volume structure before registering a volume with AdvancedCopy Manager.
When setting SDX objects of GDS for use by AdvancedCopy Manager, pay careful attention to the structure conditions of "Transaction volume" and "Backup volume" described in the next sections.
For details on GDS Snapshot and premises of the proxy structure, refer to the "PRIMECLUSTER(TM) Global Disk Services User's Guide (Solaris(TM) Operating Environment)."
To use an SDX object (logical volume) for transactions, register it as a transaction volume.
The transaction volume operates as a master object of GDS Snapshot.
Therefore, note the following about designing the backup operation:
An SDX object that belongs to a shadow class cannot be registered as the transaction volume.
The types of logical volumes that can be registered as the transaction volume are single volumes and mirror volumes. A stripe volume, a volume in a concatenation group, and a switch volume cannot be registered as the transaction volume.
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
A volume in a disk group to which a backup volume belongs cannot be registered as the transaction volume.
A logical volume that belongs to the single disk with a backup volume cannot be registered as the transaction volume.
If any of the slices that make up the transaction volume is separated temporarily or being copied, backup cannot be performed.
If the transaction volume (logical volume) is in the invalid state, backup cannot be performed.
A proxy object of GDS Snapshot cannot be used as the transaction volume.
Register an SDX object (logical volume) as a backup volume.
The backup volume operates as a proxy object of GDS Snapshot.
Therefore, note the following about designing the backup operation:
An SDX object that belongs to a shadow class cannot be registered as a backup volume.
The types of logical volumes that can be registered as backup volumes are single volumes and mirror volumes. A stripe volume, volume in a concatenation group, and switch volume cannot be registered as a backup volume.
Stripe groups and concatenation groups, however, can be used as subordinate groups of a mirror group.
A volume in a disk group to which the transaction volume belongs cannot be registered as a backup volume.
A logical volume that belongs to the single disk with the transaction volume cannot be registered as a backup volume.
An object whose class is different from that of the transaction volume cannot be used as a backup volume.
A master object of GDS Snapshot cannot be used as a backup volume.
A backup volume for backup by using EC or OPC must be a non-mirroring volume. If the backup volume is in a mirroring structure, only software-copy can be used.
If a backup volume cannot be stopped (e.g., when the backup volume is accessed by an application), backup cannot be performed.
If any slices of the slices that make up a backup volume is separated temporarily or being copied, backup cannot be performed.
As a backup volume, a logical volume must be the same size as the transaction volume.
For the backup operation, the total number of the slices that make up the transaction volume and slices that make up all backup volumes associated with the transaction volume must not exceed 32.
The following copy functions can be used in linkage with GDS Snapshot:
Advanced copy: Copying with the hardware function of ETERNUS, Fujitsu's storage systems
Software-copy: Copying with the disk driver of PRIMECLUSTER GDS
The following table shows the relationship between SDX object structures and their available copy functions.
|
Unit |
Volume |
SDX object structure Stripe- and concatenation-type objects cannot be copied. |
Available copy function |
|
|---|---|---|---|---|
|
Logical volume |
Transaction |
Single |
Advanced copy Software-copy |
|
|
Mirror |
No subordinate group exists. |
Advanced copy Software-copy |
||
|
A subordinate group exists. |
Software-copy |
|||
|
Backup |
Single |
Advanced copy Software-copy |
||
|
Mirror |
This consists of one disk. |
Advanced copy Software-copy |
||
|
This consists of multiple disks. |
Software-copy |
|||
|
Unit |
Volume |
SDX object structure Stripe-, concatenation-, and switch-type objects cannot be copied. |
Available copy function |
|
|---|---|---|---|---|
|
Logical volume |
Backup |
Single |
Advanced copy Software-copy |
|
|
Mirror |
No subordinate group exists. |
Advanced copy Software-copy |
||
|
A subordinate group exists. |
Software-copy |
|||
|
Transaction |
Single |
Advanced copy Software-copy |
||
|
Mirror |
This consists of one disk. |
Advanced copy Software-copy |
||
|
This consists of multiple disks. |
Advanced copy Software-copy |
|||
Specify options when performing backup to a backup volume in a cabinet that does not contain the transaction volume.
Backup in linkage with GDS Snapshot does not require a setting to indicate inter-cabinet copying.
To perform the backup operation with a Storage server and get information of a subordinate device of the Storage server, register the server.
For details on how to fetch the device information, refer to the section titled "Fetching device information from a Storage server. "
Register a GDS logical volume as a transaction volume or backup volume.
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/sfdsk/CLS1/dsk/vol1 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/sfdsk/CLS1/dsk/bvol1 swstdevinfoset completed |
The following SDX objects cannot be registered as transaction volumes or backup volumes:
Object of a shadow class
Stripe-type object
Concatenation-type object
Switch-type object
Before setting a backup policy, the required number of backup volumes for operation must be prepared according to the backup policy. (For details, refer to the section titled "Setting a backup policy.")
If the transaction volume is an SDX object, verify that there are as many backup volumes that can be proxy objects as the number of backup generations.
If the transaction volume is a GDS logical volume, each backup volume must be also a GDS logical volume.
In the following cases, SDX objects are not counted as available backup volumes:
The backup volume is an object whose class is different from that of the transaction volume.
The size of the backup volume is different from that of the transaction volume.
For backup of an SDX object, the transaction volume and a backup volume are associated as a master and proxy. Therefore, the total number of the slices that make up the transaction volume and slices that make up the backup volume used for backup of the transaction volume must be 32 or less.
Consequently, the number of backup generations that can be used is limited according to the GDS structure. Pay careful attention to this fact when designing a backup policy.
For example, if both the transaction volume and backup volume are single volumes, you can set the number of backup generations to 31, which is the maximum value. However, if both the transaction volume and backup volume are in a two-slice structure, the number of backup generations is limited to 15. If 16 or a higher value is set, the 16th generation and subsequent generations are not backed up.
If the transaction volume is an SDX object, select a backup volume that can be a proxy object for backup.
AdvancedCopy Manager automatically selects it from the registered backup volumes.
The available copy processing methods vary depending on the hardware where the GDS logical volumes are located.
EC/OPC cannot be used in the following cases:
The backup volume is an SDX object in a mirroring structure.
A subordinate group is connected to the disk group to which the transaction volume and backup volume belong.
Hardware
Available copy processing method
EC/OPC can be used.
Synchronous high-speed backup: EC, software-copy
Snapshot-type high-speed backup: OPC
Only OPC can be used.
Synchronous high-speed backup: Software-copy
Snapshot-type high-speed backup: OPC
EC/OPC cannot be used.
Synchronous high-speed backup: Software-copy
Snapshot-type high-speed backup: Unavailable
For restoration to a transaction volume in units of GDS logical volumes, copy the proxy to the master.
If the transaction volume is a GDS logical volume, restoration cannot be performed with the restore destination specified.
The available copy processing methods vary depending on the hardware where the GDS logical volumes are located.
OPC cannot be used in the following case:
A subordinate group is connected to the disk group to which the transaction volume and backup volume belong.
|
Hardware |
Available copy processing method |
|---|---|
|
OPC can be used. |
OPC, software-copy |
|
OPC cannot be used. |
Software-copy |
Do not use the sdxproxy command directly to change the state of a volume registered for backup management.
Otherwise, the sdxproxy command may create an inconsistency between the backup management information and the actual volume state. In such cases, perform recovery by executing the resource match command (swstsrsemtch).
This backup operation uses only the AdvancedCopy Manager function without linkage to GDS Snapshot. For its proper design and operation, you need to know the type of physical volumes that make up the logical volume.
When specifying a name in the AdvancedCopy Manager command, use the following name format that combines a logical volume name and AdvancedCopy Manager device name.
dev/sfdsk/class-name/dsk/volume-name:DEVNAM value by sdxinfo
For notes on SDX object operations, refer to "Notes on SDX object operations (backup management)," and "Notes on SDX object operations (replication management)."
If mirroring between cabinets is enabled and restoration by OPC is required in the event of a cabinet failure, both mirrored systems must be backed up. In such cases, the required capacity of the backup volume is not the size of the logical volume but the size of the physical volume.
For notes on designing the backup operation, refer to the section titled "Notes on SDX object operations (backup management)."
To perform the backup operation with a Storage server and get information of a subordinate device of the Storage server, register the server.
For details on how to fetch the device information, refer to the section titled "Fetching device information on a storage server."
Register the slices that make up the logical volume used for transactions as a transaction volume.
Slices of an SDX object cannot be registered as a backup volume.
Use general slices for a backup volume.
#/opt/FJSVswsts/bin/swstbackup /dev/sfdsk/CLS01/dsk/VOL01:c1t0d1 /dev/sfdsk/CLS01/dsk/VOL01:c1t0d1 swstbackup completed # |
Backup can be performed when the SDX object that makes up the applicable logical volume is in one of the states listed below.
If the object is in any other state, backup cannot be performed.
(AdvancedCopy Manager checks the state of the SDX object by using the sdxinfo command of SafeDISK/PRIMECLUSTER GDS.)
The state of the volume is ACTIVE or STOP.
The state of the physical disk is ENABLE.
The state of the slice is ACTIVE or TEMP.
In the following case, the preprocessing and postprocessing script is not executed:
A slice of an SDX object is in the TEMP state.
For operation in units of slices, restoration can be performed only if the transaction volume is a single volume.
An SDX object that is not a single volume cannot be restored.
For details on restoration of an SDX object that is not a single volume, refer to "Notes on SDX object operations (backup management)."
#/opt/FJSVswsts/bin/swstrestore /dev/sfdsk/CLS01/dsk/VOL01:c1t0d1 /dev/sfdsk/CLS01/dsk/VOL01:c1t0d1 swstrestore completed # |
This section describes the backup operation for volumes under VERITAS Volume Manager (VxVM).
When the VxVM volume configuration satisfy the conditions for operation in units of logical volumes, backup operation can be performed by operation in units of logical volumes.
Before starting this operation, be sure to understand the basic operation of ordinary volumes.
For the supported VxVM volume structures, refer to "Managing a device on AdvacnedCopy Manager."
The following two types of volumes can be used as backup volumes of VxVM logical volumes:
Logical volume of VxVM
Normal device (slice)
For this backup volume, however, use a VxVM logical volume in the same structure as that of the transaction volume, in anticipation of mounting of the backup volume or its use by other applications.
The same volume structure means the following conditions are satisfied:
The size of the physical disk (LUN) is the same.
The size of the private region is the same.
The size of the public region is the same.
Each subdisk in the public region has a corresponding start offset and size.
The logical volume and subdisks have a corresponding association.
If the backup volume is the same size as the public region, a backup volume of a VxVM volume can be made into a normal device (slice). However, it is generally not possible to mount the backup volume and have other applications use it.
Similarly, a backup volume of a normal device (slice) can be made into a VxVM volume. However, it is generally not possible to mount the backup volume and have other applications use it.
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = N:1 (N>1), use one of the logical volume names included with each VM disk to register a transaction volume or backup volume.
As an example, assume the transaction volume and backup volume in the following volume structure.
VM disk disk01 (transaction volume) has logical volumes named tranvol01, tranvol02, and tranvol03, and VM disk disk02 (backup volume) has logical volumes named backvol01, backvol02, and backvol03.
VM disks disk01 and disk02 have the same slice size. The subdisk structures of VM disks disk01 and disk02 are the same. (The subdisk structure can be checked by executing "vxprint -AGts".)
In the above example, use the logical volume names tranvol01 and backvol01 when setting the device information.
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/vx/dsk/AGT01/tranvol01 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/vx/dsk/AGT01/backvol01 swstdevinfoset completed |
The logical volume specified in the device information setting command is used to specify the VM disk (slice) for backup processing. This means that tranvol02 or tranvol03 instead of tranvol01 can be set in the above example (and this is also true for backvol01). However, if tranvol01 and backvol01 are already registered, the other volumes (tranvol02, tranvol03, backvol02, and backvo03) cannot be registered.
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = N:1 (N>1) and unmount/mount processing of the transaction volume with a constructed file system is to be avoided for operational reasons, customize the backup preprocessing script (OpcBackup.pre) so that the transaction volume cannot be unmounted.
In such cases, add processing before unmount processing of the backup preprocessing script (OpcBackup.pre) to clear the mount point of the VxVM logical volume, as shown below.
[Customization example]
79: exit 0 80: fi 81: post_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".pre" 82: fstype_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".fstype" 83: bd_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".bd" 84: if [ "$device" = "/dev/vx/dsk/AGT01/tranvol01" ] then mount_point="" fi 85: if [ "$mount_point" != "" ] 86: then 87: 88: # When device cannot be unmounted 89: # 90: # if [ "$device" = "/dev/dsk/c*t*d*s*" ] |
For the backup operation of a VxVM volume, a device map file must be created because a backup volume in the same volume structure as the transaction volume must be specified.
[Example of a device map file]
# Transaction volume Backup volume /dev/vx/dsk/AGT01/tranvol01 /dev/vx/dsk/AGT01/backvol01 |
For details on the device map file, refer to "Preparing a device map file."
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = N:1 (N>1), the transaction volume cannot be unmounted/mounted using the preprocessing or postprocessing script.
For this type of structure, unmount the file system before executing backup, and mount the file system after backup.
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = 1:1, the transaction volume is unmounted and mounted in the same way as in operation with normal slices, and the following procedure is not required.
[Backup procedure]
# umount /global/AGT01/tranvol01 <-- unmount tranvol01 # umount /global/AGT01/tranvol02 <-- unmount tranvol02 # umount /global/AGT01/tranvol03 <-- unmount tranvol03 # /opt/FJSVswsts/bin/swstbackup /dev/vx/dsk/AGT01/tranvol01 /dev/vx/dsk/AGT01/tranvol01 swstbackup completed # mount -F ufs /dev/vx/dsk/AGT01/tranvol01 /global/AGT01/tranvol01 <-- mount tranvol01 # mount -F ufs /dev/vx/dsk/AGT01/tranvol02 /global/AGT01/tranvol02 <-- mount tranvol02 # mount -F ufs /dev/vx/dsk/AGT01/tranvol03 /global/AGT01/tranvol03 <-- mount tranvol03 |
To prevent unmount/mount processing of the transaction volume for operational reasons, take action as described in "Customizing preprocessing and postprocessing scripts," and execute backup by using the procedure described below.
[Backup procedure (while preventing unmount/mount processing of the transaction volume)]
# lockfs -w /global/AGT01/tranvol01 <-- lock file system tranvol01 # lockfs -w /global/AGT01/tranvol02 <-- lock file system tranvol02 # lockfs -w /global/AGT01/tranvol03 <-- lock file system tranvol03 # /opt/FJSVswsts/bin/swstbackup /dev/vx/dsk/AGT01/tranvol01 /dev/vx/dsk/AGT01/tranvol01 swstbackup completed # lockfs -u /global/AGT01/tranvol01 <-- unlock file system tranvol01 # lockfs -u /global/AGT01/tranvol02 <-- unlock file system tranvol02 # lockfs -u /global/AGT01/tranvol03 <-- unlock file system tranvol03 # fsck -n -F ufs /dev/vx/dsk/AGT01/backvol01 <-- check file system backvol01 # fsck -n -F ufs /dev/vx/dsk/AGT01/backvol02 <-- check file system backvol02 # fsck -n -F ufs /dev/vx/dsk/AGT01/backvol03 <-- check file system backvol03 |
Even if lockfs -w is used to flush the file system cache and restrict subsequent update, file contents are not guaranteed for the file in Write Open (excluding the database space of Oracle used to support on-line backup).
If there is a process under renewal of metadata, consistency of data of the file system itself is also not guaranteed because lockfs is specified.
To handle this problem, perform fsck processing after backup to check the consistency of the backup data.
Even if the following message is output in fsck processing, there is no problem with the consistency of the file system. Execute fsck -y for restoration.
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = N:1 (N>1), the transaction volume cannot be unmounted/mounted using the preprocessing or postprocessing script.
For this type of structure, unmount the file system before executing restoration, and mount the file system after restoration.
If the target VxVM logical volume satisfies the condition of logical volumes:VM disk = 1:1, the transaction volume is unmounted and mounted in the same way as in operation with normal slices, and the following procedure is not required.
[Restoration procedure]
# umount /global/AGT01/tranvol01 <-- ummount tranvol01 # umount /global/AGT01/tranvol02 <-- ummount tranvol02 # umount /global/AGT01/tranvol03 <-- ummount tranvol03 # /opt/FJSVswsts/bin/swstrestore /dev/vx/dsk/AGT01/tranvol01 /dev/vx/dsk/AGT01/tranvol01 swstrestore completed # mount -F ufs /dev/vx/dsk/AGT01/tranvol01 /global/AGT01/tranvol01 <-- mount tranvol01 # mount -F ufs /dev/vx/dsk/AGT01/tranvol01 /global/AGT01/tranvol02 <-- mount tranvol02 # mount -F ufs /dev/vx/dsk/AGT01/tranvol01 /global/AGT01/tranvol03 <-- mount tranvol03 |
To change the volume structure during the backup operation, follow the procedure given below.
Specify the -z option described in "History information deletion command (swsthistdel)," to delete all history information.
Use the backup policy deletion command (swstbkpoldel) to delete the backup policies.
Delete the registration of the transaction volume by specifying the -o option in the device information setting command (swstdevinfoset). If the backup volume is a VxVM volume, also delete the registration of the backup volume by specifying the -o option in the device information setting command (swstdevinfoset).
Change the transaction volume. If the backup volume is a VxVM volume, also change the volume structure of the backup volume so that the backup volume and transaction volume can be in the same structure.
On the initial screen, execute [Get and reflect information on all devices].
Register the transaction volume and backup volume again by using the device information setting command (swstdevinfoset).
Use the backup policy setting command (swstbkpolset) to set a backup policy.
Resume the backup operation.
When the VxVM volume configuration does not satisfy the conditions for operation in units of logical volumes, backup operation can be performed by operation in units of physical disks.
When backup operation is performed in units of physical disks, disk group integrity must be maintained and, therefore, all the physical disks in the disk group must be operated synchronously.
Refer to "Device information display command (stgxfwcmdispdev)" of this manual, or the "Confirmation of devices in the save logical group" of a ETERNUS SF AdvancedCopy Manager User's Guide for the method of checking the physical volume which should take a synchronization.
It is only VM disk of the nopriv type that a physical slice becomes the unit of management.
Before starting this operation, be sure to understand the basic operation of ordinary volumes.
Snapshot backup is recommended in operation in units of physical disks. In the case of synchronized backup, the command (VxVM command etc.) which disk access produces to a copy destination disk during a copy cannot be executed.
Design disk groups that are to be used as transaction volumes or backup volumes. Observe the following conditions when designing the disk groups:
The number, sizes, and types of VM disks must be the same.
The configurations of logical volumes must be the same.
The disk group must be reconfigured in backup postprocessing. Confirm that a volume group configuration information file has been saved.
/etc/vx/cbr/bk/<disk group name>.<disk group ID>
When setting the transaction volume and backup volume, specify all disks in the volume group.
Example:
# /opt/FJSVswsts/bin/swstdevinfoset -t /dev/vx/dmp/c1t0d10s2 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -t /dev/vx/dmp/c1t0d11s2 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/vx/dmp/c1t0d20s2 swstdevinfoset completed # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/vx/dmp/c1t0d21s2 swstdevinfoset completed # |
For the backup operation of a VxVM volume, a device map file must be created because a backup volume in the same volume structure as the transaction volume must be specified.
[Example of a device map file]
# Transaction volume Backup volume /dev/vx/dmp/c1t0d10s2 /dev/vx/dmp/c1t0d20s2 /dev/vx/dmp/c1t0d11s2 /dev/vx/dmp/c1t0d21s2 |
For details on the device map file, refer to "Preparing a device map file."
Perform operation by synchronizing all physical disks in the disk group.
Perform the required preprocessing or postprocessing work for each volume group before respectively after the backup operation. Disable preprocessing and postprocessing when operating individual physical disks.
Example of snapshot backup
(Perform preprocessing for the transaction and backup volumes.) # /opt/FJSVswsts/bin/swstbackup /dev/vx/dmp/c1t0d10s2 /dev/vx/dmp/c1t0d10s2 swstbackup completed # /opt/FJSVswsts/bin/swstbackup /dev/vx/dmp/c1t0d11s2 /dev/vx/dmp/c1t0d11s2 swstbackup completed # (Perform postprocessing for the transaction and backup volumes.) |
Example of synchronous backup
(Perform preprocessing for the backup volumes.) # /opt/FJSVswsts/bin/swststartsync /dev/vx/dmp/c1t0d10s2 /dev/vx/dmp/c1t0d10s2 swststartsync completed # /opt/FJSVswsts/bin/swststartsync /dev/vx/dmp/c1t0d11s2 /dev/vx/dmp/c1t0d11s2 swstsstartsync completed (State of equivalency upkeep) (Perform preprocessing for the transaction volumes.) # /opt/FJSVswsts/bin/swstbackup /dev/vx/dmp/c1t0d10s2 /dev/vx/dmp/c1t0d10s2 swstbackup completed # /opt/FJSVswsts/bin/swstbackup /dev/vx/dmp/c1t0d11s2 /dev/vx/dmp/c1t0d11s2 swstbackup completed # (Perform postprocessing for the transaction and backup volumes.) |
The table below summarizes the preprocessing and postprocessing work to be performed before and after backup.
|
Preprocessing |
Postprocessing |
|
|---|---|---|
|
Transaction volume |
|
|
|
Backup volume |
|
|
Reconfigure the disk group as follows:
Pre-commit analysis for restoration
# /etc/vx/bin/vxconfigrestore -p dstdg Diskgroup dstdg configuration restoration started ...... Installing volume manager disk header for c1t0d20s2 ... Installing volume manager disk header for c1t0d21s2 ... - dstdg's diskgroup configuration is restored (in precommit state). Diskgroup can be accessed in read only and can be examined using vxprint in this state. Run: vxconfigrestore -c dstdg ==> to commit the restoration. vxconfigrestore -d dstdg ==> to abort the restoration. # |
Commit the change required for restoring the configuration of the copy destination disk group.
# /etc/vx/bin/vxconfigrestore -c dstdg Committing configuration restoration for diskgroup dstdg .... dstdg's diskgroup configuration restoration is committed. # |
In case of a cluster system, when a disk group or a mount resource has been defined, instead of using the import/deport command for the disk group use the online/offline process, and instead of using the file system mount/unmount commands use the online/offline processing.
When performing a system disk exchange, there are cases when conflicting backup configuration information may exist.
In such cases, the disk group ID after executing the above command needs to be set instead of the disk group.
After this operation, in case the volumes within a disk group are needed to be run in synchronous mode in the background, then depending on the volume configuration it may take some time for synchronous processing.
It is also possible to use the volumes during this time.
Perform this operation by synchronizing all physical disks in the disk group.
Perform the required preprocessing or postprocessing work for each disk group before or after restoration operation. Disable preprocessing and postprocessing when operating individual physical disks.
Example of restoration
(Perform preprocessing for the transaction and backup volumes.) # /opt/FJSVswsts/bin/swstrestore /dev/vx/dmp/c1t0d10s2 /dev/vx/dmp/c1t0d10s2 swstrestore completed # /opt/FJSVswsts/bin/swstrestore /dev/vx/dmp/c1t0d11s2 /dev/vx/dmp/c1t0d11s2 swstrestore completed # (Perform postprocessing for the transaction and backup volumes.) |
The table below summarizes the preprocessing and postprocessing work to be performed before and after restoration.
|
Preprocessing |
Postprocessing |
|
|---|---|---|
|
Backup volume |
|
Postprocessing is not required. |
|
Restoration destination volume |
|
|
Reconfigure the disk group as follows:
Restoration pre-commit analysis
# /etc/vx/bin/vxconfigrestore -p srcdg Diskgroup srcdg configuration restoration started ...... Installing volume manager disk header for c1t0d10s2 ... Installing volume manager disk header for c1t0d11s2 ... - srcdg's diskgroup configuration is restored (in precommit state). Diskgroup can be accessed in read only and can be examined using vxprint in this state. Run: vxconfigrestore -c srcdg ==> to commit the restoration. vxconfigrestore -d srcdg ==> to abort the restoration. # |
Commit the change required for restoring the configuration of the copy destination disk group.
# /etc/vx/bin/vxconfigrestore -c srcdg Committing configuration restoration for diskgroup srcdg .... srcdg's diskgroup configuration restoration is committed. # |
In case of a cluster system, when a disk group or a mount resource has been defined, instead of using the import/deport command for the disk group use the online/offline process, and instead of using the file system mount/unmount commands use the online/offline processing.
When performing a system disk exchange, there are cases when conflicting backup configuration information may exist.
In such cases, the disk group ID after executing the above command needs to be set instead of the disk group.
After this operation, in case the volumes within a disk group are needed to be run in synchronous mode in the background, then depending on the volume configuration it may take some time for synchronous processing.
It is also possible to use the volumes during this time.
|
Contents
Index
|