HP Data Protector A.06.
Legal and notice information © Copyright 1999, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and 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.
Contents Publication history .............................................................. 21 About this guide ................................................................. 23 Intended audience ............................................................................................. Documentation set ............................................................................................. Guides ....................................................................................................
Media management .......................................................................................... Backup devices ................................................................................................. User interfaces .................................................................................................. Data Protector GUI ...................................................................................... Data Protector Java GUI ..............................................
Data Protector user groups ........................................................................... 75 Data Protector user rights ............................................................................. 75 Visibility of backed up data .......................................................................... 76 Data encryption .......................................................................................... 76 How Data Protector AES 256-bit encryption works .................................
When to schedule backups .................................................................. Staggering full backups ....................................................................... Optimizing for restore ......................................................................... Automated or unattended operation ................................................................... Considerations for unattended backups ....................................................... Duplicating backed up data ....
Vaulting ................................................................................................... 151 Restoring from media in a vault ................................................................... 153 Devices .......................................................................................................... 153 Device lists and load balancing .................................................................. 155 How load balancing works ................................................
Data Protector user rights ........................................................................... 185 5 The Data Protector internal database ............................... 187 In this chapter ................................................................................................. 187 About the IDB ................................................................................................. 187 The IDB on the Windows Cell Manager .......................................................
Data Protector log files ........................................................................ Windows application log ........................................................................... Java-based online reporting ....................................................................... Data Protector checking and maintenance mechanism ................................... Central management, distributed environment ...............................................
Filesystem backup of databases and applications ................................................ 239 Online backup of databases and applications .................................................... 239 9 Direct backup ............................................................... 243 In this chapter ................................................................................................. Overview ......................................................................................................
Local mirror - dual host .............................................................................. Local mirror - single host ............................................................................ Remote mirror ........................................................................................... Local/remote mirror combination ................................................................ Other configurations ................................................................................
Examples of automated media copying .............................................................. Example 1: automated media copying of filesystem backups ........................... Incr1 backup ..................................................................................... Full backup ........................................................................................ Example 2: automated media copying of Oracle database backups ................ Full backup .....................................
Figures 1 Data Protector graphical user interface ............................................... 33 2 Backup process ............................................................................... 39 3 Restore process ............................................................................... 39 4 Network backup .............................................................................. 40 5 The Data Protector cell (physical view and logical view) .......................
23 Incremental backups ........................................................................ 95 24 Leveled incremental backups ............................................................. 95 25 Media needed to restore from simple and leveled incremental backups ......................................................................................... 98 26 Media needed to restore from leveled incremental backups ................... 98 27 Backup session ....................................................
50 Sharing an ADIC/GRAU or StorageTek ACS library ........................... 170 51 Storage Area Network ................................................................... 172 52 Loop initialization protocol .............................................................. 174 53 Example multipath configuration ...................................................... 176 54 Indirect Library Access ................................................................... 179 55 Direct Library Access .................
78 Split mirror backup concept ............................................................ 266 79 Local mirror - dual host (full performance, Zero Downtime Backup) ....... 269 80 Split mirror - remote mirror (LAN-free remote backup - data HA) ........... 271 81 Local/remote mirror combination (disaster recovery integrated backup [Service HA - HP-UX only]) .............................................................. 272 82 Snapshot backup ...................................................................
105 Overview of backup and automated media copy sessions ...................
Tables 1 Edition history ................................................................................. 21 2 Document conventions ...................................................................... 31 3 Backup behavior ............................................................................. 85 4 Backup behavior ............................................................................. 87 5 Backup behavior .............................................................................
25 ABC’s Media Pool Usage ............................................................... 325 26 The Staggering Approach for ABC Cape Town .................................. 326 27 ABC’s backup specification configuration .........................................
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 Part number Guide edition Product B6960-90059 August 2002 Data Protector Release A.05.00 B6960-90080 May 2003 Data Protector Release A.05.10 B6960-90105 October 2004 Data Protector Release A.05.
Publication history
About this guide This guide describes Data Protector concepts. Read this manual to fully understand the fundamentals and the model of Data Protector. Intended audience This guide is intended for users interested in understanding the concepts of Data Protector operation and for people who plan company backup strategies. Depending on the required level of detail, you can also use this manual together with the Data Protector online Help.
• HP Data Protector installation and licensing guide This guide describes how to install the Data Protector software, taking into account the operating system and architecture of your environment. This guide also gives details on how to upgrade Data Protector, as well as how to obtain the proper licenses for your environment. • HP Data Protector troubleshooting guide This guide describes how to troubleshoot problems you may encounter when using Data Protector.
• HP Data Protector integration guide for HP Reporter 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.
This guide describes how to configure MPE/iX clients and how to back up and restore MPE/iX data. • HP Data Protector Media Operations user's guide This guide provides tracking and management of offline storage media. It describes the tasks of installing and configuring the application, performing daily media operations and producing reports. • HP Data Protector product announcements, software notes, and references This guide gives a description of new features of HP Data Protector A.06.10.
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 Guide Install Installation and licensing guide MO GS Media Operations getting started guide MO RN Media Operations product announcements, software notes, and references MO UG Media Operations user guide MPE/iX MPE/iX system user guide PA Product announcements, software notes, and references Trouble Troubleshooting guide ZDB Admin ZDB administrator's guide ZDB Concept ZDB concepts guide ZDB IG ZDB integration guide Map The following table shows where to find information of
Integrations Look in these guides for details of the following integrations: Integration Guide HP Operations Manager for UNIX/for Windows IG-OMU, IG-OMW HP Performance Manager IG-PM/PA HP Performance Agent IG-PM/PA Concepts guide 29
Integration Guide HP Reporter IG-R HP Service Information Portal IG-SIP HP StorageWorks Disk Array XP all ZDB HP StorageWorks Enterprise Virtual Array (EVA) all ZDB HP StorageWorks Virtual Array (VA) all ZDB IBM DB2 UDB IG-IBM Informix IG-IBM Lotus Notes/Domino IG-IBM Media Operations MO User MPE/iX system MPE/iX Microsoft Exchange Server IG-MS, ZDB IG Microsoft Exchange Single Mailbox IG-MS Microsoft SQL Server IG-MS, ZDB IG Microsoft Volume Shadow Copy Service (VSS) IG-MS,
Integration Guide Sybase IG-Var EMC Symmetrix all ZDB VMware IG-Var Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 31 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
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.
Figure 1 Data Protector graphical user interface General information General information about Data Protector can be found at http://www.hp.com/go/ dataprotector. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
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: • • • • http://www.hp.com http://www.hp.com/go/software http://www.hp.com/support/manuals http://www.hp.
1 About backup and Data Protector In this chapter This chapter provides an overview of backup and restore concepts. It introduces Data Protector architecture, media management, user interfaces, backup devices, and other features. The chapter concludes with an overview of Data Protector configuration and other tasks needed to set up Data Protector.
Data Protector can be used in environments ranging from a single system to thousands of systems on several sites. Due to the network component concept of Data Protector, elements of the backup infrastructure can be placed in the topology according to user requirements. The numerous backup options and alternatives to setting up a backup infrastructure allow the implementation of virtually any configuration you want.
Data Protector enables you to meet the needs for continued business operations around the clock. In today's globally distributed business environment, company-wide information resources and customer service applications must always be available. Data Protector enables you to meet high availability needs by: • Integrating with clusters to ensure fail-safe operation with the ability to back up virtual nodes.
The DSI integration provides a set of scripts and configuration files from which users are able to see how to add their own queries using Data Protector reporting capabilities. • Monitoring, Reporting and Notification Superior web reporting and notification capabilities allow you to easily view the backup status, monitor active backup operations, and customize reports.
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. What is a restore? A restore is a process that recreates the original data from a backup copy.
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.
The Data Protector internal database (IDB) keeps track of the files you back up so that you can browse and easily recover the entire system or single files. Data Protector facilitates backup and restore jobs. You can do an immediate (or interactive) backup using the Data Protector user interface. You can also schedule your backups to run unattended.
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. The Disk Agent reads or writes data from a disk on the system and sends or receives data from a Media Agent.
Figure 6 Backup or restore operation Backup sessions What is a backup session? A backup session, shown in Figure 7 on page 44, is a process that creates a copy 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.
Figure 7 Backup session A typical backup session is more complex than the one shown in Figure 7 on page 44. 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. Restore sessions What is a restore session? A restore session, shown in Figure 8 on page 44, is a process that restores data from previous backups to a disk.
Enterprise environments What is an enterprise environment? A typical enterprise network environment, shown in Figure 9 on page 45, consists 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.
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 Chapter 2 on page 57. Data Protector allows you to manage multiple cells from a single point.
Figure 11 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. This makes devices of one cell (using the CMMDB) accessible to other cells that use the CMMDB.
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.
Backup devices Data Protector defines and models each device as a physical device with its own usage properties, such as the default pool. This device concept is used because it allows you to easily and flexibly configure devices and use them in conjunction with backup specifications. The definition of the devices is stored in the Data Protector Media Management Database.
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). Both user interfaces can run simultaneously on the same computer. Additionally, a command-line interface is available on Windows and UNIX platforms.
• A Results Tab with all the configuration wizards, properties and lists. • 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. • A comprehensive online Help system called the Help Topics, and context-sensitive Help called the Help Navigator.
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 52 About backup and Data Protector
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.
Benefits of Java GUI The Data Protector Java GUI has the following advantages over the original Data Protector GUI: • Portability The Data Protector Java GUI architecture enables you to install Java GUI Clients on all platforms that support Java Runtime Environment (JRE). • Easy firewall configuration The Java GUI Client uses port 5556 to connect to the Java GUI Server. It is easier to configure Java GUI in a firewall environment because only one port needs to be opened.
Overview of tasks to set up Data Protector This section provides an overview of global tasks to set up your Data Protector backup environment. Depending on the size and complexity of your environment, you may not need to go through all these steps. 1. Analyze your network and organizational structure. Decide which systems need to be backed up. 2. Check if there are any special applications and databases which you want to back up, such as Microsoft Exchange, Oracle, IBM DB2 UDB, SAP R/3, or others.
7. 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. • Configure backup devices. • Configure media pools and prepare the media. • Configure backup specifications, including backup of the IDB. • Configure reports, if needed. 8.
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.
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: 1.
The allowed downtime has a significant impact on the investments into network 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.
The time needed for backup depends on the type of backup, full or incremental. For more information, see “Full and incremental backups” on page 91. Data 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.
The need to guard premises to prevent unauthorized people from entering. 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.
• 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. This is a solution when the network impairs the backup speed.
is that it can require more administrative work or might even require a separate 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. • Network considerations All client systems of a cell should be on the same LAN for maximum performance.
Installing and maintaining client systems If you have several UNIX and Windows client systems, an efficient mechanism for the installation of Data Protector becomes important. Local installation on every client is not feasible in large environments. Installation Servers and the Cell Manager The main system in a Data Protector cell is the Cell Manager.
that each client system is accessible from every other client system using the same 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.
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.
You can configure a single cell over geographically remote locations. In this case, 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.
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.
High performance hardware other than devices Performance of computer systems The speed of computer systems themselves directly impacts performance. The systems are loaded during backups by reading the disks, handling software compression, and so on. The disk read data rate and CPU usage are important performance criteria for the systems themselves, in addition to I/O performance and network types.
3 fast tape devices, consider using 3 dedicated network links between system_A and system_B. • Load Balancing Using this Data Protector feature, Data Protector dynamically determines which object (disk) should be backed up to which device. Enable this feature, especially to back up a large number of filesystems in a dynamic environment. For more information, see “How load balancing works” on page 156. Note that you cannot predict to which media a particular object is written.
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. Disk image versus filesystem backups It used to be more efficient to back up disk images (raw volumes) rather than filesystems.
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. Data Protector backs up filesystems sequentially, to reduce disk head movements. It also restores files sequentially.
improve performance in your specific environment and determine the optimum asynchronous reading settings. SAN performance If large volumes of data need to be backed up in one session, the time needed to transfer the data becomes significant. This consists of the time required to move the data over a connection (LAN, local, or SAN) to a backup device.
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 Data Protector user rights Visibility and access to backed up data Cells Starting sessions Data Protector security is based on cells.
When is the account checked? 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 Chapter 4 on page 183. 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. Each user group contains defined Data Protector user rights. All the members of the group have the user rights set for the group.
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). For more information about backup owners, see “What is backup ownership?” on page 78.
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 is selected and requests an active encryption key from the KMS.
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.
the CRS process is running, or the user specified as the owner in the backup specification options. For instructions on how to specify a backup owner, see the online Help index: "ownership". Backup ownership and restore Backup ownership affects the ability of users to see and restore data. Unless the object is marked as Public, only the owner of the media set or an administrator can see the data saved in the media set.
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 specific cluster data needed to run the cluster.
you can make an appropriate determination of the ownership of the package (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.
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.
• The Data Protector client is installed in a cluster. The Cell Manager (if not installed in the cluster) in such a case is not fault tolerant; the operations in the cell must be restarted manually.
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.
The following is the expected backup behavior under this configuration. Table 3 Backup behavior Condition Result Failover of the node before a backup starts Successful backup Failover of the node during backup activity Filesystem/disk image backup: The backup session fails. The completed objects from the session can be used for restore, the failed (running and pending) objects need to be backed up again by restarting the session manually. Application backup: The backup session fails.
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 • 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.
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. The following is the expected backup behavior under this configuration.
Data Protector cluster critical resources are defined in the same package (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.
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 • 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.
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: • Customizable automatic restart of backups in case of failover of the Cell Manager. The Data Protector backup specifications can be configured to be restarted in case of failover of the Cell Manager.
Condition Result Failover of the application during backup activity without Cell Manager failover (Cell Manager runs on other node than the application). Filesystem/disk image backup The backup session fails at failover of the node where the filesystem is installed. The completed objects from the session can be used for restore, the failed (running and pending) objects need to be backed up again by restarting the session manually. Application backup The backup session fails.
Full backup Incremental backup Restore Enables simple and quick restore. A restore takes more time because of the number of media needed. IDB impact Occupies more space in the IDB. Occupies less space in the IDB. Data Protector can also make incremental backups of online database applications. These vary from application to application. On Sybase, for instance, this type of backup is referred to as a transaction backup (a backup of transaction logs modified since the last backup).
Incremental backups depend on the last full backup. If you specify an incremental 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.
Incr A simple incremental backup, shown in Figure 23 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 24 on page 95, depends on the last backup of the next lower level that is still protected. For example, an Incr1 backup saves all changes since the last full backup, while an Incr5 backup saves all changes since the last Incr4 backup.
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.
8 Full <---- Incr1 <---- Incr3 9 Full <---- Incr1 <---- Incr2 <---- Incr3 10 Full <---- <---- <---- Incr2 <---- Incr3 11 Full <---- <---- <---- <---- <---- Incr3 How to read Table 7 on page 95 • The rows in Table 7 on page 95 are independent of each other and show different 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.
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 26 on page 98. Here the required space on the media is slightly larger. Only two media sets need to be accessed to restore to the desired point in time.
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. For more information, see Appendix B on page 331.
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). You can set the protection independently for backed up data and for backup information about this data in the IDB.
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.
available, but you must know which media to use and what needs to be restored, 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.
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. This functionality is needed to move media to a different cell.
on UNIX or disk drives on Windows systems) and the destinations are specified (tape) 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.
• 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.
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. For advanced information on backup sessions, and how to control sessions, see Chapter 7 on page 219.
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. See “Staggering full backups” on page 107.
This section combines all these concepts by giving some examples of backup schedules 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 “Staggering full backups” on page 107.
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.
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. This considerably simplifies and speeds up the restore.
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.
• When is the lowest system usage and user activity? 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.
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. This can be avoided by using pre-exec and post-exec scripts that can be used to synchronize the status of applications with the backup activities.
Object copy Object mirror Media copy Smart Media Copy Appendability of target media Yes Yes No No 2 3 Result of the operation Media containing the selected object versions Media containing the selected object versions Media identical to the source media Media identical to the source media 1 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.
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. Any of these object versions can be used for a restore of the same object version.
Selection of devices 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. Object copying is load balanced by default. Data Protector makes optimum use of the available devices by utilizing as many devices as possible.
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. • Demultiplexing of media You can copy objects to eliminate interleaving of data. • Consolidating a restore chain You can copy all object versions needed for a restore to one media set.
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. Objects from a multiplexed medium are copied to several media that you specify. See Figure 33 on page 118.
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. Migration to another media type You can migrate backed up data to another media type.
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 media sets simultaneously during a backup session.
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: • It increases the availability of backed up data due to the existence of multiple copies.
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: • devices of the same block size are selected, if available • locally attached devices are selected before network attached devices When you perform an object mirror operation from the command line, load balancing is not available.
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.
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. Post-backup media copying Post-backup media copying takes place after the completion of a backup session. It copies the media used in that particular session.
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. Data Protector initiates the copy process, which is then performed by the VLS.
Restoring data Policies for restoring data are an essential part of the overall backup strategy in the company. Keep the following in mind: • Backing up and restoring files is essentially the same as copying files. Therefore, ensure that only authorized people have the rights to restore confidential data. • Ensure that unauthorized people cannot restore files of other people. This section describes some possible implementations of the restore policy using Data Protector.
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. You can influence the media set selection by specifying the media location priority.
SQL Server, and Microsoft SharePoint Portal Server integrations. Such databases 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.
End users are allowed to restore Another possible restore policy is to allow all or just selected end users to restore their own data. This policy provides sufficient security and may relieve the backup operator from doing a number of restore operations. When to use this policy Use this policy in the following cases: • When the end users have sufficient knowledge to handle restores. You may need to provide some training for the users on basic backup concepts and restore operations.
operation can begin. This includes repartitioning and/or reformatting the boot partition 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.
Disaster recovery methods Data Protector supports the following disaster recovery methods: • Manual disaster recovery This is a basic and very flexible disaster recovery method. You need to install and configure the DR OS. Then use Data Protector to restore data (including the operating system files), replacing the operating system files with the restored operating system files.
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: 1. Reinstall the operating system from scratch 2.
Planning your backup strategy
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.
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.
1. Preparing media for backup. 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 “Media management before backups begin” on page 145. 2. 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.
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. If this option is not selected, then the media will contain data from a single session only.
• system platform (one pool for UNIX systems, one for Windows 2000 systems, 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) • backup type (all full backups use one pool, and all incremental backups use another pool) • combinations of the above criteria, and more.
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 (Figure 36 on page 138): • Allocation. Media are moved from a free pool to a regular pool • Deallocation. Media are moved from a regular pool to a free pool.
All free (unprotected, empty) media can be grouped in a free pool and shared 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.
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 Figure 37 on page 140, all objects are backed up to the same media pool. The backup specification does not reference a pool, so the default pool is used, which is part of the device definition.
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” on page 155.
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.
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.
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. • You do not need to decide to which media the backed up data is to be written to; Data Protector does that for you. You back up to a media pool.
By now you should be able to estimate the quantity of media required for a full media 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. • Expect some growth in the volume of data to be backed up.
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. If you change the medium label, Data Protector modifies the medium label in the IDB and not on the medium itself.
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. Backup objects that have been backed up within the same backup session represent a media set.
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 “Calculating media condition” on page 150. 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.
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.
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. The result is higher media consumption. You could combine this with the append incrementals only policy, to get the incremental backups of the object on the same medium.
• 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. • device errors Some device errors result in the medium being marked as poor. If a device fails during a backup, the medium used for the backup in this device is marked as poor.
• 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. • Displaying a list of media needed for a restore and the physical locations where the media are stored. • Filtering of media from the media view based on specific criteria.
Restoring from media in a vault Restoring media from a vault is no different than restoring from any other media. Depending on how your data and catalog protection policies are defined, you may need to do some additional steps: 1. Bring media from a vault and insert the media into a device. 2. If the catalog protection for the media is still valid, restore data simply by selecting what you want to restore using the Data Protector user interface.
in Data Protector using different (logical) device names, for example, one without hardware data compression and another one with hardware data compression. The following sections describe some specific device functionality and how Data Protector operates with various devices. Library management console support Many modern tape libraries provide a management console that allows libraries to be configured, managed, or monitored from a remote system.
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). Balancing the use of devices By default, Data Protector automatically balances the load (the usage) of devices so that they are used evenly. This is called load balancing.
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. If at least two devices are available, the session will start with three objects being backed up in parallel to each of the first two available devices.
Disk agent concurrency 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. For example, on a standard DDS device, two Disk Agents send enough data for the device to stream.
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. Segment size is user configurable for each device. It affects the speed of a restore.
Increasing the block size can improve performance. Changing the block size should 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.
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. Preventing collision To prevent this collision, specify a virtual lockname in both device configurations.
install a Data Protector Media Agent on the system with the device connected. Data Protector can detect and automatically configure most standalone devices. During a backup, Data Protector issues a mount request when the medium in a device is full. The operator must replace the medium for the backup to continue. What are device chains? Data Protector allows you to configure multiple standalone devices to a device chain.
Large libraries What are library devices? Library devices are automated devices, also called autoloaders, exchangers or jukeboxes. In Data Protector, most libraries are configured as SCSI libraries. They contain a number of media cartridges in a device’s repository and can have multiple drives writing to multiple media at a time. A typical library device has a SCSI ID for each drive in the device and one for the library robotic mechanism that moves media from slots to drives and back.
• Obtain the number of required media. See “Implementing a media rotation policy” on page 143. Sharing a library with other applications A library device can be shared with other applications storing data to media in the device. You can decide which drives from the library you want to use with Data Protector. For example, out of a four-drive library you may choose to use only two drives with Data Protector. You can decide which slots in the library you want to manage with Data Protector.
• Scanning the barcodes of the media in a device’s repository is faster, because Data Protector does not need to actually load the media to a drive and read the medium header. • A barcode is automatically read by Data Protector and used to identify the media. • A cleaning tape is automatically detected if it has a CLN barcode prefix. • A barcode is a unique identifier for media in the IDB. You cannot have duplicate barcodes in your environment.
Protector internally redirects the robotic commands to the system that manages the 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. With Data Protector, there are two types of protocols used for drive control: • SCSI—for SCSI or Fibre Channel connected drives.
• 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).
Table 11 on page 167 show the Data Protector Media Agent (the General Media 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.
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. The SCSI robotic control protocol is used by the General Media Agent or the NDMP Media Agent on the client. The Data Protector client system with the attached robotics can also have one or more drives attached.
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. The SCSI robotic control protocol is used by the General Media Agent or the NDMP Media Agent on the client. The NDMP Server with the attached robotics can also have one or more drives attached.
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. The ADIC/GRAU robotic control protocol is used by the General Media Agent or the NDMP Media Agent on the client.
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.
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. Fibre Channel is the most reliable, highest performance solution for information storage, transfer, and retrieval available today.
Point-to-point, loop, and switched Fibre Channel topologies can be mixed to best suit your connectivity and growth requirements. For a list of supported configurations, see the HP Data Protector product announcements, software notes, and references or http://www.hp.com/support/ manuals. Point-to-point topology This topology allows the connecting of two nodes, typically a server and a backup device. It provides the basic benefit of improved performance and longer distances between nodes.
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. Switches provide scaled bandwidth to connected nodes. The switched topology provides real hot-plug of nodes.
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. Because data is transferred over the SAN, backups do not need any bandwidth on your conventional LAN. This type of backup is sometimes referred to as a “LAN-free” backup.
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.
During a restore session, the device paths are selected in the following order: 1. Paths that are on the client to which the objects are restored, if all objects are restored to the same target client 2. Paths that were used for backup 3. 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.
Indirect and Direct Library Access Upon configuring Data Protector with a SCSI Library device, there are two ways in which client systems can access library robotics: Indirect Library Access and Direct Library Access. Indirect Library Access This configuration can be used in SAN as well as conventional SCSI direct connect environments. Several systems can access the library robotics by forwarding their requests to a client system that has direct access to the library robotics.
Figure 54 Indirect Library Access Note that you cannot use a shared library if the client system that controls the robotics, castor, in our example, fails. Direct Library Access When the SAN concept is used, Data Protector can be configured with a SCSI Library so that each client system has its own access to library robotics and drives.
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). To perform a local backup of such an application, you need to configure devices with virtual hostnames instead of real node names.
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.
Media management and devices
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” on page 183 “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.
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. Note that adding a new user is not a prerequisite for backing up the system this user is using.
Using predefined user groups The following default groups are provided by Data Protector: Table 12 Data Protector predefined user groups User group Access rights Admin Allowed to configure Data Protector and perform backup, restore, and all other available operations. Operator Allowed to start backups and respond to mount requests. End-user Allowed to perform restore of their own objects. In addition, users can monitor and respond to mount requests for their own restore sessions.
Users and user groups
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. This information is needed to effectively administer the database configuration and maintenance.
• 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. • Backup management The information stored in the IDB enables you to verify how backups were done. You can also configure various reports using the Data Protector reporting functionality.
The IDB on the UNIX Cell Manager IDB location 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.
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. The transaction logs are stored in the db40\logfiles\syslog directory.
MMDB size and growth The MMDB does not grow very big in size. The largest portion of the MMDB is typically occupied by information about the Data Protector media. Space consumption is in the range of 30 MB. Ffor more details , see “IDB size estimation ” on page 203.
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. For more details, see “IDB size estimation ” on page 203.
DCBF location By default, the DCBF is located in the following directory: • On Windows Server 2008: Data_Protector_program_data\db40\dcbf • On other Windows systems: Data_Protector_home\db40\dcbf • On UNIX systems: /var/opt/omni/server/db40/dcbf Consider the disk space on the Cell Manager and relocate the DC directory, if necessary. You can create more DC directories and locate them to different disks.
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 “IDB size estimation ” on page 203. For NDMP backups, the SMBF grows proportionally to the number of objects backed up. Approximately 3 KB are used for each backed up object.
If transaction logging is enabled, an IDB backup removes old transaction logs and 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. The first step is to select a specific object (filesystem or logical drive).
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). All other records stay in the CDB and MMDB and it is possible to run a restore from such media (however, browsing is not possible).
IDB maintenance 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“.
• 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. Shift-JIS encoded filenames, for example, take up to three bytes in the IDB, while pure ASCII filenames take up only one byte.
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.
Log Directories Logs all detailed information about backed up directories (names, versions, and attributes). This represents approximately 10% of all detailed information about backed up files and directories. No Log No information about backed up files and directories is logged to the IDB. The different settings influence the IDB growth, the backup speed, and the convenience of browsing for data to be restored.
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.
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.
Specifics for large cells 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: • Reduce the logging level to the smallest acceptable level. Setting the Log Files option can reduce the IDB size to a third, and setting the Log Directories option to almost a tenth.
The Data Protector internal database
6 Service management In this chapter Service Management, reporting, and monitoring help administrators manage their backup environments more effectively. 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.
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. Demonstrating SLA compliance requires constant monitoring and periodic reporting to show whether SLA expectations have been met.
Figure 58 Service management information flow Native Data Protector functionality The functionality described in the following sections comes with Data Protector “out of the box.” Key functions • Data Protector has been equipped to track the elapsed times of key operations and to register this data as well as volume data using the Application Response Measurement Version 2.0 API (ARM 2.0 API). Registration of this data can be performed with HP Performance Agent (PA).
• • • • • send alerts via SNMP, it is possible to integrate virtually any application that can receive SNMP traps. Data Protector backup session auditing stores information about all backup tasks that were performed over extended periods for the whole Data Protector cell, and provides this information on demand in an integral and printable fashion for auditing and administrative purposes.
central operations console, such as HP Operations Manager software, paging a system operator, or taking automated remedial action to resolve the problem. Table 13 ARM functionality Transaction description (ARM 1.0) Additional data logged to ARM (ARM 2.0) Usage Backup specification session duration Processed data [MB] Availability and recovery planning. Chargeback. Object backup session duration Processed data [MB] Availability and recovery planning. Chargeback.
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.
From the monitor’s user interface, you can abort a backup, restore, or media 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.
• Select from many delivery methods used to deliver reports (such as e-mail, SNMP, broadcast (available on Windows only), write to file, and send to external command) You can combine most of these different formats, delivery methods, schedules, and triggers.
Data Protector log files Some Service Management applications, such as HP Operations Manager software, allow you to specify when and which log files should be monitored for a specific log entry. If the specified entry is detected in the file, an action can be specified. In OM this is called Log file encapsulation.
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”.
• Sending major and critical Data Protector events to your network management solution, such as HP Network Node Manager (Data Protector built-in notification engine sending SNMP traps). Service management integrations The following Data Protector integrations can be installed to help facilitate service management and to give you single-point access to rich service management functionality.
• Administration Reports • 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.
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.
Figure 62 Direct SIP integration example 218 Service management
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.
CRS The CRS (Cell Request Server) process (service) runs on the Data Protector Cell Manager. It starts and controls backup and restore sessions. The service is started when Data Protector is installed on the Cell Manager system and is restarted each time the system is restarted. MMD The MMD (Media Management Daemon) process (service) runs on the Data Protector Cell Manager and controls media management and device operations. The process is started by the Cell Request Server process (service).
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. The Data Protector monitor starts immediately and you can view the progress of the backup session.
4. 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. 5. Disk Agents read data from disks and send it to the Media Agents that write data to media.
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.
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. Optimizing the load To optimize the load on the Cell Manager, Data Protector can, by default, start up to five backup sessions at the same time.
Sending notification to an operator 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 notification” on page 211. Automating a mount request You can configure automated actions for the handling of mount requests.
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 Figure 65 on page 227, is started, the following happens: 1. The Restore Session Manager (RSM) process is started on the Cell Manager system.
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. Queuing of restore sessions Timeout When a restore session is started, Data Protector tries to allocate all needed resources, such as backup devices. The session is queued for as long as the required minimum resources are not yet available.
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. Responding to a mount request Responding to a mount request includes providing the required media or any copy of media and telling Data Protector to proceed with the 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. In this case, data is copied to multiple disks at the same time.
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 after a backup.
4. The CSM starts the Media Agents on the systems with devices configured for copying. The Media Agents load the source and target media allocated according to the backup policies. 5. Media Agents read the data from the source media and connect to the Media Agents loaded with the target media.
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.
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.
2. 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. 3. 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. If the resources are still unavailable after the timeout, the session is aborted. 4.
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. 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.
2. The MSM starts the Media Agents (MAs) on the system that has devices used for the media management session. 3. 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. 4. When the session is complete, the MSM closes the session.
8 Integration with database applications In this chapter This chapter gives a brief description of the integration of Data Protector with database applications, such as Microsoft Exchange Server, Oracle Server, IBM DB2 UDB, and Informix Server.
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. Should a failure prevent modified data from being permanently written to data files, the changes can be obtained from log files.
1. A transaction is first recorded into the transaction log. 2. Changes required in the transaction are then applied to cached pages. 3. From time to time sets of modified pages are flushed to data files on disk. Filesystem backup of databases and applications Databases are constantly changing while they are online. Database servers consist of multiple components that minimize response time for connected users and increase performance.
The essence of the backup interface is that it provides the backup application with 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. Data Protector provides a Database Library that is linked in to the database server. The database server sends data to Data Protector and requests data from it.
• There is no need to specify the location of data files. These can be located on 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. Besides full backups, users can select (block level) incremental backups or only the backup of transaction logs.
Integration with database applications
9 Direct backup In this chapter This chapter introduces the direct backup concept and the technologies that enable it. The chapter also discusses the direct backup configurations that are supported by Data Protector. It is organized as follows: “Overview” on page 243 “Requirements and support” on page 249 “Supported configurations” on page 250 Overview The storage industry’s demand for backup solutions that minimize application downtime and system loads while maximizing backup speeds is growing.
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.
Backup types 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.
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. It also discusses the required agents and where they are installed.
• The HP StorageWorks Disk Array XP (XP) is configured as Business Copy (BC) 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.
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. Resolve removes the need for multiple servers to support multiple file systems and the difficulties presented by file system-specific information formats.
Database. The Backup Media Agent (BMA) writes catalog segments and delimiters between data and catalog segments known as file-marks. 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.
Supported configurations Three hosts: CM, application, Resolve This solution uses three hosts: one each for the Cell Manager, Resolve Agent, and application. Although this configuration requires three machines, the Resolve host can be a less expensive host and the resource load is split, helping you avoid performance impact on the application. Note that in this configuration, the Cell Manager host can be running any of the operating systems supported by Data Protector.
Figure 71 Basic three host configuration Two Hosts: Cell Manager/Resolve Agent and application This solution uses two hosts: one for the Cell Manager and Resolve Agent and one for the application. Although this configuration does require two machines, the resource load is split; this can help you avoid performance impact on the application. Also, the machine that hosts the Cell Manager and the Resolve Agent can be of minimal processing capacity.
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 11.11.
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” on page 253 “Disk backup benefits” on page 254 “Data Protector disk-based devices” on page 255 Overview Industry has requirements for increasingly faster methods of backing up and restoring data.
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. The following list indicates some situations in which disk-based devices are particularly useful: • Many applications and databases continuously generate or change a large number of files, which contain business-critical data.
• Overall, disk-based storage space is becoming increasingly cheaper even if 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. Once configured, its properties cannot be changed.
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. The file library device automatically creates more file depots if a particular backup requires more space than is available in a single file depot.
11 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 devices” on page 255 “Restore and synthetic backup” on page 260 Overview With the volume of data increasing and backup windows shrinking, performing a full backup often presents a problem in terms of time and storage space.
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. Synthetic backup benefits Synthetic backup brings the following benefits: • It eliminates the need for full backups.
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. The Restore Media Agent (RMA) reads the full backup from the backup medium, which can be a tape or a disk.
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. The generated data is sent to the Backup Media Agent (BMA), which creates the virtual full backup in the file library.
Figure 74 Full and incremental backups In 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. If tape devices are used, time is spent for loading and unloading of several media and seeking for object versions to restore.
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. Figure 77 Synthetic backup and object copy In Figure 77 on page 262, a synthetic backup was performed and then copied.
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.
Synthetic backup
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. The configuration consists of one of numerous variations of single or multiple mirror structures.
Figure 78 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.
• Databases can be put into backup mode • Databases can be taken offline • A mount point can be unmounted Only when this is carried out before a replica is consistent. However, if a database is running on a filesystem or a rawdisk, there is no need to unmount the filesystem or rawdisk as the database ensures that data is really written to the disk and not to the filesystem cache. For an online database backup, a raplica alone cannot be restored.
allows up to three replicas, and each can have an additional two copies if cascading is used. During the instant recovery, the data on the specified replica (left unchanged for the purpose of instant recovery) is synchronized to the application client source volumes without restoring from a backup medium. Data Protector will only use the first three replicas because secondary mirrors cannot perform fast-resynchronization, which is critical for ensuring minimal restore time.
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.
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. A small number of archive logs reduces the space needed for the archive logs in total, as well as speeds up the recovery process of the database.
Figure 80 Split mirror - remote mirror (LAN-free remote backup - data HA) 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. No network resources are required to sync the mirrors during a backup.
remote disaster recovery site using hardware mirror concepts is widely accepted in the industry. Local/remote mirror combination If the customer has a need for a permanently available recovery site (provided, for example, by a MetroCluster) in addition to a zero downtime backup solution, the combination of a remote mirror and a local mirror can be used. This solution allows for full split mirror advantage together with a full recovery solution at the remote site.
Other configurations There are many other possible split mirror configurations that provide some particular advantage or fulfill a specific user need. However, each configuration has its specific behavioral pattern that imposes specific requirements on the control functions in order to guarantee backup and recovery. It is important to control and specify which configurations are supported. All the configurations shown above are supported by HP.
Split mirror 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.
allocation of logical volumes on physical disks, but you can influence it with a choice of protection characteristics. RAID Redundant Array of Inexpensive Disks (RAID) technology is used to control the way in which the data is distributed across the physical disks within a disk array. Various levels of RAID are available, providing different levels of data redundancy and data security, speed and access time.
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; a snapshot of the application data is produced. Once the backup client is ready and the replica for the snapshot data is created, the application is returned to normal operation.
• Databases can be put into backup mode • Databases can be taken offline • A mount point can be unmounted For an online database backup, snapshot data alone does not suffice for a restore. The archive log files from the application client are also needed. An archive log files backup utilizing the standard Data Protector backup procedure can be started immediately after creating snapshots, when the database is taken out of backup mode.
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. Only the point-in-time copies produced during ZDB-to-disk and ZDB-to-disk+tape sessions can be restored using the instant recovery functionality.
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; if the data on source volumes is lost, the associated snapshots are useless.
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.
1. Put the database into a consistent mode that permits a snapshot to be taken. 2. Perform a snapshot of the application data. 3. 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.
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.
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.
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. This allows the emulation of the Continuous Access plus Business Copy functionality that is available with HP StorageWorks Disk Array XP.
Figure 88 Campus Cluster with LVM Mirroring - HP StorageWorks Virtual Array only With this configuration, it is possible to emulate Continuous Access plus Business Copy functionality, with standard cluster failover functionality. This is often required for mission critical applications. Backup clients and clusters The backup client should not be used as a failover server for the application client. It is recommended to have application and backup services on separate clusters.
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.
Snapshot concepts
14 Microsoft Volume Shadow Copy service In this chapter This chapter introduces the Microsoft Volume Shadow Copy service (VSS) concept and its role in the backup and restore process. It also outlines the backup and restore flow when using this feature. The chapter is organized as follows: “Overview” on page 289 “Data Protector Volume Shadow Copy integration” on page 293 “VSS filesystem backup and restore” on page 295 For detailed information on the integration, see the HP Data Protector integration guide.
VSS 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.
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.
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.
VSS benefits 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.
writers, and backup and restore functionality. 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.
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. However, you can still benefit from the VSS functionality. The cooperation between the backup application and a shadow copy provider can be still used to assure a higher level of data consistency.
• 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. The level of data integrity is slightly improved in comparison to a traditional backup of active volume. For detailed information on Windows filesystem backup and restore, see the online Help.
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.
Define the periods of time during which backups of specific systems can be 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.
Determine the administration and operations rights for the backup systems users. Company XYZ XYZ is a translation agency providing the following services: • • • • • Translation, localization, language editing, and proof-reading Certification of translated documents Simultaneous and consecutive interpretation Desktop publishing and graphic design Rental of conference interpreting equipment XYZ is currently growing at 20-25 percent per year.
Depart. #Servers #Clients Current data Projected data (in 5 Years) Current devices Other Languages 1 AIX 11 UX 22 GB 67 GB 2 HP StorageWorks DAT24 autoloaders Admin 1 HP-UX 5 UX 10 GB 31 GB 1 HP StorageWorks DAT24 autoloader 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.
network shares. Employees in the Other Languages Department also work on 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. Each of the backup servers is managed individually. There is no capability for a central backup management.
Backup strategy requirements Requirements After addressing the items under “Considerations” on page 297, the following requirements have been identified for the backup solution of company XYZ: • Backup Policy • Full, weekly backups will occur and be completed within 12 hours. • Daily incremental backups will occur at the end of each workday and will be completed within 8 hours. • A permanent data protection period will be included. • Backup media will be stored at a remote site.
Proposed solution Because of the limitations of the current backup solution for both performance and enterprise-wide management, there is a need to redesign XYZ’s backup architecture and strategy to meet its business objectives. An overview of the proposed solution is given, followed by a detailed account of the solution. Note that this is a proposal and not the only possible solution to XYZ’s storage management problems.
Department Current Data Projected Data (In 5 Years) Devices * 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 4115 library. The remaining 4 HP StorageWorks DAT24 autoloaders are used in a separate R&D system, which is not of our configuration.
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. The tool is located in the same directory as the rest of the Data Protector online manuals.
Figure 93 Input parameters The results are shown in Figure 94 on page 306. In one year, the database is expected 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.
The backup devices consist of an HP StorageWorks DLT 4115w Library as well as two HP StorageWorks DAT24 autoloaders. Why use the HP StorageWorks DLT 4115w Library? The HP StorageWorks DLT 4115w Library has a single DLT4000 drive with 15 slots. It has a total compressed storage capacity of 600 GB and a maximum sustained data transfer rate of 3 MB/s, or 10.5 GB/h, with data compression. This is the transfer rate assumed for the remainder of this section.
The Data Protector Catalog Database is approximately 0.4 GB in size. It is backed up locally to an HP StorageWorks DAT24 autoloader, which has a sustained data transfer rate of 2 MB/s or 7 GB/h. Data Protector by default checks the integrity of the database before the database is backed up. It takes less than half an hour to check the integrity of a 0.4 GB database and only a few minutes to back up the database.
Table 18 on page 309 shows the size and time requirements for these full backups as of today, as well as the five year projection.
Why use level 1 incremental backups? To restore the latest data, only two media sets need to be accessed, one for the latest full backup and one for the latest level 1 incremental backup prior to the restore point-in-time. This simplifies and speeds up restore considerably. • ENG2_BS Backup specification for data in the English Department to be backed up remotely to the HP StorageWorks DLT 4115w Library.
Data protection determines the amount of time until each medium can be reused. 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 4115w 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. Other objects use default media pools.
autoloaders. All actions excluding the actual moving of media to the vault are 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. This is done once a month. Data Protector provides a report on what media need to be moved to a security company. Track the location of media that are moved to a vault.
1. Identifies the media needed for restore. 2. Brings the media from a vault, enters the media in the HP StorageWorks DLT 4115w Library or other device and then scans the media. 3. Selects the specific object to be restored using the List From Media option, if the media are not in the IDB. 4. Performs the restore. Company ABC ABC is a high growth software engineering company with headquarters in Cape Town, South Africa.
Three departments at ABC Cape Town use the Microsoft SQL database to store their data and the company uses Microsoft Exchange Server for mailing services. These databases, currently containing 11 GB and 15 GB of data, respectively, are backed up to 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.
Backup media are denoted by the name of the department, the name of the server 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: • • • • • • • • There is no online backup solution of the SAP database server. The backup solution is not centralized. Backup operations are not fully automated.
Type of data Maximum downtime Company resource data 6 hours Project data 1 day Personal data 2 days 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. This has implications on the amount of backup media required.
Location Data (in GB) ABC Pretoria 22 ABC Durban 16 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.
Configure cell A as the MoM cell for the ABC Cape Town environment, cell D as the MoM cell for the ABC Pretoria environment, and cell F as the MoM cell for the ABC Durban environment. This configuration is depicted in Figure 96 on page 318. Figure 96 ABC enterprise environment The Cell Managers and Manager-of-Managers in all the 7 cells should be Windows systems. Use a Centralized Media Management Database (CMMDB) in one of the cells in each MoM environment and Catalog Databases in each of the 7 cells.
The two cells at the ABC Durban MoM environment should also share a Centralized Media Management Database. This should be configured on the MoM of cell F to enable the sharing of the HP StorageWorks DLT 4115w Library between the cells. The following is a detailed account of the proposed solution: Proposed solution in detail • Cell Configuration Configure the departments into 7 cells, of which three are at ABC Cape Town, and two each at ABC Pretoria and ABC Durban.
MoM environment ABC Pretoria ABC Durban Cell #Windows servers #Windows clients #UNIX servers #UNIX clients #SAP B 2 11 5 21 1 C 2 20 4 12 1 D* 4 33 E 1 6 5 32 F* 2 10 4 30 p 1 11 2 29 #SAP is the number of SAP database servers * represents a MoM cell The Cell Managers and Manager-of-Managers in all the 7 cells should be Windows systems.
Figure 97 ABC Cape Town enterprise backup environment The two cells at the ABC Pretoria MoM environment should share a Centralized 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 4115w Library between the cells. Each of the cells in the environment should have its own Catalog Database. The two cells at the ABC Durban MoM environment should, likewise, share a Centralized Media Management Database.
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).
All systems in the same location should be on the same LAN for maximum performance. Use the 100TX network to connect all the systems in each of the locations and the WAN to connect the cells in the three locations. The 100TX network has a sustained data transfer rate of 10 MB/s, or 36 GB/h, of data.
Why use the HP StorageWorks DLT 4115w Library? • The HP StorageWorks DLT 4115w Library has a single DLT4000 drive with 15 slots. It has a total compressed storage capacity of 600 GB and a maximum sustained data transfer rate of 3 MB/s, or 10.5 GB/h, with data compression. This is the transfer rate assumed for the remainder of this section.
library has two drives and a sustained data transfer rate of 6 MB/s (2 x 3 MB/s), or 21 GB/h. Therefore, data is backed up to this library in up to 5 hours. The projected amount of data in five years, 185 GB, would be backed up in 9 to 10 hours, which would still be within the acceptable 12 hours. Cells D and E at ABC Pretoria share an HP StorageWorks DLT 4115w Library. This library has a single drive and a sustained data transfer rate of 3 MB/s, or 10.5 GB/h.
Media pool name Location Description P_DB_Pool Pretoria IDB D_DLT_Pool Durban HP StorageWorks DLT 4115w Library D_DAT_Pool Durban HP StorageWorks DAT24 autoloaders D_DB_Pool Durban IDB • Backup Specifications Configure backup specifications as follows: • DB_A...G Backup specifications for each of the 7 IDBs and configuration files. Schedule the backup specification such that Data Protector will run a weekly full backup and a level one incremental every day, except Sundays at 03.00.
Cell C Incr1 Incr1 Incr1 Incr1 Incr1 Full • 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 Table 27 on page 327 and level 1 incremental backups every work day. • USERS_D...G Backup specifications for user data.
Name Cell Description Backup day Time SERVERS_C C Servers Sunday 23:00 DB_D D IDB Saturday 03:00 DB_E E IDB Saturday 03:00 SERVERS_D D Servers Friday 23:00 SERVERS_E E Servers Saturday 23:00 USERS_D D User data Saturday 0:00 USERS_E E User data Sunday 0:00 DB_F F IDB Saturday 03:00 DB_G G IDB Saturday 03:00 SERVERS_F F IDB Friday 23:00 SERVERS_G G Servers Saturday 23:00 USERS_F F User data Saturday 0:00 USERS_G G User data Sunday 0:00 Bac
Set data protection to 5 years for all backup specifications except for Exchange_A, which is sued to back up personal mail. Set data protection for this backup specification to 3 months. • Concurrency Set to 5 to allow up to five Disk Agents to concurrently write data to the library. This will increase backup performance. • Media Pool Select appropriate media pools and media to be used for backup.
• Display a list of media needed for restore and the physical locations where the media are stored. • Filter media from the media view based on specific criteria, such as media with expired protection. • Restore • Restore by Query Requests for restores by query will be sent to the administrator.
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.
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.
Example 1: automated media copying of filesystem backups Your company has a MoM environment with two cells, each containing 150 computer systems (servers and workstations). On average, each system has 10 GB of data, which means that you have 3000 GB of data that you want to back up. You want to have daily Incr1 backups of the data, weekly full backups, and monthly full backups for archiving purposes.
have 900 GB of data to back up. The data is divided among backup specifications in the following way: • • • • BackupSpec1 BackupSpec2 BackupSpec3 BackupSpec4 (Drive (Drive (Drive (Drive 1) - 300 GB 2) - 300 GB 3) - 150 GB 4) - 150 GB BackupSpec1 and BackupSpec2 require 2 media each and the backup takes approximately 4 hours. BackupSpec3 and BackupSpec4 require 1 medium each and the backup takes approximately 2 hours.
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.
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. The scheduled media copying starts an hour after the backup is estimated to finish. For a graphic representation of the full backup and automated media copying, see Figure 102 on page 337.
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.
Figure 103 Overview of backup and automated media copy sessions Example 2: automated media copying of Oracle database backups Your company has an Oracle database of the size of 500 GB. You want to perform a full backup of the database daily. The backup must be performed outside the company's working hours, which means that it can start after 5 PM and must finish before 8 AM on the next day; it can also run during weekends.
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. Configuring automated media copying You use post-backup media copying because you have enough devices available.
Figure 105 Overview of backup and automated media copy sessions Internationalization Internationalization is a way to design and implement a software product so that the product interacts with the user's native language and according to the user's locale settings (currency, time, date, number, and other formats). It enables the user to enter their local language text data and correctly display it.
File name handling Handling file names in a heterogeneous environment (different operating systems with different local settings, all in one cell) is a significant challenge. Data Protector handles file names under various local settings (such as language, territory, and character sets) that were in effect on the system when the file names have been created.
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: • each user views their own file names correctly • each user views the file names of the other users as corrupted.
• the files to be restored are selected in the GUI • 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 343
Further information
Glossary access rights See user rights. ACSLS (StorageTek specific term) The Automated Cartridge System Library Server (ACSLS) software that manages the Automated Cartridge System (ACS). Active Directory (Windows specific term) The directory service in a Windows network. It contains information about resources on the network and makes them accessible to users and applications.
an archived redo log is determined by the mode the database 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. • NOARCHIVELOG - The filled online redo log files are not archived. See also online redo log.
associated with managing data and disk and provides striping 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 Virtual Library System (VLS) and virtual tape.
located (drive on Windows and mount point on UNIX). For 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 — displays the integration type (for example, SAP or Lotus). • Type: Backup object type. For filesystem objects — filesystem type (for example, WinFS). For integration objects — “Bar”.
See also application system, target volume, and replica. backup types See incremental backup, differential backup, transaction backup, full backup, and delta backup. backup to 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.
See also replica, source volume, snapshot, and CA+BC EVA. 350 BC Process (EMC Symmetrix specific term) A protected storage environment solution that has defined specially configured EMC Symmetrix devices as mirrors or Business Continuance Volumes to protect data on EMC Symmetrix standard devices. See also BCV.
See also BRBACKUP, and BRRESTORE. BRBACKUP (SAP R/3 specific term) An SAP R/3 backup tool that allows an online or offline backup of the control file, of individual data files, or of all tablespaces and, if necessary, of the online redo log files. See also BRARCHIVE, and BRRESTORE.
CAP (StorageTek specific term) Cartridge Access Port is a port built into the door panel of a library. The purpose is to enter or eject media. catalog protection Defines how long information about backed up data (such as file names and file versions) is kept in the IDB. See also data protection. CDB The Catalog Database is a part of the IDB that contains information about backups, object copies, restores, media management sessions,, and backed up data.
Database (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 Provider (Windows specific term) A module that can be queried to determine which objects on a filesystem have been created, modified, or deleted. channel (Oracle specific term) An Oracle Recovery Manager resource allocation.
client backup with disk discovery A backup of all filesystems mounted on a client. When the 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. client or client system Any system configured with any Data Protector functionality and configured in a cell.
between the MoM cell and the other Data Protector cells is highly recommended See also MoM. COM+ Registration Database (Windows specific term) The COM+ Registration Database and the Windows Registry store COM+ application attributes, class attributes, and computer-level attributes. This guarantees consistency among these attributes and provides common operation on top of these attributes.
the CRS runs under the account of the user specified at installation time. On UNIX systems, it runs under the account root. 356 CSM The Data Protector Copy and Consolidation Session Manager process controls the object copy and object consolidation sessions and runs on the Cell Manager system. data file (Oracle and SAP R/3 specific term) A physical file created by Oracle that contains data structures such as tables and indexes. A data file can only belong to one Oracle database.
they have common characteristics and share a common CA EVA log. See also copy set. 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. It can be a blobspace, dbspace, or logical log file. DC directory The Detail Catalog (DC) directory contains DC binary files, which store information about file versions.
a single device group. All devices in a device group must be 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. 358 device streaming A device is streaming if it can feed enough data to the medium to keep it moving forward continuously. Otherwise, the tape has to be stopped, the device waits for more data, reverses the tape a little and resumes to write to the tape, and so on.
directory junction (Windows specific term) Directory junctions use the reparse 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. The Disk Agent controls reading from and writing to a disk.
the backed up data, and increase the data availability and 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). 360 distributed file media format A media format, available with the file library, which supports a space efficient type of synthetic backup called virtual full backup. Using this format is a prerequisite for virtual full backup. See also virtual full backup.
can also read the data from the medium and send it to the computer system. drive-based encryption Data Protector drive-based encryption uses the 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. This number is used by the robotic control to access a drive. dynamic client See client backup with disk discovery.
and to Data Protector users who are granted the Reporting and notifications user rights. You can view or delete all events in the Event Log. 362 Event Logs (Windows specific term) Files in which Windows logs all events, such as the starting or stopping of services and the logging on and off of users. Data Protector can back up Windows Event Logs as part of the Windows configuration backup.
bi-directional transmission of large data files and can be deployed between sites kilometers apart. Fibre Channel connects nodes using three physical topologies: point-to-point, loop, and switched. Fibre Channel bridge A Fibre Channel bridge or multiplexer provides the ability to migrate existing parallel SCSI devices, like RAID arrays, solid state disks (SSD), and tape libraries to a Fibre Channel environment.
See also primary volume and MU number. 364 flash recovery area (Oracle specific term) Flash recovery area is an Oracle 10g/11g 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). See also recovery files. fnames.dat The fnames.dat files of the IDB contain information on the names of the backed up files. Typically, these files occupy about 20% of the IDB, if filenames are stored.
the directory 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.
hosting system A working Data Protector client used for Disk Delivery Disaster Recovery with a Data Protector Disk Agent installed. HP Operations Manager HP Operations Manager provides powerful capabilities for operations management of a large number of systems and applications in a network. Data Protector provides an integration into this management product. This integration is implemented as a SMART Plug-In for HP Operations Manager management servers on Windows, HP-UX, Solaris, and Linux.
information or method invocation, and returns standardized responses. See also HP StorageWorks EVA SMI-S Agent and Command View (CV) EVA. HP StorageWorks Virtual Array LUN A logical partition of a physical disk within an HP StorageWorks Virtual Array. LUNs are entities that can be replicated in the HP StorageWorks Business Copy VA configuration, or can be used as standalone entities. See also BC VA and replica.
See also backup types. 368 incremental mailbox backup An incremental mailbox backup backs up all the changes made to the mailbox after the last backup of any type. incremental1 mailbox backup An incremental1 mailbox backup backs up all the changes made to the mailbox after the last full backup. incremental (re)-establish (EMC Symmetrix specific term) A BCV or SRDF control operation.
Information Store (Microsoft Exchange Server specific term) The Microsoft 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. See also Key Management Service and Site Replication Service.
ISQL (Sybase specific term) A Sybase utility used to perform system administration tasks on Sybase SQL Server. Java GUI Client 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. Java GUI Server The Java GUI Server is a component of the Java GUI that is installed on the Data Protector Cell Manager system.
library Also called autochanger, jukebox, autoloader, or exchanger. 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 operation or unattended operation A backup or restore operation that takes place outside of normal business hours without an operator.
An LCR copy is used for disaster recovery because you can 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. See also cluster continuous replication and Exchange Replication Service.
login ID (Microsoft SQL Server specific term) The name a user uses to 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.
mailbox store (Microsoft Exchange Server specific term) A part of the Information Store that maintains information in user mailboxes. A mailbox store consists of a binary rich-text .edb file and a streaming native internet content .stm file. Main Control Unit (MCU) (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.
During a restore session, a Media Agent locates data on the 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 policy Determines in which sequence media are used for backup. The Strict allocation policy directs Data Protector to prompt for a specific medium. The Loose policy directs Data Protector to prompt for any suitable medium.
merging This defines one mode to resolve file conflicts during restore. If the file to be restored already exists at the destination, the one with the more recent modification date is kept. Files not present on the disk are always restored. See also overwrite. Microsoft Exchange Server A “client-server” messaging and a workgroup system that offers a transparent connection to many different communication systems.
MMD The Media Management Daemon process (service) runs on the Data Protector Cell Manager and controls media management and device operations. The process is started when Data Protector is installed on the Cell Manager. MMDB The Media Management Database (MMDB) is a part of the IDB that contains information about media, media pools, devices, libraries, library drives, and slots configured in the cell, as well as the Data Protector media used for backup.
OBDR capable device A device that can emulate a CD-ROM drive loaded with a bootable disk and can thus be used as a backup or boot device for disaster recovery purposes. object See backup object. object consolidation The process of merging 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. The process is a part of the synthetic backup procedure.
period (several minutes or hours). For instance, for backup 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. See also zero downtime backup (ZDB) and online backup.
• For ZDB methods, backup mode is required for the short 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. See also zero downtime backup (ZDB), and offline backup.
overwrite An option that defines one mode to resolve file conflicts during restore. All files are restored from a backup even if they are older than existing files. See also merging. ownership Backup ownership affects the ability of users to see and restore data. Each backup session and all the data backed up within it is assigned an owner.
• COPY - The mirrored pair is currently re-synchronizing. Data 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. • SUSPENDED - The link between the mirrored disks is suspended. That means that both disks are accessed and updated independently.
pre-exec A backup option that executes a command or script before the backup of an object or before the entire session is started. Pre-exec commands are not supplied by Data Protector. You need to create your own. They can be written as executables or batch files on Windows and as shell scripts on UNIX. See also post-exec. primary volume (P-VOL) (HP StorageWorks Disk Array XP specific term) Standard HP StorageWorks Disk Array XP LDEVs that act as a primary volume for the CA and BC configurations.
instance translates the commands into a sequence of low level SCSI commands. 384 rawdisk backup See disk image backup. RCU See Remote Control Unit (RCU). RDBMS Relational Database Management System. RDF1/RDF2 (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.
Recovery Manager (RMAN) (Oracle specific term) An Oracle command-line interface that directs an Oracle Server process to back up, restore, or recover the database it is connected to. RMAN uses either the recovery catalog or the control file to store information about backups. This information can be used later in restore sessions. recycle A process that removes the data protection from all backed up data on a medium, allowing Data Protector to overwrite it during one of the next backups.
is replicated. However, if a volume manager is used on UNIX, the whole volume or disk group containing a backup object (logical volume) is replicated. If partitions are used on Windows, the whole physical volume containing the selected partition is replicated. See also snapshot, snapshot creation, split mirror, and split mirror creation. 386 replica set (ZDB specific term) A group of replicas, all created using the same backup specification. See also replica and replica set rotation.
RSM (Windows specific term) Removable Storage Manager (RSM) includes a media management service that facilitates communication among applications, robotic changers, and media libraries. It enables multiple applications to share local robotic media libraries and tape or disk drives and to manage removable media. scan A function that identifies the media in a device. This synchronizes the MMDB with the media that are actually present at the selected locations (for example, slots in a library).
shadow copy (Microsoft VSS specific term) A volume that represents a 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. The original volume continues to change as the backup process continues, but the shadow copy of the volume remains constant. See also Microsoft Volume Shadow Copy Service and replica.
number. To read a medium, a robotic mechanism moves the medium from a slot into the drive. SMB See split mirror backup. smart copy (VLS specific term) A copy of the backed up data created from the virtual tape to the physical tape library. The smart copy process allows Data Protector to distinguish between the source and the target medium thus enabling media management. See also Virtual Library System (VLS).
use. However background copying processes normally continue after creation. See also snapshot. 390 source (R1) device (EMC Symmetrix specific term) An EMC Symmetrix device that participates in SRDF operations with a target (R2) device. All writes to this device are mirrored to a target (R2) device in a remote EMC Symmetrix unit. An R1 device must be assigned to an RDF1 group type. See also target (R2) device. source volume (ZDB specific term) A storage volume containing data to be replicated.
split mirror restore (EMC Symmetrix and HP StorageWorks Disk Array XP specific term) A process in which data backed up in a ZDB-to-tape or a ZDB-to-disk+tape session is restored from tape media to a split mirror replica, which is then synchronized to the source volumes. Individual backup objects or complete sessions can be restored using this method. See also ZDB to tape, ZDB to disk+tape, and replica.
for a single-drive device and multiple SCSI entries are required for a multi-drive library device. 392 stackers 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. standalone file device A file device is a file in a specified directory to which you back up data.
synthetic backup A backup solution that produces a synthetic full backup, an 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 backup The result of an object consolidation operation, where a restore chain of a backup objects is merged into a new, synthetic full version of this object.
tablespace A part of a database structure. Each database is logically divided into one or more tablespaces. Each tablespace has data files or raw volumes exclusively associated with it. tapeless backup (ZDB specific term) See ZDB to disk. target database (Oracle specific term) In RMAN, the target database is the database that you are backing up or restoring. target (R2) device (EMC Symmetrix specific term) An EMC Symmetrix device that participates in SRDF operations with a source (R1) device.
TNSNAMES.ORA (Oracle and SAP R/3 specific term) A network configuration 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.
UIProxy The Java GUI Server (UIProxy service) runs on the Data 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. The service is started as soon as Data Protector is installed on the Cell Manager. unattended operation See lights-out operation.
user rights. Users have the access rights of the user group to which they belong. vaulting media The process of storing media to a safe and remote place. The media are brought back to the data center when they are needed for restore or are ready for reuse in subsequent backups. The vaulting procedure depends on your company's backup strategy and policies for data protection/reliability. verify A function that lets you check whether the Data Protector data on a specified medium is readable.
virtual tape (VLS specific term) An archival storage technology that backs up data to disk drives in the same way as if it were being stored on tape. Benefits of virtual tape systems include improved backup and recovery speed and lower operating costs. See also Virtual Library System (VLS) and Virtual Tape Library. Virtual Tape Library (VTL) (VLS specific term) An emulated tape library that provides the functionality of traditional tape-based storage. See also Virtual Library System (VLS).
See also resync mode, source volume, primary volume (P-VOL), replica, secondary volume (S-VOL), and replica set rotation. VxFS Veritas Journal Filesystem. VxVM (Veritas Volume Manager) A Veritas Volume Manager is a system for managing disk space on Solaris platforms. A VxVM system consists of an arbitrary group of one or more physical volumes organized into logical disk groups. Wake ONLAN Remote power-up support for systems running in power-save mode from some other system on the same LAN.
XBSA interface (Informix Server specific term) ON-Bar and Data Protector communicate with each other through the X/Open Backup Services Application Programmer's Interface (XBSA). XCopy engine (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.
ZDB to tape (ZDB specific term) A form of zero downtime backup where 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. On split mirror arrays, split mirror restore can also be used.
Glossary
Index A adding data to media during backups, 148 ADIC (EMASS/GRAU) AML, 162 admin user group, 185 alarms, 208 alternative disaster recovery methods, 131 operating system vendors, 131 third-party tools, 131 ANSI X3.
backup with disk discovery, 225 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 key factors, 198 database growth and performance key factors, 198 backup environments, 299, 313 backup generations, 144, 307, 331 backup options, 310, 328 backup overview, 3
benefits 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 C cache memory, 72, 238 Catalog Database location, 192 records, 191 Catalog Database growth factors catalog protection, 100 catalog protection, 310 as an IDB key tunable parameter, 201 backup generations, 332 Catalog Database, 191 do not log any details, 100 filename size an
client systems, 42 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 MC/Service Guard, 79 Microsoft Cluster Server, 79 nodes, 80 package, 81 primary node, 81 secondary node, 81 shared disks, 80 Veritas Cluster, 79 virtual cluster node backup, 84, 86, 8
creating cells mixed environment, 66 UNIX environment, 64 Windows domains, 65 Windows workgroups, 66 Windows environment, 65 CRS, 220 D daily maintenance IDB 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 features, 35 Data Protector GUI, 50 data encoding, 76 data files, 238 data protection, 99 Data Protector concepts cells, 40 Data Protector Inet, 219 Data Protector servic
database on the UNIX Cell Managers IDB format, 189 IDB location, 189 database on the Windows Cell Manager IDB format, 188 IDB 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 factors backup environment growth, 198 backup environment growth, 198 database growth and performance key tunabl
device lists, 155 device locking, 159 device sharing in clusters, 180 device sharing in SAN, 175 drives, 177 robotics, 177 device streaming (definition), 156 devices, 49, 68, 153 - 181 disk-based, 255 ADIC (EMASS/GRAU) AML, 162 autoloaders, 162 cleaning tape support, 164 concurrency, 156 configuring, 153 device chaining, 155 device lists, 155 device locking, 159 device streaming, 156 exchangers, 162 GRAU/EMASS, 162 HP StorageWorks DAT Autoloaders, 324 HP StorageWorks DAT24 Autoloaders, 307 HP StorageWorks
Direct Library Access, 179 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 Disk Agent concurrency, 157, 311 Disk Agents, 42 disk backup, 253 benefits, 254 disk based devices overview, 253 disk discovery (definition), 225 disk discovery vs.
exchangers, 162 See also libraries expired catalog protection, 201 exporting media, 102 IDB operation, 195 removed objects, 195 F factors affecting restore duration, 125 factors influencing backup strategies, 60 failover, 81, 82 FC-AL, 173 features of Data Protector, 35 fibre channel planning performance, 73 Fibre Channel (definition), 172 Fibre Channel Arbitrated Loop, 173 Fibre Channel topologies, 173 loop topology, 173 point-to-point, 173 switched topology, 174 file jukebox device, 255 file library devi
I IDB, 187 advantages, 187 architecture, 189 Catalog Database, 191 Detail Catalog Binary Files, 192 in the Manager-of-Managers environment, 189 management, 196 Media Management Database, 190 on the UNIX Cell Managers, 189 on the Windows Cell Manager, 188 operation, 194 Serverless Integrations Binary Files, 194 Session Messages Binary Files, 193 size and growth, 188 IDB architecture IDB parts scheme, 190 IDB growth and performance key factors, 197 IDB management IDB configuration, 196 IDB maintenance, 197 ID
incremental backups, 71 types, 93 Indirect Storage Are Networks, 178 Indirect Library Access Library Access, 178 Indirect Library Access, 179 influence of logging level and catalog protection on IDB growth scheme, 199 initializing media, 135 media ID, 145 Installation Servers, 42, 64 instant recovery snapshot backup, 279 split mirror backup, 267 integration with database applications, 38, 237 - 241 integrations, 210 Volume Shadow Copy service, 293 interactive backup sessions, 221 interactive object consolid
lock names, 159, 177 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 speed, 200 Log All, 199 Log Directories, 200 Log File, 199 No Log, 200 Loop Initialization Primitive (Protocol), 173 loop topology, 173 M magazine devices cleaning, 161 managemen
media pools, 135, 309, 325 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 handling, 144, 162 media location, 145 media location priority, 126 media management, 48, 133 - 153 adding data to media, 148 copying media, 122 labeling media, 145 media condition, 148 me
monitoring, 38, 210, 211 mount prompt handling, 111 mount requests, 224, 232, 235 automating, 224 notification, 224 responding, 224, 228 mount requests (restore sessions), 228 MSM, 235 multiple cells, 45, 62 multiple devices, 155 multiple slots, 163 N NDMP Media Agent, 165 network environment, 39 node cluster, 80 primary, 81 secondary, 81 notification, 38 number of concurrent sessions media management, 236 object consolidation, 234 object copy, 231 number of buffers, 159 number of cells, 62 considerations,
planning cells, 62 - 67 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 network backups, 67 parallelism, 69 software compression, 70 planning security, 73 - 76 data encoding, 76 Data Protector user accounts, 74 Data Protector user groups, 75 visibility of back
reporting, 38, 211 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 end users, 128 restore by query, 312, 330 restore chain, 96 restore duration, 125 factors affecting, 125 parallel restore, 125 restore options, 311 restore overview, 39 restore policies operators, 127 Restore Session Managers, 226 restore sessions, 44, 78, 225 - 229 definition, 225 mount requests, 228 queuing, 227 timeo
Service Management, 37, 205 - 215 Application Response Measurement, 207 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 location, 193 records, 193 size and growth, 193 sessions backup, 43, 220 media management, 235 object consolidation, 233 object copy, 229 restore,
snapshot backup, 275 application client, 277 archive log backup, 278 backup client, 277 backup client as failover server, 286 concepts, 276 configuration, Campus Cluster with LVM Mirroring, 286 configuration, multiple application hosts - single backup host, 283 configuration, multiple disk arrays dual host, 282 configuration, single disk array - dual host, 281 configuration, disk arrays - single host, 284 configuration, LVM mirroring, 285 configuration, other, 286 configurations, 281 high availability, 275
standalone devices, 161 standalone devices, 160 standalone file device, 255 standard restore vs parallel restore, 228 standard backup vs disk discovery, 225 static drives, 180 Storage Area Networks any-to-any connectivity, 171 LAN-free backups, 175 Storage Area Networks, 170 - 181 concepts, 171 device sharing, 175 device sharing in clusters, 180 Direct Library Access, 179 Fibre Channel, 172 Fibre Channel topologies, 173 Indirect Library Access, 178 LAN-free backups, 177 lock names, 177 sharing devices, 175
V Z vaulting, 134, 151 - 153, 311, 329 definition, 151 restoring, 153 restoring from a vault, 312, 330 vaulting usage example, 152 Veritas Cluster, 79 virtual cluster nodes, 84, 86, 89 virtual full backup, 258 virtual server, 81 visibility of backed up data, 76, 183 Volume Shadow Copy service (VSS) shadow copy set, 290 Volume Shadow Copy service (VSS) backup, 293 overview, 289 writer, 290 Volume Shadow Copy service (VSS) backup model, 291 benefits, 293 filesystem backup, 293 filesystem backup and restore,
