HP StorageWorks P9000 Replication Manager Software 7.1.1 CLI User Guide (TB584-96032, September 2011)

#2
This file is created when the backup command executes.
#3
When a VDI metafile storage directory was registered by using the drmsqlinit command, the
metafile is stored in the registered directory. The file name is backup-ID_database-ID.dmp. When
a VDI metafile storage directory was not registered by using the drmsqlinit command, the
metafile is stored in the directory that contains the file whose management number (file_id)
for SQL Server in the database file is a minimum value. The file name is META_database-ID.dmp.
In Application Agent, data is backed up and restored in physical volumes units so the object
configuration of an SQL Server database requires the following:
• Configure the database configuration files that comprise one instance on one physical volume.
Do not store database configuration files that comprise multiple instances on one physical volume.
• Store the following directory and file on a physical volume that does not contain database config-
uration files (*.mdf, *.ndf, and *.ldf):
• Metafile storage directory (except when metafile setting is blank)
• Backup data of the transaction log
Roll-forward recovery processing can be performed if the above directory and file are placed on
separate volumes. This is because, even if a restoration is performed, the metadata and transaction
log file cannot return to the status they were in when the backup was performed.
Backup processing for Application Agent checks whether these requirements are satisfied. If they
are not satisfied, backup processing will terminate with an error.
• You can use the following characters when naming a database:
• ASCII characters
• Multi-byte characters (one character must be expressed by using 1 or 2 bytes)
However, do not use the following characters:
\ / : , ; * ? < > |
• Do not use the name META_database-ID (ten digits).dmp for a data file of a database or transaction
log file.
• In a cluster environment, specify a user on each node for the owner of a database subject to
backup. Local users with the same user name and password on different nodes are not considered
to be the same user. Therefore, use a domain user account that is common to all nodes. If failover
is performed to a node where the database-owner user does not exist, backup fails because the
database owner is unknown.
• 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.
• Storetempdb 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 280 to check if the
database can properly be restored.
Application Agent system configurations78