HP XP7 Replication Manager Application Agent CLI Reference Guide (TK981-96014, May 2014)

NOTE:
This command cannot be applied to the system databases (master, msdb, model, tempdb, and
distribution).
After a database has been restored, the log backup for different recovery paths are mixed and
displayed.
For the instance that is the target of this command, if the drmsqlbackup command of Application
Agent 6.3.0-00 or later has been executed for the instance, you can back up the transaction logs
entries associated with a backup ID, regardless of whether the backup catalog exists.
If the transaction log of SQL Server is backed up from any product other than Application Agent
before Application Agent executes the log backup of SQL Server, LAST-FULL-BACKUP-TIME
indicates the time at which the backup was executed from the product.
To associate a backup ID with a transaction log backup by using this command when the backup
catalog does not exist, all of the following conditions must be satisfied:
- The drmsqlbackup command in Application Agent 6.3.0-00 or later is used to back up the target
instance. Note that if the drmsqlbackup command in Application Agent 6.3.0-00 or later has not
been used to back up the target instance (for example, when specific databases only were backed
up with the -target option), the backup catalog for the target database (created by any version of
Application Agent) will exist when the drmsqlbackup command of Application Agent 6.3.0-00 or
later is executed.
- None of the following options are specified for the drmsqllogbackup command: -no_cat, -v,
-lsn, or -d
- An instance name is specified for the drmsqllogbackup command.
If you have deleted an instance, and then registered it again with the same instance name, you need
to create a backup catalog with the drmsqlbackup command before executing the
drmsqllogbackup command. If you execute the drmsqllogbackup command without creating a
backup catalog, the database name before the re-registration of the instance will be the target of
transaction log backup.
You have to back up a transaction log of the SQL Server database from Application Agent. If you
back up the transaction log from software other than Application Agent, the log sequence number
for the starting point of recovery for the values from FIRST-LSN to LAST-LSN might not be included.
In this case, an attempt to recover from Application Agent will fail because the log sequence number
for the starting point cannot be identified.
Return Values
0: Normal termination
Any value other than 0: Termination with an error
Examples
• In this example, the command is used to back up the transaction log file of the instance DEFAULT:
PROMPT> drmsqllogbackup DEFAULT
• In this example, the command is used to display information on the backups of the transaction log
backup files with backup ID 0000000020 and with a log backup ID from 0001 to 0003:
Basic commands172