You are on page 1of 110

Veritas Backup Exec 20.

1: Administration
(Agents and Features)

Lesson 03: Protecting Microsoft Exchange Server

© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or
its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
Lesson introduction
Install and Configure
• Lesson 00: Course Introduction
• Appendix A: Storage Devices
• Lesson 01: Backup Exec Fundamentals
• Appendix B: Central Admin Server Feature
• Lesson 02: Licensing Backup Exec
• Appendix C: Remote Administration Console
• Lesson 03: Installing Backup Exec
• Lesson 04: Working with the Backup Exec Administration Agents and Features
Console
• Lesson 00: Course Introduction
• Lesson 05: Disk Storage Devices
• Lesson 01: Deduplication Feature
• Lesson 06: Cloud-based Storage Devices
• Lesson 02: Introduction to Remote Agent, Applications and
• Lesson 07: Network Storage Devices Databases
• Lesson 08: Disk and Network Storage Data Management • Lesson 03: Protecting Microsoft Exchange Server
• Lesson 09: Tape Devices and Tape Management • Lesson 04: Protecting Microsoft SQL Server
• Lesson 10: Backing up Data • Lesson 05: Protecting Microsoft SharePoint Server
• Lesson 11: Managing Servers and Jobs • Lesson 06: Protecting Microsoft Active Directory
• Lesson 12: Restoring Data • Lesson 07: Protecting Virtual Environments
• Lesson 13: Working with the Database Encryption Key • Lesson 08: Performing Virtual Machine Conversions
• Lesson 14: Simplified Disaster Recovery • Appendix A: Agent for Linux
• Lesson 15: Upgrading Backup Exec
Lesson objectives (1/2)
Topic Objective
Backup Exec Agent for Microsoft Explain the procedure and requirements for installing the agent for
Exchange: Installation Microsoft Exchange.

Backing up a DAG Describe how to backup a DAG.

Explain different backup selections available for Microsoft Exchange


Exchange backup selections
backups
State the different backup settings available in Backup Exec 20.1 to backup a
Exchange backup settings
Microsoft Exchange server.
Exchange Preferred Servers Only State the steps to configure the preferred server only backup option.
backups

Restoring Exchange Data Explain the different types of Microsoft Exchange restores available in
Backup Exec 20.1.
Exchange Database Restore Restore a Microsoft Exchange database.
GRT Browse Restore Perform a GRT browse restore.
GRT Search Restore Perform a GRT search restore.
Lesson objectives (2/2)
Topic Objective
Restore Considerations: GRT Explain the different options available in Backup Exec 20.1 for GRT restore.
Explain the different options available in Backup Exec 20.1 for Public Folder
Restore Considerations: Public Folders
restore.
Explain the different options available in Backup Exec 20.1 for Site Mailbox
Restore Considerations: Site Mailbox
restore.
Restore Considerations: Database Explain the option available for overwriting a database on a different
Overwrite Exchange server.
Explain the different options available in Backup Exec 20.1 for restoring to a
Restore Considerations: RDB
Recovery Database or RDB.
Restore Considerations: Disaster Perform disaster recovery for an Exchange server.
Recovery
Volume Shadow Copy State the role of Volume Shadow Copy or VSS in Exchange backups.
Troubleshooting: VSS Provider and Troubleshoot issues related to VSS Provider and Exchange writers.
Exchange Writer
Topic: Backup Exec Agent for Microsoft Exchange:
Installation

After completing this topic, you will be able to explain the procedure and
requirements for installing the agent for Microsoft Exchange.
Installing the Agent for Microsoft Exchange
Backup Exec Component Installation

Backup Exec Component Install Target

Agent for Applications & Backup Exec server


Databases
Required on Exchange database servers
Agent for Windows
Not required on any Client Access Servers
Supported Microsoft Exchange server platforms

Microsoft Exchange Version Service Pack

Exchange 2010 SP1, SP2, and SP3


CU3, CU5, CU6, CU7, CU8, CU9, CU10, CU11,
Exchange 2013
CU12,CU13,CU14 and SP1
Exchange 2016 CU1, CU2 and CU3

CU1 and CU2 are for Exchange


