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

Figure 76 Database statuses during restoration and recovery
Note that when a database in the standby status is viewed by Enterprise Manager, before executing
the drmsqlrecover command or drmsqlrecovertool command, either cut the connection to
the database in Enterprise Manager, or terminate Enterprise Manager. Since the database is locked
when the drmsqlrecover command or drmsqlrecovertool command is executed while Enterprise
Manager is connected to the database server, the command will terminate in an error.
Requirements for transaction log backup
• Before transaction log backup, use the drmsqlinit command to set the transaction log backup
file storage directory.
• If there is no backup catalog and you want to perform a transaction log backup associated with
the backup ID by using the drmsqllogbackup command, the target instance must be backed
up beforehand by using the drmsqlbackup command in Application Agent 6.3.0-00 or later.
• The instance to be backed up must be running.
• If the transaction log is corrupt, transaction log backup cannot be performed. If the KAVX1344-E
error message is output when the drmsqllogbackup command with the -no_truncate option
is executed, the transaction log might be corrupt.
• The recovery model of the database is Full or Bulk_Logged. (The recovery model Simple of the
database is not included.)
Precautions regarding backup of transaction logs
• drmsqllogbackup command cannot be applied to the system databases (master, msdb, model,
tempdb, and distribution).
• Once a database has been restored, the transaction log backups for different recovery paths are
mixed and displayed.
• Specify the latest backup ID when you perform a transaction log backup by using the drmsqllo-
gbackup command. If you specified the instance name, the latest backup ID is used.
• A transaction log backup is performed from the full backup that was last taken. However, when
LOCAL_BACKUP in the user script file used during backup is set to NO, since a backup ID is not
issued, the start point for transaction log backup is not switched.
As a result, the transaction log backup information displayed by using the drmsqllogbackup
-v command becomes inappropriate.
Operation for SQL Server databases282