HP B6960-96035 Concepts Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. B6960-96035
  6. Concepts manual
HP B6960-96035 Concepts Manual

HP B6960-96035 Concepts Manual

Hp projector user manual
Hide thumbs
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
Table of Contents

Advertisement

Quick Links

HP Data Protector A.06.10
Concepts guide
B6960-96035
Part number: B6960-96035
First edition: November 2008

Advertisement

Table of Contents
loading

Related Manuals for HP B6960-96035

Summary of Contents for HP B6960-96035

  • Page 1 HP Data Protector A.06.10 Concepts guide B6960-96035 Part number: B6960-96035 First edition: November 2008...
  • Page 2 Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.

  • Page 3: Table Of Contents

    Integrations ... 29 Document conventions and symbols ... 31 Data Protector graphical user interface ... 32 General information ... 33 HP technical support ... 33 Subscription service ... 34 HP websites ... 34 Documentation feedback ... 34 1 About backup and Data Protector ... 35 In this chapter ...
  • Page 4 Media management ... 48 Backup devices ... 49 User interfaces ... 50 Data Protector GUI ... 50 Data Protector Java GUI ... 52 Overview of tasks to set up Data Protector ... 55 2 Planning your backup strategy ... 57 In this chapter ...
  • Page 5 Data Protector user rights ... 75 Visibility of backed up data ... 76 Data encryption ... 76 How Data Protector AES 256-bit encryption works ... 76 How Data Protector drive-based encryption works ... 77 Restore from encrypted backups ... 78 What is backup ownership? ...
  • Page 6 When to schedule backups ... 107 Staggering full backups ... 107 Optimizing for restore ... 107 Automated or unattended operation ... 110 Considerations for unattended backups ... 110 Duplicating backed up data ... 112 Copying objects ... 113 Why use object copy? ... 116 Object mirroring ...
  • Page 7 Restoring from media in a vault ... 153 Devices ... 153 Device lists and load balancing ... 155 How load balancing works ... 156 Device streaming and concurrency ... 156 Segment size ... 157 Block size ... 158 Number of disk agent buffers ... 159 Device locking and lock names ...
  • Page 8 Data Protector and service management ... 206 Native Data Protector functionality ... 207 Application Response Measurement version 2.0 (ARM 2.0 API) ... 208 Integration with HP Operations Manager software ... 210 SNMP traps ... 210 The monitor ... 210 Reporting and notification ... 211...
  • Page 9 Windows application log ... 213 Java-based online reporting ... 213 Data Protector checking and maintenance mechanism ... 214 Central management, distributed environment ... 214 Using the data provided by Data Protector ... 214 Service management integrations ... 215 Data Protector OM-R integration ... 215 Data Protector OM SIP ...
  • Page 10 Filesystem backup of databases and applications ... 239 Online backup of databases and applications ... 239 9 Direct backup ... 243 In this chapter ... 243 Overview ... 243 Direct backup ... 244 Direct backup benefits ... 245 How direct backup works ... 245 Environment ...
  • Page 11 Local mirror - single host ... 270 Remote mirror ... 270 Local/remote mirror combination ... 272 Other configurations ... 273 13 Snapshot concepts ... 275 In this chapter ... 275 Overview ... 275 Storage virtualization ... 275 Snapshot concepts ... 276 Snapshot backup types ...
  • Page 12 Examples of automated media copying ... 332 Example 1: automated media copying of filesystem backups ... 333 Incr1 backup ... 333 Full backup ... 335 Example 2: automated media copying of Oracle database backups ... 338 Full backup ... 339 Internationalization ...
  • Page 13 Figures Data Protector graphical user interface ... 33 Backup process ... 39 Restore process ... 39 Network backup ... 40 The Data Protector cell (physical view and logical view) ... 41 Backup or restore operation ... 43 Backup session ... 44 Restore session ...
  • Page 14 Leveled incremental backups ... 95 Media needed to restore from simple and leveled incremental backups ... 98 Media needed to restore from leveled incremental backups ... 98 Backup session ... 102 Full backup with daily simple incremental backups ... 108 Full backup with daily level 1 incremental backups ...
  • Page 15 Storage Area Network ... 172 Loop initialization protocol ... 174 Example multipath configuration ... 176 Indirect Library Access ... 179 Direct Library Access ... 180 IDB parts ... 190 The influence of logging level and catalog protection on IDB growth ... 199 Service management information flow ...
  • Page 16 Multiple disk arrays - dual host ... 282 Multiple application hosts - single backup host ... 283 Disk array(s) - single host ... 284 LVM mirroring - HP StorageWorks Virtual Array only ... 285 Campus Cluster with LVM Mirroring - HP StorageWorks Virtual Array only ... 286 Actors of the traditional backup model ...
  • Page 17 Overview of backup and automated media copy sessions ... 340 Concepts guide...
  • Page 18 Hardware and software environment of XYZ ... 299 Proposed environment ... 303 The staggering approach ... 308 Remote full backups to the HP DLT 41 15 library ... 309 Size of backup environment ... 313 Maximum acceptable downtime for recovery ... 315 How long data should be kept ...
  • Page 19 The Staggering Approach for ABC Cape Town ... 326 ABC’s backup specification configuration ... 327 Concepts guide...

  • Page 21: Publication History

    Guide updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition history...
  • Page 22 Publication history...

  • Page 23: About This Guide

    Documentation & Help component on Windows or the OB2-DOCS component on UNIX. Once installed, the guides reside in the Data_Protector_home\docs directory on Windows and in the /opt/omni/doc/C directory on UNIX. You can find these documents from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select your product.
  • Page 24 This guide describes the integrations of Data Protector with Oracle, SAP R3, and SAP DB/MaxDB. • HP Data Protector integration guide for IBM applications: Informix, DB2, and Lotus Notes/Domino This guide describes the integrations of Data Protector with the following IBM applications: Informix Server, IBM DB2, and Lotus Notes/Domino Server.
  • Page 25 This manual describes how to install, configure, and use the integration of Data Protector with HP Reporter. It is intended for backup administrators. It discusses how to use the application for Data Protector service management. • HP Data Protector integration guide for HP Operations Manager for UNIX...

  • Page 26: Online Help

    • HP Data Protector product announcements, software notes, and references This guide gives a description of new features of HP Data Protector A.06.10. It also provides information on supported configurations (devices, platforms and online database integrations, SAN, and ZDB), required patches, and limitations, as well as known problems and workarounds.

  • Page 27: Documentation Map

    Documentation map Abbreviations Abbreviations in the documentation map that follows are explained below. The guide titles are all preceded by the words “HP Data Protector”. Abbreviation Concepts Help IG-IBM IG-MS IG-O/S IG-OMU IG-OMW IG-PM/PA IG-Report IG-SIP IG-Var Guide Command line interface reference...

  • Page 28: Map

    Abbreviation Install MO GS MO RN MO UG MPE/iX Trouble ZDB Admin ZDB Concept ZDB IG The following table shows where to find information of different kinds. Shaded squares are a good place to look first. About this guide Guide Installation and licensing guide Media Operations getting started guide Media Operations product announcements, software notes, and...

  • Page 29: Integrations

    Integrations Look in these guides for details of the following integrations: Integration HP Operations Manager for UNIX/for Windows HP Performance Manager HP Performance Agent Guide IG-OMU, IG-OMW IG-PM/PA IG-PM/PA Concepts guide...
  • Page 30 Integration HP Reporter HP Service Information Portal HP StorageWorks Disk Array XP HP StorageWorks Enterprise Virtual Array (EVA) HP StorageWorks Virtual Array (VA) IBM DB2 UDB Informix Lotus Notes/Domino Media Operations MPE/iX system Microsoft Exchange Server Microsoft Exchange Single Mailbox...

  • Page 31: Document Conventions And Symbols

    CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. Element Cross-reference links and e-mail addresses http://www.hp.com website addresses Text emphasis • File and directory names • System output •...

  • Page 32: Data Protector Graphical User Interface

    NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Data Protector graphical user interface Data Protector provides a cross-platform (Windows and UNIX) graphical user interface. You can use the original Data Protector GUI (Windows only) or the Data Protector Java GUI. For information about the Data Protector graphical user interface, see the online Help.

  • Page 33: General Information

    Figure 1 Data Protector graphical user interface General information General information about Data Protector can be found at dataprotector. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers •...

  • Page 34: Subscription Service

    Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: •...

  • Page 35: About Backup And Data Protector

    “Overview of tasks to set up Data About Data Protector HP Data Protector is a backup solution that provides reliable data protection and high accessibility for your fast growing business data. Data Protector offers comprehensive backup and restore functionality specifically tailored for enterprise-wide and distributed environments.
  • Page 36 Windows clients, you need an Installation Server for Windows. The remote installation can be performed from any client with an installed Data Protector GUI. For supported platforms for the Installation Server, see the HP Data Protector product announcements, software notes, and references.
  • Page 37 Data Protector enables you to meet high availability needs • Integrating with clusters to ensure fail-safe operation with the ability to back up virtual nodes. For a list of supported clusters, see the HP Data Protector product announcements, software notes, and references.

  • Page 38: Introducing Backups And Restores

    SQL Server, Oracle, Informix Server, SAP R/3, Lotus Notes/Domino Server, IBM DB2 UDB, Sybase database objects, and VMware Virtual Infrastructure objects. For a list of supported versions for a particular operating system, see the HP Data Protector product announcements, software notes, and references.

  • Page 39: What Is A Restore

    Figure 2 Backup process In most cases, the source is data on a disk, such as files, directories, databases, and applications. If the backup is expected to be used for disaster recovery, it needs to be consistent. Software that actually copies data to the destination is a backup application. The destination is a backup device, such as a tape drive, with media to which a copy of the data is written.

  • Page 40: Direct Backup

    Figure 4 Network backup To accomplish backup of a network environment you need an application that allows you to: • Attach backup devices to any system in the network This enables local backups of systems with large volumes of data and network backups in order to reduce backup device costs.

  • Page 41: The Data Protector Cell (Physical View And Logical View)

    The GUI and the Cell Manager systems can run on UNIX and Windows operating systems; they do not have to run the same operating system. For a list of supported operating systems for a particular Data Protector component, see the HP Data Protector product announcements, software notes, and references .

  • Page 42: Operations In The Cell

    Systems to be backed up Client systems you want to back up must have the Data Protector Disk Agent (DA), also called Backup Agent, installed. To back up online database integrations, install the Application Agent. In the rest of the manual, the term Disk Agent will be used for both agents.

  • Page 43: Backup Sessions

    Figure 6 Backup or restore operation Backup sessions What is a backup session? A backup session, shown in of data on storage media. It is started either interactively by an operator using the Data Protector user interface, or unattended using the Data Protector Scheduler. How does it work? The Backup Session Manager process starts Media Agent(s) and Disk Agent(s), controls the session, and stores generated messages to the IDB.

  • Page 44: Restore Sessions

    Figure 7 Backup session A typical backup session is more complex than the one shown in A number of Disk Agents read data from multiple disks in parallel and send data to one or more Media Agents. For more information on complex backup sessions, see Chapter 7 on page 219.

  • Page 45: Enterprise Environments

    Enterprise environments What is an enterprise environment? A typical enterprise network environment, shown in of a number of systems from different vendors with different operating systems. The systems may be located in different geographical areas and time zones. All the systems are connected with LAN or WAN networks operating at various communication speeds.

  • Page 46: Single-Point Management Of Multiple Cells

    Why split large environments into multiple cells? • Geographical grouping of systems. • Logical grouping of systems, for example, departments. • Slow network connection between some systems. • Performance considerations. • Separate administrative control. For a list of considerations in planning your environment, see Data Protector allows you to manage multiple cells from a single point.

  • Page 47: Manager-Of-Managers Environment

    Figure 1 1 Manager-of-Managers environment Manager-of-Managers provides the following features: • Centralized licensing repository This enables simplified license management. This is optional but useful for very large environments. • Centralized Media Management Database (CMMDB) The CMMDB allows you to share devices and media across several cells in a MoM environment.

  • Page 48: Media Management

    Media management Data Protector provides you with powerful media management, which lets you easily and efficiently manage large numbers of media in your environment in the following ways: Media management functionality • Grouping media into logical groups, called media pools, which allows you to think about large sets of media without having to worry about each medium individually.

  • Page 49: Backup Devices

    Each device is linked to a media pool; this media pool can be changed in the backup specification. For example, backup specification 2 references the pool Dept_X instead of the default pool. Data Protector supports various devices. For more information, see the HP Data Protector product announcements, software notes, and references. Concepts guide...

  • Page 50: User Interfaces

    User interfaces Data Protector provides easy access to all configuration and administration tasks using the Data Protector GUI on Windows and UNIX platforms. You can use the original Data Protector GUI (on Windows) or the Data Protector Java GUI (on Windows and UNIX).
  • Page 51 • Easy configuration and management of the backup of online database applications that run in Windows environments, such as Microsoft SQL Server, Microsoft Exchange Server, SAP R/3, and Oracle or those that run in the UNIX environments, such as SAP R/3, Oracle, and Informix Server. •...

  • Page 52: Data Protector Java Gui

    Figure 14 Original Data Protector GUI Figure 15 Data Protector Java GUI Data Protector Java GUI The Data Protector Java GUI is a Java-based graphical user interface with a About backup and Data Protector...

  • Page 53: Data Protector Java Gui Architecture

    client-server architecture. It enables backup management with the same look and feel as the original Data Protector GUI. The Java GUI consists of two components: Java GUI Server and Java GUI Client. Figure 16 on page 53 shows the relationship between these components. Figure 16 Data Protector Java GUI architecture The Java GUI Server is installed on the Data Protector Cell Manager system.
  • Page 54 The communication between the Java GUI Client and the Java GUI Server is done through HTTP, which is also firewall friendlier. For details, see the Data Protector support matrices under specifications at /www.hp.com/support/manuals. • Improved localization and internationalization Only one installation package is needed for all locales.

  • Page 55: Overview Of Tasks To Set Up Data Protector

    However, this is valid only for 60 days from the date of installation. For details, see the HP Data Protector installation and licensing guide. Consider security aspects: • Analyze security considerations. See the HP Data Protector installation and licensing guide. • Consider which user groups you need to configure.
  • Page 56 Install and configure your Data Protector environment. • Install the Data Protector Cell Manager system and use the Data Protector user interface to distribute Data Protector components to other systems. • Connect devices (tape drives) to the systems that will control them. •...

  • Page 57: Planning Your Backup Strategy

    2 Planning your backup strategy In this chapter This chapter describes backup strategy planning. It focuses on planning Data Protector cells, performance, and security, as well as backing up and restoring data. The chapter also discusses basic backup types, automated backup operation, clustering, and disaster recovery.

  • Page 58: Backup Strategy Planning

    Backup strategy planning Data Protector is simple to configure and administer. However, if you work in a large environment with diverse client systems and huge amounts of data to back up, plan in advance. Planning simplifies subsequent configuration steps. What is backup strategy planning? Backup strategy planning is a process that includes the following steps: Defining the requirements and constraints for backups, for example, how often your data needs to be backed up or whether you need additional copies of the...
  • Page 59 infrastructure and equipment needed for backups. For each type of data, list the maximum acceptable downtime for recovery, that is, how long specific data can be unavailable before recovered from a backup. For example, user files may be restored in two days, while some business data in a large database would need to be recovered in two hours.

  • Page 60: Factors Influencing Your Backup Strategy

    For more information, see Protector also backs up some popular online database applications. For more information, see the HP Data Protector integration guide. If you back up to disk, you can take advantage of synthetic backup and disk staging. These advanced backup strategies significantly reduce the time needed for backup.
  • Page 61 This also includes safeguarding all relevant data against unauthorized access, using physical access prevention and electronic password protection. • Types of data that need to be backed up List the company’s types of data and how you want to combine them in backup specifications, including the time frames available for backups.

  • Page 62: Planning Cells

    • Consider backing up to a disk-based device. Besides other benefits, backup to disk reduces the time needed for backup and enables the use of advanced backup strategies such as synthetic backup and disk staging. • Consider configuring your system for direct backup by attaching a library device to the SAN through a fibre channel bridge.
  • Page 63 administrator for each cell. • Size of each cell The size of a Data Protector cell affects backup performance and the ability to manage the cell. The recommended maximum size for a Data Protector cell is 100 client systems. Cells with more than 200 client systems are less manageable. •...

  • Page 64: Installing And Maintaining Client Systems

    Installation Servers and Cell Managers before you start installing the software. A dedicated port, generally port 5555, needs to be available throughout the cell. For details, see the HP Data Protector installation and licensing guide. The Cell Manager and Installation Servers are installed directly from the CD. After you have installed the Cell Manager and Installation Servers you can then install the components on various client systems using the Data Protector Installation GUI.

  • Page 65: Creating Cells In The Windows Environment

    fully qualified node name. Creating cells in the Windows environment Due to the different possible configurations (domain versus workgroup), the various levels of support for Windows Administrators may have some impact on the setup of Data Protector during installation. An important prerequisite is to have a clean node name resolving setup, so that each client system is accessible from every other client system using the same fully qualified node name.

  • Page 66: Windows Workgroups

    Windows workgroups Some of the configuration tasks require more steps in some cases, because there are no global users as in a domain. Software distribution requires a unique logon for every client system that you install the software on. This means that to install 100 client systems in a workgroup environment, you are required to enter 100 logons.

  • Page 67: Understanding And Planning Performance

    you need to ensure that data transfer from each client system to the corresponding device is not done over a WAN. Because a WAN network is not a stable connection, it is possible that connections are lost. MoM environment A MoM environment does not require a reliable network connection from cells to the central MoM cell, because only controls are sent over the long distance connections, and backups are performed locally within each Data Protector cell.

  • Page 68: Network Or Server Versus Direct Backups

    To maximize performance, use local backup configurations for high volume datastreams. Network or server versus direct backups Sending data over a network and through a server introduces additional overhead, as the network and the server become performance considerations. Data Protector handles the datastream differently for the following cases: •...

  • Page 69: High Performance Hardware Other Than Devices

    For more information on Zero Downtime Backup, see the HP Data Protector zero downtime backup concepts guide. Using hardware in parallel Using several datapaths in parallel is a fundamental and efficient method to improve performance.

  • Page 70: Configuring Backups And Restores

    By default, hardware compression is enabled. On HP-UX systems, enable hardware compression by selecting a hardware compression device file. On Windows systems, enable hardware compression during device configuration.

  • Page 71: Full And Incremental Backups

    Full and incremental backups A basic approach to improve performance is to reduce the amount of data to back up. Carefully plan your full and incremental backups. Note that you may not need to perform all the full backups of all the client systems at the same time. If you back up to disk, you can use advanced backup strategies such as synthetic backup and disk staging.

  • Page 72: Disk Performance

    Disk performance All data that Data Protector backs up resides on disks in your systems. Therefore, the performance of disks directly influences backup performance. A disk is essentially a sequential device, that is, you can read or write to it, but not both at the same time. Also, you can read or write one stream of data at a time.

  • Page 73: San Performance

    For more information on how Data Protector integrates with various applications and for tips on how to improve backup performance, see the HP Data Protector integration guide. Also see the documentation that comes with your online database application for more information on how to improve backup performance.

  • Page 74: Cells

    Data Protector security features The following features allow and restrict access to Data Protector and the backed up data. The items in this list are described in detail in the following sections. • Cells • Data Protector user accounts • Data Protector user groups •...

  • Page 75: Data Protector User Groups

    When a user starts the Data Protector user interface, Data Protector checks user rights. User rights are also checked when specific tasks are performed by a user. For more information, see Data Protector user groups What are user groups? When a new user account is created, the user becomes a member of the specified user group.

  • Page 76: Visibility Of Backed Up Data

    Visibility of backed up data Backing up data means creating a new copy. Therefore, when you deal with confidential information, it is important to restrict access to both the original data and to the backup copy itself. Hiding data from other users When configuring a backup, you can decide whether during a restore the data is visible to everyone (public) or only to the owner of the backup (private).

  • Page 77: How Data Protector Drive-Based Encryption Works

    encrypts the data. Thus the backed up data is encrypted before it is transferred over the network and written to media. Figure 17 on page 77 shows a basic interaction during an encrypted backup session with the AES 256-bit encryption option selected. Figure 17 Backup session with AES 256-bit encryption How Data Protector drive-based encryption works The BSM reads the backup specification in which the Drive-based encryption option...

  • Page 78: Restore From Encrypted Backups

    If a source medium involved in an automatic media copy session stores encrypted as well as non-encrypted data, all data written to the corresponding target medium will be either encrypted or non-encrypted, depending on current settings for drive-based encryption. Figure 18 on page 78 shows a basic interaction during an encrypted backup session with the Drive-based encryption option selected.

  • Page 79: Clustering

    Support either the addition or subtraction of components For clustering purposes, Data Protector integrates with Microsoft Cluster Server for Windows Server, with MC/Service Guard for HP-UX, with Veritas Cluster for Solaris and with Novell NetWare Cluster Services. For a list of supported clusters, see the HP Data Protector product announcements, software notes, and references.

  • Page 80: Typical Cluster

    Figure 19 Typical cluster Components: • Cluster nodes (two or more) • Local disks • Shared disks (shared between nodes) Cluster nodes Cluster nodes are computers that compose a cluster. They are physically connected to one or more shared disks. Shared disks The shared disks volumes (MSCS, Novell NetWare Cluster Services) or shared volume groups (MC/SG, Veritas Cluster) contain mission-critical application data as well as...
  • Page 81 (MC/SG, Veritas Cluster) or group (MSCS). What is a package or group? A package (MC/SG, Veritas Cluster) or a group (MSCS) is a collection of resources that are needed to run a specific cluster-aware application. Each cluster-aware application declares its own critical resources. The following resources must be defined in each group or package: •...

  • Page 82: Cluster Support

    A cluster-aware Data Protector Cell Manager that is responsible for running the IDB and managing backup and restore operations has many major benefits over non-cluster versions: High availability of the Data Protector Cell Manager All Cell Manager operations are always available since Data Protector services are defined as cluster resources within the cluster and are automatically restarted when a failover occurs.

  • Page 83: Example Cluster Environments

    in the cluster) in such a case is not fault tolerant; the operations in the cell must be restarted manually. The behavior of the Cell Manager after the failover is configurable as far as the backup session (failed due to the failover) is concerned - the failed session can be: •...

  • Page 84: Cell Manager Installed Outside A Cluster

    Figure 20 Cell Manager installed outside a cluster When creating a backup specification, you can see three or more systems that can be backed up in the cluster. • Physical Node A • Physical Node B • Virtual Server Virtual server backup If you select the virtual server in the backup specification, then the backup session will back up the selected active virtual host/server regardless of the physical node the package or group is currently running on.

  • Page 85: Cell Manager Installed Outside A Cluster, Devices Connected To The Cluster Nodes

    Table 3 Backup behavior Condition Failover of the node before a backup starts Failover of the node during backup activity Cell Manager installed outside a cluster, devices connected to the cluster nodes In the environment depicted below: • The Cell Manager installed outside a cluster •...

  • Page 86: Cell Manager Installed Outside A Cluster, Devices Connected To The Cluster

    Figure 21 Cell Manager installed outside a cluster, devices connected to the cluster nodes When creating a backup specification, you can see three or more systems that can be backed up in the cluster. • Physical Node A • Physical Node B •...

  • Page 87: Cell Manager Installed In A Cluster, Devices Connected To The Cluster Nodes

    NOTE: The difference with the previous example is that each of the cluster nodes has a Data Protector Media Agent installed. Additionally, you need to use the Data Protector load balancing functionality. Include both devices in the backup specification. With load balancing set to min=1 and max=1, Data Protector will only use the first available device.
  • Page 88 (MC/ServiceGuard) or group (Microsoft Cluster Server) as the application cluster critical resources. IMPORTANT: Only in such a configuration, it is possible to define the automated action concerning the Data Protector sessions aborted during the failover. • The Data Protector Cell Manager is configured to run (both during the normal operation and during the failover) on nodes other than the application node - the Data Protector cluster critical resources are defined in some other package (MC/ServiceGuard) or group (Microsoft Cluster Server) as the application...

  • Page 89: Cell Manager Installed In The Cluster, Devices Connected To Cluster

    Figure 22 Cell Manager installed in the cluster, devices connected to cluster nodes When creating a backup specification, you can see three or more systems that can be backed up in the cluster. • Physical Node A • Physical Node B •...

  • Page 90: Backup Behavior

    NOTE: Clusters do not support a SCSI bus with shared tapes. To bring high availability also to Media Agents, the Fibre Channel technology can be used as an interface to the device. The device itself is not highly-available in this configuration. This configuration allows the following features: •...

  • Page 91: Full And Incremental Backups

    This results in the corruption of the medium. Additionally, the Data Protector cluster Cell Manager/client can be integrated with the EMC Symmetrix or HP StorageWorks Disk Array XP environment, producing a very highly-available backup environment. For more information, see the HP Data Protector zero downtime backup administrator's guide.

  • Page 92: Full Backups

    A number of additional backup types (such as direct backup, split mirror backup, snapshot backup, and data mover backup) are available with Data Protector application integrations. For more information, see the respective HP Data Protector integration guides for more information.

  • Page 93: Conventional Incremental Backup

    backup and there is no protected full backup, a full backup is performed instead. Conventional incremental backup Before running an incremental backup of a specific backup object, Data Protector compares the trees in the backup object with the trees in the valid restore chain of this object.
  • Page 94 Incr A simple incremental backup, shown in Figure on page 95, is based on the last backup that is still protected, which can be a full backup or an incremental backup. Incr1-9 A leveled incremental backup, shown in Figure on page 95, depends on the last backup of the next lower level that is still protected.

  • Page 95: Incremental Backups

    Figure 23 Incremental backups Figure 24 Leveled incremental backups Table 7 on page 95 shows the relative referencing of backup runs with various backup types. See the text following the table for a full explanation. Table 7 Relative referencing of backup runs Full <---- Full...

  • Page 96: Considering Restore

    Full Full Full Full How to read Table 7 on page 95 • The rows in Table 7 situations. • The age of the backups increases from right to left, so that the far left is the oldest and the far right is the most recent backup. •...
  • Page 97 TIP: Use the Data Protector Appendable on Incrementals Only option to keep data from full and incremental backups (of the same backup specification) on the same media set. Another common use of the incremental backup concept is indicated in Figure on page 98.

  • Page 98: Media Needed To Restore From Simple And Leveled Incremental

    Figure 25 Media needed to restore from simple and leveled incremental backups Figure 26 Media needed to restore from leveled incremental backups Note that you must set the appropriate data protection in order to get all needed full and incremental backups for restore. If the data protection is not properly set, you can get a broken restore chain.

  • Page 99: Keeping Backed Up Data And Information About The Data

    Keeping backed up data and information about the data Data Protector lets you specify how long to keep your backed up data on the media itself (data protection), how long to keep information about the backed up data in the IDB (catalog protection), and what level of information to keep in the IDB (logging level).

  • Page 100: Catalog Protection

    Catalog protection What is catalog protection? Data Protector saves information about backed up data in the IDB. Since the information about the backed up data is written to the IDB each time a backup is done, the IDB grows with the number and the size of backups. Catalog protection tells Data Protector how long the information about backed up data is available to users browsing data during restore.

  • Page 101: Enabling The Browsing Of Files And Quick Restore

    for example, the exact file name. The IDB also keeps information on how long the actual data on the media will not be overwritten. Data protection, catalog protection and logging level policies influence the availability of data and access time to data during restore. Enabling the browsing of files and quick restore To restore files quickly, both information about backed up data in the catalog and protected data on the media, must exist.

  • Page 102: Exporting Media From A Cell

    Exporting media from a cell Exporting media from a Data Protector cell removes all the information about backed up data on the media and the media themselves from the IDB. You cannot browse, select or restore files from exported media using the Data Protector user interface. You need to re-read (or add) the media back into the Data Protector cell.

  • Page 103: Creating A Backup Specification

    devices. During the backup session, Data Protector reads the objects, transfers data through the network, and writes it to the media residing in the devices. The backup specification names the devices to use. It also can specify a media pool. If no media pool is specified, the default media pool is used.
  • Page 104 • Description: uniquely defines the backup objects with identical client name and mount point. • Type: backup object type, for example filesystem or Oracle. The way in which a backup object is defined is important to understand how incremental backups are done. For example, if the description of a backup object changes, it is considered as a new backup object, therefore a full backup will be automatically performed instead of incremental.

  • Page 105: Backup Sessions

    Backup sessions What is a backup session? A backup session is a process that backs up data from a client system to media. A backup session always runs on the Cell Manager system. A backup session is based on a backup specification and is started when a backup is run. During a backup session, Data Protector backs up data using default or customized behavior.

  • Page 106: Scheduling, Backup Configurations, And Sessions

    You can combine full and incremental backups when you configure scheduled backups. For example, you may run a full backup on Sundays and incremental backups every working day. To back up a large amount of data and avoid the high volume peak for the full backups, use the staggered approach.

  • Page 107: When To Schedule Backups

    and some tips for efficient scheduling. When to schedule backups Typically, you schedule backups to run during lowest user activity, usually at night. Full backups take the most time, so schedule them at weekends. Consider scheduling full backups for different clients (backup specifications) on different days, as shown in NOTE: Data Protector offers reports that show available time slots from a device-usage point of...

  • Page 108: Full Backup With Daily Simple Incremental Backups

    incremental backup. For more information on how Data Protector selects media for backups, see Selecting media for backups Example 1 Figure 28 on page 108 depicts a scheduling policy based on a full backup plus simple incremental backups. Figure 28 Full backup with daily simple incremental backups This policy reduces the media space and time needed for backing up, because you only back up changes from the previous day.

  • Page 109: Full Backup With Daily Level 1 Incremental Backups

    Figure 29 Full backup with daily level 1 incremental backups This policy requires slightly more time for backups and also requires a little more media since you back up all the changes from the last full backup every day. To restore files from Thursday’s backup, you need to provide media for the full and for Thursday’s incremental backup, that is, two media sets only.

  • Page 110: Automated Or Unattended Operation

    Figure 30 Full backup with mixed incremental backups This policy takes into account the fact that there are not many changes during weekends. Data is backed up using a combination of simple incremental backups and Incr1 (differential) backups to optimize backup performance. To restore files from Thursday’s backup, you need to provide media from the full backup and the second Incr1 backup, that is, two media sets.
  • Page 111 Typically, this is at night and most backups are scheduled to run during the night. Data Protector can generate reports about devices used for backup. • What kind of data do you have and how often do you want to schedule backups of this data? Data that changes often and is important to the company, such as user files, transactions, and databases must be backed up regularly.

  • Page 112: Duplicating Backed Up Data

    If you need to back up large amounts of data and the backup window presents a problem, consider backing up to disk-based devices and using advanced backup strategies such as synthetic backup and disk staging. • How can I prepare running applications for backups? Many applications keep files open, so running a backup would produce an inconsistent backup.

  • Page 113: Copying Objects

    Object copy Appendability of target media Result of the Media operation containing the selected object versions Source media are located on virtual tapes stored on disk arrays and target media are located on a physical tape library attached to the VLS. You can use only unformatted media, empty media, or media with expired protection as target media.

  • Page 114: Object Copy Concept

    Figure 31 Object copy concept In the figure, there is an object version resulting from a backup of object A, version 1, and two additional copies of the same object version. Version 1- 1 has been obtained by copying the object version resulting from the backup, and version 1- 1 - 1 by copying a copy of the object version.
  • Page 115 You need separate devices to be used with the source media and the target media. The destination devices can have a larger block size than the source devices. However, to avoid impact on performance, it is recommended that the devices have the same block size and are connected to the same system or to a SAN environment.

  • Page 116: Why Use Object Copy

    Why use object copy? Additional copies of backed up data are created for multiple purposes: • Vaulting You can make copies of backed up objects and keep them in several locations. • Freeing media To keep only protected object versions on media, you can copy such object versions, and then leave the medium for overwriting.

  • Page 117: Freeing Media

    Figure 32 Freeing media Demultiplexing of media Multiplexed media contain interleaved data of multiple objects. Such media may arise from backup sessions with the device concurrency more than 1. Multiplexed media may compromise the privacy of backups and require more time for restore. Data Protector offers a possibility of demultiplexing of media.

  • Page 118: Demultiplexing A Medium

    Figure 33 Demultiplexing a medium Consolidating a restore chain You can copy a restore chain (all backups that are necessary for a restore) of an object version to a new media set. A restore from such a media set is faster and more convenient, as there is no need to load several media and seek for the needed object versions.

  • Page 119: Object Mirroring

    Figure 34 Disk staging concept Disk staging also eliminates the need for frequent backups of numerous small objects to tape. Such backups are inconvenient due to frequent loading and unloading of media. The use of disk staging reduces backup time and prevents media deterioration. Object mirroring What is object mirroring? The Data Protector object mirror functionality enables writing the same data to several...
  • Page 120 The result of a successful backup session with object mirroring is one media set containing the backed up objects and additional media sets containing the mirrored objects. The mirrored objects on these media sets are treated as object copies. Benefits of object mirroring The use of the object mirror functionality serves the following purposes: •...

  • Page 121: Object Mirroring

    Figure 35 Object mirroring Selection of devices Object mirroring is load balanced by default. Data Protector makes optimum use of the available devices by utilizing as many devices as possible. Devices are selected according to the following criteria in the order of priority: •...

  • Page 122: Copying Media

    Backup performance also depends on factors such as device block sizes and the connection of devices. If the devices used for backup and object mirroring have different block sizes, the mirrored data will be repackaged during the session, which takes additional time and resources. If the data is transferred over the network, there will be additional network load and time consumption.
  • Page 123 Automated media copying What is automated media copying? Automated media copying is an automated process that creates copies of the media containing backups. This functionality is available with library devices. Data Protector offers two types of automated media copying: post-backup media copying and scheduled media copying.

  • Page 124: Automated Media Copying

    Smart media copying using VLS What is smart media copying? In smart media copying, the data is first backed up to a virtual tape library (VTL) configured on the Virtual Library System (VLS). Then, a copy of a virtual tape containing a backup is made to the physical library attached to the VLS in a process called automigration.

  • Page 125: Restoring Data

    67. • The application you are recovering, for example, Oracle database files. For more information, see the appropriate HP Data Protector integration guide. • The use of parallel restore. Several objects can be restored with a single read operation, depending on how the data was backed up.

  • Page 126: Selection Of The Media Set

    Selection of the media set If an object version that you want to restore exists on more than one media set, which has been created using one of the Data Protector data duplication methods, any of the media sets can be used for the restore. By default, Data Protector automatically selects the media set that will be used.

  • Page 127: Operators Are Allowed To Restore

    are usually backed up with interdependent data streams and, consequently, restore must be started with the same number of devices as used during backup. • Automatic device selection (default): Data Protector should automatically replace unavailable devices with available devices of a compatible type. You can define which devices are compatible by giving them the same device subtype name during configuration.

  • Page 128: End Users Are Allowed To Restore

    This section provides only a short overview of the disaster recovery concepts. Detailed disaster recovery concepts, planning, preparation, and procedures are described in the HP Data Protector disaster recovery guide. A computer disaster refers to any event that renders a computer system unbootable, whether due to human error, hardware or software failure, natural disaster, etc.
  • Page 129 and recovery of the operating system with all the configuration information that defines the environment. This has to be completed in order to recover other user data. After a computer disaster has occurred, the system (referred as target system) is typically in a non-bootable state and the goal of Data Protector disaster recovery is to restore this system to the original system configuration.

  • Page 130: Disaster Recovery Methods

    The system is booted from the OBDR tape and automatically recovered. For a list of supported disaster recovery methods for a particular operating system, see the Support Matrices in the HP Data Protector product announcements, software notes, and references or on the Web: http://www.hp.com/support/manuals...

  • Page 131: Alternative Disaster Recovery Methods

    Alternative disaster recovery methods This section compares the Data Protector disaster recovery concept with concepts of other vendors. This section points out only significant aspects of alternative recovery concepts. Two alternative recovery approaches are discussed: Recovery methods supported by operating system vendors Most vendors provide their own methods, but when it comes to restore, they typically require the following steps: Reinstall the operating system from scratch...
  • Page 132 Planning your backup strategy...

  • Page 133: Media Management And Devices

    3 Media management and devices In this chapter This chapter describes Data Protector concepts of media and device management. It discusses media pools, devices, and large libraries. It is organized as follows: “Media management” on page 133 “Media life cycle” on page 134 “Media pools”...

  • Page 134: Media Life Cycle

    Media management functionality Data Protector provides the following media management functionality that allows simple and efficient management of a large number of media: • Grouping media into logical groups, media pools, that enable you to think about large sets of media without having to worry about each medium individually. •...

  • Page 135: Media Pools

    This includes initializing (formatting) media for use with Data Protector and assigning media to media pools, which are used to track the media. For more information, see begin” on page 145. Using media for backup. This defines how media are selected for backup, how the condition of the media is checked, how new backups are added to the media, and when data on the media is overwritten.
  • Page 136 else, does not matter; it always belongs to its pool until it is recycled and exported from the cell. Several devices can use media from the same pool. Media pool property examples Examples of pool properties are: • appendable This allows Data Protector to append data to the media in this pool when performing subsequent backup sessions.

  • Page 137: Free Pools

    and one for Windows XP systems) • per system (every system has its own pool) • organizational structure (all systems in department_A have a pool, and systems in department_B have another pool) • systems categories (running large databases, or business critical applications) •...

  • Page 138: Free Pools

    What is a free pool? A free pool is an auxiliary source of media of the same type (for example, DLT) for use when all free media in a regular pool run out. It helps to avoid failed backups due to missing (free) media. Figure 36 Free pools When is a free pool used? Media are moved between regular and free pools on two events...
  • Page 139 between all media pools that support free pool usage. • Reduced operator intervention for backup Assuming that all free media are shared, the need for mount requests is reduced. Free pool properties A free pool: • can be created manually or automatically when you configure the use of one. You cannot delete free pools if they are linked to a normal pool or are not empty.

  • Page 140: Media Pool Usage Examples

    Media pool usage examples The examples below show some configurations you may want to consider when choosing the appropriate strategy for a particular backup environment. Example 1 In the model shown in media pool. The backup specification does not reference a pool, so the default pool is used, which is part of the device definition.

  • Page 141: Configuration Of Media Pools For Large Libraries

    Figure 38 Configuration of media pools for large libraries Example 3 Figure 39 on page 142 shows an example when data is backed up to media in a media pool with multiple devices simultaneously. Higher performance is achieved due to the use of several devices in parallel, regardless of which pool is used. For more information, see “Device lists and load balancing”...

  • Page 142: Multiple Devices, Single Media Pool

    Figure 39 Multiple devices, single media pool Example 4 Data is backed up to media in multiple media pools on multiple devices simultaneously. If you want to use the same device with different pools, you need to create several backup specifications. In the example below, a separate media pool is dedicated to each database application.

  • Page 143: Implementing A Media Rotation Policy

    Figure 40 Multiple devices, multiple media pools Implementing a media rotation policy What is a media rotation policy? A media rotation policy defines how media are used during backup, including the following. In defining a media rotation policy, answer the following questions: •...

  • Page 144: Media Rotation And Data Protector

    Media rotation and Data Protector Automatic media rotation and media handling Data Protector automates media rotation and media handling as follows: • Because media are grouped into media pools, you no longer need to manage single media. Data Protector automatically tracks and manages each single medium in the media pools.

  • Page 145: Media Management Before Backups Begin

    rotation. Additional media will be required in case you: • Assume 10% overhead added by Data Protector to the data on the media for directory and file information. This information is already calculated in the backup preview size. • After the media no longer fulfill the usage criteria, they need to be replaced. •...

  • Page 146: Location Field

    Data Protector also assigns each medium a media ID that uniquely identifies this medium. An ANSI X3.27 label is also written on the tape for identification on other systems. Data Protector writes these labels with other information to a medium header and to the IDB.

  • Page 147: Media Management During Backup Sessions

    Media management during backup sessions What happens during backup? During a backup session, Data Protector automatically selects media for backup and keeps track of which data is backed up to which media. This simplifies management of media so that the operator does not need to know exactly which data was backed up to which media.

  • Page 148: Adding Data To Media During Backup Sessions

    Media condition The condition of the media also influences which media are selected for backup, for example, media in good condition are used for backup before media in fair condition. For more information, see Adding data to media during backup sessions To maximize space usage of media as well as backup and restore efficiency, you can select how Data Protector treats the space on the medium left over from the previous backup.

  • Page 149: Multiple Objects And Sessions Per Medium, Sequential Writes

    Figure 41 Multiple objects and sessions per medium, sequential writes Figure 41 on page 149 shows an example of eight sequential writes over four sessions, using the appendable media usage policy. The data was written in four sessions, one object at a time. The three media belong to the same media pool. Medium_A and medium_B are already full, while medium_C has still some space left.

  • Page 150: Writing Data To Several Media Sets During Backup

    concurrently written in sess_7 and the second one in sess_8. Note that one object can be stretched over several media. The media usage policy is appendable. Figure 44 Each object written on a separate medium Figure 44 on page 150 shows an example of using one backup specification per object with the non-appendable media usage policy.

  • Page 151: Media Management After Backup Sessions

    • media age The age of a medium is calculated as the number of months that have elapsed since you formatted, or initialized, the medium. Once a medium is older than the threshold number of months, it is marked as poor. •...
  • Page 152 • A report showing media used for backup within a specified time-frame. • A report showing which backup specifications have used specified media during the backup. • A report showing media stored at a specific location with data protection expiring in a specific time.

  • Page 153: Restoring From Media In A Vault

    “Keeping backed up data and information about the Devices Data Protector supports a number of devices available on the market. For an up-to-date list of supported devices, see the HP Data Protector product announcements, software notes, and references. Using devices with Data Protector To use a device with Data Protector, you must configure the device in the Data Protector cell.
  • Page 154 By selecting a dedicated menu item in the GUI, a web browser is invoked and the console interface is automatically loaded into it. For a list of device types for which this feature is available, see the HP Data Protector product announcements, software notes, and references. IMPORTANT:...

  • Page 155: Device Lists And Load Balancing

    Device lists and load balancing Multiple devices for backup When configuring a backup specification, you can specify several standalone devices or multiple drives in a library device that will be used for the operation. In this case, the operation is faster because data is backed up in parallel to multiple devices (drives).

  • Page 156: How Load Balancing Works

    gets full, the backup automatically continues on the medium in the next device in the device chain. How load balancing works For example, assume that there are 100 objects configured for backup to four devices with concurrency set to three and with load balancing parameters MIN and MAX both configured at two.

  • Page 157: Segment Size

    The number of Disk Agents started for each Media Agent is called Disk Agent (backup) concurrency and can be modified using the Advanced options for the device or when configuring a backup. Data Protector provides default numbers that are sufficient for most cases.

  • Page 158: Block Size

    NOTE: Some tape technologies place limitations on the number of file marks per medium. Ensure that your segment size is not too low. Figure 45 Data format Segment size, measured in megabytes, is the maximum size of data segments. If you back up a large number of small files, the actual segment size can be limited by the maximum size of catalog segments.

  • Page 159: Number Of Disk Agent Buffers

    be done before formatting tapes. For example, a tape written with the default block size cannot be appended to using a different block size. NOTE: Use the same block size for media that can be used with different device types. Data Protector can only append data to media using the same block size.

  • Page 160: Standalone Devices

    Physical device collision When specifying a device used for backup, you may specify one device name in one backup specification and another device name of the same physical device in a different backup specification. Depending on the backup schedule, this may result in Data Protector trying to use the same physical device in several backup sessions at the same time, thus creating a collision.

  • Page 161: Small Magazine Devices

    Data Protector treats the magazine as if it were a single medium. A magazine has a larger capacity than a single medium and is easier to handle than several single media. For a list of supported devices, see the HP Data Protector product announcements, software notes, and references.

  • Page 162: Large Libraries

    SCSI IDs, four for the drives and one for the robotic mechanism. Data Protector also supports silo libraries, such as HP StorageWorks Libraries, StorageTek/ACSLS and ADIC/GRAU AML. For a list of supported devices, see the HP Data Protector product announcements, software notes, and references.

  • Page 163: Sharing A Library With Other Applications

    For example, out of the 60 slots library you might use slots 1-40 with Data Protector. The remaining slots would then be used and controlled by a different application. Sharing of the library with other applications is especially important with large HP libraries and silo libraries, such as StorageTek/ACSLS or ADIC/GRAU AML devices.

  • Page 164: Cleaning Tape Support

    You can optionally use the barcode as medium label during the initialization of the medium. Cleaning tape support HP Data Protector provides automatic cleaning for most devices using a cleaning tape. This medium will be used automatically by Data Protector if a dirty drive event from the device is detected.

  • Page 165: Connecting Drives To Multiple Systems

    robotics. Figure 47 Connecting drives to multiple systems Control protocols and Data Protector Media Agents The drives in the library must be able to physically connect to different systems that have a Data Protector Media Agent (the General Media Agent or the NDMP Media Agent) installed.

  • Page 166: Required Data Protector Media Agent For Drive Control

    • SCSI—for robotics other libraries • NDMP—for NDMP robotics All four library robotic control protocols are implemented in both the General Media Agent and in the NDMP Media Agent. Drive control Any Data Protector client system configured to control a drive in a library (regardless of the drive control protocol and platform used) can communicate with any Data Protector client system configured to control the robotics in the library (regardless of the robotics control protocol and platform used).

  • Page 167: Required Data Protector Media Agent For Robotic Control

    Agent or the NDMP Media Agent) required on a client system configured for robotic control of a library with drives shared among multiple client systems. Table 1 1 Required Data Protector Media Agent for robotic control Drive control protocol (NDMP or SCSI) Exemplary configurations Figures Figure 48...

  • Page 168: Sharing A Scsi Library

    Figure 48 Sharing a SCSI library (robotics attached to a Data Protector Client System) Figure 48 on page 168 shows a SCSI library, with its robotics attached to and configured on the Data Protector client system with either the General Media Agent or the NDMP Media Agent installed.

  • Page 169: Sharing A Scsi Library (Robotics Attached To An Ndmp Server)

    Figure 49 Sharing a SCSI library (robotics attached to an NDMP Server) Figure 49 on page 169 shows a SCSI library, with its robotics attached to an NDMP Server and configured on the Data Protector client system with either the General Media Agent or the NDMP Media Agent installed.

  • Page 170: Data Protector And Storage Area Networks

    Figure 50 Sharing an ADIC/GRAU or StorageTek ACS library Figure 50 on page 170 shows an ADIC/GRAU or StorageTek ACS library, with its robotics attached to an ADIC/GRAU or StorageTek ACS Server and configured on the Data Protector client system with either the General Media Agent or the NDMP Media Agent installed.

  • Page 171: Storage Area Networks

    Storage Area Networks A Storage Area Network (SAN), depicted in Figure 51 on page 172, is a new approach to network storage that separates storage management from server management with a network devoted to storage. A SAN provides any-to-any connectivity for all network resources, thus enabling device sharing between multiple client systems and increasing data traffic performance as well as the availability of devices.

  • Page 172: Fibre Channel

    Figure 51 Storage Area Network Fibre Channel Fibre Channel is an ANSI standard for high-speed computer interconnection. Using either optical or copper cables, it allows the bidirectional transmission of large data files at up to 4.25 gigabits per second, and can be deployed between sites within a 30 kilometer range.

  • Page 173: Point-To-Point Topology

    For a list of supported configurations, see the HP Data Protector product announcements, software notes, and references or manuals. Point-to-point topology This topology allows the connecting of two nodes, typically a server and a backup device.

  • Page 174: Switched Topology

    Figure 52 Loop initialization protocol Switched topology The switched topology provides any-to-any connectivity between all nodes connected to a switch. Switches are easy to install and use, because the Fibre Channel protocol provides self-configuration and self-management. Switches automatically detect what is connected (nodes, FC-AL Hubs or other FC switches), and configure themselves accordingly.

  • Page 175: Device Sharing In San

    Device sharing in SAN Data Protector supports the SAN concept by enabling multiple systems to share backup devices in the SAN environment. The same physical device can be accessed from multiple systems. Thus, any system can perform a local backup on some device or any other device.

  • Page 176: Example Multipath Configuration

    Figure 53 Example multipath configuration Why use multiple paths With previous versions of Data Protector, a device could be accessed from only one client. To overcome this problem, several logical devices had to be configured for a physical device using a lock name. Thus, if you were using lock names for configuring access from different systems to a single physical device, you had to configure all devices on every system.

  • Page 177: Device Locking

    Paths that are on the client to which the objects are restored, if all objects are restored to the same target client Paths that were used for backup Other available paths If direct library access is enabled, local paths (paths on the destination client) are used for library control first, regardless of the configured order.

  • Page 178: Indirect And Direct Library Access

    This is called Indirect Library Access. In the example depicted in systems are attached to an HP StorageWorks DLT multidrive library. The client system castor controls the robotics and the first drive, while the client system pollux controls the second drive.

  • Page 179: Direct Library Access

    Figure 55 on page 180 shows an HP StorageWorks DLT multidrive library attached via a SAN to two client systems. Both client systems have access to the library and to both drives. The SCSI protocol is used for communication with the library.

  • Page 180: Device Sharing In Clusters

    Figure 55 Direct Library Access Device sharing in clusters Clustering, which is often used in combination with the SAN concept, is based on sharing network resources (for example network names, disks, and tapes devices) between nodes. Cluster-aware applications can at any time run on any node in a cluster (they run on virtual hosts).

  • Page 181: Floating Drives

    Floating drives Floating drives are device that are configured on a virtual host, using virtual system names. Floating drives should be configured for the backup of cluster-aware applications. This ensures that no matter on which node in the cluster the application is currently running, Data Protector always starts a Media Agent on that same node.
  • Page 182 Media management and devices...

  • Page 183: Users And User Groups

    4 Users and user groups In this chapter This chapter discusses Data Protector security, users, user groups, and user rights. It is organized as follows: “Increased security for Data Protector “Users and user groups” on page 184 Increased security for Data Protector users Data Protector provides advanced security functionality that prevents unauthorized backing up or restoring of data.

  • Page 184: Users And User Groups

    can see and restore the backed up data. You can make data visible to other users using the Data Protector Public option. For instructions, see the Data Protector online Help. Users and user groups To use Data Protector, you must be added to the Data Protector configuration as a Data Protector user with certain privileges.

  • Page 185: Using Predefined User Groups

    Using predefined user groups The following default groups are provided by Data Protector: Table 12 Data Protector predefined user groups User group Admin Operator End-user NOTE: Admin capabilities are powerful. A member of the Data Protector admin user group has system administrator privileges on all the clients in the Data Protector cell.
  • Page 186 Users and user groups...

  • Page 187: The Data Protector Internal Database

    5 The Data Protector internal database In this chapter This chapter describes the Data Protector internal database (IDB) architecture, as well as its usage and operation. Explanations of the database parts and their records are presented, along with recommendations on how to manage database growth and performance, including formulas for calculating its size.

  • Page 188: The Idb On The Windows Cell Manager

    • Fast and convenient restore The information stored in the IDB enables you to quickly find the media required for a restore, and therefore makes the restore much faster. It also offers you the convenience of being able to browse for files and directories to be restored.

  • Page 189: The Idb On The Unix Cell Manager

    The IDB on the UNIX Cell Manager is located in the /var/opt/omni/server/db40 directory. IDB format The IDB on the HP-UX and Solaris Cell Manager stores all text information in ASCII single- and multi-byte formats. The ASCII format limits the support of filenames and messages localized to other languages.

  • Page 190: Media Management Database (Mmdb)

    For robustness considerations and recommendations for optimizing robustness by relocating some IDB directories, see the online Help index: “robustness of IDB“. Underlying technology The MMDB and CDB parts are implemented using an embedded database consisting of tablespaces. This database is controlled by the RDS database server process. All changes to the MMDB and CDB are updated using transaction logs.

  • Page 191: Catalog Database (Cdb)

    A file or directory on the HP-UX or Solaris Cell Manager occupies approximately 50-70 bytes, and a file or directory on the Windows Cell Manager occupies 70- 1 00 bytes in the IDB.

  • Page 192: Detail Catalog Binary Files (Dcbf)

    when one of these files starts running out of space, so that you can add new files to extend the size of the filenames part of the IDB. Size and growth for CDB (objects and positions) The CDB records other than filenames occupy a minor share of space in the IDB. Space consumption is in the range of 100 MB for a medium size backup environment.

  • Page 193: Session Messages Binary Files (Smbf)

    On other Windows systems: Data_Protector_home\db40\msg • On UNIX systems: /var/opt/omni/server/db40/msg You can relocate the directory by editing the SessionMessageDir global option. For more information on the Data Protector global options file, see the HP Data Protector troubleshooting guide. Concepts guide...

  • Page 194: Serverless Integrations Binary Files (Sibf)

    Serverless Integrations Binary Files (SIBF) SIBF records The Serverless Integrations Binary Files stores raw NDMP restore data. This data is necessary for restore NDMP objects. SIBF size and growth The SIBF does not grow very big in size. For more details, see ”...

  • Page 195: During Restore

    starts creating new ones, which are necessary for an IDB recovery. During restore When configuring a restore, Data Protector performs a set of queries in the CDB and DCBF parts to enable users to browse virtual filesystems of backed up data. These browse queries are done in two steps.

  • Page 196: Removing The Detail Catalog

    Removing the detail catalog When the detail catalog is removed for a specific medium, its DC binary file is removed. The same result is achieved by removing the catalog protection for all object versions and object copies on that medium (the next daily maintenance of DC binary files removes the binary file).

  • Page 197: Idb Growth And Performance

    Once you configure the IDB, its maintenance is reduced to a minimum, mainly acting on notifications and reports. IDB recovery An IDB recovery is needed if some of the IDB files are missing or corrupted. The recovery procedure depends on the level of corruption. For detailed information, see the online Help index: “IDB, recovery“.

  • Page 198: Idb Growth And Performance: Key Tunable Parameters

    • Growth of your backup environment The number of systems being backed up in the cell influences the IDB growth. Plan for the growth of your backup environment. • Character encoding used for your filenames (applicable for UNIX only) Depending on the filename encoding, a character in the filename can take up from one to three bytes in the IDB.

  • Page 199: Logging Level As An Idb Key Tunable Parameter

    Figure 57 The influence of logging level and catalog protection on IDB growth Logging level as an IDB key tunable parameter What is logging level? Logging level determines the amount of details about backed up files and directories written to the IDB. You can always restore your data, regardless of the logging level used during backup.
  • Page 200 Log Directories No Log The different settings influence the IDB growth, the backup speed, and the convenience of browsing for data to be restored. Impact on performance The logging level defines the amount of data written to the IDB during a backup. This also influences the IDB speed, and therefore the backup process.

  • Page 201: Catalog Protection As An Idb Key Tunable Parameter

    Catalog protection as an IDB key tunable parameter What is catalog protection? Catalog protection determines how long the information about backed up data is available in the IDB. This is different from data protection, which determines how long the backed up data is available on the medium itself. If there is no catalog protection, you can still restore your data, but you cannot browse for it in the Data Protector GUI.
  • Page 202 protection is set for 4 weeks, then significant growth of the IDB stops after 4 weeks. Therefore, in this case, the IDB is 13 times larger if the catalog protection is set to Permanent. It is recommended that catalog protection includes at least the last full backup. For example, you can set a catalog protection of 8 weeks for full backups and one week for incremental backups.

  • Page 203: Idb Size Estimation

    If the number of files grows into the tens of millions, or there are tens of thousands of files generated on a daily basis, and you use the Log All option, then backup speed and IDB growth will become a problem in a relatively short period of time. In this situation, you have the following options: •...
  • Page 204 The Data Protector internal database...

  • Page 205: Service Management

    This chapter describes the concepts behind the service management features and benefits available in both a standalone Data Protector installation and through its integration with HP service management products. It is organized as follows: “Overview” on page 205 “Native Data Protector...

  • Page 206: Data Protector And Service Management

    Service management measures and reports are a key tool IT managers can use to demonstrate value delivered to the organization and also to maintain competitive cost structures. Service providers use Service Level Agreements (SLAs), that typically establish availability and performance objectives, to document provider-customer contractual expectations.

  • Page 207: Native Data Protector Functionality

    Application Response Measurement Version 2.0 API (ARM 2.0 API). Registration of this data can be performed with HP Performance Agent (PA). • Built-in monitoring of running sessions allows you to instantly react to occurrences in your backup environment.

  • Page 208: Application Response Measurement Version 2.0 (Arm 2.0 Api)

    (and also user supplied information that may be relevant to a particular transaction) for ARM compliant system management and monitoring tools such as HP Performance Agent (PA). PA will log ARM transaction information in its repository for subsequent analysis and reporting. It can also raise real time alerts (or “alarms”) when the elapsed time of a specific transaction, such...

  • Page 209: Arm Functionality

    PA is already present or vice versa, the transaction data will immediately show up in PA and HP Performance Manager (PM). On HP-UX, the only required task is to create a link from a PA library to a Data Protector directory. For more information, see the online Help index: “ARM integration, installing“.

  • Page 210: Integration With Hp Operations Manager Software

    Integration with HP Operations Manager software Functionality of the Data Protector OM integration Data Protector integrates with HP Operations Manager software (OM). OM simplifies management of large networks by allowing the operator to monitor and administer the network and the applications from a single point. Once Data Protector is integrated in the OM environment, the network administrator can immediately see if anything is wrong during backup and react upon the information given.

  • Page 211: Reporting And Notification

    management session or respond to “mount” requests. If you make use of the Manager-of-Managers, you can monitor sessions of multiple cells simultaneously from one user interface. Reporting and notification Data Protector reporting represents a powerful, customizable, and flexible tool for managing and planning your backup environment.

  • Page 212: Event Logging And Notification

    The Data Protector built-in notification engine sends alerts or activates the Data Protector reporting mechanism based on the log entries. The event log is the information source for SLA-compliance reports in Data Protector or in HP software management applications. In addition to reports, log entries feed HP software management applications via the Data Protector SPI (SMART Plug-In) so that they can trigger preventive or corrective actions (for details, see the example under 3.1).

  • Page 213: Data Protector Log Files

    Data Protector services (if they are stopped) to Windows Application Log, set the EventLogMessages variable in the Data Protector global options file to 1. For more information on the Data Protector global options file, see the HP Data Protector troubleshooting guide.

  • Page 214: Data Protector Checking And Maintenance Mechanism

    Data Protector checking and maintenance mechanism Data Protector has a rich automated daily self-check and maintenance mechanism, which improves its operational reliability and predictability. Data Protector’s self-check and maintenance tasks include: • “Not Enough Free Media” check • “Data Protector License Expiration” check For more information, see the online Help index: “checks performed by Data Protector”.

  • Page 215: Service Management Integrations

    Data Protector OM-R integration The integration of Data Protector with HP Operations Manager software (OM) is extended by adding HP Reporter 3.7 or 3.8 (English version). With Reporter, service providers can generate reports from the OM console as a central management point.

  • Page 216: Data Protector Reporter Example

    • Media Pool Reports • Performance An IT Service Provider can use these reports to demonstrate its SLA compliance to a customer. For example, the “Data Protector Transaction Performance” Report consists of service performance metrics (one of the IT SLA parameters): Figure 60 Data Protector Reporter example In addition to SLA compliance reports, An IT Service Provider can generate monthly operational reports for the Data Protector environment.

  • Page 217: Data Protector Om Sip

    Figure 61 Operational error status report Data Protector OM SIP This integration also uses SIP to provide Data Protector information through a web-based interface. It does not require OVO to be installed. The integration provides information through tables and gauges. Concepts guide...

  • Page 218: Direct Sip Integration Example

    Figure 62 Direct SIP integration example Service management...

  • Page 219: How Data Protector Operates

    7 How Data Protector operates In this chapter This chapter describes the operation of Data Protector. It explains Data Protector processes (on UNIX) and services (on Windows), backup and restore sessions, and media management sessions. It is organized as follows: “Data Protector processes or “Backup sessions”...

  • Page 220: Backup Sessions

    UIProxy For instructions on how to manually start or stop the Data Protector processes and services, see online Help. Backup sessions This section describes how a backup session is started, what happens during a backup session, and the processes and services involved. What is a backup session? When a backup specification is started it is called a backup session.

  • Page 221: Scheduled And Interactive Backup Sessions

    Scheduled and interactive backup sessions Scheduled backup session A scheduled backup session is started by the Data Protector Scheduler at the time you have specified. You can view the progress of the scheduled backup session in the Data Protector monitor. Interactive backup session An interactive backup session is started from the Data Protector user interface directly.

  • Page 222: Backup Session Information Flow (1)

    The BSM starts Disk Agents (DAs) for each disk to be backed up in parallel. The actual number of Disk Agents started depends on the concurrency of Disk Agents configured in the backup specification. This is the number of Disk Agents that can be started to send data in parallel to a Media Agent, thus allowing a device to stream.

  • Page 223: Pre-Exec And Post-Exec Commands

    To prevent Data Protector processes from exceeding system capabilities, the maximum number of concurrent backup sessions is limited. The limit is configurable. Figure 64 on page 223 shows multiple sessions running concurrently. Figure 64 Backup session information flow - multiple sessions Pre-exec and post-exec commands Data Protector pre-exec commands enable you to execute some actions before a backup or a restore session.

  • Page 224: Queuing Of Backup Sessions

    Queuing of backup sessions Timeout When a backup session is started, Data Protector tries to allocate all needed resources, such as devices. The session is queued until the required minimum resources are available. If the resources are still unavailable after the timeout, the session is aborted. The timeout period can be set using the SmWaitForDevice global option.

  • Page 225: Backing Up With Disk Discovery

    You can configure a Data Protector notification to send an e-mail to the operator with information about the mount request. The operator can take the appropriate actions, such as manually loading the needed media or aborting the session. For more information, see “Reporting and Automating a mount request...

  • Page 226: Restore Session Data Flow And Processes

    A restore session is started interactively. You tell Data Protector what to restore, let Data Protector determine the needed media, select some options and start the restore. You and other users can monitor the progress of the session. Restore session data flow and processes What happens in a restore session? When a restore session, as shown in happens:...

  • Page 227: Queuing Of Restore Sessions

    Figure 65 Restore session information flow How many restore sessions can run concurrently? A number of restore sessions can run in the cell at the same time. This number is limited by resources in the cell, such as the Cell Manager and systems with connected devices.

  • Page 228: Mount Requests In A Restore Session

    Mount requests in a restore session What is a mount request? A mount request appears in a restore session when the media needed for restore are not available in the device. Data Protector allows you to configure a desired action that should happen when a mount request appears.

  • Page 229: Fast Multiple Single File Restore

    Figure 66 Parallel restore session flow In a parallel restore, Data Protector reads multiplexed data for all selected objects and assembles the parts needed for all the objects on the fly, sending the right data to the right Disk Agents. This improves performance when reading from the media. The performance is additionally improved if the selected objects are written to different physical disks.

  • Page 230: Automated And Interactive Object Copy Sessions

    What is an object copy session? An object copy session is a process that creates an additional copy of the backed up data on a different media set. During an object copy session, the selected backed up objects are copied from the source to the target media. Automated and interactive object copy sessions Automated object copy session An automated object copy session can either be scheduled or started immediately...
  • Page 231 copying. The Media Agents load the source and target media allocated according to the backup policies. Media Agents read the data from the source media and connect to the Media Agents loaded with the target media. If destination devices are not specified per object, Data Protector selects them automatically from those you selected in the object copy specification according to the following criteria in the order of priority: •...

  • Page 232: Queuing Of Object Copy Sessions

    Figure 67 Object copy session information flow Queuing of object copy sessions Timeout When an object copy session is started, Data Protector tries to allocate all needed resources. The session is queued until the required minimum resources are available. If the resources are still unavailable after the timeout, the session is aborted. The timeout period can be set using the SmWaitForDevice global option.

  • Page 233: Object Consolidation Sessions

    Object consolidation sessions This section describes how an object consolidation session is started, what happens during the session, and the processes and services involved. What is an object consolidation session? An object consolidation session is a process that merges a restore chain of a backup object, consisting of a full backup and at least one incremental backup, into a new, consolidated version of this object.

  • Page 234: Queuing Of Object Consolidation Sessions

    The CSM opens the IDB, reads the information about the needed media, and writes the information about the object consolidation session, such as generated messages, to the IDB. The CSM locks the devices. The session is queued until all read Media Agents and the minimum required write Media Agents are locked, with the same timeout as for backup.

  • Page 235: Mount Requests In An Object Consolidation Session

    The timeout period can be set using the SmWaitForDevice global option. Mount requests in an object consolidation session What is a mount request? A mount request in an object consolidation session is issued when a source or a target medium needed for the object consolidation operation is not available. Responding to a mount request Responding to a mount request includes providing the required medium and confirming the mount request.
  • Page 236 The MSM starts the Media Agents (MAs) on the system that has devices used for the media management session. Media Agents perform the requested operation and send generated messages to the Data Protector user interface, where you can track the progress. The session is also stored in the IDB.

  • Page 237: Integration With Database Applications

    “Overview of database “Filesystem backup of databases and “Online backup of databases and For a detailed list of supported integrations, see the HP Data Protector product announcements, software notes, and references. Overview of database operation From the user’s perspective, a database is a set of data. Data in a database is stored in tables.

  • Page 238: Relational Database

    Figure 68 Relational database Figure 68 on page 238 shows a typical relational database with the structures described below. Data files are physical files that contain all of a database’s data. They change randomly and can be very large. They are internally divided into pages. Transaction logs record all database transactions before they are further processed.

  • Page 239: Filesystem Backup Of Databases And Applications

    The functionality of the backup APIs varies depending on the database vendor. Data Protector integrations are available for major databases and applications. For a detailed list of supported integrations, see the HP Data Protector product announcements, software notes, and references. Concepts guide...

  • Page 240: Data Protector Integration With Databases

    consistent data (even if it may not be consistent on the disk) while at the same time keeping the database operational. Figure 69 Data Protector integration with databases Figure 69 on page 240 shows how a relational database is integrated with Data Protector.
  • Page 241 different disks. • The logical structure of the database can be browsed. It is possible to select only a subset of the database. • Applications are aware of backup operation and keep track of which parts are backed up. • Several modes of backup are possible.
  • Page 242 Integration with database applications...

  • Page 243: Direct Backup

    “serverless” backup technologies. For enterprises and service providers that manage mission critical Oracle environments, Data Protector’s direct backup feature is a non-intrusive, serverless backup extension to HP’s family of network backup solutions. support” on page 249 Concepts guide...

  • Page 244: Direct Backup

    Direct backup extends the benefits of HP’s ZDB solution by moving data directly from disk to tape and making the load on the backup server negligible or even making the backup server optional. It minimizes the impact on database production servers by using hardware-based mirroring technologies rather than intrusive software-based snapshots.

  • Page 245: Direct Backup Benefits

    Direct backup supports backup of application data files and control files and of disk images -- either raw disk or raw logical volume. Direct backup benefits Because the data mover is in the SAN bridge and the technology that interprets the target system is built into the General Media Agent, direct backup users can use a low-cost management server to drive the backup and can avoid having to invest in multiple servers to perform block identification.

  • Page 246: Environment

    Figure 70 on page 246 shows a basic direct backup configuration. The Resolve Agent is on a separate backup host in this configuration. Data, however, does not move through this host. Figure 70 Direct backup architecture Environment This section describes the direct backup environment in terms of the devices that need to be connected and what they need to be connected to.

  • Page 247: About Resolve

    with mirrors configured with enough disk space. • The SAN is properly configured in order to provide access to source (disks) and target (tape) devices from both the XCopy engine and the host where the Data Protector General Media Agent is running. This means that LUN masking and SAN zoning must be configured so that: •...

  • Page 248: Xcopy + Resolve

    XCopy + Resolve Prior to Resolve, you needed a server with a matching file system to get this information. This was because even with the right server, getting this information could be difficult as the operating system might have converted the actual physical sectors into its logical view before returning the information.

  • Page 249: Restore

    There are two restore options when using direct backup: • If you are using the HP StorageWorks XP disk array and you have instant recovery capability, you can use it to restore the data. For an explanation of using instant recovery, see the HP Data Protector zero downtime backup administrator's guide.

  • Page 250: Supported Configurations

    Note that in this configuration, the Cell Manager host can be running any of the operating systems supported by Data Protector. The application and Resolve Agent hosts must be running HP-UX 1 1.1 1. Direct backup...

  • Page 251: Two Hosts: Cell Manager/Resolve Agent And Application

    Also, the machine that hosts the Cell Manager and the Resolve Agent can be of minimal processing capacity. Note that in this configuration, both hosts must be running HP-UX 1 1.1 1. Basic configuration: single host This solution uses a single host on which the Cell Manager, application, and Resolve Agent are all installed.
  • Page 252 Media Agent may impact the application database’s performance (XCopy’s processing requirements are negligible). Note that in this configuration, the host must be running HP-UX 1 1.1 1. Direct backup...

  • Page 253: 10 Disk Backup

    10 Disk backup In this chapter This chapter introduces the concepts associated with backing up data to disk and the technologies that enable it. It also discusses the disk-to-disk backup configurations that are supported by Data Protector. It is organized as follows: “Overview”...

  • Page 254: Disk Backup Benefits

    Disk backup benefits There are many situations in which it is advantageous to use disk-based devices when performing backups. Disk-based devices are, in fact, specific files in specified directories, to which you can back up data instead of or in addition to backing it up to tape.

  • Page 255: Data Protector Disk-Based Devices

    compared to tape-based storage. Data Protector disk-based devices Data Protector has the following disk-based devices: • Standalone file device • File jukebox device • File library device Standalone file device The standalone file device is the simplest disk-based backup device. It consists of a single slot to which data can be backed up.
  • Page 256 of free disk space approaches the configured minimum amount required for the device to work. This enables you to free more disk space in good time for the device to continue saving data. If all the space allocated to the file library device is ever completely used, a warning message appears on the screen with instructions as to how to solve the problem.

  • Page 257: 1 Synthetic Backup

    1 1 Synthetic backup In this chapter This chapter introduces the concept of synthetic backup and explains the synthetic backup solution provided by Data Protector. It is organized as follows: “Overview” on page 253 “Disk backup benefits” on page 254 “Data Protector disk-based “Restore and synthetic Overview...

  • Page 258: Synthetic Backup Benefits

    new, synthetic full backup. This can be repeated indefinitely, with no need to run a full backup again. In terms of restore speed, a synthetic full backup is equivalent to a conventional full backup. The restore chain consists of only one element, so a restore is as quick and simple as possible.

  • Page 259: Synthetic Backup

    The following figures explain the concept of synthetic backup and virtual full backup. They show how a synthetic full backup or a virtual full backup is created from a full backup and any number of incremental backups. Figure 72 Synthetic backup Figure 72 on page 259 shows how a synthetic full backup is created.

  • Page 260: Synthetic Backup And Media Space Consumption

    Figure 73 Virtual full backup Figure 73 on page 260 shows how a virtual full backup is created. With this type of backup, all the backups reside in a single file library that uses distributed file media format. The Restore Media Agent (RMA) reads the information about the full backup and the incremental backups, and generates the data for the virtual full backup.

  • Page 261: Full And Incremental Backups

    Figure 74 Full and incremental backups Figure 74 on page 261, conventional backups were performed. To restore to the latest possible state, you need the full backup and all four incremental backups. The restore chain consists of five elements, which often reside on different media. Such a restore can take a considerable amount of time, as each incremental backup must be read.

  • Page 262: How Data Protection Periods Affect Restore From Synthetic Backup

    Figure 76 Regular synthetic backup Figure 76 on page 262 shows a situation where a synthetic backup was performed after each incremental backup. This strategy enables the simplest and quickest restore to the latest possible state, or to any earlier point in time that was backed up. Only one element is required for restore, namely the synthetic full backup of the desired point in time.
  • Page 263 By default, the last synthetic full backup in the backup chain is used for restore, irrespective of whether the preceding backups are still valid or their protection has already expired and the objects are removed from the IDB. For additional safety, set data protection to permanent so that data on the media is not overwritten unintentionally.
  • Page 264 Synthetic backup...

  • Page 265: 12 Split Mirror Concepts

    12 Split mirror concepts In this chapter This chapter introduces the split mirror backup concept and discusses the configurations that are supported by HP. It is organized as follows: “Overview” on page 243 “Supported configurations” on page 269 Overview Modern high availability (HA) storage configurations introduce new demands on backup concepts.

  • Page 266: Split Mirror Backup Concept

    The target volumes in replica are typically connected to a separate client, which also has tape devices connected to allow for local backup. Usually, hardware mirror technologies such as HP StorageWorks Disk Array XP or EMC Symmetrix are used to create a replica such as: •...
  • Page 267 Several replicas can exist at the same time. For example, HP StorageWorks Disk Array XP Concepts guide...
  • Page 268 (tape) from the replica. The replicas (up to three) can be used for various purposes, such as offline data processing or instant recovery; the latter is possible only if HP StorageWorks BusinessCopy XP configuration was used. It is only possible to restore objects from a ZDB-to-disk session by using the instant recovery functionality.

  • Page 269: Supported Configurations

    Supported configurations Local mirror - dual host This solution uses a local mirroring functionality such as Business Copy XP. Both disks are in the same disk array, which means the I/O infrastructure of the RAID system is actually shared between the application client (or host) and the backup client. As the application client and the backup client are two physically different systems, they can use their own resources (I/O channels, CPUs, memory, etc.) for their dedicated activities, such as backup, without interfering with each other.

  • Page 270: Local Mirror - Single Host

    database into a consistent mode that permits the split, as well as to take it out of this mode again. This configuration enables an offline backup of a very large database in a short time, as well as an online backup that creates very few archive log files, since the backup mode time of the database is kept to a minimum.

  • Page 271: Split Mirror - Remote Mirror (Lan-Free Remote Backup - Data Ha)

    Figure 80 Split mirror - remote mirror (LAN-free remote backup - data The remote mirror transfers data to a physically separate site where it can be backed up to locally available tapes. This allows the separation of production data from backup data, eliminating the risk of a fire or other disaster damaging both the production and the backup environment at the same time.

  • Page 272: Local/Remote Mirror Combination

    (site B). Figure 81 Local/remote mirror combination (disaster recovery integrated backup [Service HA - HP-UX only]) In order to have the failover functionality independent of the backup operation, the backup client must be a separate additional client outside the cluster. If a MetroCluster solution is implemented, the cluster arbitration client could be the backup client.

  • Page 273: Other Configurations

    It is important to control and specify which configurations are supported. All the configurations shown above are supported by HP. For an updated list of supported configurations,see the following URL: http://www.hp.com/support/ manuals.
  • Page 274 Split mirror concepts...

  • Page 275: 13 Snapshot Concepts

    13 Snapshot concepts In this chapter This chapter introduces the snapshot backup concepts and discusses the configurations that are supported by HP. It is organized as follows: “Overview” on page 275F “Supported configurations” on page 281 Overview The rapidly expanding requirement for high availability storage configurations has led to the introduction of new zero downtime backup (ZDB) technologies.

  • Page 276: Snapshot Concepts

    RAID1 provides duplication of all data, RAID5 provides protection of data by parity. The snapshot integrations for Data Protector are designed to work with disk arrays that use the snapshot technology, such as HP StorageWorks Virtual Array and HP StorageWorks Enterprise Virtual Array. Snapshot concepts In a typical basic setup using the snapshot technology, a single disk array might be connected to separate application and backup systems.

  • Page 277: Snapshot Backup

    Figure 82 Snapshot backup The backup client is set up as a Data Protector client with tape devices connected, to allow a local backup to be performed. When a backup session begins, the application client enters the backup mode of operation while the backup client is being prepared for the backup process;...

  • Page 278: Snapshot Backup Types

    Snapshot data of the application data is produced using the virtual disk array technologies, such as: • HP StorageWorks Business Copy Virtual Array • HP StorageWorks Enterprise Virtual Array Snapshot backup types Within the Data Protector snapshot integrations, the following types of snapshot backups are available: •...

  • Page 279: Instant Recovery

    Instant recovery During snapshot backup sessions, several snapshot copies of data can be produced and can be retained on a disk array, each point-in-time copy in its own replica. The retained snapshot copies of data can then be used for various purposes, such as offline data processing or instant recovery.
  • Page 280 not written to that reserved space until necessary. As the data changes on the source volume, the snapshot data on the target volume is updated with the original data. Since this snapshot technique caches only the difference between the ever-changing original data content against the point-in-time state, copy-on-write snapshots with the preallocation of disk space are depended on their source volumes;...

  • Page 281: Supported Configurations

    Supported configurations Basic configuration: single disk array - dual host Both hosts are connected to the same disk array, so that the I/O infrastructure of the RAID system is actually shared between the application client and the backup client. As the application client and the backup client are two physically different systems, they can use their own resources (I/O channels, CPUs, memory, etc.) for their dedicated activities, such as backup, without interfering with each other.

  • Page 282: Other Supported Configurations

    Put the database into a consistent mode that permits a snapshot to be taken. Perform a snapshot of the application data. Return the database to normal operating mode. This configuration enables an offline backup of a very large database in a short time, as well as an online backup that creates very few archive log files, since the backup mode time of the database is kept to a minimum.

  • Page 283: Multiple Application Hosts - Single Backup Host

    Figure 85 Multiple application hosts - single backup host With this solution, multiple application hosts may be connected to a single or multiple disk arrays, which are, in turn connected to a single dedicated backup host. The I/O infrastructure of the RAID systems is shared between the application clients and the backup client.

  • Page 284: Disk Array(S) - Single Host

    Figure 86 Disk array(s) - single host In cases where no dedicated backup server is available, both functions (application and backup) can be performed on the same client (or host). Offline backups of mail applications, for instance, could reduce the downtime of the application to minutes instead of hours in this way.

  • Page 285: Lvm Mirroring - Hp Storageworks Virtual Array Only

    Figure 87 LVM mirroring - HP StorageWorks Virtual Array only In the supported configurations described previously, only Business Copy functionality is possible with the HP StorageWorks Virtual Array integration. However, by using LVM mirroring, it is possible to create snapshot copies of data between different virtual arrays, writing to both at the same time.

  • Page 286: Other Configurations

    It is important to control and specify which configurations are supported. Only the configurations shown are supported by HP. For an updated list of supported configurations, see the following URL: http://www.hp.com/support/manuals. Snapshot concepts...
  • Page 287 In the event that you want to back up data in a configuration not listed, this does not mean that it cannot be supported. Please contact your local HP representative or HP Consulting to investigate the supportability of additional configurations.
  • Page 288 Snapshot concepts...

  • Page 289: Microsoft Volume Shadow Copy Service

    “Overview” on page 289 “Data Protector Volume Shadow Copy “VSS filesystem backup and For detailed information on the integration, see the HP Data Protector integration guide. For detailed information on the filesystem backup and restore, see the Data Protector online Help.
  • Page 290 Volume Shadow Copy service (VSS) is a software service introduced by Microsoft on Windows operating systems. This service collaborates with the backup application, applications to be backed up, shadow copy providers, and the operating system kernel to implement the management of volume shadow copies and shadow copy sets.

  • Page 291: Data Protector And Vss

    The example of the hardware provider is disk array, which has its hardware mechanism of providing point-in-time state of a disk. A software provider operates on physical disks and uses software mechanism for providing point-in-time state on a disk. The system provider, MS Software Shadow Copy Provider, is a software mechanism, which is a part of the Windows Server 2003 operating system.

  • Page 292: Actors Of The Traditional Backup Model

    Figure 89 Actors of the traditional backup model Figure 90 Actors of the VSS backup model In the traditional model, the backup application had to communicate with each application it backed up individually. In the VSS model, the backup application communicates with the VSS only, and the VSS coordinates the whole backup process.

  • Page 293: Data Protector Volume Shadow Copy Integration

    The advantages of using Volume Shadow Copy service are as follows • A unified backup interface for all writers. • A unified backup interface for all shadow copy providers. • Writers provide data integrity at application level. Intervention from the backup application is unnecessary.
  • Page 294 For detailed information on the integration, see the HP Data Protector integration guide. VSS backup In case of VSS-aware writers’ backup, the consistency of data is provided at writer level and does not depend on the backup application. Data Protector follows the requirements provided by the writers when selecting what to back up.

  • Page 295: Vss Filesystem Backup And Restore

    VSS filesystem backup and restore Some applications are not aware of the Volume Shadow Copy service. Such applications cannot guarantee consistency of data during the creation of a shadow copy. The VSS mechanism cannot coordinate the activities of these applications in order to perform a consistent backup.
  • Page 296 • Backups can be performed at any time without locking out users. • There is little or no impact on the performance of the application system during the backup process. Backup and restore VSS backup is implemented as an additional Windows filesystem backup on Windows Server 2003.

  • Page 297: A Backup Scenarios

    A Backup scenarios In this appendix This Appendix describes two scenarios: one for company XYZ and one for company ABC. Both companies plan to enhance their data storage systems. Their current backup solutions are described along with the inherent problems. Solutions are then proposed to alleviate the problems and to meet the future data storage needs of both companies.
  • Page 298 done. • Local versus network backups Determine which systems, that the backup devices are connected to, are backed up locally and which are backed up over the network. • Backup policy implementation • How backups are done, and which backup options are used This defines the frequency of full and incremental backups.

  • Page 299: Company Xyz

    Table 15 Hardware and software environment of XYZ Depart. #Servers English 1 Windows 2000 Figure 91 on page 300. #Clients Current Projected data data (in 5 Years) 35 GB 107 GB Windows Table 15 on page 299 Current devices 3 HP StorageWorks DAT24 autoloaders Concepts guide...

  • Page 300: Current Xyz Backup Topology

    Other 1 AIX Languages Admin 1 HP-UX Figure 91 on page 300 shows how the XYZ backup environment is organized. Figure 91 Current XYZ backup topology XYZ currently has three servers with an estimated total data volume of 67 GB. In the English Department, data is copied manually by each of the employees to their respective servers at the end of each day.
  • Page 301 Saturdays. Problems with the current solution The current backup solution is not able to keep pace with the growth rate of XYZ. The actual backup process is very labor intensive. The current backup process makes it impossible to consolidate backup management or create an enterprise-wide backup architecture.

  • Page 302: Backup Strategy Requirements

    Software The backup servers need to be running on one of the supported operating systems. For information on supported operating systems for the Cell Manager, see the HP Data Protector product announcements, software notes, and references. • Protection Against Disaster Upon completion of backups, the media will be stored on-site, where they will be retrieved upon request for file restoration.

  • Page 303: Proposed Solution

    Department as the Installation Server for UNIX systems. The backup devices consist of an HP StorageWorks DLT 41 15w Library, as well as two of the HP StorageWorks DAT24 autoloaders that had been used to date. This suffices for the next five years at the present data growth rate of 20 to 25% per year.
  • Page 304 * One HP StorageWorks DAT24 autoloader is currently used to locally back up the 12 GB of data. The other HP StorageWorks DAT24 autoloader is used to back up the IDB and configuration files. The rest of the data in this department is backed up remotely to the HP StorageWorks DLT 41 15 library.

  • Page 305: Proposed Xyz Backup Topology

    Figure 92 Proposed XYZ backup topology • The Cell Manager maintains the Catalog Database (CDB). This provides a minimum of 20 days of file and directory detail on the current database. Estimating the size of the IDB The Internal Database Capacity Planning Tool was used to estimate the size of the IDB in a year.

  • Page 306: Input Parameters

    Figure 93 Input parameters The results are shown in to grow to approximately 419.75 MB. Figure 94 Results • Hardware • Network All systems should be on the same 100TX network for maximum performance. This network has a sustained data transfer rate of 10 MB/s, or 36 GB/h, of data.
  • Page 307 This is the transfer rate assumed for the remainder of this section. Currently, the total amount of data to be backed up to the HP StorageWorks DLT 41 15w Library as a full backup, whether this is a single full backup, or the staggering approach is used, is about 55 GB.

  • Page 308: The Staggering Approach

    All the other available data in the system, which is currently about 55 GB) is backed up remotely to the HP StorageWorks DLT 41 15w Library, which has a sustained data transfer rate of 3 MB/s, or 10.5 GB/h. Most of this data is via the 100TX network, which has a sustained data transfer rate of 10 MB/s, or 36 GB/h, of data.

  • Page 309: Remote Full Backups To The Hp Dlt 41 15 Library

    Table 18 Remote full backups to the HP DLT 41 15 library Department Current Data/Backup Time English 23 GB / 3 h Other Languages 22 GB / 3 h...
  • Page 310 • OTH_BS Backup specification for data in the Other Languages Department to be backed up remotely to the HP StorageWorks DLT 41 15w Library. Schedule the backup specification such that Data Protector will run a full backup every Saturday at 20:00 and level 1 incremental backups every day, except Sunday at 20:00.
  • Page 311 Set data protection to permanent so that data on the media is not overwritten unintentionally. • Concurrency Set to 5 to allow up to five Disk Agents to concurrently write data to the HP StorageWorks DLT 41 15w Library. This will increase backup performance. • Media Pool For the IDB, select the DB_Pool with the appropriate media to be used for the backup.
  • Page 312 done by the software solution, including queries done internally in the database to prevent the administrator from having to find media that require ejection. The second migration of media is done to move media from the vault to a security company.

  • Page 313: Company Abc

    Brings the media from a vault, enters the media in the HP StorageWorks DLT 41 15w Library or other device and then scans the media. Selects the specific object to be restored using the List From Media option, if the media are not in the IDB.

  • Page 314: Current Abc Cape Town Backup Topology

    2 HP StorageWorks DAT24 autoloaders. The system architecture of ABC Cape Town includes the SAP R/3 system using Oracle databases. Three HP T600 servers are used as SAP database servers. ABC Cape Town uses K260 SAP application servers that are configured into application groups, i.e.

  • Page 315: Backup Strategy Requirements

    and first and last dates on which backups were performed on the media. At the end of each quarter, media are sent for storage to a central offsite location. Problems with current solution The current backup solution has the following deficiencies: •...

  • Page 316: How Long Data Should Be Kept

    Type of data Company resource data Project data Personal data This recovery time mainly consists of the time needed to access the media and the time required to actually restore data to a disk. • How long specific types of data should be kept Table 21 on page 316 shows how long data should be kept.

  • Page 317: Proposed Solution

    Location ABC Pretoria ABC Durban Plans for future growth of the amount of data ABC plans to grow at 15 to 20% per year. The amount of data to be backed up is expected to grow accordingly. This has implications not only on the amount of time it takes to run backups and backup devices needed for backup, but also on the size of the IDB.

  • Page 318: Abc Enterprise Environment

    Centralized Media Management Database allows you to share libraries between cells within each MoM environment. Each of the three locations should have its own library. Use the HP StorageWorks DLT 4228w Library for the ABC Cape Town environment. Use HP StorageWorks DLT 41 15w Libraries for ABC Pretoria and ABC Durban.

  • Page 319: Abc Cell Configuration

    Media Management Database. This should be configured on the MoM of cell F to enable the sharing of the HP StorageWorks DLT 41 15w Library between the cells. The following is a detailed account of the proposed solution: Proposed solution in detail •...
  • Page 320 Centralized Media Management Database in MoM cell A to allow you to share the same library with cells B and C. Share the HP StorageWorks DLT 4228w Library for the ABC Cape Town environment. With a capacity of 1,1 TB in compressed format, this library should suffice for the company’s projected needs...

  • Page 321: Abc Cape Town Enterprise Backup Environment

    Media Management Database. This should be configured on the MoM of cell D. The purpose of using the CMMDB is to enable the sharing of the HP StorageWorks DLT 41 15w Library between the cells. Each of the cells in the environment should have its own Catalog Database.

  • Page 322: Results

    catalog protection (3 weeks), number of full backups per week (1), and number of incremental backups per week (5). Figure 98 Input parameters The results are shown in Figure 99 on page 322. In one year, the database is expected to grow to approximately 667.47 MB. Figure 99 Results You can also use the Internal Database Capacity Planning Tool to estimate the size of the IDB in environments with online databases (Oracle, SAP R/3).
  • Page 323 ABC Cape Town and two HP StorageWorks DLT 41 15w Libraries for ABC Pretoria and ABC Durban as well as 7 HP StorageWorks DAT24 autoloaders for backing up the IDB and configuration files in all the cells and 2 HP StorageWorks DAT24 autoloaders for backing up the Microsoft SQL database and the Microsoft Exchange database at ABC Cape Town.
  • Page 324 47 GB. ABC’s backup policy requires that two backup generations of data be kept. Therefore, 47*2 GB, or 94 GB, of library space will be required for storage. The HP StorageWorks DAT24 autoloader’s 144 GB storage capacity therefore suffices.
  • Page 325 12 hours. Cells D and E at ABC Pretoria share an HP StorageWorks DLT 41 15w Library. This library has a single drive and a sustained data transfer rate of 3 MB/s, or 10.5 GB/h.
  • Page 326 Table 26 The Staggering Approach for ABC Cape Town Cell A Incr1 Cell B Incr1 Backup scenarios Location Description Pretoria Durban HP StorageWorks DLT 41 15w Library Durban HP StorageWorks DAT24 autoloaders Durban Table 26 on page 326: Incr1 Incr1...
  • Page 327 Cell C Incr1 Incr1 • SERVERS_A...G Backup specifications for the company’s servers to prepare for disaster recovery. Each time a new server is installed, or an existing server is upgraded, this backup specification is updated. Schedule the backup specifications such that Data Protector will run full backups as shown in and level 1 incremental backups every work day.
  • Page 328 Name SERVERS_C DB_D DB_E SERVERS_D SERVERS_E USERS_D USERS_E DB_F DB_G SERVERS_F SERVERS_G USERS_F USERS_G Backup options Use default Data Protector backup options. Set the following options as follows: • Log Directories This filesystem backup option ensures that details only on directories are stored in the Catalog Database.
  • Page 329 Media will be moved to the vault once a week and replaced by new media in the HP StorageWorks DLT 4228w Library, the HP StorageWorks DLT 41 15w Library, and HP StorageWorks DAT24 autoloaders. All actions excluding the...
  • Page 330 Identifies the media needed for restore. Brings the media from a vault, enters the media in the HP StorageWorks DLT 4228w Library, the or HP StorageWorks DLT 41 15w Library or other device and then scans the media.

  • Page 331: B Further Information

    B Further information In this appendix This appendix provides additional information about some of the aspects of Data Protector concepts, including backup generations, examples of automated media copying, and internationalization. Backup generations Data Protector provides a time/date related protection model. It is easy to map a generation-based backup model to the time-based model, assuming regular backups are done.

  • Page 332: Examples Of Automated Media Copying

    Figure 100 Backup generations You configure Data Protector to automatically maintain the desired number of backup generations by selecting the appropriate data and catalog protection durations, and scheduling for unattended backups, both full and incremental. For example, to keep three backup generations while you have weekly full backups and daily leveled incremental backups, specify data protection to 7*3+6=27 days.

  • Page 333: Example 1: Automated Media Copying Of Filesystem Backups

    To do this, you will use automated media copying. You use an HP StorageWorks 6/60 Tape Library with 6 LTO drives, and LTO Ultrium 1 media. Based on previous experience, you assume that the data transfer rate is about 80 GB per hour, and the average capacity of a medium is 153 GB.
  • Page 334 have 900 GB of data to back up. The data is divided among backup specifications in the following way: • BackupSpec1 (Drive 1) - 300 GB • BackupSpec2 (Drive 2) - 300 GB • BackupSpec3 (Drive 3) - 150 GB •...

  • Page 335: Full Backup

    Figure 101 Incr1 backup and automated media copying Full backup Configuring backups You schedule your weekly full backup on Friday at 6 PM. The data protection is set to 8 weeks. You have 3000 GB of data to back up. The data is divided among backup specifications in the following way: •...
  • Page 336 Again, you use post-backup media copying to copy the media used with BackupSpec1 and BackupSpec2, and scheduled media copying to copy media used in BackupSpec3 and BackupSpec4. The devices and the data protection settings are the same as those used for the copying of the Incr1 backup.

  • Page 337: Full Backup And Automated Media Copying

    Figure 102 Full backup and automated media copying You schedule your monthly full backup on Sunday at 6 AM. This backup is intended for archiving purposes, so it is normally not copied. Figure 103 on page 338 presents an overview of the time when the devices are busy. Note that this is a rough overview, so the graph ignores the partial overlap of some of the backup and copy sessions.

  • Page 338: Example 2: Automated Media Copying Of Oracle Database Backups

    The media should be copied after the backup finishes. To do this, you will use post-backup media copying. You use an HP StorageWorks 10/700 Tape Library with 10 LTO drives, and LTO Ultrium 1 media. Based on previous experience, you assume that the data transfer rate is about 80 GB per hour, and the average capacity of a medium is 153 GB.

  • Page 339: Full Backup

    Full backup Configuring backups You schedule your daily full backup each day from Monday to Friday at 6 PM. The data protection is set to 4 weeks. You have 500 GB of data to back up. You use Drive 1, Drive 2, Drive 3, and Drive 4. The backup uses 4 media and is completed in approximately 2 hours.

  • Page 340: Internationalization

    “File name handling” on page 341. Data Protector is localized to various languages. For more information on available languages, see the HP Data Protector product announcements, software notes, and references, your supplier, or the local HP sales office. Further information...

  • Page 341: File Name Handling

    GUI. For example, when using Data Protector, it is possible to back up files on HP-UX where the Disk Agent is running and to view those files using the Data Protector GUI running on Windows. Unless identical code sets are used on both platforms, file names may not display properly.

  • Page 342: File Name Handling During Backup

    UNIX incompatibility example Three users working on a Solaris system without Data Protector installed, each using a different character set, create files on the same filesystem outside the ASCII character range. If the users then use the ls command to display the files they created as well as those created by the other users, the following happens: •...
  • Page 343 • Data Protector searches the tape for the specified data and restores it • the original file names (original copies from the tape) are restored Concepts guide...
  • Page 344 Further information...

  • Page 345: Glossary

    Glossary access rights ACSLS Active Directory AES 256–bit encryption application agent application system archived redo log user rights. (StorageTek specific term) The Automated Cartridge System Library Server (ACSLS) software that manages the Automated Cartridge System (ACS). (Windows specific term) The directory service in a Windows network.
  • Page 346 archive logging ASR Set Audit Logs Audit Report Auditing Information autochanger autoloader Automatic Storage Management Glossary is using: • ARCHIVELOG - The filled online redo log files are archived before they are reused. The database can be recovered if an instance or a disk fails. A “hot” backup can be performed only when the database is running in this mode.
  • Page 347 and mirroring capabilities to optimize performance. automigration (VLS specific term) The functionality that allows data backups to be first made to the VLS' virtual tapes and then migrated to physical tapes (one virtual tape emulating one physical tape) without using an intermediate backup application. See also BACKINT (SAP R/3 specific term) SAP R/3 backup programs can call the...
  • Page 348 backup owner backup session backup set backup set backup specification backup system Glossary integration objects — backup stream identification, indicating the backed up database/application items. • Description: For filesystem objects — uniquely defines objects with identical client name and mount point. For integration objects —...
  • Page 349 IAP A Data Protector based backup to the HP Integrated Archiving Platform (IAP) appliance. It takes advantage of the IAP capability to eliminate redundancies in the stored data at a block (or chunk) level, by creating a unique content address for each data chunk.
  • Page 350 See also BCV. (HP StorageWorks Virtual Array specific term) Business Copy VA allows you to maintain internal copies of HP StorageWorks Virtual Array LUNs for data backup or data duplication within the same virtual array. The copies (child or Business Copy LUNs) can be used for various purposes, such as backup, data analysis or development.
  • Page 351 (HP StorageWorks Disk Array XP specific term) Continuous Access XP allows you to create and maintain remote copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data duplication, backup, and disaster recovery. CA operations involve the main (primary) disk arrays and the remote (secondary) disk arrays.
  • Page 352 catalog protection CDF file cell Cell Manager centralized licensing Centralized Media Management Glossary into the door panel of a library. The purpose is to enter or eject media. Defines how long information about backed up data (such as file names and file versions) is kept in the IDB. See also data protection.
  • Page 353 (CMMDB) Change Journal (Windows specific term) A Windows filesystem feature that logs a record of each change as it occurs to the files and directories on a local NTFS volume. Change Log (Windows specific term) A module that can be queried to Provider determine which objects on a filesystem have been created, modified, or deleted.
  • Page 354 disk discovery client or client system cluster-aware application cluster continuous replication CMD Script for Informix Server CMMDB Glossary backup starts, Data Protector discovers the disks on the clients. Client backup with disk discovery simplifies backup configuration and improves backup coverage of systems that often mount or dismount disks.
  • Page 355 It provides database consistency information used for recovery. copy set (HP StorageWorks EVA specific term) A pair that consists of the source volumes on a local EVA and their replica on a remote EVA.
  • Page 356 More than one database is backed up at a time if the number of available devices allows you to perform backups in parallel. (HP StorageWorks EVA specific term) A logical grouping of EVA virtual disks. It can contain up to eight copy sets provided...
  • Page 357 EVA log. See also database server A computer with a large database stored on it, such as the SAP R/3 or Microsoft SQL database. A server has a database that can be accessed by clients. Dbobject (Informix Server specific term) An Informix Server physical database object.
  • Page 358 device streaming DHCP server differential backup differential backup differential database backup direct backup Glossary on the same EMC Symmetrix unit. You can use a device group to identify and work with a subset of the available EMC Symmetrix devices. A device is streaming if it can feed enough data to the medium to keep it moving forward continuously.
  • Page 359 point concept of Windows. An NTFS 5 directory junction allows you to redirect a directory/file request to another location. disaster recovery A process to restore a client’s main system disk to a state close to the time when a (full) backup was performed. Disk Agent A component needed on a client to back it up and restore it.
  • Page 360 distributed file media format Distributed File System (DFS) DNS server domain controller DR image DR OS drive Glossary accessibility for restore. The backup stages consist of backing up data to one media type first (for example disk) and later copying it to a different media type (for example tape). A media format, available with the file library, which supports a space efficient type of synthetic backup called virtual full backup.
  • Page 361 computer system. drive-based Data Protector drive-based encryption uses the encryption encryption functionality of the drive. While performing the backup, the drive encrypts both the data and the meta-data that is written to the medium. drive index A number that identifies the mechanical position of a drive inside a library device.
  • Page 362 Windows) or package (on UNIX) from one cluster node to another. A failover can occur mostly because of software or hardware failures or maintenance on the primary node. (HP StorageWorks EVA specific term) An operation that reverses the roles of source and destination in CA+BC EVA configurations.
  • Page 363 (HP StorageWorks Disk Array XP specific term) HP StorageWorks Disk Array XP allows up to three mirror copies of a primary volume and each of these copies can have additional two copies.
  • Page 364 flash recovery area fnames.dat formatting free pool full backup full database backup full mailbox backup full ZDB global options file Glossary (Oracle specific term) Flash recovery area is an Oracle 10g/1 1g managed directory, filesystem, or Automatic Storage Management disk group that serves as a centralized storage area for files related to backup and recovery (recovery files).
  • Page 365 Data_Protector_program_data\Config\Server\Options (Windows Server 2008), Data_Protector_home\Config\Server\Options (other Windows systems), or /etc/opt/omni/server/options (HP-UX or Solaris systems). group (Microsoft Cluster Server specific term) A collection of resources (for example disk volumes, application services, IP names, and addresses) that are needed to run a specific cluster-aware applications.
  • Page 366 HP Operations Manager, extending the managed domain. Through the Data Protector integration, which is implemented as an HP Operations Manager SMART Plug-In, a user can have an arbitrary number of Data Protector Cell Managers monitored as an extension to HP Operations Manager.
  • Page 367 HP StorageWorks A logical partition of a physical disk within an HP StorageWorks Virtual Array LUN Virtual Array. LUNs are entities that can be replicated in the HP StorageWorks Business Copy VA configuration, or can be used as standalone entities.
  • Page 368 incremental mailbox backup incremental1 mailbox backup incremental (re)-establish incremental restore incremental ZDB Inet Glossary An incremental mailbox backup backs up all the changes made to the mailbox after the last backup of any type. An incremental1 mailbox backup backs up all the changes made to the mailbox after the last full backup.
  • Page 369 Exchange Server service that is responsible for storage management. Information Store in Microsoft Exchange Server manages two kinds of stores: mailbox stores and public folder stores. A mailbox store consists of mailboxes that belong to individual users. A public folder store contains public folders and messages that are shared among several users.
  • Page 370 Java GUI Client Java GUI Server jukebox jukebox device keychain Key Management Service key store Glossary administration tasks on Sybase SQL Server. The Java GUI Client is a component of the Java GUI that contains only user interface related functionalities and requires connection to the Java GUI Server to function.
  • Page 371 A library contains media in repository slots. Each slot holds one medium (for example, DDS/DAT). Media are moved between slots and drives by a robotic mechanism, allowing random access to media. The library can contain multiple drives. lights-out A backup or restore operation that takes place outside of normal operation or business hours without an operator.
  • Page 372 lock name log_full shell script logging level logical-log files Glossary switch to the LCR copy in a few seconds. If an LCR copy is used for backup and if it is located on a different disk than the original data, then the I/O load on a production database is minimal. A replicated storage group is represented as a new instance of Exchange writer called Exchange Replication Service and can be backed up (using VSS) as a normal storage group.
  • Page 373 log on to Microsoft SQL Server. A login ID is valid if Microsoft SQL Server has an entry for that user in the system table syslogin. login information (Oracle and SAP R/3 specific term) The format of the login to the Oracle information is user_name/password@service, where: Target Database •...
  • Page 374 A mailbox store consists of a binary rich-text .edb file and a streaming native internet content .stm file. (HP StorageWorks Disk Array XP specific term) An HP StorageWorks XP disk array that contains the primary volumes for the CA and BC configurations and acts as a master device.
  • Page 375 backup medium and sends it to the Disk Agent. The Disk Agent then writes the data to the disk. A Media Agent also manages the robotics control of a library. media allocation Determines in which sequence media are used for backup. The policy Strict allocation policy directs Data Protector to prompt for a specific medium.
  • Page 376 Microsoft Management Console (MMC) Microsoft SQL Server Microsoft Volume Shadow Copy Service (VSS) mirror (EMC Symmetrix and HP StorageWorks Disk Array XP specific term) mirror rotation (HP StorageWorks Disk Array XP specific term) Glossary the file to be restored already exists at the destination, the one with the more recent modification date is kept.
  • Page 377 The Data Protector Media Session Manager, which runs on the Cell Manager and controls media sessions, such as copying media. MU number (HP StorageWorks Disk Array XP specific term) Mirror Unit number. An integer number (0, 1 or 2), used to indicate a first-level mirror. See also...
  • Page 378 device object object consolidation object consolidation session object copy object copy session object copying object ID object mirror object mirroring offline backup Glossary bootable disk and can thus be used as a backup or boot device for disaster recovery purposes. backup object.
  • Page 379 to tape, until streaming of data to the tape is finished. • For ZDB methods, the database is also put into the quiescent state, but for the period of the data replication process only (several seconds). Normal database operation can then be resumed for the rest of the backup process.
  • Page 380 online redo log OpenSSH Oracle Data Guard Oracle instance ORACLE_SID original system Glossary period of the data replication process only (several seconds). Normal database operation can then be resumed for the rest of the backup process. In some cases, transaction logs may also have to be backed up to allow a consistent database to be restored.
  • Page 381 IP names and addresses) that are needed to run a specific cluster-aware application. pair status (HP StorageWorks Disk Array XP specific term) A mirrored pair of disks can have various status values depending on the action performed on it. The three most important status values are:...
  • Page 382 parallel restore parallelism physical device post-exec pre- and post-exec commands prealloc list Glossary is transferred from one disk to the other. The disks do not contain the same data. • PAIR - The mirrored pair is completely synchronized and both disks (the primary volume and the mirrored volume) contain identical data.
  • Page 383 Manager XP application provides an extensive list of commands to report and control the status of the CA and BC applications. The commands communicate through a RAID Manager instance with the HP StorageWorks Disk Array XP Disk Control Unit. This secondary volume (S-VOL) and also...
  • Page 384 rawdisk backup RDBMS RDF1/RDF2 Recovery Catalog Recovery Catalog Database recovery files RecoveryInfo Glossary SCSI commands. disk image backup. Remote Control Unit (RCU). Relational Database Management System. (EMC Symmetrix specific term) A type of SRDF device group. Only RDF devices can be assigned to an RDF group. An RDF1 group type contains source (R1) devices and an RDF2 group type contains target (R2) devices.
  • Page 385 Oracle uses the redo log to record all changes made to data. Remote Control (HP StorageWorks Disk Array XP specific term) The Remote Unit (RCU) Control Unit (RCU) acts as a slave of an MCU in a CA configuration.
  • Page 386 A process that copies data from backup media to a client. (HP StorageWorks Disk Array XP VSS provider specific term) One of two XP VSS hardware provider operation modes. When the XP provider is in the resync mode, the source volume (P-VOL) and its replica (S-VOL) are in the suspended mirror relationship after a backup.
  • Page 387 By setting up a schedule, you automate the start of backups. secondary volume (HP StorageWorks Disk Array XP specific term) secondary (S-VOL) volumes, or S-VOLs, are XP LDEVs that act as a secondary CA or BC mirror of another LDEV (a P-VOL). In the case of CA, S-VOLs can be used as failover devices in a MetroCluster configuration.
  • Page 388 shadow copy provider shadow copy set shared disks SIBF single instancing Site Replication Service slot Glossary duplicate of the original volume at a certain point in time. The data is then backed up from the shadow copy and not from the original volume.
  • Page 389 One binary file is created per session. The files are grouped by year and month. snapshot (HP StorageWorks VA and HP StorageWorks EVA specific term) A form of replica produced using snapshot creation techniques. A range of snapshot types is available, with different characteristics, depending on the arrays/techniques used.
  • Page 390 (EMC Symmetrix and HP StorageWorks Disk Array XP specific term) A replica created using split mirror techniques. Such a replica provides an independent, exact duplicate, or clone of the contents of the source volumes.
  • Page 391 SSE Agent (HP StorageWorks Disk Array XP specific term) A Data Protector software module that executes all tasks required for a split mirror backup integration. It communicates with the HP StorageWorks...
  • Page 392 stackers standalone file device Storage Group StorageTek ACS library storage volume switchover Sybase Backup Server API Sybase SQL Server Symmetrix Agent (SYMA) Glossary for a multi-drive library device. Devices with multiple slots for media storage usually with only one drive. A stacker selects media from the stack sequentially. In contrast, a library can randomly select media from its repository.
  • Page 393 equivalent to a conventional full backup in terms of data, without putting stress on the production servers or the network. A synthetic full backup is created from a previous full backup and any number of incremental backups. synthetic full The result of an object consolidation operation, where a restore backup chain of a backup objects is merged into a new, synthetic full version of this object.
  • Page 394 tapeless backup (ZDB specific term) target database target (R2) device target system target volume Terminal Services thread TimeFinder Glossary divided into one or more tablespaces. Each tablespace has data files or raw volumes exclusively associated with it. ZDB to disk. (Oracle specific term) In RMAN, the target database is the database that you are backing up or restoring.
  • Page 395 file that contains connect descriptors mapped to service names. The file may be maintained centrally or locally, for use by all or individual clients. transaction A mechanism for ensuring that a set of actions is treated as a single unit of work. Databases use transactions to keep track of database changes.
  • Page 396 unattended operation user account (Data Protector user account) User Account Control (UAC) user disk quotas user group user profile user rights Glossary Protector Cell Manager. It is responsible for communication between the Java GUI Client and the Cell Manager, moreover, it performs business logic operations and sends only important information to the client.
  • Page 397 (HP StorageWorks EVA specific term) A unit of storage allocated from an HP StorageWorks Enterprise Virtual Array storage pool. Virtual disks are the entities that are replicated using the HP StorageWorks Enterprise Virtual Array snapshot functionality. See also...
  • Page 398 Microsoft Volume Shadow Copy Microsoft Volume Shadow Copy (HP StorageWorks Disk Array XP VSS provider specific term) One of two XP VSS hardware provider operation modes. When the XP provider is in the VSS compliant mode, the source volume (P-VOL) and its replica (S-VOL) are in simplex, unpaired state after a backup.
  • Page 399 replica, VxFS Veritas Journal Filesystem. VxVM (Veritas A Veritas Volume Manager is a system for managing disk space Volume Manager) on Solaris platforms. A VxVM system consists of an arbitrary group of one or more physical volumes organized into logical disk groups.
  • Page 400 XCopy engine ZDB database ZDB to disk ZDB to disk+tape Glossary communicate with each other through the X/Open Backup Services Application Programmer's Interface (XBSA). (direct backup specific term) A SCSI-3 copy command that allows you to copy data from a storage device having a SCSI source address to a backup device having a SCSI destination address, thus enabling direct backup.
  • Page 401 data in the replica produced is streamed to a backup medium, typically tape. Instant recovery is not possible from such a backup, so the replica need not be retained on the disk array after backup completion. The backed-up data can be restored using standard Data Protector restore from tape.
  • Page 402 Glossary...

  • Page 403: Index

    Index adding data to media during ADIC (EMASS/GRAU) admin user group, 185 alarms, 208 alternative disaster recovery operating system third-party tools, 131 ANSI X3.27 labels, 146 any-to-any connectivity, 171 Application Agents, 42 Application Response Measurement real time alerts, 209 application client snapshot backup, 277 split mirror...
  • Page 404 Backup Agents, 42 backup client split mirror backup, 267 backup client as failover server snapshot backup, 286 split mirror backup, 268 backup concurrency, 157, 311 backup devices, 49, 68 overview, 153 backup duration example calculations, 307, 324 backup environment growth database growth and performance factors, 198 database growth and performance...
  • Page 405 disk backup, 254 synthetic backup, 258 Volume Shadow Copy service, 293 benefits of online integrations, 240 block size backup devices, 158 default, 158 devices, 158 performance, 158 broadcasts, 207 browsing files, 101 BSM, 221 cache memory, 72, 238 Catalog Database location, 192 records, 191 Catalog Database growth factors...
  • Page 406 clients, 42 installing, 64 maintaining, 64 cluster heartbeat, 80 cluster (definition), 79 cluster integrations overview, 82 cluster node, 80 clustering, 79 - 91 automatic restart, 82 Cell Manager availability, 82 device sharing, 180 failover, 81 floating drives, 181 group, 81 heartbeat, 80 load balancing, 82...
  • Page 407 mixed environment, 66 UNIX environment, 64 Windows domains, 65 Windows workgroups, 66 Windows environment, 65 CRS, 220 daily maintenance operation, 196 data hiding from other users, 76 visibility, 76 data encoding, 76 data encryption, 76 data protection, 310 Data Protector architecture Cell Managers, 40 Data Protector...
  • Page 408 format, 189 location, 189 database on the Windows Cell Manager format, 188 location, 188 database architecture, 189 database growth and performance key factors filesystem dynamics, 197 database growth and performance key factors, 197 database growth and performance key tunable parameters, 198 logging level, 199 database growth and performance key...
  • Page 409 159 device streaming, 156 exchangers, 162 GRAU/EMASS, 162 HP StorageWorks DAT Autoloaders, HP StorageWorks DAT24 Autoloaders, 307 HP StorageWorks DLT 41 15w Libraries, 307 HP StorageWorks DLT 4228w Libraries, 323 jukeboxes, 162 library management console, support, 154 load balancing, 155...
  • Page 410 dirty drive detection, 164 disaster, 128 Disaster Recovery Phase 3, 129 disaster recovery, 129 Disaster Recovery concepts, 128 overview, 128 Phase 1, 129 Phase 0, 129 Phase 2, 129 disaster recovery alternative methods, 131 disaster recovery alternative , 131 Disk Agent concurrency, 329 disk performance, 72...
  • Page 411 Agent, 206, 208 HP Performance Agent integration, 209 HP StorageWorks Disk Array HP StorageWorks DAT24 Autoloaders, 307, 324 HP StorageWorks DLT 41 15w HP StorageWorks DLT 4228w HP StorageWorks Enterprise Virtual Array, 276 HP StorageWorks Virtual Array, 276 HTML, 207...
  • Page 412 IDB, 187 advantages, 187 architecture, 189 Catalog Database, 191 Detail Catalog Binary in the Manager-of-Managers environment, 189 management, 196 Media Management on the UNIX Cell on the Windows Cell operation, 194 Serverless Integrations Binary Session Messages Binary size and growth, 188 IDB architecture IDB parts scheme, 190...
  • Page 413 163 cleaning tape connecting to multiple drives, 165 entering and ejecting mail HP StorageWorks DAT HP StorageWorks DAT24 Autoloaders, 307 HP StorageWorks DLT 41 15w Libraries, 307 HP StorageWorks DLT 4228w sessions, Libraries, 323 management console, media handling, 162...
  • Page 414 log all detailed information Catalog Database, 100 log directory names only Catalog Database, 100 log level of information, 104 logging level IDB size and growth, 188 logging level enabling restore, 200 impact on ability to browse for restore, 200 impact on IDB speed and backup processes, 200 impact on restore All, 199...
  • Page 415 default, 136 properties, 136 usage examples, 140 Media Agents, 42 General Media Agent, 165 media allocation policies, 144 media allocation policies, 136, 147 loose, 147 strict, 147 media condition, 150 calculating, 150 fair, 148 good, 148 media condition factors, 150 media description, 145 media...
  • Page 416 mount prompt handling, 111 mount requests, 224, 232, 235 automating, 224 notification, 224 responding, 224, 228 mount requests (restore MSM, 235 multiple cells, 45, 62 multiple devices, 155 multiple slots, 163 NDMP Media Agent, 165 network environment, 39 node cluster, 80 primary, 81 secondary, 81 notification, 38...
  • Page 417 Cell Managers, 64 Installation Servers, 64 number of cells, 62 planning performance, 67 - 73 backup types, 71 compression, 68 devices, 68 direct backups, 68 disk fragmentation, 72 disk performance, 72 fibre channel, 73 hardware compression, 70 infrastructure, 67 load balancing, 70 local backups, 67...
  • Page 418 reporting and notification, 311, 329 broadcasts, 207 e-mail, 207 examples, 212 HTML, 207 SNMP, 207 requirements Direct backup, 249 response time, 208 restore policies, 125 users, 128 restore by query, 312, 330 restore chain, 96 restore duration, 125 factors affecting, 125 parallel restore, 125 restore...
  • Page 419 Measurement, monitor, 210 notification, 211 operative analyses of trends, 206 overview, 205 reporting, 211 service management applications, 206 HP Performance Agent, 206 Service Management examples, 214 service monitoring, 210 services, 219 Session Messages Binary Files, 193 Session Messages Binary Files...
  • Page 420 application client, 277 archive log backup, 278 backup client, 277 backup client as failover concepts, 276 configuration, Campus Cluster with Mirroring, 286 configuration, multiple application hosts - single backup configuration, multiple disk arrays - dual host, 282 configuration, single disk array - dual host, 281 configuration, disk arrays - single host, 284...
  • Page 421 177 sharing devices, 175 storage duration of backed up - 102 storage virtualization, 275 StorageTek/ACSLS, 162 Subscriber's Choice, HP, 34 supported configurations for Direct Backup , 250 switched topology, 174 synthetic backup, 257 benefits, 258 operation, 258 media space...
  • Page 422 294 shadow copy, 290 shadow copy provider, 290 See Volume Shadow Copy service backup, 293 VSS backup model, 291 websites HP Subscriber's Choice for , 34 product manuals, 23 Windows domains, 65 Windows workgroups, 66 writer, 290 Writer Metadata Document...

This manual is also suitable for:

Data protector a.06.10

Table of Contents