MEG-101-4.1-EN-01 10/29/09
Application Plugin Module
™
(APM)
for Exchange Server
version 4.1
BakBone Software
9540 Towne Centre Drive, Suite 100 San Diego, California 92121 866.484.2663Copyrights
NetVault: Backup APM for Exchange Server User’s Guide Software Copyright © 2009 BakBone Software
Documentation Copyright © 2009 BakBone Software
This software product is copyrighted and all rights are reserved. The distribution and sale of this product are intended for the use of the original purchaser only per the terms of the License Agreement. All other product trademarks are the property of their respective owners.
The NetVault: Backup APM for Exchange Server User’s Guide is copyrighted and all rights are reserved.
This document may not, in whole or part, be copied, photocopied, reproduced, translated, reduced or transferred to any electronic medium or machine-readable form without prior consent in writing from BakBone Software.
THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED INTO NEW EDITIONS OF THE PUBLICATION. BAKBONE SOFTWARE MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
© 1999-2009 BakBone®, BakBone Software®, NetVault®, Application Plugin Module™, BakBone
logo®, Integrated Data Protection™, NetVault: SmartDisk™, Asempra®, FASTRecover™,
ColdSpark® and Spark Engine™ are all trademarks or registered trademarks of BakBone
• About the Exchange Server APM ... 7
- NetVault: Backup APM for Exchange Server at a Glance ... 7
- Key Benefits ... 7
- Feature Summary ... 9
- Target Audience ... 10
- Recommended Additional Reading ... 10
• Technical Support ... 10
• Documentation Updates ... 10
Chapter 2: Strategy
11
• Defining an Exchange Server Backup and Recovery Strategy ... 11- Exchange Server Databases ... 11
- Exchange Server Transaction Log and Patch Files ... 12
- Available Backup Methods ... 12
- Transaction Log File Management ... 13
- Backup Types ... 14
• Example Backup Sequences ... 17
- Full Backups Only ... 17
- Full + Incremental Backups ... 17
- Full + Differential Backups ... 18
Chapter 3: Deployment 19
• Deployment Overview ... 19• Standalone Deployment ... 19
• Local Continuous Replication (LCR) ... 20
NetVault: Backup
APM for Exchange Server User’s Guide
4
• Cluster Continuous Replication (CCR) ... 23
Chapter 4: Installation
25
• Pre-Installation Requirements ... 25- Disabling Circular Logging ... 25
- Enabling Services ... 26
- Configuring Localization Settings ... 27
- Enabling Deleted Item Recovery ... 28
• Installation Procedure for Standalone and LCR Deployments ... 29
• Installation Procedure for SCC/Failover Cluster and CCR Deployments ... 30
- Pre-Installation Requirements ... 30
- Installation Procedure ... 30
• Removing Exchange Server APM ... 32
Chapter 5: Configuration
35
• Configuring Exchange Server APM ... 35- Required Windows User Account Permissions ... 35
- Configuration Process ... 36
- Specifying Default Configuration (Optional) ... 39
• About Window ... 40
Chapter 6: Backup
41
• Performing Backups with Exchange Server ... 41- Selecting Data for a Backup ... 41
- Setting Backup Options ... 43
- Finalizing and Submitting the Job ... 47
Chapter 7: Restore
49
• Restoring Data with the Exchange Server APM ... 49• Understanding Exchange Server Restore Process ... 49
- Restore Methods Available ... 50
- Phases of a Restore ... 51
• Restoring Backups in Exchange Server ... 52
- Preparing Exchange Server for Recovery ... 52
- Finalizing and Submitting Restore Job ... 62
- Performing Post Restore Steps for CCR Environments ... 63
- Performing Post Restore Steps and SCR Environments ... 64
- Example Restore Sequences ... 64
• Advanced Restore Procedures ... 70
- Renaming Storage Groups ... 70
- Moving Databases to Alternate Storage Group ... 72
- Restoring Data to Recovery Storage Group ... 75
- Disaster Recovery of Exchange Server ... 78
- Recovering to Alternate Exchange Server ... 79
Chapter 8: Troubleshooting 91
• Diagnosing VSS Related Issues ... 91I
NTRODUCTION
About the Exchange Server APM
NetVault: Backup APM for Exchange Server at a Glance Key Benefits
Feature Summary Target Audience
Recommended Additional Reading Technical Support
Documentation Updates
1.1.0 About the Exchange Server APM
1.1.1 NetVault: Backup APM for Exchange Server at a Glance
NetVault: Backup APM for Exchange Server (Exchange Server APM) increases confidence in the recoverability of Exchange and enables users to create flexible backup policies that can account for multiple recovery scenarios. Support for online backups via Exchange Server’s Extensible Storage Engine (ESE) and Volume Shadow Copy Service (VSS) provides users the flexibility to select their preferred backup method without requiring them to learn Exchange internals. Through an intuitive and easy-to-use console and automated workflow, the Exchange Server APM offers users a centralized console to setup, configure and define backup and restore policies for all of your Exchange Servers, including those deployed in a Local Continuous Replication (LCR), Single Copy Cluster (SCC), or Cluster Continuous Replication (CCR) environment. Exchange Server APM offers granular control that allows users to restore complete Information Stores, individual Storage Groups, or individual databases. Through automatic integration with a wide range of backup devices, Exchange Server APM gives the confidence that the recovery data is protected and stored offsite to ensure business continuity.1.1.2 Key Benefits
Chapter 1 Introduction
8
Copy Service (VSS) without having to worry about understanding Exchange internals.
Exchange Server APM’s flexible backup features also include: Protection for Standalone, SCC, LCR, and CCR environments Online ESE or VSS based backups
Full, Incremental, and Differential Backups while data is online and
accessible
Copy-only Backups
Protection down to the individual database
By relying on Exchange Server APM to implement your backup policies,
users can be freed to focus on more critical tasks without risking your ability to recover exactly what is needed in the unfortunate event of a failure. In addition, an IT managers' confidence is increased by knowing their email is protected, no matter what.
Speeds Up Restores to Reduce Downtime – With Exchange Server APM, you select what needs to be restored, the backup set to restore from, and NetVault: Backup's APM for Exchange Server automatically performs the restore. To maximize availability, the Exchange Server APM is designed for granular recoveries, allowing users to recover complete Information Stores, individual Storage Groups, or individual databases. Through point-and-click automated options, the Exchange Server APM reduces reliance on human interaction which eliminates errors often caused by manual intervention
Additional Exchange Server APM restore features include: Full, Incremental, and Differential Restores
Restores of complete Information Store, individual Storage Groups, or
individual databases
Rename of Storage Groups during restores
Restores to Recovery Storage Groups Restores to alternate Exchange Server
Ensure Business Continuity with Automatic Integration of Backup
gives you the confidence that your email environment is being protected and stored offsite for disaster recovery purposes. At the same time, it frees administrators from having to be available 24x7 because less experienced Exchange administrators can initiate restores with confidence that they will be performed correctly and as quickly as possible, thereby reducing downtime and improving business continuity. Exchange Server APM also provides an option for granular recovery of individual mailboxes or mailbox items without performing additional brick-level backups, eliminating backup windows and reducing storage costs. Users can also search for emails that meet specific criteria such as keywords, subject, date, or specific users across all
mailboxes without analyzing individual mailboxes one at a time or using Microsoft Recovery Storage Groups. This speeds up individual email restores by reducing the time to identify the emails to be restored. Individual mailbox items can be restored to a PST file for further analysis, discovery, or investigative purposes, thereby extending the use of individual message recovery beyond protection for accidental deletions.
1.1.3 Feature Summary
Protection for Standalone, SCC, LCR, and CCR environments Online ESE or VSS based backups
Full, Incremental, and Differential Backups while data is online and
accessible
Copy-only Backups
Protection down to the individual database Full, Incremental, and Differential Restores
Restores of complete Information Stores, individual Storage Groups,
individual databases, mailboxes, or mailbox items.
Rename of Storage Groups during restores
Restores to Recovery Storage Groups Restores to alternate Exchange Server
Chapter 1 Introduction
10
1.1.4 Target Audience
This guide is intended for users who are responsible for the backup and recovery of Exchange Server. Familiarity with Exchange Server administration and the operating system under which the database is running is assumed. Advanced knowledge of Exchange Server would be useful for defining an efficient backup and recovery strategy for the database.
1.1.5 Recommended Additional Reading
BakBone recommends that the following documentation be readily available for reference when setting up and while using this APM.
Exchange Server 2007 Documentation
http://technet.microsoft.com/en-us/library/bb124558.aspx Exchange Server 2003 Documentation
http://technet.microsoft.com/en-us/library/bb123872.aspx Exchange Server 2000 Documentation
http://technet.microsoft.com/en-us/exchange/bb330828.aspx
1.2.0 Technical Support
BakBone Software is dedicated to providing friendly, expert advice to our customers. Our highly trained professionals are available to answer questions, offer solutions to problems and generally help make the most of any BakBone software purchase. Log on to our web site for more information.
http://www.bakbone.com/supportportal
1.3.0 Documentation Updates
For late-breaking documentation updates, refer to the BakBone Software Knowledge Base. BakBone’s Knowledge Base article for NetVault: Backup APM for Exchange Server can be found at:
S
TRATEGY
Defining an Exchange Server Backup and Recovery Strategy
Exchange Server Databases
Exchange Server Transaction Log and Patch Files
Available Backup Methods Transaction Log File Management
Backup Types
Example Backup Sequences
Full Backups Only
Full + Incremental Backups
Full + Differential Backups
2.1.0 Defining an Exchange Server Backup and
Recovery Strategy
The purpose of creating Exchange Server backups is to recover an Exchange Server that is damaged from media failure or data corruption. Reliable use of backup and restore for recovery requires a well-designed backup and restore strategy which maximizes data availability and minimizes data loss, taking into account defined business requirements.
A backup and restore strategy is divided into two pieces, a backup piece and a restore piece. The backup piece of the strategy defines the type and frequency of backups that are required to meet the goals for availability of the Exchange Server and for minimizing data loss. The restore piece of the strategy defines who is responsible for performing restores and how restores should be performed to recover from the particular type of damage or failure.
2.1.1 Exchange Server Databases
A database is the finest granularity of storage organization within the Exchange Server schema. Mailboxes are assigned to specific databases, allowing
segregation of data by mailbox for security or scalability purposes. Occasionally, critical or high-volume mailboxes will be segregated to a separate database to improve performance or to perform more frequent backups.
Chapter 2 Strategy
12
mail stores and public folder stores. Note that in Exchange Server terminology, a store is the same as a database.
Microsoft also differentiates editions of the Exchange Server product by increasing support for concurrent databases. The Enterprise Edition is defined as supporting more concurrent databases than the Standard Edition.
2.1.2 Exchange Server Transaction Log and Patch Files
All changes made to the Exchange Server database are first committed to transaction log files. Any time a user modifies data stored in a mailbox or data is added to the mailbox, that change is written to a transaction log file before it is written to the Exchange Server database.Patch files are exclusive to Exchange Server 2000. They are transient files that are used for a limited time during operation and then “merged” into the database as necessary. They are often treated the same way as transaction log files. Patch files became obsolete in Exchange Server 2003.
2.1.3 Available Backup Methods
Extensible Storage Engine (ESE)
Volume Shadow Copy Service (VSS)
The Exchange Server APM supports implementing an ESE or a pure VSS backup strategy, that is, your backup strategy should include either ESE backups or VSS backups, not a combination of the two.
2.1.3.a Extensible Storage Engine (ESE)
Supported Exchange Versions – All
Supported Exchange Deployments – Standalone, Single Copy Clusters/
Failover Clusters, Local Continuous Replication (Active Copy Only), Cluster Continuous Replication (Active Copy Only)
Microsoft supports the ability to perform online backups of the Exchange Server’s databases utilizing the Extensible Storage Engine (ESE). ESE is provided by Microsoft as a standard Exchange Server component, and provides the highest levels of compatibility with all the supported versions of Exchange.
2.1.3.b Volume Shadow Copy Service (VSS)
Supported Exchange Versions – 2003 and 2007
Supported Exchange Deployments – All
Microsoft supports the ability to create snapshots of Exchange data using Volume Shadow Copy Service (VSS). Microsoft provides Exchange specific VSS writers which coordinate with the Exchange Services (operating on behalf of the
to unfreeze and truncate logs after the backup is complete.
VSS is the recommended backup method for Exchange 2007 Local Continuous Replication (LCR) and Cluster Continuous Replication (CCR) environments. When using the VSS backup method in a CCR environment, administrators have the ability to choose whether the active or passive node is backed up.
2.1.3.c ESE vs. VSS Backup Method
Consider the following differences when determining the backup method for your Exchange backup strategy.
VSS based backups are performed only at the Storage Group level, that is, individual databases cannot be backed up, while ESE based backups allow you to backup individual databases.
Restoring an individual database from a VSS based backup is supported;
however, the entire Storage Group must be offline.
Only one VSS based backup can run at one time; however, that one backup can simultaneously backup multiple Storage Groups which can reduce backup windows. Meanwhile, ESE allows multiple backup jobs for different Storage Groups to run concurrently; however, each job backs up Mailbox Databases in a serial fashion.
In LCR and CCR environments, VSS allow backups of either the active copy
or the passive copy, while ESE based backups are only allowed on the active copy. Backing up the passive copy allows users to take advantage of the extra resources available at the second copy location as well as a longer backup window due to not competing on the same resources against the actual client activity during normal work hours.
VSS based backups in 2003 cannot be restored to Recovery Storage Groups due to Microsoft limitations.
VSS based backups can be restored to alternate Exchange Servers in the
same domain while ESE based backups can only be restored to alternate Exchange Servers in a different domain.
2.1.4 Transaction Log File Management
When defining an Exchange Server backup strategy, transaction log file management is a primary consideration.
2.1.4.a Transaction Log File Truncation
Chapter 2 Strategy
14
BakBone recommends that backups that perform transaction log file truncation be performed regularly. Often, a weekly or semi-monthly backup that performs transaction log file truncation is recommended. The optimum frequency may vary considerably, depending on the use and configuration of each Exchange Server. Truncating transaction log files is performed during the backup process, when backing up using a Backup Type that provides transaction log file truncation such as the Full and Incremental Backup types.
2.1.4.b Full vs. Transaction Logs-only Backups
Full Backups will backup all files for a database, regardless of the type of file. Transaction Logs-only Backups are those that backup only the transaction log files for a database.
Full Backups allow all database files to be backed up, providing standalone restore capabilities. Depending on the size of the database, Full Backups can be
demanding in terms of storage requirements, as well as time required to complete the backup. For very large databases, this may be a significant consideration. Transaction Logs-only Backups are lighter-weight backups that are intended to capture any new activity since the last Full Backup was performed. This can radically reduce the backup time and storage requirements for large databases, but introduces dependencies on one or more prior backups to perform a complete restore.
Important: VSS based backups for non-Continuous Replication environments will truncate the transaction logs at the completion of Full or Transaction Logs Only Backups. In Continuous Replication (LCR and CCR) environments, log truncation will be delayed by the Microsoft Exchange Replication Service until all
necessary log files are replayed into the replica copy. Microsoft Exchange Replication Service will delete the backed up log files both from the active and the passive copy log file paths after it verifies that the to-be-deleted log files have successfully been applied to the passive copy database and both the active and passive copy database check points have passed the log files in question.
2.1.5 Backup Types
The Exchange Server APM provides eight essential backup types:
Full Copy Incremental Differential
A Full Backup is the most common type of backup performed. It is used to perform a complete backup of a database or Storage Group. A Full Backup does not depend on any other backup and can be restored in a single step.
A Full Backup includes all files and performs transaction log file truncation. Perform regular Full Backups to keep the Exchange Server in good health and maintain its performance.
2.1.5.b Copy Backup Type
Sometimes a backup must be taken for a special purpose and should not affect the overall backup and restore procedures for the Exchange Information Store. A Copy Backup is used to backup all database files without performing transaction log file truncation. This provides a snapshot of the files as they existed at the time of the backup. A Copy Backup should be used to perform a fast, non-intrusive complete backup of an Exchange Server and is common in scaling and migration scenarios.
As a Copy Backup does not perform transaction log file truncation, the disk footprint of the Exchange Server does not change as a result of the backup. Consequently, a Copy Backup does not perform any housekeeping measures, and therefore does not maintain the performance of the Exchange Server in any way. Copy Backups should not be considered as a part of a regular backup policy, but as a special-purpose type of backup.
2.1.5.c Incremental Backup Type
Incremental Backups perform backups of the transaction log files that capture the changes made to the database since the most recent Full or Incremental Backup. The transaction logs are then truncated which assists in the proper maintenance of the Exchange Server Mailbox Databases. Incremental Backups are generally very fast and correspondingly small.
As a Transaction Logs-only Backup, an Incremental Backup must always have a “base” backup, which is often a Full Backup. Performing an Incremental Backup without first performing a Full Backup may lead to backup failures, in addition to an inability to restore and recover your Exchange Server properly.
An Incremental Backup should not be performed in the following conditions:
When an Initial Full Backup has Not Been Created – The transaction log
only contains changes made to the database after the last backup was created, thus a “base” backup is required.
Chapter 2 Strategy
16
permanently lost. At that point the transactions have already been deleted from the Exchange Server logs. Though the data still exists within the Exchange Server, errors would occur if you attempted to restore Incremental Backups that were created after a failed Incremental Backup job. This issue does not apply to a failed Incremental Backup that contains only a single Storage Group.
Important: If this an Incremental Backup containing multiple Storage Groups fails, a Full Backup should be performed immediately to prevent any potential data loss.
After the Transaction Log is Manually Truncated – In this case a Full or
Differential Backup must be performed before an Incremental Backup. Microsoft strongly recommends against manually truncating transaction logs.
2.1.5.d Differential Backup Type
Differential Backups perform backups of the transaction log files since the most recent Full or Incremental Backup. Differential Backups do not perform transaction log truncation, and therefore do not maintain the operating health of the Exchange Server.
Subsequent Differential Backups will increase not only in size, but also in duration because each backup of this type will include the transaction log files that were also included in the previous Differential Backup, as well as the transaction log files that have been generated since the previous Differential Backup. For example, if a Full Backup was taken on Sunday with Differential Backups scheduled Monday through Saturday, Monday's Differential will include the transaction log files generated since the Full Backup on Sunday, while Tuesday's Differential will include the transaction log files generated on Monday as well as those generated on Tuesday. Wednesday's Differential will include the transaction log files for Monday, Tuesday, and Wednesday, and so on.
As a Transaction Logs-only Backup, a Differential Backup must always have a “base” backup, which is often a Full Backup. Performing a Differential Backup without first performing a Full Backup may lead to backup failures in addition to an inability to restore and recover your Exchange Server properly.
When used in combination with Full Backups, Differential Backups provide acceptable tradeoffs with good backup performance, good restore performance, and reasonable overall database maintenance via the Full Backup.
2.1.5.e Incremental vs. Differential Backups
human intervention needed to initiate the multiple restore jobs.
Differential Backups do not truncate the transaction log files after they are backed up. Subsequent Differential Backups take increasing longer because all the transaction log files since the last Full Backup are included in the backup.
Nevertheless, restore sequences that utilize Differential Backups require that only one Differential Backup be restored after the Full Backup is restored. This results in quicker restores because less human intervention is required during the restore process.
Another consideration when deciding between Incremental and Differential Backups is the desired frequency of transaction log file truncation. When implementing Incremental Backups, the transaction log files will be truncated at the same frequency as the Incremental Backups.
For example, if Incremental Backups are performed on a daily basis, the transaction log files will be truncated on a daily basis. However, with Differential Backups, the transaction log files will be truncated only when a Full Backup is performed. Therefore, if the Full Backup is only performed weekly, the transaction log files will only be truncated weekly.
Implementing a Differential Strategy will lead to faster restores but will require more frequent Full Backups to maintain the operating health of the Exchange Server.
2.2.0 Example Backup Sequences
2.2.1 Full Backups Only
When business requirements define backup protection to the previous day, performing Full Backups nightly should be sufficient under the following conditions:
Backup windows are large After-hours email volume is low
Regular transaction log file truncation is required
2.2.2 Full + Incremental Backups
When business requirements guarantee data protection up to the previous day,
backup time should be as fast as possible, and regular transaction log file
truncation is required, Full Backups coupled with Incremental Backups is the best combination.
Chapter 2 Strategy
18
the previous night's backup whether it be the Sunday evening Full Backup or one of the Incremental Backups from a weekday.
It is important to remember that restoring this type of backup sequence will be more time-consuming. For example, if recovery is performed on Tuesday, only Sunday's Full Backup and Monday's Incremental Backup must be restored; whereas, if recovery is performed on Wednesday, Sunday's Full Backup followed by Monday's and Tuesday's Incremental Backups must be restored. Even though the backups are quicker, the restores can take longer due to the additional intervention that is required to execute multiple restore jobs.
2.2.3 Full + Differential Backups
When business requirements guarantee data protection up to the previous day,
restore and backup time should be reasonably fast, and only occasional
transaction log file truncation is required, Full Backups coupled with Differential Backups is the best combination.
For example, Full Backups are performed every Sunday night at 11:00 p.m. while Differential Backups are performed Monday through Saturday at 11:00 p.m. Each Differential Backup will include the transaction log files that were generated since the last Full Backup. This may require more overall backup time than an
Incremental Backup. Regardless of the point-in-time to which recovery is
D
EPLOYMENT
Deployment Overview
Standalone Deployment
Local Continuous Replication (LCR)
Single Copy Cluster (SCC) or Failover Cluster Cluster Continuous Replication (CCR)
3.1.0 Deployment Overview
Microsoft supports the deployment of Exchange Mailbox Server on either a single server or high-availability/clustered environment, including:
Local Continuous Replication (LCR)
Single Copy Cluster (SCC) or Failover Cluster
Cluster Continuous Replication (CCR)
Deploying the Exchange Server APM in each of these environments is almost identical in the fact the Exchange Server APM is installed on the server(s) that host the Exchange Server mailbox databases. The following sections detail how the Exchange Server APM is deployed in each the available type of Exchange Mailbox Server deployments.
3.2.0 Standalone Deployment
Supported Exchange Server Versions – All Supported Exchange Server Editions – All Supported Backup Methods – ESE and VSS
Chapter 3 Deployment
20
Figure 3-1: Standalone Deployment diagramImportant: Regardless of configuration environment in place (that is, separate NetVault: Backup Sever and Exchange Server, vs. a single machine configured as both), the Exchange Server APM must be installed on the host where Exchange Server mailbox databases reside. Example images and procedures throughout this guide assume that this two machine environment is in place and all configuration requirements have been met
3.3.0 Local Continuous Replication (LCR)
Supported Exchange Server Versions – 2007 Only
Supported Exchange Server Editions – All
Supported Backup Methods – ESE (Active Copy Only), VSS (Active or Passive Copy)
Local Continuous Replication (LCR) is a single Exchange Mailbox Server solution that uses built-in asynchronous log shipping technology to create and maintain a copy of a Storage Group on a second set of disks that are connected to the same server as the production Storage Group. LCR provides log shipping, log replay, and a quick manual switch to a secondary copy of the data. For more information, refer to Exchange 2007 Local Continuous Replication at:
http://technet.microsoft.com/en-us/library/bb125195.aspx
LCR Deployment diagram
3.4.0 Single Copy Cluster (SCC) or Failover Cluster
Supported Exchange Server Versions – All
Supported Exchange Server Editions – Enterprise Only Supported Backup Methods – ESE and VSS
Exchange Server APM License Required – Exchange Server APM
Enterprise Edition Cluster Support
Single Copy Cluster (SCC) or Failover Cluster is a clustered solution that uses a single copy of a Storage Group on storage that is shared between the nodes in the cluster. In an SCC deployment, the Exchange Server APM is aware of which node is the active node and will perform backups of the Active Copy of the Storage Groups. During the restore process, data is restored to the active node.
For additional information, refer to Understanding Exchange Server 2003 Clustering at:
Chapter 3 Deployment
22
For Exchange 2007 Single Copy Clusters, refer to:
http://technet.microsoft.com/en-us/library/bb125217.aspx
In an SCC deployment, the APM is installed on the Exchange Virtual Server, which is the group of nodes/hosts comprising the cluster and that are seen by the NetVault: Backup Server as a single client called a Virtual Client. When installing the APM on the Virtual Server, the APM is installed on all nodes via NetVault: Backup’s Cluster Support. NetVault: Backup’s Virtual Client is used to backup a single clustered resource, which in this example is the Exchange Virtual Server.
Figure 3-3:
Supported Exchange Server Versions – 2007 Only Supported Exchange Server Editions – Enterprise Only
Supported Backup Methods – ESE (Active Copy Only),
VSS (Active or Passive Copy)
Exchange Server APM License Required – Exchange Server APM Enterprise Edition Cluster Support
Cluster Continuous Replication (CCR) is a clustered solution that uses built-in asynchronous log shipping technology to create and maintain a copy of each Storage Group on a second server in a failover cluster. CCR is designed to be either a one or two data center solution, providing both high availability and site resilience. According to Microsoft, CCR uses the database failure recovery functionality in Exchange 2007 to enable the continuous and asynchronous updating of a second copy of a database with the changes that have been made to the active copy of the database. During installation of the passive node in a CCR environment, each Storage Group and its database is copied from the active node to the passive node. This operation is called seeding, and it provides a baseline of the database for replication. After the initial seeding is performed, log copying and replay are performed continuously. For more information, refer to: Exchange 2007 Cluster Continuous Replication at:
http://technet.microsoft.com/en-us/library/bb124521.aspx
I
NSTALLATION
Pre-Installation Requirements
Disabling Circular Logging Enabling Services
Configuring Localization Settings Enabling Deleted Item Recovery
Installation Procedure for Standalone and LCR Deployments
Installation Procedure for SCC/Failover Cluster and CCR Deployments
Pre-Installation Requirements Installation Procedure
Removing Exchange Server APM
4.1.0 Pre-Installation Requirements
Before installing the Exchange Server APM, ensure the following requirements are met on the machine that is to serve as the Exchange Server:
4.1.1 Disabling Circular Logging
If either an Incremental or Differential Backup type is to be created, ensure that Circular Logging is disabled. The Exchange Server will overwrite files if Circular Logging is enabled, making it impossible to reliably restore from the transaction logs. For more information on Backup Types see Backup Typeson page 14. Follow these steps to disable Circular Logging:
Disabling Circular Logging in Exchange 2000/2003
1. Open Exchange System Manager.
2. Expand Servers, and then expand an Exchange Server.
3. Right-click the desired Storage Group and select Properties. The Storage Group properties dialog box will appear.
4. Deselect the Enable circular logging check box, and then click OK to save the changes.
Chapter 4 Installation
26
Complete instructions for this procedure can be found in the relevant Microsoft Exchange 2000 and Exchange 2003 documentation. For more information, refer to Circular Logging is Disabled at:
http://technet.microsoft.com/en-us/library/842c428a-9cc2-4a3c-b9df-bf40c2f2727a.aspx
Disabling Circular Logging in Exchange 2007
1. Open Exchange Management Console.
2. Expand Server Configuration and expand the desired server.
3. Right-click the desired Storage Group and select Properties. The Storage Group properties dialog box will appear.
4. In the Properties dialog box, deselect the Enable circular logging check box.
5. Click OK to save the setting.
6. Close Exchange Management Console and restart the Microsoft Exchange Information Store service for the change to take effect. Complete instructions for this procedure can be found in the relevant Microsoft Exchange 2007 documentation. For more information, refer to How to Enable or Disable Circular Logging for a Storage Group at:
http://technet.microsoft.com/en-us/library/bb331968.aspx
4.1.2 Enabling Services
Verify that the following Services are enabled and running Windows Control Panel > Administrative > Services for the Exchange Mailbox Servers:
Microsoft Exchange Information Store Microsoft Exchange System Attendant
Microsoft Exchange Replication Service (Required in LCR and CCR
Environments)
Required for VSS Backups
Microsoft Software Shadow Copy Provider
Volume Shadow Copy (Started automatically by Microsoft Software Shadow
Copy Provider)
The Exchange VSS Writer is disabled automatically in a Small Business Server installation. This VSS Writer must be enabled prior to performing VSS based backups, or they will fail. For more information, refer to How to turn on the
Exchange writer for the Volume Shadow Copy service in Windows Small Business Server at:
The Exchange Server APM uses traditional Windows code page selection to enable localization, and is therefore subject to certain limitations. The Exchange Server APM must be used in an environment with correctly configured
localizations settings to function properly.
Figure 4-1: Advanced tab of the Regional and Language Options window where the Windows Active Code Page is configured
To ensure correct operation in a localized environment, all of the following conditions must be met:
All Exchange Server entities (Storage Groups, Mailbox Stores, Public Folder Stores, and so on) must be named using the same language, with no intermixing of languages.
The Windows Active Code
Page must be set to exactly the same language as used in the Exchange Server.
The language specified in the NetVault: Backup Configurator for both the NetVault: Backup Server and Client(s) must match the language set in the Windows Active Code Page.
If used in a clustered environment, all nodes in the cluster must be configured
to use the same language, also conforming to the previous rules.
Follow the steps below to correctly configure the Windows Active Code Page: 1. Open the Windows Control Panel.
2. Select Regional and Language Options. 3. Select the Advanced tab.
4. Select the correct language in the drop-down menu under the text Select a language to match the language version of the non-Unicode programs you want to use.
If the correct language is not available in the list, it must be installed by following the Microsoft Windows administrative procedures for installing additional language support.
Chapter 4 Installation
28
Figure 4-2: General tab of the NetVault Configurator with the Language Selection drop-down menu selected1. Open the NetVault Configurator. 2. Select the General tab.
3. Scroll to the bottom of the General tab and locate the Language Selection field. 4. Access the drop-down menu and
select the desired language.
5. Select the OK button to save the changes.
Important: When non-English languages are used in an environment that is not correctly configured, backup and restore operations may not function as expected. The demonstrated behavior may include, but is not limited to:
– Failure to backup selected items.
– Backing up or restoring items that were not selected (for example, you select the first Storage Group, but second Storage Group is affected).
– Failure to backup or restore altogether, often with the indication that no matching items were found.
4.1.4 Enabling Deleted Item Recovery
BakBone recommends that the Deleted Item Recovery functionality be enabled in Exchange to reduce the need to perform recovery for individual messages or mailboxes. This feature enables the recovery of recently deleted items by saving messages for a predetermined number of days. Follow these steps to enable Deleted Item Recovery:
Enabling Deleted Item Recovery
1. Open the Exchange Management Console or Exchange System Manager.
2. In the console tree, expand Microsoft Exchange, expand Server Configuration, and then select Mailbox Store.
3. Right-click the database and select Properties. 4. Select the Limits tab.
5. In the Deletion settings area, enter the number of days to retain deleted items in the Keep deleted item for (days) field.
6. Click OK to save the changes.
7. To recover deleted items on the client, select the Deleted Items folder, and on the Tools menu, select Recover Deleted Items, and select the items from the list presented. Select Recover selected items to have the items restored to your Deleted Items folder.
Deleted Item at:
http://technet.microsoft.com/en-us/library/aa997155.aspx
4.2.0 Installation Procedure for Standalone and LCR
Deployments
Use the following steps to successfully install the Exchange Server APM. 1. From the machine acting as the NetVault: Backup Server, launch the NVBU
Console and access the Client Management window by clicking either of the Client Management buttons on the command toolbar (or select the Client Management command from the Administration pull-down menu).
Figure 4-3: Clients pop-up menu with Install Software selected
2. Locate the machine configured as the Exchange Server in the Clients frame and right-click it. Select the Install Software command from the pop-up menu.
3. In the additional window that appears, navigate to the location of the “.npk” installation file for the Exchange Server APM (for example, the NetVault: Backup APM Installation CD or the directory to which the file was
downloaded from BakBone Software’s web site). Based on the operating system in use, the directory path for this software may vary on the installation CD.
Chapter 4 Installation
30
5. The installation process will occur automatically, and after it has completed, a successful installation message will appear in the Install Software dialog box. The Exchange Server APM is now successfully installed.
Installation and removal of the Exchange Server APM can also be performed via the NetVault Configurator. For more information, refer to the Packages Tab section in the NetVault: Backup Configurator Guide.
4.3.0 Installation Procedure for SCC/Failover Cluster
and CCR Deployments
4.3.1 Pre-Installation Requirements
The following prerequisites must be met before it is possible to install the Exchange Server APM in a SCC/ Failover Cluster or CCR deployment:
Microsoft Exchange SCC or CCR Environment in Place – You must have
a properly configured SCC or CCR environment. SCC and CCR are only supported with Exchange Server Enterprise Edition.
Separate NetVault: Backup Server Machine – The machine that is to serve
as the NetVault: Backup Server must be properly configured and it must
exist outside the Exchange Server SCC or CCR deployment, but have
network connectivity to the nodes/hosts within the cluster.
NetVault: Backup’s Encryption Plugin Must Be Disabled for NVBU v8.2.2
and Earlier – NetVault: Backup Encryption Plugin distributed with NVBU v8.2.2 and earlier is not supported in an Exchange Server SCC/Failover Cluster or CCR environment and must be disabled. Refer to NetVault: Backup Administrator’s Guide for details on disabling this functionality.
Review Using NetVault: Backup in Cluster Setup Details – BakBone strongly recommends that the Using NetVault: Backup in Cluster Setup chapter of the NetVault: Backup Administrators Guide be thoroughly
reviewed to obtain a better understanding of how the information presented in the following sections work in conjunction with Exchange Server SCC and CCR functionality.
4.3.2 Installation Procedure
of the selected nodes.
4.3.2.a Creating a Virtual Client
The Virtual Client creation process is not APM specific and complete details can be found in the Using NetVault: Backup in Cluster Setup chapter of the NetVault: Backup Administrators Guide. However, a couple of points should be taken into consideration during the Virtual Client creation process:
Only Include Relevant Cluster Nodes in the Virtual Client – The hosts that
are to be included in the creation of a Virtual Client should only be those nodes or Exchange Mailbox Servers which comprise the SCC or CCR deployment. During the creation of the Virtual Client, you can specify either the IP address of the Exchange virtual cluster or the name of the Exchange virtual cluster. After the creation of the Virtual Client, the APM is transferred to all designated cluster nodes and installed locally. The installed Exchange Server APM can be used via the Virtual Client to backup/restore the SCC or CCR deployment. Figure 4-4: Virtual Client Installation Window with relevant Cluster nodes selected
Assign a Name to the Virtual Client – BakBone highly recommends that the
Virtual Server network name assigned to the Exchange Server be used as the NetVault: Backup Virtual Client name. When a Virtual Client is browsed, NetVault: Backup will locate the node currently in control of the clustered application, and reveal the Exchange Server Instance (for example, in the Selections tab of the Backup window). With a Virtual Client name set up as the Exchange Server Virtual Server network name, it will be easy to
Chapter 4 Installation
32
Figure 4-5: NetVault: Backup with Selections tab revealing Exchange Server Virtual Server4.4.0 Removing Exchange Server APM
Use the steps that follow to remove this APM in a Standalone deployment: 1. In the Client Management window, locate the machine in the Clients frame
housing the Exchange Server APM (that is, the one configured as the Exchange Server).
2. Right-click this machine and select the Remove Software command from the pop-up menu. The Remove Software window will be displayed.
3. In the list of installed plugins that is displayed, locate the Exchange Server Application Plugin Module item and select it
Figure 4-6:
Remove Software Window
4. Click the Remove button to begin the software removal process.
Administrator’s Guide for details on removing the Exchange Server APM in an SCC or CCR deployment.
Chapter 4 Installation
C
ONFIGURATION
Configuring Exchange Server APM
Required Windows User Account Permissions Configuration Process
Specifying Default Configuration (Optional) About Window
5.1.0 Configuring Exchange Server APM
Before initiating a backup, you must configure the Exchange Server APM Authentication Details and select the Backup Method.
5.1.1 Required Windows User Account Permissions
The Exchange Server APM uses Windows Authentication to provide essential security and access control for sensitive data contained in an Exchange Server's databases. Windows Authentication allows you to log on to a specified Windows user account. This Windows user account can be configured to restrict a user’s privileges so that only backups may be performed, or can allow both backups and restores to be performed, depending on what permissions are allocated to the account.
5.1.1.a Required Windows User Account Permissions
For a user to perform a backup of Exchange, the Windows user account used must:
Be a valid domain or local account.
Be a member of the Power Users Group.
Be a member of the domain’s Backup Operator’s Group (for Domain accounts).
Be a member of the Backup Operator’s Group on the machine that Exchange
is running on.
To perform a restore of Exchange, the Windows user account must:
Be a valid domain or local account. Be a member of the Power Users Group.
Be a member of the domain’s Backup Operator’s Group (for Domain
Chapter 5 Configuration
36
Be a member of the Backup Operator’s Group on the machine that Exchange
is running on.
Be a member of the Administrators Group on the machine that Exchange is
running on.
The Domain Administrator account will have all the permissions necessary to perform backup and restore procedures in the Exchange Server APM by default. Note: The NetVault Process Manager Service Log on as: account must be a Local System or an Exchange Administrator Account.
5.1.2 Configuration Process
1. From the NVBU Console running on the NetVault: Backup Server, open the Backup window (via either of the buttons offered on the command toolbars, or by using the Backup command in the Operations pull-down menu). A list of NetVault: Backup Clients will be displayed in the Selections tab.
2. Locate the Client configured as the Exchange Server, and open it to display a list of APMs/plugins installed on the machine.
3. To open any node in the Selections tab, you can do either of the following:
Double-click the node, or
Right-click the node and Select the Open command from the pop-up
menu
4. Next, locate the Exchange Server APM node in the list.
Figure 5-1: Exchange Server pop-up menu with Configure selected
5. Right-click and select the Configure command from the pop-up menu. The Exchange Server
Configuration window is displayed. The Server Name field displays the machine name of the
Exchange Server. This field cannot be edited. 6. Select Server Role from the drop-down menu:
Standalone Server
Local Continuous Replication (LCR) Single Copy Cluster (SCC)
Server 2007 Configuration window
7. From within the Backup Method frame, select the default Backup Method to be used for this Exchange Mailbox Server.
The Exchange Server APM supports the following types of backup methods:
Extensible Storage Engine (ESE)
Volume Shadow Copy Service (VSS)
The Backup Method will default to the Backup Method selected in the Exchange Server APM Configuration Window.
The Exchange Server APM supports implementing an ESE or a pure VSS backup strategy; that is, your backup strategy should include either ESE backups or VSS backups, not a combination of the two. Refer to the chapter
Strategyon page 11 for more details on selecting the backup method for your Exchange Server backup strategy.
8. Edit the following fields in the Exchange Authentication Details frame:
Exchange Administrator User Name – Enter either a local or domain
Windows account that meets the criteria specified in Required Windows User Account Permissionson page 35.
Chapter 5 Configuration
38
Windows Domain – If a domain account is specified in the Exchange
Administrator User Name field, enter the name of the domain. The field can be left blank if a local system account is specified.
9. From the Advanced Options frame, select the default action for Incomplete Backup of ALL Items Selected.
When multiple items are included in a backup, and the APM is unable to successfully backup all the items selected, the Exchange Server APM lets you specify what action the backup should take. For example, if a job includes multiple Storage Groups selected and the backup of all but one of the Storage Groups selected is successful, then you specify what action the backup job should take in this situation.
The default action for all Exchange Server APM Backup jobs can be set by selecting one of the following four settings from the drop-list. The default action selected can be overridden at the individual backup job level.
Complete with Warnings - Saveset Retained – This backup job status is set to Backup Completed with Warnings. The backup of the items which were successfully completed is retained as a saveset.
Complete without Warnings - Saveset Retained – This backup job
status is set to Backup Completed. The backup of the items which were successfully completed is retained as a saveset.
Fail - Saveset Retained - This backup job status is set to Backup Failed. The backup of the items which were successfully completed is retained as a saveset.
Fail - No Saveset Retained - This backup job status is set to Backup
Failed. The backup of the items which were successfully completed is not retained as a saveset.
The Exchange Server APM provides the ability to set default options for backup and restore jobs. These options can be overwritten on a per job basis. The default options can be set via the NetVault: Backup Configurator. The steps to set these default options are outlined below:
1. Open the NVBU Configurator.
2. The Configurator window will appear. Click the Plugin Options tab. 3. Click the Exchange Server APM tab, where the following options will be
displayed:
Exchange Administrator User Name – Specify either a local or domain Windows account to set as the default account. When the Exchange Server Configuration window is opened, this account will appear by default in the Exchange Administrator User Name field.
Windows Domain – If a domain Windows account is specified in the
Exchange Administrator User Name field, enter the name of the domain. When the Exchange Server Configuration window is opened, this domain will appear by default in the Windows Domain field. This field can be left blank if a local system account is specified.
Figure 5-3: Exchange Server APM default configuration options in NVBU Configurator
Chapter 5 Configuration
40
5.2.0 About Window
The About window shows you the software version. You can access this window from the Backup Selections tab by using the following steps:
Figure 5-4:
Exchange Server APM About window
1. Launch the NVBU Console on the NetVault: Backup Server and access the Backup window (via either of the buttons offered on the command toolbars, or by using the Backup command in the Operations pull-down menu). A list of machines successfully added as NetVault: Backup Clients will be displayed in the Selections tab.
2. Locate the NVBU Client configured as the Exchange Server, and open it to display a list of APMs/plugins installed on the machine.
3. Locate the Exchange Server APM in the list and right-click it. 4. Select About from the pop-up menu.
B
ACKUP
Performing Backups with Exchange Server
Selecting Data for a Backup Setting Backup Options
Finalizing and Submitting the Job
6.1.0 Performing Backups with Exchange Server
A backup using Exchange Server APM in Exchange Server can be divided into the following phases: Selecting Data for a Backup
Setting Backup Options
Finalizing and Submitting the Job
6.1.1 Selecting Data for a Backup
1. Launch the NVBU Console on the NetVault: Backup Server and access the Backup window via either of the buttons offered on the command toolbars, or by using the Backup command in the Operations pull-down menu. A list of machines successfully added as NetVault: Backup Clients will be displayed in the Selections tab.
2. Locate the NVBU Client configured as the Exchange Server, and open it to display a list of APMs/plugins installed on the machine.
3. To open any node in the Selections tab, you can do either of the following:
Double-click the node.
Right-click the node, and select the Open command from the pop-up
Chapter 6 Backup
42
Figure 6-1: Exchange Server APM is opened to display items available for inclusion in a backup job4. Next, locate the Exchange Server APM node in the list and drill down to the name of the
Exchange Server or Exchange Virtual Server and its available Information Stores.
5. Expand the desired Microsoft
Information Store to
display all of the Storage Groups contained within. It is also possible to open an individual group to display all of the databases contained within that group. 6. Select data as desired for backup by clicking the box to the left of that item
(that is, to mark it with a green check). It is possible to select groups as follows:
Entire Exchange Server
Entire Microsoft Information Store
Individual Storage Groups Sets of Storage Groups
Individual Databases Groups of Databases
Selecting the Microsoft Exchange Server node is equivalent to selecting the Exchange Server or Virtual Server Node, in that the entire Exchange Server will be backed up. However, selecting the Microsoft Exchange Server node will enable creating a selection set that can be used across multiple Exchange Server APMs.
Important:
1. Backing up individual databases may affect the behavior of log truncation for all databases in the Storage Group. This may result in excess log files in the backup, premature truncation of log files, or deferred truncation of log files depending on the conditions in your environment and the Exchange Server version (including patches) in use.
A Selection Set allows you to save the frequently selected data items in a composite set, which can be easily accessed for future backup jobs. This
eliminates the need to manually select these items each time a backup is required. Moreover, BakBone highly recommends Selection Sets for Differential and Incremental Backups. If your backup strategy includes these backup types, you should create a Selection Set when making a Full Backup, and use this Selection Set for the Full Backup as well as the Differential and/or Incremental Backups. The backup job will complete with warnings if a Selection Set is not used for Differential and Incremental Backups. Because the Exchange Server APM uses Selection Sets to ensure Incremental Backups are restored in order, failing to use selection sets will prevent the APM from being able to perform this
validation.
Creating a Selection Set
To create a Selection Set, do the following:
1. With the desired items selected, click the Save As button in the Backup Selection Set frame at the bottom of the Selections window.
2. In the Save Backup Selection Set window that appears, enter a unique name for the Selection Set.
3. Click OK.
Loading a Selection Set
To use a Selection Set, follow the steps below:
1. Click the Load button in the Backup Selection Set frame at the bottom of the Selections window.
2. In the Load Backup Selection Set window that appears, select the required set.
3. Click OK.
Selection Sets are not unique to the Exchange Server APM. For details on their creation and use, refer to the NetVault: Backup Administrator’s Guide.
6.1.2 Setting Backup Options
The next phase in the backup procedure involves the following tasks:
Selecting Backup Method
Specifying Backup Type Setting Advanced Options
Chapter 6 Backup
44
Figure 6-2: Options available in the Backup Options tab for Exchange Server6.1.2.a Selecting Backup Method
The Exchange Server APM supports the following types of backup methods:
Extensible Storage Engine (ESE) Volume Shadow Copy Service (VSS)
The Backup Method will default to the Default Backup Method selected in the Exchange Server APM Configuration window.
The Exchange Server APM supports implementing an ESE or a pure VSS backup strategy; that is, your backup strategy should include either ESE backups or VSS backups, not a combination of the two. Refer to the chapter Strategyon page 11 for more details on selecting the backup method for your Exchange Server backup strategy.
6.1.2.b Specifying Backup Type
The Exchange Server APM provides the following types of backups for use with Exchange Server. Refer to the section Backup Typeson page 14 for more information on each supported backup type.
Full – A Full Backup performs a complete backup of the set of items that
have been selected. A Full Backup does not depend on any other backup and can be restored in a single step. A Full Backup includes all files and performs transaction log file truncation.
Copy – A Copy Backup backs up the set of items that have been selected
be used to perform a fast, non-intrusive complete backup of an Exchange Server and is commonly used for offline scaling and migration scenarios.
Incremental – Incremental Backups perform backups of the transaction log
files of the set of items that have been selected since the most recent Full Backup or Incremental Backup. After the backup is complete, the transaction logs will be truncated. This helps maintain the operating health of the
Exchange Server.
Differential – A Differential Backup performs backups of the transaction log files of the set of items that have been selected since the most recent Full Backup or Incremental Backup. Differential Backups do not perform
transaction log truncation, and therefore do not maintain the operating health of the Exchange Server.
6.1.2.c Setting Advanced Options
The Exchange Server APM allows you to set certain additional options for the backup job, such as specifying the number of parallel streams to be used in a backup and whether to mount any unmounted databases before attempting to backup the database. You can set these options from the Advanced Options frame. This frame contains the following options:
Maximum Number of Parallel Streams – To enable the fastest backups possible, the Exchange Server APM uses parallel streams to backup the Storage Groups simultaneously. This option allows you to specify the maximum number of parallel streams to use during a backup. The maximum number of parallel streams must meet both of the following conditions:
Less than or equal (<=) to the number of drives for the backup devices specified in the Target window.
Less than Maximum number of Storage Groups that can be created. The
following table details the maximum number of Storage Groups allowed by each Exchange Server version/edition:
For example, if you are targeting a Virtual Tape Library configured with 2 drives and you have 20 Storage Groups, the Maximum Number of Parallel Streams should be 2 or less.
Exchange Server Method Server Edition Maximum Number of Storage Groups
Exchange Server 2000/2003 Standard 1
Enterprise 4
Exchange Server 2007 Standard 5
Chapter 6 Backup
46
Mount Unmounted Databases Before Backup – This option will mount any
unmounted databases before attempting to backup the database.
Incomplete Backup of ALL Items Selected – When multiple items are included in a backup, and the APM is unable to successfully backup all the items selected, the Exchange Server APM lets you specify what action the backup should take. For example, if a job includes multiple Storage Groups selected and the backup of all but one of the Storage Groups selected is successful, then you specify what action the backup job should take in this situation. The action for the backup job can be set by selecting one of the following four settings from the drop-list.
Complete with Warnings - Saveset Retained – This backup job status is set to Backup Completed with Warnings. The backup of the items which were successfully completed is retained as a saveset.
Complete without Warnings - Saveset Retained – This backup job status
is set to Backup Completed. The backup of the items which were successfully completed is retained as a saveset.
Fail - Saveset Retained - This backup job status is set to Backup Failed. The backup of the items which were successfully completed is retained as a saveset.
Fail - No Saveset Retained - This backup job status is set to Backup Failed.
The backup of the items which were successfully completed is not retained as a saveset.
6.1.2.d Setting VSS Backup Options
When performing VSS based backups in an LCR or CCR environment, the Exchange Server APM is able to perform backups on either the active copy or passive copy of the Exchange Server data. By enabling backups of the passive copy, the load on the active node is reduced. This frame contains the following options:
Active Copy – Select this option to backup the active copy of all Storage Groups. This is the default option for Standalone deployments, and the only option available for SCC/Failover Cluster deployments or deployments that have Standby Continuous Replication (SCR) enabled for any of the Storage Groups.
Passive Copy – Select this option to backup the passive copy of all Storage
Groups. While available for both CCR and LCR deployments, this option is the default option for CCR deployments and has the following restrictions:
If selecting this option for LCR deployments, backups will be performed only for Storage Groups that have LCR enabled. Storage Groups that do not have LCR enabled will not be backed up.
If Standby Continuous Replication (SCR) is enabled for any of the Storage
passive copy.
When performing backups of passive data, it is important to ensure that
the passive copies in CCR and LCR environments have a state of Healthy in the Exchange Management Console. If the passive copy has a status of Failed, the backup will fail. The Failed passive copy can be returned to a Healthy state by deleting it and updating it with the StorageGroupCopy command. For more information on the Update-StorageGroupCopy command refer to:
http://technet.microsoft.com/en-us/library/aa998853.aspx
Mixed (Available only for LCR deployments) – Selecting this option will
backup the passive copies of all Storage Groups along with active copy Storage Groups that are not LCR enabled. This is the default and the recommended option for LCR deployments that do not have Standby Continuous Replication (SCR) enabled, and has the following restriction:
If SCR is enabled for any of the Storage Groups, selecting this option will cause the backups to fail. The Active Copy option should be selected for environments where LCR and SCR are simultaneously deployed.
6.1.3 Finalizing and Submitting the Job
With the desired data items selected and the necessary Backup Options set, follow the steps below to finalize the backup job and submit it:
1. Set the additional options that are available in the Schedule, Target, and Advanced Options, as required. These options are not unique to the Exchange Server APM. For information on these tabs and the options within, refer to the NetVault: Backup Administrator’s Guide.
2. Enter a suitable name for the job in the Job Title field. Specify a detailed name that allows you to easily identify the job for monitoring its progress or restoring data.
3. Click the Submit button.
Chapter 6 Backup
R
ESTORE
Restoring Data with the Exchange Server APM
Understanding Exchange Server Restore Process Restore Methods Available
Phases of a Restore
Restoring Backups in Exchange Server
Preparing Exchange Server for Recovery Selecting Data for Restore
Setting Restore Options
Finalizing and Submitting Restore Job
Performing Post Restore Steps for CCR Environments Performing Post Restore Steps and SCR Environments
Example Restore Sequences Advanced Restore Procedures
Renaming Storage Groups
Moving Databases to Alternate Storage Group
Restoring Data to Recovery Storage Group Disaster Recovery of Exchange Server
Recovering to Alternate Exchange Server
7.1.0 Restoring Data with the Exchange Server APM
This chapter offers basic instructions on the use of the Exchange Server APM to restore and recover Exchange Server databases. The information in this chapter is organized into the following sections: Understanding Exchange Server Restore Process
Restoring Backups in Exchange Server Other Restore Procedures
