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

• Do not use the name META_database-ID (ten digits).dmp for a data file of a database or transaction
log file.
• Backed-up data cannot be restored or recovered by specifying the -undo option during execution
of the drmsqlinit command when there is no registered directory for storing the UNDO file.
• Backup for the transaction log cannot be executed during execution of the drmsqlinit command
when there is no registered directory for storing the transaction log backup file.
• If the system databases (master, model, and msdb) are to be backed up, specify, as the output
destination for SQL Server error log files, a volume different than the one that contains the system
databases.
• Store tempdb in a volume other than the user database to be backed up. If it is stored in the user
database subject to backup then, when the user database is restored, tempdb is overwritten by
the data restored from the secondary volume while it is online, and consequently the SQL Server
might go into an abnormal state. In this case, restart the SQL Server to recreate tempdb and restore
the server to a normal state. After restarting the SQL Server, specify a volume other than the user
database to be backed up, and then re-execute the restoration. Before re-executing restoration,
see “SQL Server database requirements for executing commands” on page 286 to check if the
database can properly be restored.
• The database cannot be restored to SQL Servers with the version different from the one at backup.
For example, a database backed up with SQL Server 2005 cannot be restored to SQL Server
2008.
• If the version of the SQL Server service pack used when the database was backed up differs from
the one used when the database was restored, the integrity of the database cannot be guaranteed.
Therefore, HP recommends that you back up the database again when you apply the SQL Server
service pack.
• One execution of the drmsqlbackup command can back up a maximum of 64 databases. If
you want to back up 65 or more databases, execute the drmsqlbackup command more than
once.
The following points must be considered if you are using SQL Server:
• In Application Agent, a backup or restoration cannot be performed for database snapshots. If you
want to back up all the instances, delete the database snapshot. If you include the database
snapshot in the backup target, the backup will fail.
• The service broker becomes disabled for databases that are restored by using the drmsqlrestore
command. To enable the service broker, execute the following SQL statement after restoration:
ALTER DATABASE [database name database-name] SET ENABLE_BROKER
• If any of the following commands is executed on a database where the database mirroring function
is used, execute the command on the principal server:
drmsqlbackup, drmsqllogbackup, drmsqldisplay -refresh
• If a database that uses the database mirroring function is to be restored, release the database
mirroring setting before restoring the database.
• If the system databases (master, model, and msdb) are to be restored in addition to a database
that uses the database mirroring function, release the mirroring setting on the database that is to
be restored, restore the system databases, and then restore the database that uses the database
mirroring function.
• If you use any of the following commands to delete backup information, the VDI metafile that was
created when the backup was performed will also be deleted. Before deleting the backup inform-
ation, back up the exported backup information and the VDI metafile.
• drmresync
• drmappcat -delete
• EX_DRM_RESYNC
Application Agent CLI User Guide 53