IBM Tivoli Storage FlashCopy Manager for UNIX and Linux, Version 4.1

Restoring data with remote mirroring

Tivoli® Storage FlashCopy® Manager software can be used to complete a remote FlashCopy restore of database or custom application data.

About this task

The instructions that are provided in this section assume the following environment:

Data is successfully backed up and the backup copy of data is accessible.
A take over host is running with the same operating system level as the production host. In addition, the take over host is configured on the remote side.
(Databases only) The database instance is created on the take over host.
Tivoli Storage FlashCopy Manager software is installed on the take over host. The software level on the production host and take over host match.

The instructions for restoring data with remote mirroring slightly vary, depending on the database or custom application. Use the instructions that match your environment.

Restore DB2® database data

The Tivoli Storage FlashCopy Manager snapshot local repository is restored to the take over host at a point in time after the remote backup. The database is restored to the take over host by using the Tivoli Storage FlashCopy Manager snapshot local repository after the remote backup. The database instance is created on the take over host. Complete the following steps:

Start the DB2 database manager with the following command: db2start
Update the Tivoli Storage FlashCopy Manager configuration parameters with the setup script wizard. Specifically, in the GLOBAL section, set the ACSD parameter to use the acsd on the take over host. Do not use the acsd of the production host.
Stop the Tivoli Storage FlashCopy Manager acsd daemon on the primary production host. Transfer all the repository files from the primary production host to the take over host. The repository files are in the directory that is defined by the parameter ACS_REPOSITORY in the ACSD section of the profile.
Start the Tivoli Storage FlashCopy Manager acsd daemon on the take over host.
From the backups that are displayed, select the remote backup to use for the restore. The backups are displayed when you enter the query command on the take over host. For example: db2acsutil query show details

Start the restore by entering the following command:

db2 restore db <db_name> use snapshot taken at <backup_timestamp>

Restore Oracle database data

Update the Tivoli Storage FlashCopy Manager configuration parameters with the setup script wizard. Specifically, in the GLOBAL section, set the ACSD parameter to use the host name on the take over host. Do not use the acsd of the production host.
Stop the Tivoli Storage FlashCopy Manager acsd daemon on the primary production host. Transfer all the repository files from the primary production host to the take over host. The repository files are in the directory that is defined by the parameter ACS_REPOSITORY in the ACSD section of the profile.
Start the Tivoli Storage FlashCopy Manager acsd daemon on the take over host.
From the backups that are displayed, select the remote backup to use for the restore. The backups are displayed after you enter the query command on the take over host. For example: acsora -f inquire_detail
Start the restore by entering the following command:
```
acsora -f restore -b <backup_id>
```

Restore Oracle in an SAP environment database data

The Tivoli Storage FlashCopy Manager snapshot local repository and the SAP backup directory, /oracle/<SID>/sapbackup, is restored to the take over host at a point in time after the remote backup. When you are restoring data in a maintenance scenario, not a disaster recovery scenario, the Tivoli Storage FlashCopy Manager repository and the SAP backup repository can be shared by NFS. Complete the following steps:

Update the Tivoli Storage FlashCopy Manager configuration parameters with the setup script wizard. Specifically, in the GLOBAL section, set the ACSD parameter to use the acsd on the take over host. Do not use the acsd of the production host.
In the init<SID>.utl file, set the ACSD parameter to use the acsd on the take over host. Do not use the acsd of the production host.
Stop the Tivoli Storage FlashCopy Manager acsd daemon on the primary production host. Transfer all the repository files from the primary production host to the take over host. The repository files are in the directory that is defined by the parameter ACS_REPOSITORY in the ACSD section of the profile.
Start the Tivoli Storage FlashCopy Manager acsd daemon on the take over host.
From the backups that are displayed, select the remote backup to use for the restore. The backups are displayed when you enter the query command on the take over host. For example: fcmcli -f inquire_detail

Start the restore by entering the following command:

BR_NSC=1 brrestore -m full -p <dir>/init<SID>.sap -b <sap backup log id> 
	-d util_vol -r <dir>/init<SID>.utl

Restore custom application agent data

The Tivoli Storage FlashCopy Manager snapshot local repository is restored to the take over host at a point in time after the remote backup. When you are recovering data for maintenance, not disaster recovery, the Tivoli Storage FlashCopy Manager repository can be shared by NFS. Complete the following steps:

Update the Tivoli Storage FlashCopy Manager configuration parameters with the setup script wizard. Specifically, in the GLOBAL section, set the ACSD parameter to use the host name on the take over host. Do not use the acsd of the production host.
Stop the Tivoli Storage FlashCopy Manager acsd daemon on the primary production host. Transfer all the repository files from the primary production host to the take over host. The repository files are in the directory that is defined by the parameter ACS_REPOSITORY in the ACSD section of the profile.
Start the Tivoli Storage FlashCopy Manager acsd daemon on the take over host.
From the backups that are displayed, select the remote backup to use for the restore. The backups are displayed when you enter the query command on the take over host. For example: fcmcli -f inquire_detail
Start the restore by entering the following command:
```
fcmcli -f restore -b <backup_id>
```

Results

The remote mirroring relationships are stopped. The volume groups with the file systems that contain the table spaces are restored from the FlashCopy targets to the remote mirroring targets. The file systems that contain the table spaces are mounted.

For IBM® System Storage® SAN Volume Controller all versions, starting with 6.2, the remote relationships are stopped. You must restart the remote relationships before another snapshot of targets of remote mirroring can be performed. For IBM XIV® Storage System and IBM System Storage SAN Volume Controller versions lower than 6.2, the remote relationships are removed. You must re-create the remote relationships before another snapshot of targets of remote mirroring can be performed.

Feedback