This section explains operations for backing up Symfoware.
Before performing the backup operation, configure the environment settings that are required for the backup according to "4.1.4 Preparing to Start the Backup".
There are two kinds of backup in AdvancedCopy Manager:
Snapshot high-speed backup
Synchronized high-speed backup
For performing a snapshot high-speed backup of Symfoware, specify the transaction volumes or log groups and run the swstbackup (Backup execution command). If you specify backup for a log group, backup will be executed at once for all transaction volumes that are included in that log group.
The following backup methods are available:
Backup method | Description |
|---|---|
Normal dump | Databases are backed up while archive log operation (i.e. normal operation) is in progress. |
Reference dump | For purposes such as long-term preservation, databases are backed up after detaching them from archive log operation. |
Note
If you specify backup for transaction volumes, you cannot specify reference dump for transaction volumes that include multi-database spaces (physical structures in which a single table or index is assigned to multiple database spaces).
When you back up with reference dump, you have to execute Symfoware's rdbrtr command in order to set inhibition of updates (disable writing of data) for all DSI (instance that expresses the storage structures for tables) on the transaction volumes to be backed up.
From the Web Console, you cannot specify backup of individual transaction volumes.
For performing a synchronized high-speed backup of Symfoware, follow the procedure below:
Use the swststartsync (Backup synchronous processing start command) to specify the transaction volumes or log groups and start backup synchronous processing. If you specify a log group, backup synchronous processing will be executed for all transaction volumes that are included in that log group.
After starting backup synchronous processing, you can cancel it with the swstcancelsync (Backup synchronous processing cancel command).
Run the swstsyncstat (Backup synchronous processing progress display command) to check that the transaction volumes are in the equivalency maintenance state while backup synchronous processing is in progress. If you have specified backup synchronous processing for a log group, check that all transaction volumes in the log group are in the equivalency maintenance state.
Specify the transaction volumes or log groups, and run the swstbackup (Backup execution command) to collect the backup. With the swstbackup (Backup execution command), you can use the backup methods shown below. On executing the swstbackup (Backup execution command), the current status at that time is registered in the backup history information, and backup synchronous processing is stopped.
Backup method | Description |
|---|---|
Normal dump | Databases are backed up while archive log operation (i.e. normal operation) is in progress. |
Reference dump | For purposes such as long-term preservation, databases are backed up after detaching them from archive log operation. |
Note
If you specify backup for transaction volumes, you cannot specify reference dump for transaction volumes that include multi-database spaces (physical structures in which a single table or index is assigned to multiple database spaces).
When you back up with reference dump, you have to execute Symfoware's rdbrtr command in order to set inhibition of updates (disable writing of data) for all DSI (function that expresses the storage structures for tables) on the transaction volumes to be backed up.
If you run the swstbackup (Backup execution command) before the transaction and backup volumes are in an equivalent state, an error will occur.
From the Web Console, you cannot specify backup of individual transaction volumes.
Point
With synchronized high-speed backup, backups are created by stopping or suspending synchronous processing. If you specify to suspend when you run the swstbackup (Backup execution command), the Suspend/Resume function performs the backup after suspending synchronous processing. For details on the Suspend/Resume function, refer to "Chapter 5 Backup Operation using Suspend/Resume Function".
For recovering the data backed up by snapshot high-speed backup or synchronized high-speed backup, execute the swstrestore (Restore execution command).
For recovery of Symfoware, from the backup volume where the history of backups by the swstbackup (Backup execution command) is managed, specify the transaction volumes or log groups when you run the swstrestore (Restore execution command).
Note
If you specify recovery for a log group, recovery will be executed at once for all transaction volumes that are included in that log group.
You can also use the -bundle option for batch recovery of multiple transaction volumes that are included in the same log group. This is called "bundle recovery".
If multiple database spaces are allocated in a RAID group, you can recover these database spaces in a single batch, which reduces the time required for applying logs and thereby the entire recovery time.
The following recovery methods are available:
Recovery to the latest status
Restoring of a specific point in time by specifying the end point of recovery (specifying the -e option when executing swstrestore (Restore execution command))
Restoring of the point in time of backup (specifying the -a option when executing swstrestore (Restore execution command))
The available recovery methods depend on the backup method (normal dump or reference dump) that was used for the data to be recovered. You can specify the following combinations:
Backup method | Recovery unit | Recovery method | ||
|---|---|---|---|---|
Recovery to the latest status | Restoring of a specific point in time by specifying the end point of recovery (*1) | Restoring of the point in time of backup | ||
Normal dump | Log group | A | A | A |
Multiple transaction volumes in the same log group | A | A | A | |
Reference dump | Transaction volume | A | N/A | N/A |
Log group | A | N/A | A | |
Multiple transaction volumes in the same log group | A | N/A | A | |
Transaction volume | A | N/A | N/A | |
A: available; N/A: not available
*1: For details on recovery points, refer to the Symfoware Server manuals. You have to memorize the recovery points until you carry out recovery of a database.
Note
All of the described methods require that access to the database spaces to be recovered is not permitted. In order to prohibit access, execute the rdbinh or the rdbexspc command provided by Symfoware. For details on these commands, refer to the Symfoware Server RDB Operations Guide.
For individual recovery of transaction volumes in a log group, the only available method is recovery to the latest status. In such a case, it is required that the database administrator takes charge of matching the relations between tables within this log group.
For performing "Recovery to the latest status" or "Restoring of a specific point in time by specifying the end point of recovery", when the archive log files are stored on external media, you have to create a file that contains the backup file names required during recovery on the Managed Server that includes the transaction volume to be recovered, and specify this file name when you start recovery. For information on how to describe this file, refer to the Symfoware Server RDB Operations Guide.
If recovery started by the swstrestore (Restore execution command) fails due to insufficient space in the working directory, you can use the -w option to retry recovery with a different directory serving as a temporary working directory. For details on the -w option, refer to swstrestore (Restore execution command).
If you perform "Restoring of a specific point in time by specifying the end point of recovery" or "Restoring of the point in time of backup", processing to restore Symfoware's management information will also be implemented. Since this processing is implemented as a portion of recovery processing, it takes time for commands to be processed.
If the recovered data were originally backed up mixing both methods (normal dump and reference dump) within a log group, recovery cannot be carried out at once for the entire log group. In such a case, specify the -bundle option in the swstrestore (Restore execution command) in order to recover multiple transaction volumes in the same log group in a batch.
If you originally backed up in units of database spaces, for recovery in units of log groups or for bundle recovery, you have to specify the relative generation number in the generation specification. This is necessary because, as shown in below example of a backup that was implemented in units of database spaces, the situation may occur that, after updating the history of a specific transaction volume (database space), absolute generation numbers are not complete for the corresponding relative generation numbers.
Example: For a log group (LOG1/RDB1) containing Database space 1 (DB1.DBSP1) and Database space 2 (DB1.DBSP2)
Day 1: Backup of Database space 1 (DB1.DBSP1)
C:\>C:\Win32app\AdvancedCopyManager\bin\swstbackup g1d0p1 g1d0p1 swstbackup completed |
Day 2: Separate backup of Database space 1 (DB1.DBSP1) and Database space 2 (DB1.DBSP2)
C:\>C:\Win32app\AdvancedCopyManager\bin\swstbackup g1d0p1 g1d0p1 swstbackup completed C:\>C:\Win32app\AdvancedCopyManager\bin\swstbackup g1d0p2 g1d0p2 swstbackup completed |
Display of history information
C:\>C:\Win32app\AdvancedCopyManager\bin\swsthistdisp -n LOG1/RDB1 Server=SV01 Device= g1d0p1 Mount-Point=DB1.DBSP1/LOG1/RDB1 (SymfoWARE) Generation Version Backup-Date Backup-Disk Status Execute ArcSerial 1 2 2006/04/12 22:00 g1d1p2 succeeded ---- 5 2 1 2006/04/11 22:00 g1d1p1 succeeded ---- 5 Server=SV01 Device= g1d0p2 Mount-Point=DB1.DBSP2/LOG1/RDB1 (SymfoWARE) Generation Version Backup-Date Backup-Disk Status Execute ArcSerial 1 1 2006/04/12 23:00 g1d1p3 succeeded ---- 5 |
For recovery in units of log groups or for bundle recovery using a history as shown above, depending on the specified option, different backup data are used. In the case described above, since, by specifying the relative generation numbers, both database spaces use the backup data of Day 2, consistency of databases after recovery can be ensured.
Type of generation number | Specified option | Backup data used in recovery | |
|---|---|---|---|
DB1.DBSP1 | DB1.DBSP2 | ||
Relative generation number | -g 1 | Backup data of Day 2 | Backup data of Day 2 |
Absolute generation number | -v 1 | Backup data of Day 1 | |
Note
If you backed up in units of log groups, the situation may occur that absolute generation numbers are not complete for backups that were implemented in units of database spaces or due to deleting a history, but the absolute generation numbers of backup in units of log groups will be complete. As shown in the below example, this is due to the fact that the numbers for transaction volumes (database spaces) with smaller absolute generation numbers are matched with the numbers for transaction volumes (database spaces) with larger absolute generation numbers. Therefore, intermediate absolute generation numbers for transaction volumes (database spaces) with smaller absolute generation numbers are missing.
Example: For a log group (LOG1/RDB1) containing Database space 1 (DB1.DBSP1) and Database space 2 (DB1.DBSP2)
Day 1: Backup of Database space 1 (DB1.DBSP1)
C:\>C:\Win32app\AdvancedCopyManager\bin\swstbackup g1d0p1 g1d0p1 swstbackup completed |
Day 2: Backup of Database space 1 (DB1.DBSP1) and Database space 2 (DB1.DBSP2) in units of log groups
C:\>C:\Win32app\AdvancedCopyManager\bin\swstbackup -n LOG1/RDB1 LOG1/RDB1 swstbackup completed |
Display of history information
C:\>C:\Win32app\AdvancedCopyManager\bin\swsthistdisp -n LOG1/RDB1 Server=SV01 Device= g1d0p1 Mount-Point=DB1.DBSP1/LOG1/RDB1 (SymfoWARE) Generation Version Backup-Date Backup-Disk Status Execute ArcSerial 1 2 2006/04/12 22:00 g1d1p2 succeeded ---- 5 2 1 2006/04/11 22:00 g1d1p1 succeeded ---- 5 Server=SV01 Device= g1d0p2 Mount-Point=DB1.DBSP2/LOG1/RDB1 (SymfoWARE) Generation Version Backup-Date Backup-Disk Status Execute ArcSerial 1 2 2006/04/12 22:00 g1d1p3 succeeded ---- 5 |
For recovery in units of log groups or for bundle recovery using a history as shown above, since all absolute generation numbers corresponding to the relative generation numbers are complete, the same backup data will be used regardless of which type of generation number you specify.
Type of generation number | Specified option | Backup data used in recovery | |
|---|---|---|---|
DB1.DBSP1 | DB1.DBSP2 | ||
Relative generation number | -g 1 | Backup data of Day 2 | Backup data of Day 2 |
Absolute generation number | -v 2 | ||
However, if you specify "-v 1", the restore command will result in an error, because backup data for Database space 2 (DB1.DBSP2) do not exist.
Point
Recovery can also be carried out using the Web Console. Bundle recovery, however, cannot be carried out using the Web Console.
Point
For executing a bundle recovery, a "Device list file" must be created in advance, defining the transaction volumes that are to be recovered in a batch. For details on device list files, refer to "4.1.5.3.1 Describing a device list file".
Create the device list file in any suitable location on the Managed Server that carries out recovery. Specifying this file when you start recovery enables you to recover multiple transaction volumes in a batch.
The following provides an example of a device list file:
# A comment line starts with "#". # LOG01/GRP1 g1d0p3 # A comment can be described here also. g1d0p4 g1d0p5 g1d0p6 g1d0p7 : : |
The rules for creating a device list file are as follows:
Describe a single transaction volume name in one line. 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 transaction 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.
Note
If you run the Restore execution command with the -bundle option specified, all transaction volumes described in the device list file will be restored. In the following cases, restore processing will result in an error:
When there is not a single description for a transaction volume
When an existing description for a transaction volume contains a formal mistake
When a transaction volume is not a Symfoware volume
When transaction volumes are straddling across multiple log groups
When the description for a transaction volume contains any incorrect lines other than descriptive lines
When the same transaction volume is specified more than once, as shown in the following example:
# Example for multiple descriptions of same transaction volume g1d0p4 g1d0p4 : : |
History information for backups that were performed with the swstbackup (Backup execution command) can be displayed and deleted.
History information for backups that were performed with the swstbackup (Backup execution command) can be displayed using the Web Console or the swsthistdisp (History information display command).
History information for backups that were performed with the swstbackup (Backup execution command) can be deleted using the Web Console or the swsthistdisp (History information display command).
Point
From the Web Console, you cannot specify deletion of backup history information for individual transaction volumes that are included in log groups.
