User Scenario For Microsoft Exchange Server 2003 Backup And Restore; Example - Vss Transportable Backup - HP Data Protector A.06.11 Integration Manual

Action
Since only one RSG can exist for the same storage group and since Data Protector
can only delete an RSG that exists on the target restore location, you need to manually
delete the RSG on the other system and restart the restore.
User scenario for Microsoft Exchange Server 2003
backup and restore
This section provides examples of backup and restore policies for Microsoft Exchange
Server 2003. Three examples are provided, one for ZDB (transportable VSS snapshots)
and two for different types of restore.

Example - VSS transportable backup

This example describes a backup scenario for Microsoft Exchange Server 2003 using
VSS transportable backup together with HP StorageWorks EVA. The data is to be
backed up on tape once a day for the storage group containing critical mailboxes
and every second day for all other storage groups.
The storage groups should be backed up separately.
The following example setup is possible:
• A Microsoft Exchange Server 2003 is running on the application system and is
connected to a HP StorageWorks Enterprise Virtual Array. A tape drive is
connected to the application system for restore purposes.
• A separate backup system is connected to a tape library.
• Two storage groups are configured on the Microsoft Exchange Server 2003,
each containing two stores.
The first storage group, named Lists_Group, contains company-wide mailing lists.
The storage group contains two stores, Staff_Store for general mailing lists and
Team_Store for team mailing lists.
The second storage group, named Mailbox_Group, contains a larger number of
individual mailboxes for employees, which are given higher priority. This way
the mailboxes are still available even if mailing lists are down. The mailboxes
are set up in two separate stores, one store for each department, and named
Sales_Store and Support_Store.
• Every storage group has a separate backup specification to reduce the time
needed for the shadow copy creation. Refer to "Backup
Zero downtime backup integration guide
problems" on page 410.
417