Redpaper
Alex Osuna
Bert Jonker
Richard Waal
Henk Vonk
Peter Beijer
Microsoft Exchange Recovery using N
series Snapshots
In this Redpaper we provide instructions on how to restore snapshots from the
SnapManager® console.
Introduction
Restore a snapshot when you must do one of the following:
򐂰
򐂰
򐂰
򐂰
Recover lost or corrupt data
Recover individual deleted or archived mailboxes
Recover email items from a users mailbox
Restore a mail store to the recovery storage group
Our Environment
The following configurations are used to develop this paper (Figure 1 on page 2):
򐂰 2x IBM® Xseries 3850 in a cluster
– Broadcom onboard for cluster heartbeat
– 2x Intel® PCI dual port 1 GB Ethernet adapter
򐂰
򐂰
򐂰
򐂰
򐂰
•
One port of each dual port adapter setup with its own IP adress to the storage
VLAN
•
One port of each dual port adapter setup in a smart load balancing team
•
One active 11 stanby adapter
MS Windows® 2003 Enterprise R2 32 bit with SP2
MS Exchange 2003 Enterprise with SP2
Snapmanager for Exchange 4.0.0.1273
Snapdrive 5.0
Microsoft® iSCSI initiator 2.05 with MPIO
© Copyright IBM Corp. 2008. All rights reserved.
ibm.com/redbooks
1
򐂰 Nseries 2x n5200 A20
򐂰 Ontap 7.2.3
Clustered X3850
VLAN
N5200 A20’s clustered
Figure 1 Our environment
Restoring snapshots with SnapManager
To successfully restore a snapshot, follow the steps that are described below:
From the start menu:
1. Open the SnapManager for Exchange console.
2. Select the server name.
3. Click Restore.
4. Right-click Restore, the context menu appears.
5. Choose Restore Wizard (Figure 2 on page 3).
6. The welcome page appears.
2
Microsoft Exchange Recovery using N series Snapshots
Figure 2 Snapshot™ restore
7. Click Next to continue.
8. Choose Restore SnapManagerbackups that were created on the same Exchange Server
Figure 3 on page 4) option.
9. Click Next.
Note: SnapManager thinks of the Exchange cluster as one server, even though it is
comprised of two separate nodes.
Microsoft Exchange Recovery using N series Snapshots
3
Figure 3 Exchange wizard
10.Choose the snapshot you are restoring from the list of available snapshots are on the left
side of the window.
11.Double-click the snapshot so that the name of the snapshot shows in the Selected
Backups to restore field (Figure 4 on page 5).
12.Click Next to continue to the next window.
4
Microsoft Exchange Recovery using N series Snapshots
Figure 4 Choosing snapshot
Now you must choose a Restore option. There are two options:
򐂰 Restore back to the same Storage Group
As the name implies, this option restores the snapshot to the original Storage Group,
overwriting all present data. This option is chosen in case of an emergency, when the
Exchange Storage Group, or mail store must be available after a hardware or software
failure.
򐂰 Restore to the Recovery Storage Group
This option restores the selected snapshot to the Recovery Storage group. Use this option
when to recover a select number of individual mailboxes, or to test a SnapManager
restore. The restore you make to a Recovery Storage group does not affect the production
data, so this type of restore is relatively safe to perform.
The next few steps are the same for both restore options described above. The only
difference is the location in which the restored data becomes available. With the first option,
the restored data is stored to the original storage group. With the second option the restored
data is located in the Recovery Storage group. In this case the procedure describes a
situation in which the Restore back to the same Storage Group option is chosen.
1. Choose the Restore option by selecting the corresponding radio button.
2. Click Next to continue (Figure 5 on page 6).
Microsoft Exchange Recovery using N series Snapshots
5
Figure 5 Choosing restore option
3. Choose the database you want to restore from the list of available mail stores and Public
folder stores.
4. Check the box for each store you are restoring. Check all stores if you are recovering from
a hardware or software failure, and are trying to get all the Exchange data back to its most
recent state (Figure 6 on page 7).
5. Click Next to continue.
6
Microsoft Exchange Recovery using N series Snapshots
Figure 6 Choosing items to be restored
Figure 7 on page 8 shows you how to restore snapshots using the following two options:
򐂰 A Point-In-Time restore
The Exchange storage group is restored to the original snapshot. This means that all
changes made to the mail stores after the time of the snapshot are lost. This scenario can
be used in cases when the Exchange mail store is corrupt, or when you want to restore
Exchange, but the log files of a storage group are not available or corrupt.
򐂰 Up-to-the-minute restore
The Exchange mail store is restored to its original state during the snapshot. But in this
scenario all available log files are played back. This ensures that all changes that occurred
after the snapshot are made are incorporated in the mail store. This scenario is the
preferred method to restore after an emergency, but requires that the log files for the
particular storage group are available, and that they are located in the log directory that is
configured in Exchange 2003.
6. Choose your preferred method of restoration, by selecting the corresponding radio button.
7. Click Next to continue.
Microsoft Exchange Recovery using N series Snapshots
7
Figure 7 Choosing method of restoration
You are given a choice to perform a test restore, or to perform an actual restore. In some
situations it is useful to perform a test restore before you restore. A test restore gives you the
ability to see if a restore encounters problems. In this scenario we perform an actual restore.
8. Choose the option to perform an actual restore.
9. Click Next to continue (Figure 8 on page 9).
8
Microsoft Exchange Recovery using N series Snapshots
Figure 8 Choosing type of restore
You can choose SnapManager to verify the Exchange log files and databases before a
restore. Choosing to verify log files and databases takes some time. You can speed up the
restoration process by unchecking these option, which are selected by default. However, it is
recommended that you let SnapManager verify the log files and database files. This
Redpaper assumes that you choose to perform the verifications.
10.Select the verification options you desire (verification of log and database files, and
exhaustive verification are recommended).
11.Click Next to continue (Figure 9 on page 10).
Microsoft Exchange Recovery using N series Snapshots
9
Figure 9 Selecting verification options
On the Mount options window (Figure 10 on page 11) you are able to choose if SnapManager
must automatically mount a recovered database in Exchange 2003. This is useful if you want
to have the restored stores available immediately after the restore. The option is selected by
default, and in this scenario we also choose to restore using this option. If you, however, want
to manually mount the store, uncheck the option.
12.Click Next to continue.
10
Microsoft Exchange Recovery using N series Snapshots
Figure 10 Choosing mount options
13.Figure 11 on page 12 shows a summary of actions that are performed by SnapManger.
14.Read the summary, and then click the Finish to confirm the restore operation.
Microsoft Exchange Recovery using N series Snapshots
11
Figure 11 Summary page
15.A status window appears (Figure 12 on page 13). The window displays the tasks that are
carried out by SnapManager.
16.Click the Start Now to begin the actual restore operation.
12
Microsoft Exchange Recovery using N series Snapshots
Figure 12 Status window
17.If you have chosen to restore using the Point-in-Time option, a warning message appears
(Figure 13). It warns you that all data created after the moment that the specific snapshot
is created will be lost. If you are sure that this is ok, click the Yes to begin restoring. If not,
choose No, go back and select the Up-to-the-Minute option.
Figure 13 Warning message
18.The Restore Status window shows you the status of the restore operation.
19.When the restore is finished successfully, a message appears.
20.Click OK to close the message. Depending on the choice you made earlier to automatically
mount recovered databases, you might need to mount the stores in Microsoft Exchange to
make the data available for users.
Microsoft Exchange Recovery using N series Snapshots
13
The team that wrote this IBM Redpaper
This paper was produced by a team of specialists from around the world working at the
International Technical Support Organization, Austin Center.
Alex Osuna is a project leader at the International Technical Support Organization, Tucson
Center. He has 30 years in the IT industry mainly focused on storage. He writes extensively
and teaches IBM classes worldwide on all areas of storage. Before joining the ITSO 3 years
ago, Alex worked as a Pricipal Engineer in Tivoli® Storage. Alex holds over 10 certifications
form IBM, Microsoft and RedHat.
Bert Jonker is a Senior IT Specialist in the Netherlands. He has more than 10 years of
experience as a technical teamlead on large acounts and complex projects. His areas of
expertise include a range of Microsoft Windows products in combination with several storage
solutions. He has written extensively on migration scenarios at large environment
Richard Waal is an IT Specialist in the Netherlands. He has 6 years of experience as an
engineer working on both national and international large infrastructure projects for different
customers. His areas of expertise focuses on Microsoft technology and scripting.
Henk Vonk is a IT Specialist in The Netherlands. He has more than 5 years experience on
large accounts as technical engineer. His area of expertise include Microsoft Products.
Peter Beijer is a IT Specialist in The Netherlands. He has more than 5 years experience on
large accounts as technical engineer. His area of expertise include Microsoft Products.
14
Microsoft Exchange Recovery using N series Snapshots
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that does
not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.
© Copyright International Business Machines Corporation 2008. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
15
This document REDP-4428-00 was created or updated on July 7, 2008.
®
Send us your comments in one of the following ways:
򐂰 Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to:
redbooks@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400 U.S.A.
Redpaper ™
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are
marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate
U.S. registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at "Copyright and trademark information" at:
http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
IBM®
Redbooks (logo)
®
Tivoli®
The following terms are trademarks of other companies:
Snapshot, SnapManager, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the
U.S. and other countries.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States,
other countries, or both.
"Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation."
Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
16
Microsoft Exchange Recovery using N series Snapshots