This type of restore is also called Hot Server Restore. You can keep
up-to-date copies of the production databases on alternate servers, thus
minimizing down time in cases where the production database server has failed.
The advantages of Warm Database Restore over a traditional restore scenario
is that the database is always kept in a near ready state. In the case of
disaster, users do not need to wait for the time it would take to restore the
database in its entirety. Only the latest backup may need to be applied to the
target database before turning the application over to use it.
From the CommCell Browser, navigate to Client Computers |
<Client> | MySQL.
Right-click the <Instance>, point to All Tasks, and select
Restore MySQL Server.
Clear the Data checkbox.
Select the Recurring Restore checkbox.
In the Staging Location box, type the location where the logs
will be recovered and applied. Alternatively, click Browse to select
the staging location.
Click OK.
Click the Job Initiation tab.
Click Schedule to schedule the restore for a specific
time.
Click Configure.
In the Schedule Name box, type a schedule name.
Select the appropriate scheduling options. For example: Click
Weekly.
In the Select date and time of one job box, set the date
and time for the restore job.
In case if your entire primary server is lost or corrupted, you can directly
use the standby server until the primary server is online. When using the
standby server, perform regular backups of the database, and use those backups
to perform a full system restore on the primary server.
Once the full system restore has completed, you will
need to set up the hot standby server again by repeating the steps outlined
in this procedure.