IBM Remote Data Protection PART 2 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  Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  Additional Options  Tools for Designing a Solution  Customer Sizing Scenarios  Competitive Overview

© Copyright IBM Corporation 2008IBM Remote Data Protection 3 Objectives Upon completion of this presentation, you should be able to:  Explain the technology of Remote Data Protection  Articulate the key points of Remote Data Protection  Identify Remote Data Protection’s fundamental features and functions  Articulate the three service options with Remote Data Protection  Gather and analyze customer requirements for Remote Data Protection  Identify critical factors required to ensure a solution will perform to the customer’s requirements  Use the sizing tool to design Remote Data Protection solution  Articulate the key points of IBM’s Managed Service Model 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  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  *Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  Additional Options  Tools for Designing a Solution  Customer Sizing Scenarios  Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 5 Remote Data Protection – Fundamental Features and Functionalities  Remote Data Protection OS Support  Remote Data Protection Database Support  Microsoft Exchange  SQL Server®  Other Databases  VmWare Support  Restores  Remote Data Protection Offsite Replication  Remote Data Protection Security TCP/IP Ports

© Copyright IBM Corporation 2008IBM Remote Data Protection 6 Remote Data Protection OS Support  IBM follows EMC/Avamar’s OS Compatibility Matrix

© Copyright IBM Corporation 2008IBM Remote Data Protection 7 Remote Data Protection Database Support  IBM follows EMC/Avamar’s Database Compatibility Matrix.  In general, agents should be used where supported.  Databases (including Exchange) will always drive a higher rate of change than a file server.  Database sizing is critical when designing a solution.  Database/application environments will most likely drive onsite devices. Database Microsoft Exchange Server 5.5, 2000, and 2003 Information store (database) and mailbox backups Requires: Windows 2003 and Windows 2000 Server (Service Pack2 minimum: Service Pack3 required for Exchange Server 2003) Microsoft SQL Server 2000 Standard or 7.0 Requires: Windows 2000 or 2003 DB2 8.2 Requires: IBM AIX 5.2, 5.1 Windows x64 (non-Itanium)

© Copyright IBM Corporation 2008IBM Remote Data Protection 8 Microsoft Exchange  The Remote Data Protection service has the ability to back up data with two different methods: – Agent-based backups – Export file backups  The Exchange Agent is recommended. Export files should only be used if necessary.  Export files consume large amounts of bandwidth and storage, leading to increased backup windows.  Agent backups can take advantage of commonality, which will significantly reduce the amount of data travelling the network when compared to export file backups.  The Exchange Agent supports two forms of backups: – Infostor – Mailbox (Message) Level  If both options are selected, the customer’s usage is doubled. – If the customer has a server with a 100GB Infostor and selects both options, their daily usage will be 200GB. Note: Mailbox level backups utilize Microsoft MAPI transport protocol, which may cause backup throughput limitations.

© Copyright IBM Corporation 2008IBM Remote Data Protection 9 SQL Server  The Remote Data Protection service has the ability to back up data with two different methods: –Agent-based backups –Export file backups  The SQL Agent is recommended. Export files should only be used if necessary.  Export files will consume large amounts of bandwidth and storage, leading to increased backup windows.  Agent backups can take advantage of commonality, which will significantly reduce the amount of data travelling the network as compared to export file backups.  Currently, the Remote Data Protection service does not support “transaction log” backups. –IBM advises customers to use Enterprise Manager to export and truncate transaction logs to local disk for backup.

© Copyright IBM Corporation 2008IBM Remote Data Protection 10 Other Databases For applications outside of the compatibility list, an export of the application data can be utilized. Most database applications have the ability to export the contents of the database to a file, which can then be backed up with the Remote Data Protection OS agent:  The same methodology can be used for any application with the capability to export database data to a file. It is imperative that the customer understand the effects of using encryption or compression when exporting databases for backups.  Encrypted and compressed data will need a complete backup every time it is backed up.  Data de-duplication is not as efficient with this type of data.

© Copyright IBM Corporation 2008IBM Remote Data Protection 11 VmWare Support In VMWare environments, there are two key terms to understand: VMWare Server and Guest Host.  VMWare Server – The server that is acting as the underlying technology that creates and manages the virtualized operating systems  Guest Host – The hosts that are bringing virtualized and running production applications For protection of guest hosts, RDP natively supports any guest host that falls within the supported platform list. For protection of the VMWare server, RDP does support protection of these, but is a more complicated process. See reference document: EMC/Avamar VCB backups.

© Copyright IBM Corporation 2008IBM Remote Data Protection 12 Restores Filesystem Data Restore  Customers can restore single or multiple files/directories.  Customers have two options for restoring their data: 1.For restores under 1 GB, customers can use the Remote Data Protection Web Restore Portal. 2.For restores over 1 GB, a restore request must be made to. Database Restore  For restores of data protected with the SQL Server or Exchange Agent, a request must be made to the. The option to restore database data (agent-based) is not available through the Remote Data Protection Web Restore Portal. New Server  If a customer’s server is destroyed, the customer must provision a new server and activate it to the Remote Data Protection platform. Once this is done, an alternate client restore is executed from the Global Support Center.

