HP XP P9000 Replication Manager Software 7.6.0-00 Application Agent CLI Reference Guide

Basic command specifications (SQL Server database backups)
drmsqlbackup (Backs up an SQL Server database to a secondary volume)
Formats
To back up:
drmsqlbackup { instance-name | DEFAULT }
[ -system | target database-name | -f target-definition-file-name ]
[ -rc [ name-identifying-the-generation ]]
[ -pf copy-parameter-definition-file ]
[ -comment backup-comment ]
[ -script user-script-file-name ]
[ -s backup-server-name
[ -auto_import
[ -auto_mount [ mount-point-directory-name ]]
]
[ -svol_check ]
]
To create backup catalog:
drmsqlbackup { instance-name | DEFAULT }
[ -system | target database-name | -f target-definition-file-name ]
-template
[ -comment backup-comment ]
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.
Application Agent CLI Reference Guide 145