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

Description
The drmsqlbackup command takes the volume that contains the specified instance in memory, and
backs it up to the secondary volume. If the instance's objects (such as data files and various databases)
exist across several volumes, all primary volumes will be backed up to secondary volumes.
When SQL Server instances are backed up, an online backup will be performed. If instances that are
not running are specified when executing a command, a command error occurs.
When a command is executed, SQL Server's VDI is used to create a snapshot of the database within
the instance.
Snapshot data (metafiles) are stored in one of the following directories, depending on the situation:
• If you registered a VDI metafile storage directory by using the drmsqlinit command:
The metafile is stored in the registered directory. The file name is backup-ID_database-ID.dmp.
• If you did not register a VDI metafile storage directory by using the drmsqlinit command:
The metafile is stored in the directory that contains the file with the smallest management number
(file_id) value for SQL server in the database file. The file name is META_database-ID.dmp.
If the metafile storage directory is blank, no metafiles exists in the primary volume after backup finishes.
Only the secondary volume contains metafiles.
Do not use META_database-ID.dmp as the name of the data file or transaction log file stored in
the location where the primary data file is stored. If a file with such a name exists, the backup will
fail.
The backup ID used in the metafile is a ten-digit numerical value assigned during command execution.
The database ID is a ten-digit numerical value, assigned by the SQL server that identifies a database.
If you specify an instance that is not running, the command fails. All the user databases included in
the instance are to be backed up. The system databases (master, model, and msdb) for SQL server
are not included. You can back up system databases in either of the following ways:
• To back up all system databases (master, model, and msdb) other than tempdb, and all user
databases, execute this command with the -system option specified.
• To back up only system databases (master, model, and msdb), specify the databases to be backed
up for the -target option or the -f option and then execute the command.
The system cache of the secondary volume must be cleared before executing this command. Mount
or unmount the secondary volume on the backup server to clear the system cache.
When you execute this command on the copy group in the paired status (PAIR), the status of the
copy group is changed to PSUS.
When the drmsqlbackup command is executed while the pair status is SMPL, paircreate is not
run automatically. Execute the paircreate command only when the PAIR_CREATE parameter of
the RAID Manager-linkage definition file (DEFAULT.dat) is set to ENABLE.
When the drmsqlbackup command is executed on the local site, and the pair status is SMPL, the
command does not automatically create a pair. In this case, if the PAIR_CREATE parameter in the
RAID Manager-linkage definition file (DEFAULT.dat) is set to ENABLE, the command automatically
creates a pair.
After installation, if the drmsqlbackup command is executed without executing the drmsqldisplay
command with the -refresh option specified, and no dictionary map files are created, dictionary
map files are created using the drmsqlbackup command. In this case, the processing time required
to create the dictionary map files is added to the time required to execute the backup command.
Therefore, before you execute the drmsqlbackup command, make sure to first execute the
drmsqldisplay command with the -refresh option specified to create the dictionary map files.
Application Agent CLI Reference Guide 143