Tivoli Storage Manager for MailTivoli Storage …tsm-symposium.oucs.ox.ac.uk/2007/papers/Del Hoobler...

Tivoli Storage, IBM Software Group

Tivoli Storage Manager for MailTivoli Storage Manager for Mail --Data Protection for Exchange: A Look Under the Hood

Del HooblerOxford University TSM Symposium 2007September 2007

© 2007 IBM Corporation


DisclaimerDisclaimer

This presentation describes potential future enhancements to the IBM Tivoli Storage Manager family of productsStorage Manager family of products

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice and represent goals and objectiveschange or withdrawal without notice, and represent goals and objectives only

Information in this presentation does not constitute a commitment to deliver pthe described enhancements or to do so in a particular timeframe

IBM reserves the right to change product plans, features, and delivery h d l di t b i d d i tschedules according to business needs and requirements

This presentation uses the following designations regarding availability of potential product enhancementspotential product enhancements– Planned 5.5: Planned for delivery in TSM v5.5 (2007) – Next Release Candidate: Candidate for delivery in the next release after v5.5

Future Candidate: Candidate for delivery in future release

© 2007 IBM Corporation2 Tivoli Storage Manager for Mail - Data Protection for Exchange

– Future Candidate: Candidate for delivery in future release


Presentation ContentsPresentation Contents

This presentation covers details on IBM Tivoli Storage s p ese tat o co e s deta s o o Sto ageManager for Mail - Data Protection for Exchange.

It provides a brief history of the product, its functions and features best practices and what the future holdsfeatures, best practices, and what the future holds.



Presenter InformationPresenter Information

Del Hoobler

– IBMer since 1989, TSMer since 1991

– IBM Tivoli Storage Manager Development Team Lead

– Data Protection for Exchange Server

– Data Protection for SQL Server

– TSM for Copy Services


– TSM for Copy Services


AgendaAgenda

Microsoft Exchange Server - Background / Architectureg g

Data Protection for Exchange

DP for Exchange - Functions and Features

DP for Exchange - A Look Under The Hood

DP for Exchange - Strategies and Best Practices

DP for Exchange - FuturesDP for Exchange - Futures

Questions and Answers



Microsoft Exchange Server - BackgroundMicrosoft Exchange Server Background



Microsoft Exchange Server - Backgroundg g

What is Exchange Server?

– Messaging (email) and collaboration application

– Supported on Windows “Server” Operating Systems

History

– Exchange Server 5.5 – 1998

– Exchange Server 2000 – 2000





Microsoft E change Ser er Architect reMicrosoft Exchange Server – Architecture

Exchange Server topology is tightly integrated with:– Active Directory

– DNS

Exchange hierarchical structure

– “Servers” contain “Storage Groups”

– “Storage Groups” contain “Databases”

– “Databases” contain “Mailboxes”



Microsoft Exchange Server – ESM GUI Screenshot*Microsoft Exchange Server ESM GUI Screenshot

*This example was taken from

the Exchange System Manager GUI

on Exchange Server 2003



Microsoft Exchange Server – Architecture

Exchange Servers contains “Storage Groups”Exchange Servers contains Storage Groups– Before Exchange 2007: Max 4 storage groups per server

Exchange 2007: Max 50 storage groups per server– Exchange 2007: Max 50 storage groups per server

“Storage Groups” contains DatabasesStorage Groups contains Databases – Two Database Types: “Mailbox” and “Public Folder”

Before Exchange 2007: Max 5 databases per storage group– Before Exchange 2007: Max 5 databases per storage group

– Exchange 2007: Max 50 databases per server allowed

Exchange 2007: Microsoft recommends 1 database per storage group– Exchange 2007: Microsoft recommends 1 database per storage group



Microsoft Exchange Server – Architecture

“Databases” are made up of databases filesDatabases are made up of databases files

– Based on Microsoft’s ESE (“JET”) database technology( ) gy

– .EDB file – rich-text database (MAPI content)( )

– .STM file – native content database (non-MAPI)Thi fil i l d i E h S 2007• This file is no longer used in Exchange Server 2007

– .LOG files – transaction log filesg• Before Exchange 2007: Log files are 5 MB• Exchange Server 2007: Log files are 1 MB



Microsoft Exchange Server – Backup Architecture

Exchange supports two (2) backup architectures:Exchange supports two (2) backup architectures:

1 Legacy (streaming) backups1. Legacy (streaming) backups– Special “backup” and “restore” API

