This section describes the preparations that are required for backup operation.
In order to carry out backup operations, the services of AdvancedCopy Manager must be started on both the Management Server and the Managed Servers. Normally, these services are automatically started up when the system is started.
If the startup fails or a service has been stopped, start the service manually, referring to "Chapter 2 Starting and Stopping Services".
For carrying out backup operations from the backup management window, start the Web Console, referring to "How to start Web Console" in the ETERNUS SF Web Console Guide.
On the Management Server, register the Managed Servers that are to be managed.
This process is carried out using the Web Console.
This process can be executed using either Web Console or the stgxfwcmsetdev (Device information collection/reflection command).
When the process is finished, use the Web Console or the displayed result for the stgxfwcmdispdev (Device information display command) to confirm that the Symfoware information is displayed on the corresponding device. You can also use the stgxfwcmsetdev (Device information collection/reflection 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.
The area required when updating the repository may not be available when information concerning devices under multiple Managed Servers is fetched. Therefore, check if there is sufficient area for updating the repository before fetching the device information. If there is insufficient area, allocate the required area before fetching the device information. Refer to step 2 in "11.2.3 Troubleshooting: Failure in accessing a repository database" for details on checking the required area.
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.
While backup synchronous processing or synchronous replication processing is being performed, device information may not be fetched correctly. Therefore, for fetching device information, cancel all synchronous processing beforehand.
This process can be executed using either Web Console or the swstsvrset (Managed Server configuration information setting command).
When performing backup using commands only, the Managed Server configuration information setting command must be executed at the time that operations start.
Point
If the Management Server also works as a Managed Server, these environment settings are also required for the Management Server.
If the Managed Server environment setup has already been carried out, this process is not required.
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 running the swstdevinfoset (Device information setting 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:
Run the History information deletion command to delete the backup history information of all registered transaction volumes.
Delete the backup policies of all registered transaction volumes.
Run the Device information setting command to unregister them as transaction volumes.
Redo the procedure described in "4.1.4.4 Fetching device information on a Managed Server".
Run the Device information setting 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.
Backup operation of Symfoware database spaces that are allocated to SDX objects is not supported.
Settings for backup volumes
Run the swstdevinfoset (Device information setting 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 a 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 a Managed Server" before you register them by running the swstdevinfoset (Device information setting command).
The backup volume must have the same size as the transaction volume.
Devices to which a drive letter or mount point is assigned cannot be configured as backup volumes.
Run the swstbkpolset (Backup policy setting 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 will be set for all transaction volumes that are included in that log group.
For details on backup policies, refer to "4.1.2.4 Configuring a 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 a backup volume".
You can display the set backup policies by running the swstbkpoldisp (Backup policy display 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.
Pre-processing and Post-processing scripts for Backup need to be customized in the following conditions:
The database space exists on a file system, and
To add special pre-processing and post-processing to the corresponding scripts.
For information about the customization method, refer to "Appendix A Pre-processing and Post-processing of Backup and Restoration".
Point
Where there has been an upgrade to existing versions of AdvancedCopy Manager or its components, any scripts used with AdvancedCopy Manager or its components should be reviewed and customized accordingly after upgrading rather than continuing to reuse scripts from previous versions.
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 g1d0p1 g1d1p1 g1d0p2 g1d1p2 g1d0p3 g1d1p3 # LOG01/GRP1 # A comment can be described here also. g1d2p1 g1d3p1 g1d2p2 g1d3p2 g1d2p3 g1d3p3 # LOG02/GRP2 g1d4p1 g1d5p1 g1d4p2 g1d5p2 : : |
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 will still be read, subsequent occurrences will be 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.
