Muutke küpsiste eelistusi

Enterprise Systems Backup and Recovery: A Corporate Insurance Policy [Pehme köide]

(Preston de Guise, Sydney Australia)
  • Formaat: Paperback / softback, 326 pages, kõrgus x laius: 254x178 mm, kaal: 566 g, 16 Tables, black and white; 48 Illustrations, black and white
  • Ilmumisaeg: 01-Oct-2008
  • Kirjastus: Auerbach
  • ISBN-10: 1420076396
  • ISBN-13: 9781420076394
Teised raamatud teemal:
  • Formaat: Paperback / softback, 326 pages, kõrgus x laius: 254x178 mm, kaal: 566 g, 16 Tables, black and white; 48 Illustrations, black and white
  • Ilmumisaeg: 01-Oct-2008
  • Kirjastus: Auerbach
  • ISBN-10: 1420076396
  • ISBN-13: 9781420076394
Teised raamatud teemal:
The success of information backup systems does not rest on IT administrators alone. Rather, a well-designed backup system comes about only when several key factors coalescebusiness involvement, IT acceptance, best practice designs, enterprise software, and reliable hardware. Enterprise Systems Backup and Recovery: A Corporate Insurance Policy provides organizations with a comprehensive understanding of the principles and features involved in effective enterprise backups.

Instead of focusing on any individual backup product, this book recommends corporate procedures and policies that need to be established for comprehensive data protection. It provides relevant information to any organization, regardless of which operating systems or applications are deployed, what backup system is in place, or what planning has been done for business continuity. It explains how backup must be included in every phase of system planning, development, operation, and maintenance. It also provides techniques for analyzing and improving current backup system performance.

After reviewing the concepts in this book, organizations will be able to answer these questions with respect to their enterprise:











What features and functionality should be expected in a backup environment?





What terminology and concepts are unique to backup software, and what can be related to other areas?





How can a backup system be monitored successfully?





How can the performance of a backup system be improved?





What features are just "window dressing" and should be ignored, as opposed to those features that are relevant?