Interfaces with ESE to provide consistent backup– Interfaces with ESE to provide consistent backup

– Will be going away in some future release of Exchange

2. Volume Shadow Copy Service (VSS) backups– Utilizes Microsoft’s generalized snapshot architecture– Utilizes Microsoft s generalized snapshot architecture

– Started with Exchange Server 2003



New Exchange Server 2007 FeaturesNew Exchange Server 2007 Features

LCR – Local Continuous Replication

CCR – Cluster Continuous Replication

SCR - Standby Continuous Replication (Exchange Server 2007 SP1)

Changes for backup are centered around replication and VSSChanges for backup are centered around replication and VSS

Exchange 2007 supports backing up using VSS from LCR/CCR replica database copiesdatabase copies

Note: Microsoft does not support backing up using legacy APIs from the replicasreplicas

Exchange 2007 supports VSS restores into a Recovery Storage Group



IBM Tivoli Storage Manager for MailIBM Tivoli Storage Manager for Mail

Data Protection for Exchange



Challenges for Protecting Vital DataChallenges for Protecting Vital Data

Application availability24x7availability of revenue generating applicationszero application downtime is expectedshrinking backup window

Increasing volume of database content complex database management

Amount of Data Backup Window

complex database managementbackup window no longer adequate

--Loss of vital business data because of

hardware errors (computer and disk)logical errors (software bugs, operator/administrator

)

-

errors, user errors)disaster (fire, water, earthquake) Mountains of critical data



Tivoli Storage Manager and ExchangeTivoli Storage Manager and Exchange

IBM Tivoli Storage Manager supports Exchange!

IBM Tivoli Storage Manager for Mail –g gData Protection for Microsoft Exchange

Sometimes referred to as “TDP for Exchange”

Almost 10 years old!

TSM for Copy Services is a complementary product that “enables” the VSS support for Data Protection for Exchange


enables the VSS support for Data Protection for Exchange


Data Protection for Exchange – Release Historyg yRelease Date Function

1 1 0 4/1998 Initial release of product1.1.0 4/1998 Initial release of product

Exchange Server 5.52 2 0 3/2001 Added Exchange 2000 support2.2.0 3/2001 Added Exchange 2000 support

Added Integrated Policy Management5.1.5 10/2002 Tighter Integration with BA Client

5.2.1 9/2003 Added Exchange 2003 Legacy Support

5.3.3 3/2006 Added Exchange 2003 VSS Support(Note: TSM for Copy Services is required for VSS operations)

5 4 1 5/2007 Added Exchange 2007 Legacy Support5.4.1 5/2007 Added Exchange 2007 Legacy Support

5.5.0 (Planned 5.5) Adding Exchange 2007 VSS Support(Note: TSM for Copy Services is required for VSS operations)


(2007) (Note: TSM for Copy Services is required for VSS operations)


Data Protection for Exchange Features - TodayData Protection for Exchange Features TodayBack up Exchange Server storage groups and transaction logs

S E h S 2003 L d VSS (*)Supports Exchange Server 2003 - Legacy and VSS (*)

Supports Exchange Server 2007 - Legacy

Maintain multiple versions of Exchange Server storage group and transaction log backups

R t t d t ti l b k d l thRestore storage group and transaction log backups and replay the transaction log files

Automatically inactivate previous backups when performing a full backupAutomatically inactivate previous backups when performing a full backup

Automate scheduled backups

*Note: VSS operations are “enabled” in the Data Protection for Exchange 5.3.3 (or later) interfaces when TSM for Copy Services is installed


5.3.3 (or later) interfaces when TSM for Copy Services is installed


Data Protection for Exchange Features - TodayData Protection for Exchange Features Today

Set automatic expiration of backup objects that are based on version limit d t ti i dand retention period

Monitor results through the Data Protection for Exchange activity log and automatically prune the activity log

Query a local Exchange Server or a Tivoli Storage Manager server for configuration information

Legacy restore of mailbox databases into the Exchange Server 2003 Recovery Storage Group (RSG)

Legacy back up and restore of Exchange Site Replication Service (SRS) databases

Supports MSCS and Veritas Cluster EnvironmentsSupports MSCS and Veritas Cluster Environments

Globalization Support



