In order to carry out backup operations, the daemons of AdvancedCopy Manager must be started on both the Management Server and the Managed Servers. Normally, these daemons are automatically started up when the system is started.
If the startup fails or a daemon has been stopped, start the daemon manually, referring to "Chapter 2 Starting and Stopping Daemons".
For carrying out backup operations from the backup management window, start Web Console, referring to "How to Start Web Console" in the Web Console Guide.
With Web Console, register Managed Servers that are to be managed.
Note
Change to the value of 800 characters or less before registering the Managed Server when the value of the environment variable PATH of the Management Server is more than 800 characters.
Perform this task after confirming that it is possible to communicate from the Managed Server to the IP address of the Management Server. Check the Management Server IP address with the stgxfwcmdispsrv command.
This process can be executed using either Web Console or the stgxfwcmsetdev command.
Refer to "Add/Reload Device" in the Web Console Guide for information on the operating procedures of Web Console.
When the process is finished, use Web Console or the displayed result for the stgxfwcmdispdev command to confirm that the Symfoware information is displayed on the corresponding device. You can also use the stgxfwcmsetdev command for confirmation.
Note
For fetching the configuration information for a Symfoware database, start the Symfoware database before you fetch the device information from the Managed Server.
Device information on the Managed Server must briefly be stored in the repository.
In order to be able to fetch Symfoware information, Symfoware Server Advanced Backup Controller must be running. If you have installed Symfoware Server Advanced Backup Controller after fetching the device information, you must fetch it again.
Also, depending on the system environment on which it is installed, the software's version level may be different. For details, refer to the related software manuals.
The time required for this operation depends on the total number of devices defined on the selected Managed Server. If the number of devices is large, perform this operation while the CPU load and I/O load are both low. As a guideline, each operation takes about 0.5 seconds per device (or partition) under no-load conditions.
To perform this process, execute the swstsvrset command.
Point
If the Management Server also works as a Managed Server, these environment settings are also required for the Management Server.
Symfoware Server Advanced Backup Controller must be running beforehand. If Symfoware Server Advanced Backup Controller is installed after having configured server environments, configure the server environments again.
Define the partition on which the Symfoware database space to be backed up is configured as a transaction volume, and the target volume as a backup volume.
Settings for Transaction Volumes
Define the partition on which the Symfoware database space to be backed up is configured as a transaction volume by executing the swstdevinfoset command.
For log groups, all partitions to which database spaces included in a log group are allocated must be registered separately as transaction volumes. If a single partition remains unregistered, AdvancedCopy Manager cannot back up the unregistered database spaces and, as a consequence, not maintain consistency of relations among tables when recovering the database.
Devices on which no Symfoware database space is set up cannot be set as transaction volumes for Symfoware.
Note
If you have modified any RDB system names, database space names or log group names that are assigned to transaction volumes for Symfoware, follow the procedure below to register them as transaction volumes:
Execute the swsthistdel command to delete the backup history information of all registered transaction volumes.
Delete the backup policies of all registered transaction volumes.
Execute the swstdevinfoset command to unregister them as transaction volumes.
Redo the procedure described in "4.1.4.4 Fetching Device Information on Managed Server".
Execute the swstdevinfoset command to re-register devices as transaction volumes.
For unregistering transaction volumes that are included in a log group, delete all backup policies and backup history information for these transaction volumes before you start to unregister them.
Settings for Backup Volumes
Execute the swstdevinfoset command to configure a backup volume as a backup target. If backup volumes are already registered, this operation is not required.
For the number of backup volumes required by backup management, refer to "4.1.2.5 Preparing Backup Volume".
Note
Before you modify the configuration of partitions that are registered as backup volumes, unregister them as backup volumes, and after changing the configuration, redo the procedure described in "4.1.4.4 Fetching Device Information on Managed Server" before you register them by executing the swstdevinfoset command.
Execute the swstbkpolset command to set backup policies for the transaction volumes or log groups.
If you set a backup policy for a log group, the same backup policy is set for all transaction volumes that are included in that log group.
For details on backup policies, refer to "4.1.2.4 Configuring Backup Policy".
Note
When you set backup policies, the backup volumes required for backup operations must already be registered. For the number of backup volumes required for backup operation, refer to "4.1.2.5 Preparing Backup Volume".
You can display the set backup policies by executing the swstbkpoldisp command.
If you add a database space to a log group for which a backup policy is specified and set it up as a transaction volume, you have to redo the backup policy settings for the entire log group.
From the backup of a group of volumes that are registered as backup volumes, AdvancedCopy Manager automatically selects a volume for use as a backup target volume which has the same capacity as the transaction volume.
However, when it is necessary to recognize a specific backup target volume for any operational reasons, a "device map file" that defines the relationship between a transaction volume and a backup volume must be created in advance.
Create the device map file in any suitable location on the Managed Server that carries out backup. Specifying this file when you start the backup enables you to recognize the backup targets during operation.
Point
For managing multiple backup generations, you need multiple device map files.
Device map files to be used for starting backup or synchronization must fulfill one of the following conditions:
A backup volume that is not yet in use must be specified.
A backup volume must be specified that is used in the history which is going to be deleted in the backup process.
Therefore, if you operate with multiple backup volumes, you need different device map files for the different backup volume situations.
The following provides an example of a device map file:
# A comment line starts with "#". # Business volume name Output destination backup volume name # Normal Disks /dev/sdc1 /dev/sdv1 /dev/sdc2 /dev/sdv2 /dev/sdc3 /dev/sdv3 # LOG01/GRP1 /dev/sdd1 /dev/sdz1 /dev/sdd2 /dev/sdz2 /dev/sdd3 /dev/sdz3 # LOG02/GRP2 /dev/sdg4 /dev/sdl4 /dev/sdg5 /dev/sdl5 : : |
The rules for creating a device map file are as follows:
Describe a transaction volume name and a corresponding output target backup volume name in one line. Separate the transaction volume name and backup volume name with one or more space or tab characters. One or more space or tab characters may be used as delimiters between the beginning of a line and a transaction volume name or between the end of a target backup volume name and the end of a line (new line character).
Blank lines (spaces or tab characters) may be included in the file.
Anything after the symbol '#' until the end of the line is regarded as a comment.
You cannot specify more than one backup volume for the same transaction volume in one device map file. If you do, only the first occurrence is valid. While the device map file is still read, subsequent occurrences are ignored.
A device map file may include descriptions of transaction volumes other than the processing target (Device-Name or Log-Group-Name). Refer to the description example provided in the beginning of this chapter.
If you define a backup volume as the output target for a log group, the descriptions for all transaction volumes must be included in the same single file. The descriptions must not straddle across multiple lines.
