HP Serveur lame HP ProLiant BL465c Gen8 - Manual (Page 283)

The following figure shows the example when LOCAL_BACKUP is set to YES and the secondary
volume on the local site is backed up. In this example, the point A is used as the start point and
transaction log backup 1 and 2 are obtained.
Subsequently, the secondary volume on the remote site is backed up when LOCAL_BACKUP is set
to NO .
Transaction log backup 3 is obtained, with the backup ID 0000000001 .
When the drmsqllogbackup -v command is executed, transaction log backups 1, 2, and 3
are displayed for the backup ID
0000000001
. If you perform restore operations by using the
backup ID 0000000001 , transaction log backup 3 cannot be recovered on the local site (however,
transaction log backup 3 can be recovered on the remote site).
Also, if an operation is performed on the remote site due to problems on the local site, the display
of the
drmsqllogbackup -v command on the remote site is inaccurate because the backup
catalog does not exist on the remote site.
• Roll-forwards using a transaction log file which is marked by the BEGIN TRANSACTION MARK
command of SQL Server, and Roll-forwards with a specified recovery time are not supported.
Precautions regarding sequences of transaction logs
To obtain backups of transaction logs, Application Agent provides EX_DRM_SQL_TLOG_BACKUP .
Application Agent manages internal backups from primary volumes to secondary volumes, as well
as transaction log backup sequences. As such, keep the following in mind.
Transaction log backups after roll-forward
After applying a transaction log backed up by Application Agent, you must use Application Agent
commands to back up transaction logs, using one of the following methods:
• Apply backups of all transaction logs, using roll-forward.
Application Agent CLI User Guide 283