CU = Cumulative Update 2013 not supported.

For the updated supported Microsoft Exchange server platforms list –


Backup Exec 20.1 Software Compatibility List
Permissions

Exchange 2016 Exchange 2013 Exchange 2010

Local Admin on Yes Yes Yes


Exchange server

Domain Admin Yes Yes Yes

Exchange Admin Organization Management Role suggested


Minimal Permissions required

Unique Mailbox and Yes Yes Yes


Visible in Global
Address List
Topic: Backing up a DAG

After completing this topic, you will be able to describe how to backup a
DAG.
Adding an Exchange DAG in Backup Exec
Client Access Server
(CAS) Role: Secondary Site
All clients connect using Client Access
CAS Server DB1
DB3
Mailbox Role Mailbox DB5
Primary Site
• Host Mailboxes Server 6
Client Access Server • Failover managed
within Exchange

Mailbox Mailbox Mailbox Mailbox Mailbox


Server 1 Server 2 Server 3 Server 4 Server 5

DB1 DB4 DB2 DB5 DB3


Database DB2 DB5 DB3 DB1 DB4
centric DB3 DB1 DB4 DB2 DB5
failover
Adding DAG to Backup Exec: Add

1. Add 2. Which type 3. Establish


4 5 6 7 8
of Server Trust
Adding DAG to BE: Which type of server

1. Add 2. Which type 3. Establish


4 5 6 7 8
of Server Trust
Adding DAG to BE: Establish Trust

1. Add 2. Which type 3. Establish


4 5 6 7 8
of Server Trust
Adding DAG to BE: DC containing the forest

3. Establish 4. DC containing 5. Logon


1 2 Trust the forest Account 6 7 8
Adding DAG to BE: Logon Account

3. Establish 4. DC containing 5. Logon


1 2 Trust the forest Account 6 7 8
Adding DAG to BE: Participating servers

6. Participating 7. Upgrade and


1 2 3 4 5 Servers 8. Summary
Restart
Adding DAG to BE: Upgrade and Restart

Note: When you add a Microsoft Exchange database


availability group, it is recommended that you manually
reboot each Exchange Server, if required, after installing the
Agent for Windows. If you select to automatically reboot
after install, all the Exchange Servers in the DAG may reboot
at the same time.

6. Participating 7. Upgrade and


1 2 3 4 5 Servers 8. Summary
Restart
Adding DAG to BE: Summary

6. Participating 7. Upgrade and


1 2 3 4 5 Servers 8. Summary
Restart
Support for Exchange DAG on Hyper-V and VMware virtual
machines
For Exchange Backing up an
GRT, the individual
DAG backups
Agent for Member
include
Windows Server does
clustered
must be not include
resources
installed on clustered
(mailbox
each resources
databases)
Member that are on
Server that machine

If the Member Servers is virtual:


• To fully protect it, select from the virtual host; backups will use the
Agent for Virtual Machines instead of the Agent for Windows.
• Exchange data from the Member Server will be included in this backup.
Topic: Exchange backup selections

After completing this topic, you will be able to explain different backup
selections available for Microsoft Exchange backups.
Select DAG or Stand-alone server
DAG

Standalone
Test/Edit Credentials
DAG Standalone
Logon Account
DAG

Standalone
Edit Selections
DAG Standalone
Selections: Exchange DAG
DAG

Standalone
Public Folders

Exchange 2013 and Exchange 2016:


Public Folders are a mailbox within a
Mailbox Database

Exchange 2010:
Public Folders are a
Database
Site Mailbox
Exchange 2013:
Site Mailbox is a
mailbox within a
Mailbox
Database

Note: To protect a
Site Mailbox, both
Exchange 2013 and
SharePoint 2013
must be backed up
at the same point-in-
time.

TechNet – Site Mailbox


Topic: Exchange backup settings

After completing this topic, you will be able to state the different backup
settings available in Backup Exec 20.1 to backup a Microsoft Exchange
server.
Edit Backup Settings
Exchange Backup Settings
Backup Methods

Note: Differential or Incremental backups


of Exchange Databases cannot be
performed if circular logging is enabled.
Database files

