supported. In this case, perform manual failover of Exchange Server before the
restore.
•
Restore to a different location can be only performed using Microsoft Virtual Disk
Service.
Therefore, with XP VSS hardware provider, restore to a different location is possible
only after the backup session was run in the VSS compliant mode.
•
With XP VSS hardware provider, if a backup of an LCR or CCR storage group
copy is run in the resync mode, restore of data to the original location (original
database or Exchange Information Store) fails.
The reason for such a behavior is that source volumes, on which the database
copy or Exchange Replication Service resides, are in the suspended mirror
relationship with the ZDB replica, which should be restored to the original
database.
Under such circumstances, the restore process first unpresents the source volumes
from the Exchange Server database copy, and presents them to the Exchange
Server original database afterwards. These actions result in shortage of source
disks presented to the database copy. After restore, you need to set up your LCR
or CCR environment again.
To enable such restore process, set the omnirc variable
OB2VSS_FORCE_INSTANT_RECOVERY to 1, perform restore, and after it,
manually set up the LCR or CCR environment.
•
With Microsoft Exchange Server 2007 running in a CCR environment, whose
database copy resides on the backup system, there are particular situations where
you need to consider additional steps for performing instant recovery:
• When XP VSS hardware provider is used, and the application system, where
the production database resides, and the backup system, where the database
copy resides, are connected to different disks arrays that are not configured
in the same SAN. In such a configuration, the application system does not
see LUNs on the backup system and vice versa.
• When EVA VSS hardware provider is used and the disk arrays of the
application system and the backup system are not controlled by the same
Command View.
• When the XP VSS hardware provider is used in the resync mode, regardless
of the number of disk arrays are used.
In the above situations, there is only one instant recovery scenario. For a successful
instant recovery, follow the steps:
1.
Fail over Exchange Server. This will cause your production database to reside
on the former backup system, where the database copy resided before
failover.
Zero downtime backup integration guide
399
Need help?
Do you have a question about the Data Protector A.06.11 and is the answer not in the manual?
Questions and answers