Converse agora com nosso suporte
Chat com o suporte

NetVault Plug-in for Exchange 12.0 - User Guide

Introducing NetVault Backup Plug-in for Exchange Defining an Exchange data protection strategy Planning your Exchange Server deployment Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data Troubleshooting

Planning your Exchange Server deployment

•
Deployment overview
•
Standalone deployment
•
High-availability deployments

Deployment overview

Microsoft supports the deployment of Exchange Mailbox Server on either a single server or high-availability environment, including:

•
Database Availability Group (DAG)
•
Local Continuous Replication (LCR)
•
Single Copy Cluster (SCC) or Failover Cluster
•
Cluster Continuous Replication (CCR)

Deploying the Plug‑in for Exchange in each of these environments is almost identical because the Plug‑in for Exchange is installed on the server that hosts the Exchange Server Mailbox Databases. The following topics describe how the Plug‑in for Exchange is deployed in each type of Exchange Mailbox Server deployment.

Standalone deployment

•
Supported Exchange Server Versions: All
•
Supported Exchange Server Editions: All
•
Supported Backup Methods: ESE and VSS

In a standalone deployment, there is a single Exchange Mailbox Server. The Plug‑in for Exchange is installed on the server that is designated the Mailbox Server and performs all backups and restores to and from this server. In this type of deployment, no high-availability solution, such as LCR, has been deployed.

While you can install the NetVault Backup Server on the Exchange Mailbox Server, Quest recommends that you use separate machines.

Figure 1. Standalone deployment

 
* 
IMPORTANT: Regardless of the environment, a separate NetVault Backup Server and Exchange Server vs. a single machine configured as both, the Plug‑in for Exchange must be installed on the host where Exchange Server Mailbox Databases reside. Sample images and procedures throughout this guide assume that this two-machine environment is in place and that all configuration requirements have been met.

High-availability deployments

High-availability deployments include:

•
Single-location Database Availability Group (DAG)
•
Local Continuous Replication (LCR)
•
Single Copy Cluster (SCC) or Failover Cluster
•
Cluster Continuous Replication (CCR)
Single-location Database Availability Group (DAG)
•
Supported Exchange Server Versions: Exchange 2010 and later
•
Supported Exchange Server Editions: All
•
Supported Backup Methods: VSS
•
Plug‑in for Exchange License Required: Plug‑in for Exchange Standard Edition Cluster Support or Plug‑in for Exchange Enterprise Edition Cluster Support

In an Exchange Single-Location DAG, multiple Exchange Mailbox Servers exist in a single Active Directory Site and are physically located in the same data center. A DAG is created across multiple Mailbox Servers with the Database Copies spread across the multiple Mailbox Servers. In a Single-Location DAG, you create a NetVault Backup Virtual Client where the Plug‑in for Exchange is installed on each of the Exchange Mailbox Servers.

In the backup process for a DAG environment, the Plug‑in for Exchange lets you select either all active copies of the databases or a database copy whenever possible. If you choose the latter and there are multiple copies, the copy with the lowest activation preference number is selected. If you choose the latter and a database copy is not available, the active database is selected. For more information about the activation preference number, see Mailbox Database Copies at http://technet.microsoft.com/en-us/library/dd979802.aspx.

 
* 
IMPORTANT: To support a DAG that does not use a cluster name object (CNO) or IP address, create a NetVault Backup Virtual Client that uses a fixed IP address or network name that corresponds to one of the Real Clients in the DAG. If the machine to which the fixed IP address or network name corresponds goes offline for any reason, subsequent backup jobs fail. Either bring the machine back online or update the Virtual Client to use a different IP address or network name.
Figure 2. DAG deployment

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação