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

• Obtain transaction logs, without truncating those subsequent to point C.
To obtain transaction logs without truncating, execute the EX_DRM_SQL_TLOG_BACKUP with
the -no_truncate option specified.
DBServer > EX_DRM_SQL_TLOG_BACKUP Operation_A -no_truncate
When the -no_truncate option is specified, transaction logs are obtained from after transaction
log backup acquisition at point B, until failure occurred.
To perform restoration or recovery after obtaining transaction logs:
To perform recovery by applying the transaction logs:
1. Restore the data in the SQL Server database backed up at point A.
The database is recovered to point A. For details on how to restore the SQL Server database
backed up at point A, see “Restoring SQL Server databases” on page 315.
2. Perform recovery by applying the transaction logs backed up at point B.
When applying the transaction logs backed up at point B performs recovery, the database is
reverted to the state at point B.
For details on how to perform recovery the drmsqlrecovertool dialog by applying the
transaction logs, see “Using the drmsqlrecovertool dialog box to recover an SQL Server
database” on page 315.
When you apply multiple transaction logs for the drmsqlrecover command, you can apply
multiple transaction logs by using the transaction logs batch. For details about how to perform
recovery using a transaction log list file, see “Using the drmsqlrecover command to recover an
SQL Server database (using a transaction log list file)” on page 316.
3. Perform recovery by applying transaction logs obtained with the -no_truncate option specified.
When applying performs recovery transaction logs obtained by specifying the -no_truncate
option, transactions are applied from transaction log backup acquisition at point B until the time
of failure, and the database is reverted to the state at point C.
For details about how to perform recovery by using the drmsqlrecovertool dialog box to apply
transaction logs, see “Using the drmsqlrecovertool dialog box to recover an SQL Server
database” on page 315.
Backing up and restoring transaction log backup files
Before you can recover an SQL Server database, you need to back up the transaction logs.
Two methods are available to save transaction logs that have previously been backed up, to tape or
other storage media:
• Backing up pertinent files directly using a tape backup management software
• Backing up the transaction logs to the primary volume, and then saving the contents of the primary
volume to tape or other storage media. This method does not place a heavy load on the LAN.
The rest of this section explains the procedure that is used when transaction logs are to be backed
up to the primary volume, to back up transaction logs to the primary volume, and then save the primary
volume contents to tape or other storage media.
Operation for SQL Server databases318