Data Protection for Exchange Features - TodayData Protection for Exchange Features TodayVSS Backup - Back up Exchange Server databases via snapshotsVSS Off loaded Backup Perform a VSS Backup to the Tivoli StorageVSS Off-loaded Backup - Perform a VSS Backup to the Tivoli Storage Manager server using an alternate machine instead of a production machineVSS R t R t VSS B k th t id Ti li StVSS Restore - Restore VSS Backups that reside on Tivoli Storage Manager server storage to their original locationVSS Fast Restore -Restore VSS Backups that reside on local shadow

l i fil l l h ivolumes using file-level copy mechanismsVSS Instant Restore - Restore VSS Backups that reside on local shadow volumes using hardware-assisted volume-level copy mechanismsg yA single graphical user interface for performing legacy and VSS backup, restore, and query operationsA single command line interface for performing legacy and VSS backupA single command line interface for performing legacy and VSS backup, restore, and query operations

Note: VSS operations require Data Protection for Exchange 5 3 3 (or later) and TSM for Copy


Note: VSS operations require Data Protection for Exchange 5.3.3 (or later) and TSM for Copy Services 5.3.3 (or later)


Data Protection for Exchange - Backup SupportData Protection for Exchange Backup SupportBackup Type

Database Logs Logs Truncated

TSM Legacy

S

TSM VSS

SType Truncated Support Support

Full

Copy

Incremental

Differential

DBCOPY



Data Protection for Exchange – GUI SampleData Protection for Exchange GUI Sample



Data Protection for Exchange – What’s Inside?Data Protection for Exchange What s Inside?



Data Protection for Exchange Overview - LegacyData Protection for Exchange Overview Legacy

DP forExchange

ExchangeS TSMTCP/IP

TSM Server Storage

Server TSM Server

TSM API

TSM Server Database

1. DP Exchange tells the Exchange Server that we want to back up a storage group.

2 E h S th i t d t ll DP f E h h t th2. Exchange Server prepares the environment and tells DP for Exchange what the “files” are to back up. This includes database and/or log files.

3. DP Exchange then opens the files using the Exchange backup/restore APIs.g p g g p

4. The DP Exchange multi-threaded, multi-buffered backup engine reads the data into buffers and hands the buffers to the TSM API.


5. The TSM API sends the data directly to the TSM server.


TSM VSS - Snapshot Support TopologyTSM VSS Snapshot Support Topology

ApplicationData

Local Snapshot Versions

Application Server

B k t

Backup Server

Data Versions

Snapshot Creation

Backup to TSM Server

Restore from Snapshot

Backup to Restore from TSM ServerRestore from TSM Server

Policy-based snapshot

management

TSM Server

Storage Hierarchy


Hierarchy


TSM VSS Component InteractionTSM VSS Component Interaction

Machine A (primary)Machine B (secondary)

SourceExchange

Server

Machine B (secondary)Volumes

S h t

DataProtection

F

VSS/VDS VSS/VDS

SnapshotVolumes

ForExchange

LocalDSMAgent

RemoteDSMAgent

TSM


TSMServer


Strategies and Best PracticesStrategies and Best Practices



Sample Legacy Backup StrategySample Legacy Backup Strategy

"COPY"-type legacy backups done once per month with proper policy binding for long term retentionpolicy binding for long term retention

"FULL" t l b k d k"FULL"-type legacy backups done once per week

"INCREMENTAL"-type legacy backups done one or more times per day

Restore Types Supported:

R t t li E h S th h l b k API– Restore to live Exchange Server through legacy backup API

– Restore to alternate location at file level (RESTOREFILES)



Sample Backup Strategy using both VSS and Legacy"COPY"-type legacy backups done once per month with proper policy binding for long term retention

"FULL"-type legacy backups done once per week

"FULL"-type VSS snapshot backups done once or more times per day– If multiple snapshots per day, may choose to move data to TSM

only once per day

R t T S t dRestore Types Supported:

– Restores from VSS snapshot backup • VSS “Instant Restore" (Requires IBM SVC or DS6000/DS8000 disk subsystem)VSS Instant Restore (Requires IBM SVC or DS6000/DS8000 disk subsystem)

• VSS “Fast Restore"• VSS Restore

Restores from Legacy backup– Restores from Legacy backup • Restore to live Exchange Server through legacy backup API • Restore into the Recovery Storage Group

R t t lt t l ti t fil l l (RESTOREFILES)


• Restore to alternate location at file level (RESTOREFILES)


Recommended Best PracticesRecommended Best PracticesSee Microsoft documentation for their best practices

