Protect Microsoft Exchange 2013 using Symantec Netbackup 7.6.0.1

Document created by leo nguyen on Jul 23, 2014
Version 1Show Document
  • View in full screen mode

Protect Microsoft Exchange 2013 using Symantec Netbackup 7.6.0.1

This tech note shows how you can use Symantec Netbackup 7.6.0.1 on Hitachi Virtual Storage Platform G1000 to protect your Microsoft® Exchange 2013 databases from logical corruption or accidental deletion for 2,000 mailboxes in a database availability group environment.

Symantec Netbackup is an enterprise level heterogeneous backup and recovery data protection application. It provides cross-platform backup functionality for a large variety of hypervisors, operating systems and applications. Netbackup provides the following features:

§  Central administration

§  Heterogeneous support

§  Media and device management

§  Exchange DAG support

§  Reporting


NoteTesting of this configuration was in a lab environment. Many things affect production environments beyond prediction or duplication in a lab environment. Follow the recommended practice of conducting proof-of-concept testing for acceptable results in a non-production, isolated test environment that otherwise matches your production environment before your production implementation of this solution.

Solution Components

Symantec Netbackup is an enterprise level heterogeneous backup and recovery data protection application. It provides cross-platform backup functionality to a large variety of hypervisors, operating systems and applications.

Figure 1 shows the Symantec Netbackup architecture using disk-based backup to backup Exchange databases to Hitachi Virtual Storage Platform G1000.

        nbu diagram.png                    

Figure 1.

 

Table 1 lists the hardware components used in this solution.

 

Table 1. Hardware Components

              

Hardware

Description

Version

Quantity

Hitachi Virtual Storage Platform Hitachi   Virtual Storage Platform G1000

§  Dual controllers

§    6 × 8 Gb/sec Fibre Channel ports

§  110 GB cache memory

§  48 × 3 TB SAS disks

80-01-24-00

1

Hitachi Compute Blade 500 chassis

§  8-blade chassis

§  2 management modules

§  6 cooling fan modules

§  4 power supply modules

§  2 Brocade 5460 Fibre Channel switch   modules

§  2 Brocade 10 GbE DCB switch modules

SVP: A0135-D-6829

1

520H B2 server blade

§  Half blade

§    2 × 12-core Intel Xeon E5-2697 v2   processor, 2.70 GHz

§  192 GB RAM

§  Emulex 10 GbE CNA onboard network   adapter

§    Hitachi 8Gb/sec Fibre Channel Mezzanine Card

04-05

2

 

Table 2 lists the software components used in this solution.

 

Table 2. Software Components

                      

Software

Version

Symantec Netbackup

7.6.0.1

Hitachi Dynamic Provisioning

VSP G1000 microcode dependent

Hitachi Storage Navigator

VSP G1000 microcode dependent

Microsoft Windows Server®

2012 R2 Datacenter

Microsoft Windows Server®

2012 R2 Standard

Microsoft Exchange Server

2013 SP1 Enterprise

Microsoft System Center

2012 R2

Microsoft System Center Virtual   Machine Manager

2012 R2

Microsoft SQL Server®

2012

Test Environment Configuration

 

The test environment consisted of the following:

§  Two server blades were configured for Microsoft Hyper-V with clustered share volumes presented to both hosts.

§  Two Microsoft Exchange virtual machines were installed as combined mailbox and client access roles

§  One Symantec Netbackup virtual machine was configured to backup Exchange databases via disk-based backup

 

Hitachi Virtual Storage Platform G1000 Configuration

Four Hitachi Dynamic Provisioning (HDP) pools were configured as RAID 10 (2D+2D) on the storage using forty 3 TB 7.2k disks The configuration details for the pools are listed in Table 3.

 

Table 3. Virtual Storage Platform G1000 HDP Pool Configuration

             

HDP   Pool

Number   of Drives

Pool   Capacity  (TB)

Windows OS VHDX

4

5.3

Exchange active database

12

16

Exchange passive database

12

16

Disk-based backup

12

16

 

Microsoft Exchange Configuration

Eight 700 GB databases were configured on two Exchange mailbox virtual machines. Each database had 500 1 GB mailboxes. The configuration details for the database distribution are listed in Table 4.

 

Table 4. Exchange Database Distribution

                

DAG

Server    1

Server    2

Active database

db1

db3

db2

db4

Passive database

db3

db1

db4

db2

 

 

Use Cases Tested

 

These are the use cases tested for protecting Microsoft Exchange 2013 with Hitachi Application Protector.

Create a Full Backup to Backup Active Databases

The objective of this test was to schedule and manually run a full backup of the active databases.

The backup completed successfully. It took on average 2 hours to backup two 700 GB Exchange databases.

Create a Full Backup to Backup Passive Databases

The objective of this test was to schedule and manually run a full backup of the passive databases.

The backup completed successfully. It took on average 1.5 hours to backup two 700 GB Exchange databases.

Restore a Database to its Orginal Location

The objective of this test was to recover and overwrite the existing active database. A use case for this restore is due to a logical corruption or accidental deletion of a database. Prior to the restore, do the following:

§  Suspend the passive copy

§  Check to verify that this database can be overwritten by a restore

§  Dismount the active database

The restore completed successfully. It took an hour to restore 700 GB.

Restore a Database to a Different Location

The objective of this test was to recover a database to an alternate location. Prior to the restore, do the following:

Create a recovery database by running these Powershell commands.

§  New-MailboxDatabase -Recovery -Name recovery db name -Server mailbox server name -EdbFilePath "database path"-LogFolderPath "log path"

§  Mount-database recovery db name

The restore completed successfully. It took an hour to restore 700 GB.

Granular Email Recovery

Granular email recovery is not supported on version 7.6.0.1. It will be available in the next release version.

Attachments

    Outcomes