Database logs: .edb Transaction logs: .log

• Active Exclusion: File backup skips active database files.


• Must be protected by Database Agent.
Transaction logs

Only Exchange Full


and Incremental
backups Truncate
Exchange logs
Consistency check

• Run by Exchange
• Reported in the Job Log
Active or Passive server
Snapshot

If the Use snapshot technology check box is not selected for the
backup job, Backup Exec continues to use VSS snapshot for Exchange
backups.
Granular Recovery Technology
Ensure GRT is enabled.

Storage Device: An NTFS Disk Storage or Backup Exec Deduplication storage is recommended.
Tape, OST, Cloud or FAT32 Disk storage will require Staging during restore
Instant GRT and full Catalog
Not supported to tape
or any device that
requires staging.
Example: OST
Backup: Instant GRT: Best Practice

Use the Search Wizard to


find items to restore after
the full catalog operation
is complete.

Best Practice:
• Run a full catalog operation as a separate job immediately after the backup job
finishes or
• Daily, early morning after the backup window ends
Topic: Exchange Preferred Servers Only backups

After completing this topic, you will be able to state the steps to configure
the preferred server only backup option.
Preferred server only backup option
Exchange Active and Passive copies

Example 1 Example 2

EXCHMB1 EXCHMB2 EXCHMB3 EXCHMB1 EXCHMB2 EXCHMB3


(Down)

Replication Replication

Replication
DB1 DB1 DB1 DB1 DB1 DB1
(Active) (Passive) (Passive) (Down) (Active) (Passive)

DAG member EXCHMB1 has failed


Exchange Database Availability
causing DB1 to become active on
Group.
EXCHMB2.
Preferred Servers

exchange.example.com
Preferred Servers: Manage
Preferred Server: Edit
Scenarios: Preferred Servers Only backup
PREFERRED

Scenario
Server 1 Server 2 Server 3

Replication
1
Replication
DB1 DB1 DB1
(Active)

Replication
Backup results are
2 Replication per each database.
DB2 DB2 DB2
(Active) (Bad Passive) (Good Passive)

3 Replication

DB3 DB3
(Passive) (Active)

Does not Does not


4 have a copy have a copy
of DB4 of DB4
DB4
(Active)
Topic: Restoring Exchange data

After completing this topic, you will be able to explain the different types of
Microsoft Exchange restores available in Backup Exec 20.1.
Restore
DAG

Standalone
What type of data
DAG

Standalone
Type of restore

Database

GRT Browse

GRT Search
Topic: Exchange Database restore

After completing this topic, you will be able to restore a Microsoft Exchange
database.
Database: Type of Restore

Database
Database: Select Database

Note that the range of log files


contained in the selected
backup set are displayed in the
right pane next to Logs
Database: Where to Restore
Performing a DAG redirect restore

The name of a member server or physical node needs to be entered and not the DAG
name.
Using the DAG name will fail the restore since there is no AAP and this wizard does
not prompt for Active Directory information.
Database: Purge Existing Transaction logs
Database: Temp location
Database: Bring Online

Yes – Sends a request to Exchange to mount and commit the database.


Exchange performs the actions.
Topic: GRT Browse restore

After completing this topic, you will be able to perform a GRT browse
restore.
GRT Browse

GRT Browse
GRT Browse: Selections

GRT allows restore of individual items from an Information Store


backup without having to restore the whole backup.
Performing a GRT restore for DAG

GRT browse for restore may show a mailbox named:


• SystemMailbox{8cc370d3-822a-4ab8-a926-bb94bd0641a9}
• The mailbox is associated with the Exchange AuditLog and is normally
hidden and should not be selected for restore.
GRT Browse: Where to Restore

Restore to a PST
GRT Browse: Overwrite existing mail

Original location setting

Redirect location setting


Topic: GRT Search restore

After completing this topic, you will be able to perform a GRT search
restore.
GRT Search

GRT Search
GRT Search results
Topic: Restore considerations: GRT

After completing this topic, you will be able to explain the different options
available in Backup Exec 20.1 for GRT restore.
GRT redirect to PST
Restore to:
• Local Backup Exec Server or Remote Server
• Must have Microsoft Outlook installed
Outlook 2007, or 2010 32 bit only.
• Local file path on target server must be specified.

