IBM Remote Data Protection and IBM Remote Data Express PART 1 IPS – Information Protection Services October 2008 © Copyright International Business Machines Corporation All rights reserved. IIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at Microsoft and SQL Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others.

© Copyright IBM Corporation 2008IBM Remote Data Protection 2 Topic  *Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 3 Objectives The result of this presentation for you:  An understanding of the technology, features, and functions for Remote Data Protection. With this knowledge, you will be able to successfully construct a solution and articulate the value of Remote Data Protection for your customers.

© Copyright IBM Corporation 2008IBM Remote Data Protection 4 Topic *Indicates current topic.  Introduction  *Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State

© Copyright IBM Corporation 2008IBM Remote Data Protection 5 Remote Data Protection 1.Remote Data Protection 2.Remote Data Protection Technology 3.How It Works 4.Target Customer

© Copyright IBM Corporation 2008IBM Remote Data Protection 6 Remote Data Protection (continued) Remote Data Protection is:  An Enterprise class data protection solution targeted at distributed data environments using disk storage as its medium for backup It is constructed of best of breed technologies:  EMC Avamar  IBM servers Enterprise Performance and Reliability Bringing distributed data into the data center

© Copyright IBM Corporation 2008IBM Remote Data Protection 7 Remote Data Protection (continued) Comparison - Remote Data Protection Express to Remote Data Protection Remote Data Protection Express Remote Data Protection Number of locationsUp to 3 locationsNo Limit Systems to be backed up Up to 5 production serversNo limit Data to be backed upUp to 150 GB/siteNo Limit Minimum Charge50 GBBased on solution Retention Points Standard Retention only (7-0-0, , 8-5-4) Standard plus option to customize Supported OSMS WindowsRef. Support Matrix Supported Database agents MS ExchangeMS Exchange + others

© Copyright IBM Corporation 2008IBM Remote Data Protection 8 Remote Data Protection (continued) The Remote Data Protection service provides:  Automatic data protection for remote/branch offices and mobile workforce  Solutions for servers and PCs  Security-enhanced, bandwidth-efficient, network-based daily backups to a Remote Data Protection platform  Comprehensive platform and database support  Powerful de-duplication and compression

© Copyright IBM Corporation 2008IBM Remote Data Protection 9 Remote Data Protection Technology EMC/Avamar  Backup and recovery software that utilizes data de-duplication 2-Stage Data De-Duplication  It is technology that identifies redundant data at the source.  Avamar’s term for their data de-duplication factoring is “commonality.”  Data is analyzed and de-duplicated at the bit level. Enables Remote Data Protection  Data is de-duplicated prior to leaving the protected host.  This results in very low bandwidth utilization, with much better efficiencies than competitors.  It leads to the ability to protect more data over the existing bandwidth.  Efficiencies occur with various data types.

© Copyright IBM Corporation 2008IBM Remote Data Protection 10 How It Works

© Copyright IBM Corporation 2008IBM Remote Data Protection 11 Target Customer What works well High Value Proposition  Environments where data has been distributed across many geographically dispersed locations What does not work well Diminished Value Proposition  Environments where data has been consolidated into a few data centers or customer premise environments  Large highly transactional environments—large transactional databases, large, very busy servers

© Copyright IBM Corporation 2008IBM Remote Data Protection 12 Topic  Introduction  Remote Data Protection  *Architecture Overview  Key Points  Initialization versus Steady State *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 13 Architecture Overview 1.Remote Data Protection Platforms 2.Remote Data Protection Architecture 3.Multi-Node versus Single-Node – When to Use

© Copyright IBM Corporation 2008IBM Remote Data Protection 14 Remote Data Protection Platforms Two platforms are available with the Remote Data Protection service. The Multi-Node Platform has a number of capacity options:  Remote Data Protection Single-Node Platform – Capacity = 1.5 TB  Remote Data Protection Multi-Node Platform – Capacity = 3, 4.5, 6, 7.5 and 9TB

© Copyright IBM Corporation 2008IBM Remote Data Protection 15 Remote Data Protection Architecture Remote Data Protection Single-Node Components  IBM Express™ x3650  Management Switch  Firewall 1.5 TB Platform

© Copyright IBM Corporation 2008IBM Remote Data Protection 16 Remote Data Protection Architecture (continued) Remote Data Protection Multi-Node Components  IBM Express x3650  Management Switch  Data Switch  Firewall 9 TB Platform

© Copyright IBM Corporation 2008IBM Remote Data Protection 17 Multi-Node versus Single-Node: When to Use Single-Node Platform - The most cost effective and easily scalable RDP solution  The Single-Node platform is less complicated, with fewer components, and smaller scale points, which means it is more flexible and more cost-effective.  It should be used as the default unless a Multi-Node configuration is required. Multi-Node Platform - Not as cost effective, but it can be deployed in larger single instances  This is to be used when the requirement is identified to support a single host that consumes more than one single-node system.  Traditionally, this has been for database or environments that exceed ~250 GB on one server.

© Copyright IBM Corporation 2008IBM Remote Data Protection 18 Topic  Introduction  Remote Data Protection  Architecture Overview  *Key Points  Initialization versus Steady State *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 19 Key Points 1.Remote Data Protection Key Terms 2.Standard Service Assumptions 3.Data Types 4.Retention Schedules 5.Backup Windows 6.Remote Data Protection Billing Model 7.Backup Quotas 8.Custom Deals

