HP P6000 Continuous Access Software - Manual (Page 21)

dbutil -pre sqlserver_name database_name username password
IF %ERRORLEVEL% NEQ 0 goto ErrHand1
paircreate -g db_group1 -vl
IF %ERRORLEVEL% NEQ 0 goto ErrHand2
pairevtwait -s PAIR
IF %ERRORLEVEL% NEQ 0 goto ErrHand2
pairsplit -S -g db_group1
IF %ERRORLEVEL% NEQ 0 goto ErrHand3
pairevtwait -s SMPL
IF %ERRORLEVEL% NEQ 0 goto ErrHand3
dbutil -post sqlserver_name database_name username password
goto TheEnd
:ErrHand1
echo DB FREEZE FAILED: %0%
RingAlarm "DB FREEZE FAILED: %0%"
goto TheEnd
:ErrHand2
echo Pair Create FAILED: %0%
RingAlarm "Pair Create FAILED: %0%"
goto TheEnd
:ErrHand3
echo Pair Split FAILED: %0%
RingAlarm "Pair Split FAILED: %0%"
goto TheEnd
:TheEnd
Testing the process
Thoroughly test the entire backup and restore process before implementing it in a production
environment.
Chapter 3 describes the recovery and restore process in more detail.
Backing up transaction logs
Snapshots and snapclones are point-in-time images of the database as it exists when the snapshot or
snapclone is created. By themselves, these backups can be used to restore the database to the same
point in time. To roll the database forward from the point of the backup to a more recent time, you
need a continuous set of transaction log backups for the database.
See your Microsoft SQL Server documentation for information about backing up transaction logs.
Regardless of the method used, a restored database can be rolled forward only to the point in time
of the most recent transaction log. This determines the “data exposure” or the maximum amount of
data that may be lost in a failure. Give this critical aspect of the backup and restore process careful
consideration when planning backups.
HP StorageWorks DButil user guide 21