Embed Size (px)
DESCRIPTION
Want to make sure you’re getting the most out of your investment in HP Data Protector? Then attend this session and learn best practices for maintaining the stability, performance, and efficiency of your backup environment. We’ll present tips and tricks for backup architecture sizing, cell manager sizing, media server sizing, and client count per cell. Best practices covered will include IDB maintenance, catalog maintenance and performance tuning. And we’ll cover tools and methodologies for identifying performance bottlenecks and managing issues.
Citation preview
1 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Best Practices for Maintaining your Data Protector Environment
John OliverTechnical Consultant
2
Agenda
– Best practices for maintaining your data protector environment, including:
• Backup Architecture Sizing
• Internal Database Maintenance
• Performance Tuning
• Issue Management
• PSO Service Delivery
– Details on an exciting data health check offer
– Where to go for more information
– Simple ways to get going
3
Backup Architecture Sizing
– Subtitle goes here
4
Backup Architecture Sizing: Best Practices
– Cell Manager and Media Servers
• CPU− 4 processors – minimum− rds CPU bound; backup, copy, restore, IDB maintenance, media
agent
• Memory− 32 GB− rds memory intensive; backup, copy, restore, IDB maintenance,
media agent
– Network
• Dedicated backup network
• Separate application from backup traffic
– Media Agent on Dedicated Server
• Analyze backup demand: prevent bottleneck
• Number of media servers
5
Backup Architecture Sizing: Best Practices
– Client Count
• Rule of thumb: 250 clients per cell manager
• Results vary; example factors include actual volumes backed up, window and SAN vs. network
– SAN clients
• High backup volume; rule of thumb: backup volume over 750 GB
• Do not share media agents placed on SAN clients
– Backup to Disk
• Deduplication and replication
• Longer retention on local storage
• Prevent redundant backup operations
– Backup to Tape
• LTO-5: 3TB capacity at 280 MB/sec native write speed
• Leverage for long term retention
6
Internal Database Maintenance
– Subtitle goes here
7
IDB Maintenance: Best Practices
– Daily Health Check Process
• Ensure daily runs
– Manual Purges
• Monitor IDB size and growth
• Schedule regular IDB purge maintenance
– Periodic IDB Reorganization
• Perform reorganization at least annually to reclaim unused space
• Improved performance and stability
– Periodic IDB Archival
• Combine with IDB Reorganization
• Can be restored to standby cell manager to support restores of sessions already purged from the catalog
• Prevents long media import times for pre 6.11 media
8
Performance Tuning
– Subtitle goes here
9
Keys to Tuning the Backup Environment
1. A Source of Data
2. A Backup ServerSystem
3. A Connection
4. A Connection
5. The Tape Drive
The Point: All are equal possible causes of performance issues!
2
1
3
4
5
10
5 Level SAN Tuning Approach
1. Primary Storage – Although this could reside on a local adapter
within the server, it is usually a large disk subsystem on the SAN
network.
2. The Backup Server – connects via the SWITCH to its Primary
storage and the backup target. It runs the backup application. It
uses an HBA to link to the SAN
3. The Switch – The glue that holds everything together, this box
permits systems and storage to be shared at high speeds.
4. The Interface Controller – This device extracts the SCSI commands
out of the SAN Fibre Channel protocol and permits simple tape and
disk drives to connect to the SAN.
5. The Tape or Disk Backup Target (Secondary Storage) System –SCSI devices that appear as locally connected SCSI to the Server,
via the magic of Fibre Channel!
11
Primary StorageWhat to expect
Average Data Extraction Rates
Data Extraction Rates on slower systems
Data Extraction Rates on high end systems
Windows Servers 15-30 MB/secUnder 10 MB/sec
Over 30 MB/sec
UNIX and SAN systems 40-60 MB/secUnder 30 MB/sec
Over 60 MB/sec
12
Primary Storage
Best Case
– Low File Count
– Large Files
– Simple File System Structure
– Short file names
– Compressible Data (2:1)
Source Data: Best Case vs. Worst Case Data
Worst Case
– High File Count
– Tiny Files (1k byte)
– Complex directory Structure
– Long File Names
– Non-Compressible Data (1:1)
13
Primary Storage– Mange Source to Target Speed for Streaming
– Tape Streaming
• Today’s tape devices faster native speed than source disk
• Drive should never be waiting for data− Prevent repositioning -> prematurely wears out tape drive heads and media
• Requires higher source speed compared to target device speed
• Multiplexing
Multiplexing to feed a single Tape Drive
Tape
14
Backup Server
– Hardware Considerations
• Number of Processors: min 2 processors, at least 1.5 GHz
– BEST PRACTICE: min 4 cores / CPU’s
• Memory: min 1 GB RAM serving each processor
– BEST PRACTICE: 32 GB optimal (4 GB RAM serving each processor)
• Faster C: Drive can help OS and TAPE Software
• SCSI HBA: Dedicated 64-bit or above PCI bus
– BEST PRACTICE: bus not shared with other HBA’s
• # SAN connections
– Software Considerations
• Don’t put the Backup app. database on a slow drive
– Use the largest block sizes for tape drivers
– BEST PRACTICE: 256KB as minimum for today’s tape devices
– NOTE: Windows default blocksize is 64KB; may result in possible overhead on Windows systems
Sizing Considerations
15
SAN SwitchTips and Considerations
– Tuning Considerations• Verify director and switch firmware versions• Verify transfer rate speeds set as intended• The SAN Fabric can consist of many switches that are interconnected
via ISL’s ( Inter Switch Links ).• Backup tuning should always analyse the pathways from the source
to the target (disk to tape) to determine if the paths through the switches are bottlenecked by insufficient ISL’s.
16
SAN Switch
2 x Network Storage Routers
Total Bandwidth unnecessarily constrained
ISL IS TOO SMALL!
What Is WRONG with this Picture?
17
Interface Controller: Performance
Ultra 2 I/F controllers have a total bandwidth of 140MB/sec, 2 SCSI U2 ports
E1200/E2400up to 2 x SDLT220/320 or 2 x Ultrium 230 per SCSI port
E2400-160, N1200-320 & M2402– 1 Ultrium 460 per SCSI port- up to 2 x Ultrium, SDLT, DLT or AIT 230 per SCSI port
Ultra 3 Routers have a total bandwidth of 230MB/sec, 2 SCSI U3 ports
Don’t exceed these values or the router will Become the bottleneck to backup performance.
18
Tape Backup TargetToday’s High Performance Devices
DriveCapacity (native)
GB
Native Write Speed
MB/SecondsInterface(s)
SDLT220 110 57 Ultra 2 SCSISDLT320 160 57 Ultra 2 SCSISTK9940B 200 108 FC -2Gb/sAIT 100 100 43 Ultra 2 SCSIS-AIT1 500 108 Ultra 3 SCSILTO 2 200 40 Ultra 3 SCSILTO 3 400 80 Ultra 3 SCSILTO 4 800 120 Ultra 3 SCSILTO 5 1500 180 Ultra 3 SCSI
– Factors to Consider in Backup Environment Design• More storage on tape media means fewer media required
than in the past• Higher native speeds -> more difficult to stream
– Plan how to stream physical devices properly
19
Tape Backup TargetStreaming vs Repositioning
No data available from host
Reverse
Ramp up speed
Continue writing
– Streaming• Maintains tape operations at highest native speed• Contributes to stability in backup environment
– Repositioning• Frequent repositioning will prematurely wear out tape drive
heads and media• Contributes to instability in backup environment
• e.g. LTO-4 Ultrium 1840 running at 6200mm/sec requires 2.9 seconds to reposition
20
Tape Backup Target
– Device Parallelism or Multiple Device Streams
• Uses the Principle that data from a specific source system can be
routed to a dedicated device in a one-to-one relationship
• Effective for D2D backup, or using older tape technologies
Network Backup with ‘Parallel’ Data Transfers
AGENT
AGENT
BACKUP
ENGINE
Network
SwitchBackup
Server
Data
Source A
Data
Source B
BACKUP OF DATA
SOURCE A
BACKUP OF DATA
SOURCE B
21
Tape Backup Target
– Combines data from multiple Data streams from multiple sources onto a single tape so we can maintain tape streaming
– Increases backup performance but can reduce restore performance
– Most ISVs now support up to 32 data streams onto a single tape
AGENT
AGENT
BACKUP
ENGINE
Network
SwitchBackup
Server
Data
Source A
Data
Source B
SOURCE A
SOURCE B
SOURCE A
SOURCE B
SOURCE A
SOURCE B
Backup Session
using 'Interleaving'
Multiplexing / Interleaving -> Backup with Concurrency
22
Issue Management
– Subtitle goes here
23
Issue Management: Best Practices
– Review and Categorize all Backup Issues
• Determine commonalities among issue categories
• Identify the root cause of groups of issues
• Resolve systemic issues in the backup environment to achieve
stability
– Work with HP Professional Services
• Recommendations to resolve top priority issues
– Work with HP DP Support
• Log DP issues with Support
• Log enhancement requests
24
Professional Services Offering
– Subtitle goes here
25
HP Data Protector Health Check Offering
– 20 hours remote delivery
– One cell manager and up to two installation servers
– Review of up to four tape library configurations
– Review of up to 25 clients
– Review of up to four on-line integrations
– Review state of IDB
– Detailed information gathering and analysis of current backup
environment
– Documentation of the major issues in the backup environment
– Recommendations that leverage standards and best practices
26
Next Steps
Download at
www.hp.com/go/imhub/dataprotector
Under “Getting the best of it” tab
You can contact us at:
27
Learn More…
www.hp.com/go/dataprotector
– Download Trial software
– HP Data Protector Release 6.11 Frequently Asked Questions
www.hp.com/go/imhub/dataprotector
– HP Data Protector Operations Guide (2.2MB, PDF)
– White Paper: HP Data Protector 6.1 software VMware Integration Installation Best Practice (670KB, PDF)
– HP Data Protector Software Cell Manager Planning and Sizing White Paper (473KB, PDF)
www.hp.com/go/techdemos– HP Data Protector: automate high performance backup and
recovery – 1st and 3rd Tuesday of each month
28
Software Universe Data Protector Sessions
Date and Time Room Session Title
5:00, Tuesday National
Harbor 7
What’s new for HP Data Protector software
9:00, Wednesday National
Harbor 6Best practices for maintaining your HP Data
Protector environment
10:30, Wednesday National
Harbor 7
Data protection in Wrigley’s highly available
mission-critical environment
3:30, Wednesday National
Harbor 3
Backup and recovery for virtualized environments
5:00, Wednesday National
Harbor 6
Cloud-based data protection: getting the best
and avoiding risk
10:30, Thursday National
Harbor 7
Protecting Microsoft 2010 applications
29
Q&A
30 ©2010 Hewlett-Packard Development Company, L.P.
To learn more on this topic, and to connect with your peers after
the conference, visit the HP Software Solutions Community:
www.hp.com/go/swcommunity
31