© Copyright IBM Corporation 2008IBM Remote Data Protection 13 Remote Data Protection Offsite Replication Offsite Replication  Replicating data offsite is a requirement for any customer using a Remote Data Protection Onsite Device.  Replicated data will be sent to an IBM vault.  This provides the customer with offsite retention points.  The offsite retention points mirror the onsite retention points.  Customers who are not using an Onsite Device do not have the option of replicating data to another IBM vault.

© Copyright IBM Corporation 2008IBM Remote Data Protection 14 Remote Data Protection Security Encryption  Data is analyzed and shredded prior to being sent across the network. –The result is that data “in flight” is in pieces and encrypted.  All data is encrypted “in flight” between host and backup platform. Data is not encrypted (but is shredded) at rest.  Encryption Standard –AES 128 bit

© Copyright IBM Corporation 2008IBM Remote Data Protection 15 TCP/IP Ports The following chart list the client ports that are associated with the Remote Data Protection Service. PORT PROTOCOL INCOMING/ OUTGOING APPLICATIONDESCRIPTION 443TCPOutgoingBaseline. Client to secure Web server. HTTPS connection to backup server TCPOutgoingBaseline. Client to backup server; proprietary communication TCPOutgoingBaseline. Client to backup server TCPOutgoingBaseline. Client to backup server (SSL). The onsite appliance does not require ports to be open, but if the customer needs a second off-site copy, ports will need to be opened.

© Copyright IBM Corporation 2008IBM Remote Data Protection 16 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  Remote Data Protection – Fundamental Features and Functionalities  *Customer Requirements  Additional Options  Tools for Designing a Solution  Customer Sizing Scenarios  Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 17 Customer Requirements  Customer Requirements

© Copyright IBM Corporation 2008IBM Remote Data Protection 18 Customer Requirements  The gathering of accurate requirements is the key to the successful implementation and steady state support of customer environments.  History has proven that when requirements were not gathered accurately, customer satisfaction has been low.  This section describes the critical information needed from a customer in order to design an appropriate solution.

© Copyright IBM Corporation 2008IBM Remote Data Protection 19 Customer Requirements (continued) Number of sites Location of sites Bandwidth at each location: (What is currently deployed and what is the available room?) Restore Time Backup Window

© Copyright IBM Corporation 2008IBM Remote Data Protection 20 Customer Requirements (continued) Total number of servers a customer wants protected OS type  Supported platforms according to the OS compatibility matrix Data footprint (how much data will be protected)  Both aggregate for the site and per server Types of Data  Calling out the amount of filesystem data  Calling out the amount of database data Types of applications on servers  RDP Database Agents required

© Copyright IBM Corporation 2008IBM Remote Data Protection 21 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  *Additional Options  Tools for Designing a Solution  Customer Sizing Scenarios  Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 22 Additional Options  Remote Data Protection Onsite Device  Remote Data Protection QuickStart  Remote Data Protection QuickRestore

© Copyright IBM Corporation 2008IBM Remote Data Protection 23 Remote Data Protection Onsite Device Onsite Device - A permanent onsite device is placed at the customer’s site while replicating to a Remote Data Protection platform at a BCRS recovery site This option provides the customer with a permanent onsite backup device. The customer will run its regular backups to this device. The backed up data will then be replicated to a Remote Data Protection platform at an IBM data center. This provides the customer with the advantages of local backups and restores at LAN speeds along with offsite retention points.

© Copyright IBM Corporation 2008IBM Remote Data Protection 24 Remote Data Protection QuickStart QuickStart - Provides a temporary onsite appliance at the customer’s site to capture initial data backup (alternative to initial network-based backup) A storage device will be placed at the customer’s site for a period of time. During this time, an initial copy of the customer’s data will be backed up to the device. Once all data is copied over, the device is shipped to a specific IBM site that houses a permanent Remote Data Protection platform. The data from the storage device is then backed up to the permanent platform. Once this completes, the customer can begin regular backups to the Remote Data Protection platform.

© Copyright IBM Corporation 2008IBM Remote Data Protection 25 Remote Data Protection QuickRestore QuickRestore – Provides a temporary onsite appliance at the customer’s site to perform data restores (alternative to network restores) A temporary storage device is placed locally to the Remote Data Protection platform. The customer’s data is then replicated from the Remote Data Protection platform to the temporary device. Once this completes, the temporary device is then shipped to the customer. At this point, they can restore their data locally.

© Copyright IBM Corporation 2008IBM Remote Data Protection 26 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  Additional Options  *Tools for Designing a Solution  Customer Sizing Scenarios  Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 27 Tools for Designing a Solution  Remote Data Protection Sizing Tool

