HP Reference Information Storage System Version 1.6 Administration Guide revision 2 (T3559-90809, September 2007)

Table 41 DB Bac kup History
Feature
Description
Backup Status
General status of the backup server and each of its services.
•
A check icon indicates normal operation.
•
A ! icon indicates a problem or inactive service.
Configuration
Information
Configuration information such as backup service (enabled or disabled),
job schedule
(time) database backup file pa th location, Tivoli version.
RISS Backup Events
Information about the backup.
Table 42 Link to DB and Data Backup view
Origin
Link
left menu
Data Management > DB and Data backup
Backup file locations
• Database backup files: The database backup files and D B2 transaction log files are stored on
the database server (par tition: /db2/VolBack). The files are mirrored to a directory on the
kickstart machine ( /install/db2backups). Database files are backed up once a day, and
the local backups are kept for two days before they are d eleted.
• Master configuration files: There are three master con fi guration files: BlackBoxConfig.jcml,
Domain.jcml,andtheUserKeyStore file in the /install/configs/primary director y
on the k ickstart server. Whenever one of these files is changed and the converter and
Registr y Loader are run, the changed fi les are copied to the PCC machine, to the directory
/usr/local/MasterConfigFiles.
(To run the Registr yLoader scrip t after changing a con figuration file, run the following script on the
kickstart server: regloader.pl -cv.)
NOTE:
The file BlackBoxConfig.bct is not included in the backup, because it can be generated
from BlackBoxConfig.jcml (/install/tools/converter/dumpBCT). The script
createBBC.zr generates the .jcml versionthatisthenbackedup.
If the backup server is installed and application backup (APP) is enabled in the BlackBoxConfig.bct
file, the database backup files and copies of the master configuration files are also backed up to tape.
Restoring DB2 and master configuration file backups
The DB2 database can be restored from the backup files on the /db2/VolBack partition on the
database server. When data is lost because the database machine was reinstalled, restore the backup
files first. Restore the backup files from either the copy on the kickstart server, or tape backups if
application backup is enabled.
The functionality to restore the database backup partition and the database itself is implemented in the
script: /opt/bin/backup/db2BackupUtility on the database server. Obtain detailed usage
information by running the command without any arguments.
Follow these steps to restore the da tabase:
1. Before restoring the database, stop all RISS applications by issuing /opt/bin/stop on the PCC
serv er.
2. Log on to the database system.
Administrator Guide
71