NetVault Plug-in for Exchange 12.0

In the list of plug-ins, open Plug‑in for Exchange, and drill down to the name of the Exchange Server or Exchange Virtual Server and its available nodes.

If you are using Exchange 2007, complete the following steps:

Expand the applicable Microsoft Information Store to display all the Storage Groups contained within. You can also open an individual group to display all databases contained within that group.

Select the data that you want to back up by clicking the box to the left of that item, that is, to mark it with a green check. You can also 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 all databases on the Exchange Server are backed up. However, selecting the Microsoft Exchange Server node enables creating a selection set that can be used across multiple installations of Plug‑in for Exchange.


	IMPORTANT: Backing up individual databases might affect the behavior of log truncation for all databases in the Storage Group. This issue might 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. If an individual database is selected for a VSS-based backup, the entire Storage Group is backed up because VSS backups are performed only at the Storage Group level.

If you are using Exchange 2010 or later, complete the following steps:

Expand the applicable Exchange Server to display all the Mailbox Databases contained within

Select the database that you want to back up by clicking the box to the left of that item, that is, to mark it with a green check. You can also select the entire Exchange Server.

Selecting the Microsoft Exchange Server node is equivalent to selecting the Exchange Server or NetVault Backup Virtual Client, in that all databases included in the DAG or standalone deployment are backed up. However, selecting the Microsoft Exchange Server node enables creating a selection set that can be used across multiple installations of Plug‑in for Exchange.

Click Save, enter a name in the Create New Set dialog box, and click Save.

The name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.

Setting backup options

The next step involves creating the Backup Options Set or selecting an existing one.


	TIP: To use an existing set, in the Plugin Options list, select the set that you want to use.

Next to the Plugin Options list, click Create New.

If you are using Exchange 2007, select the applicable option in the Backup Method section:

•

Extensible Storage Engine (ESE)

•

Volume Shadow Copy Service (VSS)

The Backup Method defaults to the Default Backup Method selected on the Exchange Server Configuration dialog box. The plug-in 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. Because Exchange 2010 and later only support VSS, you do not have to select a method for these versions. For more information about selecting a backup method for your Exchange Server, see Defining an Exchange data protection strategy.

In the Exchange Backup Type section, select the applicable option.

•

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. In Exchange Server, a Full Backup includes all database files and transaction log files.

•

Copy: A Copy Backup backs up the set of items that have been selected without performing a transaction log file truncation. This backup 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, nonintrusive complete backup of an Exchange Server and is commonly used for offline scaling and migration scenarios.

•

Incremental: An Incremental Backup backs up 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 completed, the Exchange Server truncates the transaction logs. This truncation helps maintain the operating health of the Exchange Server.

•

Differential: A Differential Backup backs up 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.

For more information, see Reviewing the backup types.

In the Snapshot Options section, complete the following:

•

Backup Files to Storage: This option, which is selected by default, copies the selected data from snapshots to a storage device. The plug-in uses a VSS provider to create persistent or non-persistent snapshots on the client, and copies the selected data from the snapshot, or snapshots, to the storage device.

•

Retain Snapshot as Persistent: To retain persistent snapshots on a disk array, select this check box.

•

If the Backup Files to Storage and Retain Snapshot as Persistent check boxes are both selected, the plug-in copies the selected files to a storage device and adds the snapshot information to the backup index.

•

If you clear the Backup Files to Storage check box and select this check box, the plug-in writes only the index entries to the backup stream and creates persistent snapshots on the disk array.

•

Discard After: If you selected the Retain Snapshot as Persistent check box and you want to delete persistent snapshots from a disk array after a specified period, select this check box and complete the expiration fields.

Regardless of the expiration settings, a snapshot is automatically deleted when the associated saveset is retired. Therefore, this option is only useful when you want to discard a snapshot before the associated saveset is retired. To expire a snapshot immediately, you must log in to the storage array, and manually expire the snapshot. Otherwise, the snapshot expires according to the retention policy selected while creating the snapshot.


	NOTE: To use the Retain Snapshot as Persistent and Discard After options, the Exchange Mailbox Server that you back up must reside on a NetVault Backup-supported disk array and the vendor’s hardware-based VSS provider must be in place. For more information, see Understanding snapshot-based backups.

