Exchange Data Protection: To the DAG and Beyond. Whitepaper by Brien Posey
|
|
- Johnathan Page
- 8 years ago
- Views:
Transcription
1 Exchange Data Protection: To the DAG and Beyond Whitepaper by Brien Posey
2 Exchange is Mission Critical Ask a network administrator to name their most mission critical applications and Exchange Server is almost certain to be near the top of the list. Exchange admins know all too well that Exchange servers store more than just messages. Users also use Exchange to store customer contact data and appointments for client meetings. To make a long story short, even a brief Exchange Server outage can have a significant impact on the organization s bottom line. Users might for example miss an important appointment or be unable to respond to a message from a potential customer in a timely manner. As such, it has become critically important for Exchange Admins to keep Exchange Server up and running. Fortunately Microsoft also understands the importance of keeping Exchange Server online and has designed Exchange Server 2010 in a way that allows it to be configured for resilience to failure. The primary feature for mailbox server resilience is Database Availability Groups (DAGs). Built-in High Availability: Microsoft Exchange DAGs DAGs are designed to be a next generation replacement for the continuous replication features that were found in Exchange Server Although DAGs do have a few things in common with Exchange 2007 s continuous replication, there are some important differences. For instance, in Exchange 2007, administrators were forced to choose the type of continuous replication that they wanted to use (local continuous replication, cluster continuous replication, or standby continuous replication). In Exchange 2010, DAGs are the only high availability solution for mailbox servers. There are no longer multiple continuous replication models to choose from. DAG Benefits DAGs use failover clustering to make Exchange 2010 mailbox databases highly available. Prior to the release of Exchange Server 2010, mailbox databases were considered to be server level objects. In Exchange Server 2010 however, mailbox databases become an organizational level feature, which means that a mailbox database can reside on any Exchange 2010 mailbox server within the organization. DAGs build on the concept by allowing mailbox databases to be replicated to multiple mailbox servers. A DAG can consist of up to sixteen Exchange 2010 mailbox servers. Each DAG member can contain a mixture of active and passive mailbox databases. Mailbox databases can be replicated to other DAG members on an as needed basis. Replica databases can be mixed and matched on the DAG members. It is not necessary to replicate a mailbox database to every DAG member. The Exchange administrator is free to pick and choose which mailbox databases will be replicated and where those replicas will reside. DAGs ensure mailbox database resiliency by allowing a mailbox database to automatically fail over to another DAG member in the event that the server that was hosting the active copy of the database fails. Although this type of resilience is critical to many organizations, DAGs have another capability that is often equally appealing. Exchange Server 2010 makes it possible to create a stretched DAG that spans multiple datacenters. Stretched DAGs make it possible to replicate mailbox databases to remote
3 datacenters for safe keeping. These remote replicas can be activated in the event that the primary datacenter experiences a catastrophic failure. DAG Limitations In spite of all of their promise, DAGs are not without limitation. DAGs tend to work extremely well so long as they are confined to a local datacenter, however stretched DAGs require very careful planning. All too often organizations invest in Exchange Server 2010 with the intention of building a stretched DAG, only to discover that their existing network infrastructure rules out the possibility of creating such a structure. The factors with the greatest impact on an organization s ability to create a stretched DAG are network latency and Active Directory structure. Microsoft only supports the use of DAGs on networks with a round trip latency of 500 milliseconds or less. Often times this limit prohibits organizations from passing DAG traffic across a WAN link. The Active Directory structure can also impact an organization s ability to create a stretched DAG. DAG members must all belong to a common domain. Many organizations use a separate domain (or domain hierarchy) for each physical location. For instance, an organization might use one domain name for the Miami office and another domain name for the office in Las Vegas. This domain naming convention would prohibit the use of a stretched DAG between the two facilities. Stretched DAGs can only be used if the Active Directory domain also spans the physical locations. Even though network latency and Active Directory structure tend to be the greatest barriers to creating a stretched DAG, they are far from being the only limitations. Microsoft has a very strict set of requirements that must be adhered to when creating a DAG. First off, DAGs can only be comprised of Exchange 2010 mailbox servers. Servers that are running earlier versions of Exchange cannot take part in a DAG. Likewise, DAGs can only be used with native Exchange 2010 mailbox databases. This requirement carries a couple of implications. First, it means that public folder databases are not supported. If an organization wants to provide high available for public folders, they will have to use the public folder replication feature. The other implication to the native Exchange 2010 database requirement is that DAGs cannot be used with Exchange 2007 databases. For example, an organization cannot build a DAG and then copy the database from an Exchange 2007 mailbox server to a DAG member and mount the database. In addition to meeting the requirements that Microsoft has established for DAGs, there is a lot of careful planning that must go into the DAG creation process. DAGs are relatively easy to deploy, but without careful planning a DAG might not provide the level of protection that would be expected. When an organization creates a DAG, they are creating a Majority Node Set (MNS) failover cluster (The Node and File Share Majority model is used for DAGs with an even number of members). An MNS cluster can only function if the cluster is able to maintain quorum, which means that more than half of the DAG members are functional and responsive. Because more than half (technically half plus one) of the DAG members must be functional in order for the cluster to retain quorum, a DAG cannot contain less than three servers. If a DAG
4 consisted of only two servers then the failure of a single DAG member would cause the cluster to lose quorum. Of course there are hardware and licensing costs associated with deploying DAG members. Smaller organizations may want the benefits of a DAG, but might lack the financial ability to create a three member DAG. In these types of situations it is possible to create a DAG consisting of two DAG members and a witness server. The witness server is simply a server with a dedicated file share that takes the place of a third DAG member. Exchange mailbox databases cannot fail over to the witness server, but the witness server can prevent the DAG from losing quorum in the event of a DAG member failure. It might at first seem that the concept of making sure that DAGs are able to maintain quorum are only a concern for smaller organizations. However, this concept can be just as important in larger organizations, especially when stretched DAGs come into the picture. The main problem with stretched DAGs is that if the WAN link between datacenters were to fail, Exchange would interpret the network failure as a failure of any DAG members residing on the other side of the link. This means that an organization must design their DAG so that there are enough DAG members residing in the primary datacenter that the primary datacenter will always be able to retain quorum even if a WAN failure occurs. This means placing more than half of the DAG members in the primary datacenter. While this concept probably seems straightforward, there are a few things to consider. First, any time that additional DAG members are added to a remote office, the addition of the new server impacts the number of DAG members that must remain online in order to retain quorum. As such, adding an Exchange mailbox server to a remote site might also require a mailbox server to be added to the primary datacenter as well in order to ensure that the primary datacenter is always able to maintain quorum. Needless to say, this approach can be expensive and it can also be difficult to work within Exchange Server s limitations since the DAG cannot exceed sixteen members. Another consideration is that the primary datacenter might actually need more than the minimum number of DAG servers required to maintain quorum. The primary datacenter can theoretically maintain quorum if more than half of the DAG members reside in the physical datacenter. However, if a WAN failure and the failure of a DAG member at the primary datacenter occurred simultaneously then the primary datacenter would lose quorum unless the datacenter contained enough DAG members to absorb the loss. One big problem with this scenario is that if a WAN failure did occur and the primary datacenter retained quorum then the remote datacenter would lose quorum, which would mean an outage for users working in the remote datacenter. The only way to avoid this type of situation using native Exchange Server components is to create multiple DAGs. However, each mailbox server can only belong to a single DAG, so this approach can become quite expensive. So what about the failure of an individual DAG member within a stretched DAG? By default, when a DAG member fails the databases can failover to any other DAG member with a suitable database replica. This is concerning in a stretched DAG because it is generally undesirable to have a failover occur across a WAN link. Microsoft allows you to prevent cross site failovers by setting the DatabaseCopyAutoActivationPolicy to Blocked. Of course this also means that if a situation ever occurs in which a cross site failover is needed then the Exchange administrator will have to work through a manual procedure to facilitate the failover.
5 Database Availability Groups work really well as a fault tolerant solution in a single datacenter environment. However, stretched DAGs can be expensive and complex to implement, and may not fully address all of an organization s needs. Considering DAG Lagged Copies Consultants and other commentators often consider the use of a lagged database copy within a DAG for Exchange 2010 deployments. Typically, once there is more than two passive database copies, thoughts turn to the creation of a lagged copy to provide the ability for a point in time recovery should the need arise. A lagged database copy is one that is not updated by replaying transactions as they become available. Instead, the transaction logs are kept for a certain period and are then replayed. The lagged database copy is therefore maintained at a certain point relative to the active database and the other non-lagged database copies. The primary reason to use lagged database copies (7 or 14 days for example) is to provide you with the ability to go back to a point in time when you are sure that a database is in a good state. By delaying the replay of replicated transaction logs into a database copy, you always have the ability to go to that copy and know that it represents a point in time in the past when the database was in a certain condition. But the promise is stronger than the reality, as Microsoft IT does not recommend the use of using lag copies with database availability groups. Microsoft no longer necessarily recommends lag copies as a backup strategy for Exchange data, and if you choose to implement them, you should have a solid justification based on your organizational size, available hardware, and so forth. Tony Redmond, a noted Exchange author, also recommends storage-based approaches when looking at point-in-time recovery solutions. Considerations of using lagged copies: Consumes large amount of free space (space for the database plus 7-14 days worth of log files) Microsoft provides no wizard or GUI interface to recover data from a lagged database. Manual Recovery: Steps are straightforward but they are manual and depend on the administrator. Difficult to use for single-item or mailbox recovery If lagged copy becomes primary, you force a reseed for all other database copies. Regarding the use of lagged copies: Recovery of complete databases is a different matter. My recommendation is that you should invest in storage or backup technology that incorporates strong recovery capabilities. Some storage offers very good snapshot recovery capabilities so that recovery is a matter of selecting the appropriate snapshot and recovering from it; some backup products provide similar capabilities. Your choice will be dictated by personal preference, previous deployment history, and your knowledge of how strong support personnel are within your company. In other words, you ll select the best tool for the job to fit the unique circumstances of your Exchange 2010 deployment. Tony Redmond, Exchange MVP
6 Complementing Exchange Availability with Array Based Technology Many companies are protecting Exchange 2010 with backups and built-in availability technologies such as Database Availability Groups but have started to realize that while DAG s are a great technology, there are often areas where third-party replication and management technology will have a positive impact. Database Availability Groups can be difficult to setup and manage especially in multi-site implementations and as such, companies are looking to complement the local high availability offered with DAGs with remote replication technologies offered by infrastructure companies like EMC. Another reason to consider storage-based solutions is for companies also have a need to quickly restore copies for operational recovery purposes such as single-item restores which cannot be fulfilled quickly and easily by DAGs or DAG lagged copies. Technology like snapshots and continuous data protection technology can enhance these protection technologies and enable instant, granular restores and zero data loss replication and can be managed from a central location. Snapshots Overview In general, a snapshot is a copy taken of a network share or an application using hostbased resources (software VSS snapshots) or hardware based options (using hardware providers). Snapshots can be made quickly and enable multiple application restore points primarily for faster recoveries, but also for use cases such as test/dev, reporting, analysis, and repurposing. Advantages of snapshots Improves speed of backup and restore Conserves resources on the server Provides a point in time of your application s data Data can be restored quickly to the same state as the copy Volume remains available to applications during the snapshot process Can remove the need for Exchange DAG lagged copies Disadvantages of snapshots Offered only on some storage systems Requires additional host software to enable application consistency Can utilize excess capacity if not managed correctly Continuous Data Protection Overview Continuous data protection (CDP) is a protection technology that is becoming increasingly popular. CDP creates an electronic journal of changes for every instant in time that data modification occurs. CDP technology enables any point in time recovery for recovery to the millisecond, using a unique DVR-like rollback mechanism.
7 Advantages of continuous data protection include: It preserves a record of every transaction that takes place in the company. If the system becomes infected with a virus or Trojan, or if a file becomes mutilated or corrupted and the problem is not discovered until sometime later, it is possible to recover the most recent clean copy of the affected file. It offers data recovery in a matter of seconds much less time than tape backups or archives. The installation of hardware and programming is straightforward and simple and does not put existing data at risk. Disadvantages of CDP include: Performance on the production application is decreased while waiting for confirmation that the replication has occurred. In the event of data corruption, the restoration process can be lengthy and contingent on network speed and file size. It requires proprietary hardware that adds cost and complexity.
8 Looking to the Future Some administrators may be understandably hesitant to invest in a high availability / disaster recovery solution for Exchange Server because Microsoft is expected to release Exchange Server 2013 next year. With each new Exchange Server release Microsoft has traditionally improved Exchange Server s resiliency to failure, so it is only natural to question whether the improvements that will be available in Exchange 2013 will mitigate the need to invest in a third party solution. Database Availability Groups continue to be the mechanism for ensuring the resiliency of mailbox servers in Exchange However, the improvements that Microsoft has made to DAGs might best be described as modest in scope. The improvements that Microsoft has made in Exchange Server 2013 fall into two general categories improvements to DAGs and improvements to the databases themselves. Let s start by talking about database level improvements. Database Improvements Without a doubt the most significant improvement that Microsoft has made at the database level is that of replacing the old store.exe with a managed store that has been entirely rewritten in C#. The reason why this change is so important is because the managed store provides failure isolation. Thanks to the managed store, each database now has a dedicated worker process. This means that is anything goes wrong with a database process, the problem will only impact that database. Other databases will remain unaffected because they are managed by separate worker processes. Some of the other database level improvements that Microsoft has made are not quite as drastic, but may prove to be helpful nonetheless. For example, Microsoft has added support for disks of up to 8 TB in size, and Exchange 2013 will make it possible to mix active and passive database copies on the same disk something that was not previously possible. DAG Improvements The improvements to DAGs in Exchange 2013 are more evolutionary than revolutionary. For instance, Microsoft has automated the configuration of DAG networks and they have made some enhancements to some of the DAG related PowerShell cmdlets. DAGs have also been optimized so that failover can occur more quickly. Exchange 2010 DAGs were designed to failover at the database level. When a failure was detected, Exchange would launch a process to determine which database copy would be the best choice to use during the failover. Exchange 2013 still supports database level failovers, but the process of selecting the best database copy to use has been enhanced. Some of the criteria that are considered include the copy queue length, the replay queue length, the database status, and the content index status. In addition to supporting database level failures, Exchange 2013 also supports failovers at the server level or even the datacenter level. Although the prospect of datacenter level failovers initially sounds promising, early Exchange 2013 builds indicate that many of the problems that plagued stretched DAGs in Exchange 2010 may still be an issue in Exchange For example, there is simply no getting around the cost and complexity of planning and implementing a stretched DAG.
9 WAN bandwidth limitations will also likely continue to be an issue. The WAN link must be able to deliver adequate bandwidth to facilitate the replication process without the link becoming saturated in the process. Of course organizations must also consider the ongoing costs associated with the logistics of managing remote Exchange Server deployments. It may ultimately be easier and more cost effective for organizations to use a third party solution for Exchange Server data replication than to rely on stretched DAGs. Summary In future, Exchange teams should continue to use what they know but also invest in leading edge technologies from Microsoft and third-party companies with proven technology.
Exchange DAG backup and design best practices
Exchange DAG backup and design best practices Brien M. Posey Modern Data Protection Built for Virtualization Database Availability Groups (DAGs) are the primary fault-tolerant mechanism used for protecting
More informationCA ARCserve and CA XOsoft r12.5 Best Practices for protecting Microsoft Exchange
CA RECOVERY MANAGEMENT R12.5 BEST PRACTICES CA ARCserve and CA XOsoft r12.5 Best Practices for protecting Microsoft Exchange Overview Benefits The CA Advantage The CA ARCserve Backup Support and Engineering
More informationSQL SERVER ADVANCED PROTECTION AND FAST RECOVERY WITH DELL EQUALLOGIC AUTO SNAPSHOT MANAGER
WHITE PAPER SQL SERVER ADVANCED PROTECTION AND FAST RECOVERY WITH DELL EQUALLOGIC AUTO SNAPSHOT MANAGER Business critical applications depend on Relational Database Management Systems (RMS) to store and
More informationA review of BackupAssist within a Hyper-V Environment. By Brien Posey
A review of BackupAssist within a Hyper-V Environment By Brien Posey 2 Contents Introduction... 3 An Introduction to BackupAssist... 4 Testing Methodologies... 5 Test 1: Restore a Virtual Machine s Configuration...
More informationDeploying Exchange Server 2007 SP1 on Windows Server 2008
Deploying Exchange Server 2007 SP1 on Windows Server 2008 Product Group - Enterprise Dell White Paper By Ananda Sankaran Andrew Bachler April 2008 Contents Introduction... 3 Deployment Considerations...
More informationContinuous Data Protection. PowerVault DL Backup to Disk Appliance
Continuous Data Protection PowerVault DL Backup to Disk Appliance Continuous Data Protection Current Situation The PowerVault DL Backup to Disk Appliance Powered by Symantec Backup Exec offers the industry
More informationExchange Server 2010 backup and recovery tips and tricks
Exchange Server backup and recovery tips and tricks Exchange Server backup and recovery Exchange Server A big part of your job as an Exchange Server administrator involves preparing for and recovering
More informationReal-time Protection for Hyper-V
1-888-674-9495 www.doubletake.com Real-time Protection for Hyper-V Real-Time Protection for Hyper-V Computer virtualization has come a long way in a very short time, triggered primarily by the rapid rate
More informationNon-Native Options for High Availability
The Essentials Series: Configuring High Availability for Windows Server 2008 Environments Non-Native Options for High Availability by Non-Native Options for High Availability... 1 Suitability and Cost...
More informationHigh Availability and Disaster Recovery for Exchange Servers Through a Mailbox Replication Approach
High Availability and Disaster Recovery for Exchange Servers Through a Mailbox Replication Approach Introduction Email is becoming ubiquitous and has become the standard tool for communication in many
More informationHow to Manage Critical Data Stored in Microsoft Exchange Server 2010. By Hitachi Data Systems
W H I T E P A P E R How to Manage Critical Data Stored in Microsoft Exchange Server 2010 By Hitachi Data Systems April 2012 2 Table of Contents Executive Summary and Introduction 3 Mission-critical Microsoft
More informationEnhancing Exchange Server 2010 Availability with Neverfail Best Practices for Simplifying and Automating Email Continuity
2010 Enhancing Exchange Server 2010 Availability with Neverfail Best Practices for Simplifying and Automating Email Continuity Anil Desai http://anildesai.net 2/1/2010 Enhancing Exchange Server 2010 Availability
More informationWhite Paper. Mimosa NearPoint for Microsoft Exchange Server. Next Generation Email Archiving for Exchange Server 2007. By Bob Spurzem and Martin Tuip
White Paper By Bob Spurzem and Martin Tuip Mimosa Systems, Inc. January 2008 Mimosa NearPoint for Microsoft Exchange Server Next Generation Email Archiving for Exchange Server 2007 CONTENTS Email has become
More informationSQL SERVER ADVANCED PROTECTION AND FAST RECOVERY WITH EQUALLOGIC AUTO-SNAPSHOT MANAGER
WHITE PAPER SQL SERVER ADVANCED PROTECTION AND FAST RECOVERY WITH EQUALLOGIC AUTO-SNAPSHOT MANAGER MANAGEMENT SERIES Business critical applications depend on Relational Database Management Systems (RDBMS)
More informationThe Microsoft Large Mailbox Vision
WHITE PAPER The Microsoft Large Mailbox Vision Giving users large mailboxes without breaking your budget Introduction Giving your users the ability to store more e mail has many advantages. Large mailboxes
More informationA review of BackupAssist within a Hyper-V Environment
A review of BackupAssist within a Hyper-V Environment By Brien Posey Contents Introduction... 2 An Introduction to BackupAssist... 3 Testing Methodologies... 4 Test 1: Restore a Virtual Machine s Configuration...
More informationWindows Geo-Clustering: SQL Server
Windows Geo-Clustering: SQL Server Edwin Sarmiento, Microsoft SQL Server MVP, Microsoft Certified Master Contents Introduction... 3 The Business Need for Geo-Clustering... 3 Single-location Clustering
More informationVirtual Infrastructure Security
Virtual Infrastructure Security 2 The virtual server is a perfect alternative to using multiple physical servers: several virtual servers are hosted on one physical server and each of them functions both
More informationVess A2000 Series HA Surveillance with Milestone XProtect VMS Version 1.0
Vess A2000 Series HA Surveillance with Milestone XProtect VMS Version 1.0 2014 PROMISE Technology, Inc. All Rights Reserved. Contents Introduction 1 Purpose 1 Scope 1 Audience 1 What is High Availability?
More informationEMC RECOVERPOINT FAMILY
EMC RECOVERPOINT FAMILY Cost-effective local and remote data protection and disaster recovery solution ESSENTIALS Maximize application data protection and disaster recovery Protect business applications
More informationTABLE OF CONTENTS THE SHAREPOINT MVP GUIDE TO ACHIEVING HIGH AVAILABILITY FOR SHAREPOINT DATA. Introduction. Examining Third-Party Replication Models
1 THE SHAREPOINT MVP GUIDE TO ACHIEVING HIGH AVAILABILITY TABLE OF CONTENTS 3 Introduction 14 Examining Third-Party Replication Models 4 Understanding Sharepoint High Availability Challenges With Sharepoint
More informationA SURVEY OF POPULAR CLUSTERING TECHNOLOGIES
A SURVEY OF POPULAR CLUSTERING TECHNOLOGIES By: Edward Whalen Performance Tuning Corporation INTRODUCTION There are a number of clustering products available on the market today, and clustering has become
More informationTECHNICAL SOLUTION BRIEF
EXCHANGE 2010 DAG Microsoft Exchange Database Availability Groups (DAG) provide a simpler way to replicate data than the approaches in previous versions of Exchange, allowing for easier creation of a single-site
More informationDeploy App Orchestration 2.6 for High Availability and Disaster Recovery
Deploy App Orchestration 2.6 for High Availability and Disaster Recovery Qiang Xu, Cloud Services Nanjing Team Last Updated: Mar 24, 2015 Contents Introduction... 2 Process Overview... 3 Before you begin...
More informationWHITE PAPER THE BENEFITS OF CONTINUOUS DATA PROTECTION. SYMANTEC Backup Exec 10d Continuous Protection Server
WHITE PAPER THE BENEFITS OF CONTINUOUS DATA PROTECTION SYMANTEC Backup Exec 10d Continuous Protection Server 1 TABLE OF CONTENTS EXECUTIVE SUMMARY...3 Current Situation...3 The New Opportunity...3 The
More informationProtecting Exchange 2010
Protecting Exchange 2010 Introduction With the introduction of Exchange 2010, many new Exchange features have been added or refined in the areas of mailbox recovery, mail archiving, and system robustness.
More informationContinuous Data Protection for any Point-in-Time Recovery: Product Options for Protecting Virtual Machines or Storage Array LUNs
EMC RECOVERPOINT FAMILY Continuous Data Protection for any Point-in-Time Recovery: Product Options for Protecting Virtual Machines or Storage Array LUNs ESSENTIALS EMC RecoverPoint Family Optimizes RPO
More informationSymantec Backup Exec 11d for Windows Servers Sets the Standard for Exchange 2007 Server Data Protection
Symantec Backup Exec 11d for Windows Servers Sets the Standard for Exchange 2007 Server Data Protection Agent for Microsoft Exchange Server TechPDF Peter Imming, Backup Exec Product Management April 16,
More informationHigh Availability with Postgres Plus Advanced Server. An EnterpriseDB White Paper
High Availability with Postgres Plus Advanced Server An EnterpriseDB White Paper For DBAs, Database Architects & IT Directors December 2013 Table of Contents Introduction 3 Active/Passive Clustering 4
More informationUsing Hitachi Protection Manager and Hitachi Storage Cluster software for Rapid Recovery and Disaster Recovery in Microsoft Environments
Using Hitachi Protection Manager and Hitachi Storage Cluster software for Rapid Recovery and Disaster Recovery in Microsoft Environments Robert Burch, Advanced Technical Consultant Leland Sindt, Principal
More information10135A: Configuring, Managing, and Troubleshooting Microsoft Exchange Server 2010
10135A: Configuring, Managing, and Troubleshooting Microsoft Exchange Server 2010 Course Number: 10135A Course Length: 5 Day Course Overview This instructor-led course will provide you with the knowledge
More informationAcronis Backup & Recovery 11.5. Backing Up Microsoft Exchange Server Data
Acronis Backup & Recovery 11.5 Backing Up Microsoft Exchange Server Data Copyright Statement Copyright Acronis International GmbH, 2002-2012. All rights reserved. Acronis and Acronis Secure Zone are registered
More informationWHITE PAPER PPAPER. Symantec Backup Exec Quick Recovery & Off-Host Backup Solutions. for Microsoft Exchange Server 2003 & Microsoft SQL Server
WHITE PAPER PPAPER Symantec Backup Exec Quick Recovery & Off-Host Backup Solutions Symantec Backup Exec Quick Recovery & Off-Host Backup Solutions for Microsoft Exchange Server 2003 & Microsoft SQL Server
More informationFeature Comparison. Windows Server 2008 R2 Hyper-V and Windows Server 2012 Hyper-V
Comparison and Contents Introduction... 4 More Secure Multitenancy... 5 Flexible Infrastructure... 9 Scale, Performance, and Density... 13 High Availability... 18 Processor and Memory Support... 24 Network...
More informationSnapManager 5.0 for Microsoft Exchange Best Practices Guide
NETAPP TECHNICAL REPORT SnapManager 5.0 for Microsoft Exchange s Guide Shannon Flynn, NetApp November 2008 TR-3730 Table of Contents 1 EXECUTIVE SUMMARY... 3 1.1 PURPOSE AND SCOPE... 3 1.2 INTENDED AUDIENCE...
More informationAcronis Backup & Recovery 11.5. Update 2. Backing Up Microsoft Exchange Server Data
Acronis Backup & Recovery 11.5 Update 2 Backing Up Microsoft Exchange Server Data Copyright Statement Copyright Acronis International GmbH, 2002-2013. All rights reserved. Acronis and Acronis Secure Zone
More informationNear-Instant Oracle Cloning with Syncsort AdvancedClient Technologies White Paper
Near-Instant Oracle Cloning with Syncsort AdvancedClient Technologies White Paper bex30102507wpor Near-Instant Oracle Cloning with Syncsort AdvancedClient Technologies Introduction Are you a database administrator
More informationAcronis Backup Advanced for Exchange. Version 11.5 Update 3. Backing Up Microsoft Exchange Server Data
Acronis Backup Advanced for Exchange Version 11.5 Update 3 Backing Up Microsoft Exchange Server Data Copyright Statement Copyright Acronis International GmbH, 2002-2014. All rights reserved. Acronis and
More information70-662: Deploying Microsoft Exchange Server 2010
70-662: Deploying Microsoft Exchange Server 2010 Course Introduction Course Introduction Chapter 01 - Active Directory and Supporting Infrastructure Active Directory and Supporting Infrastructure Network
More informationSystem Protection for Hyper-V Whitepaper
Whitepaper Contents 1. Introduction... 2 Documentation... 2 Licensing... 2 Hyper-V requirements... 2 Definitions... 3 Considerations... 3 2. About the BackupAssist Hyper-V solution... 4 Advantages... 4
More informationAvailability and Disaster Recovery: Basic Principles
Availability and Disaster Recovery: Basic Principles by Chuck Petch, WVS Senior Technical Writer At first glance availability and recovery may seem like opposites. Availability involves designing computer
More informationEXCHANGE 2010 DISASTER RECOVERY OPTIONS WITH CROSS-SITE EXCHANGE DAG AND EMC RECOVERPOINT
White Paper EXCHANGE 2010 DISASTER RECOVERY OPTIONS WITH CROSS-SITE EXCHANGE DAG AND EMC RECOVERPOINT A Detailed Review EMC GLOBAL SOLUTIONS Abstract This white paper provides analysis, data points and
More informationGuarding Physical Servers in a Virtual World
Guarding Physical Servers in a Virtual World By: Brien M. Posey A whitepaper written for IT Professionals, IT Administrators and IT Managers There is no question that server virtualization has revolutionized
More informationMicrosoft Exchange 2013 Ultimate Bootcamp Your pathway to becoming a GREAT Exchange Administrator
Microsoft Exchange 2013 Ultimate Bootcamp Your pathway to becoming a GREAT Exchange Administrator Introduction Microsoft Exchange with its inherent high level of security features, improved assistant,
More informationAcronis Backup & Recovery 11.5
Acronis Backup & Recovery 11.5 Update 2 Backing Up Microsoft Exchange Server Data Copyright Statement Copyright Acronis International GmbH, 2002-2013. All rights reserved. Acronis and Acronis Secure Zone
More informationSolution Brief Availability and Recovery Options: Microsoft Exchange Solutions on VMware
Introduction By leveraging the inherent benefits of a virtualization based platform, a Microsoft Exchange Server 2007 deployment on VMware Infrastructure 3 offers a variety of availability and recovery
More informationBUSINESS CONTINUITY AND DISASTER RECOVERY FOR ORACLE 11g
BUSINESS CONTINUITY AND DISASTER RECOVERY FOR ORACLE 11g ENABLED BY EMC VMAX 10K AND EMC RECOVERPOINT Technical Presentation EMC Solutions Group 1 Agenda Business case Symmetrix VMAX 10K overview RecoverPoint
More informationEnsuring business continuity after Active Directory disasters
www.lepide.com Ensuring business continuity after Active Directory disasters Whitepaper 2013 Introduction Active Directory is the distributed directory system that contains identification and authentication
More informationAssuring High Availability in Healthcare Interfacing Considerations and Approach
Assuring High Availability in Healthcare Interfacing Considerations and Approach High availability is a term used in the software industry to indicate that the application is available a high percentage
More informationExchange 2010 ITPro. Milan Marenčík Microsoft Services
Exchange 2010 ITPro Milan Marenčík Microsoft Services Exchange 2010 64 bit AD required 5 serverovych roli Anywhere, anytime, any device Secure by design 5 roli Mailbox Client Access Hub Transport Unified
More informationBest practice: Simultaneously upgrade your Exchange and disaster recovery protection
Best practice: Simultaneously upgrade your Exchange and disaster recovery protection March 2006 1601 Trapelo Road Waltham, MA 02451 1.866.WANSync www.xosoft.com Contents The Value Proposition... 1 Description
More informationMicrosoft SharePoint 2010 on VMware Availability and Recovery Options. Microsoft SharePoint 2010 on VMware Availability and Recovery Options
This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware
More informationAdvice for Virtualizing Exchange 2010 Server Roles
E-Guide Advice for Virtualizing Exchange 2010 Server Roles When virtualizing Exchange Server 2010, it's important to correctly configure virtual machines (VMs) that will host certain Exchange Server roles
More informationCREATING SQL SERVER DISASTER RECOVERY SOLUTIONS WITH SIOS DATAKEEPER
CREATING SQL SERVER DISASTER RECOVERY SOLUTIONS WITH SIOS DATAKEEPER Learn how DataKeeper Cluster Edition can be used to create disaster recovery solutions for SQL Server deployments. By Allan Hirt, SQLHA
More informationWestek Technology Snapshot and HA iscsi Replication Suite
Westek Technology Snapshot and HA iscsi Replication Suite Westek s Power iscsi models have feature options to provide both time stamped snapshots of your data; and real time block level data replication
More informationEliminating End User and Application Downtime:
Eliminating End User and Application Downtime: Architecting the Right Continuous Availability and Disaster Recovery Environment March 2010 Table of Contents Introduction 3 Where to Start 3 Moving to Continuous
More informationAcronis Backup Advanced Version 11.5 Update 6
Acronis Backup Advanced Version 11.5 Update 6 APPLIES TO THE FOLLOWING PRODUCTS Advanced for Exchange BACKING UP MICROSOFT EXCHANGE SERVER DATA Copyright Statement Copyright Acronis International GmbH,
More informationIMPROVING MICROSOFT EXCHANGE SERVER RECOVERY WITH EMC RECOVERPOINT
White Paper IMPROVING MICROSOFT EXCHANGE SERVER RECOVERY WITH EMC RECOVERPOINT Applied Technology Abstract This white paper outlines the challenges faced by Microsoft Exchange administrators in managing
More informationVersion: 1.5 2014 Page 1 of 5
Version: 1.5 2014 Page 1 of 5 1.0 Overview A backup policy is similar to an insurance policy it provides the last line of defense against data loss and is sometimes the only way to recover from a hardware
More informationData Storage And Backup
Data Storage And Backup The availability of Superfast Broadband enables you to take advantage of a range of cloud-based storage and backup solutions capable of handling vast volumes of digital data. Data
More informationEMC Backup and Recovery for Microsoft SQL Server 2008 Enabled by EMC Celerra Unified Storage
EMC Backup and Recovery for Microsoft SQL Server 2008 Enabled by EMC Celerra Unified Storage Applied Technology Abstract This white paper describes various backup and recovery solutions available for SQL
More informationProtecting Microsoft Hyper-V 3.0 Environments with CA ARCserve
Solution Brief: CA ARCserve R16.5 Complexity ate my budget Protecting Microsoft Hyper-V 3.0 Environments with CA ARCserve Customer Challenges Today, you face demanding service level agreements (SLAs) while
More informationAvailability for the modern datacentre Veeam Availability Suite v8 & Sneakpreview v9
Veeam Summer School Availability for the modern datacentre Veeam Availability Suite v8 & Sneakpreview v9 Jan van Leuken System Engineer Benelux, Veeam Software jan.vanleuken@veeam.com +31 (0)615 83 50
More informationBackup and Recovery for Microsoft Hyper-V Using Best Practices Planning. Brien M. Posey
Backup and Recovery for Microsoft Hyper-V Using Best Practices Planning Brien M. Posey Introduction There usually isn t anything overly complicated about backing up a physical datacenter. While it s true
More informationAdministration GUIDE. Exchange Database idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233
Administration GUIDE Exchange Database idataagent Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233 User Guide - Exchange Database idataagent Table of Contents Overview Introduction Key Features
More informationHandling Hyper-V. In this series of articles, learn how to manage Hyper-V, from ensuring high availability to upgrading to Windows Server 2012 R2
White Paper Handling Hyper-V In this series of articles, learn how to manage Hyper-V, from ensuring high availability to upgrading to Windows Server 2012 R2 White Paper How to Make Hyper-V Virtual Machines
More informationCloud Optimize Your IT
Cloud Optimize Your IT Windows Server 2012 The information contained in this presentation relates to a pre-release product which may be substantially modified before it is commercially released. This pre-release
More informationEMC NetWorker Module for Microsoft for Exchange Server VSS
EMC NetWorker Module for Microsoft for Exchange Server VSS Version 9.0 User Guide 302-001-753 REV 02 Copyright 2007-2015 EMC Corporation. All rights reserved. Published in USA. Published October, 2015
More informationHigh availability and disaster recovery with Microsoft, Citrix and HP
High availability and disaster recovery White Paper High availability and disaster recovery with Microsoft, Citrix and HP Using virtualization, automation and next-generation storage to improve business
More informationLEARN EXCHANGE PART 2 Managing your Exchange Architecture
LEARN EXCHANGE PART 2 Managing your Exchange Architecture Niels Engelen System Engineer, Veeam Software niels.engelen@veeam.com Johan Huttenga System Engineer, Veeam Software johan.huttenga@veeam.com 2014
More informationPreface... 1. Introduction... 1 High Availability... 2 Users... 4 Other Resources... 5 Conventions... 5
Table of Contents Preface.................................................... 1 Introduction............................................................. 1 High Availability.........................................................
More informationEMC NetWorker Module for Microsoft for Exchange Server VSS
EMC NetWorker Module for Microsoft for Exchange Server VSS Version 8.2 Service Pack 1 User Guide 302-001-233 REV 01 Copyright 2007-2015 EMC Corporation. All rights reserved. Published in USA. Published
More informationHow To Install The Exchange Idataagent On A Windows 7.5.1 (Windows 7) (Windows 8) (Powerpoint) (For Windows 7) And Windows 7 (Windows) (Netware) (Operations) (X
Page 1 of 208 User Guide - Exchange Database idataagent TABLE OF CONTENTS OVERVIEW Introduction Key Features Add-On Components Customized Features for Your Exchange Version Terminology SYSTEM REQUIREMENTS
More informationHigh Availability for Citrix XenApp
WHITE PAPER Citrix XenApp High Availability for Citrix XenApp Enhancing XenApp Availability with NetScaler Reference Architecture www.citrix.com Contents Contents... 2 Introduction... 3 Desktop Availability...
More informationThis course is intended for IT professionals who are responsible for the Exchange Server messaging environment in an enterprise.
10233A: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Course Number: 10233A Course Length: 5 Day Course Overview This instructor-led course provides you with the knowledge
More informationDisaster Recovery Strategies: Business Continuity through Remote Backup Replication
W H I T E P A P E R S O L U T I O N : D I S A S T E R R E C O V E R Y T E C H N O L O G Y : R E M O T E R E P L I C A T I O N Disaster Recovery Strategies: Business Continuity through Remote Backup Replication
More informationExchange 2010 Best Practices and Strategies for Backing Up and Restoring Exchange 2010 Environment
Best Practices and Strategies for Backing Up and Restoring Exchange 2010 Environment 1 Exchange 2010 Can Only Be Backed Up Using VSS Writers Microsoft: Windows Server Backup System Center Data Protection
More informationWindows Server Failover Clustering April 2010
Windows Server Failover Clustering April 00 Windows Server Failover Clustering (WSFC) is the successor to Microsoft Cluster Service (MSCS). WSFC and its predecessor, MSCS, offer high availability for critical
More informationSystem Protection for Hyper-V User Guide
User Guide BackupAssist User Guides explain how to create and modify backup jobs, create backups and perform restores. These steps are explained in more detail in a guide s respective whitepaper. Whitepapers
More informationAppSense Environment Manager. Enterprise Design Guide
Enterprise Design Guide Contents Introduction... 3 Document Purpose... 3 Basic Architecture... 3 Common Components and Terminology... 4 Best Practices... 5 Scalability Designs... 6 Management Server Scalability...
More informationCA ARCserve Family r15
CA ARCserve Family r15 Rami Nasser EMEA Principal Consultant, Technical Sales Rami.Nasser@ca.com The ARCserve Family More than Backup The only solution that: Gives customers control over their changing
More informationHyper-V Protection. User guide
Hyper-V Protection User guide Contents 1. Hyper-V overview... 2 Documentation... 2 Licensing... 2 Hyper-V requirements... 2 Windows Server 2012 Hyper-V support... 3 2. Hyper-V protection features... 3
More informationSymantec NetBackup Blueprints
Symantec NetBackup Blueprints Blueprint for Microsoft Exchange Symantec Backup and Recovery Technical Services Symantec NetBackup Blueprints 1 Symantec NetBackup Blueprints Preface/disclaimer Notice This
More informationUBDR and Microsoft Cluster Server
WHITE PAPER UBDR and Microsoft Cluster Server UltraBac Version 8.x OVERVIEW UltraBac Software, author of award-winning backup and storage management software, is proud to announce enhanced support for
More informationData Storage and Backup
Data Storage and Backup The availability of Superfast Broadband enables you to take advantage of a range of cloud-based storage and backup solutions capable of handling vast volumes of digital data. www.business.wales.gov.uk/superfastbusinesswales
More informationCisco and EMC Solutions for Application Acceleration and Branch Office Infrastructure Consolidation
Solution Overview Cisco and EMC Solutions for Application Acceleration and Branch Office Infrastructure Consolidation IT organizations face challenges in consolidating costly and difficult-to-manage branch-office
More informationEvery organization has critical data that it can t live without. When a disaster strikes, how long can your business survive without access to its
DISASTER RECOVERY STRATEGIES: BUSINESS CONTINUITY THROUGH REMOTE BACKUP REPLICATION Every organization has critical data that it can t live without. When a disaster strikes, how long can your business
More informationDell PowerVault DL2200 & BE 2010 Power Suite. Owen Que. Channel Systems Consultant Dell
Dell PowerVault DL2200 & BE 2010 Power Suite Owen Que Channel Systems Consultant Dell Dell PowerVault DL2200 powered by Symantec Backup Exec 2010 1 Replace Tape with Deduplication Customer Storage Challenge
More informationCloud Optimize Your IT
Cloud Optimize Your IT Windows Server 2012 Michael Faden Partner Technology Advisor Microsoft Schweiz 1 Beyond Virtualization virtualization The power of many servers, the simplicity of one Every app,
More informationConnectivity. Alliance Access 7.0. Database Recovery. Information Paper
Connectivity Alliance Access 7.0 Database Recovery Information Paper Table of Contents Preface... 3 1 Overview... 4 2 Resiliency Concepts... 6 2.1 Database Loss Business Impact... 6 2.2 Database Recovery
More informationEMC VPLEX FAMILY. Continuous Availability and data Mobility Within and Across Data Centers
EMC VPLEX FAMILY Continuous Availability and data Mobility Within and Across Data Centers DELIVERING CONTINUOUS AVAILABILITY AND DATA MOBILITY FOR MISSION CRITICAL APPLICATIONS Storage infrastructure is
More informationNSI Solutions with Microsoft VSS
Published: March 2004 Abstract With the introduction of Volume Shadow Copy Service (VSS) in Microsoft Windows Server 2003 and Windows Storage Server 2003 and the strength of NSI Software Double-Take you
More informationWHITE PAPER [MICROSOFT EXCHANGE 2007 WITH ETERNUS STORAGE] WHITE PAPER MICROSOFT EXCHANGE 2007 WITH ETERNUS STORAGE
WHITE PAPER MICROSOFT EXCHANGE 2007 WITH ETERNUS STORAGE ETERNUS STORAGE Table of Contents 1 SCOPE -------------------------------------------------------------------------------------------------------------------------
More informationHyper-V backup implementation guide
Hyper-V backup implementation guide A best practice guide for Hyper-V backup administrators. www.backup-assist.ca Contents 1. Planning a Hyper-V backup... 2 Hyper-V backup considerations... 2 2. Hyper-V
More informationHow To Protect Data On Network Attached Storage (Nas) From Disaster
White Paper EMC FOR NETWORK ATTACHED STORAGE (NAS) BACKUP AND RECOVERY Abstract This white paper provides an overview of EMC s industry leading backup and recovery solutions for NAS systems. It also explains
More informationThe Benefits of Continuous Data Protection (CDP) for IBM i and AIX Environments
The Benefits of Continuous Data Protection (CDP) for IBM i and AIX Environments New flexible technologies enable quick and easy recovery of data to any point in time. Introduction Downtime and data loss
More informationProtecting Windows Microsoft Exchange Server Data Protection
Solution Brief Protecting Microsoft Exchange Server Growth in data for Microsoft Exchange is expanding at a rapid growth rate. Mailbox sizes are increasing due to multimedia file, documentation collaboration
More informationSnapManager 4.0 for Microsoft Exchange
SnapManager 4.0 for Microsoft Exchange Best Practice Guide Shannon Flynn, NetApp January, 2007 TR-3541 Table of Contents 1. Executive Summary... 4 1.1 Purpose and Scope... 4 1.2 Intended Audience... 4
More informationFive Fundamentals for Modern Data Center Availability
Five Fundamentals for Modern Data Center Availability David Davis VMware vexpert Kirsten Stoner Product Strategy Coordinator Contents Introduction...3 Use an availability solution built for modern data
More informationCA XOsoft High Availability for Windows
CA XOsoft High Availability for Windows Microsoft File Server Operation Guide r12.5 This documentation and any related computer software help programs (hereinafter referred to as the Documentation ) is
More information