5 data restoration using a recovery database, Data restoration using a recovery database – HP 3PAR Application Software Suite for Microsoft Exchange User Manual
Page 97
8.7
Recovery Procedures
3PAR Recovery Manager 4.1.0 For Microsoft Exchange 2010 User’s Guide
2
Repeat the point-in-time recovery for volume restore,
step 1 on page 8.5
to
step 4 on
page 8.6
.
3
With Exchange database(s) dismounted, preserve the current log files on your Mailbox
Database volumes if you were not able to do so from
.
4
After you have put all the disk(s) out of maintenance mode, perform the following:
a
Copy the .LOG files that you preserved and overwrite the logs recovered. This includes
the extra logs not covered by the virtual copy, making the recovery more forward-in-
time.
b
Delete the checkpoint file (.CHK).
c
Now you are ready to re-mount the database(s) to continue.
Result: The Exchange server performs a soft recovery and automatically replays the log.
Once the store is mounted, a confirmation is displayed.
8.4.5 Data Restoration Using a Recovery Database
A recovery database is a mailbox database that allows the mounting of a restored mailbox
database and data extraction from the restored database as part of the recovery operation.
Recovery databases allow you to recover data from a backup or copy of a database without
disrupting access to current data. Use the Restore-Mailbox cmdlet to extract mailbox content
from a restored database.
The following are required to restore data using a recovery database:
■
A recovery database must be created.
■
Recovery databases can ony be used for Exchange 2010 mailbox databases.
■
The target mailbox used for data merges and extraction must be in the same Active
Directory forest as the database mounted in the recovery database.
■
The database and LOG files containing the recovered data must be restored or copied into
the recovery database folder structure that was created when the recovery database was
created.
NOTE: If Windows will allow you to move, or even copy, exchange .LOG files
because it is being used by another program, part of Exchange is still live. If this is
the case, move on to
step 2 on page 8.7
.