Operation using transaction log backups – HP Serveur lame HP ProLiant BL465c Gen8 User Manual
Page 312
•
The primary volume and the secondary volume are pair defined in the database server and the
backup server.
•
The tape backup management software is installed on the backup server.
•
The parameters of the tape backup management software have been registered by using the
drmtapeinit
command.
•
The FTP service on the backup server is started, and the system is set up so a user who has logged
onto the OS of the database server can log onto the FTP server and transfer files to the FTP server.
The FTP user ID is
admin
, and the FTP user password is
password
.
•
Data for which an online back up was performed from the primary volume to the secondary volume
was backed up to tape.
•
The instance
DEFAULT
exists on the database server (server name:
DBServer
), and the service
is started.
•
On the database server and the backup server, the temporary directory for extended commands
and the VDI metafile storage directory are created.
•
The secondary volume is not always mounted. It is mounted on the E drive (drive character
E:
)
only while it is operating.
•
The primary volume configured as a pair with the secondary volume to be backed up will not be
backed up until the secondary volume is backed up onto tape.
•
The
cscript //H:Cscript
command is executed from the command prompt and the host
parameters are updated.
Example of operation using a transaction log backup
This subsection explains an example of operation using a combination of database backup and
transaction log backup. In this example, when database data is deleted accidentally after transaction
log backup, the transaction log is applied, and the database is restored to the same state at "point
C". The operation ID is
Operation_A
.
Figure 91 Operation using transaction log backups
This example is based on backup being obtained as follows:
1.
Back up the SQL Server database at point A.
For details about how the database is backed up at point A, see “
2.
Back up the SQL Server database transaction log at point B and point C.
For details about how transaction logs are backed up, see “
Operation for SQL Server databases
312