Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing
any restore operation.
For ProxyHost clients to which you are restoring Exchange data, the Exchange
log files must be deleted before beginning the restore operation. When an Exchange
database and transaction log are restored, only that portion of the transaction
log that existed at the time of the backup is overwritten. Log files that were
created after the backup still exist, but they are not associated with the restored
transaction log. The presence of these unrelated files within the transaction
log causes the backup to fail in the truncating log phase. To prevent this from
occurring, you must manually delete Exchange log files before using the ProxyHost
iDataAgent to restore Exchange data.
To
restore Exchange 2000 data by Synchronizing the BCV group:
Perform any ProxyHost restore procedure.
NOTES
From the Restore Options (General) dialog box, you must
select:
the backup host as the destination machine
the Unconditional Overwrite option
When the restore has successfully completed on the backup host, dismount
all Exchange Services that will be restored.
On the backup host, run the BCV restore command to synchronize the data
from the backup host to the primary devices. The restore command will differ
depending on which snapshot engine you are using; refer to the manufacturer’s
documentation for instructions on synchronizing a BCV/clone with the primary
volume.
When the synchronization has successfully completed, mount the Exchange
stores.
EMC TimeFinder for SQL Integration Module (TSIM) has two restore types,
automatic and manual. The automatic restore can be completed in one step, unless
it is a standby restore, and can be covered by one script. This script can also
be used for Post Restore. The manual restore is broken into multiple steps which
can be found in the EMC ResourcePak documentation.
Backed up data should be restored to the BCVs. In order to synchronize with
the primary volumes of the production server, the user will have to manually
run specific TSIM restore commands. These commands are included in the EMC ResourcePak
for Windows.
To
restore single/multiple SQL databases to the production server in one TSIM restore
command:
Restore data/log file system to backup host.
Run the TSIM restore command to restore database.
Split the BCV pair.
Since each tsimsnap_restore command can only
specify one database, Steps 2 and 3 have to be repeated again in the same script
file to restore multiple databases. Follow the steps below to perform this operation:
Run TSIM restore command to restore database1.
Split the BCV pair1.
Run TSIM restore command to restore database2.
Split the BCV pair2.
It will take a moment for the BCV group to update the status flag to "RESTORED".
The "RESTORED" flag is required for the splitting to run.
To improve performance, a flag query command can be inserted between Step 1 and
Step 2 (also Step 3 and Step 4). In that way Step 2 or Step 4 will not start until
the "RESTORED" flag is received by query command.
The final tsim_restore script structure will
contain the following sections:
Run TSIM restore command to restore database1.
Wait for the BCV group1 to update the status flag to "RESTORED".
Split the BCV pair1.
Run TSIM restore command to restore database2.
Wait for the BCV group2 to update the status flag to "RESTORED".
For both EMC SnapView and Compaq EVM snapshot systems, the SQL database
which was selected for restore must be manually detached prior to the restore.
The restore does not use SQL APIs, it instead is just a file system restore.
If the database is not detached before the restore, a reboot will be enforced
after the restore has completed.
The database freeze/thaw utility does not support file group level, therefore
restores cannot be executed on individual file groups.
Only data that was frozen and backed up should be restored.
To
restore an Oracle database to the production server:
Shut down the Oracle Database.
Perform any ProxyHost restore procedure.
NOTES
From the Restore Options (General) dialog box, you must select
the Unconditional Overwrite option.
When the restore has successfully completed, start the Oracle Database.
You may need to recover the database by applying the Logs. For more information
on this procedure please refer to your Oracle documentation.
To
restore an Oracle database by Synchronizing the BCV group:
Shut down the Oracle Database.
Perform any ProxyHost restore procedure.
NOTES
From the Restore Options (General) dialog box, you must select:
the backup host as the destination machine
the Unconditional Overwrite option
When the restore has successfully completed on the backup host, execute
the EMC SYMCLI utilities to synchronize the BCV volumes with the Primary volumes.
When the synchronization has successfully completed, start the Oracle Database.
You may need to recover the database by applying the Logs. For more information
on this procedure please refer to your Oracle documentation.
To restore Exchange 2000 data to the
production server: