HP XP7 Replication Manager Application Agent CLI User Guide (TK981-96015, May 2014)

21. Perform takeover at the local site to change the local site to the primary volume.
Execute the horctakeover command at the local site.
PROMPT> horctakeover -g TC01 -d sql01
22. At the local site, mount the primary volume and start the SQL Server service.
When performing this step, note the following point.
A transaction log backup file is associated with the backup catalog that was created for the last
complete backup of the SQL Server database. However, if this last backup was performed with NO
assigned to LOCAL_BACKUP in the user script file, no backup ID was assigned. Therefore, when the
transaction log backup information is displayed by executing drmsqllogbackup with the -v option
specified, the backup catalog and the transaction log file do not correspond, and the information
cannot be used for a recovery. In this situation, use the drmsqlrecovertool dialog box to select
transaction log backup files that are needed to perform recovery operations and perform the recovery
operations.
Backing up and restoring using a tape backup management
software that cannot link with Application Agent
When using a tape backup management software that is unable to link with Application Agent, carry
out the following procedure to back up an SQL Server database to tape, or restore an SQL Server
database from tape. For details on operations from step 1 to step 6 in the backup procedure, see
“Backing up an SQL Server database to tape” on page 300.
For details on the restoration procedure, see “Restoring an SQL Server database from
tape” on page 303.
To back up an SQL Server database to tape (when using a tape backup management software that
is unable to link with Application Agent):
1. When usual operation is in the split state, execute EX_DRM_CACHE_PURGE to clear the secondary
volume cache.
2. When usual operation is in the split state, execute EX_DRM_RESYNC to resynchronize the copy
group.
3. Execute EX_DRM_SQL_BACKUP to back up the SQL Server database into the secondary volume.
4. Execute EX_DRM_DB_EXPORT to export the backup information into the temporary file.
5. Execute EX_DRM_SQLFILE_PACK to back up the SQL Server metafile created at the backup to
the temporary folder.
6. Execute EX_DRM_FTP_PUT to transfer the temporary files to the backup servers.
7. Execute EX_DRM_DB_IMPORT to import the temporary files transferred from the database server,
into the backup catalog of the backup server.
8. Execute EX_DRM_SQLFILE_EXTRACT to deploy, on the backup server, the SQL Server metafile
transferred from the database server.
9. Check the backup ID.
To check the backup ID, open the backup ID record file (operation-ID.bid) in the following
directory on the backup server:
FTP_HOME_DIR-value\FTP_SUB_DIR-value\operation-ID\BK\operation-ID.bid
Operation for SQL Server databases376