HP Serveur lame HP ProLiant BL465c Gen8 - Manual (Page 338)

END_CODE=TERMINATE_NZ
TIMEOUT=0
[SPLIT_PROC]
# Target pair volume: SI01,dev01
[CMD]
CMDLINE=C:\HORCM\etc\pairsplit.exe -g TC01 -d sql01 -FBC 0
ENV=HORCMINST=0
ENV=HORCC_MRCF=
END_CODE=TERMINATE_NZ
TIMEOUT=10
[CMD]
CMDLINE=C:\HORCM\etc\pairevtwait.exe -g TC01 -d sql01 -s psus -t 600 -FBC 0
ENV=HORCMINST=0
END_CODE=TERMINATE_NZ
TIMEOUT=0
[FINISH_PROC]
#do nothing
Example of backing up an SQL Server database
This section describes procedures used to back up an SQL Server database to a secondary volume
at a local site while simultaneously backing it up to a secondary volume at a remote site (a backup
in a multi-target configuration). The system uses
opid_SQL as the operation ID.
To back up an SQL Server database in a multi-target configuration:
1. Clear the cache of the secondary volume.
Before performing backup, clear the system cache of the backup server.
To clear the system cache, execute EX_DRM_CACHE_PURGE on the backup server at the local
site to mount and then unmount the secondary volume. In this example, the copy group name is
set to
SI01,sq101 .
hostA > EX_DRM_CACHE_PURGE opid_SQL -cg SI01,sql01
2. Resynchronize the copy groups.
To resynchronize the copy group, execute EX_DRM_RESYNC on the database server at the local
site. If there is a big difference between the primary volume data and the secondary volume data
when data is backed up from the primary volume to the secondary volume, the backup might
take a while. Resynchronizing the copy groups before you perform backup enhances the speed
of backup processing.
hostB > EX_DRM_RESYNC opid_SQL -cg SI01,sql01 -copy_size 7
3. Back up the SQL Server database onto the secondary volume.
Perform an online backup of the SQL Server database. To do this, execute EX_DRM_SQL_BACKUP .
Specify the operation ID opid_SQL as the argument. Additionally, specify the user script file to
be executed.
hostB > EX_DRM_SQL_BACKUP opid_SQL -script C:\Uscrip.txt
Operation for SQL Server databases 338