The difference between a normal restore and a full system restore is the severity of
the problem. Normally, if data is lost or removed, it is recovered from the archives using
the normal restore procedures. However, when a normal restore operation cannot correct a
software and/or hardware corruption problem, some additional changes may be
required.
The level of system restore required may be different as described below.
When the database is corrupted and a restore is required, both the
application software and database must be restored. This can
be achieved by performing the following steps:
Restoring the application by using the file system iDataAgent
restore options.
Restoring the database files using the restore options in the
iDataAgent.
When the client system (operating system, hardware, hard drives, etc.) is
damaged or destroyed, a full system restore may be required.
The following procedure provides the steps to perform a full system restore
when the client system is damaged or destroyed.
The procedure assumes the
following:
Latest DB2 backups are available.
If you set the point-in-time recovery
option during a full system restore, you may lose some of your data
(because of a system crash, for example). Therefore, it is
recommended that the completion time of your latest backup correspond as
closely as possible to the time identified for the point-in-time
recovery option.
The path that you will follow in this procedure is based on whether or not
DB2 database applications were running during the previous full system backup.
If no such applications were running, the following are brought up after the
full system restore of your file system: DB2 database applications, DB2
instances, and the existing databases for the DB2 instances. However, if
at least one such application was running, only the DB2 database applications
and the DB2 instances are brought after the restore (the existing databases for
the DB2 instances are not brought up).
Install directories and appropriate application files have been
backed up by the File System iDataAgent.
On Windows, system state has been backed up.
To
perform a full system restore
If necessary, rebuild the hardware as it existed before.
Using the appropriate instructions, perform a full system restore of
your file system to rebuild your operating system. In
addition to restoring your operating system, this operation will restore
the DB2 application files and iDataAgent
software.
Reboot the machine.
Without deleting the DB2 iDataAgent icon from the CommCell Console,
install the DB2 iDataAgent (again). If you do
delete this icon before installing the iDataAgent, you will lose all the DB2 backups.
For a DB2 on Windows install only, you
are prompted to provide directory paths for several items. The
system will not accept the directory paths that you entered for the
original install during a reinstall. Therefore, be sure to enter
"new" directory paths during a reinstall.
Determine whether or not any DB2 database applications were running during
the previous full system backup. To this purpose, enter the following
command at the client machine for each database to be restored:
db2 connect to <database name>
where database name is the
name of the database.
If a connection is made to each database, the restore procedure is completed.
However, if a connection to any database is unsuccessful, a message for each
unsuccessful attempt similar to the following appears:
SQL 1036C An I/O error occurred
while accessing the database. SQLSTATE=58030"
In such a case, go to the next step.
Drop each database to which no connection was made in the previous step.
To this purpose, enter the following command for each such database:
db2 drop database <database name>
where database name is the
name of the database.
Use the appropriate procedure in
Browsing Data
to restore and bring up each dropped database from its database
backup image.
To
perform a full system restore