Exchange QRC

8/13/2019 Exchange QRC

http://slidepdf.com/reader/full/exchange-qrc 1/7

Quick Reference Card

For internal circulation only

Backup to disk storage: Process Flow

1. Backup Exec job engine (BENGINE) on the Backup Exec server queries the Backup Exec Agent for Windows(BEREMOTE) on the Microsoft Exchange server as per the backup job submitted.

2. BEREMOTE with the help of MONAD runs a set of commands to check if the logon account used for the

backup job is a member of the Organization Management role, and has local administrator rights. These

commands also validate the list of Exchange items to be backed up from the Active Directory. Note that

the Backup Exec SP2 release allows lesser privileges to be defined and does not require the Organization

Management role.

3. Depending on whether the Exchange database is an active or a passive database, the snapshot is taken.

The required data is then backed up with the help of the snapshot. By default, Backup Exec selects the

best passive copy by referring to the preferred server list.

4. The backed up data is sent to BEREMOTE.

5. BEREMOTE transfers the data to BENGINE through the data connection.6. Catalog mining is performed and the information is sent to BENGINE.

SGmon Logging - I. Communcation between BENGINE and BEREMOTE

SGmon Logging - II. Microsoft Exchange Agent specific binaries in AWS

SGmon Logging - III. Snapshot Process

SGmon Logging - IV. Catalog Process




Backup to tape: Process Flow

1. Backup Exec job engine (BENGINE) on the Backup Exec server queries the Backup Exec Agent for Windows

(BEREMOTE) on the Microsoft Exchange server as per the backup job submitted.

2. BEREMOTE with the help of MONAD runs a set of commands to check if the logon account used for the

backup job is a member of the Organization Management role. These commands also validate the list of

Exchange items to be backed up from the Active Directory.

3. Depending on whether the Exchange database is an active or a passive database, the snapshot is taken.

The required data is then backed up with the help of the snapshot.

4. The backed up data is sent to BEREMOTE.

5. Catalog mining is performed.

6. BEREMOTE transfers the backed up data and metadata to BENGINE through the data connection.




Restore from disk storage: Process Flow

1. BENGINE collects GRT data as mentioned in the restore job from the IMG folders.

2. Virtual File Filter (VFF) and Extensible storage engine (ESE) send the requested GRT data back to BENGINE.

3. BENGINE queries BEREMOTE on the Microsoft Exchange server.

4. BEREMOTE with the help of the Exchange Web Services (EWS) retrieves the Microsoft Exchange database

and mailbox details.

5. The Microsoft Exchange database and mailbox detail is sent back to BEREMOTE.

6. BENGINE transfers the requested GRT data to BEREMOTE on the Microsoft Exchange server.

7. GRT data is copied to the Microsoft Exchange database.

SGmon Logging - II. GRT data collection

SGmon Logging - IV. Exchange data copy to the Exchange database

EWS Logging - III. Database and Mailbox retrieval




Restore from tape: Process Flow

1. BENGINE writes GRT data to a staging (temporary) location. The Microsoft Exchange database is then

mounted and the GRT data is collected.

2. Virtual File Filter (VFF) and Extensible storage engine (ESE) send the requested GRT data back to BENGINE.

3. BENGINE queries BEREMOTE on the Microsoft Exchange server.

4. BEREMOTE with the help of the Exchange Web Services (EWS) retrieves the Microsoft Exchange database

and mailbox details.

5. The Microsoft Exchange database and mailbox detail is sent back to BEREMOTE.

6. BENGINE transfers the requested GRT data to BEREMOTE on the Microsoft Exchange server.

7. GRT data is copied to the Microsoft Exchange database.




Backup to disk storage: SGmon log

I. Communcation between BENGINE and BEREMOTE

II. Microsoft Exchange Agent specific binaries in AWS

III. Snapshot Process

IV. Catalog Process




Restore from Disk: SGmon log

II. GRT data collection

IV. Exchange data copy to the Exchange database




III. Database and Mailbox retrieval: EWS Log

Gathering Exchange Environment information

Prior to troubleshooting Microsoft Exchange issues, you must gather the following information:

What is the version and patch level of the Microsoft Exchange application? Does the Exchange Management Tools on the Backup Exec server match the Exchange server? Is the issue related to backup or restore? What type of backup storage is used? Is it tape, disk, deduplication, or OST? How many servers are part of the Exchange setup? What are the server names and what role is assigned to each server?

Backup Exec 2012 - Microsoft Exchange best practices

1. First, backup Microsoft Exchange data to disk and then copy to tape (D2D2T) for optimal performance.

2. Use a 64-bit Backup Exec server (hardware and operating system) for Exchange 2010 and Exchange 2013.

3. Leverage a separate network for backups (prevents saturation, improves performance).

4. Protect the Active Directory infrastructure in addition to Exchange components.

5. Enable Granular Recovery Technology for optimal recovery flexibility.

6. Ensure all required Backup Exec logon account permissions are configured properly.

7. Uniquely named mailbox is required for Exchange Granular Recovery.

8. For high-availability configurations, protect the passive copy of mailbox servers and databases.

9. Exchange Management Tools may be required on the Backup Exec server.

10. When firewall access is required, ensure ports are configured properly.

Refer to Best practices for Backup Exec 2012 Agent for Microsoft Exchange Server for more information.

http://www.symantec.com/docs/HOWTO74428




Documents

Exchange QRC