Example, System configuration – HP XP Command View Advanced Edition Software User Manual
Page 390
@echo off
@bpbackup -k "%DRMENV_COMMENT%" -p ptm_plc -s ptm_schd -i -S BackupServer -w -t 0 -L C:\temp
\nbu.log
if NOT "%ERRORLEVEL%"=="0" GOTO ABEND
@drmumount %DRMENV_R_BACKUPID%
if NOT "%ERRORLEVEL%"=="0" GOTO ABEND
GOTO END
:ABEND
exit 1
:END
exit 0
Example
This section shows the examples used for data mining and backup.
•
Execute the
drmsqlbackup
command on the DBServer1 server to make a backup (generation
1) on the secondary volume on the DBServer2 server. The data on the secondary volume is restored
and recovered on the SQL Server instance
instB
on the DBServer2 server used for data mining.
PROMPT> drmsqlbackup instA -rc local_0 -script C:\user\script1.txt -s DBServer2 -auto_import
•
Execute the
drmsqlbackup
command on the DBServer1 server to make a backup (generation
2) on the secondary volume on the BKServer server for use as a normal backup in case of an error.
The data on the secondary volume is backed up to a tape by NetBackup.
PROMPT> drmsqlbackup instA -comment "daily backup" -rc local_1 -script C:\user\script2.txt -s
BKServer -auto_import -auto_mount O:
Backing up and restoring when using an SQL Server replication
configuration
This section explains the system configuration, requirements, and procedure for performing database
backup and database restoration and recovery in a configuration that uses the SQL Server replication
function.
When the SQL Server replication function is used, the following requirements must be satisfied:
•
Of the three replication types (snapshot, transaction, and merge), use
transaction replica-
tion
.
•
The name of the distribution database is
distribution
, and only one distribution database is
created.
•
Set the '
sync with backup
' option for both the publication database and the distribution
database. For details about how to set this option, see “
Setting and checking the 'sync with backup'
System configuration
The example is based on the system configuration shown in the figure below.
Operation for SQL Server databases
390