In the Advanced Options section, complete the following:

•

Maximum Number of Parallel Streams: To enable the fastest backups possible, the plug-in uses parallel streams to back up the Storage Groups/Mailbox Databases simultaneously. This option lets you 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 on the Target tab.

•

Less than Maximum number of Storage Groups/Mailbox Databases that can be created. The following table details the maximum number of Storage Groups/Mailbox Databases allowed by each Exchange Server version and edition:


Exchange Server method	Server edition	Maximum number of Storage Groups/Mailbox Databases
Exchange Server 2007	Standard	5 Storage Groups
Exchange Server 2007	Enterprise	50 Storage Groups
Exchange Server 2010	Standard	5 Mailbox Databases
Exchange Server 2010	Enterprise	100 Mailbox Databases
Exchange Server 2013	Standard	5 Mailbox Databases
Exchange Server 2013	Enterprise	50 Mailbox Databases
Exchange Server 2016	Standard	5 Mailbox Databases
Exchange Server 2016	Enterprise	100 Mailbox Databases

For example, if you are targeting a Virtual Tape Library configured with two drives and you have 20 Storage Groups, the Maximum Number of Parallel Streams should be 2 or less.


	NOTE: In an Exchange 2010 or later DAG deployment, the number of parallel streams is allocated on a per-server basis; therefore, the number applies to each server included in the DAG. For example, if your DAG includes three Exchange Servers and you select two streams for backup, it can create up to six simultaneous streams assuming that there are at least two databases on each server that must be backed up. If there are fewer databases, the streams are not created. If there are fewer drives available, the streams wait until the next drive is available.


	IMPORTANT: If you use parallel streams, do not select the Ensure this backup is the first on the media option in the Target Storage section. If the plug-in generates more than one data stream, each data stream targets a separate piece of media and assumes that it is the first backup on the media.

•

Mount unmounted databases before backup: This option mounts any unmounted databases before attempting to back up the database.

•

Perform VSS Consistency Check: This option indicates whether a consistency check of the VSS should be performed on the Exchange Storage Groups/Mailbox Databases included in the backup job. Quest recommends that you use this option, which is selected by default.

•

Incomplete Backup of All Items Selected: When multiple items are included in a backup and the plug-in is unable to back up all the selected items, the plug-in lets you specify what action the backup should take. For example, if a job includes multiple Storage Groups/Mailbox Databases and the backup of all but one is successful, you can specify what action the backup job should take.

•

Complete with Warnings — Saveset Retained: The job returns a status of “Backup Completed with warnings” and a backup saveset is created that includes the items that were successfully backed up.

•

Complete without Warnings — Saveset Retained: The job completes and returns a status of “Backup Completed.” The errors are logged in the NetVault Backup binary logs and ignored on the Job Status page. A backup saveset is created that includes the items that were backed up.

•

Fail — Saveset Retained: The job returns a status of “Backup Failed.” However, a backup saveset is generated that includes the items that were successfully backed up.

•

Fail — No Saveset Retained: The job returns a status of “Backup Failed” and no saveset of backed-up objects is kept. That is, even if some of the objects were successfully backed up, the saveset is discarded.

•

Backup Algorithm in DAG (only available in DAG deployments):

•

All Active: If you want the Plug‑in for Exchange on each Mailbox Server to back up only the databases that are active when the backup is performed, select this option.

•

Backup Database Copies with the Lowest Activation Preference Number: Select this option if you want the plug-in to select an available database copy. The plug-in selects the copy with the lowest activation preference number for backup. If a database copy is not available for backup or the copy is disabled, the plug-in selects the active database.

•

Backup Database Copies with the Highest Activation Preference Number: Select this option if you want the plug-in to select the available database copy with the highest activation preference number. If a database copy is not available for backup or the copy is disabled, the plug-in selects the active database.

