HP StorageWorks Reference Information Storage System V1.5 Administrator Guide (T3559-96044, June 2006)

Table 42 DB Backup History
Feature
Description
Status
General status of the backup server and each of its services.
•
A check icon indicates normal operation.
•
A!iconindicatesaproblemorinactiveservice.
Completion Time
Completion time of the backup.
Size
Size of the backup.
The size shown for local backups is the size of the DB2 backup only. It
does not include any transaction log files. Therefore, the size of the local
backup is smaller than the size of the kickstart or tape backups.
Message
Information about the backup.
Table 43 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 ba ckup files and DB2 transaction log files are stored on a
separate hard disk on the database server (par tition: /db2/VolBack).Thefilesaremirroredto
a directory on the kic kstart machine (/install/db2backups). Database files are backed up
once a day, and the local backups are kept two days before they are deleted.
• Master configuration files: There are three master configuration files: BlackBoxConfig.jcml,
Domain.jcml,andtheUserKeyStore file in the /install/configs/primary directory
on the kickstart server. Whenever one of these files is changed and the converter and
Registry Loader are run, the changed files are copied to the PCC machine, to the directory
/usr/local/MasterConfigFiles.
(To run the converter and RegistryLoader after changing a configuration file, run the following
scripts on the kickstart server: createBBC.pl, converter.zr,andregloader.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 converter creates
the .jcml version that is then backed up.
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 m aster 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 firs
t. 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: /o
pt/bin/backup/db2BackupUtility on the database server. Obtain detailed usage
informat
ion by running the command without any arguments.
Follow these steps to restore the database:
1. Before restoring the database, stop all RISS applications by issuing /opt/bin/stop on the PCC
server.
70
Data management