Backup and recovery systems touch on just about every system in an organization. Properly implemented, they can provide an enterprise with greater assurance that its information is safe. By utilizing the information in this book, organizations can take a greater step toward improving the security of their data and preventing the devastating loss of data and business revenue that can occur with poorly constructed or inefficient systems.
Preface xvii
Acknowledgments xix
Introduction
1(18)
Who Should Use This Book?
1(2)
Concepts
3(5)
What Is a Backup?
3(4)
Think Insurance
7(1)
Information Lifecycle Protection (ILP)
7(1)
Backups Versus Fault Tolerance
8(2)
Risk Versus Cost
10(4)
Dispelling Myths
14(2)
Myth: Tape Is Going to Die Within a Few Years, and We'll All Be Backing Up to Cheap Disk
14(1)
Myth: Commercial Backup Software Is Not as ''Trustworthy'' as Operating System Invoked Tools
15(1)
Myth: Commercial Backup Software Is Not as Efficient as Customized Backup Scripts Written a Good System Administrator with Local Environment Knowledge
15(1)
Myth: The Use of Commercial Backup Software Would Require Staff Training
15(1)
Myth: Commercial Backup Software Offers No Tangible Improvements over Regular Operating System Backups
15(1)
Myth: Deploying Commercial Backup Software Requires Budgeting for Additional Yearly Maintenance Fees
15(1)
Myth: Backup Is a Waste of Money
16(1)
Myth: It Is Cheaper and More Appropriate to Develop In-House Backup Systems Than to Deploy Commercial Backup Systems
16(1)
Myth: If a Department Can't Fund Backups for Its Systems, They Don't Get Backed Up
16(1)
The Top Ten Rules
16(1)
Online Resources
17(2)
Human and Technical Layers
19(14)
Introduction
19(1)
Human Layers: Roles and Responsibilities
19(9)
Overview
19(1)
Technical Staff
20(1)
Operators
20(1)
Help Desk Staff
20(1)
Backup Administrators
21(1)
System Administrators
22(1)
Application Administrators
22(1)
Management
23(1)
Local Management and Team Leaders
23(2)
Upper Management
25(1)
The Board and the CEO
26(1)
Users
26(1)
Key Users
26(1)
End Users
27(1)
Domain Disputes
27(1)
Technical Layers
28(5)
Introduction
28(1)
Technical Service Layers
28(1)
External and Security
29(1)
Client Systems
29(1)
Processing Systems/Servers
29(1)
Virtualization Systems
30(1)
Storage Systems
30(1)
Backup/Protection Systems
30(1)
Service Component Layers
30(3)
Backup and Recovery Concepts
33(64)
Introduction
33(1)
Host Nomenclature
33(1)
Backup Topology
34(3)
Decentralized Backups
34(1)
Centralized Backups
35(2)
Backup Levels
37(13)
Full Level
37(1)
Incremental Level
38(2)
Differential Level
40(1)
Simple Differential Backups
40(4)
Multi-Layered Differential Levels
44(3)
Consolidated Level
47(1)
Manual Backups
48(1)
Skipping Backups
48(1)
Full Once, Incremental Forever
49(1)
Data Availability
50(5)
Offline
50(1)
Online
51(2)
Snapshot Backups
53(2)
Data Selection Types
55(3)
Inclusive Backups
55(2)
Exclusive Backups
57(1)
Backup Retention Strategies
58(4)
Dependency-Based Retention
58(2)
Simple Model
60(1)
Manual Backups Revisited
61(1)
Recovery Strategies
62(7)
Recovery Types
62(1)
Aggregated Filesystem View
62(1)
Last Filesystem View
63(1)
Point-in-Time Recovery
64(1)
Destructive Recovery
65(1)
Non-Index Recovery
65(1)
Incremental Recovery
66(1)
Recovery Locality
67(1)
Local Recovery
67(1)
Server-Initiated Recovery
68(1)
Directed Recovery
68(1)
Cross-Platform Directed Recovery
68(1)
Client Impact
69(6)
Server-Based Backups
69(1)
Serverless Backups
70(1)
Filesystem/Volume Clones and Snapshots
71(1)
Array Replication
71(1)
Summarizing Serverless Backups
72(1)
Virtual Machine Snapshots
73(2)
Database Backups
75(5)
Cold Backup
75(1)
Hot Backup
76(2)
Export Backup
78(1)
Snapshot Backup
79(1)
Backup Initiation Methods
80(2)
Server Initiated
80(1)
Client Initiated
80(1)
Externally Scheduled
81(1)
Miscellaneous Enterprise Features
82(10)
Pre- and Post-Processing
83(1)
Arbitrary Backup Command Execution
83(1)
Cluster Recognition
84(1)
Client Collections
84(1)
Backup Segregation
85(1)
Granular Backup Control
85(1)
Backup Schedule Overrides
86(1)
Security
87(1)
Duplication and Migration
87(1)
Alerts
88(1)
Command Line Interface
88(1)
Backup Catalogues
89(3)
Media Handling Techniques
92(5)
Spanning
92(1)
Rapid Data Access
93(2)
Multiplexing
95(1)
Media Tracking
95(2)
Backup
97(10)
Introduction
97(1)
What to Back Up
97(10)
Servers
98(1)
Storage Devices
99(1)
SAN
99(1)
NAS
100(3)
Non-Traditional Infrastructure
103(1)
Desktops and Laptops
104(1)
Hand-Held Devices
105(1)
Removable Storage: Devices and Media
105(2)
Documentation and Training
107(18)
Introduction
107(1)
Documentation
107(11)
System Configuration
108(1)
System Map
108(5)
Administrative Operations
113(1)
Media Handling
114(1)
Backup and Recovery Operations
114(1)
Disaster Recovery Operations
115(1)
Troubleshooting
116(1)
Acceptance Test Procedures
116(1)
Test Register
117(1)
Vendor-Supplied Documentation
117(1)
Release Notes
118(1)
Training
118(7)
The Case for Training
118(1)
Backup Administrators
119(1)
System Administrators
119(1)
Application and Database Administrators
120(1)
Operations Staff
121(1)
Help Desk Staff
121(1)
End Users
122(1)
Management
123(2)
Performance Options, Analysis, and Tuning
125(52)
Introduction
125(1)
Performance Techniques
126(22)
Backup Bandwidth
126(1)
Multiplexing
126(11)
NDMP
137(2)
Backup Efficiency
139(1)
Client-Side Compression
139(1)
Bandwidth Limiting
140(1)
File Consolidation
140(3)
Block-Level Backup
143(2)
Data Deduplication
145(3)
Diagnosing Performance Issues
148(12)
Network Performance Analysis
148(1)
Ping Test
149(1)
Speed and Duplexing
149(1)
File Transfer Test
150(1)
Name Resolution Response Times
150(1)
Client Performance Analysis
151(1)
Hardware
151(1)
Filesystem
151(3)
Software
154(1)
Device Performance Analysis
155(3)
Backup Server Performance Analysis
158(2)
Improving Backup Performance
160(17)
Multi-Tiered Backup Environments
160(2)
Incrementals Forever, Revisited
162(1)
Upgrade Hardware
162(1)
Tape Robots
163(2)
Faster Backup Devices
165(1)
Backup to Disk
165(1)
Disk Backup Units
165(1)
Virtual Tape Libraries
166(1)
Dynamic Device Allocation
167(3)
Serverless Backup
170(1)
NDMP
170(1)
Snapshots
170(1)
Multiplex Larger Filesystems
171(1)
Filesystem Change Journals
172(1)
Archive Policies
173(1)
Anti-Virus Software
174(1)
Slower Backup Devices
175(2)
Recovery
177(44)
Introduction
177(1)
Designing Backup for Recovery
178(5)
Recovery Performance
178(2)
Facilitation of Recovery
180(1)
How Frequently Are Recoveries Requested?
180(1)
Backup Recency Versus Recovery Frequency
180(2)
Who May Want to Perform Recoveries?
182(1)
Recovery Procedures and Recommendations
183(16)
Read the Documentation before Starting a Recovery
183(1)
Choosing the Correct Recovery Location
184(2)
Provide an Estimate of How Long the Recovery Will Take
186(1)
Give Updates during Recoveries
186(1)
Write-Protect Offline Media before Using
187(1)
Don't Assume a Recovery Can Be Done if It Hasn't Been Tested
188(1)
Recall All Required Media at the Start of the Recovery
189(1)
Acclimatize Off-Site Recovery Media Whenever Possible
189(1)
Run Recoveries from Sessions That Can Be Disconnected From/Reconnected To
190(1)
Know the Post-Recovery Configuration Changes
190(1)
Check Everything before It Is Done
190(1)
Remember Quantum Physics
191(1)
Be Patient
192(1)
Document the Current Status of the Recovery
193(1)
Note Errors, and What Led to Them
193(1)
Don't Assume the Recovery Is an Exam
194(1)
If Media/Tape Errors Occur, Retry Elsewhere
195(1)
Ensure the Recovery Is Performed by Those Trained to Do It
195(1)
Read and Follow the Instructions if They've Never Been Used Before
196(1)
Write a Post-Recovery Report
196(1)
Update Incorrect Instructions
197(1)
Preserve the Number of Copies of Backups
197(1)
Send Off-Site Media Back Off Site
198(1)
Remind Vendors of SLAs
198(1)
Cars Have Bandwidth, Too
199(1)
Disaster Recovery
199(10)
Maintenance Backups
199(1)
Perform a Backup before Maintenance
199(1)
Perform a Full Backup Following Maintenance
200(1)
If Time Permits, Backup after Recovery
200(1)
Avoid Upgrades
201(1)
Read the Documentation before the Backups Are Performed
201(1)
Disaster Recoveries Must Be Run by Administrators
202(1)
Test and Test and Test Again
202(1)
Use the Same Hardware
203(1)
Know Dependencies (and How to Work around Them)
204(1)
Keep Accurate System Documentation
205(1)
Do You Know Where Your Licenses Are at 1 A.M.?
206(1)
Disaster Recovery Exercises
206(1)
Off-Site Storage
207(1)
Keep the Disaster Recovery Site Current
208(1)
Hot or Cold Disaster Recovery Site?
209(1)
Service Level Agreements
209(8)
Recovery Time Objective SLAs
210(2)
Recovery Point Objective SLAs
212(1)
Planning SLAs
212(1)
Map IT Systems
212(1)
Establish SLAs on a Per-System Basis
213(1)
Confirm SLAs Are Realistic
213(2)
Upgrade IT Environment or Revisit SLAs
215(1)
Failure Costs
215(1)
Formally Agree To, and Publish SLAs
216(1)
Enact Policies to Protect SLAs
216(1)
Verify SLAs
217(1)
Testing
217(4)
Protecting the Backup Environment
221(18)
Introduction
221(1)
Why Protect the Backup Server?
221(2)
Protecting the Backups
223(8)
Via Backup Software
223(1)
Post-Backup Cloning
223(3)
Inline Cloning
226(1)
Storage of Duplicates
226(1)
Hardware-Level Protection
227(1)
Hot-Pluggable Tape Libraries
227(1)
RAIT
228(1)
RAID for Disk Backup
228(1)
Physical Protection
229(1)
Physical Security
230(1)
Protecting the Backup Server
231(8)
Backup Server Components
231(1)
Ensuring Availability
232(2)
Historical Considerations
234(1)
Migration
235(1)
Maintenance
235(2)
Archives
237(2)
Problem Analysis
239(14)
Introduction
239(1)
Network
239(4)
Basic Configuration
240(1)
Switch/NIC Settings
240(1)
Hostname Resolution
240(2)
Basic Connectivity
242(1)
Ping Test
242(1)
Port Test
242(1)
Backup Software Connectivity
242(1)
Hardware Validation
243(3)
Backup Device Validation
243(1)
Physical Inspection
243(1)
Operability Validation
244(1)
Media Validation
245(1)
Firmware Validation
245(1)
System Hardware Validation
246(1)
Server/Storage Node
246(1)
Client
247(1)
Software Validation
247(2)
Log Review
247(1)
Version Compatibility Validation
248(1)
Error Review
249(2)
Tracking Failures
251(2)
Backup Reporting
253(6)
Introduction
253(1)
Reporting Options
254(1)
Automated Reports
254(2)
Automated Report Parsing
255(1)
Zero-Failure Policy
256(3)
Choosing a Backup Product
259(14)
Introduction
259(1)
Coverage
260(10)
Value Products That Value Protection
260(1)
Value Frameworks, Not Monoliths
260(1)
Operating Systems
261(1)
Databases
262(1)
Applications
263(1)
Clustering
264(1)
Hardware
264(1)
Functionality Checklist
265(5)
Administrative Considerations
270(3)
Training
270(1)
Support
271(1)
Maintenance
271(1)
Technical Support
271(2)
Best Practices
273(6)
Introduction
273(1)
Backup to Recover
273(1)
Documentation
273(1)
What to Backup
274(1)
Protect the Backups
274(1)
Results Checking and Reporting
275(1)
Core Design Considerations
275(1)
Track Failures
276(1)
Clearly Delineate Roles and Responsibilities
276(1)
Network, Not Netwon't
277(1)
Ensure the System Is Supported
277(2)
Appendix A Technical Asides
279(10)
Introduction
279(1)
Transactional Logging
279(3)
Snapshots
282(7)
Traditional Snapshots
282(1)
Fast Resynchronization Snapshots
282(2)
Copy-On-Write Snapshots
284(2)
Cache Snapshots
286(1)
Apply-Deferred Snapshots
286(3)
Appendix B Sample Recovery Request Form
289(2)
Appendix C Sample Test Form
291(2)
Appendix D Glossary of Terms
293(4)
Index 297
IDATA Pty Ltd., Sydney, Australia