Make sure you have a well defined and tested recovery plan that meets yourMake sure you have a well-defined and tested recovery plan that meets your service level objectives

Continue to schedule and perform a periodic legacy backup in your Exchange Server backup scheme

Place databases files on separate volumes from log files

Do not place database files or log files from multiple storage groups on the same "logical" volume or LUN

Do not place other "data" on Exchange storage volumesDo not place other data on Exchange storage volumes

Use archive logging rather than circular logging for maximum protection

Use the Recovery Storage Group to help minimize downtimey g p p

Use Exchange 2007 LCR and CCR to help reduce frequency of backups

Did I mention…. TEST your restores!



Exchange and “IMR”Exchange and IMR“IMR” = Individual Mailbox Restore

IMR describes a function to restore accidentally deleted individual Exchange mailboxes and individual mail items

O th d t hi thi i th h “b i k l l” b kOne common method to achieve this is through “brick-level” backups

But… your Exchange backup solution cannot just be at the brick level.You MUST have storage group/database level backupsYou MUST have storage group/database level backups.

Doing brick-level backups and database level backups require duplicate backup of dataof data

Microsoft has tried to remove the need for backing up at the item-level:– Deleted Item Restore– Deleted Item Restore– Deleted Mailbox Restore– Recovery Storage Group



TSM and “IMR”TSM and IMR

TSM provides “IMR” support through the MicrosoftTSM provides IMR support through the Microsoft Exchange backup and restore API along with the Microsoft built-in features tools and wizardsMicrosoft built in features, tools, and wizards

IBM recommends:

– Exploit the Deleted Item Retention Feature

Exploit the Deleted Mailbox Retention Feature– Exploit the Deleted Mailbox Retention Feature

– Use the Recovery Storage Group and Exchange Wizards to recover needed data

Want to know more? BOF session to discuss IMR© 2007 IBM Corporation32 Tivoli Storage Manager for Mail - Data Protection for Exchange

Want to know more? BOF session to discuss IMR


Data Protection for Exchange – What’s Next?Data Protection for Exchange What s Next?



Data Protection for Exchange – Planned 5 5 (2007)Data Protection for Exchange – Planned 5.5 (2007)

Add Exchange Server 2007 - VSS SupportAdd Exchange Server 2007 VSS Support

Windows x64-bit support

Exchange 2007 - VSS back up of replica copy of an LCR database

Exchange 2007 - VSS back up of replica copy of a CCR database

Exchange 2007 - VSS restore into a Recovery Storage GroupExchange 2007 VSS restore into a Recovery Storage Group

Exchange 2007 - VSS restore into an alternate storage group

Exchange 2007 - VSS restore into a relocated storage group



Other Useful SessionsOther Useful Sessions

TSM for Copy Services and TSM for Advanced CopyTSM for Copy Services and TSM for Advanced Copy Services: Today and Tomorrow

This is a deeper dive into Exchange VSS and TSM for Copy Services.

Exchange “IMR” Birds of a Feather (BOF) Session

This is an informal discussion about IMR related questions and positioning.


p g


For Further ReadingFor Further Reading

IBM Tivoli Storage Manager Main Product Web Pagehttp://www 306 ibm com/software/tivoli/products/storage mgr mail/http://www-306.ibm.com/software/tivoli/products/storage-mgr-mail/

Data Protection for Exchange Server Installation and User’s Guidehttp://publib.boulder.ibm.com/tividd/td/StorageManagerforMail5.3.3.html

Redbook - Using IBM Tivoli Storage Manager to Back Up Microsoft Exchange with VSShttp://www.redbooks.ibm.com/abstracts/sg247373.html

White Paper: IBM System Storage TSM solution for Exchange Server 2003 and DS6000/DS8000White Paper: IBM System Storage TSM solution for Exchange Server 2003 and DS6000/DS8000http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101009

White Paper: IBM System Storage TSM solution for Exchange Server 2003 and DS4000 Serieshttp://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS2451

IBM TSM for Mail Support Web Pagehttp://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforMail.html

Microsoft Exchange Server Main Web Sitehttp://www.microsoft.com/exchange/default.mspx



Questions and AnswersQuestions and Answers


Tivoli Storage Manager for MailTivoli Storage …tsm-symposium.oucs.ox.ac.uk/2007/papers/Del Hoobler...

Documents

Transcript of Tivoli Storage Manager for MailTivoli Storage …tsm-symposium.oucs.ox.ac.uk/2007/papers/Del Hoobler...