•

Backup Databases from preferred Exchange Server whenever possible: Select this option if you want to specify a list of preferred Exchange Servers to perform backups from and a list of servers to exclude. The plug-in skips database copies that are in a disabled state.

This option works with the following fields:

•

If possible Backup Exchange Databases only from the following Exchange Server: If you selected Backup Databases from preferred Exchange Server whenever possible, enter a comma-separated list of Exchange Servers, in order of preference, that should be used to back up the database. If the database, copy or active, is available in the Exchange Server listed first, it is backed up from that server. If not, the plug-in tries the next server in the list, and so on. If there is not an available copy — including the active database — on any of the listed servers, the plug-in uses the server that contains the active database or the database copy with the lowest activation preference number.

•

If possible do not Backup Exchange Databases from the following Exchange Server: If you selected Backup Databases from preferred Exchange Server whenever possible, enter a comma-separated list of Exchange Servers, in order of preference, that should not be used to back up the database. The server listed first has the lowest preference. If the database, copy or active, is available on any other Exchange Server, the database is not backed up from the server listed. The plug-in tries to exclude all servers listed in this field. If the database is only available on one of the excluded servers, the plug-in performs the backup using the last server in the list of exclusions.


	NOTE: The If possible Backup Exchange Databases only from the following Exchange Server option takes precedence over If possible do not Backup Exchange Databases from the following Exchange Server. If the backup can be performed using a server from the first list, the plug-in does not process the list of excluded servers.

If you are performing a VSS-based backup in an LCR or CCR environment, complete the following in the Volume Shadow Copy Service (VSS) section:


	NOTE: When performing VSS-based backups in an LCR or CCR environment, the plug-in is able to back up 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.

•

Active Copy: To back up the active copy of all Storage Groups, select this option. This option is the default 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: To back up the passive copy of all Storage Groups, select this option. While available for both CCR and LCR deployments, this option is the default option for CCR deployments and has the following restrictions:

•

If you are selecting this option for an LCR deployment, backups are performed only for Storage Groups that have LCR enabled. Storage Groups that do not have LCR enabled are not backed up.

•

If SCR is enabled for any of the Storage Groups, even in a CCR and LCR deployment, selecting this option causes the backups to fail. Failure occurs because backups cannot be performed from the 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 fails. The Failed passive copy can be returned to a Healthy state by deleting it and updating it with the Update-StorageGroupCopy command. For more information about the Update-StorageGroupCopy command, see http://technet.microsoft.com/en-us/library/aa998853.aspx.

•

Mixed (Available only for LCR deployments): Selecting this option backs up the passive copies of all Storage Groups along with active copy Storage Groups that are not LCR enabled. This option is the default and the recommended option for LCR deployments that do not have SCR enabled, and has the following restriction:

If SCR is enabled for any of the Storage Groups, selecting this option causes the backups to fail. The Active Copy option should be selected for environments where LCR and SCR are simultaneously deployed.

Click Save to save the set.

In the Create New Set dialog box, specify a name for the set, and click Save.

The name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Windows, there is no length restriction; however, a maximum of 40 characters is recommended.

Finalizing and submitting the backup job

Use the Schedule, Target Storage, and Advanced Options lists to configure any additional required options.

Click Save or Save & Submit, whichever is applicable.


	TIP: To run a job that you have already created and saved, select Manage Job Definitions on the Navigation pane, select the applicable job, and click Run Now.

You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Backup Administrator’s Guide.


	IMPORTANT: Restarting services that host Exchange VSS Writers, including the Microsoft Exchange Information Store, Microsoft Exchange Replication Service, complete OS reboots, and cluster failovers causes running backup jobs to fail. This failure is due to a loss of in-memory ‘backup-in-progress’ state that Microsoft maintains for VSS backups.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

NetVault Plug-in for Exchange 12.0 - User Guide

Backing up data

Selecting data for a backup

Setting backup options

Finalizing and submitting the backup job