HP OpenView Storage Data Protector Administrator’s Guide Manual Edition: May 2003 Manufacturing Part Number: B6960-90078 Release A.05.10 © Copyright Hewlett-Packard Development Company, L.P.2003.
Legal Notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
©Copyright 1985-86, 1988 Massachusetts Institute of Technology ©Copyright 1989-93 The Open Software Foundation, Inc. ©Copyright 1986-1997 FTP Software, Inc. All rights reserved ©Copyright 1986 Digital Equipment Corporation ©Copyright 1990 Motorola, Inc.
HP-UX Release 11.00 and later (in both 32- and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation. OpenView® is a registered U.S. trademark of Hewlett-Packard Company. © 2003 Bristol Technology, Inc., Bristol Technology, Wind/U, HyperHelp and Xprinter are registered trademarks of Bristol Technology Inc. Other reserved names are trademarks of the respective companies.
Contents 1. Introducing Data Protector In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 The Data Protector Cell Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 How a Backup Session Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 How a Restore Session Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Activating Cartridge Memory Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling a Backup Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a Backup Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming a Backup Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Locking . . . . . . . . . .
Contents Selecting Media for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Data Protection for Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recycling Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Backing Up CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Windows Clients Using Disk Discovery . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Windows Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Windows Disks as Disk Image Objects . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up Novell NetWare Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Preventing Backup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Restarting Failed Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 6. Restore In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Your Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 7. Monitoring, Reporting, Notifications, and the Event Log In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Currently Running Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Finished Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Generating the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Protector Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 355 355 356 8.
Contents Reducing the IDB Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reducing the IDB Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purging Obsolete Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extending the Database Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Database Size . . . . . . . . .
Contents Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Automated Disaster Recovery of a Windows System . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitations . . . . . . . . . . . .
Contents General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Assisted Manual Disaster Recovery . . . . . . . . . . . . . . . Troubleshooting Disk Delivery Disaster Recovery . . . . . . . . . . . . . . . . . . Troubleshooting EADR and OBDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ........ ........ ........ ........ 514 515 515 516 In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Troubleshooting Data Protector Services and Daemons . . . . . . . . . . . . . . . . . . . . . . . 569 Problems Starting Data Protector Services on Windows . . . . . . . . . . . . . . . . . . . . . 569 Problems Starting Data Protector Daemons on UNIX . . . . . . . . . . . . . . . . . . . . . . . 571 Data Protector Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Troubleshooting Devices and Media . . . . . . . . . . . . . . . . . . . . . . . .
Contents Temporary Directory Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problems During Backup and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMDB and CDB Are Not Synchronized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Reporting and Notifications . . . . . . . . . . .
Contents 14. ADIC/GRAU DAS and STK ACS Libraries In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADIC/GRAU DAS and STK ACS Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Management Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Creating a libaci.o on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-26 Example of the Package Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-28 Example of the Package Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-38 Data Protector Log Files Example Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-44 debug.log . . . . . . . . . . . . . .
Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
xx
Conventions The following typographical conventions are used in this manual. Table 2 Convention Italic Meaning Example Book or manual titles, and manual page names Refer to the HP OpenView Storage Data Protector Integration Guide for more information. Provides emphasis You must follow these steps. Specifies a variable that you must supply when entering a command At the prompt type: rlogin your_name where you supply your login name. Bold New terms The Data Protector Cell Manager is the main ...
Data Protector provides a cross-platform (Windows and UNIX) graphical user interface.
Contact Information General Information General information about Data Protector can be found at http://www.hp.com/go/dataprotector Technical Support Technical support information can be found at the HP Electronic Support Centers at http://support.openview.hp.com/support.jsp Information about the latest Data Protector patches can be found at http://support.openview.hp.com/patches/patch_index.
xxiv
Data Protector Documentation Data Protector documentation comes in the form of manuals and online Help. Manuals Data Protector manuals are available in printed format and in PDF format. Install the PDF files during the Data Protector setup procedure by selecting the User Interface component on Windows or the OB2-DOCS component on UNIX. Once installed, the manuals reside in the \docs directory on Windows and in the /opt/omni/doc/C/ directory on UNIX.
• HP OpenView Storage Data Protector UNIX Integration Guide This manual describes integrations running on the UNIX operating system, such as Oracle, SAP R/3, Informix, Sybase, NetApp Filer, IBM DB2 UDB, HP OpenView Network Node Manager, and Lotus Domino R5 Server. HP OpenView Storage Data Protector Concepts Guide This manual describes Data Protector concepts and provides background information on how Data Protector works.
HP OpenView Storage Data Protector Integration Guide for HP OpenView This manual describes how to install, configure, and use the integration of Data Protector with HP OpenView Service Information Portal, HP OpenView Service Desk, and HP OpenView Reporter. It is intended for backup administrators. It discusses how to use the OpenView applications for Data Protector service management.
xxviii
In This Book The HP OpenView Storage Data Protector Administrator’s Guide describes how to configure and use the Data Protector network backup product. You must properly install Data Protector before you can configure it. NOTE This manual describes Data Protector functionality without specific information on particular licensing requirements. Some Data Protector functionality is subject to specific licenses.
Organization The manual is organized as follows: Chapter 1 “Introducing Data Protector” on page 1. Chapter 2 “Configuring and Using Backup Devices” on page 17. Chapter 3 “Configuring Users and User Groups” on page 81. Chapter 4 “Managing Media” on page 97. Chapter 5 “Backup” on page 151. Chapter 6 “Restore” on page 267. Chapter 7 “Monitoring, Reporting, Notifications, and the Event Log” on page 307. Chapter 8 “Manager-of-Managers Environment” on page 359.
1 Introducing Data Protector Chapter 1 1
Introducing Data Protector In This Chapter In This Chapter This chapter contains some general principles on how Data Protector works, covered in these sections: “The Data Protector Cell Environment” on page 3 “Using the Data Protector User Interface” on page 6 “Overview of Tasks to Set Up Data Protector” on page 15 2 Chapter 1
Introducing Data Protector The Data Protector Cell Environment The Data Protector Cell Environment The Data Protector cell is a network environment containing a Cell Manager, clients, and backup devices. The Cell Manager has the main Data Protector control software installed and is the central point from which the cell is administered and backup and restore operations are controlled. Systems that are to be backed up can be added to the cell and set up as Data Protector clients.
Introducing Data Protector The Data Protector Cell Environment NOTE For further information on these terms, or on the principles of Data Protector operation, see the HP OpenView Storage Data Protector Concepts Guide. How a Backup Session Works A backup session starts either when a backup is requested through the user interface, or when a scheduled backup is initiated. During this session, Data Protector backs up the requested filesystems and disks to the specified media. 1.
Introducing Data Protector The Data Protector Cell Environment 2. The Cell Manager determines the type of session that has been requested (restore), and starts the appropriate Session Manager. 3. The Session Manager then determines which filesystems or directories to restore, which devices to use, and what restore options have been specified. 4. The Session Manager starts the appropriate Disk Agent and Media Agent.
Introducing Data Protector Using the Data Protector User Interface Using the Data Protector User Interface There is one Data Protector user interface, available on Windows and UNIX platforms. It consists of the Data Protector graphical user interface (GUI) and the command-line interface. Using the Data Protector user interface, you can perform all Data Protector tasks.
Introducing Data Protector Using the Data Protector User Interface Graphical User Interface The Data Protector graphical user interface (GUI) uses features such as buttons and text boxes to enhance usability. Whenever possible, drop-down lists are provided to allow you to select from a list instead of typing in your selection. In addition, a comprehensive online Help system provides information about each window and each task.
Introducing Data Protector Using the Data Protector User Interface xomnicellmon to start the MoM cell monitoring GUI xomnimm to start the media and devices management GUI xomnimonitor to start the monitoring a single cell GUI xomnirestore to start the restore GUI xomniinstrec To start the instant recovery GUI. A special license is needed to start this GUI.
Introducing Data Protector Using the Data Protector User Interface Elements of the Data Protector Graphical User Interface For the visual representation of the GUI elements, refer to Figure 1-1 on page 6. Context List The Context List is a drop-down list, from which you can select the management contexts described below: Clients Controls all of the client systems in the current Data Protector cell. You can add, delete, and monitor any client within the cell.
Introducing Data Protector Using the Data Protector User Interface Internal Database Allows you to get information on the IDB storage capacity, database objects, and sessions. Monitor Allows you to monitor sessions that are in progress. Scoping Pane The Scoping Pane provides a tree of items that can be selected to open a view. Selecting an item in the Scoping Pane displays information in the Results Area.
Introducing Data Protector Using the Data Protector User Interface The Command-Line Interface The command-line interface (CLI) follows the standard UNIX format for commands and options and provides complete Data Protector functionality. You can use these commands in scripts to speed up your commonly performed tasks. The omniintro man page lists all supported Data Protector commands, as well as differences between commands on the UNIX and Windows platforms. See also “Data Protector Commands” on page A-7.
Introducing Data Protector Using the Data Protector User Interface Data Protector Online Resources Information about Data Protector is available in this manual and in the online Help system. This manual contains the information you need to plan and administer your Data Protector network, and information on some more commonly performed tasks. The online Help system contains the information you need to perform all available tasks.
Introducing Data Protector Using the Data Protector User Interface If the GUI concerned is running on Windows, the Help Navigator is dynamic: Once it is started, its contents automatically change as you go to the next page of the wizard or to another view in the Data Protector user interface.
Introducing Data Protector Using the Data Protector User Interface 3. In the Open text box, enter mmc to open the Microsoft Management Console window. 4. From the Console menu, select Add/Remove Snap-in. In the Standalone property page of the Add/Remove Snap-in window, click Add. 5. In the Add Standalone Snap-in window, select HP OpenView Storage Data Protector. Click Close to exit the window, then click OK to get back to the Microsoft Management Console window.
Introducing Data Protector Overview of Tasks to Set Up Data Protector Overview of Tasks to Set Up Data Protector Although configuring Data Protector is easy, some advanced planning will help you configure the environment and optimize your backups. This section provides an overview of the global tasks to set up a 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.
Introducing Data Protector Overview of Tasks to Set Up Data Protector • Which devices will be used, and how? • Which user groups do you want to have, and what will they do? • How many backup specifications do you want to have, and how should they be grouped? 6. Install the Data Protector Cell Manager and Installation Server(s). Then use the Data Protector GUI to distribute Data Protector agents to other systems. Also, connect the devices (tape drives) to the systems that will control them.
2 Configuring and Using Backup Devices Chapter 2 17
Configuring and Using Backup Devices In This Chapter In This Chapter This chapter includes information on the following topics: “Configuring Backup Devices” on page 20 “Configuring Standalone Devices” on page 23 “Configuring File Devices” on page 26 “Configuring Library Devices” on page 29 “Configuring Libraries with Multiple Systems” on page 32 “Configuring Magazine Devices” on page 34 “Configuring Stacker Devices” on page 35 “Configuring a Library for Mixed Media” on page 37 “Configuring Devices for Dire
Configuring and Using Backup Devices In This Chapter NOTE Backup devices (like tape drives) are subject to specific Data Protector licenses. See the HP OpenView Storage Data Protector Installation and Licensing Guide for details.
Configuring and Using Backup Devices Configuring Backup Devices Configuring Backup Devices Preparation of a backup device consists of connecting the device to the system and knowing which of the (working) associated device files (SCSI address) is to be used. To configure a device: 1. Connect the device to a computer. Refer to the documentation that comes with the device. 2. Make sure that you have done the following: UNIX Systems Create or find the device filename for a device connected to a UNIX system.
Configuring and Using Backup Devices Configuring Backup Devices Windows Robotics Drivers On Windows, disable the Removable Storage Service or Windows medium changer (robotics) driver before you configure the robotics device with Data Protector. For detailed steps, refer to the online Help index keyword “robotics drivers”. For further information, refer to Appendix B of the HP OpenView Storage Data Protector Installation and Licensing Guide.
Configuring and Using Backup Devices Configuring Backup Devices Figure 2-1 How Backup Specifications, Devices, and Media Pools Relate 22 Chapter 2
Configuring and Using Backup Devices Configuring Standalone Devices Configuring Standalone Devices What Are Standalone Devices? Standalone devices are simple backup devices with one drive that reads from or writes to one medium at a time. They are used for small-scale backups. When a medium is full, the operator has to manually replace it with a new medium so that the backup can proceed. Standalone devices are not appropriate for large, unattended backups.
Configuring and Using Backup Devices Configuring Standalone Devices Figure 2-2 Specifying Device Type and Name Configuring Device Chains Data Protector allows you to configure standalone devices of the same type into device chains. When a medium in one device becomes full, the backup automatically continues on the medium in the next device in the device chain. Device chains are possible for only one Media Agent, that is, you can connect a device chain to only one system.
Configuring and Using Backup Devices Configuring Standalone Devices Protector can immediately use media that are recognized and unprotected. Data Protector can also use blank media, so that you do not have to format them.
Configuring and Using Backup Devices Configuring File Devices Configuring File Devices What Are File Devices? A file device is a file in a specified directory to which you back up data instead of writing it to a tape. File devices are available for standalone devices and Jukebox devices simulation. The file device functionality is available on the Windows, HP-UX, Solaris, AIX, and Linux operating systems. The default capacity of a file device is 100 MB for data and 10 MB for the catalog.
Configuring and Using Backup Devices Configuring File Devices You specify the capacity of a file device when you first format the medium. When you reformat the medium, you can specify a new size; however, the originally specified size will be used. You can change the capacity of a file device only by deleting the file from the system. The path to a file device can be anywhere, whether it is an internal drive or an external portable hard drive.
Configuring and Using Backup Devices Configuring File Devices To create a jukebox file device, specify the Jukebox device type in the Add Device wizard. As device addresses, specify different pathnames that will simulate jukebox slots. For detailed steps, refer to the online Help index keyword “configuring file devices”.
Configuring and Using Backup Devices Configuring Library Devices Configuring Library Devices What Are Library Devices? SCSI-II library devices, also called autoloaders, are large backup devices. They contain a number of media cartridges in a device’s repository and can have multiple drives handling multiple media at the same time. Most library devices also allow you to configure automatic drive cleaning, which is performed by Data Protector when the drive gets dirty. Refer to “Drive Cleaning” on page 61.
Configuring and Using Backup Devices Configuring Library Devices NOTE It is not necessary to configure all drives for use with Data Protector. You can configure one media pool for all drives, or have an independent media pool for each drive. It is recommended that you use the default media pool when configuring a device.
Configuring and Using Backup Devices Configuring Library Devices policy, and the device file or SCSI address of the device, and also configures the drive and slots. For detailed steps, refer to the online Help index keyword “autoconfiguring backup devices”. To verify the device configuration, right-click the created drive, and choose Scan Medium. If the device is configured correctly, Data Protector will be able to load, read, and unload media in the slots.
Configuring and Using Backup Devices Configuring Libraries with Multiple Systems Configuring Libraries with Multiple Systems You can configure a library so that each drive receives data from a different system running a Data Protector Media Agent. The library robotics control is still performed by one system. This improves performance in high-end environments by allowing local backup, instead of having to move the data over the network.
Configuring and Using Backup Devices Configuring Libraries with Multiple Systems • Configure a backup. See Chapter 5, “Backup,” on page 151.
Configuring and Using Backup Devices Configuring Magazine Devices Configuring Magazine Devices What Are Magazine Devices? Magazine devices group a number of media into a single unit called a magazine. A magazine allows you to handle large amounts of data more easily than when using many individual media. Data Protector allows you to perform media management tasks on magazines as sets, or on a single medium. Prerequisite Create at least one media pool with the Magazine Support option set.
Configuring and Using Backup Devices Configuring Stacker Devices Configuring Stacker Devices What Are Stacker Devices? A stacker is a single device with one drive and sequentially accessed media. Using stacker devices requires more human media management than using a small library. Data Protector provides simple configuration and management of media used in stacker backup devices. How to Configure a Stacker Device? To create a stacker device, specify the Stacker device type in the Add Device wizard.
Configuring and Using Backup Devices Configuring Stacker Devices Backup and Restore with Stacker Devices Only the first medium has to be manually loaded. When a tape is full, it is ejected and the next tape is loaded automatically. When all the tapes are used in a stacker magazine, the magazine has to be unmounted manually and the next one has to be inserted. Again the first tape has to be loaded manually into the drive.
Configuring and Using Backup Devices Configuring a Library for Mixed Media Configuring a Library for Mixed Media A mixed media library contains media of several types, such as DLT and magneto-optical. It uses identical robotics to move all the media (regardless of media type) between slots and drives. In order to use this library functionality, configure several (sub)libraries: one library definition per media type.
Configuring and Using Backup Devices Configuring Devices for Direct Backup Configuring Devices for Direct Backup This section provides the configuration steps for backup devices used in a direct backup environment. Refer to the HP OpenView Storage Data Protector Concepts Guide for a more detailed information on direct backup concepts. Direct backup is a Data Protector backup solution in a SAN environment.
Configuring and Using Backup Devices Configuring Devices for Direct Backup Backup Device Auto-detection The XCopy engine must reside on the FC bridge to which the backup device or drive is connected (external FC bridge), or on the internal FC bridge. A backup device that is used with direct backup functionality is auto-detected whenever a direct backup session is started.
Configuring and Using Backup Devices Configuring Devices for Direct Backup Configuring Standalone Devices Refer to the online Help index keyword “configuring standalone devices for direct backup” for detailed information on how to configure a standalone device for a direct backup. Configuring SCSI-II Libraries Refer to the online Help index keyword “configuring SCSI-II libraries for direct backup” for detailed information on how to configure a SCSI-II library for a direct backup.
Configuring and Using Backup Devices Support of New Devices Support of New Devices To use a device that is not listed as supported in the HP OpenView Storage Data Protector Software Release Notes, download the latest software package for the scsitab file from the HP OpenView World Wide Web site at http://www.hp.com/go/dataprotector. IMPORTANT Modifying the scsitab file is not supported. After you have downloaded the scsitab software package, follow the installation procedure provided with it.
Configuring and Using Backup Devices Using Several Drive Types in a Library Using Several Drive Types in a Library Using several drive types of a similar technology like DLT 4000/7000/8000 (the same is true within the DDS family) in the same library can lead to problems when you use the media in any drive, but do not ensure a common format on all media. For example, at restore time, a DLT 4000 cannot read a tape that has been written with a DLT 8000 (highest density).
Configuring and Using Backup Devices Using Several Drive Types in a Library On Windows and UNIX systems, you can configure separate media pools for different groups of drives. This allows you to use different density settings for different drive types. For example, you could create a DLT 4000 pool and a DLT 8000 pool. The related setting in the device definition must be used at the time the media are formatted.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Shared Devices in the SAN Environment This section describes some of the basic concepts of Storage Area Networks (SANs). For further conceptual information, see the HP OpenView Storage Data Protector Concepts Guide.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Figure 2-5 Multiple System to Multiple Device Connectivity in SAN Chapter 2 45
Configuring and Using Backup Devices Shared Devices in the SAN Environment Using FC-AL SANs Using tape devices in Fibre Channel Arbitrated Loops (FC-ALs) may with LIP cause certain anomalies that could abort a backup session. This problem arises because the FC-AL performs a Loop Initialization Protocol (LIP) whenever a new FC link is connected or disconnected, or whenever a system connected to the FC-AL is rebooted. This re-initialization of the FC-AL causes running backups to be aborted.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Direct Library Access Concept With direct library access, every system sends control commands directly to the library robotics. Therefore, a system does not depend on any other system in order to function. With direct library access , when multiple systems send commands to the same library, the sequence of such communication has to be coordinated.
Configuring and Using Backup Devices Shared Devices in the SAN Environment This section describes how you can manually configure the library robotics so that they can be used in a SAN environment. • Manually configuring the devices This section describes the steps that need to be performed to configure the drives. It also explains when Lock Names and direct access should be used. • Manually configuring the libtab file This section describes the purpose and usage of the libtab file.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Figure 2-6 SAN Environment Configuration Because the library is attached to several systems that can access its drives directly, you need to configure as many drives on each host as you want to use from that host. In this case, all four physical drives are to be used from each host. From a Data Protector perspective, the goal is as follows.
Configuring and Using Backup Devices Shared Devices in the SAN Environment ✓ Use a lock name if the (physical) device will be used by another host as well (shared device). ✓ Optionally, select direct access if you want to use this functionality. If you use it, ensure that the libtab file is set up on that host.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Protector then configures the device by setting up a logical name, a Lock Name, the media type, and the device file or SCSI address of the device, as well as the drive and slots. During the autoconfiguration procedure, you can choose which libraries and devices you want to be configured on which hosts.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Prerequisite Before configuring Data Protector devices in a SAN environment, the Data Protector Media Agent must be installed on each host that needs to communicate with the shared library. See the HP OpenView Storage Data Protector Installation and Licensing Guide for more information on installing a Media Agent.
Configuring and Using Backup Devices Shared Devices in the SAN Environment The drive naming convention shows its benefits during backup specification creation. Whenever you configure a backup on any host, all you have to do now is to use the drive that is configured on that host, since the drive includes the host name in its name.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Figure 2-7 Setting Advanced Options When you are setting the locking name of a drive, use the same lock name for the same physical drive when using it in the device definition on another host.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Figure 2-8 Summary of Device Definitions Using Lock Names Enabling Direct Access The Direct Access mechanism always uses the default robotics control host first for media movements, but if this fails, Data Protector uses direct access, if enabled. To enable direct access, select the Use direct library access option (see Figure 2-9 on page 56) and configure the libtab file on every host on which you want to use direct access.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Figure 2-9 Selecting Direct Access Manually Configuring the libtab Files The purpose of the libtab files is to map the library robotic control access so that it also works on the “direct access requesting system”, since here the local control path is likely to be different from the one used on the default library robotic control system.
Configuring and Using Backup Devices Shared Devices in the SAN Environment • is the control path to the library robotic driver on this client host. • is the name of the device definition used on this client host. You need one line per device for which you request direct access. The libtab file is located on: • \libtab on Windows systems • /opt/omni/.libtab on HP-UX and Solaris systems • /usr/omni/.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Example libtab file on donat Example of the libtab file on host donat.company.com (Solaris): donat.company.com /dev/rsst6 SAN_LIB_1_sample donat.company.com /dev/rsst6 SAN_LIB_2_sample donat.company.com /dev/rsst6 SAN_LIB_3_sample donat.company.com /dev/rsst6 SAN_LIB_4_sample NOTE If the host is part of a cluster, must be the virtual host name, and must refer to the local node.
Configuring and Using Backup Devices Shared Devices in the SAN Environment In order to share a device among multiple systems, configure one logical device for each system on which you want to use the device locally. NOTE Before the ATS component can be configured, the MC/ServiceGuard configuration has to be completed and a cluster has to exist.
Configuring and Using Backup Devices Shared Devices in the SAN Environment Table 2-3 How to Configure a Floating Drive Lock Name Libl_Drive_1 Static Drives The drives can still be used in the standard way using the static hostname and the local device file. (You can use the local HP-UX or ATS device file.) The local drives should be configured on the node.
Configuring and Using Backup Devices Drive Cleaning Drive Cleaning There are several methods for cleaning dirty drives: • Library built-in cleaning mechanism Some tape libraries have a functionality for cleaning drives automatically when a drive requests head cleaning. When the library detects a dirty drive, it automatically loads a cleaning tape. However, Data Protector is not notified of this action. This interrupts any active session, causing it to fail.
Configuring and Using Backup Devices Drive Cleaning to store cleaning tape(s). • Detection and use of cleaning tapes depends on the system platform where the Media Agent is running. See the HP OpenView Storage Data Protector Software Release Notes for further information. • You should not use another kind of device management application if you configure automatic drive cleaning managed by Data Protector, as this may cause unexpected results.
Configuring and Using Backup Devices Drive Cleaning 1. Enable dirty drive detection. This needs to be done for all device types (standalone and libraries). This enables Data Protector to recognize the event issued by the drive. 2. Configure a slot for the cleaning tape in the library or magazine device. Enabling Dirty Drive Detection To enable dirty drive detection, select the Detect dirty drive advanced option in the Settings property page for the drive.
Configuring and Using Backup Devices Drive Cleaning Where is the name of the file you will use to simulate a dirty drive, and is the name of the drive you want to test. You can add multiple entries for various drives. Do not add any directories in front of the name of the file. Testing the Configuration In order to test your configuration, do the following: 1. In the Data Protector tmp directory, create an empty file that will be used to simulate a dirty drive.
Configuring and Using Backup Devices Busy Drive Handling Busy Drive Handling Data Protector expects drives to be empty, i.e., there should not be a medium in the drive unless a restore or backup is currently active. Several factors can cause a medium to still be in a drive, for instance, if the medium was used with a different application and not removed, or if the system writing the data to the tape (Media Agent) failed during the backup. The next backup using this drive has to deal with this situation.
Configuring and Using Backup Devices Activating Barcode Support Activating Barcode Support If a SCSI library device uses media with barcodes, Data Protector can use barcodes by providing the following support: • Recognition of cleaning tapes with a CLN prefix. • Reference to media by their barcodes. Data Protector adds the media barcode to the Data Protector media label. • Quickly scanning the media in the slots of the library repository using media barcodes.
Configuring and Using Backup Devices Activating Barcode Support Figure 2-10 Activating Barcode Reader Support Chapter 2 67
Configuring and Using Backup Devices Activating Cartridge Memory Support Activating Cartridge Memory Support Cartridge memory support can be activated for drives with the LTO-Ultrium media type. It provides the following: • Updating or changing media management information, such as medium label, medium location and pool name, and media usage information. The latter includes date of last access, date of last write, and number of writes.
Configuring and Using Backup Devices Activating Cartridge Memory Support Figure 2-11 Cartridge Memory Support Activation for a Drive Chapter 2 69
Configuring and Using Backup Devices Disabling a Backup Device Disabling a Backup Device Disabling a backup device is useful when the device is damaged or in maintenance mode. If you disable a backup device, all subsequent backups skip this device. The next available device defined in the list of devices for the backup specification is used, provided that load balancing has been selected. All devices using the same lock name as the disabled device are also disabled.
Configuring and Using Backup Devices Disabling a Backup Device Figure 2-12 Disable Device Chapter 2 71
Configuring and Using Backup Devices Removing a Backup Device Removing a Backup Device By removing a backup device from the Data Protector configuration, you stop using this device for backup or restore. Make sure that you remove the device from all backup specifications that use the device. Otherwise the backup or restore will fail. TIP Also, if you are not using a certain backup device with Data Protector anymore, you may want to delete the Data Protector Media Agent software from the system.
Configuring and Using Backup Devices Renaming a Backup Device Renaming a Backup Device When you rename a backup device, the device is no longer used under its old name for backup or restore. IMPORTANT Make sure that you remove the device's old name from all backup specifications that use the device. Otherwise, Data Protector tries to back up to or restore from a device that does not exist, and the session fails.
Configuring and Using Backup Devices Device Locking Device Locking Internal Locking The internal locking of backup devices prevents two Data Protector sessions from accessing the same physical device at the same time. For example, if one backup session is using a particular device, all other backup/restore sessions must wait for this device to become free before starting to use it. When a backup or restore session starts, the Data Protector locks the device, the drive, and the slot used for that session.
Configuring and Using Backup Devices Device Locking Data Protector recognizes in order to lock the device before starting backup and restore sessions. Both logical devices need to have the same lock name. Refer to “Shared Devices in the SAN Environment” on page 44 for example on how to use Lock Name. How to Lock a Device Lock a backup device by selecting the Use Lock Name advanced option from the Settings property page for the device, and then entering the lock name of your choice.
Configuring and Using Backup Devices Device Concurrency, Segment Size, and Block Size Device Concurrency, Segment Size, and Block Size Streaming To maximize a device’s performance, it has to be kept 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 writing to the tape, and so on.
Configuring and Using Backup Devices Device Concurrency, Segment Size, and Block Size Figure 2-13 Advanced Options Dialog Box: Concurrency Chapter 2 77
Configuring and Using Backup Devices Device Concurrency, Segment Size, and Block Size Figure 2-14 Device Properties Dialog Box: Concurrency Changing Segment Size Segment size is related to the size of data areas which Data Protector uses in writing data to the media. It is user-configurable for each device. Note that a smaller segment size consumes media space because each segment has a file mark which takes up space on a medium.
Configuring and Using Backup Devices Device Concurrency, Segment Size, and Block Size You can change the segment size in the Advanced Options dialog box of a specific device. For detailed steps, refer to the online Help index keyword “segment size”. Changing the Data Protector Media Agents and Disk Agents use memory buffers Number of Buffers during data transfer. Memory is divided into a number of buffer areas. Values from 1 - 32 may be specified.
Configuring and Using Backup Devices Device Concurrency, Segment Size, and Block Size Before changing the block size for a particular SCSI card, refer to the SCSI vendor documentation or contact the vendor support. Changing the Block Size in Data Protector You can set the block size in the Advanced Options dialog box of a specific device. For detailed steps, refer to the online Help index keyword “block size”.
3 Configuring Users and User Groups Chapter 3 81
Configuring Users and User Groups In This Chapter In This Chapter This chapter explains how to configure both user groups and individual users.
Configuring Users and User Groups Data Protector User Rights Data Protector User Rights Data Protector users have the user rights of the user group they belong to. For example, all members of the Admin user group have the rights of the Data Protector Admin user group. When configuring a Windows NT or a Windows 2000 user in a Data Protector cell running the Cell Manager on the HP-UX or Solaris platform, the user has to be configured with the Domain Name or the wildcard group "*".
Configuring Users and User Groups Data Protector User Rights Start backup specification Allows the user to perform a backup using a backup specification, so that the user can back up objects listed in any backup specification and can also modify existing backups. Save backup specification Allows the user to create, schedule, modify, and save any backup specification. Back up as root Allows the user to back up any object with the rights of the root login on UNIX clients.
Configuring Users and User Groups Data Protector User Rights Start restore Allows users to restore their own data as well as monitor and abort their own restore sessions. Users that have this user right are able to view their own objects and public objects on the Cell Manager. Restore to other clients Allows the user to restore an object to a system other than the one from where the object was backed up. Restore from other users Allows the user to restore objects belonging to another user.
Configuring Users and User Groups Predefined Data Protector User Groups Predefined Data Protector User Groups The following default groups are provided: Admin, Operator, and User.
Configuring Users and User Groups Predefined Data Protector User Groups The user rights you have set on the Cell Manager determine the availability of the Data Protector Cell Manager GUI or GUI contexts to the computer from which you connect to the Cell Manager. For example, if you have only the Start Restore user right set, then only the Restore context is available when you install the User Interface component. After the initial installation, all default user groups are empty except for the Admin group.
Configuring Users and User Groups Adding or Deleting a User Group Adding or Deleting a User Group The default Data Protector user groups are sufficient for most needs. It is recommended that you verify and, if necessary, modify the default user group rights to better fit your requirements. Adding a User Group 1. In the Data Protector Manager, switch to the Users context. 2. In the Scoping Pane, right-click Users, and then click Add User Group. The Add User Group wizard appears. 3. Follow the wizard.
Configuring Users and User Groups Adding or Deleting a User Group Deleting a User Group 1. In the Data Protector Manager, switch to the Users context. 2. In the Scoping Pane, expand Users to dispaly the user groups. 3. Right-click the user group to be deleted and click Delete. 4. Confirm the action.
Configuring Users and User Groups Adding or Deleting a User Adding or Deleting a User After the product installation, the following users are configured in the Admin user group: • UNIX root user on UNIX systems • Windows administrator on Windows systems • The user performing the installation By adding a new user to one of the Data Protector user groups you assign this user the rights of that particular group. See “Data Protector User Rights” on page 83 for a description of the user rights.
Configuring Users and User Groups Adding or Deleting a User Figure 3-2 Adding New Users For further information, press F1.
Configuring Users and User Groups Modifying a User Modifying a User You can change the properties of an existing user, or move the user from one user group to another. NOTE You cannot change user rights for individual users, but only for the entire user group. Changing User Properties To modify a user’s properties, follow these steps: 1. In the Data Protector Manager, switch to the Users context. 2. In the Scoping Pane, expand Users, and click the user group to which the user belongs. 3.
Configuring Users and User Groups Changing User Group Rights Changing User Group Rights Users have the rights of the groups to which they belong. So, changing the user rights of the user group changes the user rights for all users in that group. You can change the rights of user groups and, in doing so, change the rights of each user within that group. You cannot change the rights of the Admin user group, however.
Configuring Users and User Groups Example User Configurations Example User Configurations This section gives some examples of typical user configurations. Allowing Users to Restore Their Own Files This restore policy allows all or just selected users to restore their own data. It provides sufficient security and may relieve the backup operator from doing a number of restore operations. When to Use This Policy • When the users have sufficient knowledge to handle restores.
Configuring Users and User Groups Example User Configurations 2. Add the users who will be able to configure their own backups to this user group. 3. Change the owner of the backup configuration so that the users will be able to start these backups. See Figure 3-1 on page 88.
Configuring Users and User Groups Example User Configurations 96 Chapter 3
4 Managing Media Chapter 4 97
Managing Media In This Chapter In This Chapter This chapter gives detailed information on how to manage your media, including: “Overview of Data Protector Media Management” on page 99 “Creating a Media Pool” on page 102 “Adding Media to a Media Pool” on page 107 “Formatting Media” on page 108 and “Importing Media” on page 113 “Appending Backups to Media” on page 117 “Using a Pre-Allocation List of Media for Backup” on page 119 “Selecting Media for Backup” on page 120 “Setting Data Protection for Media” on
Managing Media Overview of Data Protector Media Management Overview of Data Protector Media Management Data Protector provides a powerful media managing functionality that allows simple and efficient management of a large number of media. NOTE Data Protector recognizes and uses different format types to write data to media. For limitations incurred, refer to “Using Different Media Format Types” on page 148.
Managing Media Overview of Data Protector Media Management • The ability to store information about media in a central place and share this information among several Data Protector cells. • Support for media vaulting, also known as archiving or off-site storage. • Creation of additional copies of media. Media copying can be either manually started or automated. Information about the media used is stored in the IDB.
Managing Media Overview of Data Protector Media Management “Creating a Media Pool” on page 102. “Adding Media to a Media Pool” on page 107. 2. Using media for backups. This includes how the media are selected for a backup, what media condition factors are checked (for example, the number of overwrites), how new backups are appended to the media, and when data on the media can be overwritten. 3. Vaulting media to a safe place (vault). 4. Recycling media once data on the media is not needed anymore.
Managing Media Creating a Media Pool Creating a Media Pool What Is a Media Pool? A media pool represents a set of media of the same type (for example DLT) used for backup, with the same usage policy and properties. For example, you may have one media pool for regular backup, one for archive backup, and one for each department. 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.
Managing Media Creating a Media Pool Properties of a Media Pool This section describes the properties of a media pool. You specify them when you are configuring the media pool. Some of the properties can be modified later. Pool Name A media pool name identifies a media pool. It can be up to 32 characters long, including spaces. You should assign a meaningful name that will help you identify the media pool later, for example, your department name.
Managing Media Creating a Media Pool If InitOnLoosePolicy is set to 1 (by default, it is set to 0) media that are unrecognized by Data Protector (new media) are automatically formatted. This policy is preferred if you want unattended backup to succeed, as it maximizes the number of media Data Protector can choose from. Unformatted media first This is a modification of the Loose policy.
Managing Media Creating a Media Pool medium is used first. If additional media are needed during the same backup session, they must be free and not contain any protected backups. This media usage policy will create media which will contain a full backup, followed by any number of incremental backups. NOTE If you use the append functionality and the backup requires more than one medium, only the first medium used can contain backed up data from a previous session.
Managing Media Creating a Media Pool Maximum number of overwrites The usage of a medium is defined as the number of overwrites from the beginning of the medium. Once the medium has more than the threshold number of overwrites, it is marked as poor. The default threshold is 250 overwrites, except for DDS tapes, for which it is 100 overwrites. For more information on how media condition factors are calculated, see “Changing How Media Condition Is Calculated” on page 134.
Managing Media Adding Media to a Media Pool Adding Media to a Media Pool Once you have created a media pool, you have to add the media that you want to use for backup to this media pool. How to Add the Unused Media To add unused media to the media pool, see “Formatting Media” on page 108. If your media allocation policy for the media pool is set to loose, formatting media as a separate step is not required.
Managing Media Formatting Media Formatting Media What Is Formatting Formatting media prepares them for use with Data Protector by saving Media? the information about the media (media IDs, description and location) in the IDB, and also writes this information on the medium itself (medium header). When you format media, you also specify to which media pool the media belong. NOTE Certain media management operations (initialize, scan, enter, and eject) can be performed during backup or restore.
Managing Media Formatting Media How to Format Media To format media, browse for the specific device, media pool, or library slot in the Devices & Media context, right-click it and click Format. For detailed steps, refer to the online Help index keyword “formatting media”. If you use library devices, you can select multiple slots using the Ctrl key and format several media in a single step. For detailed steps, refer to the online Help index keyword “formatting media in library devices”.
Managing Media Formatting Media Figure 4-2 Cartridge Memory Reformat for Specific Slot What’s Next? Once you have formatted your media, you may use the media for backup. See Chapter 5, “Backup,” on page 151 for more information on how to configure backups. Formatting Media in a Magazine If you are using a device with magazine support, Data Protector allows you to format all media or a single medium in the magazine.
Managing Media Formatting Media TIP To format media used by other applications, use the Force Operation option. Data Protector protected media cannot be re-formatted using this option. You have to first remove the protection. See “Recycling Media” on page 123 for more information. What’s Next? Once you have formatted your media, you may use these media for backup. See Chapter 5, “Backup,” on page 151 for more information on how to configure backups.
Managing Media Formatting Media NOTE Do not rely on Data Protector to recognize other media types, as recognition depends on the platforms you use. Cartridge Memory Enabled Recognition With Cartridge Memory enabled LTO drive(s) used with Cartridge memory enabled media, Cartridge Memory provides the attributes for giving specific ownership information. Data Protector uses this ability to recognize media under ownership of other applications.
Managing Media Importing Media Importing Media Importing media adds media already used by Data Protector to a media pool, without losing the data on the media. Media used by Data Protector are media that were formatted by Data Protector, but exported from the Data Protector cell. Importing a medium writes detailed information about backed up data on the medium to the IDB, so that you can later browse it for a restore. Use media import when moving your media between Data Protector cells.
Managing Media Importing Media Figure 4-3 Import Multiple Media Importing the Catalog from Media Importing the catalog from a medium writes the information about file versions into the IDB, enabling you to browse files and directories for restore. Use Import Catalog if the catalog protection for a particular object has expired and you can no longer browse its files and directories. This operation is not available for media in free pools.
Managing Media Importing Media Figure 4-4 Import Catalog Importing Media in a Magazine Device If you use a device with magazine support, Data Protector allows you to import all media or a single medium into the magazine. Prerequisite The media pool for the magazine device must be configured with the Magazine Support option enabled.
Managing Media Importing Media Figure 4-5 Import Magazine How to Import a Single Medium into a Magazine To import a single medium into a magazine device, expand the media pool used for that device in the Devices & Media context, select the specific magazine, right-click the Media item and then click Import. For detailed steps, refer to the online Help index keyword “importing a single medium in a magazine”. What’s Next? Once you have imported the media, you may use these media for backup.
Managing Media Appending Backups to Media Appending Backups to Media Data Protector allows you to add new backups to media which already contain backups. This method conserves media space. Limitation Backups cannot be appended on media used in Travan devices. The appendable media usage policy can be selected when configuring a media pool. Appendable media contain some currently protected objects; the media must be in good condition and must not be full.
Managing Media Appending Backups to Media • Link a different pool to each client in the backup specification, or create a separate backup specification per client. This is a method to create media containing restore chains. Be aware that occasionally media will be created which contain incremental backups only. See “Media Usage Policy” on page 104 for a description of media usage policy options like Appendable.
Managing Media Using a Pre-Allocation List of Media for Backup Using a Pre-Allocation List of Media for Backup You can specify the order in which media from a media pool will be used for backup. This order is called a pre-allocation list. You specify the pre-allocation list when configuring a backup. The purpose of a pre-allocation list is to control which media will be used for a backup session. You have to match the pre-allocation list with the available media before each backup.
Managing Media Selecting Media for Backup Selecting Media for Backup Data Protector media management automatically selects the most appropriate media for backup. This section explains various factors that influence how media are selected for backup. Media Allocation Policy You can influence how media are selected for backup using the media allocation policy.
Managing Media Selecting Media for Backup Media in poor condition are not used for backup. Media in fair condition are used only if no media in good condition are available. Media in good condition are sorted to use the one with the least number of overwrites first. Media are always selected first from the specified pool and (optionally) from the free pool. Table 4-2 How Media Are Selected for Backup Allocation Policy Allocate Unformatted Media First Data Protector Selection Order Loose OFF 1.
Managing Media Setting Data Protection for Media Setting Data Protection for Media Data Protector keeps track of data on every medium used. When configuring a backup, you can protect your data from being overwritten by newer backups for a specified time. This protection is on a session basis: if data from several sessions is on the same media, the longest protection defines protection of the media. See “Data Protection: Specifying How Long Data Is Kept on the Media” on page 228 for detailed information.
Managing Media Recycling Media Recycling Media Data Protector keeps track of data on every medium used. When configuring a backup, you protect your data from being overwritten by newer backups for a specified time. See Chapter 5, “Backup,” on page 151 for detailed information. Keep in mind that on all media there may be data from several backup sessions. Each session can contain data from several backup objects (file systems).
Managing Media Moving Media to Another Pool Moving Media to Another Pool Data Protector lets you move a medium from one media pool to another media pool of the same media type. You need this feature if you want to reorganize the backups and rearrange the purpose of each pool. It is also useful when you want to use the medium in a device which is the default device of another media pool.
Managing Media Exporting Media from Data Protector Exporting Media from Data Protector What Is Exporting Media? Exporting (removing) a medium removes the information about the medium and its contents from the IDB. Data Protector no longer recognizes that this medium exists. The medium and the data it contains remain unchanged. You can import the medium later, thus re-reading the information about data on the medium back to the IDB. See “Importing Media” on page 113 for instructions.
Managing Media Modifying Media Locations Modifying Media Locations What Is a Location? The media location helps you to physically locate the media. You enter the location when you format the media. The initial location information is written on the media and to the IDB. You should modify the location whenever you move media to a different place, such as to off-site storage, for example, “Shelf 4-Box 3”. The revised location information is only written to the IDB.
Managing Media Modifying Media Descriptions Modifying Media Descriptions What Is a Description? The media description helps you identify media. You can define a media description when you format new media. The initial description is written on the media and to the IDB. If media were auto-formatted during backup, you may want to change the automatically-created description to something better suited to your needs. The revised description information will only be written to the IDB.
Managing Media Verifying Data on a Medium Verifying Data on a Medium What Is Verifying? Verifying a medium shows whether the data on the medium is valid. It also updates the information about the medium in the IDB, such as medium condition. Data Protector performs the following: • Checks the Data Protector headers with information about the medium (medium ID, description, and location.) • Reads all blocks on the medium.
Managing Media Scanning Media in a Device Scanning Media in a Device What Is Scanning? You scan a device to update Data Protector information about the media in the device or library. • In a standalone device, you scan a medium in a drive. • In a library device, you scan media in the selected slots. • With Cartridge Memory enabled drives, Data Protector can check the library inventory very quickly.
Managing Media Scanning Media in a Device List Cartridge Memory List Cartridge Memory, available for Cartridge Memory enabled drives, is equivalent to a standard Data Protector scan, with the difference that the information is retrieved from Cartridge Memory instead of tape. It does not require the loading or unloading of tape and is faster. However, using this method to synchronize the repository with the IDB is not recommended. Use the standard scan instead.
Managing Media Checking the Condition of a Medium Checking the Condition of a Medium Data Protector allows you to view information about the usage and condition of a medium. The condition of the medium affects the ability to write to the medium and read the data contained on it. This helps you determine when the medium has to be replaced. See “Factors Influencing the Condition of Media” on page 132 for a description of when to change your media.
Managing Media Checking the Condition of a Medium Cartridge Memory List To view some additional information about Cartridge Memory enabled media, you can use the Cartridge Memory List feature. This lets you view the contents of Cartridge Memory for the medium. Information stored in the IDB is not related to the information stored in the Cartridge Memory. Factors Influencing the Condition of Media Data Protector uses media condition factors to calculate the condition of the media.
Managing Media Checking the Condition of a Medium Statuses of Media and Media Pools Media or media pools can have three statuses, based on the media condition factors: Good. Less than 80% of the threshold for age or usage. Fair. 81 to 100% of the threshold for age or usage. Poor. Exceeds 100% of the threshold for age or usage, or read/write errors have occurred on this medium. See below for information on how to change the media condition factors.
Managing Media Checking the Condition of a Medium Changing How Media Condition Is Calculated When you add a medium to a media pool, you can define the media condition factors that are used to calculate the condition of the medium. IMPORTANT For Data Protector to accurately calculate the condition of the media, use new media when adding media to the media pool. Change the media condition factors using the Condition property page for the media pool.
Managing Media Searching for and Selecting a Medium Searching for and Selecting a Medium Use this function to locate and select specific media without having to browse through the entire list of media. Media selection is especially useful for vaulting purposes, for example, selecting all media older than 14 days and moving them to a vault.
Managing Media Entering a Medium into a Device Entering a Medium into a Device Data Protector allows you to physically enter media into a library device. You can select the slot that you want to use. Entering and ejecting media does not affect the media pool to which they belong. IMPORTANT It is recommended that you use Data Protector to handle the media in the device. This keeps the information about the media in the IDB up to date.
Managing Media Ejecting a Medium from a Device Ejecting a Medium from a Device Data Protector allows you to physically eject media from the device. When used with library devices, media are moved to the specified slot. You can select the slot that you want to use. IMPORTANT It is recommended that you use Data Protector to handle the media in the device. This keeps the information about the media in the IDB up to date.
Managing Media Ejecting a Medium from a Device TIP Ejecting of media can be scheduled. Refer to “Scheduled Eject of Media” on page 138 for details. What’s Next? If you want to put media in a vault, see “Vaulting Media” on page 140 for more information. Scheduled Eject of Media Data Protector allows you to schedule the ejection of specific media through the reporting mechanism. The scheduled ejection of media is linked to a specific report made using the external send method.
Managing Media Ejecting a Medium from a Device If media are not removed from the mail slots after a default time span, and there are still media to be ejected, the omnimm command aborts the operation. You can change the default time span in the .omnirc file. Refer to “Using Omnirc Options” on page 525. For an example of configuring scheduled ejection of media, refer to Appendix, “Example of Scheduled Eject of Media,” on page A-14.
Managing Media Vaulting Media Vaulting Media What Is Vaulting? Vaulting is a process of moving media with important information to a safe place where they are kept for a specified period of time. The safe place for media is often called a vault. This is also known as off-site storage. Vaulting and Data Protector Data Protector supports vaulting on various levels: • Allows setting up of data protection and catalog protection policies. • Allows easy selection and ejection of media from the library.
Managing Media Vaulting Media 4. Select the media that you want to store in the vault, change the location of the media, eject the media, and store them in the vault. 5. Select the media that you want to remove from the vault, such as media with expired data protection. You can get a list of such media using the List of Media report. For how to generate this report, see “Running Individual Reports” on page 338. 6. Enter the media into the library, scan them, and then change the location field. 7.
Managing Media Vaulting Media 2. Take the media from a vault, enter the media in the library, and scan them. 3. If the catalog protection for the media is still valid, restore data by selecting what you want to restore, using the Data Protector user interface. If the catalog protection for the media has expired, Data Protector may not have detailed information about the backed up data.
Managing Media Copying Media Copying Media What Is Media Copying? Data Protector enables copying of backed up data to a second set of media. You can move either the copies or the original media to a safe place for archiving/vaulting purposes, and keep the other set of media on site for restore purposes. For how to configure Data Protector for vaulting, see “Vaulting Media” on page 140. For more information on vaulting, refer to the HP OpenView Storage Data Protector Concepts Guide.
Managing Media Copying Media NOTE When copying media, it is possible that the target medium reaches the end of the tape before the source medium. This may happen if the source medium was written in streaming mode and you make a copy on a busy system or through a loaded network, which can create blank space where the tape has stopped and started again. You can prevent this by enabling tape padding when you format media. See “Formatting Media” on page 108.
Managing Media Copying Media Automated Media Copying What Is Automated Automated media copying is an automated process that creates copies of Media Copying? the media containing backups. Data Protector offers two types of automated media copying: post-backup media copying and scheduled media copying. What Is Post-Backup Media Copying? Post-backup media copying takes place after the completion of a backup session. It copies all media used in that particular session.
Managing Media Copying Media target medium is selected to which the data will be copied. The target media are selected from the same media pool as the source media, from a free pool, or from the blank media in a library. Selection and Use of Devices For each source medium, Data Protector selects a pair of devices from the devices that you specified in the automated media copy specification. The automated media copy functionality provides its own balancing.
Managing Media Detection of Write-Protected Media Detection of Write-Protected Media Data Protector can detect and handle media that has been mechanically protected by setting the write protection switch on. NOTE It is recommended not to use write-protected media with Data Protector. The following operations can detect and handle write-protected media: • Read-only operations, such as: list, scan, and verify. Read-only operations detect the write-protected media and proceed without any warnings.
Managing Media Using Different Media Format Types Using Different Media Format Types Data Protector recognizes and uses two different format types to write data to media: • Data Protector (for backup devices that are under direct Data Protector control) • NDMP (for backup devices that are connected to NDMP servers) Both format types use different Data Protector Media Agent components to communicate with backup devices.
Managing Media Modifying Views in the Media Management Window Modifying Views in the Media Management Window You can customize the information you see about the media in the Media Management window. This enables you to always see the information you need. To customize your view, do the following: 1. Open the global options file. On the UNIX Cell Manager: /etc/opt/omni/options/global On the Windows Cell Manager: \config\options\Global 2.
Managing Media Modifying Views in the Media Management Window 150 Chapter 4
5 Backup Chapter 5 151
Backup In This Chapter In This Chapter This chapter explains how to back up your data. It also describes some advanced Data Protector features.
Backup Configuring a Backup Configuring a Backup A backup is a process that creates a copy of system data on backup media. This copy is stored and kept for future use in case the original is destroyed or corrupted. Prerequisites • You need to have a Disk Agent installed on every system that is to be backed up, unless you use NFS (on UNIX) or Network Share Backup (on Windows) for backing up these systems. • You need to have at least one backup device configured in the Data Protector cell.
Backup Configuring a Backup A backup session is based on the backup specification, and can be started interactively. During the backup session, Data Protector reads the backup objects, transfers their data through the network, and writes them to the media residing in the devices. Figure 5-1 Backup Session Creating a Backup Specification You can configure a backup specification using the Data Protector user interface.
Backup Configuring a Backup Key Points • The backup type (full or incremental) is the same for the whole backup session. All data in a group is backed up using the same backup type. • A backup object can be added to multiple backup specifications. For example, you may have one backup specification for full backups, one for incremental backups, one for a departmental backup, and one for the archive backup. You can give a description for each object.
Backup Configuring a Backup Figure 5-2 Create New Backup Dialog Box 5. Select what you want to back up. Figure 5-3 on page 157 shows data sources selected for backup. Click Next to proceed.
Backup Configuring a Backup Figure 5-3 Source Page of the Backup Wizard 6. Select the device(s) that will be used to back up your data. See Figure 5-4 on page 158. Click Next to proceed.
Backup Configuring a Backup Figure 5-4 Device Page of the Backup Wizard 7. Select backup options. See “Using Backup Options” on page 225 for details. Click Next. 8. In the Schedule page, you can schedule the backup. See “Scheduling Unattended Backups” on page 207 for more information. Click Next. 9. In the Backup Object Summary page, you can review the backup options. See Figure 5-5 on page 159. Click Next.
Backup Configuring a Backup Figure 5-5 Backup Object Summary Page 10. In the final page of the Backup wizard, you can save the backup specification, start the interactive backup, or preview the backup. See Figure 5-6 on page 160. It is recommended to save the backup specification so that you can schedule or modify it later.
Backup Configuring a Backup Figure 5-6 Final Page of the Backup Wizard 11. Click Start Backup to run the backup interactively. The Start Backup dialog box appears. NOTE During a backup, you may be prompted to add more media to continue your backup. This is called a mount request. See “Responding to Mount Requests” on page 310 for more detailed information.
Backup Backing Up UNIX Systems Backing Up UNIX Systems You can install a Disk Agent on every UNIX system in order to back it up. Alternatively, you may use the Network Filesystem (NFS) to back up data from systems that do not have a Disk Agent. See “Backing Up Disks Using NFS” on page 164 for details. See the HP OpenView Storage Data Protector Installation and Licensing Guide or online Help for instructions on how to install a Disk Agent.
Backup Backing Up UNIX Systems Data Protector provides a sophisticated mechanism for incremental backups. To determine which files have changed, the Data Protector Disk Agent checks when each was last modified. This method keeps Data Protector from detecting moved files, as moving the file does not change the modification time. NOTE During a backup session, each file being backed up is opened and read. Therefore, the access time of the file is changed after the backup.
Backup Backing Up UNIX Systems Backing Up Clients Using Disk Discovery How Are Disks Discovered? If you specify a client backup with disk discovery, Data Protector contacts the client at backup time and finds all filesystems on the disks that are attached to that system. Only mounted disks are identified using the mount command. Then Data Protector backs up each filesystem identified as a regular filesystem, except for NFS, CD mounted filesystems, and removable volumes.
Backup Backing Up UNIX Systems Figure 5-7 Selecting an Entire Client to Be Backed Up NOTE Selecting all of the client’s drives is not the same as selecting the check box next to the client name, which is the procedure for a Disk Discovery backup. When you perform a client backup, all the files and directories that belong to the root (/) mountpoint are automatically backed up. Therefore, you cannot exclude the root in the backup specification. If you want to exclude the root, perform a filesystem backup.
Backup Backing Up UNIX Systems To back up this filesystem using NFS, follow the same procedure as if you were backing up any other filesystem on bserv, except that you have to manually type /nfs/wiz/home/special as a mountpoint. Only local filesystems can be browsed. Figure 5-8 NFS Environment Limitations • You can use NFS only if backing up files on HP-UX clients. You can not back up soft links, or character and device files. • ACL attributes are not preserved. NFS does not support ACLs on remote files.
Backup Backing Up UNIX Systems NOTE It is recommended to have root permission on mounted NFS filesystems. When to Use NFS Backup Use NFS backup in either of the following situations: • A system to be backed up is not a part of the Data Protector cell. • You want to back up system platforms that are not supported by Data Protector.
Backup Backing Up UNIX Systems IMPORTANT Unmount a disk before a disk image backup and mount it later. You can use pre- and post- exec commands for this purpose. See Appendix, “Examples of Pre-Exec and Post-Exec Commands for UNIX,” on page A-20. To back up a disk image object, follow the procedure described in “Example of Creating a Backup Specification” on page 155 until you get to the Backup Object Summary page of the wizard. Proceed as follows: 1. In the Backup Object Summary page, click Manual Add.
Backup Backing Up Windows Systems Backing Up Windows Systems Prerequisites You have to install a Disk Agent on at least one Windows computer in the Data Protector cell. This computer then becomes a Disk Agent client. Files that do not reside on Disk Agent clients can be backed up if they share their disks with Disk Agent clients. It is better to install a Disk Agent on every Windows system that you want to back up. See “Backing Up Windows Shared Disks” on page 185 for details.
Backup Backing Up Windows Systems • NTFS alternate data streams • NTFS security data NOTE The sharing properties of a folder are not stored in the filesystem and are not backed up within filesystem backup. Information about shares is stored in the registry and is backed up and restored within CONFIGURATION backup object. What Is Not Backed Up? In the backup specification, you can specify the files to be excluded from or skipped by the backup.
Backup Backing Up Windows Systems NTFS 3.x Filesystem Features The NTFS 3.x filesystem has introduced new file attributes and concepts, which can be summarized as follows: • The NTFS 3.x filesystem supports reparse points. The volume mount points, Single Instance Storage (SIS), and directory junctions are based on the reparse point concept. See “Glossary” for details. • The NTFS 3.x filesystem supports sparse files as an efficient way of reducing the amount of allocated disk space. • The NTFS 3.
Backup Backing Up Windows Systems The advantages of the VSS filesystem backup are the following: • A computer can be backed up while applications and services are running. Therefore, the applications can continue writing data to the volume during a backup. • Open files are no longer skipped during the backup process, because they appear closed on the shadow copy volume at the time of the shadow copy creation. • Backups can be performed at any time without locking out users.
Backup Backing Up Windows Systems Sparse Files Sparse files contain many zero data sets as opposed to, for example, compressed files. At backup time, Data Protector automatically skips zero-parts, so that the media space on the backup device is allocated for non-zero parts only. UNIX and Windows sparse files are not compatible.
Backup Backing Up Windows Systems Figure 5-9 Specifying Objects Using Manual Add For detailed steps, refer to the online Help index keyword “concurrency”. Backing Up CONFIGURATION The Data Protector CONFIGURATION object is a set of data structures maintained by the Windows operating system that are not treated as a part of a filesystem backup when you, for example, select logical drives such as C: or D: for the backup.
Backup Backing Up Windows Systems Figure 5-10 Windows NT CONFIGURATION TIP The SystemRecoveryData file is only needed for Windows disaster recovery. If a backup version is not used for disaster recovery, clear the SystemRecoveryData check boxes when backing up CONFIGURATION. Windows 2000/XP/Server 2003 CONFIGURATION The items listed at “Windows NT CONFIGURATION” on page 173 also belong to the Windows 2000/XP/Server 2003 CONFIGURATION.
Backup Backing Up Windows Systems See “Backing Up WINS, DHCP, and DNS” on page 178. • SysVol SysVol is a shared directory that stores the server copy of the domain's public files, which are replicated among all domain controllers in the domain. • IIS Microsoft Internet Information Server is a network file and application server that supports multiple protocols. Primarily, IIS transmits information in Hypertext Markup Language (HTML) pages by using the Hypertext Transport Protocol (HTTP).
Backup Backing Up Windows Systems Backing Up CONFIGURATION Only one CONFIGURATION backup can run on a system at the time. You have to expand a client and select its CONFIGURATION in the Backup wizard. See “Example of Creating a Backup Specification” on page 155, Figure 5-10 and Figure 5-11. Backing Up the Windows 2000/XP/Server 2003 System State The Windows System State consists of several elements related to various aspects of Windows. They are structured under their respective Windows backup object.
Backup Backing Up Windows Systems Figure 5-12 System State on Windows 2000/XP/Server 2003 Backing Up the Windows Registry The database repository of information containing the Windows system configuration is known as the Registry. The Windows Registry is important for the system operation, and must be backed up regularly. The Registry can be backed up as a part of CONFIGURATION, or separately by selecting the Registry folder as shown in Figure 5-13.
Backup Backing Up Windows Systems Figure 5-13 Backing Up the Windows Registry Backing Up WINS, DHCP, and DNS WINS, DHCP, DNS Servers In TCP/IP networks, the following services can be configured and run on Windows servers: • WINS Server This service, also known as Windows Internet Name Service, is a dynamic replicated database service that can register and resolve NetBIOS names to IP addresses used on a TCP/IP network. To back up this database, select WINS in the Backup wizard.
Backup Backing Up Windows Systems Backing Up the Windows 2000/XP/Server 2003 Services Backing up the Windows 2000/XP/Server 2003 services means backing up the data structures used by these services. A particular database is exported (dumped) into a file, which is then backed up. The Windows 2000/XP/Server 2003 services are always backed up if CONFIGURATION was selected in the Backup wizard.
Backup Backing Up Windows Systems This service provides automatic distribution of events to subscribing COM+ components. To back up this database, select the ComPlusDatabase in the Backup wizard. • Removable Storage This service manages removable media, drives, and libraries. To back up this database, select RemovableStorageManagementDatabase in the Backup wizard. IMPORTANT You can back up the Removable Storage database, but this service is not used for Data Protector media management.
Backup Backing Up Windows Systems For example, if you use Active Directory to publish Certificate Revocation Lists (CLRs), back up the Active Directory services along with the Certificate Services. • Remote Storage Service Remote Storage Service (RSS) is used to automatically move infrequently accessed files from local to remote storage. Remote files are recalled automatically when the file is opened. Although RSS databases are part of System State data, you must back them up manually.
Backup Backing Up Windows Systems net stop/start “Remote Storage Engine” net stop/start “Remote Storage File” The RSS databases are located in the following directories: <%SystemRoot%>\System32\RemoteStorage <%SystemRoot%>\System32\NtmsData Backing Up Windows User Profiles, Event Logs, and User Disk Quotas User Profiles A User Profile contains information about a user configuration. This includes the profile components, such as desktop settings, screen colors, and network connections.
Backup Backing Up Windows Systems See also “Warnings When Backing Up System Disks” on page 263. Event Logs Event logs are files where the Windows operating system saves information about events, such as starting and stopping services or the logging on and logging off of a user. User Disk Quotas User Disk Quotas enable enhanced tracking and control over disk space usage on Windows 2000. Data Protector backs up user disk quotas on the whole system and for all configured users at a time.
Backup Backing Up Windows Systems How to Perform a Backup To perform a Windows client backup, you have to create a backup specification as described in “Example of Creating a Backup Specification” on page 155. In the Source property page of the Backup wizard, select the check box next to the client name to obtain the disk discovery functionality. Then, follow the wizard.
Backup Backing Up Windows Systems See “Using Backup Options” on page 225 for information on using and structuring your backup specifications. Backing Up Windows Shared Disks Data Protector allows you to back up data on Windows shared disks. You have to use a regular Disk Agent client, which can then be used to back up other remote systems via shared disks. Then you can configure a backup specification.
Backup Backing Up Windows Systems IMPORTANT The Disk Agent client must have the Inet service configured using an account with access to the shared disks. This must be a specific user account, not the system account. See “Setting the User Account for the Data Protector Inet Service” on page 187 for more information on how to use the appropriate logon account. Once you have set the user account for the Inet service, you can back up the shared disks as though they were residing on the local system.
Backup Backing Up Windows Systems 9. Enter the required information. See online Help for details. Setting the User Account for the Data Protector Inet Service The following procedure describes how to change the user account used by the Data Protector Inet service to access disks that belong to remote computers. This account must have permission to access both the local client and the remote shared disks. It must be a specific user account, not the system account.
Backup Backing Up Windows Systems Figure 5-16 Inet Logon Option on Windows NT 7. Click OK to return to the Services dialog box. 8. Ensure that Data Protector Inet is still selected, and then click Start. 9. Click Close to confirm and exit this dialog. Data Protector is now able to access all disks to which the account you entered has access. Windows 2000/XP/Server 2003 Proceed as follows to change the user account on a Windows 2000/XP/Server 2003 Disk Agent client: 1.
Backup Backing Up Windows Systems Figure 5-17 Inet General Property Page on Windows 2000/XP/Server 2003 4. In the Log On As area, select the This Account button. 5. Enter or browse for the account that has the correct permission to access the shared disks you want to back up. 6. Enter the password, then confirm it.
Backup Backing Up Windows Systems Figure 5-18 Inet Logon option on Windows 2000/XP/Server 2003 7. Click Apply to apply the changes and then restart the service by clicking the Start button in the General property page. Backing Up Windows Disks as Disk Image Objects What Is a Disk Image Backup? A disk image backup is a high-speed backup of disks, disk partitions, or logical volumes without tracking the file and directory structure stored on these data sources.
Backup Backing Up Windows Systems How to Specify a Disk Image Section You can specify a disk image section in two ways. In case of a zero downtime backup (snapshot or split mirror), you must use the second way. • \\.\, for example: \\.\E: • \\.\PHYSICALDRIVE#, where # is the current number of the disk you want to back up. For example: \\.
Backup Backing Up Windows Systems Figure 5-19 The Numbers Representing Disks (Physical Drive Number) on Windows 2000 System NOTE The numbers representing disks can change if the system is rebooted. Limitation A disk image backup fails if a file on the target system is open, since Data Protector cannot lock the file. How to Perform a Disk Image Backup To perform a disk image backup, use the Manual add function from the Backup Object Summary page.
Backup Backing Up Windows Systems Figure 5-20 The Manual Add Functionality Chapter 5 193
Backup Backing Up Novell NetWare Systems Backing Up Novell NetWare Systems This section describes how to back up Novell NetWare filesystems and NetWare Directory Services (NDS). Backing Up Novell NetWare Filesystems (Volumes) Prerequisites To back up data on a Novell NetWare system, install the Novell NetWare Disk Agent on the Novell NetWare system. See the HP OpenView Storage Data Protector Installation and Licensing Guide for instructions.
Backup Backing Up Novell NetWare Systems • Trustee information • Inherited right mask • File and directory attributes • Time attributes (creation date/time, modification date/time, last accessed date/time, last modified date/time, last archived date) • Owner • Owning name space • Search mode • Volume or directory space restrictions. To back up volume restrictions, select the whole volume object for backup. Server Specific Information is backed up separately as a part of CONFIGURATION mount point.
Backup Backing Up Novell NetWare Systems • The Compress option • The omit_deleted_files option (restore option) Files of up to 4 GB are backed up on NetWare 4.X. NOTE To allow users to run backups on the Novell NetWare system, grant them the Backup as Root user right. See Chapter 3, “Configuring Users and User Groups,” on page 81 for details on how to change user rights. Data Protector cannot back up moved files during incremental backup sessions.
Backup Backing Up Novell NetWare Systems Figure 5-21 Backing Up NetWare 4.x and NetWare 5.
Backup Backing Up Novell NetWare Systems Client Backup with Disk Discovery You can discover disks (volumes) on NetWare just as you can for UNIX or Windows systems. How Are Disks Discovered? If you specify a client backup with disk discovery, Data Protector first contacts the client and discovers all volumes that belong to the client. Then it backs up the CONFIGURATION item and each discovered volume as a regular filesystem.
Backup Backing Up Novell NetWare Systems Backing Up NetWare Directory Services (NDS) Data Protector backs up NDS using Novell NetWare Storage Management Services (SMS). Data Protector backs up and restores all extensions to the NDS Schema. NOTE Incremental backup of the NDS database is not possible. A full backup of the NDS database is always performed.
Backup Backing Up Novell NetWare Systems has its counterpart used by Data Protector, containing forward slashes, which are used for Windows as well: /[Root]/O=HSL/CN=Admin Except for this naming rule, the Data Protector backup specification syntax is the same as for Novell NetWare or UNIX filesystem objects. NOTE NDS objects (container and leaf objects) are represented and backed up as directories. These objects can be skipped using the skip option or backed up using the only option.
Backup Backing Up OpenVMS Systems Backing Up OpenVMS Systems This section describes how to back up OpenVMS filesystems. Backing Up OpenVMS Filesystems Prerequisites To back up data on a OpenVMS system, install the OpenVMS Disk Agent on the OpenVMS system. See the HP OpenView Storage Data Protector Installation and Licensing Guide for instructions. To use backup devices connected to an OpenVMS system with Data Protector, install the OpenVMS Media Agent on the OpenVMS system.
Backup Backing Up OpenVMS Systems Files can be backed up from mounted FILES-11 ODS-2 or ODS-5 volumes only. Limitations • Any file specifications that are entered into the GUI or passed to the CLI must be in UNIX style syntax: /disk/directory1/directory2/filename.ext.n — The string should begin with a slash, followed by the disk, directories, and filename, separated by slashes. — Do not place a colon after the disk name. — A period should be used before the version number instead of a semi-colon.
Backup Backing Up OpenVMS Systems Files with multiple directory entries are only backed up once using the primary path name. The secondary path entries are saved as soft links. During a restore, these extra path entries will also be restored. There is no support for an equivalent to BACKUP/IMAGE. To make a restored copy of an OpenVMS system disk bootable, the OpenVMS WRITEBOOT utility has to be used to write a boot block on to the restored disk.
Backup Backing Up in a Direct Backup Environment Backing Up in a Direct Backup Environment This section provides the steps for the configuration of a direct backup backup specification. Please refer to HP OpenView Storage Data Protector Concepts Guide for a complete information on direct backup concepts. Prerequisites • The application and backup systems must be configured for split mirror or snapshot backup, depending on the disk array used.
Backup Backing Up in a Direct Backup Environment • You need to have appropriate user rights for performing a backup. Refer to Chapter 3, “Configuring Users and User Groups,” on page 81. Limitations • The systems in the direct backup environment must be HP-UX 11.0. • The min and max options for the load balancing option are ignored for direct backup. All devices selected in the backup specification are load balanced, if load balancing is used.
Backup Backing Up in a Direct Backup Environment • rawdisks • Oracle8i databases (online) • Oracle8i databases (offline) Backing Up Rawdisks Please refer to the online Help index keyword “configuring direct backup specifications” for detailed information on how to configure a rawdisk direct backup specification.
Backup Scheduling Unattended Backups Scheduling Unattended Backups Data Protector allows you to configure unattended backups by scheduling backups of your systems at specific times. The configuration and your scheduling policies can significantly influence the effectiveness and performance of your backup. Key Points • To simplify scheduling, Data Protector provides backup specifications for group clients.
Backup Scheduling Unattended Backups • Each backup specification can be scheduled multiple times with different option values. Within one backup specification, you can schedule both ZDB disk and ZDB disk/tape backups, and specify a different data protection period for each individual or periodic scheduled backup. • Data and catalog protection settings determine the period that data is kept on a medium (data protection) and in IDB (catalog protection).
Backup Scheduling Unattended Backups Starting Backups on Specific Dates Data Protector allows you to define the date and time when you want your unattended backup to start. You usually want to back up on specific dates when configuring exceptions to your regular periodic backups, for example, if you want to back up some data before a specific event. How to Configure Backups on Specific Dates To configure a backup on a specific date, you can create a new backup specification, or modify an existing one.
Backup Scheduling Unattended Backups Fortnightly full Data Protector runs a full backup every second Friday. Between these backups, Data Protector runs Incr1 backups every Monday to Thursday, all at 21:00 (9 p.m.). Monthly full Data Protector runs a full backup on the first of every month, an Incr1 backup every week, and an incremental backup every other day. This is intended for relatively static environments.
Backup Scheduling Unattended Backups To disable a backup schedule, select the Disable Schedule option in the Schedule property page. The backup will not be performed until you deselect this option. Disabling backup schedules does not influence currently running backup sessions. Skipping Backups During Holidays By default, Data Protector runs backups on holidays. If you do not wish to run your backups on holidays, set the Holidays option to ON in the Schedule page of the Backup wizard.
Backup Scheduling Unattended Backups Running Consecutive Backups You can start a backup after one is finished. For example, you can start a backup of an Oracle database after a filesystem backup is finished. For detailed steps, refer to the online Help index keyword “running consecutive backups”. For details on pre- and post-exec scripts on UNIX systems, refer to the Appendix, “Examples of Pre-Exec and Post-Exec Commands for UNIX,” on page A-20.
Backup Selecting a Backup Type: Full or Incremental Selecting a Backup Type: Full or Incremental To save time and media during a backup, you can combine full and incremental backups. For example, you can create a second-level incremental backup based on a previous first-level incremental backup, a third-level incremental backup based on a previous second-level incremental backup, and so on. The backup type (full or incremental) applies to the entire backup specification and only to filesystem objects.
Backup Selecting a Backup Type: Full or Incremental backup. Even if the previous backup was an incremental (Incr or Incr1, Incr2, ...) backup, the subsequent incremental backup includes only those files that changed in the interim. • Incr1 backup This backup type refers to the most recent still protected full backup with the same ownership. It does not depend on any previous incremental backups. The files that have changed since the most recent still protected full backup are included in the backup.
Backup Selecting a Backup Type: Full or Incremental How to Read Table • The rows in Table 5-1 are independent of each other and show 5-1 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. • The full and IncrX represent still-protected objects of the same owner. Any existing IncrX that is not protected can be used for restore, but is not considered for referencing on subsequent backup runs.
Backup Using Backup Templates Using Backup Templates Overview Data Protector backup templates are a powerful tool that can help you simplify your backup configuration. A template has a set of clearly specified options for a backup specification, which you can use as a base for creating and modifying backup specifications. Data Protector enables you to apply a group of options offered by the template. A template can be used in two ways: • It can be used to create a new backup specification.
Backup Using Backup Templates Figure 5-22 Options Offered by Templates Destination Backup device settings specified in your template apply to your backup specification. Backup specification Backup specification options specified in the template apply to your backup specification. Filesystem Filesystem options specified in the template apply to all filesystem objects of your backup specification.
Backup Using Backup Templates Using a Backup Template When Creating a New Backup Specification When creating a new backup specification, Data Protector offers you a set of backup templates, either default templates or templates you have created. Select an appropriate template, or optionally, select or deselect some groups of options, and then proceed with the Backup wizard. To create a backup specification without predefined settings, select Blank Filesystem Backup.
Backup Using Backup Templates To apply a template to backup specifications, right-click the backup specification and click Apply Template. The Apply Template window appears, in which you apply the desired options. For detailed steps, refer to the online Help index keyword “applying backup templates”.
Backup Using Backup Templates Creating a New Template You can create new templates and use them for creating or modifying backup specifications. To create a new template, use the Backup context. For detailed steps, refer to the online Help index keyword “creating backup templates”. For more information on individual options, refer to “Using Backup Options” on page 225.
Backup Using Backup Templates For more information on individual options, refer to “Using Backup Options” on page 225.
Backup Groups of Backup Specifications Groups of Backup Specifications Data Protector offers you the ability to organize backup specifications into different groups. The purpose of grouping is to organize the specifications of multiple backups. For example, backup specifications for “Corporation X” can be classified into three different groups: • USER_FILES: This group contains backup specifications that perform weekly, full backups for all users in each of the ten departments.
Backup Groups of Backup Specifications Figure 5-26 Example of Backup Specification Groups How to View and Create Groups The following procedure describes how to view the available backup groups and how to create a new one: 1. In the Data Protector Manager, switch to the Backup context. 2. In the View menu, click By Group. The list of available backup groups appears under the Backup Specifications item. Clicking a group lists the backup specifications within that group. 3.
Backup Groups of Backup Specifications How to Delete a Group Before deleting a group, you have to empty it first. One way of doing this is to move the backup specifications into other groups. See online Help for details.
Backup Using Backup Options Using Backup Options Data Protector offers a comprehensive set of backup options to help you fine-tune your backups. All options have default values that are appropriate for most cases. The availability of backup options depends on the type of data being backed up. For example, not all backup options available for a filesystem backup are available for a disk image backup.
Backup Using Backup Options For split mirror and snapshot backups, the backup type is ignored (it is set to full). Data protection that is specified in the Schedule Backup dialog overrides protection settings anywhere else in the backup specification. See Figure 5-27 for a graphic scheme of how some of these options work. You can use backup templates to apply the same group of options to a number of backup specifications. Applying a template changes the backup specification according to the template.
Backup Using Backup Options Figure 5-27 Backup Options Most Frequently Used Backup Options This section describes the options that are most likely to be modified according to specific backup policies.
Backup Using Backup Options Data Protection: Specifying How Long Data Is Kept on the Media Configuring protection policies is extremely important for the safety of your data and for successful management of your environment. See the HP OpenView Storage Data Protector Concepts Guide for more detailed information on how to define these policies. Based on your company data protection policies, you have to specify how long your backed up data is kept on the medium.
Backup Using Backup Options You can specify a different period of protection for each individual or periodic scheduled backup. The data protection specified in the Schedule Backup dialog overrides all other data protection settings in the backup specification. If you leave the default protection, data protection is applied as described for interactive backups. On how to specify data protection, refer to the online Help index keyword “specifying data protection”.
Backup Using Backup Options Figure 5-29 Backup Object Properties - Options: Protection Catalog Protection: How Long Info Is Kept in the Database Besides the Protection option, which controls how long data is protected on media, you can set the Catalog Protection option, which controls the time for which information about backed up files and directories is kept in IDB. Catalog protection and data protection can be set independently. Catalog protection has no effect if the log level is Log None.
Backup Using Backup Options Even when catalog protection expires, you are still able to restore, but you must specify filenames manually. Be aware that catalog protection, together with logging level, has a very big impact on the growth of the IDB. Therefore, it is very important to define a catalog protection policy appropriate to your environment. Refer to the IDB section in the HP OpenView Storage Data Protector Concepts Guide for more information on catalog protection and usage recommendations.
Backup Using Backup Options Table 5-2 Log Directories When this logging level is selected, all detailed information about backed up directories (names, versions, and attributes) is logged to the IDB. You can browse only directories before restoring. However, during the restore Data Protector still performs fast positioning because a file is located on the tape near the directory where it actually resides. This option is suitable for filesystems with many auto-generated files, such as news and mail systems.
Backup Using Backup Options When to Use Load It is recommended that you use the Load Balancing option when you Balancing want to back up a large number of objects to a number of available devices, and you would like Data Protector to keep all the devices busy all of the time. You should use Load Balancing to minimize the impact of unavailable devices on the backup.
Backup Using Backup Options • Objects that reside on the client connected to the backup device have a higher priority. • Objects are selected so that the number of Disk Agents per client is kept as low as possible. The size of objects does not play a role in assigning an object to a device. If a device becomes unavailable, the following happens: • All objects backed up to the device before the failure time are actually backed up.
Backup Using Backup Options • If load balancing is only selected in the template, the device options are applied only if the backup specification has no devices. For more information on failed backups, refer to “Managing Failed Backups” on page 263. Ownership: Who Will Be Able to Restore? Who Is a Backup Session Owner? A user who starts an interactive backup is the session owner. If a user starts an existing backup specification without modifying it, the backup session is not considered interactive.
Backup Using Backup Options Changing the owner works only for saved backup specifications. If the backup configuration is changed and not saved, the backup is treated as an interactive backup and the owner is not changed. This could result in a different kind of backup than expected. For example, if you interactively start an incremental backup and you are not the owner of the full backup, you will get another full backup instead of an incremental one.
Backup Using Backup Options Figure 5-30 Backup Specification Options - General and Other Available Backup Specification Options Description You can type in any text to describe the purpose or contents of the backup specification. This text has no effect on the backup session. Load Balancing If this option is set, Data Protector dynamically assigns backup objects to available devices. This means that devices are evenly used, and if one fails, a backup continues on other available devices.
Backup Using Backup Options • root on UNIX Cell Managers • the user specified at installation time on Windows Cell Managers The default value is not specified. See “Ownership: Who Will Be Able to Restore?” on page 235 for more information. You can change the session owner by using the following steps: 1. In the HP OpenView Storage Data Protector Manager, switch to the Backup context. 2. Double-click Backup Specifications, then right-click on the backup specification you want to modify. 3.
Backup Using Backup Options See “Pre- and Post- Exec Commands on Windows Systems” on page 251 for details of specifying post-exec commands on Windows. See “Pre- and Post- Exec Commands on UNIX Systems” on page 257 for details of specifying pre-exec commands on UNIX. See Appendix, “Examples of Pre-Exec and Post-Exec Commands for UNIX,” on page A-20 for some sample scripts on UNIX. Default value is not specified.
Backup Using Backup Options Figure 5-31 Filesystem Options Setting the Disk Image Options 1. Select the backup specification. 2. Select the Options property page. 3. Under Disk Image Options, click Advanced. 4. Click either the Options or the Other tab, and specify the options as desired. For a description of each option, click Help in the dialog box. NOTE On the Options tab, if specifying Pre- and/or Post- exec command names, you may or may not have to specify the full paths for the commands.
Backup Using Backup Options See “Pre- and Post- Exec Commands on Windows Systems” on page 251 for details of specifying pre-exec commands on Windows. See “Pre- and Post- Exec Commands on UNIX Systems” on page 257 for details of specifying pre-exec commands on UNIX. Figure 5-32 Disk Image Options 5. Click OK to confirm and exit the dialog box. Setting the Object Specific Options 1. Select the backup specification whose options you want to set. 2. Select the Backup Object Summary property page. 3.
Backup Using Backup Options Figure 5-33 Object Properties - General and Trees/Filters The Object Properties window for a UNIX filesystem contains the General, Options, Other, and the Trees/Filters tabs. Options and Other are the same as shown in Figure 5-31, while General and Trees/Filters are the same as in Figure 5-33, except that Object type is described as Filesystem [UNIX]. The Object Properties window for a disk image object contains the General, Options, Other, and the Disk Image Options tabs.
Backup Using Backup Options Figure 5-34 Object Properties - General and Disk Image Options 4. Set the options and click OK to confirm the selection. See below for details on a particular option. Allow Fallback (Windows-Specific Options) If the Use Shadow Copy option is specified, but the shadow copy creation on the system where the VSS filesystem backup is running fails, the backup also fails by default. However, you can avoid backup failure by specifying the Fallback to legacy option.
Backup Using Backup Options is made. In the second traverse, only one hard link is backed up with the file contents, while all the others are backed up as hard links. The first traverse also allows Data Protector to estimate the size of the backup. If set, Data Protector backs up the entire file contents for each hard link. Data Protector traverses the filesystem tree only once, thus significantly speeding up the backup process. Use this option when there are no hard links in your directory.
Backup Using Backup Options Encode Open Systems and public networking make data security in large enterprises essential. Data Protector lets you encode file and disk image data so that it becomes unreadable. Data is encoded before it is transferred over the network and written to the media. Data Protector uses a fixed, built-in algorithm for this purpose. The default value is OFF.
Backup Using Backup Options Open Files (Windows-Specific Option) This option controls what Data Protector does when it encounters open Windows files. If the Number of retries value is specified, this number defines how many times Data Protector tries to back up an open or busy file. The Time out value is the amount of time in seconds during which Data Protector waits before retrying to back up an open or busy file.
Backup Using Backup Options Report Open Locked Files As (Windows-Specific Option) This option sets the report level for files that are opened and locked at the time Data Protector attempts to back them up. Data Protector reports such files as per the regard to the Report Level setting. The default value is Warning. Software Compression Data Protector can compress data on a Disk Agent client before sending it to a Media Agent client. This feature is also known as software compression.
Backup Using Backup Options Use Shadow Copy (Windows-Specific Option) When performing filesystem backup on Windows Sever 2003 systems, Data Protector uses MS Volume Shadow Copy service (VSS) for coordinating the point-in-time backup. VSS allows you to create shadow copy backups of volumes and exact point-in-time copies of files, including all open files. This means that the VSS mechanism commits all pending I/O operations and holds incoming writing requests during the preparation of a shadow copy volume.
Backup Using Backup Options Device Backup Options You can select the options listed below for each backup device in use. None of the settings are needed, because CRC Check, Concurrency, and Media Pool use the default values that are set when the device is configured. The Prealloc List value is specified along with the media pool settings. CRC Check Set this option to have Data Protector calculate the CRC (Cyclic Redundancy Check) when a backup runs.
Backup Pre- and Post-Exec Commands Pre- and Post-Exec Commands Before a backup or restore session begins, an additional action is sometimes necessary. For example, you may want to check the number of files to back up, stop some transaction processing, or shut down a database. Such actions are performed using pre- and post-exec commands. Pre- and post-exec commands are not supplied by Data Protector. Depending on your needs, you have to write your own executables to perform the required actions.
Backup Pre- and Post-Exec Commands c. The post-exec (for each object in the backup specification) starts and completes. 3. The post-exec command for the entire backup specification starts and completes. Figure 5-36 Pre- and Post-Exec Control Flow Pre- and Post- Exec Commands on Windows Systems This section describes how to implement pre- and post-exec commands on Windows Cell Managers and clients. How to Write the Commands Pre- and post-exec commands can be written as executables or batch files.
Backup Pre- and Post-Exec Commands the filename. For scripts that are not located in the \bin directory, you must specify a full path name of the script. How to Specify the In the backup specification, click the Options tab. Under Backup Filename or Specification Options, click Advanced. Write the filename or Pathname pathname in the Pre-exec and/or Post-exec text box.
Backup Pre- and Post-Exec Commands RESTARTED Set to 1 if this is a restarted backup session, otherwise set to 0. The post-exec can use this variable to prevent an additional restart in the case that SMEXIT equals 0. SESSIONID Is used to identify a finished session and is recorded in the database. You cannot use this to preview a session (use SESSIONKEY). SESSIONKEY Is used to identify a running session. You may, for example, abort a backup session before it is started if something is wrong.
Backup Pre- and Post-Exec Commands ✓ The execution of pre- and post-exec commands is implemented using the Windows pipe mechanism. All processes started in the preor post-exec functions must finish before processing continues. ✓ A pre- or post-exec command must return a non-negative value upon successful completion. ✓ If a pre-exec command fails (returns a value less than 0), the status of the backup session is set to Failed and the session is aborted.
Backup Pre- and Post-Exec Commands Pre- and Post-Exec Commands for a Specific Backup Object Pre- and post-exec commands for an object are executed before and after the backup of the object, respectively. You can specify these commands for all objects in a backup specification, or for each individual object. When backing up integrations, for example Oracle, the database is considered as an object, so the commands are executed before and after the database backup.
Backup Pre- and Post-Exec Commands NOTE If you perform a host backup, the pre-exec script is started once, before the first filesystem backup for the particular system, while the post-exec script is started after the backup. In this case, BDACC cannot be exported because the variable is related to a single filesystem object, not to a whole client. Key Points ✓ The pre- and post-exec commands for a backup object have to be executable or batch files.
Backup Pre- and Post-Exec Commands ✓ Time-out is provided. If no message is received within the specified time-out in seconds, the session is aborted. ✓ You can disable a pre- and post-exec script by adding the line OB2OEXECOFF=1 in the omnirc file on any client. ✓ You can secure the client by specifying which Cell Managers are allowed to access the client. Only permitted Cell Managers will be able to execute pre- and post-exec commands on the client.
Backup Pre- and Post-Exec Commands How to Specify the For information on how to specify the commands, refer to the online Help Filename or index keyword “pre- and post-exec commands for backup specifications”. Pathname? Environment Variables The following environment variables are exported, and can be used in pre- and post-exec scripts for a backup specification session on any host: DATALIST The name of the backup specification.
Backup Pre- and Post-Exec Commands Key Points Check the following before configuring pre- and post- exec commands for a backup specification on a local or remote host: ✓ If a pre-exec command fails (returns a non-zero value), the backup status of the session is set to failed and the session is aborted. ✓ If a post-exec command fails (returns a non-zero value), the backup of the session is set to completed with errors.
Backup Pre- and Post-Exec Commands /opt/omni/lbin/utilns/detach pre_script [arguments...] • You can disable a session’s pre- and post-exec command execution on the Cell Manager by setting the SmDisableScript global option to 1. • You can disable remote session pre- and post-exec command execution on any client by adding OB2REXECOFF=1 into the omnirc file on the specific client. • You can secure the client by specifying which Cell Managers are allowed to access the client.
Backup Pre- and Post-Exec Commands Environment Variables The following environment variables are exported, and can be used in the pre- and post-exec scripts for an object on the system where the Disk Agent is running: BDACC The Disk Agent sets its exit code (0 is successful) to the BDACC environment variable. This variable can be checked in the post-exec script, thus making the post-exec command dependent on the successful termination of the Disk Agent.
Backup Pre- and Post-Exec Commands ✓ The pre- and post-exec processes operate in background mode. Therefore, do not use any interactive commands for the pre- and post-exec processing. ✓ If a command writes any text to stdout, this text is received by the Disk Agent, sent to the Session Manager, and written to the database. A stderr is redirected to /dev/null. You can redirect it to stdout to get error messages logged to the database.
Backup Managing Failed Backups Managing Failed Backups During a backup, some systems may not be available because they were shut down, there were some networking problems, or similar occurrences. This results in some systems not being backed up entirely. Setup Notification Data Protector lets you configure a notification so that you are informed about unexpected events, such as a mount request or a device error during a backup session.
Backup Managing Failed Backups The following example is a list of files that cannot be opened on an active Windows NT 4.0 system with the Windows NT software installed on the C: drive: <%SystemRoot%>\system32\config\default <%SystemRoot%>\system32\config\default.LOG <%SystemRoot%>\system32\config\SAM <%SystemRoot%>\system32\config\SAM.LOG <%SystemRoot%>\system32\config\SECURITY <%SystemRoot%>\system32\config\SECURITY.LOG <%SystemRoot%>\system32\config\software <%SystemRoot%>\system32\config\software.
Backup Managing Failed Backups If a backup of an object fails to start, Data Protector tries to back up this object again at the end of the backup session. If it fails again, the object is not backed up, and the status of the object and the session is set to Failed. A backup is repeated when it is scheduled. If some objects finish properly, the session status is completed with failures.
Backup Managing Failed Backups NOTE You can enable Wake ONLAN support for computers equipped with a Wake ONLAN-compatible LAN interface, such as the HP NightDIRECTOR series. The Wake ONLAN (WOL) option is available in the BIOS setup. When you install a Disk Agent on a Windows client and add it to a cell, the client’s Mac address is automatically discovered. You can also manually change the Mac address in the same section where you enable the Wake ONLAN (WOL) option, as shown below.
6 Restore Chapter 6 267
Restore In This Chapter In This Chapter This chapter describes restore topics, such as how to restore specific data and how to use restore options to achieve a desired restore behavior.
Restore Restoring Your Data Restoring Your Data A restore is a process that recreates the original data from a backup copy on a disk. This process consists of the preparation and actual restore of the data, and optionally some post-restore actions that make the data ready for use. Data Protector includes an internal database (IDB) that keeps track of data, including what files from which system are kept on a particular medium. The IDB provides fast and convenient access to the data to be restored.
Restore Restoring Your Data • The location you want to restore data to • The device to restore from • How to handle file conflicts with existing files • Restore options, such as locking files during restore For detailed steps of standard restore tasks, refer to the online Help index keyword “standard restore procedure”.
Restore Restoring Your Data Figure 6-1 Selecting Data for Restore Selecting a Backup Version When selecting data that you want to restore, the last backup version is selected by default. This means that only directories and/or files from the last backup session are selected for restore. Directories and files in the same tree structure that have not been backed up in the same backup session are shaded.
Restore Restoring Your Data possible options: Keep most recent, No overwrite, and Overwrite. For more information on these options, refer to “Restore Options” on page 294. Specifying Restore Location By default, Data Protector restores data to the same client and directory from which it was backed up. You can change these default settings in the Destination property page by specifying where to restore your data to: • With the appropriate user rights, you can restore to another client.
Restore Restoring Your Data NOTE With some database integrations, you can set the changed device as a default restore device for all Data Protector integration restore sessions (regardless of the type of integration), by clicking the Save as default button. Finding Needed Media To get a list of the media on which your data is stored, go to the Media property page after you select data for restore.
Restore Restoring Your Data Prerequisites You need to meet the following prerequisites in order to perform a disk image restore: • The disk must have been backed up using the disk image backup. • To restore a disk image on a disk other than the disk from which you backed it up, the new disk must be of the same size or larger. • On UNIX systems, unmount the disk before a disk image restore and then mount it back afterwards.
Restore Restoring Your Data Restoring Your Data to a Shared Disk Data Protector allows you to restore UNIX and Windows data to a Windows shared disk, even if the data was not originally backed up from the shared disk. The Data Protector user account and its Inet service must have permission to access the remote computer and permission on the Disk Agent client.
Restore Restoring UNIX Systems Restoring UNIX Systems What Is Restored? When restoring files to the original location from which the backup was performed, Data Protector restores the files, including file attributes. System-specific data, such as ACL (Access Control List) on UNIX, is restored only on the same filesystem type and operating system from which the backup was made. Restoring Regular Use the standard restore procedure to restore UNIX files and directories.
Restore Restoring Windows Systems Restoring Windows Systems What Is Restored? When restoring a Windows filesystem, Data Protector restores the data within the files and directories, as well as Windows-specific information about the files and directories. Consider the filesystem restore limitations when restoring to a different filesystem from the one where the backup was performed. See “Filesystem Limitations” on page 278.
Restore Restoring Windows Systems Filesystem Limitations You can select a different target filesystem from the one where the backup was performed. This functionality has limitations that should be taken into consideration. See Table 6-1. Table 6-1 Windows Filesystem Restore Limitations TO FROM FAT32 FAT16 CDFS UDF NTFS 1.1a NTFS 3.0b NTFS 3.1c FAT32 FC FC N/A N/A FC FC FC FAT16 FC FC N/A N/A FC FC FC CDFS FC FC N/A N/A FC FC FC UDF FC FC N/A N/A FC FC FC NTFS 1.
Restore Restoring Windows Systems Table 6-1 shows that NTFS 3.x filesystem objects can only be adequately restored to the NTFS 3.x filesystem. The filesystem-specific attributes and alternate data streams are lost when restoring into a different or older filesystem version. • A Windows 2000/XP/Server 2003 reparse point, such as a directory junction or a volume mountpoint, can only be restored to an NTFS 3.x filesystem. UNIX reparse points cannot be restored to an NTFS 3.x filesystem.
Restore Restoring Windows Systems Restoring Disk Images Refer to “Restoring Disk Images” on page 273. Restoring the Windows CONFIGURATION To restore the Windows CONFIGURATION, select the CONFIGURATION object and follow the standard restore procedure. See Figure 6-3. Figure 6-3 Restoring Windows CONFIGURATION Prerequisites The CONFIGURATION consists of data structures that influence system operation. Therefore, the system must be prepared for such a restore.
Restore Restoring Windows Systems • You have to boot the system in the Active Directory restore mode to restore the Active Directory. Refer to “Restoring Windows 2000/XP/Server 2003 Services” on page 283 for details. When the whole CONFIGURATION is restored, restart the system to read the restored data in the Registry. Refer to “Restoring the Windows Registry” on page 282 for details.
Restore Restoring Windows Systems 1. System State objects that belong to CONFIGURATION. Refer to “Backing Up the Windows 2000/XP/Server 2003 System State” on page 176 for a list of these objects. 2. The SystemVolumeInformation folder and the boot files. These are located on the system drive. Figure 6-4 Selecting System State Items NOTE From the Data Protector point of view, the System State consists of ordinary filesystem objects and CONFIGURATION objects.
Restore Restoring Windows Systems Once the restore session is completed, restart the system. NOTE If you select the whole Windows 2000/XP/Server 2003 Registry for a restore, some of the Registry keys are not restored, and others are treated in a special way during a restore. This is because certain keys are being used by the operating system.
Restore Restoring Windows Systems the local system account and then restart the services. Refer to “Setting the User Account for the Data Protector Inet Service” on page 187 for more details. Select Active Directory, and set a replication mode by choosing among the Windows 2000 specific options: Primary, Nonauthoritative, Authoritative. For information on these options, refer to “Active Directory Specific Options” on page 297. NOTE To perform an Authoritative restore, you also need to run ntdsutil.
Restore Restoring Windows Systems Remote Storage Service Restore Although the RSS databases are part of System State data, you restore them manually. The RSS database must be restored offline. You can provide pre- and post-exec scripts to stop and restart the service, or you can stop and restart it manually before and after the restore, respectively.
Restore Restoring Windows Systems 2. To keep the restored files unmerged, you can delete the files in the newly created profile before running a restore session. 3. Log off and start the restore session by logging on as a different user or by using another system. The system may assign a different name to the user. In this case, use the Restore As option to restore the files to the newly assigned location. When the restore has finished, restart the system.
Restore Restoring Novell Netware Filesystems Restoring Novell Netware Filesystems Use the standard restore procedure to restore Novell NetWare filesystems. Refer to “Standard Restore Procedure” on page 269. Restoring Namespace Information and Volume Space Restrictions To restore only volume space restrictions, specify the Volume space restrictions only restore option in the Destination page. The object selected for the restore must be a volume.
Restore Restoring Novell Netware Filesystems • You cannot restore Novell NetWare files that have been backed up in their compressed format to non-NetWare platforms. Restoring File Ownerships and Trustees Data Protector restores owner and trustee information on a per-file/directory basis. The owner and trustees of the file or directory are restored correctly if the relevant objects exist in the NDS database (Novell NetWare 4.X).
Restore Restoring Novell Netware Filesystems Figure 6-6 Restoring the NetWare Configuration Restoring Novell NDS Prerequisites The prerequisites for performing a successful restore are the same as for a backup of the NDS database. Data Protector restores NDS objects in the same way as Novell NetWare filesystem data, except in the following cases: • NDS objects cannot be restored to other Novell NetWare volumes.
Restore Restoring Novell Netware Filesystems For Novell NDS restore you can specify how to handle conflicts between the version currently on the disk and the backup version of a file. File Conflict Handling offers you three possible options: Keep most recent, No overwrite, and Overwrite. For more information on these options, refer to “Restore Options” on page 294. Restoring NDS Schema and NDS Objects Data Protector allows single NDS object restore.
Restore Restoring OpenVMS Filesystems Restoring OpenVMS Filesystems Use the standard restore procedure to restore OpenVMS filesystems. Refer to “Standard Restore Procedure” on page 269. What is Restored? The directory structure and the files are restored, together with the following filesystem information: • The directory and file attributes. • ACL (Access Control List) if available (see Limitations below). • Secondary file entries.
Restore Restoring OpenVMS Filesystems — File specifications for OpenVMS files are case insensitive. For example: An OpenVMS file specification of: $1$DGA100:[USERS.DOE]LOGIN.COM;1 must be specified in the form: /$1$DGA100/Users/Doe/Login.Com.1 • There is no implicit version number. You always have to specify a version number. Only file versions selected for the backup will be restored.
Restore Restoring OpenVMS Filesystems Files during Restore (-lock) option is enabled or disabled. • The default device and directory for pre- and post-exec command procedures is /omni$root/bin. To place the command procedure anywhere else the file specification must contain the device and directory path in UNIX style format: For example:/SYS$MANAGER/DP_SAVE1.COM • If the Restore Protection Attributes (-no_protection) option is disabled, the files are created with the default owner, protection and ACL.
Restore Restore Options Restore Options Data Protector offers a set of comprehensive restore options that allow fine-tuning of a restore. All these options have default values which are appropriate in most cases. Restore options depend on the data being restored. For example, restore options for a filesystem are different from those for a disk image restore. List of Restore Options The following list of restore options can be set for a particular object.
Restore Restore Options The time on the Cell Manager and clients must be synchronized for the Omit Deleted Files option to function properly. Move Busy Files This option is relevant if a file on the disk is being used by an application when a restore wants to replace this file. The option is used with the Keep most recent or Overwrite options. By default, this option is disabled. On UNIX systems, Data Protector moves the busy file filename to #filename (adds a hash in front of the filename).
Restore Restore Options Restore Sparse Files This option restores sparse files in their original compressed form. This is important because sparse files can consume additional disk space unless they are restored in their original form. By default, this option is disabled. This option applies to UNIX sparse files only. Windows sparse files are always restored as sparse. Lock Files During Restore This option denies access to files during the restore. By default, this option is disabled.
Restore Restore Options Post-Exec File Conflict Handling Options Active Directory Specific Options This option allows you to enter a command to be executed after the restore of each object is completed. The post-exec command is executed on the client system where the Disk Agent is running. On how to specify the command, refer to online Help. Keep Most Recent If this option is selected, the most recent versions of files are kept.
Restore Restore Options User Defined Restore Variables You can use variables (a variable name and its value) for flexible operations on some platforms and integrations with Data Protector. For detailed steps, refer to the online Help index keyword “setting user definable restore variables”.
Restore Restore Techniques Restore Techniques The following restore techniques apply to the UNIX and Windows platforms. Restoring Files to Different Paths By default, Data Protector restores data to the same client and directory from which it was backed up. You can restore your data to a different client system and directory. For individual files and directories, you can specify a different path and different name.
Restore Restore Techniques This capability is available for the initially selected tree node (directory) and for tree nodes that are not hierarchically dependent on any already selected tree nodes. A selected tree node is indicated by a blue check mark, and a dependent tree node is indicated by a black check mark. Restore Into appends the source path to the new one entered under Location. For example, if the colors.
Restore Restore Techniques Figure 6-8 Restoring Files in Parallel The figure shows an example of restoring files in parallel from one medium. Each object uses a different DA. How to Run a Parallel Restore Select the data that you want to restore to different disks and start the restore. Data Protector asks you if you want to perform a parallel or single restore. Choosing parallel restore enables multiple Data Protector Disk Agents to run in parallel.
Restore Restore Techniques • The catalog protection has expired. Refer to “Most Frequently Used Backup Options” on page 227 for more information about data and catalog protection. • The media are not from the same Data Protector cell and, as such, are not recognized in the IDB of the cell. In this case, you need to import it first. Prerequisite A large amount of memory on the Cell Manager is required.
Restore Restore Techniques Figure 6-9 Restore by Query To search for a file or a directory, you need to know at least a part of its name. The Restore by Query task enables you to search for files and directories backed up from a specific client system in a specified timeframe, or for files and directories with specific criteria (using wildcards: *, ?).
Restore Restore Techniques How to Restore by Start the Restore by Query task from the Restore context of the Data Query Protector Manager. Use the Tasks navigation tab. See Figure 6-9. For detailed steps, refer to the online Help index keyword “restore by query”. Skipping Files for Restore Data Protector allows you to skip certain files during restore. By using wildcards (* or ?), you can skip files matching specific criteria. For example, entering *.exe skips the files that end in .exe.
Restore Restore Techniques Figure 6-11 Matching Files for Restore Restoring Files and Directories Manually You need to restore a file or a directory manually when you can no longer browse for the file or directory. This happens when the catalog protection for your data has expired, or when backup was done using the No log option. Prerequisite To add a file or a directory manually, you need to know the exact path and the name of the file or the directory. The file and path names are case sensitive.
Restore Restore Techniques 306 Chapter 6
7 Monitoring, Reporting, Notifications, and the Event Log Chapter 7 307
Monitoring, Reporting, Notifications, and the Event Log In This Chapter In This Chapter This chapter consists of the following sections: “Monitoring Sessions” on page 309 “Monitoring Several Cells Simultaneously” on page 314 “Data Protector Reporting” on page 315 “Configuring Reports Using the Data Protector GUI” on page 335 “Running Reports and Report Groups Using the Command-Line Interface” on page 339 “Data Protector Notifications” on page 342 “Configuring Reports and Notifications on the Web” on page 3
Monitoring, Reporting, Notifications, and the Event Log Monitoring Sessions Monitoring Sessions Data Protector allows you to manage running sessions and to respond to mount requests. You can view the status of sessions, their type, owner, session ID, and start time, as well as the names of the corresponding backup specifications.
Monitoring, Reporting, Notifications, and the Event Log Monitoring Sessions The progress and status of current sessions appear in the Results Area. You can sort the sessions by clicking the column headings in the Results Area. TIP To view the details of a running session, double click the session. The detailed monitor view of the session appears. Viewing Finished Sessions As soon as a session is finished or is aborted, it is no longer displayed in the Data Protector GUI, Monitor context.
Monitoring, Reporting, Notifications, and the Event Log Monitoring Sessions 2. Insert the needed medium into the device. If you have a library device, it is not necessary to use the slot requested by the mount request. 3. In the Results Area, double-click the session with the mount request status to display details about the session. 4. Select the device with the mount request status. 5. In the Actions menu, click Confirm Mount Request. The status of the session and device changes to Running.
Monitoring, Reporting, Notifications, and the Event Log Monitoring Sessions You can sort your sessions using the buttons on the top of each of the columns. 4. Right-click on your failed session, and then select Restart Failed Object. 5. Click Yes to confirm. Aborting Running Sessions You can abort a session if you want to stop a backup, restore, or media management operation. A backup copy or restored data will exist only for data that was backed up or restored before you aborted the session. 1.
Monitoring, Reporting, Notifications, and the Event Log Monitoring Sessions See “Restore Options” on page 294 for information on which restore options affect your displayed messages.
Monitoring, Reporting, Notifications, and the Event Log Monitoring Several Cells Simultaneously Monitoring Several Cells Simultaneously You can monitor several cells at the same time using the Manager-of-Managers functionality. See Chapter 8, “Manager-of-Managers Environment,” on page 359 for more information.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Reporting Data Protector Reporting What Is Reporting? Data Protector reports provide various information on your backup environment. For example, you can check the status of the last backup, check which systems in your network are not configured for backup, check the status of devices, and more. Data Protector reporting represents a powerful, customizable, and flexible tool for managing and planning your backup environment.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Reporting If no optional input parameters (optional selections) are specified when configuring a report, a default value is set, which is in case of objects and in case of time frames.
Monitoring, Reporting, Notifications, and the Event Log Report Types Report Types Data Protector provides various types of reports, as shown in Table 7-1: Table 7-1 Backup Specifications Provides information on backups, such as average size of backed up objects, schedule of backups, filesystems not configured for backup, and so on. Configuration Provides information on the configuration of the Data Protector cell, on devices not configured for backup, on systems not configured for backup, and so on.
Monitoring, Reporting, Notifications, and the Event Log Report Types For supported formats, refer to “Report Formats” on page 329. Table 7-2 Backup Specification Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Trees in Backup Specification Lists all trees in the specified backup specification. It also shows names of drives and the name of a tree.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-2 Backup Specification Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Not Configured Filesystems Lists all disks (filesystems) that are not configured in any of the selected backup specifications.
Monitoring, Reporting, Notifications, and the Event Log Report Types Configuration Reports The following table lists the Configuration reports. Configuration reports provide information on the configuration of the Data Protector cell, devices, systems not configured for backup, and so on. For supported formats, refer to “Report Formats” on page 329.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-3 Configuration Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Client Backup Lists information about the specified clients such as: filesystems not configured, all objects, and all objects with a valid backup. Reports also list times and average sizes. Host Name none all formats host IDB Reports The following table lists the IDB reports.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-4 IDB Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Purge Preview Lists the following information: overall number of filenames in database (in thousands), estimated number of obsolete filenames in database (in thousands) and estimated duration of database purge (in seconds).
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-4 IDB Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats System Dynamics Lists for each Data Protector client in the cell: the number of filenames (in thousands) in the IDB, the number of active filenames (in thousands) in the IDB, the IDB filenames growing ratio (new filenames per day), the number of deleted filenames in the IDB per day, active growth per year, and a dyna
Monitoring, Reporting, Notifications, and the Event Log Report Types Pools and Media Reports The following table lists the Pools and Media reports. Pools and media reports provide information on media pools and used media. For supported formats, refer to “Report Formats” on page 329. Table 7-5 Pools and Media Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Extended List of Media Lists all media matching the specified search criteria.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-5 Pools and Media Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Media Statistics Reports the statistics on the media matching the search criteria. The following information is provided: number of media; number of scratch media; number of protected, good, fair and poor media; number of appendable media; and total, used, and free space on media.
Monitoring, Reporting, Notifications, and the Event Log Report Types Number of remaining days in which the data protection will expire, counted from the moment of starting the report / Never 2. Timeframe in which the medium was used for a backup. Relative time: the first parameter sets the starting point of the timeframe (number of hours counted from the moment of starting the report backwards), the second parameter sets the end point of the timeframe (number of hours counted from the starting point).
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-6 Sessions in Timeframe Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Device Flow Graphically presents the usage of each medium. A flow chart of the backup sessions matching the search criteria is shown. TimeFrame1 • Backup HTML Lists media that have been used during the backup sessions in the specified timeframe, together with their statistics.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-6 Sessions in Timeframe Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Extended Report on Used Media Provides extended information about all media that were used in the selected session. TimeFrame1 • Backup all formats used_media _extended Specifications • Backup Specification Group 1. Timeframe in which the medium was used for a backup.
Monitoring, Reporting, Notifications, and the Event Log Report Types Table 7-7 Single Session Reports Report and omnirpt Option Description Required Selections Optional Selections Supported Formats Session per Client Provides information about each client that took part in the selected session. Using the Generate multiple reports option, this report can be split into smaller reports, one for each client.
Monitoring, Reporting, Notifications, and the Event Log Report Types IMPORTANT TIP When sending an HTML report on a Windows Cell Manager using the email send method, how the report is displayed will depend on the email client used to open it. Many email clients will display the report as plain ASCII text. To ensure the report displays correctly as HTML, open it in a Web browser. Short A report is generated as plain text, but in a short, summary form, showing the most important information.
Monitoring, Reporting, Notifications, and the Event Log Report Send Methods Report Send Methods Report Send Methods Reports can be sent using various methods: • Email send method • Broadcast message send method • SNMP send method • External send method • Log to file send method The following sections describe specifics of each method. Email Send Method The email send method allows you to send or receive an email with the output of the report.
Monitoring, Reporting, Notifications, and the Event Log Report Send Methods 5. In the information services list, select Microsoft Exchange Server. 6. Click Next to display the Profiles page. 7. In the Profile Name text box, enter OmniBack, and then click Next. The Microsoft Exchange Server page appears. 8. In the Microsoft Exchange Server text box, enter the name of the server. 9. In the Mailbox text box, enter the name that you want to appear in email messages.
Monitoring, Reporting, Notifications, and the Event Log Report Send Methods NOTE On a UNIX Cell Manager, SNMP traps are sent to the systems configured in the notification. On a Windows Cell Manager, SNMP traps are sent to the systems configured in the Windows SNMP traps configuration. Windows NT To configure Windows NT SNMP traps, proceed as follows: 1. On the Cell Manager, click Control Panel, Network, and then Services.
Monitoring, Reporting, Notifications, and the Event Log Report Send Methods 6. Right-click SNMP Service and select Properties. a. Select the Traps tab and enter public in the Community name text box and the hostname of the VPO Management Server in the Trap Destinations text box. b. Select the Security tab. Under Accepted community names, select the community public, click Edit and set Community rights to READ CREATE. c. Confirm your settings. 7. Start omnisnmp.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports Using the Data Protector GUI Configuring Reports Using the Data Protector GUI This section describes how to configure Data Protector reports using the Data Protector GUI. NOTE To display the input parameters (selections) in the output of a report, select the Show selection criteria in report option in the Report Wizard.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports Using the Data Protector GUI Administrators can configure a report group and add a separate report for each of the requirements. They can schedule the report group to be executed early enough in the morning, so that all recipients receive the reports before coming to work. NOTE The Mount Request Report and Device Error Report can only be used in a report group and are not available as interactive reports.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports Using the Data Protector GUI NOTE To trigger a report group by a notification, you first need to configure a report group and then configure the notification to use the Use Report Group send method. 4. The report group is created and displayed in the Scoping Pane. 5. To add multiple reports to the group, right-click the group and then select Add Report.
Monitoring, Reporting, Notifications, and the Event Log Running Reports and Report Groups Using the Data Protector GUI Running Reports and Report Groups Using the Data Protector GUI Data Protector reports can be run individually, or they can be grouped into report groups and then run. Running Individual Reports To run each report individually, do the following: 1. In the Data Protector Manager, switch to the Reporting context. 2. Click the Tasks tab below the Scoping Pane to switch to the tasks context.
Monitoring, Reporting, Notifications, and the Event Log Running Reports and Report Groups Using the Command-Line Interface Running Reports and Report Groups Using the Command-Line Interface Data Protector reports can be generated using the command-line interface. The command-line interface allows you to include Data Protector reports in some other configuration scripts you are using. It allows you to generate individual reports, run report groups, and define report formats and send methods.
Monitoring, Reporting, Notifications, and the Event Log Running Reports and Report Groups Using the Command-Line Interface omnirpt -report session_flow -timeframe 24 24 -log session_flow.html -html Figure 7-1 A Session Flow Report Example 2 The following command creates a Media Statistics Report on media in poor condition and logs it in the file in the ASCII format, as shown in Figure 7-2 on page 340: omnirpt -report media_statistics -status poor -log media_statistics.
Monitoring, Reporting, Notifications, and the Event Log Running Reports and Report Groups Using the Command-Line Interface omnirpt -report device_flow -timeframe 24 24 -email ulmo@outersea.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications Data Protector Notifications What Are Notifications? The Data Protector notification functionality allows you to receive notifications when specific events occur. For example, when a backup session is completed, you can receive an email with a status of the session. You can set up a notification so that it triggers a report.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications ✓ End of Session ✓ Mail Slots Full ✓ Mount Request • Notifications that are scheduled and started by the Data Protector checking and maintenance mechanism: ✓ Database Purge Needed ✓ Database Space Low ✓ Health Check Failed ✓ License Will Expire ✓ Not Enough Free Media ✓ Unexpected Events ✓ User Check Failed For more information on the Data Protector checking and maintenance mechanism, refer to “Data Protector Checking and M
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications Table 7-8 Data Protector Notifications Name Optional Input Parameters Default Message Level and Optional Input Parameter Default Values Message Displayed Unexpected Events Number of Events (threshold value for the number of events in the Data Protector Event Log that triggers this notification) • Warning Data Protector Event log increased for unexpected events in last day Health Check Failed non
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications Table 7-8 Data Protector Notifications Name Optional Input Parameters Default Message Level and Optional Input Parameter Default Values Message Displayed Database Purge Needed • Days Last • Warning Filename purge should be run for Internal Database Purge [days]) • Num. Estimated Filenames [mio] • Estimated • 180 days • 6 million • 120 minutes • 100 million Time Purge [min] • Num.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications Explanation of Some Notifications Alarm The Alarm notification is used to display critical Data Protector messages triggered by Data Protector internal conditions.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications For more information on the Data Protector checking and maintenance mechanism, refer to “Data Protector Checking and Maintenance Mechanism” on page 605. Health Check Failed As a part of the Data Protector checking and maintenance mechanism, Data Protector will by default once per day start the Health Check, which starts the omnihealthcheck command and triggers the notification if the omnihealthcheck command fails.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications • Broadcast message send method • SNMP send method • External send method • Log to file send method • Use Report Group send method • Data Protector Event Log send method NOTE By default, all notifications are configured to be sent to the Data Protector Event Log. In order to send an additional notification using some other send method, an additional notification has to be configured.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications 7. In the Profile Name text box, enter OmniBack, and then click Next. The Microsoft Exchange Server page appears. 8. In the Microsoft Exchange Server text box, enter the name of the server. 9. In the Mailbox text box, enter the name that you want to appear in email messages. This is usually Data Protector or the administrator’s name. 10. The remaining information is optional.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications Windows NT To configure Windows NT SNMP traps, proceed as follows: 1. On the Cell Manager, open Control Panel, Network, Services. If there is no SNMP Service entry in the list of network services under the Services tab, perform step 2. If there is, skip step 2. 2. Click Add and select SNMP Service. Click OK. Insert the Windows NT installation CD, or provide an alternative path to the requested files. Click Continue. 3.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications 7. Start omnisnmp. External Send Method External script notification allows you to process the output of the report in your own script. The script receives the output as standard input (STDIN). The recommended format for script processing is the tab format.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Notifications TIP To trigger a report group by a notification, configure a report group and then configure the notification to use the Use Report Group send method. 4. The notification is created and displayed in the Scoping Pane.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports and Notifications on the Web Configuring Reports and Notifications on the Web You can use your Web browser to view Data Protector reports and notifications. Using the web reporting and notifications interface, you can view, configure, and start Data Protector reports and notifications from any system on your network. You can configure reports and notifications that are delivered using various reporting methods and formats.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports and Notifications on the Web 3. Optionally, configure a password to limit access to Web reports. The steps are described below. Copying Data Protector Java Programs to the Web Server To allow access to Data Protector Web reporting and notifications interface from a browser from any system, copy Data Protector Java reporting programs to the web server.
Monitoring, Reporting, Notifications, and the Event Log Configuring Reports and Notifications on the Web Generating the Reports To generate reports using the Data Protector Web reporting and notifications interface, you have to access this interface. The actual steps depend on your configuration. Once you are logged on the Cell Manager, you can generate various types of reports. See “Data Protector Reporting” on page 315 for more information on report types.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Event Log Data Protector Event Log The Data Protector Event Log represents a centralized event management mechanism, dealing with specific events that occurred during the Data Protector operation. The events are logged in the \log\Ob2EventLog.txt (Windows systems) or in the /var/opt/omni/log/Ob2EventLog.txt (HP-UX and Solaris systems) file on the Cell Manager.
Monitoring, Reporting, Notifications, and the Event Log Data Protector Event Log When the Data Protector graphical user interface is started by a user, if there are new notifications that have not been seen by this user in the Data Protector Event Log, the following message is displayed: Figure 7-4 The Event Log Message Chapter 7 357
Monitoring, Reporting, Notifications, and the Event Log Data Protector Event Log 358 Chapter 7
8 Manager-of-Managers Environment Chapter 8 359
Manager-of-Managers Environment In This Chapter In This Chapter This chapter shows you how to configure and use the Data Protector Manager-of-Managers, which is used to control an enterprise backup environment.
Manager-of-Managers Environment Manager-of-Managers Manager-of-Managers The Data Protector Manager-of-Managers (MoM) allows administrators to centrally manage a large environment consisting of several Data Protector cells, also known as MoM clients, from a single point. Refer to the HP OpenView Storage Data Protector Concepts Guide for further details about the enterprise environment. NOTE Each MoM client and the MoM Manager need to run the same version of Data Protector.
Manager-of-Managers Environment Configuring the Manager-of-Managers Configuring the Manager-of-Managers To configure the MoM environment, you need to do the following: • Set up the MoM Manager. See “Setting Up MoM Manager” on page 363. • Import Data Protector cells into MoM environment. See “Importing Data Protector Cells” on page 363. • Create a Data Protector user in the Admin user group on every cell in the environment (MoM administrator). See “Adding a MoM Administrator” on page 364.
Manager-of-Managers Environment Configuring the Manager-of-Managers Setting Up MoM Manager To set up an enterprise environment, configure one of your Cell Managers as a MoM Manager. 1. In the Data Protector Manager, click Clients in the Context List. 2. In the Actions menu, click Configure CM as Manager-of-Managers Server. 3. Stop and restart Data Protector services. Refer to the section “Restarting Data Protector Services” on page 364.
Manager-of-Managers Environment Configuring the Manager-of-Managers 3. Enter, or browse for, the name of the Cell Manager that you want to import, and then click Finish. The selected Cell Manager is now a part of your MoM environment. NOTE If you are adding a Cell Manager installed on a cluster to the MoM cell, ensure that you enter its virtual server name. Adding a MoM Administrator A MoM administrator can perform administration tasks in all cells in the enterprise environment.
Manager-of-Managers Environment Configuring the Manager-of-Managers cmhaltpkg where is the name of the Data Protector cluster package. 2.
Manager-of-Managers Environment Centralized Media Management Database (CMMDB) Centralized Media Management Database (CMMDB) The IDB is an embedded database that keeps information about backup, restore, and media management sessions, devices, and media. It consists of five parts that are located on the Cell Manager.
Manager-of-Managers Environment Centralized Media Management Database (CMMDB) NOTE A backup anywhere in the enterprise environment will not run if the cell running the backup does not have access to the CMMDB. For example, this happens if a network failure occurs between the cell and the MoM cell.
Manager-of-Managers Environment Configuring a Centralized Media Management Database Configuring a Centralized Media Management Database It is not required to set up a Centralized Media Management Database (CMMDB). If you do not set up a CMMDB, Data Protector will work in a multi-cell environment, but each cell will have its own IDB. See “Centralized Media Management Database (CMMDB)” on page 366 for more information on this functionality.
Manager-of-Managers Environment Configuring a Centralized Media Management Database On the MoM, add one cell at a time to the CMMDB. Prerequisites • Data Protector Cell Managers in all cells have to have the same version of Data Protector installed and running. • Check that there are no backup, restore, or media management sessions running on any of the cells to be added to the multi-cell environment.
Manager-of-Managers Environment Configuring a Centralized Media Management Database TIP If you are configuring a new cell, (and you do not yet have devices and media configured) there is no need to merge the database. You only want to merge cells with the CMMDB that already have devices and media configured. 3.
Manager-of-Managers Environment Configuring a Centralized Media Management Database • On Windows: \bin\omnicc -update_mom_server • On UNIX: /opt/omni/bin/omnicc -update_mom_server Chapter 8 371
Manager-of-Managers Environment Centralized Licensing Centralized Licensing It is not required to set up centralized licensing. Individual licenses can be installed on each Cell Manager. Without centralized licensing, these individual licenses are restricted to the cell on which they are installed, and all licensing administration tasks have to be performed locally. NOTE If you have clusters configured in the MoM cell, make sure you identify a cluster client with its virtual hostname.
Manager-of-Managers Environment Centralized Licensing On Windows: \config\cell\lic_server On UNIX: /etc/opt/omni/cell/lic_server 3. Stop and restart Data Protector services on each Cell Manager where you made the changes. See “Restarting Data Protector Services” on page 364. 4. In the Data Protector Manager-of-Managers, click Clients in the Context List. 5.
Manager-of-Managers Environment Centralized Licensing NOTE Data Protector checks the license configuration with the MoM Manager every hour. The licensing status is kept for 72 hours. In case of a communication problem, after this 72 hour period, local licenses are used.
Manager-of-Managers Environment Centralized Licensing Moving Licenses in the MoM Environment If you have not configured centralized licensing, you cannot move licenses between cells without the approval of the HP Password Delivery Center. This is, however, possible in the MoM environment with configured centralized licensing, where the MoM administrator allocates licenses as needed. In the example below, assume that the clients from one cell were moved to another.
Manager-of-Managers Environment Centralized Licensing Deactivating Centralized Licensing Centralized licensing can be deactivated and changed back to local licensing. Deactivation Procedure 1. In the Data Protector Manager-of-Managers, click Clients in the Context List. 2. In the Scoping Pane, right-click the Cell Manager for which you want to deactivate centralized licensing, then click Configure Licensing to open the wizard.
Manager-of-Managers Environment Working with a MoM Environment Working with a MoM Environment The Manager-of-Managers interface enables you to configure, manage, and control an enterprise backup environment from a single point. In the MoM user interface, you can import and export cells, move clients among cells, and distribute the MoM configuration to other cells in the environment. Other tasks are performed on the MoM Manager in the same way as if you were a local administrator.
Manager-of-Managers Environment Working with a MoM Environment Moving Client Systems Among Cells Data Protector allows you to move systems among cells. During the process, Data Protector: • Checks whether the system to be moved is configured in any backup specification and leads you through the steps to reconfigure the backup of this system in the new cell. • Checks whether there are any devices configured on the system and leads you through the steps to move devices to another system.
Manager-of-Managers Environment Working with a MoM Environment Configuring Data Protector Users You can add users or user groups to a MoM environment as you would for a single Cell Manager. This procedure updates all Cell Managers with the new users. See Chapter 3, “Configuring Users and User Groups,” on page 81 for more information about users and user groups. To configure Data Protector users or user groups, follow these steps: 1.
Manager-of-Managers Environment Restoring, Monitoring, and Reporting in an Enterprise Environment Restoring, Monitoring, and Reporting in an Enterprise Environment Restoring data in an enterprise environment is the same as restoring data in a single cell environment. Select data from the appropriate source and restore as described in Chapter 6, “Restore,” on page 267. Data Protector allows you to monitor currently running or previously run sessions for any cell in the enterprise environment.
9 Managing the Data Protector Internal Database Chapter 9 381
Managing the Data Protector Internal Database In This Chapter In This Chapter This chapter provides information about the Data Protector internal database (IDB) and tasks related to managing the database.
Managing the Data Protector Internal Database About the Data Protector Internal Database About the Data Protector Internal Database What Is the Data Protector Internal Database (IDB)? The Data Protector internal database (IDB) is an embedded database, located on the Cell Manager, which keeps information regarding what data is backed up; on which media it resides; the result of backup, restore, and media management sessions; and what devices and libraries are configured.
Managing the Data Protector Internal Database The IDB Architecture The IDB Architecture The IDB consists of the following parts: • MMDB (Media Management Database) • CDB (Catalog Database) • DCBF (Detail Catalog Binary Files) • SMBF (Session Messages Binary Files) • SIBF (Serverless Integrations Binary Files).
Managing the Data Protector Internal Database The IDB Architecture Figure 9-1 IDB Architecture Each of the IDB parts stores specific Data Protector information (records), influences the IDB size and growth in different ways, and is located in a separate directory on the Cell Manager. MMDB The Media Management Database stores information about the following: • Configured devices, libraries, library drives, and slots. • Data Protector media used for backup. • Configured media pools and media magazines.
Managing the Data Protector Internal Database The IDB Architecture • Backup sessions and restore sessions. This is the copy of the information sent to the Data Protector Monitor window. • Backed up objects and their versions. • Pathnames of backed up files (filenames) together with client system names. Filenames are stored only once per client system. The filenames created between backups are added to the CDB. • Positions of backed up objects on media.
Managing the Data Protector Internal Database The IDB Architecture For additional information on each of the IDB parts, refer to the HP OpenView Storage Data Protector Concepts Guide.
Managing the Data Protector Internal Database Configuring the IDB Configuring the IDB The IDB configuration helps to manage the following: • the size of the IDB and available disk space • the location of the IDB directories • transaction log usage • the IDB backup necessary in case of IDB corruption or a disaster • configuration of the IDB reports and notifications Once the IDB is configured, it should be maintained only when you are notified about the need.
Managing the Data Protector Internal Database Configuring the IDB • You need to estimate future IDB size (disk space necessary for future IDB needs). Refer to the HP OpenView Storage Data Protector Concepts Guide for the IDB size estimation. How Much Disk Space Is Needed? The disk space needed to accommodate the IDB varies significantly as a function of many configuration aspects and policies used in defining and operating backups.
Managing the Data Protector Internal Database Configuring the IDB • The filenames part of the IDB is proportional to the total number of filenames in the cell (but not the data volume and the number of backups). Typically the filename growth is moderate, with the exception of some mail servers or other systems with a large amount of automatically generated files. • The file versions part of the IDB grows with the number of backups, the number of files in the cell, and the duration of the catalog protection.
Managing the Data Protector Internal Database Configuring the IDB • The DCBF and SMBF parts of the IDB are not required for basic operation of Data Protector, such as backup and restore. However, if they are not present, restore becomes less convenient (no filename browsing) and the session messages are lost.
Managing the Data Protector Internal Database Configuring the IDB • If the IDB is installed in a cluster, it must be installed on disks in the cluster group (Microsoft Cluster Server) or cluster package (MC/ServiceGuard).
Managing the Data Protector Internal Database Configuring the IDB Figure 9-2 Recommended Location of IDB Directories Relocating the IDB Directories You can change the location of any of the following IDB directories: the • datafiles directory, containing CDB (objects, positions, and filenames) and MMDB parts of the IDB • the logfiles directory, containing transaction logs and the IDB recovery file • the dcbf directory, containing the DCBF part of the IDB • the msg directory, containing the SMBF part of th
Managing the Data Protector Internal Database Configuring the IDB NOTE On UNIX, you can use symbolic links to relocate the directories, but the links are not allowed beneath the /var/opt/omni/db40/datafiles directory. Follow the described below to relocate the IDB directories: 1.
Managing the Data Protector Internal Database Configuring the IDB • On UNIX: /opt/omni/sbin/omnisv -start If the IDB is installed on MC/ServiceGuard, run the cmrunpkg command on the active node to start the Data Protector package. Creating an Additional Copy of the IDB Recovery File Creating an additional copy of the IDB recovery file prevents you from losing important data for IDB recovery. Use the following steps to make another copy of the IDB recovery file: 1.
Managing the Data Protector Internal Database Configuring the IDB Creating or Relocating DC Directories Creating a DC Directory Create a DC directory using the Database context in the Data Protector Manager. See Figure 9-3. For detailed steps, refer to the online Help index keyword “creating DC directories”. Relocating a DC Directory To change the location of a DC directory, proceed as follows: 1. Create a new DC directory on a new location, using the Data Protector user interface. See Figure 9-3. 2.
Managing the Data Protector Internal Database Configuring the IDB By default, transaction logging is disabled. If enabled, transaction logs from the latest IDB backup are kept until the next backup. If a transaction log file reaches 2 MB, a new one is created. An IDB backup removes all existing transaction logs, except for the currently active one, and starts to create new ones.
Managing the Data Protector Internal Database Configuring the IDB • On Windows: \bin\omnisv -start • On UNIX: /opt/omni/sbin/omnisv -start Configuring the Database Backup An essential part in the IDB configuration is to configure the backup of the IDB itself. Once the IDB backup is performed regularly, the most important preparation for recovery in case of a disaster is done. The IDB recovery is essential for restore of other backed up data in the event that the Cell Manager crashes.
Managing the Data Protector Internal Database Configuring the IDB • Perform the IDB backup using a separate media pool on separate media, on a specific device. Make sure you know which media you use for the IDB backup. You can configure a Session Media Report to be informed about the media used for the backup. This greatly simplifies eventual restore. If possible, use a device locally connected to the Cell Manager. Refer to “Data Protector Reporting” on page 315.
Managing the Data Protector Internal Database Configuring the IDB In environments where the Cell Manager is used heavily and the time needed to perform the check of the IDB creates a problem, you may need to disable the Check Internal database option. In such cases, consider the following suggestions: • Schedule the IDB backup with the IDB check option enabled to be performed when the automatic check activity is acceptable. • Schedule the daily IDB backup with the IDB check option disabled.
Managing the Data Protector Internal Database Configuring the IDB IDB Size Report Lists the sizes of the individual parts of the IDB. There are also other Data Protector reports to be considered. For example, the List of Sessions report shows the number of files backed up in one session. Refer to “Data Protector Reporting” on page 315 for more information. IDB Notifications The following list presents IDB notifications: Low Database Space Informs you if the IDB is running out of space.
Managing the Data Protector Internal Database Maintaining the IDB Maintaining the IDB Once you have configured the IDB, you need to perform IDB maintenance tasks in the following cases: • the IDB is running out of space If configured, the Low Database Space notification informs you about this. • the IDB needs a file version purge With the OmniBack II A.03.50/A.03.51 and earlier databases, the level of the granularity of the purge was at the object level.
Managing the Data Protector Internal Database Maintaining the IDB The Database Corrupted notification informs you about IDB corruption. Refer to Table 9-3 for information on which of the maintenance tasks you can perform in which cases.
Managing the Data Protector Internal Database Maintaining the IDB Table 9-3 IDB Maintenance Tasks Situation Which Task Can You Perform? Reference The IDB is running out of space • Extend the size of the IDB • “Extending the Database Size” on page 408 • Purge the IDB filenames • Reduce the growth of the IDB • Reduce the current size of the IDB • “Purging Obsolete Filenames” on page 408 • “Reducing the IDB Growth” on page 405 • “Reducing the IDB Size” on page 406 Obsolete filenames in the IDB • Pur
Managing the Data Protector Internal Database Maintaining the IDB Reducing the IDB Growth You can reduce the growth of the IDB by reducing the logging level and catalog protection settings of your backup specifications. These actions do not influence the current size of the IDB, but they do influence its future growth. The effect of reducing the logging level is a reduction in browse comfort at restore time.
Managing the Data Protector Internal Database Maintaining the IDB Figure 9-6 Changing Logging Level and Catalog Protection Settings Reducing the IDB Size You can reduce the IDB size by changing the catalog protection settings for a complete backup session (all objects in the session) or for specific objects only. The effect of reducing the catalog protection is that browsing is not possible for some restores (namely of those backups that have exceeded the catalog protection).
Managing the Data Protector Internal Database Maintaining the IDB By changing the catalog protection, you change protection in the IDB only. The information is still stored on media. Therefore, if you export media and import it back, Data Protector rereads information about catalog protection from the media. How to Reduce the Change the logging level and catalog protection settings using the IDB Size Internal Database context in the Data Protector Manager. See Figure 9-7 and Figure 9-8.
Managing the Data Protector Internal Database Maintaining the IDB Purging Obsolete Filenames During the purge process, Data Protector automatically checks for and purges obsolete filenames from the IDB to free up space for new information. A filename becomes obsolete when there are no file versions for the filename in the IDB. Use the Internal Database Purge Preview Report and Internal Database Purge Report to get more information about the purge.
Managing the Data Protector Internal Database Maintaining the IDB Creating New fnames.dat Files What Are fnames.dat Files? The fnames.dat files contain information on the names of backed up files. Typically, these files occupy about 20% of the IDB. The default size of a fnames.dat file is 2 GB; the maximum size is 32 GB. How to Create fnames.dat Files You add new fnames.dat files using the Internal Database context in the Data Protector Manager. See Figure 9-9.
Managing the Data Protector Internal Database Maintaining the IDB Checking the Database Size You can check the current size of the IDB parts using the Data Protector GUI. Also, if configured, the Database Size Report and Low Database Size notifications report on the IDB size. How to Check IDB Size Check the size of the IDB parts, CDB, MMDB, DCBF, SMBF, and SIBF using the Internal Database context in the Data Protector Manager. See Figure 9-10.
Managing the Data Protector Internal Database Maintaining the IDB Checking the Consistency of the Database Data Protector by default checks the consistency of the IDB before the IDB is backed up. This is extremely important for recovering the IDB and backed up data in case of a disaster. Additionally, you can manually perform the following IDB checks: Check of the core part of the IDB Checks the MMDB (Media Management Database) and CDB (Catalog Database) parts without information about filenames.
Managing the Data Protector Internal Database Maintaining the IDB Extended check Checks the critical part (MMDB and CDB), filenames, the DCBF part, and the DC part. To perform it, run the omnidbcheck -extended command. If you run into problems using the IDB, refer to the troubleshooting section “Troubleshooting the IDB” on page 592 and “Recovering the IDB” on page 417.
Managing the Data Protector Internal Database Maintaining the IDB On Windows systems: \db40\msg to \db40\msg On UNIX systems: /var/opt/omni/db40/msg to /var/opt/omni/db40/msg • SIBF files to the same relative pathname: On Windows systems: \db40\meta to \db40\meta On UNIX systems: /var/opt/omni/db40/meta to /var/opt/omni/db40/meta • DC directories to the same or other locations.
Managing the Data Protector Internal Database Restoring the IDB Restoring the IDB If you have backed up the IDB using the standard procedure, you can restore it using the methods described in this section. For a detailed description of how to handle the IDB recovery in case of a disaster, refer to “Recovering the IDB” on page 417. Restoring the IDB consists of two phases: 1. Restoring the IDB to a temporary location. IMPORTANT This step is necessary because the IDB is in use during the restore.
Managing the Data Protector Internal Database Restoring the IDB NOTE You should not select the directory, as this directory is the original location of the IDB. If you want to restore to a different system, specify the new Cell Manager’s name. 6. Click Restore. Moving the IDB to the Original Location After you have restored the IDB to a temporary location, you need to move the IDB directories to their original location. Proceed as follows: On an UNIX Cell Manager 1.
Managing the Data Protector Internal Database Restoring the IDB 3. Move the existing IDB directories (db40 and config) from the directory. This prevents merging of old and new files. 4. Copy the IDB directories from the temporary directory to the original directory . If your extension files were located on some other directory, be sure to copy them to the original disk and directory as well. 5.
Managing the Data Protector Internal Database Recovering the IDB Recovering the IDB When Is Recovery Needed? IDB recovery is needed if all or some of the IDB files are not available or are corrupted. There are three levels of IDB issues, each with its own techniques for repair: • Troubleshoot the IDB problems that are caused by OS configuration issues, such as not mounted filesystems, nameservice problems, and so on. Refer to the troubleshooting section “Troubleshooting the IDB” on page 592.
Managing the Data Protector Internal Database Recovering the IDB The Most Convenient Complete Recovery When the complete IDB is missing or the core part is corrupted, the corruption level is critical. If the IDB recovery file and the original device used for the IDB backup are available, you can perform the Guided Autorecovery (IDB Restore and Replay Logs). Refer to “Performing Guided Autorecovery” on page 421. Otherwise, follow one of the methods given under “More Recovery Methods” on page 418.
Managing the Data Protector Internal Database Recovering the IDB Table 9-4 Restoring the IDB Current situation Remark Recovery Procedure The IDB recovery file is not available. The method is essentially the same as the guided autorecovery method, but less guided, and more complex and time consuming. “Recovering the IDB Without the IDB Recovery File” on page 426. You want to recover the IDB from a specific IDB backup (not the latest one).
Managing the Data Protector Internal Database Recovering the IDB You can use the IDB consistency check to determine which part of the IDB is corrupted. Depending on the level of corruption, the IDB recovery procedure differs. Figure 9-11 IDB Corruption Levels How to Identify the Identify the level of IDB corruption using the omnidbcheck -extended Corruption Level command: NOTE The extended check may take several hours.
Managing the Data Protector Internal Database Recovering the IDB Performing Guided Autorecovery Guided autorecovery is the most convenient IDB recovery method. You can perform it if the IDB recovery file and the original device used for the IDB backup together with the IDB backup medium are available. This method guides you through restoring the IDB and replaying transaction logs since the last IDB backup.
Managing the Data Protector Internal Database Recovering the IDB • If the IDB is installed on Microsoft Cluster Server, take the OBVS_VELOCIS cluster group offline using the Cluster Administrator utility on the active node before performing the guided autorecovery. When the guided autorecovery has finished, bring the OBVS_VELOCIS and OBVS_MCRS cluster groups online using the Cluster Administrator utility. Recovery Procedure To recover the IDB, run the omnidbrestore -autorecover command.
Managing the Data Protector Internal Database Recovering the IDB label and media pool. 2. Run the omnidbutil -fixmpos command to establish consistency between media positions (mpos) and binary files. 3. Import the catalog from the media to recreate the binary files. Refer to “Importing the Catalog from Media” on page 114. Recovering if DC Binary Files Are Corrupted If some DC binary files are corrupted, you can remove the DC binary files and recreate them.
Managing the Data Protector Internal Database Recovering the IDB • The catalogs created by subsequent backups are good enough. • There is no IDB backup available. Recovery Procedure Proceed as follows: 1. Run the command: omnidbutil -writedb -no_detail -cdb -mmdb to write the IDB without detail catalogs to ASCII files. 2. Run the command: omnidbutil -readdb -cdb -mmdb to read the IDB from the ASCII files. The operation lasts approximately 5-20 minutes.
Managing the Data Protector Internal Database Recovering the IDB • Verify that Data Protector is installed on the Cell Manager and the system where a device is attached (preferably, the device used for the IDB backup). • If the IDB is installed on MC/ServiceGuard, run the cmhaltpkg command on the active node before performing the guided autorecovery, to stop the Data Protector package.
Managing the Data Protector Internal Database Recovering the IDB -dev scsi0:0:0:0 -mahost goedl.hermes -maid 0100007f:3a486bd7:0410:0001 -position 3:0 -daid 977824764 2. Modify the restjob.txt file to specify the current device or the slot in which the media are currently located. For example, if the DDS drive that had the SCSI address scsi0:0:0:0 at backup time has the SCSI address scsi0:0:1:0 at restore time, the restjob.
Managing the Data Protector Internal Database Recovering the IDB drive letters must be assigned). If this cannot be ensured, follow the procedure for recovering the IDB to a different disk/volume layout. You can use the -preview option of the omnidbrestore command to see where the files will be restored. • If possible, move the media.log file from the previous installation to a safe place. It will provide you with the information about the media used since the last IDB backup.
Managing the Data Protector Internal Database Recovering the IDB • Mahost (Media Agent host) • Policy (number) A policy number can be obtained using the following translation: 1 for Standalone devices, 3 for Stacker devices, 10 for SCSI-II Libraries, and 5 for Jukebox devices. • Media type (number) A media type number can be obtained using the following translation: 1 for DDS, 3 for ExaByte, 10 for DLT, or 7 for File. • SCSI address • Robotics SCSI address (only if using Exchanger library devices) 5.
Managing the Data Protector Internal Database Recovering the IDB procedure for recovering the IDB to a different disk/volume layout. You can use the -preview option of the omnidbrestore command to see where the files will be restored. • If possible, move the media.log file from the previous installation to a safe place. It will provide you with the information about the media used since the last IDB backup. This is very helpful for updating the IDB if transaction logs are not available.
Managing the Data Protector Internal Database Recovering the IDB Replaying IDB Transaction Logs In a successful omnidbrestore -autorecover, transaction logs are already replayed. Use this procedure only if you need to retry replaying of transaction logs or you postponed it before. Replaying transaction logs after the IDB restore is completed recovers the IDB to the same state as before the crash, except that binary files are not updated and changes to binary files are lost.
Managing the Data Protector Internal Database Recovering the IDB the procedure below, bring the OBVS_VELOCIS and OBVS_MCRS cluster groups online using the Cluster Administrator utility. How to Replay Transaction Logs Proceed as follows: 1. Run the following command to replay the transaction logs: omnidbrestore -replay_only -firstlog where is the first transaction log that was created just after the IDB backup was started.
Managing the Data Protector Internal Database Recovering the IDB 1. In the Data Protector Manager, browse the Internal Database backup object and select it for restore. Refer to “Selecting Your Data for Restore” on page 270. 2. For the db40/datafiles directory, use the Restore As/Into option to specify a restore location other than the default one. Refer to “Restoring Files to Different Paths” on page 299.
Managing the Data Protector Internal Database Recovering the IDB Updating the IDB by Importing Media To successfully complete the IDB recovery, you need to update the IDB changes after the IDB is restored. If transaction logs are not available, update the changes by importing all media since the last IDB backup. Do this once the IDB restore has finished. To verify that transaction logs are available, or to update the changes using transaction logs, refer to “Replaying IDB Transaction Logs” on page 430.
Managing the Data Protector Internal Database Recovering the IDB 434 Chapter 9
10 Disaster Recovery Chapter 10 435
Disaster Recovery In This Chapter In This Chapter This chapter provides an overview of disaster recovery on Windows UNIX clients and Cell Managers.
Disaster Recovery Introduction Introduction This section explains the basic terms used in the Disaster Recovery chapter. For overview and concepts of the available disaster recovery methods as well as table outlining the possible combinations of disaster recovery methods and operating system, please see the Disaster Recovery section in the HP OpenView Storage Data Protector Concepts Guide.
Disaster Recovery Introduction Table 10-1 Supported Disaster Recovery Methods and Operating Systems 32-bit Windows XPa/Server 2003 Cell Manager Client • “Assisted Manual Disaster Recovery of a Windows System” on page 450 • “Assisted Manual Disaster Recovery of a Windows System” on page 450 • “Automated System Recovery” on page 480 • “Disk Delivery Disaster Recovery of a Windows Client” on page 459 • “Automated System Recovery” on page 480 64-bit Windows XP/Server 2003 • “Assisted Manual Disaster R
Disaster Recovery Introduction Table 10-1 Supported Disaster Recovery Methods and Operating Systems Cell Manager Tru64/AIX Client • “Disk Delivery Disaster Recovery of an UNIX Client” on page 507 a. ASR is not available on Windows XP Home Edition, therefore it is not supported. What Is a Computer Disaster? A computer disaster refers to any event that renders a computer system unbootable, whether due to human error, hardware or software failure, virus, natural disaster, etc.
Disaster Recovery Introduction What Is a Hosting System? Hosting system is a working Data Protector client used for Disk Delivery Disaster Recovery with Disk Agent installed. What Is Auxiliary Disk? Auxiliary disk is a bootable disk that has a minimal operating system with networking and Data Protector Disk Agent installed. It can be carried around and used to boot the target system in Phase 1 of Disk Delivery Disaster Recovery of UNIX clients.
Disaster Recovery Introduction • user profiles volume • Certificate Server database volume on Windows Server • Active Directory Service volume on domain controller on Windows Server • quorum volume on Microsoft Cluster Server. What is Online Recovery? Online recovery is performed when Cell Manager is accessible. In this case most of Data Protector functionalities are available (Cell Manager runs the session, restore sessions are logged in the IDB, you can monitor the restore progress using GUI, etc.).
Disaster Recovery Introduction The Recovery Process The disaster recovery process consists of 4 phases with the Phase 0 (preparation) being the prerequisite for a successful disaster recovery. In Phase 1, DR OS is installed and configured, which usually includes repartitioning and reformatting of the boot partition, since the boot or system partition of the system are not always available and the environment needs to be recovered before normal restore operations can resume.
Disaster Recovery Preparing for a Disaster Recovery Preparing for a Disaster Recovery Carefully follow the instructions in this section to prepare for a disaster recovery and to ensure fast and efficient restore. Preparation does not depend on the disaster recovery method, however, it does include developing a detailed disaster recovery plan, performing consistent and relevant backups and updating the SRD file on Windows.
Disaster Recovery Preparing for a Disaster Recovery On UNIX systems: • Creation of tools, such as the auxiliary disk with the minimum operating system, network resources, and the Data Protector Disk Agent installed. • Creation of pre-execution scripts, which collect the storage structure and other client-specific preparations. On Windows systems: • Updating System Recovery Data (SRD) and storing it to a safe place. You should restrict access to SRD files due to security reasons.
Disaster Recovery Preparing for a Disaster Recovery On Windows, while the system is up and running, many system files cannot be replaced because the system keeps them locked. For example, the user profiles that are currently being used cannot be restored. The login account has to be changed or the relevant service has to be stopped. Data consistency of an application can be violated depending on what is active on the system when the backup runs, thereby causing re-start and execution issues after recovery.
Disaster Recovery Preparing for a Disaster Recovery corresponding media must be added to the SRD. The SRD can be updated only on a Windows client. The name of the updated SRD file is recovery.srd.
Disaster Recovery Preparing for a Disaster Recovery Omnisrdupdate requires a session_ID to update an existing SRD file with backup object information belonging to the given session. Using this value, omnisrdupdate will update the SRD file with the backup object information which belongs to the passed session_ID value. After the SRD is updated it will be saved back on the Cell Manager.
Disaster Recovery Preparing for a Disaster Recovery To determine for which hostname the SRD file from the Cell Manager should be updated, use the option -host with the command omnisrdupdate. If you don’t specify the hostname, the local host is assumed. SRD file on the Cell Manager is not updated. Example To update the SRD file with the backup object information which belongs to a session 2002/05/02-5 for the client with the hostname computer.company.
Disaster Recovery Preparing for a Disaster Recovery IMPORTANT You should restrict access to SRD files due to security reasons.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System Assisted Manual Disaster Recovery of a Windows System The following sections explain how to prepare and execute an Assisted Manual Disaster Recovery on Windows systems. For details on supported operating systems, refer to the HP OpenView Storage Data Protector Software Release Notes. Assisted Manual Disaster Recovery is an elementary method that consists of the following steps: 1.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System Requirements • The partitions have to be the same size or larger than the partitions on the failed disk. This way the information stored on the failed disk can be restored to the new one. Also, the type of filesystem and compression attributes of the volumes must match (FAT, NTFS). • The hardware configuration of the target system must be the same as of the original system. This includes SCSI BIOS settings (sector remapping).
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System 1. You need a Windows bootable installation CD-ROM to enable your system to start from the CD-ROM. If you do not have a bootable CD-ROM, use the standard procedure for booting the computer from diskettes. 2. Ensure that you have drivers for the system you want to recover. You may need to install some drivers, such as network, HBA and SCSI drivers during Windows Setup. 3.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System \i386\tools\DRSetup (located on Data Protector installation medium) for 32 bit Windows Client or Cell Manager on two floppy disks (drsetup diskettes) or \Depot\DRSetup64 or \i386\tools\DRSetup64 (Data Protector installation medium) for 64 bit Windows systems on three floppy disks. In case of a disaster, save the updated SRD file of the crashed client to the first floppy disk (disk1).
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System The table on the next page is an example of the preparation for the disaster recovery. Note that data in the table belongs to a specific system and cannot be used on any other system. Refer to the Appendix A, “Windows Manual Disaster Recovery Preparation Template,” on page A-49 for an empty template which can be used when preparing for the Assisted Manual Disaster Recovery.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System Table 10-3 client properties computer name ANDES hostname andes.company.com drivers hpn.sys, hpncin.dll Windows Service Pack Windows NT SP6 TCP/IP properties IP address 3.55.61.61 default gateway 10.17.250.250 subnet mask 255.255.0.0 DNS order 11.17.3.108, 11.17.100.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System Recovery Follow the procedure below to recover a Windows system using Assisted Manual Disaster Recovery. If you are performing advanced recovery tasks (such as disaster recovery of a Cell Manager or IIS), see also “Advanced Recovery Tasks” on page 490. 1. Install the Windows system from the CD-ROM and install additional drivers if needed. The Windows operating system has to be installed on the same partition as prior to the disaster.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System Other Windows Systems NOTE If you are recovering a Windows system other than Windows NT, install Windows into its original location, i.e. the same drive letter and directory as in the original system before the disaster. This information is stored in the SRD file. During the installation, do not add the system to the previous location where the Windows domain resided, but add the system to a workgroup instead. 3.
Disaster Recovery Assisted Manual Disaster Recovery of a Windows System CD drives for the location of disaster recovery setup files (Dr1.cab and omnicab.ini). If the required files are found, the drstart utility installs the disaster recovery files in the <%SystemRoot%>\system32\OB2DR directory. Otherwise enter their path in the DR Installation Source text box or browse for the files. 9. If the recovery.srd file is saved in the same directory as dr1.cab and omnicab.ini files, then drstart.
Disaster Recovery Disk Delivery Disaster Recovery of a Windows Client Disk Delivery Disaster Recovery of a Windows Client To perform the Disk Delivery Disaster Recovery, use a working Data Protector client (Data Protector disaster recovery host) to create the new disk while connected to this client. The administrator has to ensure before the disaster that enough data is collected to correctly format and partition the disk.
Disaster Recovery Disk Delivery Disaster Recovery of a Windows Client Limitations • Disk Delivery Disaster Recovery is not supported for Microsoft Cluster Server. • RAID is not supported. This includes software RAIDs (fault-tolerant volumes and dynamic disks). • Internet Information Server (IIS) Database, Terminal Services Database and Certificate Server Database are not restored automatically during Phase 2. They can be restored on the target system using the standard Data Protector restore procedure.
Disaster Recovery Disk Delivery Disaster Recovery of a Windows Client • partitions filesystem type You can refer to Table 10-3 on page 455 as an example of the preparation for the Disk Delivery disaster recovery. Refer to the Appendix A, “Windows Manual Disaster Recovery Preparation Template,” on page A-49 for an empty template which can be used when preparing for the Disaster Recovery. Recovery This section provides the procedure for recovering your Windows client using the Disk Delivery method.
Disaster Recovery Disk Delivery Disaster Recovery of a Windows Client IMPORTANT You have to assign drive letters for Windows 2000/XP/Server 2003 mountpoints. In this case you must have enough unassigned drive letter available in order to be able to assign a drive letter for each mount point. 7. Perform all necessary drive letter mappings by right clicking on the original drive letter. This is necessary because drive letters on hosting and original system can be different. 8. Press Finish. 9.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System Enhanced Automated Disaster Recovery of a Windows System Enhanced Automated Disaster Recovery (EADR) is a fully automated Data Protector recovery method for Windows clients and Cell Manager, where user intervention is reduced to minimum. For details on supported operating systems, refer to the HP OpenView Storage Data Protector Software Release Notes.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System Any remaining partitions can be recovered using the standard Data Protector recovery procedure. The following sections explain the limitations, preparation, and recovery that pertains to EADR of the Windows clients. See also “Advanced Recovery Tasks” on page 490.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System • When backing up the client, the default 64 kB block size should be used to write to the device if you plan to perform an offline restore. This is the only default block size available on Windows when performing disaster recovery.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System Certificate Server Database are not restored automatically during Phase 2. They can be restored on the target system using the standard Data Protector restore procedure. Disk and Partition Configuration • With fault-tolerant disk drives on the OS level for Windows NT systems, mirror set is supported while stripe and volume set are not. Dynamic disks are not supported on Windows 2000 (including mirror set upgraded from Windows NT).
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System 2. In the Scoping pane, expand the Backup Specifications and then Filesystem. 3. Select the backup specification you will use for a full client backup (create it if you have not created it already). 4. In the Results Area, click Options. 5. Under Filesystem Options click Advanced. 6. Click the WinFS Options and check the Copy full DR image to disk check box.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System (create it if you have not created it already). 4. In the Results Area, click Backup Object Summary. 5. Select the client for which you would like to store its DR image file onto the Cell Manager and click Properties. 6. Click the WinFS Options and check the Copy full DR image to disk check box.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System IMPORTANT It is recommended to restrict access to backup media, DR images, SRD files and disaster recovery CDs due to security reasons. Preparing DR CD ISO Image To prepare a DR CD ISO image, perform the following steps: 1. In the Context List, select Restore. 2. Click the Tasks navigation tab and select Disaster Recovery in the Scoping Pane. 3.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System Recovery You need the following to successfully perform a disaster recovery on the crashed system: • A new hard disk to replace your crashed disk. • A successful full client backup of the client that you want to recover. • The Data Protector disaster recovery CD. EADR of a Windows Client The following is a step-by-step procedure for performing EADR of a Windows system: 1. Boot from the disaster recovery CD of the original system.
Disaster Recovery Enhanced Automated Disaster Recovery of a Windows System machine press F12, to boot from the hard disk and not from the CD. 6. Data Protector will then reestablish the previous storage structure within the selected scope of recovery and restore all critical volumes. The temporary DR OS will be deleted after the first login, except in the following cases: • Minimal Recovery is selected.
Disaster Recovery One Button Disaster Recovery of a Windows System One Button Disaster Recovery of a Windows System One Button Disaster Recovery (OBDR)is a fully automated Data Protector recovery method for Windows clients and Cell Manager, where user intervention is reduced to minimum. For details on supported operating systems, refer to the HP OpenView Storage Data Protector Software Release Notes. OBDR collects all relevant environment data automatically at backup time.
Disaster Recovery One Button Disaster Recovery of a Windows System Requirements • Data Protector Automatic Disaster Recovery and User Interface components must be installed on the systems for which you want to enable recovery using this method. See HP OpenView Storage Data Protector Installation and Licensing Guide.
Disaster Recovery One Button Disaster Recovery of a Windows System • When backing up the client, the default 64 kB block size should be used to write to the device if you plan to perform an offline restore. This is the only default block size available on Windows when performing disaster recovery.
Disaster Recovery One Button Disaster Recovery of a Windows System • One Button Disaster Recovery backup session can only be performed for one selected client or Cell Manager on the same OBDR device at a time. This has to be done on a single, locally attached OBDR capable device. Disk and Partition Configuration • With fault-tolerant disk drives on the OS level for Windows NT systems, mirror set is supported while stripe and volume set are not.
Disaster Recovery One Button Disaster Recovery of a Windows System 2. Click Tasks navigation tab and check One Button Disaster Recovery Wizard in the Scoping Pane. 3. From the drop-down list in the Results Area, select the client for which you would like to perform OBDR backup and click Next. 4. All critical objects are already selected (including the IDB in case of the Cell Manager OBDR backup) and can not be deselected.
Disaster Recovery One Button Disaster Recovery of a Windows System an OBDR backup specification to keep it in the original One Button Disaster Recovery format. If saved as a standard backup specification, it is not usable for OBDR purposes. 10. Click Start Backup to run the backup interactively. The Start Backup dialog box appears. Click OK to start the backup.
Disaster Recovery One Button Disaster Recovery of a Windows System device documentation. 4. In the screen that appears, select the scope of recovery and press Enter. There are 5 different scopes of recovery: • No recovery: Disaster recovery is not performed and the computer is rebooted. • Default Recovery: Critical volumes are recovered. All other disks are not partitioned and formatted and remain empty and ready for Phase 3.
Disaster Recovery One Button Disaster Recovery of a Windows System • You have interrupted the Disaster Recovery Wizard during the 10 seconds pause after it has found the DR installation and SRD file on the backup medium, and have selected the Use Debugs option. • You have manually started the omnidr command with the no_reset or debug options. • Disaster recovery fails. 7. Additional steps are required if you are recovering a Cell Manager or performing advanced recovery tasks.
Disaster Recovery Automated System Recovery Automated System Recovery Automated System Recovery (ASR) is an automated system on Windows systems, which reconfigures a disk to its original state (or resizes the partitions if the new disk is larger than the original disk) in the case of a disaster. This includes disk partitioning and logical volume configuration (file formats, drive letter assignments, volume mountpoints, and volume characteristics). ASR thus enables the Data Protector drstart.
Disaster Recovery Automated System Recovery The following sections explain the requirements, limitations, preparation, and recovery pertaining to Automated System Recovery on Windows systems. See also “Advanced Recovery Tasks” on page 490. Requirements • Data Protector Automatic Disaster Recovery component must be installed on systems for which you want to enable recovery using ASR. See the HP OpenView Storage Data Protector Installation and Licensing Guide.
Disaster Recovery Automated System Recovery Figure 10-4 Verifying the Default Block Size Limitations • Windows XP Home Edition does not support ASR. • Multiboot systems that do not use Microsoft's boot loader are not supported. • Internet Information Server (IIS) Database, Terminal Services Database, and Certificate Server Database are not restored automatically during Phase 2. They can be restored on the target system using the standard Data Protector restore procedure.
Disaster Recovery Automated System Recovery • Only those local backup devices are supported, that can be installed by Windows during OS installation (no additional drivers are required). Preparation Complete the steps described in the section “Preparing for a Disaster Recovery” on page 443 in addition to completing the steps listed in this section. See also “Advanced Recovery Tasks” on page 490 in order to prepare for disaster recovery.
Disaster Recovery Automated System Recovery 3. In the HP OpenView Storage Data Protector Manager, switch to the Restore context. 4. Click the Tasks navigation tab and select Disaster Recovery in the Scoping Pane. 5. From the drop down list in the Results Area, select the client for which you would like to create an ASR set. 6. Click Create Automated System Recovery set and then click Next. Figure 10-5 Data Protector will obtain the ASR archive file from the Cell Manager.
Disaster Recovery Automated System Recovery installation check box to copy DR installation files to the same location. The recommended destination is your floppy drive because you will need these files stored on diskettes (ASR set) to perform ASR. Data Protector will create two diskettes for a 32 bit Windows system and three diskettes for a 64 bit Windows system.
Disaster Recovery Automated System Recovery Recovery To successfully perform a disaster recovery of the crashed system, you need the following: • A new hard disk to replace your crashed disk. • A successful full client backup of the client that you want to recover. • Updated ASR set. • Windows installation medium. ASR Procedure The following is a step-by-step procedure for performing ASR: 1. Boot from the Windows installation medium. 2. Press F2 during the start of the OS setup to enter the ASR mode. 3.
Disaster Recovery Restoring the Data Protector Cell Manager Specifics Restoring the Data Protector Cell Manager Specifics This section explains additional steps for particular methods that should be performed when restoring Windows Cell Manager. Making IDB consistent (all methods) The procedure described in this section should only be used after you have performed the general disaster recovery procedure.
Disaster Recovery Restoring the Data Protector Cell Manager Specifics • Disaster recovery CD for the Cell Manager should be prepared in advance. IMPORTANT You have to perform a new backup and prepare a new DR CD after each hardware, software or configuration change. This also applies to any network changes, such as change of IP address or DNS server.
Disaster Recovery Restoring the Data Protector Cell Manager Specifics Automated System Recovery Specifics An additional step is required in Phase 0 if you are recovering Windows Cell Manager using Automated System Recovery (ASR): • ASR diskette for the Cell Manager should be prepared in advance. IMPORTANT You have to perform a new backup and update the ASR diskette after each hardware, software or configuration change. This also applies to any network changes, such as change of IP address or DNS server.
Disaster Recovery Advanced Recovery Tasks Advanced Recovery Tasks This section provides explanation of the steps you will need to take if you want to perform advanced recovery tasks such as restoring Microsoft Cluster Server and Internet Information Server. Restoring the Microsoft Cluster Server Specifics This section provides explanation of the steps you will need to take if you want to perform disaster recovery of a Microsoft Cluster Server (MSCS).
Disaster Recovery Advanced Recovery Tasks • all nodes • administrative virtual server (defined by the administrator) • if Data Protector is configured as a cluster aware application, then Cell Manager virtual server and IDB should be included in the backup specification. Disaster Recovery of a Secondary Node This is the basic scenario for disaster recovery of a MSCS.
Disaster Recovery Advanced Recovery Tasks Merging P1S files of all nodes for EADR Another step is required for EADR after backup has been performed. Information on shared cluster volumes in P1S files for all nodes in the MSCS has to be merged so that P1S file of each node contains information on shared cluster volumes configuration. It is namely impossible to collect enough information to configure the disk in Phase 1 for shared disk volumes that are locked by another node at backup.
Disaster Recovery Advanced Recovery Tasks • the primary node must have write access to all IDB volumes, when recovering the Cell Manager • all other nodes must be shut down until all physical disk resources are online In this case, you have to restore the primary node with the quorum disk first. The IDB has to be restored as well if the Cell Manager has been installed in the cluster. Optionally you can restore the MSCS database. After the primary node has been restored, you can restore all remaining nodes.
Disaster Recovery Advanced Recovery Tasks TIP To enable automatic restore of all shared disk volumes in the MSCS using OBDR method, move all volumes temporarily to the node for which you are preparing OBDR boot tape. It is namely impossible to collect enough information to configure the disk in Phase 1 for shared disk volumes that are locked by another node. 2. Reboot the computer. 3. Restore the cluster database. MSCS database is part of the CONFIGURATION on Windows.
Disaster Recovery Advanced Recovery Tasks Restoring Hard Disk Signatures On Windows The MSCS service uses a hard disk signature written into the MBR of every hard disk to identify physical disks. If the shared cluster disks have been replaced, this means that the disk signatures were changed during Phase 1 of disaster recovery. As a consequence, the Cluster Service will not recognize the replaced disks as valid cluster resources, and cluster groups depending on those resources will fail.
Disaster Recovery Advanced Recovery Tasks There is no simple procedure for recovering the disk signatures on Windows NT. MSDN article Q243195 describes a complicated procedure that includes manual modifying of the registry, and should be followed to recover disk signatures. Note that using Registry Editor incorrectly may cause serious problems that may require you to reinstall your operating system.
Disaster Recovery Advanced Recovery Tasks 4. The IIS Database is restored as a plain file (with the filename DisasterRecovery) into the default IIS location (%SystemRoot%\system32\inetsrv). 5. After the successful boot, restore the IIS Database using the standard Data Protector restore procedure or IIS Backup/Restore snap-in. Note that this may take quite some time. Troubleshooting 1. If any of the IIS dependant services (for example, SMTP, NNTP) do not start automatically, try to start them manually. 2.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client Manual Disaster Recovery of an HP-UX Client This chapter explains the procedure that should be used to recover a HP-UX client from a disaster. The procedure is based on the Ignite-UX product; an application primary developed for HP-UX system installation and configuration tasks, which offers (in addition to a powerful interface for the system administration) preparation and recovery of the system from a disaster.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client Use Ignite-UX GUI where it is supported. Using Custom Installation Medium Overview Large IT environments often consist of a large number of systems that are based on identical hardware and software. Installation of OS, applications and required patches can be significantly reduced if a complete snapshot of the installed system is used to install other systems.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client core.cfg to archive_.cfg: cp /opt/ignite/data/examples/core.cfg /var/opt/ignite/data//archive_.cfg Example cp /opt/ignite/data/examples/core.cfg /var/opt/ignite/data/Rel_B.11.11/archive_HPUX11_11_DP50_C L.cfg 5.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client impacts = "/stand" 1116Kb impacts = "/tcadm" 1Kb impacts = "/usr" 729579Kb impacts = "/var" 254639Kb 7. To make Ignite-UX aware of the new created depot, add an cfg entry to the /var/opt/ignite/INDEX file with the following layout: cfg "" { description "” "/opt/ignite/data//config" "/var/opt/ignite/data// archive_.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client NOTE Ignite-UX enables you to create a bootable tape or CD based on the created Golden Image. Please refer to the Ignite-UX Administration Guide for more information.Ignite-UX enables you to create a bootable tape or CD based on the created Golden Image. Please refer to the Ignite-UX Administration Guide for more information.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client Using System Recovery Tools Overview The usage of the system recovery tools, bundled with the Ignite-UX, enables you a fast and easy recovery from a disk failure. The recovery archive of system recovery tools includes only essential HP-UX directories. However, it is possible to include other files and directories (for example, additional volume groups or the Data Protector files and directories) in the archive to speed up the recovery process.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client This creates an Ignite-UX depot under /var/opt/ignite/depots/recovery_cmds, which can be specified as a source directory by swinstall on the client for the Ignite-UX software installation. After you have installed Ignite-UX on the client node, you can use the GUI on the Ignite-UX server to create recovery archives using make_net_recovery or make_tape_recovery.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client enough space to store the compressed archive. 4. Select the volume groups you want to include into the archive. 5. The archive creation process will now begin. Check the status and log file on the Ignite-UX server by right clicking the icon and selecting Client Status. NOTE Ignite-UX allows you to create bootable archive tape out of the compressed archive file.
Disaster Recovery Manual Disaster Recovery of an HP-UX Client 3. Select Install HP-UX from the Welcome to Ignite-UX screen. 4. Choose Remote graphical interface running on the Ignite-UX server on the UI Option screen. 5. Respond to the Network configuration dialogue. 6. The system is now prepared for a remote installation controlled from the Ignite-UX Server. • On the Ignite-UX Server 7. Right click the client icon within the Ignite-UX GUI and select Install Client – New Install. 8.
Disaster Recovery Disk Delivery Disaster Recovery of an UNIX Client Disk Delivery Disaster Recovery of an UNIX Client To perform a Disk Delivery Disaster Recovery of a UNIX client, connect a bootable disk that contains a minimal OS installation and Data Protector Disk Agent to the crashed system. The administrator has to ensure (before the disaster) that enough data has been collected to correctly format and partition the disk.
Disaster Recovery Disk Delivery Disaster Recovery of an UNIX Client • If the system that will be backed up has application processes active at low run levels, establish a state of minimal activity (modified init 1 run level) and enter the single user mode to prevent errors after recovery (see “Consistent and Relevant Backup” on page 444). Consult your operating system documentation for details. HP-UX Example 1. Move some kill links from /sbin/rc1.d to /sbin/rc0.
Disaster Recovery Disk Delivery Disaster Recovery of an UNIX Client single user mode: — boot -fl s to boot using already generated vmunix file — boot -fi genvmunix -fl s to boot into the single user mode with the generic kernel.
Disaster Recovery Disk Delivery Disaster Recovery of an UNIX Client — Consider logging out all users from the system. — Shut down all applications, unless the application data gets backed up separately, for example, using online database backup. — You may want to restrict network access to the system, so that no one can log on to the system while the backup is running (for example, on HP-UX, overwrite inetd.sec and use inetd -c).
Disaster Recovery Disk Delivery Disaster Recovery of an UNIX Client 4. Reconstruct the logical volume structure if applicable (for example, using LVM on HP-UX). Use the saved data for the non-root volume groups (for example, with vgcfgrestore or SAM on HP-UX). 5. Additionally, the root volume group to be restored has to be created on the repaired disk (for example, using vgimport on HP-UX). It will not look like a root volume group during the restore process.
Disaster Recovery Manual Disaster Recovery of an UNIX Cell Manager Manual Disaster Recovery of an UNIX Cell Manager Manual Disaster Recovery is a basic method, that involves recovering the system by reinstalling it in the same way as it was initially installed. In addition, Data Protector is used to then restore all files, including the operating system. Limitation For details on supported operating systems, refer to the HP OpenView Storage Data Protector Software Release Notes.
Disaster Recovery Manual Disaster Recovery of an UNIX Cell Manager • A device connected to the Cell Manager. Procedure The following steps need to be performed to recover a Cell Manager: 1. Replace the crashed disk. 2. Boot your system from the installation media of your operating system. 3. Reinstall the operating system. Refer to your system administrator’s manual for instructions.
Disaster Recovery Troubleshooting Disaster Recovery on Windows Troubleshooting Disaster Recovery on Windows This section provides explanation of the steps you will need to take if you happen to encounter problems with Manual, Disk Delivery, Enhanced, or One Button Disaster Recovery procedures on Windows systems.
Disaster Recovery Troubleshooting Disaster Recovery on Windows 4. To update this new state with disaster recovery, you should perform all necessary procedures (collecting system data, backup) once more, as described in the “Preparing for a Disaster Recovery” section. Troubleshooting Assisted Manual Disaster Recovery Problem Drstart reports: “Can not copy ” This error is reported because the drstart utility can not copy the specified file.
Disaster Recovery Troubleshooting Disaster Recovery on Windows Problem “No Operating System Found” Action After performing disaster recovery, if the final boot of a Windows NT system fails with “No Operating System Found”, check the boot.ini file for information about where the partition information is located. See Step 4 in the section “Recovery” on page 461 for additional information.
Disaster Recovery Troubleshooting Disaster Recovery on Windows \tmp) if improperly configured storage devices are attached to your system: DRIM_WIN_ERROR 13 SetupDiGetDeviceRegistryProperty • There must be enough registry space available. It is recommended to set the maximum registry size to at least twice that of the current registry size. If there is not enough registry space available, a similar entry would appear in the autodr.log : ERROR registry 'Exception while saving registry' .
Disaster Recovery Troubleshooting Disaster Recovery on Windows 'System may not boot after disaster recovery. If the boot and system volumes are both physically located below 7.8 GB, this error message can be ignored. The boot and system partitions on Windows NT 4.0 must namely be physically bellow the first 7.8 GB due to the operating system limitations. Refer to MSDN Q224526.
Disaster Recovery Troubleshooting Disaster Recovery on Windows WARNING Editing the registry incorrectly can result in failed disaster recovery. Problem Auto Logon Does Not Work Action Sometimes auto logon does not work and you have to manually log on using an administrator’s account with a blank password. Problem Computer Freezes During EADR Action Check if the CD is readable. Do not reuse CD-RWs too many times.
Disaster Recovery Troubleshooting Disaster Recovery on Windows 520 Chapter 10
11 Customizing the Data Protector Environment Chapter 11 521
Customizing the Data Protector Environment In This Chapter In This Chapter This chapter describes how you can customize Data Protector to better suit your needs. The chapter consists of the following sections: “Global Options File” on page 523 “Using Omnirc Options” on page 525 “Firewall Support” on page 528 IMPORTANT For specific information on Data Protector limitations and recommendations, see the HP OpenView Storage Data Protector Software Release Notes.
Customizing the Data Protector Environment Global Options File Global Options File Global options affect the entire Data Protector cell, and cover various aspects of Data Protector, such as time-outs and limits. All global options are described in the global options file, which you can edit in order to customize Data Protector. It is located in the /etc/opt/omni/options directory on the UNIX Cell Manager and in the \config\options directory on Windows Cell Manager.
Customizing the Data Protector Environment Global Options File balance number. • DailyMaintenanceTime: Determines the time after which the daily maintenance tasks can begin, using the twenty-four hour clock notation. By default, this time is set to 12:00 (Noon). For a list of daily maintenance tasks, refer to “Data Protector Checking and Maintenance Mechanism” on page 605. • DailyCheckTime: Determines the time after which daily check can begin, using the twenty-four hour clock notation.
Customizing the Data Protector Environment Using Omnirc Options Using Omnirc Options The omnirc options are most useful for troubleshooting or overriding other settings affecting the behavior of the Data Protector client only. However, even advanced users should not use them unless their operating environment demands it. The Disk Agents and Media Agents use the values of these options. These options are found in the following locations: Locations • /opt/omni/.
Customizing the Data Protector Environment Using Omnirc Options • OB2DEVSLEEP: Changes the sleep time between each retry while loading a device. • OB2ENCODE: Allows a user to always turn on data encoding, regardless how the backup options are set in the backup specification. • OB2OEXECOFF: Allows a user to restrict or disable any object preand post-exec scripts defined in backup specifications for a specific client.
Customizing the Data Protector Environment Using Omnirc Options • OB2VXDIRECT: Enables direct (without cache) reading for Advanced VxFS filesystems, as well as improving performance. • OB2PORTRANGE: This option limits the range of port numbers that Data Protector uses when allocating listen ports dynamically. This option is typically set to enable the administration of a cell through a firewall.
Customizing the Data Protector Environment Firewall Support Firewall Support This section describes how to configure Data Protector in an environment where the Data Protector processes communicate across a firewall. Communication in Data Protector processes communicate using TCP/IP connections. Every Data Protector Data Protector system accepts connections on port 5555 by default. In addition, some processes dynamically allocate ports on which they accept connections from other Data Protector processes.
Customizing the Data Protector Environment Firewall Support NOTE The OB2PORTRANGE variable only applies to dynamically allocated ports. It does not affect the usage of the default Data Protector port number 5555. Defining a port range for the Data Protector processes limits the port usage of Data Protector. It does not prevent other applications from allocating ports from this range as well.
Customizing the Data Protector Environment Firewall Support The table below lists all possible Data Protector agent identifiers that can be used in the OB2PORTRANGESPEC variable. Note that agent processes that do not dynamically allocate listen ports are not listed in the following table.
Customizing the Data Protector Environment Firewall Support NOTE The OB2PORTRANGESPEC variable only applies to dynamically allocated ports. It does not affect the usage of the default Data Protector port number 5555. Defining a port range for a specific Data Protector agent process limits the port usage of this agent. It does not prevent other processes (applications or other Data Protector agents) from allocating ports from this range as well.
Customizing the Data Protector Environment Firewall Support The following table provides a list of all Data Protector components. The first two columns list the process identifiers and their listen ports. The last two columns list all applicable connecting processes.
Customizing the Data Protector Environment Firewall Support Table 11-2 Listening Component Process Connecting Component Port Process Source Port Inet 5555 xSM N/Aa Application Agent Does not accept connections Application Host a. The source port of a connection is always assigned by the operating system and cannot be limited to a specific range. b. Only for backup sessions with the reconnect feature enabled.
Customizing the Data Protector Environment Firewall Support Table 11-3 Connecting Component Listening Component Process Port Process Port N/Aa xMAb 5555 N/Aa xDAb 5555 N/Aa Application 5555 Cell Manager xSM Agentb N/Aa MMDc Dynamic N/Aa Inet on CM 5555 N/Aa CRS Dynamic N/Aa BSM Dynamic N/Aa RSM Dynamic N/Aa MSM Dynamic N/Aa DBSM Dynamic N/Aa MMD Dynamic N/Aa xMA-NET Dynamic N/Aa xSMd Dynamic N/A xSMd Dynamic N/Aa UMAb’ e 5555 User Interface GUI/CLI CLI (
Customizing the Data Protector Environment Firewall Support Table 11-3 Connecting Component Listening Component Process Port Process Port Application Agent N/Aa Inet on CM 5555 N/Aa CRS Dynamic N/Aa RSM Dynamic N/Aa BSM Dynamic N/Aa xMA-NET Dynamic a. The source port of a connection is always assigned by the operating system and cannot be limited to a specific range. b.
Customizing the Data Protector Environment Firewall Support Figure 11-1 Configuration Diagram The following two items define the port range settings for this configuration: 1. In order to determine which processes need to communicate across the firewall, see Table 11-2 for the Disk Agent and Media Agent. It shows that the Disk Agent and Media Agent need to accept connections from the Session Manager on port 5555.
Customizing the Data Protector Environment Firewall Support ✓ Allow connections from the CM system to port 5555 on the MA system This table also shows that the Media Agent needs to accept connections from the Disk Agent. However, since these two agents do not communicate through the firewall, you do not need to define a firewall rule for them. 2. See also Table 11-3 for the Disk Agent and Media Agent.
Customizing the Data Protector Environment Firewall Support Example 2: Disk Agent Installed Outside, Other Components Installed Inside a Firewall You can configure your backup environment so that the Cell Manager, Media Agent, and GUI are in the intranet and some Disk Agents are in the DMZ: Figure 11-2 Configuration Diagram The following three items define the port range settings for this configuration: 538 Chapter 11
Customizing the Data Protector Environment Firewall Support 1. In order to determine which processes need to communicate across the firewall, see Table 11-2 (Disk Agent column). It shows that the Disk Agent needs to accept connections from the Session Manager on port 5555. This leads to the following rule for the firewall: ✓ Allow connections from the CM system to port 5555 on the DA system 2. See also Table 11-3 for the Disk Agent.
Customizing the Data Protector Environment Firewall Support NOTE All Session Managers allocate ports from this range, not only the one communicating through the firewall. Limitations • Remote installation of clients across the firewall is not supported. You need to install clients locally in the DMZ. • This setup does not allow the backup of databases or applications using Application Agents on the clients in the DMZ.
Customizing the Data Protector Environment Firewall Support Figure 11-3 Configuration Diagram The following three items define the port range settings for this configuration: 1. Table 11-2 and Table 11-3 show that the GUI does not accept any connections.
Customizing the Data Protector Environment Firewall Support Table 11-4 Process Port Inet 5555 CRS Dynamic BSM Dynamic RSM Dynamic MSM Dynamic DBSM Dynamic This leads to the following firewall rule for the connection to the Inet listen port: ✓ Allow connections from the GUI system to port 5555 on the CM system 2. Table 11-1 shows that CRS requires only one port.
Customizing the Data Protector Environment Firewall Support Port Range Settings on the Cell Manager For example, if there are 25 backup and five restore sessions running and two GUIs opened, you need to have at least 32 ports available. However, since other processes may allocate ports from this range as well, you should specify a range of about 100 ports on the CM system.
Customizing the Data Protector Environment Firewall Support Figure 11-4 Configuration Diagram The following three items define the port range settings for this configuration: 1.
Customizing the Data Protector Environment Firewall Support Table 11-5 Process Port CRS Dynamic RSM Dynamic BSM Dynamic DBSM Dynamic xMA-NET Dynamic Here, the application Agent connects to the Media Agent. However, this connection does not go through the firewall and so you do not need to specify a port range. This leads to the following firewall rule for the connection to the Inet listen port.
Customizing the Data Protector Environment Firewall Support one DBSM will be started. For Oracle and SAP R/3 integrations, “concurrency + 1” DBSMs will be started.
12 Troubleshooting Chapter 12 547
Troubleshooting In This Chapter In This Chapter If you have problems with Data Protector, use the suggestions in this chapter to get back on track, including information on: “Before Calling Your Support Representative” on page 549 “Data Protector Log Files” on page 550 “Debugging” on page 553 “Browsing Troubleshooting Messages” on page 561 “When You Cannot Access Online Troubleshooting” on page 562 “Description of Common Problems” on page 564 “Troubleshooting Networking and Communication” on page 565 “Trou
Troubleshooting Before Calling Your Support Representative Before Calling Your Support Representative In order to speed up the process of solving your problem, you should prepare before reporting a problem to HP Customer Support Service. See the suggestions below for preliminary steps you can take. Ensure that: • You are not running into known limitations that cannot currently be overcome.
Troubleshooting Data Protector Log Files Data Protector Log Files If you encounter problems using the Data Protector application, you can use information in the log files to determine your problem.
Troubleshooting Data Protector Log Files Log Files and Their Contents The table below describes the information found in Data Protector log files: Table 12-1 Data Protector Log Files Log File Description debug.log Unexpected conditions are logged to this file. While some can be meaningful to you, it will be used mainly by the support organization. Ob2EventLog.txt Data Protector events that occurred during Data Protector operation and all Data Protector notifications are logged into this file.
Troubleshooting Data Protector Log Files Table 12-1 Data Protector Log Files Log File Description purge.log Contains traces of the background purge of the IDB. RDS.log Contains IDB logs. The file resides on the Cell Manager: On Windows: \db40\da tafiles\catalog On UNIX: /var/opt/omni/db40/datafiles/c atalog sm.log Contains errors that occurred during backup and restore sessions, such as errors in parsing the backup specifications. Upgrade.
Troubleshooting Debugging Debugging You should collect debugs only when the support organization requires them to resolve a technical issue. When Data Protector runs in debug mode, it creates debug information that consumes a large amount of disk space. Consult the support organization about the detail level that should be applied and environmental conditions for running Data Protector in the debug mode.
Troubleshooting Debugging Ways of Debugging You can start Data Protector in the debug mode in different ways and use it to generate debug traces. For more details about debugging options refer to the section “Debug Syntax” on page 555. IMPORTANT When Data Protector runs in the debug mode, debug information is generated for every action. For example, if you start a backup specification in the debug mode, Disk Agents deliver output on each client backed up in this backup specification.
Troubleshooting Debugging NOTE Before you edit the file, make a copy of it, as the changes have to be reverted when debugging is no longer desired. -debug 1-99 sch.txt Example of a Modified Schedule -full -only 2002 -day 14 -month Dec -at 22:00 Debug Syntax Almost all Data Protector commands can be started with an additional -debug parameter that has the following syntax: -debug 1-99[,C:][,T:] [] where: 1-99 is the debug range.
Troubleshooting Debugging Trace File Name The debug postfix option is used for creating the trace files in the following directory: • On UNIX systems: /tmp • On Windows systems: \tmp • On Novell NetWare systems: SYS:\USR\OMNI\TMP The files are named OB2DBG______ where: (debugging ID) is the process ID of the first process that accepts the debugging parameters. This ID is used as an ID for the debugging session. All further processes will use this ID.
Troubleshooting Debugging OB2DBGDIR The default location of trace files can be changed on a per system basis with the omnirc variable OB2DBGDIR. For more details about omnirc variables, refer to “Using Omnirc Options” on page 525. INET Debug on UNIX To debug Inet on UNIX systems, edit the /etc/inetd.conf file and change the following line: omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni/log/inet.
Troubleshooting Debugging NOTE Use the -debug option carefully because execution traces can become quite large. CRS Debug in the Microsoft Cluster Environment In the Data Protector shared directory, edit the \Config\options\Trace file. Add the following lines: ranges=1-99,110-500 postfix=DBG select=obpkg.rc.aus.hp.com From the Cluster Administrator GUI, take the CRS service resource (OBVS_MCRS) offline.
Troubleshooting Debugging onboard_type/Adaptec xxx/... for Windows Media Agent clients. • The operating system version, for example, HP-UX 11.00, Windows NT Server 4.0 SP2... • Topology information obtained from the omnicellinfo -cell command output. • The output of the devbra -DEV command if you have issues with backup devices. 3. Discuss the technical issue with the support organization and request the following information: • Debug level (For example, “1-99.” This is a command option needed later.).
Troubleshooting Debugging Protector services on the Cell Manager and restart them without the debug option. 10. Copy the files from any clients involved with the problem. 11. Compress and pack the contents of the tmp directories (_error_run.txt files) on the Cell Manager and clients and the info file. Use WINZIP or TAR. 12. Email the files to the support organization and include in the email information about how you packed and compressed the files. 13. Delete the _error_run.
Troubleshooting Browsing Troubleshooting Messages Browsing Troubleshooting Messages Data Protector provides an interactive online troubleshooting utility, where you can get a detailed explanations of your error messages, including suggestions for correcting problems. When you receive an error message from Data Protector, the error number is presented as a clickable link. To see detailed information about the error, click the link.
Troubleshooting When You Cannot Access Online Troubleshooting When You Cannot Access Online Troubleshooting If the user interface cannot be started, you can access the troubleshooting file. This is a text file containing all Data Protector error messages each of which includes the following information: • MESSAGE: The error message as it appears in Data Protector. • DESCRIPTION: A detailed or extended information about the error. • ACTION: Actions you can take to solve or avoid the problem.
Troubleshooting When You Cannot Access Online Troubleshooting * Collect all log files (*.log) in /log directories on all hosts involved in the situation when this error occurred (i.e. host running VBDA, host running BMA and host running BSM).
Troubleshooting Description of Common Problems Description of Common Problems If you have problems with Data Protector, find the problem area listed below that most closely matches the problem you are having: • Networking and Communication, on page 565 • Service Startup, on page 569 • Device Usage, on page 574 • Starting Backup and Restore Sessions, on page 580 • User Interface Startup, on page 590 Certain functionality of Data Protector is subject to particular license requirements.
Troubleshooting Troubleshooting Networking and Communication Troubleshooting Networking and Communication The section addresses the following networking and communication problems: • “Hostname Resolution Problems” on page 565 • “Client Fails with “Connection Reset by Peer”” on page 567 Hostname Resolution Problems Hostname resolution is a very common problem in a Data Protector environment. It means that host A is unable to communicate with host B.
Troubleshooting Troubleshooting Networking and Communication Table 12-2 Data Protector Components Name Resolution Host A Host B MoM Server Host Media Agent Client Host MoM Server Host Cell Manager Host DNS Resolution Problem Test DNS resolution among hosts using the omnicheck command.
Troubleshooting Troubleshooting Networking and Communication Problem The response to the omnicheck command is: cannot connect to This means that the packet has been sent, but not received because of the timeout. Action Check for and resolve any network problems on the remote host. Checking the TCP/IP setup An important aspect of the TCP/IP configuration process is the setup of a hostname resolution mechanism.
Troubleshooting Troubleshooting Networking and Communication On Windows, apply the change to the Cell Manager first. If you run the UNIX Cell Manager and the problem persists, apply the change to any problematic Windows clients. 1.
Troubleshooting Troubleshooting Data Protector Services and Daemons Troubleshooting Data Protector Services and Daemons The Data Protector services and daemons run on the Cell Manager. Run the omnisv -status command to check whether services are running. If the Data Protector services seem to be stopped or have not been installed on the target Data Protector client, ensure first that you don’t have a name resolution problem.
Troubleshooting Troubleshooting Data Protector Services and Daemons Changed service account properties If the service account does not have permission to start the service or if the service account properties (the password, for example) have been changed, you get the following error message: The Data Protector Inet service failed to start due to the following error: The service did not start due to a logon failure. Action 1.
Troubleshooting Troubleshooting Data Protector Services and Daemons directory and the problems should be resolved. 2. Restart the services using the omnisv -start command. RDS does not work on the Windows TSE Cell Manager Use TCP transport instead of local transport by modifying the \db40\datafiles\catalog\velocis.ini file: Under TCP Configuration, set Enabled to yes.
Troubleshooting Troubleshooting Data Protector Services and Daemons There are several possible reasons why the Data Protector daemon has failed to start: Raima Velocis server daemon could not be started /opt/omni/sbin/omnisv -start Could not start Raima Velocis server daemon. Action See /var/opt/omni/db40/datafiles/catalog/RDS.log for details. Check that you have all IDB files in the /var/opt/omni/db40 directory.
Troubleshooting Troubleshooting Data Protector Services and Daemons • /etc/opt/omni/options/global • /etc/opt/omni/options/users/UserList • /etc/opt/omni/options/ClassSpec Data Protector Processes Table 12-3 shows which processes run and where they run while Data Protector is idle, or doing a backup, a restore or a media management session. Table 12-3 Which Processes Run Where, and When Idle Backup Restore Media Management rds.exe, crs.exe, omniinet.exe, bsm.exe rds.exe, mmd.exe, omniinet.exe, mmd.
Troubleshooting Troubleshooting Devices and Media Troubleshooting Devices and Media This section describes solutions to the following problems that can arise while using backup devices: • “Cannot Access Exchanger Control Device on Windows 2000/XP/Server 2003” on page 574 • “Device Open Problem” on page 575 • “Using Unsupported SCSI Adapters on Windows” on page 575 • “Medium Quality Statistics” on page 575 • “Medium Header Sanity Check” on page 577 • “Cannot Use Devices After Upgrading to Data Protector A.
Troubleshooting Troubleshooting Devices and Media Device Open Problem The error message Cannot open device (not owner) appears when trying to use a DDS device. Action Check whether you are using a medium that is incompatible with the Media Recognition System. Media used with DDS drives must comply with the Media Recognition System. Using Unsupported SCSI Adapters on Windows System fails due to usage of unsupported SCSI adapters with backup devices.
Troubleshooting Troubleshooting Devices and Media If you receive media related errors during write operations, or if the medium is marked as poor, you can check the media.log file for media errors statistics. You can do this also when receiving media related errors during read operations. Media.
Troubleshooting Troubleshooting Devices and Media • Log sense write report for LTO devices - total data sets processed. Media ID from tape=0fa003bd:3e0057e6:05b7:0001; Medium Label= ULT2; Logical drive=ultrium1; Errors corrected no delay= 0; Errors corrected delay= 0; Total= 0;Total errors corrected= 0; Total correction algorithm processed= 0; Total bytes processed= 47246; Total uncorrected errors= 0 One data set is 404352 bytes.
Troubleshooting Troubleshooting Devices and Media Action Export the medium from the IDB and restart the failed session using a different medium. Cannot Use Devices After Upgrading to Data Protector A.05.10 Problem After upgrading to Data Protector A.05.10, you cannot use devices that were configured as different device types in previous releases. For example, you cannot use 9940 devices that were configured as 9840 devices, or SuperDLT devices that were configured as DLT devices.
Troubleshooting Troubleshooting Devices and Media For example, move the media associated with the reconfigured 9940 devices to the Default T9940 media pool, and the media associated with the reconfigured SuperDLT devices to the Default SuperDLT media pool. For related procedures, refer to the online Help. Other Common Problems Other common problems are hardware-related. Action Check the SCSI communication between the system and the device, such as adapters or SCSI cables and their length.
Troubleshooting Troubleshooting Backup and Restore Sessions Troubleshooting Backup and Restore Sessions You may run into the following problems while running or starting backup and restore sessions: • “Filenames Are Not Displayed Correctly in GUI” on page 580 • “Full Backups Are Performed Instead of Incrementals” on page 580 • “Unexpected Mount Request for a Standalone Device” on page 581 • “Unexpected Mount Request for a Library Device” on page 582 • “Unexpected Mounted Filesystems Detected” on page 583 •
Troubleshooting Troubleshooting Backup and Restore Sessions No previous full backup Before performing an incremental backup of an object, Data Protector requires a full backup. Data Protector uses a full backup as a base for comparison to determine which files have changed and consequently need to be included in the incremental backup. If a protected full backup is not available for this comparison, a full backup is performed. Action Set the protection for the full backup.
Troubleshooting Troubleshooting Backup and Restore Sessions Action Modify the media pool policy to Appendable to enable the appending of backups to the media until the media are full. The media in the device are not formatted and the media pool to be used has a Strict policy If your pool uses a Strict media allocation policy, media that are not formatted will not be used for backup. If no formatted media are available, Data Protector issues a mount request.
Troubleshooting Troubleshooting Backup and Restore Sessions The media in the library are not formatted and the media pool with the media used for backup has a Strict policy If your pool uses a Strict media allocation policy, unformatted media are not used for backup. If no formatted media are available in the library, Data Protector issues a mount request. Action If you would like Data Protector to automatically format unformatted media that are available in the library, set the media pool policy to Loose.
Troubleshooting Troubleshooting Backup and Restore Sessions Action 1. Before you start a restore erase the disk image on the Data Protector client with the disk image being restored by entering the following commands: prealloc null_file 65536 dd if=null_file of= where is a device file for the disk image being restored. 2. Start the restore.
Troubleshooting Troubleshooting Backup and Restore Sessions Data Protector Backup sessions are not started at all (UNIX-specific) Action Run the crontab -l command to check whether the omnitrig program is included in the crontab file.
Troubleshooting Troubleshooting Backup and Restore Sessions reset by peer. It is possible that some parallel restore sessions are completed without errors, while other restore sessions are not even started. Action A workaround for this problem is to set the SmMaxAgentStartupRetries global variable in the Data Protector global options file (located in /etc/opt/omni/options/global) to 2 or more (max. 50).
Troubleshooting Troubleshooting Backup and Restore Sessions to the , but it cannot because it does not know this system as , but only as . The system name cannot be expanded to the full name because the DNS is improperly configured. This situation can also be the other way around, where DNS is configured on the Cell Manager and not on the Application Client. Action Set up the TCP/IP protocol and configure DNS properly.
Troubleshooting Troubleshooting Data Protector Installation Troubleshooting Data Protector Installation If you run into problems while installing the Data Protector software, check the system's log files on UNIX and setup log files on Windows to determine the problem: System Log File UNIX (local installation) /var/adm/sw/swinstall.log /var/adm/sw/swagent.log UNIX (remote installation) /var/opt/omni/log/IS_install.log Windows (local installation) :\\OB2_Setup_ ui__
Troubleshooting Troubleshooting Data Protector Installation Name Resolution Problems when Installing the Windows Cell Manager During the installation of the Data Protector Cell Manager on Windows, Data Protector detects and warns you if the DNS or the LMHOSTS file is not set up as required. In addition, Data Protector notifies you if the TCP/IP protocol is not installed on your system.
Troubleshooting Troubleshooting User Interface Startup Troubleshooting User Interface Startup Data Protector user interface start-up problems are usually the result of services not running, services not being installed, or problems with network communication. Inet Is Not Responding on the Cell Manager The following message appears: Cannot access the system (inet is not responding).
Troubleshooting Troubleshooting User Interface Startup Connection to a Remote System Refused on Windows or Novell NetWare The response of the telnet 5555 command is Connection refused. Action If the Data Protector Inet service is not running on the remote system, run the omnisv -start command to start it. If Data Protector is not installed on the remote system, install Data Protector on the remote system.
Troubleshooting Troubleshooting the IDB Troubleshooting the IDB This section provides troubleshooting for the following problems using the IDB: • “Problems During the Upgrade of the IDB on Solaris” on page 592 • “Problems While Running the User Interface” on page 595 • “Libraries (Executables) Missing” on page 595 • “Data Files (Directories) Missing” on page 596 • “Temporary Directory Missing” on page 597 • “Problems During Backup and Import” on page 598 • “Performance Problems” on page 599 • “MMDB and CDB
Troubleshooting Troubleshooting the IDB • Upgrade of detail part running. The detail upgrade was started and is currently running. • Upgrade of detail part finished. The detail upgrade finished. The Cell Manager crashes during the core upgrade The following methods can help you to identify the problem: • The omnidbutil –upgrade_info command on the Cell Manager reports Core upgrade failed. • The upgrade.
Troubleshooting Troubleshooting the IDB The detail upgrade runs out of memory on the system • The upgrade.log file on the Cell Manager contains the database network communication error entry. • Data Protector Event Log contains the Session was aborted. (Upgrade detail part.) entry. • On UNIX Cell Managers, the Data Protector RDS daemon (/opt/omni/lbin/rds) is not displayed when listing the Data Protector processes using the ps -ef | grep omni command.
Troubleshooting Troubleshooting the IDB Problems While Running the User Interface IDB is corrupted Any of the following messages can be displayed: • Database is corrupted. • Interprocess communication problem. • Cannot open Database/File. • Error - Details Unknown. Action Recover the IDB. For more information, refer to “Recovering the IDB” on page 417.
Troubleshooting Troubleshooting the IDB The RDS service/process cannot be started If one or several shared library files are missing, the omnisv -status command informs you that the RDS service/process is down, while all other services/processes are running. Action Reinstall Data Protector and reboot your Cell Manager. This will reinstall the shared libraries and restart the RDS service/process.
Troubleshooting Troubleshooting the IDB Temporary Directory Missing The following temporary directories should exist on the Cell Manager: • On Windows: \tmp • On UNIX: /var/opt/omni/tmp The Data Protector GUI cannot connect to the Cell Manager When Data Protector GUI tries to connect to the Cell Manager, the following error message is displayed if Data Protector temporary directory is missing: Cannot access the Cell Manager system.
Troubleshooting Troubleshooting the IDB Problems During Backup and Import The BSM or RSM is terminated during the IDB backup or import session If the BSM or RSM get terminated during the IDB backup or import session, the following error message is displayed: IPC Read Error System Error: [10054] Connection reset by peer In the Internal Database context, the session status of the IDB backup or import session is still marked as In progress but the session is actually not running. Action 1.
Troubleshooting Troubleshooting the IDB • On UNIX, the Data Protector MMD (/opt/omni/lbin/mmd) is not displayed when listing the Data Protector processes using the ps -ef | grep omni command. On Windows, the Data Protector MMD process (mmd.exe) is not listed among processes in the Windows Task Manager. Action 1. Close the Data Protector GUI. 2. Run the omnisv –stop command to stop the Data Protector services/processes. 3. Run the omnisv –start command to start the Data Protector services/processes. 4.
Troubleshooting Troubleshooting the IDB Action Set the time interval, which will be used when browsing object versions for restore. You can change this time interval in the Restore context when searching for the specific object version you want to restore. Set the default time interval used when browsing object versions for restore. 1. In the Data Protector GUI, click the File menu and then click Preferences. 2. Click the Restore tab and in the Search interval drop-down list, select the search interval.
Troubleshooting Troubleshooting the IDB with the CMMDB installed (MoM). Run this command for every Cell Manager in the MoM environment by specifying its hostname as the argument.
Troubleshooting Troubleshooting Reporting and Notifications Troubleshooting Reporting and Notifications If you use Outlook XP or Outlook 98/2000 with the latest security patch installed, you following problem appears: when you add a report to a report group specifying email as a send method, and then try to start a report group, GUI hangs. The same happens if you configure a notification and select the email send method.
Troubleshooting Troubleshooting Data Protector Online Help Troubleshooting Data Protector Online Help Data Protector online Help consists of two parts: Help Topics and the Help Navigator. Help Navigator is context-sensitive help, explaining screens and options in the Data Protector GUI, while Help Topics provide conceptual information, procedure instructions, and examples. The Help system you use depends on the platform (Windows or UNIX) on which you are running Data Protector.
Troubleshooting Troubleshooting Data Protector Online Help not Netscape Navigator, select Custom. IMPORTANT Data Protector supports only Netscape Navigator for online Help viewing. 2. Click Settings to open the HTML Viewer Settings window. 3. In the Location of executable script or binary file text box, enter the location of your browser (for example, /opt/netscape). 4. In the Command to start viewer text box, enter the command that will start the browser. For Netscape Navigator, enter netscape $HTML$.
Troubleshooting Check Whether Data Protector Functions Properly Check Whether Data Protector Functions Properly The following sections provide an overview of the Data Protector Checking and Maintenance Mechanism and an overview of things to be checked in order to determine whether Data Protector is properly configured in your backup environment.
Troubleshooting Check Whether Data Protector Functions Properly • Database Purge Needed For more information on Data Protector notifications, refer to “Data Protector Notifications” on page 342. Any notification that is triggered is by default sent to the Data Protector Event Log. For more information on the Data Protector Event Log, refer to“Data Protector Event Log” on page 356.
Troubleshooting Check Whether Data Protector Functions Properly Overview of Items to Be Checked In order to ensure that Data Protector is functioning properly and to identify potential problems before they arise, it is recommended that you perform regular checks as described in the following sections. Using the User Check Failed notification, it is possible to automate these checks by developing scripts including these checks.
Troubleshooting Check Whether Data Protector Functions Properly Check whether backups are configured properly 1. Run the backup preview for crucial backup specifications. Refer to Chapter 5, “Backup,” on page 151 for more information on previewing backups. Successfully completed previews prove that: • All clients in the backup specification are accessible from the Cell Manager. • All files are accessible. • The amount of data to be backed up is determined. • All backup devices are configured properly. 2.
Troubleshooting Check Whether Data Protector Functions Properly ✓ Database Space Low ✓ Not Enough Free Media ✓ Health Check Failed ✓ User Check Failed ✓ Unexpected Events ✓ License Will Expire ✓ Database Purge Needed For more information on Data Protector notifications, refer to “Data Protector Notifications” on page 342. For more information on Data Protector Event Log, refer to“Data Protector Event Log” on page 356.
Troubleshooting Check Whether Data Protector Functions Properly 610 Chapter 12
13 Integrations with Other Applications Chapter 13 611
Integrations with Other Applications In This Chapter In This Chapter This chapter gives detailed information on how to integrate the following applications with Data Protector: “Cluster Integrations with Data Protector” on page 613 “Microsoft Cluster Server Integration” on page 617 “MC/ServiceGuard Integration” on page 627 “Veritas Cluster Integration” on page 640 “Data Source Integration (DSI)” on page 644 “Application Response Measurement (ARM) Integration” on page 646 “ManageX Integration” on page 648 “
Integrations with Other Applications Cluster Integrations with Data Protector Cluster Integrations with Data Protector See the HP OpenView Storage Data Protector Software Release Notes for details on the supported cluster software on specific operating systems, level of cluster support and for supported configurations. See the HP OpenView Storage Data Protector Concepts Guide for more information about cluster support and cluster concepts.
Integrations with Other Applications Cluster Integrations with Data Protector Figure 13-1 A Typical Cluster • 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.
Integrations with Other Applications Cluster Integrations with Data Protector all cluster nodes. Each cluster node compares this packet and determines which cluster node is still operational so that appropriate ownership of the package (MC/SG, Veritas Cluster) or group (MSCS) can be determined. What is a Package A package (MC/SG, Veritas Cluster) or a group (MSCS) is a collection of or Group? resources that are needed to run a specific cluster-aware application.
Integrations with Other Applications Cluster Integrations with Data Protector NOTE In MSCS environment, Cluster Service components (for example, Database Manager) maintain a coherent image of the central cluster database, which stores information regarding changes in the status of a node, resource, or group. Cluster database must be stored on the cluster’s shared disk volume.
Integrations with Other Applications Microsoft Cluster Server Integration Microsoft Cluster Server Integration As a part of its high-availability functionality and support, Data Protector provides an integration with the Microsoft Cluster Server (MSCS). See the HP OpenView Storage Data Protector Software Release Notes for details on the supported cluster software on specific operating systems, level of cluster support and for supported configurations.
Integrations with Other Applications Microsoft Cluster Server Integration Cell Manager on Microsoft Cluster Server The Data Protector Cell Manager can be installed on the 32-bit Microsoft Cluster Server. This enables an automatic migration of the Data Protector services from one cluster node to another in case of failover. Installation See the HP OpenView Storage Data Protector Installation and Licensing Guide for more information on how to install Data Protector cluster Cell Manager.
Integrations with Other Applications Microsoft Cluster Server Integration Figure 13-2 Importing Cluster Virtual Server Hostnames to a Cell on Microsoft Cluster Server Backing Up Data in a Cluster (MSCS) When backing up data that reside on cluster node disks, you need to distinguish between: • Local cluster node disks • Shared cluster node disks In the Data Protector GUI, you can see only local disks listed for each cluster node.
Integrations with Other Applications Microsoft Cluster Server Integration To distinguish between local cluster node disks and shared cluster node disks, Data Protector queries the MSCS database for a list of physical cluster disk resources. All cluster disks presented as proprietary cluster disk resources (e.g. NetRAID 4 disk type) are treated as local cluster node disks.
Integrations with Other Applications Microsoft Cluster Server Integration Failover of Data Protector If a failover of the cluster-aware Data Protector occurs during backup, all running and pending backup sessions fail. In the Data Protector GUI and in the backup specification, you can set one of the options that define automatic backup session restart at failover of Data Protector. See Figure 13-3 on page 622.
Integrations with Other Applications Microsoft Cluster Server Integration Figure 13-3 Advanced Backup Specification Options-Clustering Do not Restart Backups At Failover When the Do not restart backups at failover option is selected, sessions that failed are not restarted. This is the default option.
Integrations with Other Applications Microsoft Cluster Server Integration Failover of Application Other Than Data Protector As the Data Protector cluster Cell Manager is a storage application within a cluster environment, it has to be aware of other applications that might be running within the cluster. If they are running on a node other than Data Protector and if some application fails over to the node where Data Protector is running, this will result in a high load on this node.
Integrations with Other Applications Microsoft Cluster Server Integration script will be run. This is the node where Data Protector is running. In the Generic Application Parameters window, enter the path name of batch file (for example, c:\program_files\omniback\bin\clus.bat) and directory of the omniclus command. This command resides in the \bin directory. Examples To abort all running sessions on the server obsv.company.com use the following command line: omniclus.exe -clus obvs.
Integrations with Other Applications Microsoft Cluster Server Integration Example In the Data Protector GUI you have configured a backup specification with abort ID = 10. Use the following command line to abort all backup sessions except one with abort ID = 10 on the server obsv.company.com: omniclus.exe -clus obvs.company.
Integrations with Other Applications Microsoft Cluster Server Integration NOTE When the command is run, the elapsed time for each backup specification is checked and the session is aborted if the specified conditions are met. For example, in the Data Protector GUI specify that the backup specification is aborted if it has been running for less than 30 minutes.
Integrations with Other Applications MC/ServiceGuard Integration MC/ServiceGuard Integration As part of its high-availability support, Data Protector provides a full integration of the Data Protector Cell Manager with MC/ServiceGuard on HP-UX systems. For details on supported operating system versions, supported configurations, and level of cluster support, refer to the HP OpenView Storage Data Protector Software Release Notes.
Integrations with Other Applications MC/ServiceGuard Integration — Package IP or virtual ip-address In addition, you will also need to create a volume group on a shared disk. • Ensure that the cluster nodes and the package IP are on the same subnet. • If you have DNS in your environment, ensure that all the cluster nodes and the package IP are registered with the DNS server.
Integrations with Other Applications MC/ServiceGuard Integration Configuring the Primary and Secondary Cell Managers The following sections explain how to configure the Primary and Secondary Cell Managers. NOTE The following sections provide step-by-step examples to configure the Primary and Secondary Cell Managers. Directory and file names, numbers, and other variables will differ from the following examples according to your environment.
Integrations with Other Applications MC/ServiceGuard Integration 2. Create a logical volume for that group (for example, /dev/vg_ob2cm/lv_ob2cm), with the following steps: a. Create a new logical volume: lvcreate -L 100 -n lv_ob2cm /dev/vg_ob2cm The number 100 presents the size of the partition in MB. The etc/opt/omni and var/opt/omni Data Protector directories will be located there. b.
Integrations with Other Applications MC/ServiceGuard Integration mount /dev/vg_ob2cm/lv_ob2cm /omni_shared 5. Modify the /etc/opt/omni/sg/sg.conf template file. IMPORTANT The SHARED_DISK_ROOT variable must contain the name of the mount point directory (for example, SHARED_DISK_ROOT=/omni_shared). The CS_SERVICE_HOSTNAME variable must contain the name of the virtual Cell Manager, as it is known to the network.
Integrations with Other Applications MC/ServiceGuard Integration 1. On system2 set up the volume group to be imported, with the following steps: a. Create a directory for the volume group to be imported: mkdir /dev/vg_ob2cm b. List all existing volume groups on the system to look for the next available minor number: ll /dev/*/group c. Create a group file for the volume group: mknod /dev/vg_ob2cm/group c 64 0x010000 d.
Integrations with Other Applications MC/ServiceGuard Integration /opt/omni/sbin/install/omniforsg.ksh -secondary /omni_shared 5. Unmount the mount point directory (Data Protector shared directory): umount /omni_shared 6. Deactivate the volume group you imported: vgchange -a n /dev/vg_ob2cm Configuring the Cell Manager Package NOTE The following section provides step-by-step examples to configure the Data Protector package.
Integrations with Other Applications MC/ServiceGuard Integration 3. Create the directory in the /etc/cmcluster directory that will hold the Data Protector package: mkdir /etc/cmcluster/ob2cl 4. Change to the /etc/cmcluster/ob2cl directory: cd /etc/cmcluster/ob2cl 5. Create a package configuration file in the Data Protector package directory: cmmakepkg -p /etc/cmcluster/ob2cl/ob2cl.conf 6. Create a package control file in the Data Protector package directory: cmmakepkg -s /etc/cmcluster/ob2cl/ob2cl.cntl 7.
Integrations with Other Applications MC/ServiceGuard Integration • SERVICE_NAME, SERVICE_FAIL_FAST_ENABLED , SERVICE_HALT_TIMEOUT Enter the service information. For the service name, you can enter any name but note that you will use the same name in the control file afterwards. For example: SERVICE_NAME omni_sv SEVICE_FAIL_FAST_ENABLED NO SERVICE_HALT_TIMEOUT 300 • SUBNET Enter the subnet of the cluster. For example: SUBNET 10.17.0.0 8.
Integrations with Other Applications MC/ServiceGuard Integration IMPORTANT The service name must be the same as that used in the configuration file. The service command (the SERVICE_CMD variable) must be the one used in the example below. For example: SERVICE_NAME [0] = omni_sv SERVICE_CMD [0] = “/etc/opt/omni/sg/csfailover.
Integrations with Other Applications MC/ServiceGuard Integration f. Import the cluster package host name manually (for example, by using the omnicc command): omnicc -import_host -virtual g. If the Data Protector Installation Server was also installed on the MC/ServiceGuard (default), you have to import this Installation Server (for example, by using the omnicc command): omnicc -import_is h.
Integrations with Other Applications MC/ServiceGuard Integration NOTE When using the Data Protector GUI, import each cluster package as a client. See Figure 13-4 on page 638 and the HP OpenView Storage Data Protector Installation and Licensing Guide for instructions. Figure 13-4 Importing an Application Cluster Package to a Cell on MC/ServiceGuard Backing Up Data in a Cluster (MC/SG) This section provides an overview of how to back up specific data in a cluster environment.
Integrations with Other Applications MC/ServiceGuard Integration NOTE When backing up a virtual host, the object ownership will acquire the ownership of the stationary host on which the cluster package is running. Therefore, when a failover occurs, the same object backup is showing a different ownership. To avoid this, set the ownership in the backup specification to the virtual host. Backing Up Local Disks To back up cluster local disks, proceed as follows: 1.
Integrations with Other Applications Veritas Cluster Integration Veritas Cluster Integration Clients on Veritas Cluster Data Protector can only be used to back up local or shared disks in a Veritas Cluster environment. Cluster aware operation is not supported for Data Protector with Veritas Clusters. Installation Data Protector has to be installed locally on each client, and each client has to be imported to the cell.
Integrations with Other Applications Veritas Cluster Integration 1. Install the Data Protector Disk Agent on each system with the local disk you want to back up. 2. Configure a backup of the local system in the cluster and define the local disks you want to back up. Backing Up Shared Disks A shared disk can only be backed up as a local disk, as described above. It can however be backed up from any of the cluster nodes between which it is shared. For example, to back up a disk shared between two nodes: 1.
Integrations with Other Applications Novell NetWare Cluster Integration Novell NetWare Cluster Integration Clients on Novell NetWare Cluster Data Protector can only be used to back up local disks or cluster shared pools in a Novell NetWare Cluster environment. Cluster aware operation is not supported for Data Protector with Novell NetWare Clusters. In case of failover, backup or restore sessions have to be restarted manually.
Integrations with Other Applications Novell NetWare Cluster Integration 2. Configure a backup of the local system in the cluster and define the local disks you want to back up. Backing Up Shared Cluster Pools A cluster shared pool can only be backed up via the virtual server. When the virtual server is selected for backup, only cluster shared pools are displayed as available pools for backup. For example, to back up a pool shared between two nodes: 1.
Integrations with Other Applications Data Source Integration (DSI) Data Source Integration (DSI) What Is DSI? The Data Source Integration (DSI) allows you to use the HP OpenView Performance Agent to log data, define alarms, and access metrics from sources of data other than the metrics logged by the HP OpenView Performance Agent scopeux collector.
Integrations with Other Applications Data Source Integration (DSI) First select which data you want to log. Data Protector provides a reporting command omnirpt located in the /opt/omni/bin/ directory. This command can be used to gather various information about the Data Protector environment. See the omnirpt manpage for more information on the command. Secondly, write a script that in an infinite loop queries for the selected data and writes it to standard output. 2. Create the class specification file.
Integrations with Other Applications Application Response Measurement (ARM) Integration Application Response Measurement (ARM) Integration What Is the ARM Integration? Data Protector supports the emerging standard for measuring the response time of transactions in distributed environments, the Application Response Measurement (ARM) interface. Data provided by Data Protector can be used in ARM-compliant system management and monitoring tools, such as HP OpenView Performance Agent.
Integrations with Other Applications Application Response Measurement (ARM) Integration The following table shows the supported ARM transactions: Table 13-1 ARM Transactions Transaction Name Additional Information Transaction Description BS- Time Duration of a backup session RS- Time Duration of a restore session BO- Time Duration of a backup of a specific object DP Number of purged records and IDB size (MB) Duration of the IDB purge DC IDB si
Integrations with Other Applications ManageX Integration ManageX Integration What Is the ManageX Integration? ManageX integration is supported on those Windows systems where ManageX is running. It allows the operator using ManageX to check Data Protector operation and backup status. What Is Supported? The integration supports the following: • Sends the Data Protector messages with the severity levels you choose to the ManageX console.
Integrations with Other Applications Access Points for System and Management Applications Access Points for System and Management Applications This section provides information on Data Protector access points for System and Management applications.
Integrations with Other Applications Access Points for System and Management Applications checking and maintenance mechanism. For more information on Data Protector checking and maintenance mechanism, refer to “Data Protector Checking and Maintenance Mechanism” on page 605.
Integrations with Other Applications Access Points for System and Management Applications Each event is marked with an Enterprise Event ID (EID) used to designate the type of entity that has sent the event. The EID for the events, sent by the OpenView entity, is “.1.3.6.1.4.1.11.2.17.1”. • Generic Event ID Each event is also marked with a Generic Event ID (GID). For standard SNMP traps, the GID tells ovtrapd which standard SNMP trap was generated.
Integrations with Other Applications Access Points for System and Management Applications Command-Line Interface, Graphical User Interface and Web Reporting Interface The Data Protector CLI provides comparable functionality as it is provided in Data Protector GUI. Using the Data Protector CLI you can: • Start the Data Protector GUI and sub-GUIs. For a list of the Data Protector sub-GUIs, refer to “Graphical User Interface” on page 6.
Integrations with Other Applications Access Points for System and Management Applications To enable automatic forwarding of all Data Protector messages and messages about the Data Protector services (if they are stopped) to Windows Application Log, set the EventLogMessages variable in the Data Protector global options file to 1. For more information on Data Protector global options file refer to “Global Options File” on page 523.
Integrations with Other Applications Access Points for System and Management Applications Refer to the omnihealthcheck man page for more information on omnihealthcheck command. Getting the Results of the Last Night’s Backup You can get the report on the results of the last night’s backups using the Data Protector reporting functionality.
14 ADIC/GRAU DAS and STK ACS Libraries Chapter 14 655
ADIC/GRAU DAS and STK ACS Libraries In This Chapter In This Chapter This chapter assumes that you have already physically configured the ADIC/GRAU or STK library. If you have not done so, refer to the documentation that comes with the ADIC/GRAU or STK library for instructions on configuring the library. For a list of supported DAS software versions, refer to HP OpenView Storage Data Protector Software Release Notes.
ADIC/GRAU DAS and STK ACS Libraries ADIC/GRAU DAS and STK ACS Integrations ADIC/GRAU DAS and STK ACS Integrations Who Uses the ADIC/GRAU DAS or STK ACS Integration? Typically, the Data Protector and ADIC/GRAU DAS or STK ACS integration is necessary in complex environments where the amount of backed up data is exceptionally large and, therefore, so is the amount of media needed to store the data.
ADIC/GRAU DAS and STK ACS Libraries ADIC/GRAU DAS and STK ACS Integrations Figure 14-1 Data Protector and ADIC/GRAU DAS Library Systems Integration Figure 14-2 Data Protector and StorageTek ACS Library Integration 658 Chapter 14
ADIC/GRAU DAS and STK ACS Libraries ADIC/GRAU DAS and STK ACS Integrations Configuration Basics When considering your environment and the configuration that is best for you, keep in mind that there are two ways to configure the ADIC/GRAU and STK ACS libraries with Data Protector: where each client accesses the library directly (direct access to the library), or where each client is connected to one system that controls the library robotics through the server (indirect access to the library).
ADIC/GRAU DAS and STK ACS Libraries ADIC/GRAU DAS and STK ACS Integrations (added to an Data Protector media pool), it remains under Data Protector’s control during its lifetime or until it is removed from the Data Protector media pool. IMPORTANT Each type of media has to have its own library. While the ADIC/GRAU or STK ACS system can store many physically different types of media, Data Protector can only recognize a library with a single type of media in it.
ADIC/GRAU DAS and STK ACS Libraries ADIC/GRAU DAS and STK ACS Integrations Although you can change the label and exclude the barcode number, this is not recommended. In this case you should manually keep track of the actual barcode and the medium label you assigned to the medium. Initializing Other Formats If Data Protector recognizes some other media data format or media that have been used by another application, it will not initialize these media unless the Force Operation option is selected.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device The ADIC/GRAU DAS Library Device Data Protector provides full support for the ADIC/GRAU DAS Library Systems. This section describes how you install and configure ADIC/GRAU DAS library devices for direct and indirect library access. Direct Access to the Library: Installation and Configuration This section focuses on the direct access configuration.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device • Before you configure a Data Protector ADIC/GRAU backup device, you have to create/update the C:\DAS\ETC\CONFIG file on the DAS server computer. In this file, a list of all DAS clients has to be defined. For Data Protector, this means that each Data Protector client with the DAS Media Agent installed has to be defined. Each DAS client is identified with a unique client name (no spaces), for example DATA_PROTECTOR_C1.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device NOTE This applies to HP-UX and Windows. For further questions on the configuration of your GRAU library please contact your local GRAU support or review your GRAU documentation. Installing the DAS Media Agent Data Protector provides a dedicated ADIC/GRAU library policy used to configure an ADIC/GRAU library with Data Protector.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device ✓ A list of available drives with corresponding DAS name of the drive. If you have defined the DAS Clients for your ADIC/GRAU system, you can get this list with the following dasadmin commands: dasadmin listd2 [client] or dasadmin listd [client], where [client] is the DAS Client for which the reserved drives are to be displayed.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device At this stage, you should have your hardware connected and your DAS software properly installed. Run the following command to check whether or not the library drives are properly connected to your system: • \bin\devbra -dev You should see the library drives with corresponding device files displayed in the list. For the NT platform, install the ADIC/GRAU library for client interface aci.dll, winrpc32.dll and ezrpcw32.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device dasadmin listd [client], where [client] is the DAS Client for which the reserved drives are to be displayed. Dasadmin command can be called from the C:\DAS\BIN directory on the OS\2 host, or from the system directory: /usr/local/aci/bin directory. ✓ A list of available Insert/Eject Areas with corresponding format specifications.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device You should see the library drives with corresponding device files displayed in the list. For the HP-UX platform, install the ADIC/GRAU library for client interface: Copy libaci.sl shared library into the /opt/omni/lib directory.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 2. Open the EIF-Configuration window by double-clicking the I/O unit icon, and then click the Logical Ranges field. In the text box the available Insert/Eject Areas are listed. NOTE One Data Protector library device can handle only one media type.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device • Enter the Device Name and, below, Description. • In the Client text box choose the DAS Media Agent client from the list that will access ADIC/GRAU robotics. • Choose the GRAU DAS Library in the Device type text box. In the DAS Server enter the hostname of the DAS Server (obtained information during installing DAS Agent). • Choose preferred action from the list for the Busy Drive situation.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device Configuring the indirect access platform requires the same preparatory steps as configuring the direct access platform. You have to create a DAS Client in the C:\DAS\ETC\CONFIG file on the DAS Server computer, install the ADIC/GRAU library in the Data Protector /bin directory, and install and start the Portmapper service.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 3. In the Edit menu, click Find. The Find dialog box appears. Use the appropriate search method to search for media. Entering Media Use this functionality to physically enter media into an ADIC/GRAU DAS repository and automatically register added media as members of the library. 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. 2. In the Scoping Pane, click Devices.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device Adding Media to a Media Pool Adding media to a media pool registers the new media in the IDB as members of this media pool. It is not necessary for these media to actually reside in the DAS repository. To add media to a pool, you have to first initialize them. Initializing media prepares it for use with Data Protector. See “Initializing Media.” You can also import it. See “Importing Media.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device The Medium Size button decides whether Data Protector will Determine the storage size of the medium, or whether you want to Specify the storage size of the medium. You can leave the default, which is Determine. Click Finish. TIP Follow online Help for information on the format wizard. Initializing Multiple 1. In the HP OpenView Storage Data Protector Manager, switch to Media in a Library the Devices & Media context. Device 2.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device Follow online Help for information on specific items in the wizard. 11. Click Finish to confirm and exit the wizard. Querying the ADIC/GRAU DAS Server If you want to get information about a repository in the GRAU DAS library from the Server, you can query the DAS Server. A query responds with the contents of the media database of the DAS Server, and then synchronizes the information in the IDB with what is actually in the repository.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 6. Right-click your selected slots and their media, and then click Verify. See online Help for further information. Scanning Media Use this function to examine the format of selected media. Also see “Scanning Media in a Device” on page 129 for more information. 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. 2. In the Scoping Pane, click Devices.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 6. Change the information that appears in the Results Area. See online Help for further information. NOTE These modifications are made to the IDB, and not to the tape itself. Moving Media Use this function to move media from one media pool to another. When you move media to another media pool, all the media information such as condition, type, medium ID, and session information is transferred to the new media pool.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 2. In the Scoping Pane, click Devices. The list of configured devices will display in the Results Area. 3. In the list of configured devices, click the name of the library, then expand it to display the Drives and Slots items. 4. Select and then right-click the slots that you want to recycle. 5. Click Recycle. See online Help for further information.
ADIC/GRAU DAS and STK ACS Libraries The ADIC/GRAU DAS Library Device 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. The Scoping Pane displays the list of devices and media configured within your cell when you expand the respective item. 2. Expand the Media item and the media pool, and then select the media you want to export. 3. Right-click one of your selections, click Export, and then confirm your decision. The exported media will disappear from the list.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device The STK ACS Library Device The concepts, configuration, and installation of the STK ACS library device are basically the same as the steps necessary to use the ADIC/GRAU DAS device with Data Protector. Refer to the “Data Protector and the ADIC/GRAU DAS Library Device” section for additional reference. The ACS Media Agent does not require the preparation necessary for installation of the DAS Media Agent.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device Connecting Library Drives Physically connect the library drives and robotics to the systems where you intend to install the ACS Media Agent software. See http://www.openview.hp.com/products/datapro/spec_0001.html for details about supported STK libraries.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device • Data Protector has to be installed and configured. See HP OpenView Storage Data Protector Installation and Licensing Guide. • The following information has to be obtained before you start installing the ACS Agent software: ✓ The of the host where ACSLS is running. ✓ A list of ACS drive IDs that you want to use with Data Protector.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device If a CAP is not in manual operating mode, change the mode using the following command: set cap manual ✓ A list of SCSI addresses for the drives, for example, scsi4:0:1:0. For more information on SCSI addresses, see HP OpenView Storage Data Protector Installation and Licensing Guide. Remote Installation The installation procedure consists of the steps: 1.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device You should see the library drives with corresponding device files/SCSI addresses displayed in the list. Installing the ACS Media Agent on a 32-bit HP-UX System Prerequisites The following prerequisites for installation have to be met before installing the ACS Agent on an HP-UX system: • The StorageTek library has to be configured and running. See the documentation that comes with the StorageTek library.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device ACSSA> query cap all The format specification of an ACS CAP has to be the following: ACS CAP: ID:#,#,#,# - (ACS num, LSM num, PANEL, DRIVE). ✓ Make sure that the CAPs that will be used for Data Protector are in the state online and in manual operating mode.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device //acs/ssi/ssi.sh start 4. On UNIX ACS client, run the following command to check whether or not the library drives are properly connected to your system: /opt/omni/lbin/devbra -dev You should see the library drives with corresponding device files/SCSI addresses displayed in the list.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device • Follow the same steps for creating drives as in the indirect library access configuration, but in Advanced Options, make sure to turn off the Force Direct Library Access feature. By default, this feature is on.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device Entering Media Use this functionality to physically enter media into an STK repository and automatically register added media as members of the library. 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. 2. In the Scoping Pane, click Devices. The list of configured devices will display in the Results Area. 3.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device Adding Media to a Media Pool Adding media to a media pool registers the new media in the IDB as members of this media pool. It is not necessary for these media to actually reside in the ACS repository. To add media to a pool, initialize it first. Initializing media prepares it for use with Data Protector. See “Initializing Media.” You can also import it. See “Importing Media.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device The Medium Capacity button defines whether Data Protector will Determine the storage size of the medium, or whether you want to Specify the storage size of the medium. You can leave the default, which is Determine. The Force Initialization button will automatically initialize blank media or media in other formats recognized by Data Protector (tar, cpio, OmniBackI, and so on). You can leave the default value.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device 11. Optionally, use the Medium Capacity button to define whether Data Protector will Determine the storage size of the medium, or whether you want to Specify the storage size of the medium. You can leave the default, which is Determine. 12. Optionally, using the Force Initialization button will automatically initialize blank media or media in other formats recognized by Data Protector (tar, cpio, OmniBackI, and so on).
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. 2. In the Scoping Pane, click Devices. The list of configured devices will display in the Results Area. 3. In the list of configured devices click the name of the library, then expand it to display the Drives and Slots items. 4. Click Slots to display the list of volsers in the Results Area. 5. Select a range of media to scan. 6.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device Moving Media Use this function to move media from one media pool to another. When you move media to another media pool, all the media information such as condition, type, medium ID, and session information is transferred to the new media pool. Getting Information about Media Use this functionality to display detailed information about the usage and condition of an individual selected Data Protector medium. This is a read-only window. 1.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device See online Help for further information. This action queries the ASCLM host for information. Recycling Media Recycling a Data Protector owned media removes protection from data objects contained on the media. A recycled medium can be reused for backup. Also see “Recycling Media” on page 123 for more information. 1. In the HP OpenView Storage Data Protector Manager, switch to the Devices & Media context. 2. In the Scoping Pane, click Devices.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device NOTE If the number of media to be removed at once exceeds fourteen, the media will not be referred to by ID (displayed in the window). You will be asked if you wish to remove that amount of media. Exporting Media This functionality enables you to remove information about backup objects contained on a Data Protector medium from the IDB. Use it when media will no longer be used in a Data Protector cell. The media contents remain unchanged. 1.
ADIC/GRAU DAS and STK ACS Libraries The STK ACS Library Device Observe messages generated during the process in the Library Management window.
ADIC/GRAU DAS and STK ACS Libraries Troubleshooting Library Installation and Configuration Troubleshooting Library Installation and Configuration Installation Steps 1. Install the DAS Media Agent on the system controlling the GRAU robotics (PC/robot). 2. Install the DAS Media Agent on the NT PCs where a drive is connected (PC/drive). 3. Copy aci.dll + winrpc.dll + ezrpcw32.dll to winnt\system32 and \bin directory. 4. Create aci directory on PC/robot. 5. Copy dasadmin.
ADIC/GRAU DAS and STK ACS Libraries Troubleshooting Library Installation and Configuration (or: dasadmin dismount -d ) where = DATA_PROTECTOR and for example = 001565 and is for example = DLT7001 and "all" stands for "allocate" If you are not successful with these commands (communication to DAS Server (OS/2), try to execute these commands on the OS/2 PC. You can find the dasadmin command in/das/bin/.
ADIC/GRAU DAS and STK ACS Libraries Troubleshooting Library Installation and Configuration pol 9 for STK The default media type is DLT.
ADIC/GRAU DAS and STK ACS Libraries Troubleshooting Library Installation and Configuration 700 Chapter 14
A Further Information Appendix A A-1
Further Information In This Appendix In This Appendix This chapter gives information on the following topics: “Backing Up and Restoring UNIX Specifics” on page A-3 “Data Protector Commands” on page A-7 “Performance Considerations” on page A-8 “Example of Scheduled Eject of Media” on page A-14 “Examples of Pre-Exec and Post-Exec Commands for UNIX” on page A-20 “Disaster Recovery: Move Kill Links on HP-UX 11.x” on page A-25 “Creating a libaci.
Further Information Backing Up and Restoring UNIX Specifics Backing Up and Restoring UNIX Specifics This section explains how to backup specific UNIX formats, including VxFS, Enterprise Filesystems, and Context Dependent Filesystems. VxFS Snapshot What Is VxFS? VxFS allows you to back up a filesystem while it is being used by some other application. This is called an online backup and is done by creating a snapshot of a filesystem and backing up this snapshot.
Further Information Backing Up and Restoring UNIX Specifics If the amount of data modified on the snapped filesystem is higher than the space available, Data Protector produces Cannot stat error messages for all the remaining files to be backed up. You must unmount the snapshot filesystem and repeat the backup procedure. 2. Create a temporary directory to which you will mount the snapshot filesystem. 3. Create shell scripts to mount and unmount the snapshot filesystem to the temporary directory.
Further Information Backing Up and Restoring UNIX Specifics # snapping the same FS will cause the Pre-exec script to fail and # a DA to abort # # 2) an attempt to mount an already mounted snapshot FS, # snapping some other FS will cause a warning to be generated, # script to fail and a DA to abort # # 3) a synchronization with the Post-exec script should be also # provided because the snapshot FS must not be unmounted while # there is other DA reading from the FS.
Further Information Backing Up and Restoring UNIX Specifics # - a block special file of the snapshot FS # # NOTE # In case of multiple Disk Agents reading from the same snapshot # FS, a kind of synchronization mechanism has to be added for # the following reasons: # # 1) Post-exec script should unmount snapshot FS only if there # is no other DA reading from the snapshot FS # # Success/failure of the DA can be checked by examining # the BDACC environment variable # MOUNT_POINT=$1 umount -v $MOUNT_POINT # #
Further Information Data Protector Commands Data Protector Commands For a complete list of supported Data Protector commands, refer to the HP OpenView Storage Data Protector Command Line Interface Reference (CLIReference.pdf) or the omniintro man page on UNIX. The HP OpenView Storage Data Protector Command Line Interface Reference is located in the \docs\MAN directory on Windows or in the /opt/omni/doc/C/ directory on UNIX.
Further Information Performance Considerations Performance Considerations This section gives an overview of the most common backup performance factors. It is not meant to discuss performance. Due to the high number of variables and permutations, it is not possible to give distinct recommendations that fit all user requirements and affordable investment levels. Further discussions can be found in the HP OpenView Storage Data Protector Concepts Guide.
Further Information Performance Considerations The speed also varies if a device-compression gets used. The achievable compression ratio depends on the nature of the data being backed up. For most cases, using high speed devices with device-compression ON does improve performance. This however is true only if the device(s) stream. Libraries offer additional advantages because of their fast and automated access to a large number of media.
Further Information Performance Considerations • Load Balancing: This is where Data Protector dynamically determines which filesystem should be backed up to which device. Normally, it is best to enable this feature. This is especially true when a large number of filesystems in a dynamic environment are being backed up. Configuring Backups and Restores Any given infrastructure must be used efficiently in order to maximize performance.
Further Information Performance Considerations NOTE By default, software compression should be disabled. Software compression should only be used for backup of many systems over a slow network where the data can be compressed before sending it over the network. If software compression is used, hardware compression should be disabled since trying to compress data twice actually expands the data.
Further Information Performance Considerations Image Backup Versus Filesystem It used to be more efficient to back up images (raw volumes) instead of backing up filesystems. This can still be true in some cases, such as with heavily-loaded systems or if the disks contain a large number of scattered files. The general recommendation is to use the filesystem backup.
Further Information Performance Considerations If you suspect that the sustained data flow to the tape device is too low or that the device does not handle it correctly, you can simulate a very fast device on the Media Agent client by doing the following: 1. Create a standalone file device and a device file /dev/null on UNIX and nul on Windows. 2. Create a separate pool and select loose policy. 3. Set InitOnLoosePolicy=1 and set data protection to None.
Further Information Example of Scheduled Eject of Media Example of Scheduled Eject of Media You might want to eject all media that were used for backup during the night every morning at 6.00 AM. To schedule such an operation proceed as follows: Schedule the Report Group 1. In the Data Protector GUI, select Reporting. 2. In the Scoping Pane expand Reporting and right click Reports. Select Add Report Group. The Add Report Group wizard is displayed. 3. In the wizard, name your report group and click Next.
Further Information Example of Scheduled Eject of Media given in the next section. The script (HP-UX and Solaris systems) or the starting batch file (Windows systems) must reside in the /opt/omni/lbin (HP-UX and Solaris systems) or \bin (Windows systems) directory. On Windows systems, the contents of the batch file containing command for starting the script is: \perl.exe "\bin\omnirpt_eject.pl" 6. Click the >> button to add this recipient. Click Finish.
Further Information Example of Scheduled Eject of Media $report =`"${OMNIBIN}omnimm" -eject \"$lib\" $slots`; #print "\debug>\n$report\n
Further Information Example of Scheduled Eject of Media while (($lib, $slot) = each(%List)) { $result |=&Library_Eject($lib,$slot); } if ($result) { return (1); } else { print "[Normal] All operations successfully completed.
Further Information Example of Scheduled Eject of Media if (!keys(%List)) { print "[Warning] No tape(s) to eject.
Further Information Example of Scheduled Eject of Media print "[Normal] Starting eject of media that have been used in the last 24 hours.
Further Information Examples of Pre-Exec and Post-Exec Commands for UNIX Examples of Pre-Exec and Post-Exec Commands for UNIX The following scripts are some examples of Pre- and Post- exec commands on UNIX. Session Pre-Exec: The script shuts down an Oracle instance.
Further Information Examples of Pre-Exec and Post-Exec Commands for UNIX else echo "Failed to unmount the disk --> ABORTED!" exit 1 fi Filesystem Pre-Exec: Report Usage of the Filesystem #!/bin/sh echo "==================================================" fuser -cu /var/application_mount_point echo "==================================================" exit 0 Session Post-Exec: Application Startup This example Post-exec script will start up the Oracle database.
Further Information Examples of Pre-Exec and Post-Exec Commands for UNIX fi Disk Image Post-Exec: Mount a Disk After the Raw Volume Backup #!/bin/sh if [ $BDACC != 0] then echo "Backup could not read the disk!" echo "Disk will not be automatically mounted!" fi echo "The disk will be now mounted!" mount /dev/vg05/lvol2 /disk_with_many_files if [ $? = 0 ] then echo "Disk successfully mounted!" exit 0 else echo "Failed to mount disk!" exit 1 fi Filesystem Post-Exec: Log Backup for the Record #!/bin/sh if
Further Information Examples of Pre-Exec and Post-Exec Commands for UNIX Session Post-Exec: Notify User #!/bin/sh /opt/omni/bin/omnirpt -report single_session -session $SESSIONID | \ mailx -s "Report for $SESSIONID" $OWNER Session Post-Exec: Start Another Backup #!/bin/sh # First check how the current backup finished if [ $SMEXIT != 0 -o $SMEXIT != 10 ] then echo "Backup not successful --> next backup will not be started!" exit 0 fi if [ $RESTARTED != 0 ] then echo "Restarted backup --> next backup wil
Further Information Examples of Pre-Exec and Post-Exec Commands for UNIX then echo "Restarted backup --> backup will not be restarted!" exit 0 fi /opt/omni/bin/omnib -restart $SESSIONID -no_mon exit 0 A-24 Appendix A
Further Information Disaster Recovery: Move Kill Links on HP-UX 11.x Disaster Recovery: Move Kill Links on HP-UX 11.x Proceed as shown below on the system which you want to back up to move some links: # The system will go from "run-level" 4 to "run-level 1" # retaining the inetd, networking, swagentd services up. The state is called "minimum activity" for backup purposes (need networking). # IMPORTANT: ensure the links are present in /sbin/rc1.d before # moving and they do have this exact name.
Further Information Creating a libaci.o on AIX Creating a libaci.o on AIX OmniBack II On AIX, Data Protector DAS Agent uses the object module libaci.o to A.03.10 and Earlier access ADIC/GRAU system. This object module has to be created from the library archive file libaci.a, that is delivered by the vendor of ADIC/GRAU system. 1. Create the file libaci.exp containing the list of modules used by Data Protector DAS Agent: #! /usr/omni/lib/libaci.
Further Information Creating a libaci.o on AIX #! /usr/omni/lib/libaci.a aci_initialize aci_qversion aci_init d_errno aci_view aci_drivestatus aci_drivestatus2 aci_driveaccess aci_mount aci_dismount aci_qvolsrange aci_eject_complete aci_eject aci_insert 2. Create the object module libaci.o by executing following command: ld -L/usr/omni/lib -bM:SRE -e_nostart -lc -bE:/libaci.exp /libaci.a -o libaci.o is the path to the directory where the library archive file libaci.
Further Information Example of the Package Configuration File Example of the Package Configuration File This section gives an example of a package configuration file that you need to modify while configuring Data Protector Cell Manager package in an MC/ServiceGuard environment: ************************************************************** ******** # ****** HIGH AVAILABILITY PACKAGE CONFIGURATION FILE (template) ******* # ************************************************************** ******** # ******* Not
Further Information Example of the Package Configuration File # Enter the failover policy for this package. This policy will be used # to select an adoptive node whenever the package needs to be started. # The default policy unless otherwise specified is CONFIGURED_NODE. # This policy will select nodes in priority order from the list of # NODE_NAME entries specified below. # # The alternative policy is MIN_PACKAGE_NODE.
Further Information Example of the Package Configuration File # move the package back to its primary node whenever the primary node # is capable of running the package. FAILBACK_POLICY MANUAL # Enter the names of the nodes configured for this package. Repeat # this line as necessary for additional adoptive nodes. # Order IS relevant. first Put the second Adoptive Node AFTER the # one.
Further Information Example of the Package Configuration File # execution of each script. # Note: The HALT_SCRIPT_TIMEOUT should be greater than the sum of # all SERVICE_HALT_TIMEOUT specified for all services. RUN_SCRIPT /etc/cmcluster/ob2cl/ob2cl.cntl RUN_SCRIPT_TIMEOUT NO_TIMEOUT HALT_SCRIPT /etc/cmcluster/ob2cl/ob2cl.cntl HALT_SCRIPT_TIMEOUT NO_TIMEOUT # Enter the SERVICE_NAME, the SERVICE_FAIL_FAST_ENABLED and the # SERVICE_HALT_TIMEOUT values for this package.
Further Information Example of the Package Configuration File # specified SERVICE_HALT_TIMEOUT, the cluster software will send # out the SIGKILL signal to the service to force its termination. # This timeout value should be large enough to allow all cleanup # processes associated with the service to complete. If the # SERVICE_HALT_TIMEOUT is not specified, a zero timeout will be # assumed, meaning the cluster software will not wait at all # before sending the SIGKILL signal to halt the service.
Further Information Example of the Package Configuration File # the subnets defined goes down, the package will be switched to another # node that is configured for this package and has all the defined subnets # available. SUBNET 10.17.0.0 # The keywords RESOURCE_NAME, RESOURCE_POLLING_INTERVAL, # RESOURCE_START, and RESOURCE_UP_VALUE are used to specify Package # Resource Dependencies.
Further Information Example of the Package Configuration File # If DEFERRED is selected, ServiceGuard will not attempt to start # resource monitoring for these resources during node start up. User # should specify all the DEFERRED resources in the package run script # so that these DEFERRED resources will be started up from the package # run script during package run time. # # RESOURCE_UP_VALUE requires an operator and a value. defines # the resource 'UP' condition.
Further Information Example of the Package Configuration File # for the first operator, and only < or <= may be used for the second operator. # For example, # Resource is up when its value is # -------------------------------# RESOURCE_UP_VALUE = 55 (threshold) # RESOURCE_UP_VALUE > 5.1greater than 5.1 # RESOURCE_UP_VALUE (range) > -5 and < 10between -5 and 10 (threshold) # # Note that "and" is required between the lower limit and upper limit # when specifying a range.
Further Information Example of the Package Configuration File # Uncomment the following lines to specify Package Resource Dependencies. # #RESOURCE_NAME #RESOURCE_POLLING_INTERVAL #RESOURCE_START #RESOURCE_UP_VALUE ] [and # The default for PKG_SWITCHING_ENABLED is YES. In the event of a # failure, this permits the cluster software to transfer the package # to an adoptive node. Adjust as necessary.
Further Information Example of the Package Configuration File NODE_FAIL_FAST_ENABLEDNO Appendix A A-37
Further Information Example of the Package Control File Example of the Package Control File This section gives an example of a package control file that you need to modify while configuring Data Protector Cell Manager package in an MC/ServiceGuard environment: ************************************************************** ******** # * * #* * HIGH AVAILABILITY PACKAGE CONTROL SCRIPT (template) # * * #* * Note: This file MUST be edited before it can be used.
Further Information Example of the Package Control File # # Uncomment the first line (VGCHANGE="vgchange -a e -q n"), and comment # out the default, if your disks are mirrored on separate physical paths, # # Uncomment the second line (VGCHANGE="vgchange -a e -q n -s"), and comment # out the default, if your disks are mirrored on separate physical paths, # and you want the mirror resynchronization to occur in parallel with # the package startup.
Further Information Example of the Package Control File # VG[0]=vg01 # VG[1]=vg02 # # The volume group activation method is defined above. The filesystems # associated with these volume groups are specified below. # VG[0]=/dev/vg_ob2cm # FILESYSTEMS # Specify the filesystems which are used by this package. Uncomment # LV[0]=""; FS[0]=""; FS_MOUNT_OPT[0]="" and fill in the name of your first # logical volume, filesystem and mount option for the file system.
Further Information Example of the Package Control File # filesystem will be fsck'd prior to being mounted. The filesystems will be # mounted in the order specified during package startup and will be unmounted # in reverse order during package shutdown. Ensure that volume groups # referenced by the logical volume definitions below are included in # volume group definitions above.
Further Information Example of the Package Control File # 192.10.25.0 enter: # IP[0]=192.10.25.12 # SUBNET[0]=192.10.25.0 # (netmask=255.255.255.0) # # Hint: Run "netstat -i" to see the available subnets in the Network field. # # IP/Subnet address pairs for each IP address you want to add to a subnet # interface card. on the same Must be set in pairs, even for IP addresses # subnet. # IP[0]=10.17.3.230 SUBNET[0]=10.17.0.0 # SERVICE NAMES AND COMMANDS.
Further Information Example of the Package Control File # # SERVICE_NAME[1]=pkg1b # SERVICE_CMD[1]="/usr/bin/X11/xload -display 192.10.25.54:0" # SERVICE_RESTART[1]="-r 2" service twice. # Will restart the # # SERVICE_NAME[2]=pkg1c # SERVICE_CMD[2]="/usr/sbin/ping" # SERVICE_RESTART[2]="-r 1" # Will restart the service an infinite # number of times. # # Note: No environmental variables will be passed to the command, this # includes the PATH variable.
Further Information Data Protector Log Files Example Entries Data Protector Log Files Example Entries This section provides some typical Data Protector messages that are logged to in some Data Protector log files. This section does not intended to provide further in-depth information on troubleshooting. For a complete list of Data Protector log files and for more in formation on them refer to “Data Protector Log Files” on page 550.
Further Information Data Protector Log Files Example Entries 03/02/00 09:36:51 INET.26130.0 ["/src/lib/ipc/ipc.c /main/r31_split/10":6920] A.03.10 b325 IpcGetPeer: Could not expand ConnectionIP "10.17.6.227" 03/16/00 19:09:42 BSM.13152.0 ["src/db/cdb/cdbwrap.c /main/84":1538] A.03.10 bPHSS_21234/PHSS_21235 DB[1] internal error [-2009] The session is disconnected 05/17/01 12:00:30 OMNIMM.7515.0 ["lib/cmn/obstr.c /main/17":187] A.04.00.
Further Information Data Protector Log Files Example Entries 5/14/01 12:41:41 PM OMNIDBUTIL.98.124 ["db/vel_cls_spec.c /main/39":103] A.04.00.%B3 b335 VELOCIS DB ERROR [0] internal error [-2005] Server unavailable sm.log 3/28/00 03:00:01 BSM.23475.0 ["/src/sm/bsm2/brsmutil.c /main/r31_split/4":630] A.03.50.%B2 b158 Error connecting to database. Code: 1166. 03/27/01 08:17:06 BSM.2709.0 ["sm/bsm2/bsmutil.c /main/502":3306] A.04.00.%B1 b281 Error opening datalist OMNIBACK-. inet.
Further Information Data Protector Log Files Example Entries 02/04/00 13:38:56 0a110210:389ac85b:3c6e:0001 "[CBF502] DLT_ARC_8" [INITIALIZATION] 02/29/00 16:04:25 0a110210:38bbdff4:6d85:0026 "NULL_33" [AUTOINITIALIZATION] 03/02/00 10:03:25 0a110210:385a24bf:410b:0002 "[CW1231] BMW_DLT_15" [IMPORT] upgrade.log 03/15/01 09:15:38 UCP session started. 03/15/01 09:20:55 UCP session finished. total running time: 317 seconds 03/15/01 10:00:09 UDP session started.
Further Information Data Protector Log Files Example Entries 03/15/01 12:40:43 Database check error! Can not proceed with upgrade. 03/15/01 13:24:15 System error 03/15/01 13:24:15 Session was aborted by child ASM, marked error=1026 03/15/01 15:27:22 OmniBack II 3.x database not found. 03/15/01 16:33:19 [12:10904] Open of detail catalog binary file failed. 03/16/01 08:39:31 Internal error: Invalid Ct function argument specified. 03/20/01 10:56:57 [12:1165] Database network communication error.
Further Information Windows Manual Disaster Recovery Preparation Template Windows Manual Disaster Recovery Preparation Template The template on the next page can be used to prepare for Windows Assisted Manual Disaster Recovery, as described in the Chapter 10, “Disaster Recovery,” on page 435.
Further Information Windows Manual Disaster Recovery Preparation Template Table A-1 client properties computer name hostname drivers Windows Service Pack TCP/IP properties IP address default gateway subnet mask DNS order medium label / barcode number partition information and order 1st disk label 1st partition length 1st drive letter 1st filesystem 2nd disk label 2nd partition length 2nd drive letter 2nd filesystem 3rd disk label 3rd partition length 3rd drive letter 3rd filesystem A-50 Appendix A
Further Information Changing Block Size on Windows Media Agent Changing Block Size on Windows Media Agent In order to increase the maximum block size on a Windows Media Agent client, you have to modify its Registry. After modifying the Registry, restart the computer. Drivers read MaximumSGList at boot time.
Further Information Changing Block Size on Windows Media Agent A-52 Appendix A
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.
Glossary (disk partitioning and logical volume configuration) and automatic recovery of the original system configuration and user data that was backed up during the full client backup. You need these diskettes to perform ASR. autochanger See library autoloader See library BACKINT (SAP R/3 specific term) SAP R/3 backup programs can call the Data Protector backint interface program via an open interface, which enables them to communicate with Data Protector software.
Glossary specified in a backup specification or an interactive session. All clients configured in one backup specification are backed up together in one backup session using the same backup type (full or incremental). The result of a backup session is a set of media, which was written to, also called the backup or media set. See also incremental backup and full backup. backup set See media set.
Glossary BC (HP StorageWorks Disk Array XP specific term) The Business Copy XP allows to maintain internal copies of HP StorageWorks Disk Array XP LDEVs for purposes such as data backup or data duplication. The copies (secondary volumes or S-VOLs) can be separated from the primary volumes (P-VOLs) and connected to a different system for various purposes, such as backup and development.
Glossary EMC Symmetrix SLDs that need to be protected. See also BC and BC Process. boolean operators The boolean operators for the full text search functionality of the online Help system are AND, OR, NOT, and NEAR. Used when searching, they enable you to define your query precisely by creating a relationship between search terms. If no operator is specified in a multi-word search, AND is used by default. For example, the query manual disaster recovery is equivalent to manual AND disaster AND recovery.
Glossary for purposes such as data duplication, backup, and disaster recovery. CA operations involve the main (primary) disk arrays and the remote (secondary) disk arrays. The main disk arrays contain the CA primary volumes (PVOLs), which contain the original data and are connected to the application system. The remote disk arrays contain the CA secondary volumes (S-VOLs) connected to the backup system.
Glossary allocate licenses to specific cells to suit your needs. See also MoM. Centralized Media Management Database (CMMDB) See CMMDB. channel (Oracle specific term) An Oracle8/9 Recovery Manager resource allocation. Every allocated channel starts a new Oracle8/9 process, which performs backup, restore, and recovery actions.
Glossary environment. One cell can control the robotics, serving the devices that are connected to systems in other cells. The CMMDB must reside on the MoM Manager. A reliable network connection between the MoM cell and the other Data Protector cells is highly recommended See also MoM. COM+ Registration Database The COM+ Registration Database and the Windows Registry store COM+ application attributes, class attributes, and computer-level attributes.
Glossary users who are granted the Reporting and notifications user rights. You can view or delete all events in the Event Log. Data Protector user account You can use Data Protector only if you have a Data Protector user account, which restricts unauthorized access to Data Protector and to backed up data. Data Protector administrators create this account specifying a user logon name, the systems from which the user can log on, and a Data Protector user group membership.
Glossary delta backup A delta backup is a backup containing all the changes made to the database from the last backup of any type. See also backup types device A physical unit which contains either just a drive or a more complex unit such as a library. device chain A device chain consists of several standalone devices configured for sequential use. When a medium in one device gets full, the backup automatically continues on a medium in the next device in the device chain.
Glossary direct backup A SAN-based backup solution in which data movement directly from disk to tape (or to other secondary storage) is facilitated by the SCSI Extended Copy (Xcopy) command. Direct backup lessens the backup I/O load on systems in a SAN environment. The data movement is facilitated directly from disk to tape (or to other secondary storage) by the SCSI Extended Copy (XCopy) command.
Glossary disk group (Veritas Volume Manager specific term) The basic unit of data storage in VxVM system. A disk group can consist of one or more physical volumes. There can be more than one disk group on the system. disk image (rawdisk) backup A high-speed backup where Data Protector backs up files as bitmap images. A disk image (rawdisk) backup does not track the files and directory structure stored on the disk, but stores a disk image structure on byte level.
Glossary system restore along with the target operating system configuration data. It is deleted after the target system is restored to the original system configuration. Active DR OS not only hosts the Data Protector disaster recovery process but is also a part of the restored system because it replaces its own configuration data with the original configuration data.
Glossary Protector cells which are managed and administered from a central cell using the Manager-of-Managers concept. See also MoM. EVA Agent (HP StorageWorks Enterprise Virtual Array specific term) A Data Protector software module that executes all tasks required for the HP StorageWorks Enterprise Virtual Array snapshot integration on the application system and the backup system. It communicates with the HSV Element Manager to control the HP StorageWorks Enterprise Virtual Array.
Glossary interface while on the other side there are parallel SCSI ports. The bridge or multiplexer enables SCSI packets to be moved between the Fibre Channel and parallel SCSI devices. File Replication Service (FRS) A Windows service that replicates the domain controller store logon scripts and group policies. FRS also enables replication of Distributed File System (DFS) shares between systems and allows any server to perform replication activity.
Glossary full database backup A backup of all data in a database regardless of whether it has changed after the last database backup was created. This means that the full database backup does not depend on any other backup media. full mailbox backup A full mailbox backup is a backup of the entire mailbox content. global options file A file that allows you to customize Data Protector.
Glossary hosting system A working Data Protector client used for Disk Delivery Disaster Recovery with a Data Protector Disk Agent installed. HP ITO See OVO. HP OpC See OVO. HP OpenView SMART Plug-In (SPI) A fully integrated, out-of-the-box solution which "plugs into" HP OpenView Operations, extending the managed domain.
Glossary an internal cache memory, and control and diagnostic software commonly referred to as the microcode. IDB The Data Protector Internal Database is an embedded database located on the Cell Manager that keeps information regarding which data is backed up, on which media it is backed up, how backup and restore sessions are run, and which devices and libraries are configured. importing media A process that re-reads all data about backup sessions which are on the medium back into the IDB.
Glossary device during the time of the original pair split, and the data that was written to the standard device during the split is overwritten with data from the BCV mirror. In SRDF control operations, an incremental restore reassigns a target (R2) device as the next available mirror of the source (R1) device in the pair.
Glossary software packages for a specific architecture. The Installation Server is used for remote installation of Data Protector clients. In mixed environments at least two Installation Servers are needed: one for UNIX systems and one for Windows systems. used in environments where all clients support trusted connections. Connections validated by Windows Server and accepted by Microsoft SQL Server are referred to as trusted connections. Only trusted connections are allowed.
Glossary LBO (EMC Symmetrix specific term) A Logical Backup Object (LBO) is an object of data storage/retrieval in the EMC Symmetrix environment. It is stored/retrieved by EMC Symmetrix as one entity and can only be restored as a whole. 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.
Glossary The lock name is a user specified string that is used for locking all such device configurations to prevent collision if several such devices (device names) are used concurrently. log_full shell script (Informix UNIX specific term) A script provided by ON-Bar that you can use to start backing up logical-log files when OnLine Server issues a logfull event alarm. The Informix ALARMPROGRAM configuration parameter defaults to the /etc/log_full.
Glossary connect to an operating system or software application. The password has to be the same as the password specified in the Oracle password file (orapwd), which is used for authentication of users performing database administration. • is the name used to identify an SQL*Net server process for the target database.
Glossary StorageWorks Disk Array XP specific term) and HP StorageWorks Disk Array XP LDEV. Manager-of-Managers (MoM) See Enterprise Cell Manager. Media Agent A process that controls reading from and writing to a device, which reads from or writes to a medium (typically a tape). During a backup session, the Media Agent receives data from the Disk Agent and sends it to the device for writing it to the medium.
Glossary media pool A set of media of the same type (such as DDS) used and tracked as a group. Media are formatted and assigned to a media pool. media set The result of a backup session is data backed up on a group of media called media set. Depending on the media usage policy, several sessions can share the same media. media type The physical type of media, such as DDS or DLT. media usage policy The media usage policy controls how new backups are added to the already used media.
Glossary Microsoft Volume Shadow Copy service (VSS) A software service that provides a unified communication interface to coordinate backup and restore of a VSSaware application regardless of its specific features. This service collaborates with the backup application, writers, shadow copy providers, and the operating system kernel to implement the management of volume shadow copies and shadow copy sets. See also shadow copy, shadow copy provider, writer.
Glossary MU number (HP StorageWorks Disk Array XP specific term) A Mirror Unit number is an integer number (0, 1 or 2), used to indicate a first level mirror. See also first level mirror. multi-drive server A license that allows you to run an unlimited number of Media Agents on a single system. This license, which is bound to the IP address of the Cell Manager, is no longer available. obdrindex.dat An IDB file with information about IDB backups, media, and devices used for the backup.
Glossary On-Bar (Informix specific term) A backup and restore system for OnLine Server. ON-Bar enables you to create a copy of your OnLine Server data and later restore the data. The ON-Bar backup and restore system involves the following components: • onbar utility • Data Protector, as the backup solution • XBSA interface • ON-Bar catalog tables, which are used to back up dbobjects and track instances of dbobjects through multiple backups.
Glossary Oracle instance (Oracle specific term) Each installation of an Oracle database on one or more systems. One computer system can have several instances of a database running. ORACLE_SID (Oracle specific term) A unique name for an Oracle Server instance. To switch among Oracle Servers, specify the desired . The is included in the CONNECT DATA parts of the connect descriptor in a TNSNAMES.ORA file and in the definition of the TNS listener in the LISTENER.ORA file.
Glossary called IT/Operation, Operations Center and Vantage Point Operations. See also merging. various status values depending on the action performed on it. The three most important status values are: ownership The ownership of a backup determines who can restore from the backup. The user who starts an interactive backup is the session owner. If a user starts an existing backup specification without modifying it, the session is not considered interactive.
Glossary data for multiple objects selected for restore is read from media at the same time, thereby improving performance. parallelism The concept of reading multiple data streams from an online database. physical device A physical unit that contains either a drive or a more complex unit such as a library. post-exec A backup option that executes a command or script after the backup of an object or after the entire session completes. Post-exec commands are not supplied by Data Protector.
Glossary public folder store (MS Exchange 2000 Server specific term) The part of the Information Store that maintains information in public folders. A public folder store consists of a binary rich-text .edb file and a streaming native internet content .stm file.
Glossary Manager and manages the IDB. The process is started when Data Protector is installed on the Cell Manager. and network configuration). This information is needed for disaster recovery. Recovery Catalog (Oracle specific term) A set of Oracle8/9 tables and views that are used by Recovery Manager to store information about Oracle8/9 databases. This information is used by Recovery Manager to manage the backup, restore, and recovery of Oracle8/9 databases.
Glossary configuration. In bidirectional configurations, the RCU can act as an MCU. Removable Storage Management Database (Windows specific term) A Windows service used for managing removable media (such as tapes and disks) and storage devices (libraries). Removable Storage allows applications to access and share the same media resources. reparse point (Windows specific term) A system-controlled attribute that can be associated with any directory or file.
Glossary of replica storage versions that are to be kept on a disk array before the oldest replica storage version for the backup specification is reused. See also replica storage rotation.
Glossary device if someone has manually manipulated media without using Data Protector to eject or enter, for example. Scheduler A function that controls when and how often automatic backups occur. By setting up a schedule, you automate the start of backups. Secondary Volume (S-VOL) (HP StorageWorks Disk Array XP specific term) Secondary Volumes, or S-VOLs, are XP LDEVs that act as a secondary CA or BC mirror of another LDEV (a P-VOL).
Glossary shared disks A Windows disk on another system that has been made available to other users on the network. Systems with shared disks can be backed up without a Data Protector Disk Agent installed. SIBF The Serverless Integrations Binary Files (SIBF) is a part of the IDB that stores raw NDMP meta data. This data is necessary to perform restore of NDMP objects. slot A mechanical position in a library. Each slot can hold a medium, such as a DLT tape. Data Protector references each slot with a number.
Glossary split mirror backup (HP StorageWorks Disk Array XP specific term) See ZDB tape backup, ZDB disk/tape backup and ZDB disk backup. split mirror restore (HP StorageWorks Disk Array XP specific term) A process where data backed up using the ZDB tape backup or ZDB disk/tape backup process is restored from tape media to the replica storage version selected by the replica rotation process or by the user. The replica storage version is then synchronized to the original storage.
Glossary address for each backup drive connected to that client. A single SCSI entry is required for a single-drive device and multiple SCSI entries are required for a multi-drive library device. 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.
Glossary Symmetrix Application Programming Interface (SYMAPI) (EMC Symmetrix specific term) A linkable library of functions that can interface with EMC Symmetrix units attached to the Data Protector clients. Provided by EMC. unload correct backup devices when Oracle issues a backup or restore request.
Glossary server is a domain controller, Active Directory directory services and the Sysvol directory are also contained in the System State data. If the server is running the Cluster service, the System State data also includes resource registry checkpoints and the quorum resource recovery log, which contains the most recent cluster database information. system volume/disk/partition A volume/disk/partition containing operating system files.
Glossary Terminal Services (Windows specific term) Windows Terminal Services provide a multi-session environment that allows clients to access a virtual Windows desktop session and Windows-based programs running on the server. thread (MS SQL Server 7.0/2000 specific term) An executable entity that belongs to only one process. It comprises a program counter, a user-mode stack, a kernel-mode stack, and a set of register values. Several threads can run at a time within one process.
Glossary archiving of transaction logs should be enabled to prevent you from losing the transaction log files that are created after the last IDB backup and are necessary for IDB recovery. transaction log table (Sybase specific term) A system table in which all changes to the database are automatically recorded. TSANDS.CFG file (Novell NetWare specific term) A file that allows you to specify the names of containers where you want backups to begin.
Glossary 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. virtual disk (HP StorageWorks Enterprise Virtual Array specific term) A unit of storage allocated from an HP StorageWorks Enterprise Virtual Array storage pool.
Glossary volume mountpoint (Windows specific term) An empty directory on a volume that can be used to mount another volume. The volume mount point acts as a gateway to the target volume. Provided that the volume is mounted, users and applications can refer to the data on the mounted volume by the full (merged) filesystem path as if both volumes are one integral part. Volume Shadow Copy service See Microsoft Volume Shadow Copy service. VPO See OVO. VSS See Microsoft Volume Shadow Copy service.
Glossary that write persistent information on a volume. Writers also participate in the shadow copy synchronization process by assuring data consistency. XBSA interface (Informix specific term) The onbar utility and Data Protector communicate with each other through the X/Open Backup Specification Services Programmer's Interface (XBSA).
Glossary ZDB part of the IDB (ZDB specific term) A part of the IDB, storing ZDB related information such as original and replica storage versions, security information and other. The ZDB part of the IDB is used for ZDB, instant recovery, and split mirror restore. See also zero downtime backup (ZDB).
Glossary G-48
Index Index A aborting all sessions, 623 backup session during the size determination, 312 running sessions, 312 sessions, elapsed time, 625 sessions, using ID, 624 user right, 84 access points Enterprise Event ID, 650 Generic Event ID, 651 graphical user interface (GUI), 652 log files, 652 SNMP traps, 649 SNMP traps format, 651 Specific Event ID, 651 system and management applications, 649 variables, 651 Windows Application Log, 652 access rights for Data Protector users, 83 accessing Event Log functiona
Index cluster (MC/SG), 638 cluster (MSCS), 619 CONFIGURATION, 176 DHCP Server, 178 direct backup environment, 204 disk image, UNIX, 166 disk image, Windows, 190 disks, using NFS, 164 DNS Server, 178 event logs, 183 event logs, Windows, 182 IDB , 398 MC/ServiceGuard local disks, 639 MC/ServiceGuard shared disks, 639 Microsoft Cluster Server local disks, 620 Microsoft Cluster Server shared disks, 620 NetWare Directory Services, NDS, 199 Novell NetWare Cluster local disks, 642 Novell NetWare Cluster shared dis
Index segment size, 78 shared in the SAN, 44 specifying type and name, figure, 24 streaming, 76 used by multiple applications, locking, 46 using, 17 backup environment setting up, tasks, 15 backup failure preventing, 264 backup files of size object specific option, 243 backup objects, 153 selecting, 168 backup options, 225 catalog, 230 configuring, 211 device, 249 frequently used, 227 list, 236 load balancing, 232 log level, 231 logging files to database , 245 ownership, 235 protection, 228 reconnecting bro
Index concepts, 3 Disk Agent, 3 exporting, 377 importing, 377 importing, MoM, 363 Media Agent, 3 monitoring simultaneously, 314 moving clients, 378 reports on multiple, 315 setting up MoM Manager, 363 Cell Manager checking, 607 concepts, 3 configuring package, MC/ServiceGuard, 633 configuring, MC/ServiceGuard, 628 disaster recovery methods, UNIX, 437 installation, troubleshooting, 589 Manual Disaster Recovery, UNIX, 512 Manual Disaster Recovery, Windows, 487 Microsoft Cluster Server, 618 moving the IDB, 41
Index Novell NetWare Cluster Services, 642 omniclus command, 623 package (MC/SG, Veritas Cluster), 615 primary node, 615 secondary node, 615 switchover, 615 Veritas Cluster, 613 virtual server, 615 cluster-aware applications, 616 cluster-aware backups, 620 CM, MA and DA in the DMZ, 540 CMMDB See Centralized Media Management Database command-line interface (CLI), 11 commands pre- and post-exec, 250 pre- and post-exec examples, A-20 pre- and post-exec, UNIX, 257 pre- and post-exec, Windows, 251 communication,
Index new Microsoft Exchange Profile, 348 notifications, 342, 351 notifications on the Web, 353 notifications, using Web reporting interface, 355 report groups, 335 report groups, using Web reporting interface, 355 reports, 335 reports on the Web, 353 SCSI-II library devices, 29 separate media pools for the different drives, 43 Session Flow report, using CLI, example, 340 SNMP traps, Windows 2000, 333, 350 SNMP traps, Windows NT, 333, 350 stacker devices, 35 stacker devices, example, 35 standalone devices,
Index copying to the Web server, 354 Data Source Integration, 644 database See IDB backup problems, 598 import problems, 598 database configuration See IDB configuration database consistency See IDB consistency database directories See IDB directories Database Purge Needed notification, 346 Database Space Low notification, 346 database troubleshooting See IDB troubleshooting DATALIST, definition, 252 DCDirAllocation global option, 523 deactivating centralized licensing, 376 debug syntax, 555 debug.
Index Disk Delivery method, 459, 507 Enhanced Automated method, 463 logging on after, 514 One Button method, 472 overview, 437 Phase 0, 442 Phase 1, 442 Phase 2, 442 Phase 3, 442 planning, 443 preparing, 443 preparing for, 443 troubleshooting, Windows NT, 514, 515 updating SRD, 445 disaster recovery operating system (DR OS), 440 disaster recovery process overview plan, 443 prepare, 443 recover, 444 disk restoring disk image (rawdisk), 273 Disk Agent buffer size, 79 concepts, 3 device streaming and concurre
Index scheduled eject, 138 elapsed session time, 625 e-mail send method notifications, 348 notifications, creating a new Microsoft Exchange Profile, 348 reports, 331 enabling Direct Access mechanism, 55 dirty drive detection, 63 encode object specific option, 245 encoding changing, GUI, 580 End of Session notification, 347 END_USER_ARCHIVE, 222 Enhanced Automated Disaster Recovery client, Windows NT/2000 , 463 disaster recovery CD, 468 disaster recovery CD ISO image, 463, 468 DR image, 466 DR OS image file,
Index backing up OpenVMS, 201 backing up UNIX, 161 backing up Windows, 168 restore limitations, 278 restoring Novell NetWare, 287 restoring OpenVMS, 291 firewall configurations CM, MA and DA in the DMZ, 540 DA and MA in the DMZ, 535 DA in the DMZ, 538 examples, 535 OB2BAR and MA in the DMZ, 543 firewall environment configuring, 528 limiting port range, 528 overview, 528 port usage in Data Protector, 531 firewall support, 528 examples, 535 limiting port range, 528 port usage in Data Protector, 531 floating d
Index HP-UX and Solaris client disaster recovery methods, 437 HTML report format, 329 I IDB architecture, 384 backing up, 398 backing up Windows Registry, 177 catalog protection, 388 checking consistency, 411 checking size, 410 complete recovery, 421 configuring, 388 configuring backup, 398 corrupted, 421, 422, 423 corruption, 419 directories, location, 391 disabling automatic check, 399 disk space, 389, 397 extending size, 408 fnames.
Index the catalog from media, 114 importing media, 113 in a magazine device, 115 multiple, figure, 114 procedure, 113 Inc backups, definition, 213 Inc1-9 backups, definition, 214 incremental backups, 155 Novell NetWare, 196 selecting, 215 troubleshooting, 580 indirect library access, 47 individual reports, running, using GUI, 338 INET debug on Unix, 557 on Windows, 557 Inet service setting user account, 187 inet.log, 551 informix.
Index limiting port range, firewall environment, 528 list restored files, 295 List of Pools report, 324 load balancing, 232 backup option, 237 local disks backing up MC/ServiceGuard, 639 backing up Microsoft Cluster Server, 620 Novell NetWare Cluster backing up, 642 Veritas Cluster backing up, 640 location of media, 126 lock files during backup object specific option, 245 lock name, 74 defining, 53 summary of device definitions using, figure, 55 locked files, 296, 302 locking backup devices, 74 devices us
Index adding to pool, 107 adding unused to a media pool, 107 adding used to a media pool, 107 allocation policy, 103, 120 appendable , 104 appendable of incrementals only, 105 appending backups to, 117 condition, 120 condition factors, 105, 132 configuration right, 83 configuring library for mixed, 37 copying, 143 copying, automated, 145 customizing information about, 149 description, 127 detection of write-protected, 147 ejecting from a device, 137 entering into a device, 136 exporting from Data Protector,
Index scanning media in a device, 129 searching for and selecting a medium, 135 selecting media for backup, 120 setting data protection, 122 using a pre-allocation list of media for backup , 119 vaulting media, 140 verifying data on a medium , 128 Media Management Database, 385 media pool adding media to, 107 adding unused media to, 107 adding used media to, 107 allocation, 102 concepts, 102 condition factors, 105 condition of, 132 configuration procedure, 102 configuring, 102 configuring separate for the d
Index MSCS See Microsoft Cluster Server multi host support, 32 multiple backup specifications, 155 multiple reports, adding to the report group, 337 N Name Space information restoring, 287 native tape driver, 20 Navigation Tabs, 10 NDS adding objects, 199 backing up, 199 NDS objects restoring, 290 NDS scheme restoring, 290 NetWare restoring filesystems, 287 NetWare Directory Services (NDS) backing up, 199 networking, troubleshooting, 565 client fails, 567 HOST file resolution problem, 567 host name resolut
Index omit deleted files, 294 omniclus, 623 omnirc options overview, 525 usage, 525 variables, 525 omnirc options file, 525 omnirpt generating reports with, 339 omniSRDupdate post-exec script, 446 standalone, 446 OmniStorage, restoring, 276 omnisv.
Index Disk Delivery Disaster Recovery, Windows client, 460 Enhanced Disaster Recovery, Windows NT/2000 client, 466, 475 for disaster recovery, 443 Manual Disaster Recovery, UNIX Cell Manager, 512 media for backup, 100 preparing for a disaster recovery, 443 prerequisites direct backup, 204 preventing backup failure, 264 PREVIEW, definition, 252 primary node, 615 private object who can restore, 235 Private, object specific option, 246 privileges group, 93 user, 83 problems IDB , 402, 404 procedure copying med
Index Enhanced Disaster Recovery, Windows NT/2000 client, 470 One Button Disaster Recovery, Windows NT/2000, 477 recurring backup configuring, 210 recycling media, 123 reducing IDB growth, 405 IDB size, 406 Registry backing up Windows, 177 NT CONFIGURATION, 173 restoring Windows, 282 reliability media condition, 105 RemovableStorageManagementDatabase, 174 removing backup devices, 72 user groups, 88 users, 90 renaming backup devices, 73 reparse points, 170, 171 report groups adding multiple reports to, 337
Index protection attributes, 296 sparse files, 296 target hostname, 294 time attributes, 296 restoring bindery, Novell NetWare, 288 data to different client, 299 DHCP Server, 286 direct backup, 205 disk images, 273 file ownerships and trustees, 288 files from media , 301 files in parallel, 300 files in use, 302 files to different paths, 299 from media copy, 144 from media in a vault, 141 IDB , 414 individual files to different paths, 299 Name Space information, 287 NDS scheme, 290 Novell NDS, 289 Novell Net
Index Scoping Pane, 10 SCSI address, 29 SCSI ID library device, 29 SCSI-II Library devices SCSI address, 29 searching for media, 135 secondary node, 615 see private objects, 85 segment size restore speed, 78 selecting backup objects, 168 Direct Access, figure, 56 media, 120 media for backup, 120 media for backup, table, 121 medium, 135 medium, procedure, 135 send methods, notifications, 347 broadcast message, 349 e-mail, 348 Event Log, 351 external, 351 log to file, 349 SNMP, 349 use report group , 351 send
Index pre- and post-exec commands, 250, 255 Specific Event ID, 651 specific object, 225 specifying pathname for a file device, figure, 28 type and name of the backup device, figure, 24 stacker devices backup and restore with, 36 configuring, 35 configuring, example, 35 scanning, verifying and formatting, 35 standalone devices chains, 24 configuring, 23 mount request for, 581 troubleshooting, 581 start backup specification user right, 84 starting daemons, 571 daemons, problems, 571 failed backup, 266 GUI, U
Index troubleshooting file, 562 user interface, 590 when the user interface not accessible, 562 troubleshooting backup sessions mount request for a library device, 582 mount request for a standalone device, 581 protection expiration, 586 starting interactive sessions, 585 starting scheduled sessions, 584 unexpected mounted system detected, 583 troubleshooting communication client fails, 567 HOST file resolution problem, 567 host name resolution problems, 565 troubleshooting devices device open problem, 575
Index used media adding, 107 user account setting for the Inet, 187 User Check Failed notification, 347, 606 user class description of access rights, 83 user configurations examples, 94 rights, 83 users restoring their own data, 94 user definable backup variables object specific option, 248 user disk quotas, 286 backing up, 183 user groups adding new, 88 changing rights, 93 deleting, 88 predefined, 86 user interfaces command-line interface graphical user interface, 6 Microsoft Management Console online Help
Index viewing currently running sessions, 309 details of a running session, 310 files from media , 301 finished sessions, 310 views modifying in the media management window, 149 virtual server, 615 volume mount points, 170 Volume Shadow Copy service (VSS), 170 volumes backing up, 194 VSS See Volume Shadow Copy service (VSS), 170 VSS filesystem backup, 170 VxFS snapshot, A-3 W Wake ONLINE, 265 Web reporting and notifications interface accessing, 354 changing password for, 354 configuring notifications using
Index X XCopy engine, 39, 204 I-26
