Exchange 2003 and Volume ShadowCopy Services |
 |
By Mike Daugherty
14 Jun 2004 | SearchExchange.com |
 |


|
The following is tip #8 from "12 ways to protect your Exchange 2003 data," excerpted
from Mike Daugherty's new book, Monitoring & Managing Microsoft Exchange Server 2003,
reprinted with permission of Digital Press, an imprint of Elsevier, copyright 2004. For more
Information, please visit www.elsevier.com. Return to the main page for more tips on this
topic.
The time required to back up an Information Store or to recover a lost or damaged
Information Store is directly related to the amount of data to be copied and the speed of
the backup device.
Administrators are always seeking better ways to improve this process, and Storage Area
Network hardware vendors have provided technologies -- specifically snapshots and clones --
that enable more rapid recovery. However, Exchange backups (regardless of whether they are
normal backups, snapshots, or clones) require coordination with Exchange software. Exchange
has always provided Application Programming Interfaces so that backup utilities could
perform Exchange-aware backups. However, until Windows 2003 and Exchange 2003, Microsoft did
not provide support for snapshots or clones. The Windows 2003 Volume ShadowCopy Service
provides Storage Area Network and software vendors with the Application Programming
Interfaces they need to develop complete Exchange-aware snapshot and clone solutions.
Windows 2003 does not provide the snapshot and clone solution; it only supplies the
Application Programming Interfaces needed to create the solution.
A snapshot is not a complete redundant copy of your Exchange Information Store and therefore
does not provide protection for a lost or damaged Information Store. A snapshot is a
metadata mapping and is designed to maintain a point-in-time view of the data in the
snapshot.
On a disk volume for which you have created a snapshot, when a block of data is changed, the
changed block is written to another location that is allocated from free volume pool space.
The original (unchanged) block is maintained as part of the snapshot. In this manner, the
original blocks that represent the point-in-time snapshot are preserved. As shown in Figure
9.16, the production data set consists of the original unchanged blocks remaining in the
disk volume, plus the changed blocks. The point-in-time snapshot consists of the original
blocks.
Clones are based on RAID 01 concepts. RAID 01 is a combination of striping (RAID 0), which
interleaves data across multiple disks for better performance, and mirroring (RAID 1), which
provides complete duplication of data. For example, Figure 9.17 shows a two-member RAID 01
set that consists of four disks mirrored to four disks.
You can create a clone by adding an additional member (or members) to this RAID 01 set and
then separating one of the members from the set (Figure 9.18). The separated member (the
clone) is a complete standalone copy of the data that you can use to restore an Exchange
Information Store.
A complete backup/recovery solution using clone technology requires the Windows 2003 Volume
ShadowCopy Service support, Storage Area Network hardware technology, and Volume ShadowCopy
Service–aware (and Exchange-aware) backup software. The backup procedures will be specific to
the hardware/software vendor.
Get more "12 ways to protect your Exchange 2003 data." Return to the main
page.
About the author: Mike Daugherty is Manager of the Microsoft Consulting
Resource Unit for the Central Region as well as a Senior Solution Architect and Program
Manager with HP Consulting and Integration Services. He travels widely, working with
large Exchange installations and helping clients manage their systems. He is
based in Texas.
');
// -->
|