© Copyright IBM Corporation 2008IBM Remote Data Protection 28 Remote Data Protection Sizing Tool Use this tool to size a customer’s environment. Key Entries  Aggregate filesystem data footprint  Aggregate database data footprint  Retention requirements Output  Total customer footprint  Total Remote Data Protection storage requirements The only two entries that need to be entered are:  Total Data Storage  Retention period

© Copyright IBM Corporation 2008IBM Remote Data Protection 29 Remote Data Protection Sizing Tool (continued) Input Output = input fields = output fields

© Copyright IBM Corporation 2008IBM Remote Data Protection 30 Remote Data Protection Sizing Tool (continued) The Sizing Tool determines initialization, steady state backups, and restore times. Key Entries  Bandwidth  Backup Window  Restore Time requirements Output  If customer fits into the Standard Service model  If possible, candidate for a custom solution  Initialization time  Steady state backup time  Full restore time

© Copyright IBM Corporation 2008IBM Remote Data Protection 31 Remote Data Protection Sales Sizing Calculator input output = input fields = output fields

© Copyright IBM Corporation 2008IBM Remote Data Protection 32 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  Additional Options  Tools for Designing a Solution  *Customer Sizing Scenarios  Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 33 Customer Sizing Scenarios Remote Data Protection Sizing Scenarios

© Copyright IBM Corporation 2008IBM Remote Data Protection 34 Remote Data Protection Customer Scenarios Which Solution(s) is the Best Fit for My Prospect? In general, three customer environmental variables determine how RDP’s capabilities are applied to provide a comprehensive solution:  The amount of data to be transmitted  The bandwidth available for transport  The time available to transmit the data Together, these variables define the physical limits of any data protection solution. By speaking with your prospect and determining these variables, we are able to match the service that best fits their needs.

© Copyright IBM Corporation 2008IBM Remote Data Protection 35 Remote Data Protection Sizing Scenario Customer Requirements  50GB server to protect –42GB filesystem –8GB database  Retention =  Backup Window = 8 hours  10Mbps WAN  Moderately aggressive restore time of 12 hours Use values to fill out the RDP Sizing Tool.

© Copyright IBM Corporation 2008IBM Remote Data Protection 36 Remote Data Protection Sizing Scenario (continued) RDP Sizing Tool

© Copyright IBM Corporation 2008IBM Remote Data Protection 37 Remote Data Protection Sizing Scenario (continued) Restore Time  Calculations show a restore time of less than 12 hours  Meets customer’s restore time requirements Solution  Remote Data Protection solution backing up over the WAN

© Copyright IBM Corporation 2008IBM Remote Data Protection 38 Topic  Introduction  Remote Data Protection  Architecture Overview  Key Points  Initialization versus Steady State  Remote Data Protection – Fundamental Features and Functionalities  Customer Requirements  Additional Options  Tools for Designing a Solution  Customer Sizing Scenarios  *Competitive Overview *Indicates current topic.

© Copyright IBM Corporation 2008IBM Remote Data Protection 39 Competitive Overview  Remote Data Protection – DIY versus Managed Services  Remote Data Protection Positioning

© Copyright IBM Corporation 2008IBM Remote Data Protection 40 DIY versus Managed Services  One of Remote Data Protection’s biggest competitors is the DIY (do-it-yourself) customer.  Differentiate between DIY and managed services  Keys to how IBM delivers managed services: –Includes all aspects of data protection strategy, not just a hardware or software purchase –Pay as you go “ Utility Model” –ROI/TCO DIY versus managed service –SLOs (Service Level Objectives) –Capex versus Opex investment –Fully managed service

© Copyright IBM Corporation 2008IBM Remote Data Protection 41 Remote Data Protection Positioning Competitive discussions regarding RDP are typically focused on 2 elements:  Current data protection methodology not working (aged assets, unsuccessful backups, and so on)  The need for remote locations to be protected You can best position the Remote Data Protection service by:  Understanding what current technology the customer is using to perform backups  Understand any current gaps in the customer’s data protection strategy  Understand how the customer’s current data protection strategy has been designed –Dedicated or shared resources for backups –Organizational accountability –Age of backup infrastructure (does equipment need to be upgraded)  What the customer currently uses for reporting/validating success rates and daily status  Regulatory or compliance drivers

© Copyright IBM Corporation 2008IBM Remote Data Protection 42 Summary You should 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 43 Questions and Support If you have questions about Remote Data Protection or need assistance architecting a solution for your customer, contact your local Information Protection Services focal point below. If a contact is not listed for your country, you can the IPS Global Deal Hub ( ) to get a focal point. Global Allen Downs Phone: Allen AG Canada: Andrew Chow Phone: Andrew US Randy Stephens Phone: Randy NE IOT Germany: Thomas Striebel Phone: Thomas UK Michelle Freel Phone: michelle Michelle Freelmichelle SW IOT France: Nicolas Tailhardat Phone: Nicolas Italy Francesco Scribano Phone: Francesco AP Japan: Toyokazu Uchiyama Phone: Toyokazu