HP XP P9000 Replication Manager Software 7.6.1-00 Application Agent CLI User Guide

For example, when ODBC sections cannot be established, if an application that performs retries
is running, since an ODBC section establishment request is issued during the roll-forward after
metafile application, the roll-forward will fail.
• When using Enterprise Manager to view a database to be backed up, before performing restora-
tion, either cut the connection to the database in Enterprise Manager, or terminate Enterprise
Manager. If restoration is performed while Enterprise Manager is connected to the database
server, restoration will fail because the database is still being used.
• Make sure that all the restoration target databases are in a state where restoration can be per-
formed. For details on the database status where restoration can be performed, see “Database
status” on page 289. If the database is in the unconfirmed status, it will be deleted and then re-
stored automatically. If even one of the restoration target databases is in a state where restoration
cannot be performed, restoration might not be performed appropriately. In such a case, delete
that database, and then re-execute the restoration command.
For example, when restoration is executed without specifying the -undo option, after restoration
the database changes to a reading status. If the restoration command is re-executed while the
database is in this status, the command will terminate with an error. In such a case, delete the
database and then execute the restoration command.
• When the drmsqlrestore command executes, it uses SQL Server with minimum startup. If the
Windows firewall functionality has been set in the database server, then when executing the
drmsqlrestore command to perform a database restoration that includes the system databases
(master, model, and msdb), a dialog box might be displayed asking if the Windows firewall is to
block SQL Server communication. If this dialog box is displayed, select Do not block. The drm-
sqlrestore command will continue processing without problems even if you do not respond to
this dialog box.
Precautions when recovering a database
• It may take a while for the consistency check processing performed within the drmsqlrecover
command to complete. In this case, you can use a parameter of the Application Agent configuration
definition file (init.conf) to specify whether this check processing is to be performed. For more
details about options to select check processing, see “Setting up the recovery option for SQL
Server database backup” on page 110.
• The number of databases that can be displayed by using the drmsqlrecovertool is 128. If
more than 128 databases exist, use the drmsqlrecover command to recover those databases
that are not displayed.
Precautions when backing up and restoring multiple databases
If one instance contains multiple databases, the unit by which volumes can be backed up and restored
differs depending on the primary volume storing each database.
• When multiple databases are stored in the same volume:
Multiple databases in the same volume can be backed up or restored at the same time.
• When multiple databases are stored in the multiple volume:
You can specify database names to back up or restore particular user databases within an instance.
When multiple databases are stored in the same volume
Databases in the same volume can be backed up or restored at the same time.
The following figure shows backup and restoration for databases stored on the same volume.
Application Agent CLI User Guide 281