or to a different location. For details, see “Microsoft Exchange Server 2007 writer
restore specifics” on page 388.
Note that restore to the original location will fail if not all objects residing on the
target volume are selected for restore. Fore example, if you have four stores and
transaction logs on the target volume, and you select only one store for restore, restore
session will fail. Thus, the following configuration scenarios are possible when
restoring Microsoft Exchange Serve data:
• Transaction logs and database stores are on the same target volume.
You cannot select only database stores for instant recovery in the GUI or CLI. If
transaction logs and/or database stores are lost, whole storage group (or all
objects residing on the target volume) need to be recovered.
In this case, you can perform only point-in-time recovery. Transaction logs will be
replaced with the backed up transaction logs.
• Transaction logs and database stores are on different target volumes.
You can select only the database stores for instant recovery in the GUI or CLI. If
a database store is lost, it can be recovered separately provided that it resides
alone on the target volume to be recovered. Otherwise, all stores residing on the
target volume must be selected for restore. If transaction logs are lost, whole
storage group should be recovered.
In this case, you can perform either point-in-time or rollforward recovery.
To perform a point-in-time recovery of Microsoft Exchange Server writer data,
select the whole storage group. Transaction logs will be replaced with the backed
up transaction logs.
To perform a rollforward recovery, select only the database stores and original
location. The existing transaction logs will be applied to restored databases.
However, rollforward recovery will not be possible if point-in-time recovery of the
same backup session was performed before.
Microsoft Exchange Server 2007 instant recovery prerequisites and limitations
Prerequisites
For prerequisites which apply also to instant recovery, see “Prerequisites” on page 390.
Limitations
• In CCR environments where original database resides on a different EVA disk
array than the database copy, restore of the database copy to the location where
original database resides will fail, since restore to a different disk array is not
Integrating the Data Protector ZDB integrations and Microsoft Volume Shadow Copy Service398
To Next Page
Loading...
Need help?
General