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 demonstrates how to perform a full system restore
when the client system is damaged or destroyed. The procedure assumes the
following:
Latest file system and MySQL backups are available.
File system backup includes the system generated MySQL database.
Originating host and destination host have the same MySQL version.
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 to your operating system, this operation will restore
the MySQL application files, the system generated MySQL database, and all of the iDataAgent
software.
Reboot the machine.
If there are any problems with the MySQL iDataAgent
software, we recommend that you un-install and re-install the software
in the same drive where it was previously installed. Use the same
installation parameters, passwords, and backup type settings as were
previously used.
Use the directives in Create an Instance
to create a simple instance on the destination host. Ensure that you are
including the parameters that were used for the instance before the system
failure.
On the destination host, start up the instance and then shut down the
instance.
Try to restore the whole system by using the directives in
Browse
and Restore.
Sometimes, it is possible that the system generated MySQL database gets lost
or corrupted and the MySQL Server and the user created databases though present
will be unusable. This is a special case of disaster recovery situation. In such
case, you will need to restore the latest backup of the mysql database using the
appropriate File System iDataAgent.
After restoring the MySQL database, ensure that the file permissions are the
same as when it was backed up, else the MySQL service will not come up.