File naming convention


– PST file names = mailbox display name
– File name collisions are handled with (n) suffix. For example,
• John Doe [jdoe].pst
• John Doe [jdoe](1).pst
• John Doe [jdoe](2).pst

File size limitations


Maximum PST file size is 20 GB
Restores larger than 20 GB are split into multiple PST files.
GRT: Redirecting to Mailbox or Public Folder

• The specified mailbox or public folder must exist.


• The logon account must have rights to the destination.
Topic: Restore considerations: Public Folders

After completing this topic, you will be able to explain the different options
available in Backup Exec 20.1 for Public Folder restore.
Public Folder restore
Exchange 2010

Exchange 2013 and later

Public Folder Mailbox

The Public Folder content can


be spread across multiple
mailboxes. Browse for restore
will only show content for the
Public Public folder mailboxes that
Folders are present in the database
you are browsing

Mailbox Database
2013 and 2016: Public Folder restore structure
Parent Folder 1

PF1.1 Before Backup Exec restore


Public
Folder Public
PF1.2 Folder
Mailbox 1 PF1.3
Mailbox 2
Parent Folder 1

PF1.1
After Backup Exec restore Public Public
Folder PF1.2 Folder
Backup Exec restores all new child Mailbox 1 Mailbox 2
folders to the location of the parent.
Existing child folders go to their PF1.3
existing location.
2013 and 2016: Public Folder restore

Backup Exec 20.1 does not recreate Exchange 2013 Public Folder
mailboxes during the restore. The user must create the Public
Restore folder mailboxes manually. Then run the restore.
Behavior

The User can run the New-Mailbox command to create the Public
Folder mailboxes manually.
Command

For more information about the New- Mailbox command, refer to:
http://technet.microsoft.com/en-us/library/aa997663(v=exchg.150).aspx
Topic: Restore considerations: Site Mailbox

After completing this topic, you will be able to explain the different options
available in Backup Exec 20.1 for Site Mailbox restore.
Backing up a Site Mailbox

Exchange 2013 and SharePoint 2013 introduced Site Mailboxes

To protect the content of a Site Mailbox, both Exchange 2013 and


SharePoint 2013 must be backed up at the same point-in-time

• Mail content is saved in Exchange Mailbox


• File content is saved in SharePoint

The Pointers for objects must match in both Exchange and


SharePoint
Restoring a Site Mailbox
The Site Mailbox must be manually created in SharePoint 2013. Backup Exec 20.1
does not recreate the Site Mailboxes during a restore. Users must recreate the Site
Mailbox manually.

SharePoint restore job – Restores the file content.

Exchange restore job – Restores the e-mail content.

Backup Exec does not support the redirected restores of items and SharePoint
document references to another location in conjunction with a restore of the related
Exchange items.
Topic: Restore considerations: Database Overwrite

After completing this topic, you will be able to explain the option available
for overwriting a database on a different Exchange server.
2010: Enabling Exchange Database Overwrite

1. Open the Exchange


Management Console
utility 2010.
2. Right-click the database
that you want to
overwrite.
3. Click Properties.
4. For Exchange 2010, on
the Maintenance tab,
select This database can
be overwritten by a
restore.

Set-MailboxDatabase DB1 -AllowFileRestore:$True
2013 and 2016: Enabling Exchange Database Overwrite
1. Open the Exchange
2013 Administration
Center.
2. Click on the Databases
tab.
3. Select the database
you want to overwrite.
4. Click Edit.
5. Select Maintenance
from the left pane.
6. Select the This
database can be
overwritten by a
restore check box.

Set-MailboxDatabase DB1 -AllowFileRestore:$True
Topic: Restore considerations: RDB

After completing this topic, you will be able to explain the different options
available in Backup Exec 20.1 for restoring to a Recovery Database or RDB.
Exchange 2010 and later: RDB and redirecting exchange restore data

Do not mount mailbox stores in the RDB before the restore.

New-MailboxDatabase -Recovery -Name Recover2 -Server 
Server1 -EdbFilePath "G:\recover2\recover.edb

