System configuration – HP Serveur lame HP ProLiant BL465c Gen8 User Manual

Page 384

Advertising
background image

Execute the

drmresync

command, specifying the backup ID of the data to be deleted.

PROMPT> drmresync -backup_id backup-ID

KAVX0001-I The drmresync command will now start.

KAVX0002-I The drmresync command will now end.

PROMPT>

When you execute this command, the primary volume and the secondary volume are
resynchronized and mirrored. Now the backup information of the specified backup ID is deleted
from the backup catalog.

Making an SQL Server database backed up to a secondary
volume available for use

By backing up an SQL Server database to a secondary volume and then performing restoration and
recovery on a server connected to the secondary volume, the database can be made available for
use on a server (SQL Server instance) other than the backup source (the server on which the backup
command is performed). This operation can be performed using a single backup command that
specifies a user script.

Additional explanation

This can be performed using the same procedure as explained in

Restoring data to an SQL

Server instance that is different from the backup source

” on page 380, except that with the procedure

in “

Restoring data to an SQL Server instance that is different from the backup source

” on page 380,

the backup, restore, and recovery commands must be performed in sequence.

This section provides an example using the following operations:

The backup data of the SQL Server database is obtained in two generations. One generation is
used for such operations as data mining on the server connected to the secondary volume, and
the other generation is used in the normal manner as a backup in the event of an error.

The restore and recovery target of this operation can only be a user database. System databases
(such as master, model, and msdb) cannot be restored to an SQL Server instance that is different from
the backup source.

System configuration

The example is based on the system configuration shown in the figure below.

Operation for SQL Server databases

384

Advertising