Upload
branden-marsh
View
215
Download
2
Embed Size (px)
Citation preview
Exchange 2013(backup &)
Disaster Recovery
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Agenda
• Exchange Data Types & Storage Locations
• Backup• Disaster Recovery• Hybrid…
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
DATA TYPES & STORAGE LOCATIONS
What files are important and which ones are not?
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Data types
User Data
• Emails• Contacts• Holiday pictures• (everything in a user’s
mailbox…)
Configuration Data
• Local Configuration Data (server-specific)
• Global Configuration Data (environment-specific)
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
User Data
• Data stored in Mailbox Database, Transaction Logs (and memory)
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Why transactions logs matter
• Exchange doesn’t update databases immediately (lazy writes)– User actions are written to transaction log files
first– Logs are ‘rolled’ into the database on the go,
but there might be a lag (checkpoint depth)
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Why transactions logs matter
#devconnections
DB01E00.log
E00x
E00E0
0E00E0
0E001
CHK1
2
3
4
5
EXCHANGE 2013 DISASTER RECOVERY
Backups & circular logging
• Circular logging removes log files which have been committed to the database– Potentially dangerous scenario *
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Backups & circular logging
#devconnections
DB01E00.log
E00x
E00E0
0E00E0
0E001
CHK1
2
34
5
E001
5
EXCHANGE 2013 DISASTER RECOVERY
Configuration data
• Configuration data stored in multiple locations:– Local Configuration Data
• server’s registry• Local files on the system
– Global Configuration Data• Stored in Active Directory
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Local Configuration Data• Most of the items in the
registry are stored in the same location:– HKLM:\Software\Microsoft\
ExchangeServer\v15• i.e. used to store M.A.
overrides
– HKLM:\System\CurrentControlSet\Services\MSExchange*• Service-specific settings
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Local Configuration Data• Configuration files stored under
Exchange installation folder: <drive>:\Program Files\Microsoft\Exchange Server\v15
• commonly-used files include:– Web.config (OWA)
• ..\ClientAcces\Owa
– CmdletExtentionAgent(s)• ..\ Bin\CmdletExtentionAgents
– Managed Availability• ..\ Bin\Monitoring\Config
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Global Configuration data• Forest Configuration Partition:
– CN=OrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=tld
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
BACKUP & RESTOREHow to bring my data into safety?
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Need for backup?
• Despite many stories about backup-less environments, backup still valid/useful for:– Historical restores– Deleted item (beyond retention time)– Legal– Purging Transaction Logs
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
What to backup?
• User Data• Configuration Data *• Optionally:– System State (Server’s Registry)– Log Files– Certificates
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Exchange 2013 Backups• Leverage a technology called VSS
– VSS “Copy-on-Write”
• Uses VSS Writer (since Exchange 2007)– part of the MSExchangeRepl service in 2013– Responsible for ‘talking’ to Exchange and
temporarily halting writes (to the database) to ensure consistency
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
High-level stepsVSS
Requestor (Backup App)
1Volume
Shadow Copy Service (VSS)
VSS Provider(hard- or software)
VSS Writer(Exchange)
Storage
Storage
Storage
2
3
4
56
EXCHANGE 2013 DISASTER RECOVERY
DISASTER RECOVERYHelp?! I’m on fire… What now?!
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
DRP! Anyone?
“A disaster recovery plan (DRP) is a documented process or set of procedures to
recover and protect a business IT infrastructure in the event of a disaster.” ~
Wikipedia
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Exchange DR procedures• Full DRP for Exchange includes:– Recovery of Mailbox, Database, Server(s)– Recover from full transaction log or database
disk– Dial Tone Recovery, Database Portability– (Re-)Seeding Database (w/ or w/o AutoReseed)– Site Recovery + Switch back
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Deleted Object Recovery• Depends on what object was deleted• Mailbox(es)
– Deleted mailbox retention allows to easily ‘reconnect’ mailbox to user account.
– Beyond retention, restore from backup is necessary
• User(s)– same process as Mailbox recovery, but user needs to be
restored first.– Beyond tombstone period > recover from AD backup first OR
connect mailbox to different user account
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Deleted Objects• Exchange Security Groups– Use Setup.exe /prepareAD to restore the
deleted groups
• Exchange RBAC Groups– Install-CannedRbacRoleAssignments will
restore the groups (not the memberships though!)
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Dial Tone Recovery• Use to quickly restore service to users (while
waiting for data recovery)1. Mount empty database to recover service to the users
(and while waiting to restore data)2. Recovery data into Recovery Database3. Swap Dial Tone database and Recovery Database4. Merge data from Dial Tone database and Restored
database
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Database portability• Exchange databases can be mounted on any
server in the organization with the same database schema.
• Can be useful in the Dial Tone Recovery procedure when the server cannot be restored/recovered (quickly)– Same process as ‘regular’ dial tone recovery, but mount
Dial Tone + Recovery Database on other server
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Server Recovery Process• Using the /m:recoverserver switch:
1. Repair failed server. If replaced, make sure the original server is not reconnected to the network.
2. Join replacement server to the domain w/ same name (reset computer account)
3. Use the Exchange Setup.exe w/ /m:recoverserver switch (cli only)
4. Re-apply customizations• Import certificates• Restore customized files
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
DEMO TIME
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Hybrid
• Infrastructure / data is less important• Brings new challenges to the game– DirSync is the root of all evil *
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
DirSync
• Used to be a real pain• “accidental deletion protection” included
since version 6765.0006
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Accidental Delete Protection
• Built-in into DirSync• Set-PreventAccidentalDelete –Enable –
ObjectDeletionThreshold <value>– Forcing the deletions can be cumbersome in
large environments due to Full Sync that is required…
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
DEMO TIMEProtecting against the “oops-scenario”…
#devconnections
EXCHANGE 2013 DISASTER RECOVERY
Q&AThank you!
#devconnections
SESSION TITLE
#devconnections
Rate This Session Now!Rate with Mobile App:1. Select the session from the
Agenda or Speakers menus
2. Select the Actions tab
3. Click Rate Session
Rate Using Our Website:1. Register at www.devconnections.com/logintoratesession
2. Go to www.devconnections.com/ratesession
3. Select this session from the list and rate it
Tell Us What You Thought
of This Session
Be Entered to
WIN
Prizes!