Backup Exec cannot backup Recovery Databases.

Requirements for redirecting Exchange storage group and database restores:


• The storage groups and databases must already exist on the destination server, and
must have the same names as the original storage groups or databases.
Redirecting
• The destination databases must be configured so that they can be overwritten.
exchange
restore data
A version of Exchange server database cannot be redirected to a different
version of the Exchange server database.
Topic: Restore considerations: Disaster Recovery

After completing this topic, you will be able to Perform disaster recovery for
an Exchange server.
Performing disaster recovery for Exchange

1. Recover the Windows server first.


2. Verify the Microsoft Exchange Information Store service is started.
3. Launch Backup Exec.
4. Catalog the backup sets of the Exchange Server storage groups you
want to recover.
5. Run the Restore Wizard.
6. Select the Full and all subsequent incremental backup sets.

Disaster recovery of an Exchange Server


Topic: Volume Shadow Copy

After completing this topic, you will be able to state the role of Volume
Shadow Copy or VSS in Exchange backups.
Snapshot
An Exchange Database backup requires a VSS Snapshot.

The VSS Exchange Writers must be stable to be able to create the snapshot.

VSS: A set of COM based APIs:


1. Providers:
• System Microsoft
• Software
• Hardware
2. Requestors
• Backup software
3. Writers
• For the object being backed up
Exchange VSS Writers
Issue the command Vssadmin.exe list writers from the command prompt on the
Exchange server, to get the state of the Exchange writers.

Microsoft Exchange Writer

Database Restores are performed by the Microsoft Exchange Writer.

Microsoft Exchange Replica Writer


Exchange Active/Passive Snapshots

Exchange 2010 Exchange 2013 and Exchange 2016


Active database Microsoft Exchange Writer Microsoft Exchange Writer
Passive Exchange Replica Writer Microsoft Exchange Writer
database

Note: Exchange 2013 onwards


does not include an Exchange
Replica Writer.
Exchange Services Host VSS Writers
Which Service hosts the Writers
– Which one can be restarted to reset the Writer
Writer Exchange 2010 Exchange 2013 Exchange 2016

Microsoft Microsoft Exchange Microsoft Microsoft


Exchange Writer Information Store Exchange Exchange
Note: If you restart the Replication Replication
Information Store service,
the database will be offline
during the service restart.
Exchange Replica Microsoft Exchange N/A N/A
Writer Replication
(passive copy)

Exchange 2013 onwards, the Microsoft Exchange writer is hosted by the


Replication service.
Offline Database Discovery
Prior to Exchange 2013, VSS did not discover an
offline dismounted database.

However, Exchange 2013 onwards, an offline


dismounted database is discovered.

Note: The backup fails during the database discovery


as the database is required to be online during a
backup.
Database state and recovery process
A clean shutdown state requires all items to be in the database with
nothing left in the memory.

A dirty shutdown is performed on VSS Exchange backups since the


content is still in the memory during the freeze.

After the restore is completed, the Exchange writer performs a soft


recovery to play the logs and get to the point of what was in the
memory during the snapshot backup.

Hard recovery is a manual process, performed to instruct Exchange on


what logs to play (Requires Microsoft assistance).
Topic: Troubleshooting: VSS Provider and Exchange
Writer

After completing this topic, you will be able to troubleshoot issues related
to VSS Provider and Exchange Writer.
Check the Services
VSS – Volume Shadow Copy

Microsoft VSS Provider – Microsoft


Software Shadow Copy Provider

Exchange version Exchange node Exchange Writers used


2016 Active/Passive Microsoft Exchange Replicaiton
2013 Active/Passive Microsoft Exchange Replication
2010 Active Microsoft Exchange Information Store
2010 Passive Microsoft Exchange Replication
VSSadmin list providers

Sample Software
provider

Sample Hardware
provider
VSSadmin list writers
Microsoft Exchange Writer
• Active and Passive backups in 2013 and 2016
• Active backups for 2010
• All Database Restores are done by Microsoft Exchange Writer

Microsoft Exchange Replica Writer


Passive backups for Exchange 2010

Check for the State and the Last Error.

