Download Global Solutions GSR Reporting in 2005

IBM Remote Data Protection
PART 2
IPS – Information Protection Services
October 2008
© Copyright International Business Machines Corporation 2008. 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 www.ibm.com/legal/copytrade.shtml
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.
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
2
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
3
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
4
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
5
Remote Data Protection OS Support
Operating System
 IBM follows
EMC/Avamar’s OS
Compatibility Matrix
Sun® Solaris® 7, 8 ,9 and 10 (SPARC)
With UFS or VXFS file system
Microsoft® Windows® Server 2003, Server 2003 x64 Edition, Server
2000, NT4 (SP6a), 2000 (SP3), XP Pro (SP1)
(with Columbia Data Products® OTM® open file management included for
Windows NT®, 2000, XP and 2003 installs)
Red Hat® Linux 7.3, 8, 9
Red Hat Enterprise Linux AS/ES/WS 3.0(32&64 bit) 4.0(32&64 bit)
SUSE Linux Enterprise Server 8, 9(32&64 bit), 10(32&64)
With ext2, ext3, ReiserFS or JFS file system
Hewlett-Packard® HP-UX® (PA-RISC)
11.0 (patch PHSS_24303 required)
11i v1 (patch PHSS_28871 required)
11i v2
With HFS or VxFS
IBM® AIX® (RISC)
5.1
5.2
5.3
With JFS file system
Apple Mac OS X v10.4 Tiger (PowerPC only)
IBM Remote Data Protection
© Copyright IBM Corporation 2008
6
Remote Data Protection Database Support
Database
 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.
IBM Remote Data Protection
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 2008
7
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
8
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
9
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
10
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
11
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 <Partner or 24x7
Global Support Center>.
Database Restore
 For restores of data protected with the SQL Server or Exchange Agent, a request
must be made to the <Partner or 24x7 Global Support Center>. 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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
12
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
13
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
14
TCP/IP Ports
The following chart list the client ports that are associated with the Remote
Data Protection Service.
PROTOCOL
INCOMING/
OUTGOING
443
TCP
Outgoing
Baseline.
27000
TCP
Outgoing
Baseline.
28001
TCP
Outgoing
Baseline.
29000
TCP
Outgoing
Baseline.
PORT
APPLICATION
DESCRIPTION
Client to secure Web server. HTTPS
connection to backup server.
Client to backup server; proprietary
communication.
Client to backup server.
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
15
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
16
Customer Requirements
 Customer Requirements
IBM Remote Data Protection
© Copyright IBM Corporation 2008
17
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
18
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
19
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
20
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
21
Additional Options
 Remote Data Protection Onsite
Device
 Remote Data Protection
QuickStart
 Remote Data Protection
QuickRestore
IBM Remote Data Protection
© Copyright IBM Corporation 2008
22
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
23
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
24
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
25
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
26
Tools for Designing a Solution
 Remote Data Protection Sizing
Tool
IBM Remote Data Protection
© Copyright IBM Corporation 2008
27
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
28
Remote Data Protection Sizing Tool (continued)
Input
= input fields
Output
= output fields
IBM Remote Data Protection
© Copyright IBM Corporation 2008
29
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
30
Remote Data Protection Sales Sizing Calculator
input
= input fields
= output fields
input
output
output
IBM Remote Data Protection
© Copyright IBM Corporation 2008
31
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
32
Customer Sizing Scenarios
Remote Data Protection Sizing Scenarios
IBM Remote Data Protection
© Copyright IBM Corporation 2008
33
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
34
Remote Data Protection Sizing Scenario
Customer Requirements
 50GB server to protect
– 42GB filesystem
– 8GB database




Retention = 8-5-4
Backup Window = 8 hours
10Mbps WAN
Moderately aggressive restore
time of 12 hours
Use values to fill out the RDP Sizing Tool.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
35
Remote Data Protection Sizing Scenario (continued)
RDP Sizing Tool
IBM Remote Data Protection
© Copyright IBM Corporation 2008
36
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
37
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.
IBM Remote Data Protection
© Copyright IBM Corporation 2008
38
Competitive Overview
 Remote Data Protection – DIY
versus Managed Services
 Remote Data Protection
Positioning
IBM Remote Data Protection
© Copyright IBM Corporation 2008
39
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
40
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
IBM Remote Data Protection
© Copyright IBM Corporation 2008
41
Summary
You should be able to:
 Successfully construct a solution and
articulate the value of Remote Data
Protection for your customers
IBM Remote Data Protection
© Copyright IBM Corporation 2008
42
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 email the IPS Global Deal Hub
([email protected]) to get a focal point.
Global
Allen Downs
Phone: 1-919-466-6700
E-mail: [email protected]
UK
Michelle Freel
Phone: 44-1252-558136
E-mail: michelle [email protected]
AG
Canada:
Andrew Chow
Phone: 1-905-316-1255
E-mail:[email protected]
SW IOT
France:
Nicolas Tailhardat
Phone: 33-1-49-31-40-28
E-mail: [email protected]
US
Randy Stephens
Phone: 1-404-921-5601
E-mail: [email protected]
Italy
Francesco Scribano
Phone: 39-06-5966-2680
E-mail: [email protected]
NE IOT
Germany:
Thomas Striebel
Phone: 49-711-785-7102
E-mail: [email protected]
AP
Japan:
Toyokazu Uchiyama
Phone: 81-3-5649-7713
E-mail: [email protected]
IBM Remote Data Protection
© Copyright IBM Corporation 2008
43