© Copyright IBM Corporation 2008IBM Remote Data Protection 20 Remote Data Protection Key Terms Restore Time  The amount of time identified by the client for restoration of data from the backup platform to the client’s server Bandwidth  The amount of throughput available for transfer of data from source to destination, either existing or new bandwidth Data Footprint  The amount of data residing on a prospect’s server that is required to be backed up  Data footprint can be the amount of data stored on a filesystem or the amount of data held in a database or other application  Data footprint is NOT the size of the hard drive or available capacity of a storage device (SAN, NAS, and so on)

© Copyright IBM Corporation 2008IBM Remote Data Protection 21 Remote Data Protection Key Terms (continued) Retention Schedule  The amount of time data will be available on disk Backup Window  The window of time during the day a backup can run Initialization  Term used for client activation and its first backup Steady State  When client initialization completes and backups run according to a regular schedule

© Copyright IBM Corporation 2008IBM Remote Data Protection 22 Standard Service Assumptions For sizing and pricing purposes, standard pricing is based on the following: Standard Data Mix: 85% Filesystem/15% Database  This is the baseline assumption of a typical customer’s data mix. If a customer’s total data mix is close to these values, we can quickly determine how well a customer will fit within our standard service and sizing parameters. –Example – Customer’s aggregate footprint = 1 TB: ~ 850 GB filesystem data, ~ 150 GB database data - standard pricing can be used –Example - Customer’s aggregate footprint = 1 TB: ~ 500 GB filesystem data, ~ 500 GB database data - standard pricing may not apply - Contact the Deal Hub. Standard Retention Schedule  There are four standard retention schedules available.

© Copyright IBM Corporation 2008IBM Remote Data Protection 23 Data Types Database Data This term is used to classify data types that produce high rates of change:  Data should be classified as database data whether or not an agent is being used to back up the data. Examples of applications that can produce “database” like data:  Microsoft® Exchange, Oracle, SQL Server®, Sybase, DB2®, Witness (voice recording data), any scientific, medical, or topographical images (x-rays, satellite images, and so on) Filesystem Data This term is used to classify data types that produce relatively low change rates:  Operating system (C: drive), user file shares, static file content, and so on Compressed Data 100% rate of change every time data is created:  This will increase bandwidth requirements, backup windows, and storage needs.

© Copyright IBM Corporation 2008IBM Remote Data Protection 24 Retention Schedules  The last 7 successful backups retained, each for 7 days (Only retention option for PCs)  The last 30 successful backups retained, each for 30 days (mixed retention to cover broad calendar range)  8 daily backups, 5 weekly backups, and 4 monthly backups  Roughly 16 retention points spread across a 120-day period  30 daily backups, 5 weekly backups, and 12 monthly backups

© Copyright IBM Corporation 2008IBM Remote Data Protection 25 Retention Schedules (continued) When designing a solution, it is important to understand that the retention schedule and data mix will impact the solution cost.

© Copyright IBM Corporation 2008IBM Remote Data Protection 26 Backup Windows  Standard service parameters are 20/7 backup window (or availability) and 24/7 restore availability  During the 4-hour period when backups are not available, the platform will perform necessary maintenance activities: –Cleaning up data from expired retention points –Taking a backup of itself –Performing data consistency checks on its backup

© Copyright IBM Corporation 2008IBM Remote Data Protection 27 Remote Data Protection Billing Model Data Protected Model  A customer is billed monthly based on the high-water mark of the data that is protected on a client. If a client’s high- water mark for the month of April is 10GB, that is what the customer will get billed for. Bill = Price * xxGB “protected”

© Copyright IBM Corporation 2008IBM Remote Data Protection 28 Backup Quotas No Hard Backup Quotas  The Remote Data Protection service does not limit customers to any backup quotas.  Backups will never be disabled or prevented from running because of an applied quota.  A customer’s monthly bill will always be based upon the amount of data that is protected within a specific month, which is Usage Based Billing.

© Copyright IBM Corporation 2008IBM Remote Data Protection 29 Custom Deals  Custom deals are needed when a customer’s requirements or qualifications do not fit within the standard service offering. Additional considerations for custom deals are: –Longer cycle to design and provide a solution –More expensive  Try to focus on the standard service offering.

© Copyright IBM Corporation 2008IBM Remote Data Protection 30 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  *Initialization versus Steady State *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 31 Initialization versus Steady State Backups  Initialization versus Steady State Backups

© Copyright IBM Corporation 2008IBM Remote Data Protection 32 Initialization versus Steady State Backups (continued)  This is the term used for client activation and its first backup.  A client’s first backup could take many hours to complete, depending on how much data there is to back up and how much bandwidth is available.  Roughly 40% of the client’s data footprint will need to be sent during initialization. Initialization

© Copyright IBM Corporation 2008IBM Remote Data Protection 33 Initialization versus Steady State Backups (continued) Steady State Backups  Once a client successfully completes its first backup, it will then continue on with steady state backups.  At this point, a client’s backup will run much more efficiently because of Avamar’s “commonality” factoring.  Redundant data is not sent over the WAN to be backed up again.  A client’s backup will now complete in a fraction of the time it took for its initialization.  Roughly 1% of the client’s data footprint needs to be sent for filesystem data during steady state, roughly 5% for database data. Important  For sizing purposes, backup times should be based on steady state backups.  Initialization times should be documented and understood by the customer.  The Quickstart/Quickrestore options can be used to address concerns and requirements regarding initializations or restores.

© Copyright IBM Corporation 2008IBM Remote Data Protection 34 Objectives Review You should have a basic understanding of the technology, features, and functions used for Remote Data Protection. Note: This is part one of a two part presentation