Failed writer
VSS Resets
If a problem is found with VSS:

If not fixed, restart the


Restart the service for that If restarting the service
Store service – Exchange
Writer. This clears most does not fix the issue,
remains offline during
writer issues. reboot the server.
restart.

Please note that these resets only clear the bad state.
– The cause for the occurring of the bad state may still exist and may cause the
problem again.
– The source of the problem must be resolved to prevent the issue from re-
occurring.
TechNotes for VSS Troubleshooting

• TechNet - Troubleshooting the Volume Shadow Copy Service.


• TechNet - VSSTester.ps1 script validate Exchange 2010 VSS writers.
• Technote-
Volume Shadow Copy Service (VSS) Information and Troubleshooting VSS issues.
Lesson summary
• Key points
– In this lesson, you learned about the procedure of adding an Exchange server or Database Availability
Group to the Backup Exec Server list.
– You also learned about the different backup selections, backup settings, and restore settings available
for Microsoft Exchange backups.
– In addition, you learned about the different options available in Backup Exec 20.1 for GRT restore, Public
Folder restore, Site Mailbox restore, overwriting a database, restoring to a Recovery Database and
performing Exchange disaster recovery .
– Finally, you learned about the role of Volume Shadow Copy or VSS in Exchange backups.
• Reference materials
– Veritas Backup Exec Technical Support:
https://www.veritas.com/content/support/en_US/BackupExec.html
– Veritas Backup Exec Master Compatibility List:
https://www.veritas.com/support/en_US/article.000017788
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.
Question 1: Preferred Server Only backups
The Preferred Server Only Backup option applies only to?

A. Exchange Database Availability Group


B. Exchange Local Continuous Replication
C. Exchange Cluster Continuous Replication
D. Exchange Single Copy Cluster
Answer 1: Preferred Server Only backups
The Preferred Server Only Backup option applies only to?

A. Exchange Database Availability Group


B. Exchange Local Continuous Replication
C. Exchange Cluster Continuous Replication
D. Exchange Single Copy Cluster

The correct answer is A. The Preferred Server Only Backup option only applies to Exchange Database Availability Group.
Question 2: Preferred Server Only backups
In a DAG environment, there are 3 servers with servers 2 and 3 listed as preferred.
Database is on server 1 with passive copies on server 2 and server 3, which copy will be
backed up?

A. Server 1
B. Server 2
C. Server 3
Answer 2: Preferred Server Only backups
In a DAG environment, there are 3 servers with servers 2 and 3 listed as preferred.
Database is on server 1 with passive copies on server 2 and server 3, which copy will be
backed up?
A. Server 1
B. Server 2
C. Server 3

The correct answer is B.


Question 3: Exchange backup settings
An instant GRT job captures GRT information for:

A. All backup sets


B. Only first backup set
C. Only the most recent backup set
D. None of the backup sets
Answer 3: Exchange backup settings
An instant GRT job captures GRT information for:

A. All backup sets


B. Only first backup set
C. Only the most recent backup set
D. None of the backup sets

The correct answer is A. An instant GRT job captures GRT information for all backup sets.
Question 4: Backing up a DAG
When you add a Microsoft Exchange DAG, you must select the option to automatically
reboot the Exchange Servers after installing the Agent for Windows.

A. True
B. False
Question 4: Backing up a DAG
When you add a Microsoft Exchange DAG, you must select the option to automatically
reboot the Exchange Servers after installing the Agent for Windows.

A. True
B. False

The correct answer is B. When you add a Microsoft Exchange DAG, it is recommended that you manually reboot each
Exchange Server, if required, after installing the Agent for Windows. If you select to automatically reboot after install, all
the Exchange Servers in the DAG may reboot at the same time.
Lab 03: Protecting Microsoft Exchange Server
• Exercise A: Viewing the Exchange DAG configuration (optional)
• Exercise B: Adding an Exchange DAG to Backup Exec
• Exercise C: Backing up an Exchange DAG
• Exercise D: Restoring Exchange mailbox items
• Exercise E: Restoring Exchange mailbox items using Search
• Exercise F: Performing a redirected restore of Exchange databases and logs
End of presentation

You might also like