11.07.2015 Views

Installation and User's Guide - Services and Support

Installation and User's Guide - Services and Support

Installation and User's Guide - Services and Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IBM Confidentialv Do not place multiple volumes on the same LUN. Microsoft recommends thatyou configure a single volume/single partition/single LUN as 1 to 1 to 1.System Provider: Be aware that if you are using the Windows VSS SystemProvider, no configuration is required.Software or Hardware Provider: If you use a software or hardware provider,consider the following requirements when planning for VSS Backups:v If a hardware provider is used, the disks that contain Exchange data must beconfigured as basic.v Place databases files for each storage group on their own dedicated logicalvolume.v Place logs for each storage group on their own logical volume.v Do not place non-Exchange data on storage volumes that are dedicated toExchange.v When using hardware snapshot providers, do not share storage group LUNswith other storage groups or applications.v Make sure to read <strong>and</strong> follow specific installation <strong>and</strong> configuration instructionsin the documentation provided by your VSS provider vendor.SAN Volume Controller: If you use SAN Volume Controller, consider thefollowing requirements when planning for VSS Backups:v Place databases files for each storage group on their own dedicated logicalvolume.v Place logs for each storage group on their own logical volume.v Do not place non-Exchange data on storage volumes that are dedicated toExchange.v When using hardware snapshot providers, do not share storage group LUNswith other storage groups or applications.v Only one backup is allowed to occur while the background copy process ispending. A new backup is not performed until the background copy process forthe previous backup completes. As a result, local backups for SAN VolumeController storage subsystems should be initiated at a frequency greater than thetime required for the background copy process to complete.VSS Backups of replica copies: Data Protection for Exchange provides VSSBackups of replica copies in Local Continuous Replication (LCR) or ClusterContinuous Replication (CCR) environments. For CCR copies, you must back upthe replica copy from the secondary node of the cluster that currently contains thereplica copy.VSS limitations: Data Protection for Exchange VSS offloaded backups will notfunction correctly if the Exchange storage group, database <strong>and</strong>/or log locationinformation is specified with UNC-based drive letters. This is not a commonconfiguration. For example, in the Exchange System Manager, you should notspecify the path of an Exchange storage group as:\\host_srv1\c$\Program Files\Exchsrvr\First Storage Groupbut rather as:C:\Program Files\Exchsrvr\First Storage GroupIf you are using a volume mount point, or using a cluster drive, or using acombination of both, you can still use drive-based naming, for example:Chapter 1. Data Protection for Exchange Overview 9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!