Preview only show first 10 pages with watermark. For full document please download

Emc® Avamar® 6.1 For Ibm Db2 User Guide

Rating
Date

November 2018
Size

2.9MB
Views

5,612
Categories

Computers & electronics Software Computer utilities Backup recovery software

Transcript

EMC® Avamar® 6.1 for IBM DB2 User Guide P/N 300-013-361 REV 05 Copyright © 2001- 2013 EMC Corporation. All rights reserved. Published in the USA. Published November, 2013 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website. 2 EMC Avamar 6.1 for IBM DB2 User Guide CONTENTS Preface Chapter 1 Introduction Architecture ................................................................................................ Avamar client software .......................................................................... Backup ....................................................................................................... Online backups..................................................................................... Offline backups..................................................................................... DB2 partition backups .......................................................................... Restore and recovery................................................................................... Restore locations .................................................................................. Table space restore and recovery .......................................................... DB2 partition restore and recovery ........................................................ Chapter 2 Installation System requirements .................................................................................. Software installation packages.................................................................... Preinstallation ............................................................................................ Client registration ....................................................................................... Installing the software on IBM AIX ............................................................... Download the installation packages for IBM AIX .................................... Install and register the Avamar Client for AIX ......................................... Install and configure the Avamar Plug-in for DB2 ................................... Uninstalling the software on IBM AIX........................................................... Upgrading the software on IBM AIX ............................................................. Installing the software on Microsoft Windows.............................................. Windows Server 2008 and 2008 R2 with User Account Control .............. Download and install the Avamar Client for Windows ............................ Register the Avamar Client for Windows ................................................ Install the Avamar Plug-in for DB2 on Windows ..................................... Uninstalling and upgrading on Microsoft Windows ...................................... Installing the software on Linux................................................................... Download Avamar installation packages for Linux ................................. Install and register the Avamar Client for Linux ...................................... Install and configure the Avamar Plug-in for DB2 ................................... Uninstalling the software on Linux .............................................................. Upgrading the software on Linux ................................................................. Chapter 3 14 16 16 16 16 16 17 19 19 20 22 22 23 24 27 27 28 30 32 34 34 34 34 36 36 37 37 38 38 39 41 41 Backup Database preparation ................................................................................. Offline backups..................................................................................... Online backups..................................................................................... DB2 database partition backups ........................................................... On-demand backup .................................................................................... Scheduled backups..................................................................................... Creating a dataset ................................................................................. Creating a group.................................................................................... EMC Avamar 6.1 for IBM DB2 User Guide 44 44 44 44 45 48 48 51 3 Contents Enabling scheduled backups ................................................................ 55 Chapter 4 Restore and Recovery Restoring DB2 databases to the original location ........................................ Restoring an offline backup................................................................... Restoring an online backup with archive logs ........................................ Restoring DB2 databases to a different location .......................................... Rolling the database forward................................................................. Restoring DB2 database partitions .............................................................. Restoring one or more table spaces............................................................. Restoring table spaces in a stand-alone DB2 environment .................... Restoring table spaces in a DB2 DPF environment ................................. Recovering retired clients ............................................................................ Disaster recovery ........................................................................................ Recovering the DB2 application............................................................. Recovering the DB2 server..................................................................... Recovering the DB2 server in a DPF environment ................................... Appendix A 58 58 61 66 69 70 73 73 76 78 82 82 82 83 Plug-in Options How to set plug-in options .......................................................................... 86 Backup options........................................................................................... 86 Restore options........................................................................................... 87 Appendix B Command-Line Interface Overview..................................................................................................... Available operations ............................................................................. Options................................................................................................. Help ...................................................................................................... DB2 instance password security on AIX and Linux ................................. Command reference .................................................................................... Synopsis ............................................................................................... Operations ............................................................................................ Options................................................................................................. CLI example commands .............................................................................. Example browse commands.................................................................. Example backup commands.................................................................. Example restore commands .................................................................. Appendix C Troubleshooting How to specify options.............................................................................. Backup or restore fails with a “Failed to create backup of db” error............ Specifying the avdb2-stream-timeoutsecs option................................ Backup fails with socket timeout errors ..................................................... Granular browse fails to display table spaces ............................................ Restore fails with a “Failed to initiate the restore operation” error ............. Unable to connect to database during backup........................................... Glossary Index 4 90 90 90 91 91 92 92 93 93 97 97 97 98 EMC Avamar 6.1 for IBM DB2 User Guide 100 102 102 103 103 105 105 TABLES Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Page Revision history ............................................................................................................ 7 Database backup types............................................................................................... 18 Restore and recover options........................................................................................ 18 Recovery types ............................................................................................................ 18 Software installation packages ................................................................................... 22 Backup plug-in options ............................................................................................... 86 Restore plug-in options ............................................................................................... 87 Operations for the avdb2 command ............................................................................ 93 Common options for the avdb2 command ................................................................... 93 Account options for the avdb2 command .................................................................... 94 Logging command options for the avdb2 command .................................................... 94 Browse command options for the avdb2 command ..................................................... 94 Backup options for the avdb2 command ..................................................................... 95 Restore options for avdb2 command ........................................................................... 96 EMC Avamar 6.1 for IBM DB2 User Guide 5 Tables 6 EMC Avamar 6.1 for IBM DB2 User Guide PREFACE As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC representative if a product does not function properly or does not function as described in this document. Note: This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document. Purpose This guide describes how to install, configure, administer, and use the Avamar Plug-in for DB2. Audience This guide is for: ◆ System administrators who are responsible for installing software and maintaining servers and clients on a network ◆ Database administrators (DBAs) responsible for backing up and maintaining DB2 databases Users should know: ◆ Operating system shell commands (root permission required) ◆ The specific version of DB2 software currently deployed at the site Revision history The following table presents the revision history of this document. Table 1 Revision history Revision Date Description 05 November 15, 2013 Added “Unable to connect to database during backup” on page 105. 04 June 17, 2013 Update for release 6.1 Service Pack 2: added a new update db cfg command to “Online backups” on page 44. 03 March 1, 2013 Removed the --verbose flag from Appendix B, “Command-Line Interface.” 02 July 31, 2012 Updated “Where to get help” on page 9 in the Preface. A01 April 25, 2012 First release of Avamar 6.1. EMC Avamar 6.1 for IBM DB2 User Guide 7 Preface Related documentation The following documentation provides more information: ◆ EMC Avamar Release Notes ◆ EMC Avamar Administration Guide ◆ EMC Avamar Operational Best Practices ◆ EMC Avamar Product Security Guide Conventions used in this document EMC uses the following conventions for special notices: DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury. WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury. CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury. NOTICE is used to address practices not related to personal injury. Note: A note presents information that is important, but not hazard-related. IMPORTANT An important notice contains information essential to software or hardware operation. IMPORTANT formation essential to software or hardware operation. 8 EMC Avamar 6.1 for IBM DB2 User Guide Preface Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: • Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus • Names of resources, attributes, pools, Boolean expressions, buttons, SQL statements, keywords, clauses, environment variables, functions, and utilities • URLs, pathnames, file names, directory names, computer names, links, groups, service keys, file systems, and notifications Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: • Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus • What the user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: • Full titles of publications referenced in text • Emphasis, for example, a new term • Variables Courier Used for: • System output, such as an error message or script • URLs, complete paths, file names, prompts, and syntax when shown outside of running text Courier bold Used for specific user input, such as commands Courier italic Used in procedures for: • Variables on the command line • User input variables <> Angle brackets enclose parameter or variable values supplied by the user [] Square brackets enclose optional values | Vertical bar indicates alternate selections — the bar means “or” {} Braces enclose content that the user must specify, such as x or y or z ... Ellipses indicate nonessential information omitted from the example Where to get help The Avamar support page provides access to licensing information, product documentation, advisories, and downloads, as well as how-to and troubleshooting information. This information may enable you to resolve a product issue before you contact EMC Customer Service. To access the Avamar support page: 1. Go to https://support.EMC.com/products. 2. Type a product name in the Find a Product box. 3. Select the product from the list that appears. 4. Click the arrow next to the Find a Product box. 5. (Optional) Add the product to the My Products list by clicking Add to my products in the top right corner of the Support by Product page. EMC Avamar 6.1 for IBM DB2 User Guide 9 Preface Documentation The Avamar product documentation provides a comprehensive set of feature overview, operational task, and technical reference information. Review the following documents in addition to product administration and user guides: ◆ Release notes provide an overview of new features and known limitations for a release. ◆ Technical notes provide technical details about specific product features, including step-by-step tasks, where necessary. ◆ White papers provide an in-depth technical perspective of a product or products as applied to critical business issues or requirements. Knowledgebase The EMC Knowledgebase contains applicable solutions that you can search for either by solution number (for example, esgxxxxxx) or by keyword. To search the EMC Knowledgebase: 1. Click the Search link at the top of the page. 2. Type either the solution number or keywords in the search box. 3. (Optional) Limit the search to specific products by typing a product name in the Scope by product box and then selecting the product from the list that appears. 4. Select Knowledgebase from the Scope by resource list. 5. (Optional) Specify advanced options by clicking Advanced options and specifying values in the available fields. 6. Click the search button. Live chat To engage EMC Customer Service by using live interactive chat, click Join Live Chat on the Service Center panel of the Avamar support page. Service Requests For in-depth help from EMC Customer Service, submit a service request by clicking Create Service Requests on the Service Center panel of the Avamar support page. Note: To open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. To review an open service request, click the Service Center link on the Service Center panel, and then click View and manage service requests. Facilitating support EMC recommends that you enable ConnectEMC and Email Home on all Avamar systems: 10 ◆ ConnectEMC automatically generates service requests for high priority events. ◆ Email Home emails configuration, capacity, and general system information to EMC Customer Service. EMC Avamar 6.1 for IBM DB2 User Guide Preface Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: [email protected] Please include the following information: ◆ Product name and version ◆ Document name, part number, and revision (for example, 01) ◆ Page numbers ◆ Other details that will help us address the documentation issue EMC Avamar 6.1 for IBM DB2 User Guide 11 Preface 12 EMC Avamar 6.1 for IBM DB2 User Guide CHAPTER 1 Introduction The EMC® Avamar® Plug-in for DB2 provides a complete backup and restore solution for DB2 databases. Topics in this chapter include: ◆ ◆ ◆ Architecture ............................................................................................................ 14 Backup ................................................................................................................... 16 Restore and recovery............................................................................................... 17 Introduction 13 Introduction Architecture The Avamar Plug-in for DB2 works with the Avamar server and the DB2 API to back up DB2 databases and archive logs from a DB2 server to the Avamar server. The Avamar Plug-in for DB2 serves as a backup module and the Avamar server as a storage device. The Avamar Plug-in for DB2 supports backups and restores of DB2 single instance configurations and DB2 configurations that implement DB2 database partitioning feature (DPF). Each DB2 server requires the installation of the Avamar Plug-in for DB2 and an Avamar file system client. You back up and restore DB2 databases by using Avamar Administrator. The Avamar Plug-in for DB2 also provides a command line interface (CLI) for backups and restores. Appendix B, “Command-Line Interface,” provides more information about the Avamar Plug-in for DB2 CLI. The following figure shows an Avamar Plug-in for DB2 configuration that backs up database files from an AIX client platform to an Avamar server. Avamar server Network Windows or Linux server Avamar Administrator Avamar client IBM DB2 Avamar Plug-in for DB2 Avamar Client for AIX GEN-001812 Figure 1 Basic Avamar Plug-in for DB2 configuration 14 EMC Avamar 6.1 for IBM DB2 User Guide Introduction The Avamar Plug-in for DB2 also supports backups to and restores from a “Data Domain system.” The following figure shows an Avamar Plug-in for DB2 configuration that backs up database files from an AIX client platform to a Data Domain system. Avamar server ddmaint utility DD Boost API metadata Data Domain Network Windows or Linux server Avamar Administrator Avamar client IBM DB2 Avamar Plug-in for DB2 Avamar Client for AIX DD Boost API GEN-001813 Figure 2 Avamar Plug-in for DB2 and Data Domain configuration The Avamar client uses the “DD Boost” application programming interface (API) for backups to and restores from the Data Domain system. The installation of Avamar Plug-in for DB2 automatically installs the DD Boost application programming interface (API) on the Avamar client. The installation of the Avamar server software automatically installs the DD Boost API on the Avamar server. To back up DB2 data to a Data Domain system, you select a Data Domain system from the user interface. Chapter 3, “Backup,” provides more information. Metadata for the backup is stored on the Avamar server. You restore backed up data from a Data Domain system the same way you restore data from the Avamar server. There are no extra steps. You follow the same restore procedure whether the data is located on the Avamar server or a Data Domain system. The EMC Avamar and Data Domain Integration Guide provides more information about Data Domain systems. Architecture 15 Introduction Avamar client software The computer that runs the DB2 Universal Database requires the following software: ◆ The applicable platform-specific Avamar file system client: Avamar Client for AIX, Avamar Client for Linux, or Avamar Client for Windows. ◆ Avamar Plug-in for DB2 The Avamar Plug-in for DB2 includes the two main components. ◆ On AIX and Linux, avdb2 binary and libdb2_avamar.so (shared library) ◆ On Windows, avdb2.exe and avdb2.dll (Dynamic Link Library) The avdb2 binary or executable performs browse, backup, restore, and cancel operations on DB2 databases that belong to a “DB2 instance.” Backup The Avamar Plug-in for DB2 supports full backups of DB2 databases and database partitions. You can perform either on-demand or scheduled backups while the database is online or offline. Online backups An online backup is performed while the database is active. During this type of backup, users and applications can connect to the database and perform transactions. Online backups can either include or exclude archive logs. To reduce the backup window, you can exclude the archive logs from the database backup by specifying the Exclude archive logs in ONLINE backup option. Then include the archive logs in a file system backup. “On-demand backup” on page 45 provides more information about the Exclude archive logs in ONLINE backup option. Offline backups An offline backup is performed while the database is inactive. During this type of backup, no connections to the database are allowed. Chapter 3, “Backup,” provides more information. Backups in a DPF environment are performed from the catalog partition only. DB2 partition backups Avamar Plug-in for DB2 supports partition backups in configurations which use DPF. A DPF configuration allows you to partition a database across multiple servers or within a large Symmetric Multi-Processor (SMP) server. The partition where you execute the CREATE DATABASE command is called the catalog node or partition. The catalog partition is where the backup process runs. The catalog partition contains the following table spaces in addition to user-defined table spaces: 16 ◆ SYSCATSPACE — A table space that describes the database itself. ◆ TEMPSPACE1— A table space used for temporary storage by the database server during operations on the database. ◆ USERSPACE1 — The default table space, which contains all tables created by the user. EMC Avamar 6.1 for IBM DB2 User Guide Introduction All other partitions are called non-catalog nodes or partitions. The Avamar Plug-in for DB2 backs up database partitions that are local to the catalog node or remote (located on remote cluster nodes). To back up database partitions, the Avamar Plug-in for DB2 backup process first connects to the database that is selected for backup and runs a query to determine configuration details. ◆ If the query determines that database partition is local, the backup process continues on the DB2 server. ◆ If the query determines that the database partition is located on a remote cluster node, DB2 forwards the backup request to the remote cluster node, and then starts the backup. Backing up a partition from a non-catalog node You cannot perform a database partition backup from a non-catalog node. Doing so returns the following error: Cannot perform multi-partition backup. The catalog node for the database is not present on this server. Backing up a partition when a node is offline You cannot back up a node in a multi-partition configuration unless all nodes are online. A multi-partition backup fails if one or more nodes is offline. The backup failure returns the following error messages for this type of failure: 2012/4/1-13:14:07.21048 [avdb2ctlplugin_assist] snapup: return from db2 API 2012-4-1 18:44:07 avdb2 Error <0000>: snapup: failed to create backup of database [db2inst1/AVAMAR2]. db2 errcode -1170 2012-4-1 18:44:07 avdb2 Error <9018>: DB2 returned error -1170 2012/4/1-13:14:07.21122 [avdb2ctlplugin_assist] retire_manager: force terminate Restore and recovery You restore and recover a database only while the database is offline. You cannot restore and recover a database that is online with connections. The restore and recovery operation automatically establishes a connection to the specified database. Once the restore operation completes, this connection is terminated. Restore and recovery 17 Introduction The Avamar Plug-in for DB2 supports DB2 database restores from both online and offline backups. You can identify whether the backup is an online or offline backup by its file name prefix. The Avamar Plug-in for DB2 uses a prefix to specify the type of backup. The following table lists the prefix-naming convention for each backup type. Table 2 Database backup types Type of backup File name prefix Example file name Offline backup of a database c- c-DBname Offline backup of a partition c- c-DBname-PartitionNumber-Hostname Online backup of a database with archive logs hl- hl-DBname Online backup of a partition with archive logs hl- hl-DBname-PartitionNumber-Hostname Online backup of a database without archive logs h- h-DBname Online backup of a partition without archive logs h- h-DBname-PartitionNumber-Hostname The Avamar Plug-in for DB2 restores and recovers database and table spaces according to the operations allowable by the DB2 API. The following table lists the types of restore and recover options you can specify for a restore operation. Table 3 Restore and recover options Option Description Backup type Restore and Recover Restores the backup and rolls the database forward by using the archive logs. When you specify this option, you also must select a Recovery Type option. Online Restore Only Restores database files only. Online or offline Restore only archive logs from ONLINE backup Restores archive logs only. Online The Avamar Plug-in for DB2 includes database recover options that enable you to roll the database or table space forward. The following table lists the recovery type options. Table 4 Recovery types 18 Recover option Description End of Logs Rolls the database forward to the end of log files. Point in Time Recovers the database to a specific time (year, month, day, hour, minute, and second). End of Backup Rolls the database forward to the end of the backup. This option is available for backups of DB2 9.5 databases and later. EMC Avamar 6.1 for IBM DB2 User Guide Introduction Restore locations You can restore a database to its original location, to a different location on the original client, or to a different client altogether. A restore to a different location is commonly referred to as a redirected restore. When you restore a database to a different location, you can only select one database for the restore operation. When performing a redirected restore, the restore target can be: ◆ The same client from which the backup was originally taken. In this case, the redirected restore operation creates a clone of the original database. The new database contains the same contents of the original database. ◆ A different client. To perform a redirected restore to a different client, the operating system version and DB2 version on the target client must be the same version as on the source client. A redirected restore sets the table space container path to the DB2 defaults. If the database contains a user-defined container path to a table space, the redirected restore redefines the default path. This process requires adequate space on the partition. The Avamar Plug-in for DB2 supports redirected restores only for databases without automatic storage on the AIX and Linux platforms. Table space restore and recovery The “granular recovery” feature enables you to restore one or more table spaces from a full database backup. To use the granular recovery feature, LOGARCHMETH1 must be set to LOGRETAIN and a full database backup must exist. During a full database backup, the Avamar Plug-in for DB2 runs the DB2 LIST HISTORY command, which compiles a list of table spaces that were backed up. The Avamar Plug-in for DB2 then uses this list of table spaces for granular recovery operations. A table space restore and recovery is performed while the database is online or offline. The exception is the SYSCATSPACE table space. A SYSCATSPACE table space restore and recovery must be performed while the database is offline. You must use the rollforward command to manually roll the table space forward after you restore a table space from an offline backup or a DPF environment. An end of backup or point-in-time recovery of a table space leaves the table space in a backup pending state. When a table is in a backup pending state, the database is read-only. No modifications can be made to the table space. After performing an end of backup or point-in-time recovery of a table space, you must perform an online or offline backup to reset the table space state. You can restore a renamed table space by using the renamed_tablespace_list option. Restore and recovery 19 Introduction Granular recovery restrictions The following restrictions apply to the granular recovery feature: ◆ The Avamar Plug-in for DB2 does not support the end of logs, point-in-time, or end of backup recovery types for a table space in a DPF environment. ◆ DB2 does not support restores of a table space to a database other than the one from which the backup was taken. You cannot restore a table space to a different location on the same host or to a different host. ◆ Restores of table spaces that have been dropped are not supported. DB2 partition restore and recovery Avamar Plug-in for DB2 supports database partition restores in configurations which use the DPF. Unlike the backup process, which must run only from the catalog partition, the restore operation runs on each partition. ◆ To restore partitions from the catalog partition, you perform a restore to the original location. ◆ To restore partitions from non-catalog partitions, you perform a restore to a different location. “Restoring table spaces in a DB2 DPF environment” on page 76 provides more information. You must use the rollforward command to manually roll the table space forward after you restore a table space in a DPF environment. You roll a database forward only from the catalog partition. DB2 does not support rollforward operations from non-catalog partitions. 20 EMC Avamar 6.1 for IBM DB2 User Guide CHAPTER 2 Installation This chapter describe how to install and configure the Avamar Plug-in for DB2. Topics in this chapter include: ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ System requirements .............................................................................................. Software installation packages................................................................................ Preinstallation ........................................................................................................ Client registration ................................................................................................... Installing the software on IBM AIX ........................................................................... Uninstalling the software on IBM AIX....................................................................... Upgrading the software on IBM AIX ......................................................................... Installing the software on Microsoft Windows.......................................................... Uninstalling and upgrading on Microsoft Windows .................................................. Installing the software on Linux............................................................................... Uninstalling the software on Linux .......................................................................... Upgrading the software on Linux ............................................................................. Installation 22 22 23 24 27 32 34 34 37 37 41 41 21 Installation System requirements You can install the Avamar Plug-in for DB2 on the following server platforms: ◆ IBM AIX 6.1 and 7.1 64-bit ◆ Microsoft Windows 2008 R1 and 2008 R2 x64 ◆ Microsoft Windows Server 2003 32-bit ◆ Red Hat Enterprise Linux 5 64-bit ◆ SuSE Linux 10 and 11 32-bit ◆ SuSE Linux 10 and 11 64-bit The “Preinstallation” on page 23 and “Client registration” on page 24 tasks apply to all server platforms. However, there are separate client installation procedures for each platform. Before you install Avamar software on a client system, ensure that the client operating system and hardware configuration are supported. Use the EMC Avamar Compatibility and Interoperability Matrix to view all software requirements. 1. Open a browser and navigate to https://support.EMC.com. 2. Type Avamar Compatibility and Interoperability Matrix in the Search EMC Support field. 3. Click Search. Software installation packages The following table lists the software packages required to install Avamar Plug-in for DB2. Each installation requires two software packages: the file system client and the DB2 plug-in. Table 5 Software installation packages (page 1 of 2) 22 Operating system Software installation packages IBM AIX 6.1 and 7.1 64-bit • AvamarClient-aix6-ppc-VERSION.bff • AvamarDB2-aix6-ppc64-VERSION.bff Microsoft Windows 2003, 2008, and 2008 R2 x64 • AvamarClient-windows-x86_64-VERSION.msi • AvamarDB2-windows-x86_64-VERSION.msi Red Hat Enterprise Linux 5 64-bit • AvamarClient-linux-rhel4-x86_64-VERSION.rpm • AvamarDB2-linux-rhel4-x86_64-VERSION.rpm SUSE Linux Enterprise Server 10 32-bit • AvamarClient-linux-rhel4-x86-VERSION.rpm • AvamarDB2-linux-rhel4-x86-VERSION.rpm EMC Avamar 6.1 for IBM DB2 User Guide Installation Table 5 Software installation packages (page 2 of 2) Operating system Software installation packages SUSE Linux Enterprise Server 11 SP132-bit • AvamarClient-linux-sles11-x86-VERSION.rpm • AvamarDB2-linux-sles11-x86-VERSION.rpm SUSE Linux Enterprise Server 10 64-bit • AvamarClient-linux-rhel4-x86_64-VERSION.rpm • AvamarDB2-linux-rhel4-x86_64-VERSION.rpm SUSE Linux Enterprise Server 11 SP1 64-bit • AvamarClient-linux-sles11-x86_64-VERSION.rpm • AvamarDB2-linux-sles11-x86_64-VERSION.rpm Preinstallation Before you install Avamar software ensure that: ◆ You have operating system root privileges on the computer that hosts the DB2 server. ◆ DB2 is installed and functioning properly. ◆ The Avamar server is operational and present on the same network as the DB2 server. To verify network connectivity, open a command shell on the DB2 server and type the following: ping AVAMARSERVER where AVAMARSERVER is the network hostname (as defined in DNS) or IP address of the Avamar server. Note the network hostname for the Avamar server and utility node. The Avamar system deployment adds these DNS entries. Preinstallation 23 Installation Client registration You must register the client to establish it with the Avamar server. A complete discussion of registering and activating new Avamar clients, domains, and user accounts is beyond the scope of this guide. The EMC Avamar Administration Guide provides additional information. To register the client: 1. In Avamar Administrator, click the Administration launcher button. The Administration window appears. 2. Click the Account Management tab. 3. Select the domain for the client. You can add this client to an existing Avamar domain, or add a domain to the Avamar system to segregate clients that perform DB2 backups from clients that back up physical file systems. The EMC Avamar Administration Guide provides additional information. 4. Select Actions > Account Management > New Client. 24 EMC Avamar 6.1 for IBM DB2 User Guide Installation The New Client dialog box appears. 5. Complete the settings in the New Client dialog box: a. For Client Type, leave the default setting, Normal. b. For New client name, type a name for the new client. To ensure error-free client registration, the Avamar client name must be the actual DB2 server network hostname as defined in DNS. c. For Contact, type the name of a contact. d. For Phone, type the contact’s telephone number. e. For Email, type the contact’s email address. f. For Location, type the contact’s location. g. Click OK. The New Client dialog box closes and the new client appears in the Account Management tree pane. 6. Select the client that you added. Client registration 25 Installation 7. Select Actions > Account Management > New User(s) to create a user account for the client. The New User(s) dialog box appears. 8. Complete the settings in the New User(s) dialog box: a. Select an authentication system from the Authentication System list. Authentication System lists Axion Authentication System as the default setting. Other external authentication systems that you have configured to work with Avamar will also be available in this list. b. Select Everyone to designate privileges for all users on the client, or select User Name and type a new user name. If you selected an external authentication system, you must specify the user name that you use to log in to that system. c. Select Backup/Restore User from the Role list. d. Type the password for the new user in the Password field. Avamar passwords must be at least six characters in length. Do not include the following special characters in the password: *!@# If you are using an external authentication system, leave the Password field blank. e. In the Confirm field, retype the password to confirm it. If you are using an external authentication system, leave the Confirm field blank. f. Click OK. The following status message appears: User added. 9. Click OK. The status message closes and the new user appears in the list of users for the client. 26 EMC Avamar 6.1 for IBM DB2 User Guide Installation Installing the software on IBM AIX To install the Avamar Plug-in for DB2 on supported IBM AIX platforms, perform these tasks: 1. “Download the installation packages for IBM AIX” on page 27. 2. “Install and register the Avamar Client for AIX” on page 28. 3. “Install and configure the Avamar Plug-in for DB2” on page 30. Download the installation packages for IBM AIX To download the Avamar installation packages for AIX DB2: 1. Log in to the DB2 server host as root. 2. Open a web browser and type the following URL: http://AVAMARSERVER where AVAMARSERVER is the Avamar system network hostname (as defined in DNS) or IP address. You are redirected to the Avamar secure web server. 3. If the browser displays a security certificate warning message, click Yes or OK to allow redirection to the Avamar secure web server. The Secure Log On page appears. 4. Page down until the Downloads and Documents hyperlink is visible. 5. Click Downloads and Documents. The Web Documents & Downloads page appears. 6. Click the operating system hyperlink for the computer that hosts the DB2 server. A directory listing appears. 7. Download the Avamar Client for AIX installation package to a temporary install directory on the system. 8. Note the Avamar Client for AIX installation package file name. 9. Download the Avamar Plug-in for DB2 installation package to the same directory as the Avamar Client for AIX installation package. 10. Note the Avamar Plug-in for DB2 installation package file name. Installing the software on IBM AIX 27 Installation Install and register the Avamar Client for AIX To install and register the Avamar Client for AIX: 1. Log in to the DB2 server host as root. 2. Start the installation by typing: cd /TMP geninstall -d AvamarClient-aix5-ppc-VERSION.bff all where: • TMP is the temporary install directory. • VERSION.bff is the Avamar software version. The following appears in the command shell: +-----------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------AVMRclnt 6.1.100.nnn # Avamar Client for AIX 6.1.100-nnn... << End of Success Section >> FILESET STATISTICS -----------------1 Selected to be installed, of which: 1 Passed pre-installation verification ---1 Total to be installed Filesystem size changed to 524288 +-----------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------+ installp: APPLYING software for: AVMRclnt 6.1.100-nnn . . . . . << Copyright notice for AVMRclnt >> . . . . . . . This software is copyright EMC Corporation, 2001-2012. Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. . . . . . << End of copyright notice for AVMRclnt >>. . . . Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log 28 EMC Avamar 6.1 for IBM DB2 User Guide Installation avagent Info <5417>: daemonized as process id 17444 avagent.d Info: Client Agent started. Finished processing all filesets. (Total time: 9 secs). +-----------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------AVMRclnt 6.1.100-nnn USR APPLY SUCCESS 3. Register the client with the Avamar server by typing: /usr/local/avamar/bin/avregister The following appears in the command shell: === Client Registration and Activation This script will register and activate the client with the Administrator server. Enter the base directory of the Avamar Client installation [/usr/local/avamar]: 4. Press Enter to accept the default base installation directory. The following appears in the command shell: Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred): 5. Type the network hostname (as defined in DNS) of the Avamar Administrator server and press Enter. The following appears in the command shell: Enter the Avamar server domain [clients]:Avamar The default domain is “clients.” However, the Avamar system administrator may have defined other domains and subdomains. Consult the Avamar system administrator for which domain to use when registering this client. If you specify a subdomain (for example, clients/MyClients), then do not include a slash (/) as the first character. Including a slash as the first character causes an error and prevents you from registering this client. 6. Press Enter to accept the default domain (clients). The following appears in the command shell: avagent.d Info: Server stopped. avagent Info <5241>: Logging to ///usr/local/avamar//var/avagent.log avagent.d Info: Client activated successfully. avagent.d Info: start avagent Info <5241>: Logging to ///usr/local/avamar//var/avagent.log avagent Info <5417>: daemonized as process id 17620 avagent.d Info: Server started. Registration Complete. Installing the software on IBM AIX 29 Installation Install and configure the Avamar Plug-in for DB2 To install and configure the Avamar Plug-in for DB2: 1. Ensure that the Avamar Client for AIX has been installed and configured before installing the Avamar Plug-in for DB2. “Install and register the Avamar Client for AIX” on page 28 provides details. 2. Ensure that you are still logged in to the computer that hosts the DB2 server as root. 3. Install the Avamar Plug-in for DB2 software by typing: cd /TMP geninstall -d AvamarDB2-aix5-ppc64-VERSION.bff all where: • TMP is the temporary install directory. • VERSION is the Avamar software version. The following appears in the command shell: +-----------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------AvamarDB2-aix5-ppc64 6.1.100.nnn # EMC Avamar client 6.1.100-nnn << End of Success Section >> +-----------------------------------------------------------------+ BUILDDATE Verification ... +-----------------------------------------------------------------+ Verifying build dates...done FILESET STATISTICS -----------------1 Selected to be installed, of which: 1 Passed pre-installation verification ---1 Total to be installed +-----------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------+ installp: APPLYING software for: AvamarDB2-aix5-ppc64 6.1.100-nnn . . . . . << Copyright notice for AvamarDB2-aix5-ppc64 >> . . . . . . . This software is copyright EMC Corporation, EMC Corporation, 2001-2012. 30 EMC Avamar 6.1 for IBM DB2 User Guide Installation Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. . . . . . << End of copyright notice for AvamarDB2-aix5-ppc64 >>. . . . installdir is /usr/local/avamar total 40 -rw-r--r-1 root system 13638 Aug 19 10:51 AvamarClient-License.txt drwxr-xr-x 2 205 staff 4096 Aug 19 10:55 bin drwxr-xr-x 2 205 staff 256 Aug 19 10:55 etc drwxr-xr-x 2 205 staff 256 Aug 19 11:41 lib drwxr-xr-x 2 205 staff 256 Aug 19 10:55 lib64 lrwxrwxrwx 1 root system 11 Aug 19 11:40 var -> /var/avamar avagent.d Info: Stopping Avamar Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 618624 avagent.d Info: Client Agent started. Installation complete You may run /usr/local/avamar/bin/avdb2setup to configure this module to backup to the dpn. Finished processing all filesets. (Total time: 5 secs). +-----------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------AvamarDB2-aix5-ppc64 6.1.100-nnn USR APPLY SUCCESS 4. Configure the Avamar Plug-in for DB2 software by typing: /usr/local/avamar/bin/avdb2setup The following appears in the command shell: This script will configure the EMC Avamar DB2 plugin Enter path to Avamar Client installation [/usr/local/avamar]: 5. Type the full path to the Avamar client installation root directory and press Enter. The following appears in the command shell: Username for DB2 instance owner: db2dba where db2dba is the database instance owner. 6. Type the user account that owns this database instance and press Enter. The following appears in the command shell: Home directory for DB2 instance owner [/home/db2dba]: where /home/db2dba is the home directory for the database instance owner. Installing the software on IBM AIX 31 Installation 7. Type the full path to the home directory of the user that owns this database instance and press Enter. The following appears in the command shell: Writing /usr/local/avamar/etc/db2.cfg... Restarting client agent... avagent.d Info: Stopping Avamar Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 479284 avagent.d Info: Client Agent started. Uninstalling the software on IBM AIX To uninstall the Avamar Plug-in for DB2: 1. Log in to the DB2 server host as root. 2. Uninstall the Avamar Plug-in for DB2 software by typing: lslpp -l | grep Avamar The following appears in the command shell: AvamarClient-aix5-ppc AvamarDB2-aix5-ppc64 VERSION COMMITTED EMC Avamar client VERSION VERSION COMMITTED EMC Avamar client VERSION 3. Type: geninstall -u AvamarDB2-aix5-ppc64 The following appears in the command shell: +-----------------------------------------------------------------+ Pre-deinstall Verification... +-----------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-deinstall verification and will be removed. Selected Filesets ----------------AvamarDB2-aix5-ppc64 6.1.100.nnn#EMC Avamar client 6.1.100-nnn... << End of Success Section >> FILESET STATISTICS -----------------1 Selected to be deinstalled, of which: 1 Passed pre-deinstall verification ---1 Total to be deinstalled +-----------------------------------------------------------------+ Deinstalling Software... +-----------------------------------------------------------------+ installp: 32 EMC Avamar 6.1 for IBM DB2 User Guide DEINSTALLING software for: Installation AvamarDB2-aix5-ppc64 VERSION Finished processing all filesets. (Total time: 1 secs). +-----------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------AvamarDB2-aix5-ppc64 6.1.100-nnn USR DEINSTALL SUCCESS 4. Uninstall the Avamar Client for AIX software by typing: lslpp -l | grep Avamar The following appears in the command shell: AvamarClient-aix5-ppc VERSION COMMITTED EMC Avamar client VERSION 5. Type: geninstall -u AvamarClient-aix5-ppc The following appears in the command shell: +-----------------------------------------------------------------+ Pre-deinstall Verification... +-----------------------------------------------------------------+ Verifying selections...avagent.d Info: Stopping Avamar Client Agent (avagent)... avagent.d Info: Client Agent stopped. done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-deinstall verification and will be removed. Selected Filesets ----------------AvamarClient-aix5-ppc 6.1.100.nnn #EMC Avamar client 6.1.100-nnn... << End of Success Section >> FILESET STATISTICS -----------------1 Selected to be deinstalled, of which: 1 Passed pre-deinstall verification ---1 Total to be deinstalled +-----------------------------------------------------------------+ Deinstalling Software... +-----------------------------------------------------------------+ installp: DEINSTALLING software for: AvamarClient-aix5-ppc VERSION Finished processing all filesets. (Total time: 2 secs). Uninstalling the software on IBM AIX 33 Installation +-----------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------AvamarClient-aix5-ppc 6.1.100-nnn USR DEINSTALL SUCCESS Upgrading the software on IBM AIX To upgrade the Avamar Client for AIX and Avamar Plug-in for DB2 software, uninstall the old software and install the new software. Installing the software on Microsoft Windows To install the Avamar Plug-in for DB2 on supported Microsoft Windows platforms: 1. “Download and install the Avamar Client for Windows” on page 34. 2. “Register the Avamar Client for Windows” on page 36. 3. “Install the Avamar Plug-in for DB2 on Windows” on page 36. Windows Server 2008 and 2008 R2 with User Account Control In Windows Server 2008, Microsoft added the User Account Control (UAC) feature. UAC prevents a user with administrator privileges from installing software unless an administrator authorizes the elevated privileges to the user. Starting the Avamar Client for Windows installer with normal account privileges does not install the software correctly on a computer with a default implementation of UAC. Run the installer with elevated administrative privileges to correctly install the software. The following installation procedures include instructions. Download and install the Avamar Client for Windows To install the Avamar Client for Windows software: 1. Log in to the DB2 server and start a web browser. 2. Type the URL of the Avamar server in the web browser: http://AVAMARSERVER where AVAMARSERVER is the Avamar system network hostname (as defined in DNS) or IP address. You are redirected to the Avamar secure web server. 3. If the browser displays a security certificate warning message, click Yes or OK to allow redirection to the Avamar secure web server. The Secure Log On page appears. 4. Page down until the Downloads and Documents hyperlink is visible. 34 EMC Avamar 6.1 for IBM DB2 User Guide Installation 5. Click Downloads and Documents. The Web Documents & Downloads page appears. 6. Click the operating system hyperlink for the client computer. A directory listing appears. 7. Click the appropriate install package: • For a 32-bit Microsoft Windows Server platform select the AvamarClient-windows-x86-VERSION.msi installation package. • For a 64-bit Microsoft Windows Server platform, select the AvamarClient-windows-x86_64-VERSION.msi installation package. where VERSION is the version number of the software. For computers with UAC, you must download the installation package to a temporary directory. Do not open it in place. “Windows Server 2008 and 2008 R2 with User Account Control” on page 34 provides additional information. 8. Start the installer by using one of these methods: • To install the software on a non-UAC computer: a. Click Run to install the software in place. b. Save the installation file to a temporary directory. c. Double-click the installation file to start the installation. • To install the software on a UAC computer: a. In Windows, right-click on the Command Prompt icon and select Run as administrator. b. In the Command Prompt window, change the working directory to the location of the installation package by typing: cd PATH-TO-INSTALL-DIR where PATH-TO-INSTALL-DIR is the full path of the temporary directory that contains the installation package. c. Type the following command on a single command line to launch the installer: msiexec /i AvamarClient-windows-x86_64-VERSION.msi where VERSION is the version number of the available installation package. The Welcome to the EMC Avamar for Windows Setup Wizard appears. 9. Follow the instructions in the wizard. 10. Click Finish to complete the installation procedure. The Avamar client icon appears in the system tray. Installing the software on Microsoft Windows 35 Installation Register the Avamar Client for Windows Before you back up or restore files on the DB2 server, you must register it with the Avamar server. To register the client: 1. Right-click the Avamar system tray icon. A menu appears. 2. Select Manage > Activate. The Activate Client Setup dialog box appears. 3. In the Administrator Server Address field, type the DNS hostname or IP address of the Avamar server. 4. In the Client Domain field, type the Avamar domain for the client. The default domain is “clients.” However, the Avamar system administrator may have defined other domains and subdomains. Consult the Avamar system administrator for the domain to use when registering this client. If you specify a subdomain (for example, clients/MyClients), then do not include a slash (/) as the first character. Including a slash as the first character causes an error and prevents you from registering this client. 5. Click Activate. The Client Activation Complete dialog box appears. 6. Click OK. The Activate Client Setup dialog box closes. Install the Avamar Plug-in for DB2 on Windows To install the Avamar Plug-in for DB2 on Windows: 1. Log in to the computer that hosts the DB2 server. 2. Open a web browser and type the following URL: http://AVAMARSERVER where AVAMARSERVER is the Avamar system network hostname (as defined in DNS) or IP address. You are redirected to the Avamar secure web server. 36 EMC Avamar 6.1 for IBM DB2 User Guide Installation 3. If the browser displays a security certificate warning message, click Yes or OK to allow redirection to the Avamar secure web server. The Secure Log On page appears. 4. Page down until the Downloads and Documents hyperlink is visible. 5. Click Downloads and Documents. The Web Documents & Downloads page appears. 6. Click the operating system hyperlink for the client computer. A directory listing appears. 7. Select the installation package: • For a 32-bit Microsoft Windows Server platform, select the AvamarDB2-windows-x86-VERSION.msi installation package. • For a 64-bit Microsoft Windows Server platform, select the AvamarDB2-windows-x86_64-VERSION.msi installation package. where VERSION is the version number of the software. 8. Either open the installation file in place (on the server) or double-click the installation file that you downloaded. The InstallShield Wizard appears. 9. Follow the instructions in the wizard. 10. Click Finish to complete the installation procedure. Uninstalling and upgrading on Microsoft Windows Installing a new version of the Avamar Plug-in for DB2 software does not require you to uninstall an earlier version of the software. The installation determines that an earlier version of the software is present, and then prompts you to upgrade to the new version or remove the current version. If you decide to remove the old installation, you must rerun the installation file to install the new version. The current installation session becomes an uninstall session and then terminates. You can also use the Add/Remove Programs feature in the Windows Control Panel to uninstall the Avamar Plug-in for DB2. Installing the software on Linux To install the Avamar Plug-in for DB2 on supported Linux platforms: 1. “Download Avamar installation packages for Linux” on page 38. 2. “Install and register the Avamar Client for Linux” on page 38. 3. “Install and configure the Avamar Plug-in for DB2” on page 39. Uninstalling and upgrading on Microsoft Windows 37 Installation Download Avamar installation packages for Linux To download the installation packages for Linux: 1. Log in to the DB2 server host as root. 2. Open a web browser and type the following URL: http://AVAMARSERVER where AVAMARSERVER is the Avamar server network hostname (as defined in DNS) or IP address. You are redirected to the Avamar secure web server. 3. If the browser displays a security certificate warning message, click Yes or OK to allow redirection to the Avamar secure web server. The Secure Log On page appears. 4. Page down until the Documents and Downloads hyperlink is visible. 5. Click Documents and Downloads. The Documents and Downloads page appears. 6. Click the operating system hyperlink for the client computer. A directory listing appears. 7. Download the Avamar Client for Linux installation package to a temporary install directory on the system. 8. Note the Avamar Client for Linux installation package file name. 9. Download the Avamar Plug-in for DB2 installation package to the same directory as the Avamar Client for Linux installation package. 10. Note the Avamar Plug-in for DB2 installation package file name. Install and register the Avamar Client for Linux To install and register the Avamar Client for Linux: 1. Log in to the DB2 server host as root. 2. Install the Avamar Client for Linux software by typing: cd /TMP rpm -ivh AvamarClient-linux-PLATFORM-VERSION.rpm where: • TMP is the temporary install directory. • PLATFORM is the platform type. • VERSION is the Avamar software version. 38 EMC Avamar 6.1 for IBM DB2 User Guide Installation The following appears in the command shell: ########################################### [100%] ########################################### [100%] Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 2066 avagent.d Info: Client Agent started. 3. Register and activate this client with the Avamar server by typing: /usr/local/avamar/bin/avregister The following appears in the command shell: === Client Registration and Activation This script will register and activate the client with the Administrator server. Enter the Administrator server address (DNS text name or numeric IP address, DNS name preferred): 4. Type the network hostname (as defined in DNS) of the Avamar Administrator server and press Enter. The following appears in the command shell: Enter the Avamar server domain [clients]: The default domain is “clients.” However, the Avamar system administrator may have defined other domains and subdomains. Consult the Avamar system administrator for which domain to use when registering this client. If you specify a subdomain (for example, clients/MyClients), then do not include a slash (/) as the first character. Including a slash as the first character causes an error and prevents you from registering this client. 5. Press Enter to accept the default domain (clients). The following appears in the command shell: avagent.d Info: Client Agent stopped. [ OK ] avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent.d Info: Client activated successfully. [ OK ] avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 3385 avagent.d Info: Client Agent started. [ OK ] Registration Complete. Install and configure the Avamar Plug-in for DB2 To install and configure the Avamar Plug-in for DB2: 1. Ensure that the Avamar Client for Linux has been properly installed and configured before installing the Avamar Plug-in for DB2. “Install and register the Avamar Client for Linux” on page 38 provides details. 2. Log in to the DB2 server host as root. Installing the software on Linux 39 Installation 3. Install the Avamar Plug-in for DB2 by typing: cd /TMP rpm -ivh AvamarDB2-linux-PLATFORM-VERSION.rpm where: • TMP is the temporary install directory • PLATFORM is the platform type. • VERSION is the Avamar software version. The following appears in the command shell: Preparing... ########################################### [100%] 1:AvamarDB2 ########################################### [100%] avagent Info: Stopping Avamar Client Agent (avagent)... avagent Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 23351 avagent Info: Client Agent started. Installation complete You may run /usr/local/avamar/bin/avdb2setup to configure this module to backup to the dpn. 4. Configure the Avamar Plug-in for DB2 by typing: /usr/local/avamar/bin/avdb2setup The following appears in the command shell: This script will configure the EMC Avamar DB2 plugin Enter path to Avamar Client installation [/usr/local/avamar]: 5. Type the full path to the Avamar client installation root directory and press Enter. The following appears in the command shell: Username for DB2 instance owner: db2dba where db2dba is the database instance owner. 6. Type the user account that owns this database instance and press Enter. The following appears in the command shell: Home directory for DB2 instance owner [/home/db2dba]: where /home/db2dba is the home directory for the database instance owner. 7. Type the full path to the home directory of the user who owns this database instance and press Enter. The following appears in the command shell: Writing /usr/local/avamar/etc/db2.cfg... Restarting client agent... avagent.d Info: Stopping Avamar Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 479284 avagent.d Info: Client Agent started. 40 EMC Avamar 6.1 for IBM DB2 User Guide Installation Uninstalling the software on Linux To uninstall the Avamar Plug-in for DB2 from a Linux platform: 1. Log in to the DB2 server host as root. 2. List installed Avamar software by typing: rpm -qa | grep Av The following appears in the command shell: AvamarClient-VERSION AvamarDB2-VERSION 3. Note the full package names. 4. Uninstall the Avamar Plug-in for DB2 by typing: rpm -e AvamarDB2-VERSION where AvamarDB2-VERSION is the Avamar Plug-in for DB2 installation package returned by the rpm command in step 2. The following appears in the command shell: Removing the AvamarDB2 libraries avagent Info: Stopping Avamar Client Agent (avagent)... avagent Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 23888 avagent Info: Client Agent started. 5. Uninstall the Avamar Client for Linux by typing: rpm -e AvamarClient-VERSION where AvamarClient-VERSION is the Avamar software installation package returned by the rpm command in step 2. The following appears in the command shell: avagent.d Info: Client Agent stopped. Upgrading the software on Linux To upgrade the Avamar Client for Linux and Avamar Plug-in for DB2 software, uninstall the old software and install the new software. Use of the Linux software upgrade command (rpm -Uh) is not supported. Uninstalling the software on Linux 41 Installation 42 EMC Avamar 6.1 for IBM DB2 User Guide CHAPTER 3 Backup This chapter describe how to use the Avamar Plug-in for DB2 to back up an entire database. Topics in this chapter include: ◆ ◆ ◆ Database preparation ............................................................................................. 44 On-demand backup ................................................................................................ 45 Scheduled backups................................................................................................. 48 Backup 43 Backup Database preparation This topic explains how to prepare the database for offline or online backups. Offline backups To perform offline backups of a DB2 database, ensure that no application is connected to the database when the operation begins and that no clients attempt to connect to the database during the backup operation. Ensure that no changes to the database are taking place during the backup window. Modifying a database in the middle of a backup can cause unpredictable application behavior, including failed backups. Online backups Perform the following steps before you perform the first online backup of a DB2 database: 1. Enable archive logging: • For DB2 version 9.1 and earlier, type: db2 update db cfg for DATABASE-NAME using LOGRETAIN ON where DATABASE-NAME is the name of the database to back up. • For DB2 version 9.5 and later, type: update db cfg for DATABASE-NAME using LOGARCHMETH1 LOGRETAIN update db cfg for DATABASE-NAME using LOGARCHMETH1 DISK where DATABASE-NAME is the name of the database to back up. 2. Perform an offline backup of the DB2 database. The database is now in a state that supports future online backups. You must also select the Create an ONLINE backup option for the dataset or for an on-demand backup. DB2 database partition backups Before you back up a DB2 database partition, you must configure the Backup agent to use the instance owner’s domain account service on all Windows systems in the DPF environment. To configure the Backup agent service: 1. From the Windows Start menu, select Run. The Run dialog box appears. 2. In the Open field, type services.msc. The Services window appears. 44 EMC Avamar 6.1 for IBM DB2 User Guide Backup 3. In the Services window, configure the Backup agent service: a. Right-click Backup agent, and then select Properties. The Backup agent Properties dialog box appears. b. Click the Log On tab, and then select This account. c. Click Browse. The Select User dialog box appears. d. Select the instance owner’s domain account, and then click OK. e. Click OK to close the Backup agent Properties dialog box. 4. From the Services window, right-click Backup agent and select Restart. On-demand backup To perform an on-demand backup: 1. Prepare the database according to the instructions in “Database preparation” on page 44. 2. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears. 3. Click the Select for Backup tab. 4. In the client tree, select the DB2 server. In a DPF environment, select the particular DPF node to back up individual partitions in a database, or select the catalog node to back up a combination of partitions or all partitions. 5. Leave the Browse for Files, Folders or Directories option selected. 6. Select the DB2 plug-in. 7. Browse to a DB2 instance folder, and then select the instance folder, a single database, or multiple databases. On-demand backup 45 Backup 8. Select Actions > Back Up Now. The On Demand Backup Options dialog box appears. 9. Complete the settings in the On Demand Backup Options dialog box: a. Select a retention policy: – To automatically delete this backup from the Avamar server after a specific amount of time, select Retention period and specify the number of days, weeks, months, or years for the retention period. – To automatically delete this backup from the Avamar server on a specific calendar date, select End date and browse to that date on the calendar. – To keep this backup for as long as this client remains active in the Avamar server, select No end date. b. From the Encryption method list, select an encryption method to use for client/server data transfer during the backup. The encryption technology and bit strength for any given client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information. 46 EMC Avamar 6.1 for IBM DB2 User Guide Backup c. Click More Options. The Backup Command Line Options dialog box appears. 10. Complete the settings in the Backup Command Line Options dialog box: a. Choose whether to perform an online or offline database backup by selecting or clearing the Create an ONLINE backup checkbox. b. If you are performing an online database backup, choose whether to include or exclude archive logs in the backup by selecting or clearing the Exclude archive logs in ONLINE backup checkbox. If you exclude archive logs from the database backup, ensure that archive log files are included in file system backups. Failure to do so might result in loss of data. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. In the Database Partition Numbers field, specify the partitions to include in the backup: – To specify all database partitions, type ALL or all. You must select this option if this is the first backup after you enable LOGRETAIN. Specifying all partitions numerically is not the same as using ALL or all. – To specify a list of partitions, type the partition numbers in a comma-separated list. – To specify a single partition, leave this field blank. e. To store the backup on a Data Domain system instead of the Avamar server: 1. Select Store backup on Data Domain system. 2. Select the Data Domain system from the Store backup on Data Domain system list box. 11. Click OK to return to the On Demand Backup Options dialog box. On-demand backup 47 Backup 12. Click OK again. The On Demand Backup Options dialog box closes. 13. Click View Activity to view status details for the backup or click Close. Scheduled backups To back up the DB2 server on a regular schedule: 1. Create a dataset for DB2 server backups, as discussed in “Creating a dataset” on page 48. 2. Create a group for the backups, as discussed in “Creating a group” on page 51. During the group creation process, you select: • The new dataset for the new group. • A schedule for the new group. • A retention policy for the new group. • The IBM DB2 client to add to the new group. 3. Enable scheduling for the group, as discussed in “Enabling scheduled backups” on page 55. The EMC Avamar Administration Guide provides more information about groups, group policy, datasets, schedules, and retention policies. Creating a dataset To create a dataset: 1. In Avamar Administrator, select Tools > Manage Datasets. The Manage All Datasets window appears. 48 EMC Avamar 6.1 for IBM DB2 User Guide Backup 2. Click New. The New Dataset dialog box appears. 3. Complete the settings in the New Dataset dialog box: a. In the Name box, type a name for the dataset. The name can include alphanumeric characters (A-Z, a-z, 0-9) and the following special characters: period (.), hyphen (-), and underscore (_). Do not use Unicode characters or the following special characters: ` ~ ! @ # $ % ^ &*()=+[]{}|\/;:'"<>,? a. Click the Source Data tab. b. Select Enter Explicitly. c. Select the DB2 plug-in from the Select Plug-In Type list. d. Click (Browse for files and/or folders). The Select Files And/Or Folders dialog box appears. 4. In the Select Files And/Or Folder dialog box: a. Select the DB2 server from the Clients tree. b. Select the DB2 plug-in. Scheduled backups 49 Backup c. Select the database to include in the dataset. d. Click OK. The Select File And/Or Folder dialog box closes and the New Dataset dialog box lists the files or folders that you selected. 5. Click the Options tab. 6. Complete the setting on the Options tab: a. Choose whether to perform an online or offline database backup by selecting or clearing the Create an ONLINE backup checkbox. b. If you are performing an online database backup, choose whether to include or exclude archive logs in the backup by selecting or clearing the Exclude archive logs in ONLINE backup checkbox. If you do not include archive logs in the database backup, ensure that archive log files are included in file system backups. Failure to do so might result in loss of data. c. Type the Instance Admin Username and Instance Admin Password. 50 EMC Avamar 6.1 for IBM DB2 User Guide Backup d. In the Database Partition Numbers field: – To specify all database partitions, type ALL or all. – To specify a list of partitions, for example partitions 1, 2 and 3, type 1,2,3. – To specify a single partition, leave this field blank. e. To store the backup on a Data Domain system: 1. Select Store backup on Data Domain system. 2. Select the Data Domain system from the Store backup on Data Domain system list box. 7. Click OK. Creating a group To create a group: 1. In Avamar Administrator, click the Policy launcher button. The Policy window appears. Scheduled backups 51 Backup 2. Select the Groups tab. 3. In the left pane, select the Avamar domain to which the group should belong. 4. Select Actions > New Group. The New Group wizard appears. 5. Complete the settings in the New Group dialog box: a. In the Name box, type a name for the new group. The name can include alphanumeric characters (A-Z, a-z, 0-9) and the following special characters: period (.), hyphen (-), and underscore (_). Do not use Unicode characters or the following special characters: ` ~ ! @ # $ % ^ &*()=+[]{}|\/;:'"<>,? b. Clear the Disabled checkbox to use this group for scheduled client backups. Selecting the checkbox disables backups for the group. c. From the Encryption method list, select an encryption method to use for client/server data transfer during the backup. The encryption technology and bit strength for any given client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information. 52 EMC Avamar 6.1 for IBM DB2 User Guide Backup d. (Optional) To override the assigned schedule for this group, select the Override Schedule option. After selecting Override Schedule: – Select Skip Next Backup to skip the next scheduled backup entirely. – Select Run Next Backup Once to perform the next scheduled backup one time only. 6. Click Next. The next wizard screen appears with dataset information. 7. From the Select an Existing Dataset list, select the dataset that you created in “Creating a dataset” on page 48. Scheduled backups 53 Backup 8. Click Next. The next wizard screen appears with schedule information. 9. From the Select an Existing Schedule list, select a schedule. You cannot edit schedules in this screen. Detailed schedule properties are shown so that you can review them before you make a selection. The EMC Avamar Administration Guide provides information about editing schedule properties. 10. Click Next. The next wizard screen appears with retention policy information. 11. From the Select an Existing Retention Policy list, select a retention policy. You cannot edit retention policies in this screen. Detailed retention policy properties are shown so that you can review them before you make a selection. The EMC Avamar Administration Guide provides information about editing retention policy properties. 54 EMC Avamar 6.1 for IBM DB2 User Guide Backup 12. Click Next. The final wizard screen appears with a tree of domains and clients. This screen is used to build a list of clients that are members of the group. 13. Select the DB2 server from the client list. 14. Click Finish. The wizard closes and the new group appears in the Policy window. Enabling scheduled backups To enable scheduled backups: 1. In Avamar Administrator, click the Policy launcher button. The Policy window appears. Scheduled backups 55 Backup 2. Click the Policy Management tab. 3. Click the Groups tab. 4. Select the group that you created in “Creating a group” on page 51. 5. Select Actions > Group > Disable Group. This clears the Disable Group option on the Actions > Group menu. A confirmation message appears. 6. Click Yes to enable this group. 56 EMC Avamar 6.1 for IBM DB2 User Guide CHAPTER 4 Restore and Recovery This chapter describes how to restore an entire database and recover its state. Topics in this chapter include: ◆ ◆ ◆ ◆ ◆ ◆ Restoring DB2 databases to the original location .................................................... Restoring DB2 databases to a different location ...................................................... Restoring DB2 database partitions .......................................................................... Restoring one or more table spaces......................................................................... Recovering retired clients ........................................................................................ Disaster recovery..................................................................................................... Restore and Recovery 58 66 70 73 78 82 57 Restore and Recovery Restoring DB2 databases to the original location Refer to the appropriate procedures to restore DB2 databases to the original directory on the original client: ◆ “Restoring an offline backup” on page 58 ◆ “Restoring an online backup with archive logs” on page 61 Restoring an offline backup Use this procedure to restore an offline backup to its original directory. An offline database name is prefixed with “c-.” To restore DB2 databases: 1. Ensure that the DB2 database is inactive. During the restore operation, no attempts to connect to the database should be made. 2. Start Avamar Administrator and log in. 3. Click the Backup & Restore launcher button. The Backup and Restore window appears. 4. Click Select for Restore. 5. In the clients tree, select the DB2 server. 6. Click By Date. 7. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 8. Select a backup from the backups table. The backup contents appear below the Backup History pane. 9. Expand the DB2 instance folder. 10. Select one or more database backups to restore. An offline database name is prefixed with “c-.” 58 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 11. Select Actions > Restore Now. The Restore Options dialog box appears. 12. Complete the settings in the Restore Options dialog box: a. Select Restore everything to its original location. b. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. Restoring DB2 databases to the original location 59 Restore and Recovery c. Click More Options. The Restore Command Line Options dialog box appears. 13. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore Only option. Leave the Recovery Type panel as is. The Recovery Type options apply only to the Restore and Recover option. b. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. c. Leave the Directory path to restore archive logs field blank. It only applies when the Restore only archive logs from ONLINE backup option is selected. A restore of a cold backup fails if the Directory path to restore archive logs field contains a path. The error message for this type of failure is similar to: restore: Invalid option for archive logs. Backup image db2inst1/c-AVAMAR1-1-sles10-32-db2-95-dpf does not contain archive logs d. Leave Database Name field blank. It only applies to redirected restores. e. Click OK to close the Restore Command Line Options dialog box. 14. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 15. Click OK. 60 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery Restoring an online backup with archive logs If you have an online backup that contains archive logs, you can restore both the database and the archive logs and automatically roll the database forward to: ◆ The end of the backup (available only for backups of DB2 9.5 databases and later) ◆ The end of the logs ◆ A specific point in time You can also restore only the database or only the archive logs. An online database backup that includes archive logs is prefixed with “hl-.” Restoring and recovering the database To restore both the database and the archive logs, and automatically roll the database forward: 1. Start Avamar Administrator and log in. 2. Click the Backup & Restore launcher button. The Backup and Restore window appears. 3. Click Select for Restore. 4. In the clients tree, select the DB2 server. 5. Click By Date. 6. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 7. Select a backup from the backups table. The backup contents appear below the Backup History pane. 8. Expand the DB2 instance folder. 9. Select one or more databases backup to restore. An online database that includes archive logs is prefixed with “hl-.” Restoring DB2 databases to the original location 61 Restore and Recovery 10. Click the Restore Now button. The Restore Options dialog box appears. 11. Complete the settings in the Restore Options dialog box: a. Select Restore everything to its original location. b. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. c. Click More Options. The Restore Command Line Options dialog box appears. 12. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore and Recover option. b. From the Type of Recovery list, select one of the following recovery types: – End of logs recovers the database by performing a rollforward operation to the end of the logs. – Point In Time recovers the database by performing a rollforward operation to a specific point in time. To use the Point In Time recovery type requires you to type a date and time in the Date and Time field. Use the yyyy-mm-dd hh:mm:ss format. The time must be in the time zone of the client system. 62 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery The entry can be truncated to the desired precision level. For example, minutes and seconds can be omitted for convenience. – End of Backup recovers the database by performing a rollforward operation to the end of the backup. The End of Backup option is valid for DB2 9.5 and later. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. In the Directory path to restore archive logs field, type the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify, and restores the archive logs to this subdirectory. e. Leave Database Name field blank. It only applies to redirected restores. The following figure shows an example Restore Command Line Options dialog box: f. Click OK to close the Restore Command Line Options dialog box. 13. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 14. Click OK. Restoring DB2 databases to the original location 63 Restore and Recovery Restoring only the database If you have an online backup that does not contain archive logs, you can first restore the database, and then manually roll the database forward to the desired point in time by issuing a rollforward command on the DB2 server. To restore only the database: 1. Complete step 1 through step 11 in “Restoring and recovering the database” on page 61. The Restore Command Line Options dialog box appears. 2. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore Only option. b. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. c. Leave the Directory path to restore archive logs field blank. It only applies when the Restore only archive logs from ONLINE backup option is selected. d. Leave the Database Name field blank. It only applies to redirected restores. The following figure shows an example Restore Command Line Options dialog box: e. Click OK to close the Restore Command Line Options dialog box. 3. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 4. Click OK. 64 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 5. After the restore completes, restore the archive logs: a. Restore the archive logs from a file system backup to the SQLOGDIR directory. The SQLOGDIR directory is the location stored by the DB2 SQLOGDIR variable. b. Use the rollforward command on the DB2 server to roll the database forward to the desired point in time. The following command performs a rollforward operation on the database to the end of the archive logs: db2 rollforward db DB-NAME to end of logs and complete db2 rollforward db DB-NAME to end of logs and complete overflow log path(/tmp/alogs) where DB-NAME is the database name. If a database is in a rollforward pending state and you do not run the rollforward command, the next Avamar Plug-in for DB2 backup of this database fails with an error message. The error message recommends that the database be rolled forward. You can perform one more restore operation on a database that is in a rollforward pending state. Restoring only the archive logs To restore only the archive logs from an online backup: 1. Complete step 1 through step 11 in “Restoring and recovering the database” on page 61. 2. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore only archive logs from ONLINE backup option. b. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. c. In the Directory path to restore archive logs field, type the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify, and restores the archive logs to this subdirectory. d. Leave Database Name field blank. It only applies to redirected restores. Restoring DB2 databases to the original location 65 Restore and Recovery The following figure shows an example Restore Command Line Options dialog box: e. Click OK to close the Restore Command Line Options dialog box. 3. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 4. Click OK. Restoring DB2 databases to a different location Use this procedures to restore DB2 databases to a different directory on the original client or to a different client. To restore DB2 databases: 1. Start Avamar Administrator and log in. 2. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears. 3. Click Select for Restore. 4. In the clients tree, select the DB2 server. 5. Click By Date. 66 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 6. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 7. Select a backup from the backups table. The backup contents appear below the Backup History pane. 8. Expand the DB2 instance folder. 9. Select one or more databases to restore, or select the top-level folder to restore all backups. An offline database name is prefixed with “c-.” 10. Select Actions > Restore Now. The Restore Options dialog box appears. 11. Complete the settings in the Restore Options dialog box: a. Select Restore everything to a different location. b. Click Browse. The Browse for Client Destination dialog box appears. c. Select the target client from the client tree, and then click OK. d. In the Items Marked for Restore pane, click Set Destination. The Set Destination dialog box appears. e. In the Set Destination dialog box, click Browse. The Browse for File, Folder, or Directory dialog box appears. f. In the directory tree, select the destination. The destination is a drive letter (for example, C: or D:) for Windows or the home directory of the instance (for example, /home/db2inst1) for Linux or UNIX. g. Click OK. Restoring DB2 databases to a different location 67 Restore and Recovery The following figure shows the Set Destination dialog after selecting a destination: h. Click OK. The destination appears in the Destination column: i. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. j. Click More Options. The Restore Command Line Options dialog box appears. 68 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 12. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore Only option. b. Leave the Recovery Type panel as is. The Recovery Type options apply only to the Restore and Recover option. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. In the Directory path to restore archive logs field, type the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify and restores the archive logs to this subdirectory. e. Type the name of the database in the Database Name field. f. Click OK to close the Restore Command Line Options dialog box. 13. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 14. Click OK. 15. Manually roll the database forward, if required. “Rolling the database forward” on page 69 provides more information. Rolling the database forward You must roll the database forward if you used the Restore Only option to restore a hot backup. A rollforward operation does not apply to restores of a cold backup. To manually roll the database forward to the desired point in time, use the rollforward command on the DB2 server. The following command is an example: db2 rollforward db DB-NAME to end of logs and complete where DB-NAME is the database name. The command rolls the database forward to the end of the archive logs. If you do not run the rollforward command, subsequent Avamar Plug-in for DB2 backups and restores fail with an error message, which recommends that the database be rolled forward. Restoring DB2 databases to a different location 69 Restore and Recovery Restoring DB2 database partitions The user interface lists all partition backups under the client that contains the catalog partition, otherwise referred to as the catalog node. The restore operation option you select depends on the location of the partition: ◆ If the partition is located on a non-catalog node, perform a redirected restore. You restore the partition to a different location from the viewpoint of the catalog node. ◆ If the partition is located on the catalog node, restore the partition to the original location. The Avamar Plug-in for DB2 restores each partition backup separately. You cannot restore all partition backups in a single restore operation. You must restore database partitions from the catalog partition only. To restore database partitions: 1. Start Avamar Administrator and log in. 2. Click the Backup & Restore launcher button. The Backup and Restore window appears. 3. Click Select for Restore. 4. In the clients tree, select the client that contains the catalog node. 5. Click By Date. 6. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 7. Select a backup from the backups table. The backup contents appear below the Backup History pane. 8. Expand the DB2 instance folder. 9. Select a partition to restore 10. Select Actions > Restore Now. The Restore Options dialog box appears. 11. Complete the settings in the Restore Options dialog box: a. To restore a partition to the catalog node, select Restore everything to its original location, and then continue to step c on page 72. b. To restore a partition to a non-catalog node: 1. Select Restore everything to a different location. 2. Click Browse. The Browse for Client Destination dialog box appears. 70 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 3. Select the target client from the client tree, and then click OK. 4. In the Items Marked for Restore pane, click Set Destination. The Set Destination dialog box appears. 5. In the Set Destination dialog box, click Browse. The Browse for File, Folder, or Directory dialog box appears. 6. In the directory tree, select the destination. The destination is a drive letter (for example, C: or D:) for Windows or the home directory of the instance (for example, /home/db2inst1) for Linux or UNIX. 7. Click OK. The following figure shows the Set Destination dialog after selecting a destination: 8. Click OK. The destination appears in the Destination column. Restoring DB2 database partitions 71 Restore and Recovery c. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. d. Click More Options. The Restore Command Line Options dialog box appears. 12. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore Only option. b. Leave the Recovery Type panel as is. The Recovery Type options apply only to the Restore and Recover option. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. In the Directory path to restore archive logs field, type the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify and restores the archive logs to this subdirectory. e. Type the name of the database in the Database Name field. f. Click OK to close the Restore Command Line Options dialog box. 13. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 14. Click OK. 15. Perform a rollforward operation from the catalog node. “Rolling the database forward” on page 69 provides more information. 72 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery Restoring one or more table spaces Before you use the granular recovery feature to restore table spaces from an online or offline backup set LOGARCHMETH1 to LOGRETAIN, and then perform an offline backup. “Online backups” on page 44 provides instructions to set up the database and create an initial offline backup. The following topics provide instructions for restoring one or more table spaces to a DB2 stand-alone or DPF environment: ◆ “Restoring table spaces in a stand-alone DB2 environment” on page 73 ◆ “Restoring table spaces in a DB2 DPF environment” on page 76 Restoring table spaces in a stand-alone DB2 environment To restore one or more table spaces from a backup: 1. Start Avamar Administrator and log in. 2. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears. 3. Click Select for Restore. 4. In the clients tree, select the DB2 server. 5. Click By Date. 6. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 7. Select a full backup from the backups table. The backup contents appear below the Backup History pane. The Browse for Image Restore and Browse for Granular Restore buttons appear above the Contents of Backup directory tree. 8. Select the top-level folder to select the entire plug-in, or select one or more databases for the granular browse operation. Restoring one or more table spaces 73 Restore and Recovery 9. Click (the Browse for Granular Restore button). The Destination Client Selection dialog box appears. 10. Leave Restore everything to its original location selected and click OK. You cannot perform a redirected restore of a DB2 table space to a DB2 stand-alone environment. The Contents of Backup panel lists a directory tree for the selection you made in step 8 on page 73. 11. Expand the folders in the directory tree to view table spaces available for restore. 12. Select one or more table spaces. The following figure shows the USERSPACE1 table space selected for restore. 74 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery The Backup and Restore window does not display the table space size correctly in the Size column. EMC plans to fix this issue in a future release. 13. Select Actions > Restore Now. The Restore Options dialog box appears. 14. Complete the settings in the Restore Options dialog box: a. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. b. Click More Options. The Restore Command Line Options dialog box appears. 15. Complete the settings in the Restore Command Line Options dialog box: a. To restore table spaces other than the SYSCATSPACE table space, select Restore Only. b. To restore the SYSCATSPACE table space, select Restore and Recover, and then select End of logs from the Type of Recovery list. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. Leave the Directory path to restore archive logs field blank. e. Leave the Database Name field blank. Restoring one or more table spaces 75 Restore and Recovery f. (Renamed table spaces only) To restore renamed table spaces: 1. Click More to display the Enter Attribute option. 2. In the Enter Attribute field, type renamed_tablespace_list. 3. In the Enter Attribute Value field, type the name of the renamed table space. 4. Click . The attribute and value pair appears in the text box: g. Click OK to close the Restore Command Line Options dialog box. 16. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 17. Click OK. Restoring table spaces in a DB2 DPF environment There are two methods for restoring table spaces in a DB2 DPF environment: ◆ To restore a table space that is local to the catalog partition, use the procedure in “Restoring table spaces in a stand-alone DB2 environment” on page 73. ◆ To restore a table space that is not local to the catalog partition, use the following procedure to perform a redirected restore from the catalog node to the target node. You cannot specify a recovery type for a table space restore in a DPF environment. 76 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery To restore one or more table spaces in a DPF environment: 1. Complete step 1 through step 9 in “Restoring table spaces in a stand-alone DB2 environment” on page 73. 2. In the Client Selection dialog box: a. Click Restore everything to a different location. b. Click Browse, and then select the DPF node that contains the target partition for the table space restore. c. Click OK to close the dialog box. 3. Expand the folders in the directory tree to view table spaces available for restore. 4. Select one or more table spaces. The Backup and Restore window does not display the table space size correctly in the Size column. EMC plans to fix this issue in a future release. 5. Select Actions > Restore Now. The Restore Options dialog box appears. 6. Complete the settings in the Restore Options dialog box: a. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. Restoring one or more table spaces 77 Restore and Recovery b. Select Restore everything to a different location. c. Click Browse to browse the list of clients. d. Select the same DPF node that you selected in step 2 on page 77. e. In the Destination field, type the path to the database. f. Click More Options. The Restore Command Line Options dialog box appears. 7. Complete the settings in the Restore Command Line Options dialog box: a. To restore table spaces other than the SYSCATSPACE table space, select Restore Only. a. To restore the SYSCATSPACE table space, select Restore and Recover, and then select End of logs from the Type of Recovery list. b. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. c. If the backup for this restore operation is an online backup and you intend to restore archive log files, type the fully qualified pathname of an existing top-level directory in the Directory path to restore archive logs field. The restore operation creates a subdirectory below the directory path you specify and restores the archive logs to this subdirectory. d. In the Database Name field, type the name of the database from which the backup was originally taken. e. Click OK to close the Restore Command Line Options dialog box. 8. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 9. Click OK. 10. Manually roll the table space forward to the desired point in time by using the rollforward command on the DB2 server. Recovering retired clients To recover a retired client: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears. 2. Click the Select for Restore tab. 3. Select the client from the MC_RETIRED domain. 4. Click the By Date tab. 78 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery 5. Select a backup date from the calendar. a. Use the year and month navigational arrows to browse to a backup. Dates highlighted by yellow indicate a valid backup was performed on that date. b. Click a date highlighted by yellow. A list of backups that were performed on that date appears in the Backups table next to the calendar. 6. Select a backup from the backups table. The backup contents appear as a list below the Backup History pane. 7. In the contents pane below the calendar, expand the folders to display the DB2 instance folder. 8. Select the database backup to restore. 9. Select Actions > Restore Now. The Restore Options dialog box appears. 10. Complete the settings in the Restore Options dialog box: a. Select Restore everything to a different location. b. Click Browse. The Browse for Client Destination dialog box appears. c. Select the target client from the Browse for Client Destination dialog box. The target client name appears in the Restore Destination Client field. Recovering retired clients 79 Restore and Recovery The target client name has the same name as the MC_RETIRED client name. d. Click Set Destination. The Set Destination dialog box appears. e. Click Browse in the Set Destination dialog box. The Browse for File, Folder, or Directory dialog box appears. f. In the Browse for File, Folder, or Directory dialog box: 1. Select the target client to expand the branch. 2. Select the database instance. 3. Click OK. g. Click OK to close the Set Destination dialog box. The database instance appears in the Destination column of the Items Marked for Restore table. h. From the Encryption method list, select an encryption method to use for client/server data transfer during this restore. The exact encryption technology and bit strength used for client/server connection depends on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides more information. 11. Click More Options. The Restore Command Line Options dialog box appears. 12. Complete the settings in the Restore Command Line Options dialog box: a. Select the Restore and Recover option. Alternately, you can select the Restore Only option and perform a manual rollforward operation after the restore completes. To perform a manual rollforward operation, use the overflow log path option with rollforward command, and then recover the database to the end of logs or to a point in time. DB2 documentation provides more information about the rollforward command. 80 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery b. From the Type of Recovery list, select one of the following recovery types: – End of logs recovers the database by performing a rollforward operation to the end of the backup. For a retired client recovery, the End of logs option recovers the database to the end of backup, not the end of the logs. – Point In Time recovers the database by performing a rollforward operation to a specific point in time. To use the Point In Time recovery type requires you to type a date and time in the Date and Time field. Use the yyyy-mm-dd hh:mm:ss format. The time must be in the time zone of the client system. You can truncate the time entry. For example, minutes and seconds can be omitted for convenience. – End of Backup recovers the database by performing a rollforward operation to the end of the backup. The End of Backup option is valid for DB2 9.5 and later. c. Type the instance owner’s user name in the Instance Admin Username field and the instance owner’s password in the Instance Admin Password field. d. In the Directory path to restore archive logs field, type the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify and restores the archive logs to this subdirectory. e. In the Database Name field, type the name of the database from which the backup was originally taken. f. Click OK to close the Restore Command Line Options dialog box. 13. Click OK to close the Restore Options dialog box. The following status message appears: Restore initiated. 14. Click OK. Recovering retired clients 81 Restore and Recovery Disaster recovery This section provides instructions for recovering the DB2 server following the loss of: ◆ The DB2 application due to corruption or other circumstances ◆ The server hardware Recovering the DB2 application The following procedure assumes that only the DB2 application requires recovery. All other Avamar components installed on the host are intact. Refer to the DB2 documentation for help with steps 1–4. To recover the DB2 application: 1. Uninstall the current installation of the DB2 application. 2. Delete all DB2 application files and directories. 3. Install the same version of the DB2 application that was previously installed. 4. Re-create the DB2 instance (UNIX) or DB2 copy (Windows) with the same name that was previously used. 5. Restore a full backup of the DB2 database to the original location by completing the appropriate instructions in “Restoring DB2 databases to the original location” on page 58. Recovering the DB2 server The following procedure assumes that a replacement machine is available. To recover the DB2 server to the replacement machine: 1. Install the same version and release of the operating system on the replacement machine. 2. Log in to the machine. 3. Configure the machine with the IP address and hostname from the old machine. 4. Install the same version of the DB2 application. 5. Re-create the DB2 instance (UNIX) or DB2 copy (Windows) with the same name that was previously used. Refer to the vendor documentation for instructions. 6. Install and register the Avamar File System client. Chapter 2, “Installation,” provides instructions. 7. Install the Avamar Plug-in for DB2. Chapter 2, “Installation,” provides instructions. 82 EMC Avamar 6.1 for IBM DB2 User Guide Restore and Recovery Recovering the DB2 server in a DPF environment To recover the DB2 server in a DPF environment: 1. Install the DB2 application on the catalog node and other participating nodes. 2. Re-create the DB2 instance (UNIX) or DB2 copy (Windows) with the same name that was previously used. 3. Restore the catalog node backup by performing a restore from the catalog node. “Restoring DB2 database partitions” on page 70 provides more information. 4. Restore all other node backups by performing a redirected restore. “Restoring DB2 database partitions” on page 70 provides more information. Disaster recovery 83 Restore and Recovery 84 EMC Avamar 6.1 for IBM DB2 User Guide APPENDIX A Plug-in Options Topics in this appendix include: ◆ ◆ ◆ How to set plug-in options ...................................................................................... 86 Backup options....................................................................................................... 86 Restore options....................................................................................................... 87 Plug-in Options 85 Plug-in Options How to set plug-in options Plug-in options enable you to control specific actions for on-demand backups, restores, and scheduled backups. The plug-in options that are available depend on the operation type and client plug-in type. You specify plug-in options when you perform on-demand backup or restore operations, or when you create a dataset for a scheduled backup. You set plug-in options in Avamar Administrator with the graphical user interface (GUI) controls (text boxes, checkboxes, radio buttons, and so forth). In addition to using the GUI controls, you can type an option and its value in the Enter Attribute and Enter Attribute Value fields, which are used for special circumstances. “How to specify options” on page 100 provides more information. The Avamar software does not check or validate the information you type in the Enter Attribute and Enter Attribute Value fields. In addition, the values in the Enter Attribute and Enter Attribute Value fields override settings that you specify with the GUI controls. Detailed instructions on how to access and set plug-in options during a backup or restore are available in Chapter 3, “Backup,” and Chapter 4, “Restore and Recovery.” Backup options The following table lists the plug-in options for the Avamar plug-in for IBM DB2. Use these options when you perform an on-demand backup or when you configure a dataset for scheduled backups. Table 6 Backup plug-in options (page 1 of 2) Setting Description Create an ONLINE backup Backs up the database while it is operational. This type of backup is also known as a hot backup. Notice: DB2 Archive Logging must be enabled to successfully perform online backups. 86 Exclude archive logs in ONLINE backup Excludes the archive logs from the backup. If you exclude the archive logs from a database backup, ensure that archive logs are included in file system backups. Failure to do so might result in loss of data. Instance Admin Username Specifies the instance owner’s user name. Instance Admin Password Specifies the instance owner’s password. Database Partition Numbers Specifies a comma-separated list of database partition numbers: • To specify all database partitions, type ALL or all. • To specify a list of partitions, for example, partitions 1, 2, and 3, type 1,2,3. • To specify a single partition, leave this field blank. EMC Avamar 6.1 for IBM DB2 User Guide Plug-in Options Table 6 Backup plug-in options (page 2 of 2) Setting Description Store backup on Data Domain system Uses a Data Domain system you select from the list to store the Avamar Plug-in for DB2 backup. Advanced Options Enable debugging messages Writes maximum information to log files. If selected, the backup creates very large log files. Restore options The following table lists plug-in options for the Avamar plug-in for IBM DB2. Use these options when you perform restore operations. Table 7 Restore plug-in options (page 1 of 2) Setting Description Recover OR Restore Restore and Recover For online backups that include archive logs, restores both the database and the archive logs, and then rolls the database forward. If you select the Restore and Recover option you must also: 1. Select one of the options from the Type of Recovery list. 2. Specify a value in the Directory path to restore archive logs field. Restore Only Performs only a restore of the backups. Select this option to restore a backup without recovery, to restore offline backups, or to restore online backups that do not have archive logs. Restore only archive logs from ONLINE backup Restores only the archive logs from the backup. Recovery Type Type of Recovery When the Restore and Recover option is selected, select a recovery option from the list: • End of Logs — Rolls the database forward until the end of the archive logs. • Point In Time — Rolls the database forward until a certain point in time, which you specify in the Date and Time field. • End of Backup — Rolls the database forward until the end of the backup. This option is available only for DB2 v9.5 and later. Date and Time When Point In Time is selected from the Type of Recovery list, specify the recovery date and time by using the following format: yyyy-mm-dd hh:mm:ss Specify the time that corresponds to the timezone of the client system. You can truncate the time entry. For example, minutes and seconds can be omitted for convenience. General Instance Admin Username Specifies the instance owner’s user name. Instance Admin Password Specifies the instance owner’s password. Restore options 87 Plug-in Options Table 7 Restore plug-in options (page 2 of 2) Setting Description Directory path to restore archive logs Specifies the fully qualified pathname of an existing top-level directory. The restore operation creates a subdirectory below the directory path you specify, and restores the archive logs to this subdirectory. Database Name Specifies the new name for the database when you perform a directed restore. DB2 supports database names that include up to eight characters. Advanced Options Enable debugging messages 88 EMC Avamar 6.1 for IBM DB2 User Guide Writes maximum information to log files. If selected, the restore creates very large log files. APPENDIX B Command-Line Interface This appendix describes how to use the command-line interface (CLI) to back up or restore DB2 database files. Topics in this appendix include: ◆ ◆ ◆ Overview................................................................................................................. 90 Command reference ................................................................................................ 92 CLI example commands .......................................................................................... 97 Command-Line Interface 89 Command-Line Interface Overview The Avamar Plug-in for DB2 provides a command line interface from which you can back up or restore DB2 database files by using the avdb2 command. You can use the CLI from all operating systems that the Avamar Plug-in for DB2 supports. The avdb2 command, which is available as a binary or executable, is located in the installation directory on the specific platform. ◆ For AIX and Linux platforms, the avdb2 binary is located in /usr/local/avamar. ◆ For a Windows platform, the avdb2 executable is located in C:\Program Files\avs\bin. You run the avdb2 command from a command shell on AIX or Linux platforms, or from the Command Prompt window on a Windows platform. Available operations The avdb2 command works with three main functions, which are referred to as operations: browse, backup, and restore. You specify an operation with the avdb2 command by using the --operation option. Browse The browse operation returns a list of client data available for backup. The CLI displays the list as formatted text or as XML text. The format depends on the value you specify for the --format option. Backup The backup operation backs up DB2 data to the Avamar server or a Data Domain system. You can specify plug-in options for the backup. Many of these plug-in options are the same options that you specify from Avamar Administrator in the Backup Command Line Options dialog box or on the Options tab when you create a dataset. Restore The restore operation restores DB2 data to the original location or to a different location. You can restore entire databases or single table spaces. You can specify plug-in options for the restore. These plug-in options are similar to the options you specify from Avamar Administrator in the Restore Command Line Options dialog box. Options There are three ways to specify options for the avdb2 command: ◆ Type the individual options on the command line. ◆ Use the avdb2.cmd file to specify options. For example, type each option on its own line in the avdb2cmd file: --online --db2-inst-user=db2inst1 ◆ 90 Create an option file as a text file, and then specify the option file on the command line using the --flagfile=FILE option, where FILE is the full path and file name of the option file. EMC Avamar 6.1 for IBM DB2 User Guide Command-Line Interface Help To display help content for all operations and options, type: avdb2 --help To display help content for a specific operation, type: avdb2 --help --operation=OPERATION where OPERATION is browse, backup, or restore. DB2 instance password security on AIX and Linux All backup and restore operations require you to specify the DB2 instance user name and password by using the --db2_inst_user and --inst-admin-password options. You can specify these options directly on the command line or in the avdb2.cmd file. When you specify the --db2_inst_user and --inst-admin-password options on the command line on AIX and Linux platforms, the user name and password appear as plain text to other users who are logged in to the system. For example, a user can use the ps -eaf command to view process status information for avdb2. The following output illustrates the information that a user can see when you specify the --db2_inst_user and --inst-admin-password options on the command line: # ps -eaf|grep avdb2 root 21569 15301 3 10:43 pts/3 00:00:00 ./avdb2 --sysdir=/usr/local/avamar/etc --operation=backup --id=guest@/clients/db2-client.example.com --password=guest123 --server=avamar1.example.emc --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=iso*help db2inst1/AVAMAR1 To prevent users on AIX and Linux from seeing DB2 instance user name and password information, specify the --db2_inst_user and --inst-admin-password options in the avdb2.cmd file: 1. Log in to the DB2 server as root. 2. Open the avdb2.cmd file in a text editor and add the --db2_inst_user and --inst-admin-password options by typing: --[avdb2]db2_inst_user=USERNAME --[avdb2]inst_admin_password=PASSWORD where: • USERNAME is the DB2 instance owner’s user name. • PASSWORD is the password for the DB2 instance owner’s password. 3. Save the changes to the avdb2.cmd file and close the text editor. 4. Change the permission on avdb2.cmd to root by typing: chmod 600 avdb2.cmd This chmod 600 command allows only the root user read and write access to the avdb2.cmd file. Overview 91 Command-Line Interface The following output illustrates the information that a user can see when the --db2_inst_user and --inst-admin-password options are specified in the avdb2.cmd file: # ps -eaf|grep avdb2 root 22255 15301 10 10:49 pts/3 00:00:00 ./avdb2 --sysdir=/usr/local/avamar/etc --operation=backup --id=guest@/clients/db2-client.example.com --password=guest123 --server=aiqferrari.bgl.avamar.emc --acnt=/clients/db2-client.example.com db2inst1/AVAMAR1 The user name and password visibility problem does not apply to the Windows operating system. Command reference The avdb2 command enables you to browse DB2 data to back up or restore, back up DB2 data, and restore DB2 data. Synopsis avdb2 --operation={browse | backup | restore} [--account=LOCATION | --acnt=LOCATION | --path=LOCATION] [--buffersize=N] [--db2_inst_user=USERNAME | --inst-admin-user=NAME] [--dbname=NAME][--dbpartitionnums=NUM] [--ddr] [--ddr-index=N] [--exclude-pluginid-list=LIST |--excludepluginids=LIST] [--expires={DAYS | TIMESTAMP}] [--help | --help --operation={browse | backup | restore}] [--id=USER@DOMAIN/HOMEACNT] [--informationals] [--inst_admin_password=PASSWORD | --inst-admin-password=PASSWORD] [--label=NAME] [--labelnum=NUM] [--logfile=FILE | --log=FILE] [--logpath=PATH] [--noinformationals] [--nologs] [--nostdout] [--nowarnings] [--online] [--password=PASSWORD | --ap=PASSWORD | --pswd=PASSWORD][--pluginid-list=LIST | --pluginids=LIST] [--quiet] [--recover | --restore-and-recover] [--recovertype=TYPE] [--renamed_tablespace_list=NAME | --renamed-tablespace-list] [--restore | --restore-only] [--restorelogs] [--retention-type=TYPE | --retentiontype=TYPE] [--server=AVAMARSERVER | --hfsaddr=AVAMARSERVER] [--socket-buffersize=N] [--target=PATH | --db-dir=PATH] [--timestamp=DATE-TIME |--date-and-time=DATE-TIME] [--version] The command line help for the --ddr, --ddr_index, and --flagfile options is not available in this release of Avamar. 92 EMC Avamar 6.1 for IBM DB2 User Guide Command-Line Interface Operations The following table lists the operations that you specify by using the --operation option with the avdb2 command. Table 8 Operations for the avdb2 command Command Description browse Lists database files available for backup or restore. backup Performs an on-demand backup of the specified database files. restore Restores the specified database files. Options The following topics list the options available for avdb2. The avdb2 command does not support the --verbose option. Common options The following table lists common options for avdb2. Table 9 Common options for the avdb2 command Option Description --db2_inst_user=USERNAME | --inst-admin-user Specifies the instance owner’s user name. --exclude-pluginid-list=LIST | --excludepluginids Constrains operation to exclude backups originally taken with one or more plug-in types, where LIST is a comma-separated list of one or more integer plug-in IDs. --flagfile=FILE Specifies the full path and file name of the options file. The options file for DB2 is named avdb2.cmd. It contains a list of options and values that the avdb2 command uses to perform the given operation. The avdb2.cmd file is located in the /usr/local/avamar/var directory on AIX or LInux and in the C:\Program Files\avs\var directory on Windows. --help Displays help content for all operations and options. --help --operation={browse | backup | restore} Displays help content for a specific operation. --inst_admin_password=PASSWORD | --inst-admin-password Specifies the instance owner’s password. --pluginid-list=STRING | --pluginids Constrains operation to include backups originally taken with one or more plug-in types, where LIST is a comma-separated list of one or more integer plug-in IDs. --version Displays the build version. Command reference 93 Command-Line Interface Account options The following table lists account options for avdb2. Table 10 Account options for the avdb2 command Option Description --account=LOCATION | --path | --acnt Specifies a hierarchical location on the Avamar server. This option is relative to the current home location, unless a slash (/) is used as a prefix to the path designation, in which case an absolute path is assumed. --id=USER@DOMAIN/HOMEACNT Specifies the client user name to use for authentication where: • USER is the user name of the registered client. • DOMAIN is the Avamar domain. • HOMEACNT is the hostname of the Avamar for IBM DB2 client. --password=PASSWORD | --ap | --pswd Specifies the authentication password for --id=USER@DOMAIN/HOMEACNT. --server=AVAMARSERVER | --hfsaddr Specifies the Avamar server IP address or fully qualified hostname (as defined in DNS). Logging options The following table lists logging options for avdb2. Table 11 Logging command options for the avdb2 command Option Description --informationals Sets information level for status messages. --log=FILES | --log Specifies the log file pathname. --noinformationals Disables all status messages. --nostdout Disables output to standard output (stdout). --nowarnings Disables warning messages. --quiet Disables both warnings and status messages. Browse options The following table lists browse options for avdb2. Table 12 Browse command options for the avdb2 command 94 Option Description --labelnum=NAME Backup label number, which is required for restore and granular browse operations. EMC Avamar 6.1 for IBM DB2 User Guide Command-Line Interface Backup options The following table lists backup options for avdb2. Table 13 Backup options for the avdb2 command Option Description --ddr Instructs the backup to store data on a Data Domain system. --ddr-index=N Specifies the index number for the Data Domain system. The Avamar server assigns an index number to the Data Domain system when the Data Domain system is added to the configuration. --expires={DAYS | TIMESTAMP} Specifies the backup expiration as a number of days from the day of the backup (NUM-DAYS) or an absolute timestamp (TIMESTAMP). Use a 24-hour local timezone value for the TIMESTAMP. The timestamp format must use the following syntax: YYYY-MM-DD HH:MM:SS You can specify partial date strings. For example, 2012-02 is equivalent to 2012-02-01 00:00:00. --label=NAME Specifies a name for the backup. --retention-type=TYPE | --retentiontype=TYPE Assigns one of the following retention policy to the backup: • none • daily • weekly • monthly • yearly --buffersize=N Specifies the DB2 buffer size in kilobytes to use during backup operations. Default is 64. Other valid values are 128, 256, and 512 [64]. --dbpartitionnums=NUM Specifies the database partition numbers of partitions for the backup: • To specify all database partitions, type ALL or all. • To specify a list of partitions, for example partitions 1, 2 and 3, type 1,2,3. --nologs Excludes log files from an online backup --online Performs an online backup. --socket-buffersize=N Specifies the socket buffer size in kilobytes to use during backup. Valid values are 256, 512, and 1024. Command reference 95 Command-Line Interface Restore options The following table lists restore options for avdb2. Table 14 Restore options for avdb2 command Option Description --dbname=NAME Specifies the name of the target database for a directed restore operation. --labelnum=NUM Specifies the label number for a backup. Restore and granular browse operations require the labelnum option. --logpath=NAME Specifies a directory path for the restored log files. --recover | --restore-and-recover Enables Point-In-Time recovery. --recovertype=N Specifies the type of recovery where N is one of the following: • 0 (default) • 1 — End of log • 2 — Point-in-Time • 3 — End of backup --renamed_tablespace_list=NAME | --renamed-tablespace-list Specifies a comma-separated list of renamed table spaces for a granular restore of renamed table spaces. --restore | --restore-only Restores the database only. Notice: A recovery of the restored database is not performed. --restorelogs Restores log files only. Notice: Database files are not restored. 96 --target=PATH | --db-dir Specifies the target path for a redirected restore. DB2 creates a directory structure at this location and restores the database to it. --timestamp=DATE-TIME | --date-and-time Recovers the database by performing a rollforward operation to a specific point in time, where DATE-TIME specifies a date and time in the yyyy-mm-dd hh:mm:ss format. The time must be in the timezone of the client system. You can truncate the time entry. For example, you can omit minutes and seconds. EMC Avamar 6.1 for IBM DB2 User Guide Command-Line Interface CLI example commands The following examples show how to use the avdb2 command to browse the data on a client, to back up data to the Avamar server or Data Domain system, and to restore data back to the client. Example browse commands The following commands returns a list of all local data available on the client for backup: ./avdb2 --operation=browse (local) ./avdb2 --sysdir=/usr/local/avamar/etc --operation=browse db2inst1 The following command returns granular browse information for an instance on a Windows system: ./avdb2 --operation=browse /DB2 id=guest@/clients/db2-client.example.com --password=PASSWORD --labelnum=18 DB2/c-AVAMAR1 To perform a granular browse operation to view backups stored on a Data Domain system, use the --acnt or --path option. ◆ The following command uses the --acnt option: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=browse --id=guest@/clients/db2-client.example.com --password=PASSWORD --labelnum=2039 db2inst1/hl-AVAMAR1 --acnt=/db2/datadomain ◆ The following command uses the --path option: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=browse --id=guest@/clients/db2-client.example.com --path=/db2/datadomain --password=PASSWORD --labelnum=2039 db2inst1/hl-AVAMAR1 Example backup commands The following commands provide examples for backing up a database to the Avamar server: ./avdb2 --sysdir=/usr/local/avamar/etc -c --operation=backup --id=guest@/clients/db2-client.example.com --password=PASSWORD --db2-inst-user=db2inst1 --inst-admin-password=PASSWORD --server=avamar-1.example.com --path=/clients/db2-client db2inst1/AVAMAR1 ./avdb2 --operation=backup --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD db2inst1/AVAMAR1 The following command backs up a database to a Data Domain system: ./avdb2 --sysdir=/usr/local/avamar/etc -c --operation=backup --id=quest@/clients/db2-client.example.com --password=PASSWORD --db2-inst-user=db2inst1 --inst-admin-password=PASSWORD --server=avamar-1.example.com --path=/clients/db2-client db2inst1/AVAMAR1 --ddr=true --ddr_index=INDEX-NUM CLI example commands 97 Command-Line Interface Example restore commands The following commands provide examples for restoring a database: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --db2-inst-user=db2inst1 --inst-admin-password=PASSWORD --server=avamar-1.example.com --path=/clients/db2-client --labelnum=18 db2inst1/c-AVAMAR1 --restore ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD --restore-only --labelnum=16 db2inst1/c-AVAMAR1 The --acnt option is optional. The following command restores a database, and then recovers it to the end of logs: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.comavamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD --recover --recovertype=1 --logpath=/home/db2inst1/logs --labelnum=24 db2inst1/hl-AVAMAR1 The following command restores only the database from a hot backup: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD --restore-only --labelnum=21 db2inst1/hl-AVAMAR1 The following command restores only the archive logs from a hot backup: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD --restorelogs --logpath=/home/db2inst1/logs --labelnum=19 db2inst1/hl-AVAMAR1 The following command performs a redirected restore: ./avdb2 --sysdir=/usr/local/avamar/etc --operation=restore --id=guest@/clients/db2-client.example.com --password=PASSWORD --server=avamar-1.example.com --acnt=/clients/db2-client.example.com --db2_inst_user=db2inst1 --inst_admin_password=PASSWORD --restore-only --labelnum=16 --target=/home/db2inst1 --dbname=AVAMAR11 db2inst1/c-AVAMAR1 98 EMC Avamar 6.1 for IBM DB2 User Guide APPENDIX C Troubleshooting This appendix provides information on how to resolve backup and restore problems. Topics in this appendix include: ◆ ◆ ◆ ◆ ◆ ◆ How to specify options.......................................................................................... Backup or restore fails with a “Failed to create backup of db” error........................ Backup fails with socket timeout errors ................................................................. Granular browse fails to display table spaces ........................................................ Restore fails with a “Failed to initiate the restore operation” error ......................... Unable to connect to database during backup....................................................... Troubleshooting 100 102 103 103 105 105 99 Troubleshooting How to specify options To resolve certain backup or restore problems may require the use of special options that you must type in the Enter Attribute and Enter Attribute Value fields. These fields are available by clicking the More button in the Backup Command Line Options or the Restore Command Line Options dialog box. The following procedure explains how to specify options from either dialog box. The procedure uses the Backup Command Line Options dialog box, however, the same steps apply to the Restore Command Line Options dialog box. The Avamar software does not validate the text you type in the Enter Attribute and Enter Attribute Value fields. Ensure that you enter the options and values correctly. To specify options: 1. From the Backup Command Line Options or the Restore Command Line Options dialog box, click the More button. The dialog box expands to display the Enter Attribute and Enter Attribute Value fields. 2. Type the option name in the Enter Attribute field and the value for the option in the Enter Attribute Value field. The following figure shows the dialog box after you type values in the Enter Attribute and Enter Attribute Value fields. 3. Click . The option and value appear in the area below the Enter Attribute and Enter Attribute Value fields. 4. To add more options for the backup or restore operation, repeat steps 2 and 3. 100 EMC Avamar 6.1 for IBM DB2 User Guide Troubleshooting The following figure shows the dialog box after adding two options. Additional information for on-demand backup and restore operations is available in Chapter 3, “Backup,” and Chapter 4, “Restore and Recovery.” How to specify options 101 Troubleshooting Backup or restore fails with a “Failed to create backup of db” error A backup or restore operation fails with an error message similar to the following: snapup: Failed to create backup of db /. db2 errcode -2025 This error message sometimes indicates that the avtar process timed out during the DB2 backup or restore initialization process. A restore of a dropped database, for example, may fail intermittently because the avtar process timed out. To resolve this problem, increase the avdb2-stream-timeoutsecs option from the 30 seconds (default setting) to 60 seconds or more. Specifying the avdb2-stream-timeoutsecs option To set the avdb2-stream-timeoutsecs option for a backup or restore: 1. Set up the backup or restore by using the correct procedure and steps in Chapter 3, “Backup,” or Chapter 4, “Restore and Recovery.” 2. Set the --[avdb2]avdb2-stream-timeoutsecs option and value for the backup as described in “How to specify options” on page 100. 3. In the Enter Attribute field, type --[avdb2]avdb2-stream-timeoutsecs. 4. In the Enter Attribute Value field, type 60 or more seconds. The following figure shows the Backup Command Line Options dialog box after adding the --[avdb2]avdb2-stream-timeoutsecs option and a value of 120 seconds. 102 EMC Avamar 6.1 for IBM DB2 User Guide Troubleshooting 5. Complete the remaining backup or restore steps as described in Chapter 3, “Backup,” or Chapter 4, “Restore and Recovery.” Backup fails with socket timeout errors If a backup fails with a socket timeout error, set the value for the --[avdb2]avdb2-stream-timeoutsecs option as described in “Specifying the avdb2-stream-timeoutsecs option” on page 102. Granular browse fails to display table spaces In an active/active DPF environment, the Browse for Granular Restore option fails to display table spaces from an offline backup and returns an error message similar to the following: The backups are taken prior to enabling the database for recovery This problem occurs even when you have enabled the database for recovery. To resolve this problem, specify the --[avdb2]avdb2-stream-delayclosesecs option with the offline backup. After the backup completes, verify that the Browse for Granular Restore option displays table spaces for the selected backup. For example, to set the --[avdb2]avdb2-stream-delayclosesecs option: 1. Complete the correct backup procedure in Chapter 3, “Backup” up to the step where you set options in the Backup Command Line Options dialog box. 2. In the Backup Command Line Options dialog box, set the --[avdb2]avdb2-stream-delayclosesecs option and value for the backup as described in “How to specify options” on page 100. 3. In the Enter Attribute field, type --[avdb2]avdb2-stream-delayclosesecs. 4. In the Enter Attribute Value field, type a value from 5 to 15. The value represents milliseconds. The default is 2 milliseconds. Backup fails with socket timeout errors 103 Troubleshooting The following figure shows the Backup Command Line Options dialog box after adding the --[avdb2]avdb2-stream-delayclosesecs option and a value of 5. 5. Complete the remaining backup steps. Chapter 3, “Backup,” provides more information. 6. After the backup successfully completes, verify that the Browse for Granular Restore option correctly displays table spaces for the backup: a. From the Backup and Restore window, click the Select for Restore tab. b. Select the date of the backup from the calendar. c. Select the offline backup you created in steps1–5 from the list of backups. d. Click (the Browse for Granular Restore button). The Destination Client Selection dialog box appears. e. Leave Restore everything to its original location selected and click OK. f. Expand the folders in the directory tree to view table spaces available for restore. 104 EMC Avamar 6.1 for IBM DB2 User Guide Troubleshooting Avamar Administrator shows the SYSCATSPACE and USERSPACE1 table spaces in the following sample figure. This ability to view table spaces confirms that the Browse for Granular Restore option is working as designed. Restore fails with a “Failed to initiate the restore operation” error A restore operation fails and writes the following error to the log file: Failed to initiate the restore operation To resolve this problem: 1. Set the --[avdb2]subprocesstimeoutsecs option and value for the restore operation as described in “How to specify options” on page 100. 2. In the Enter Attribute field, type --[avdb2]subprocesstimeoutsecs. 3. In the Enter Attribute Value field, type a value from 40 to 60. The default value is 30 seconds. 4. Retry the restore operation. Unable to connect to database during backup A backup fails with an error message similar to the following when the OS locale is set to Chinese: 2013-09-14 00:15:19 avdb2 Warning <12740>: Unable to connect to database [DBYMZ] due to sql connection failure, error : [-1]. Restore fails with a “Failed to initiate the restore operation” error 105 Troubleshooting 2013-09-14 00:15:19 avdb2 Warning <15301>: DB2 returned message [ [IBM][CLI Driver] SQL0332N Character conversion from the source code page "1392" to the target code page "UNKNOWN" is not supported. SQLSTATE=57017], SQLCODE [-332] This error occurs for backups performed by using Avamar Administrator or the avdb2 command from command-line interface. The Avamar Plug-in for DB2 does not support I18N. Only ASCII environments are supported. 106 EMC Avamar 6.1 for IBM DB2 User Guide GLOSSARY This glossary provides definitions for terms used in this guide. A activation administrator archive logs See “client activation.” The person who normally installs, configures, and maintains software on network computers, and who adds users and defines user privileges. Files that are used by DB2 for roll forward recovery. Avamar Administrator A graphical management console software application, which remotely administers an Avamar system from a supported Windows or client computer. Avamar client A computer or workstation that runs Avamar software and accesses the Avamar server over a network connection. Avamar client software comprises a client agent and one or more plug-ins. Avamar server The server component of the Avamar client/server system. An Avamar server is a fault-tolerant, high-availability system that efficiently stores the backups from all protected clients. It also provides essential processes and services required for data restores, client access, and remote system administration. An Avamar server runs as a distributed application across multiple networked storage nodes. B backup A point-in-time copy of client data that can be restored as individual files, selected directories, or as entire file systems. Although more efficient than a conventional incremental backup, a backup is always a full copy of client data that can be restored immediately from an Avamar server. C client activation client agent client registration cold backup The process of passing the client ID (CID) back to the client, where it is stored in an encrypted file on the client file system. A platform-specific software process that runs on the client and communicates with the “Management Console Server (MCS)” and with any plug-ins installed on that client. The process of establishing an identity with the Avamar server. When Avamar recognizes the client, it assigns a unique client ID (CID), which it passes back to the client during activation. A backup performed while the database is offline. EMC Avamar 6.1 for IBM DB2 User Guide 107 Glossary D Data Domain system Data Partition feature database database partition dataset DB2 instance Disk-based deduplication appliances and gateways that provide data protection and disaster recovery (DR) in the enterprise environment. A feature that enables the distribution of a DB2 UDB database across multiple servers in a cluster or multiple nodes on massively parallel processors (MPP). A DB2 database can be distributed in several database partitions. A collection of data arranged for ease and speed of update, search, and retrieval by computer software. An independent part of a partitioned database with its own data, configuration files, indexes, and transaction logs. A policy that defines a set of files, directories, and file systems to include or exclude from a backup. A dataset is a persistent and reusable Avamar policy that can be named and attached to multiple groups. An independent environment where database objects can be created and applications can be run against them. DD Boost The API that Avamar clients use to access a Data Domain system. The DD Boost API is installed automatically on the client computer when you install the Avamar client. It is also installed automatically on the Avamar server when you install Avamar. disaster recovery Recovery from any disruptive situation, such as hardware failure or software corruption, in which ordinary data recovery procedures are not sufficient to restore a system and its data to normal day-to-day operations. DNS domain Domain Name Server. A dynamic and distributed directory service for assigning domain names to specific IP addresses. A feature in Avamar Administrator that organizes large numbers of clients into named areas of control and management. F file system A software interface used to save, retrieve, and manage files on storage media by providing directory structures, data transfer methods, and file association. G granular recovery 108 An Avamar feature that enables you to restore a part of a backup rather than the entire backup. The Avamar Plug-in for DB2 enables you to restore table spaces from a backup. group A level of organization in Avamar Administrator for one or more Avamar clients. All clients in an Avamar group use the same group policies, which include the dataset, backup schedule, and retention policy. group policy The dataset, schedule, and backup retention policy attached to a group that is used by all clients in a group, unless these policy settings are overridden by an administrator at the client level. EMC Avamar 6.1 for IBM DB2 User Guide Glossary H hot backup A backup that is performed while users are online and have access to the data that is being backed up. L LAN Local Area Network. M Management Console Server (MCS) metadata The MCS provides centralized administration (scheduling, monitoring, and management) for the Avamar server. The MCS also runs the server-side processes used by the Avamar Administrator graphical management console. Hash information that identifies stored sub-file information for deduplication, and is required to revert deduplicated client backup data to the regular non-deduplicated format. P plug-in policy An Avamar plug-in is a software process that recognizes a particular kind of data on that client. A set of rules for client backups that can be named and applied to multiple groups. Groups have dataset, schedule, and retention policies. R recover redirected restore registration restore retention roll forward To restore data from a backup to a client disk and apply transaction logs to the data to make it consistent with a given point in time. The process of restoring backed up data to a location other than to its original location. See “client registration.” A file or object restore. An operation that retrieves one or more file systems, directories, files, or data objects from a backup and writes the data to a designated location. The ability to control the length of time that backups are kept in an Avamar server before automated deletion. Retention can be set to permanent for backups that should not be deleted from an Avamar server. Retention is a persistent and reusable Avamar policy that can be named and attached to multiple groups. The process of updating a database or table space by applying changes recorded in database log files. A roll forward is performed after you restore a database backup. S schedule The ability to control the frequency and the start and end time each day for backups of clients in a group. A schedule is a persistent and reusable Avamar policy that can be named and attached to multiple groups. EMC Avamar 6.1 for IBM DB2 User Guide 109 Glossary T table space transaction logs 110 Containers within a database that store specific data. DB2 includes five table spaces, which are named according to their usage: catalog, regular, large, system temporary, and user temporary. IBM DB2 documentation provides more information. A set of files that provides a history of updates made to a database. You can use transaction logs to roll back a database to a previous state. EMC Avamar 6.1 for IBM DB2 User Guide INDEX A account options 94 archive logging 16, 44 archive logs backing up 18 restoring 61 Avamar Administrator 14 Avamar file system clients 16 Avamar Plug-in for DB2 configuration 14, 15 software packages 22 system requirements 22 Avamar server 23, 24, 29, 39, 59 avdb2 binary 16 examples 97 executable 16 operations 90, 93 options 90, 93 to 96 avregister command AIX 29 Linux 39 B backing up archive logs 16, 18 DB2 partitions 17 partitions 17 backing up to Data Domain 47, 51, 87, 95 Backup agent service, configuring 44 backup errors 17, 103 backup file name prefix 18, 58 backup types offline 18 online 18 partition 18 backups CLI options 95 DB2 partitions 16 debugging 88 offline 16, 18, 44 on-demand 16, 45 online 16, 18, 44 plug-in options 86 scheduled 16, 48 without archive logs 64 C catalog node. See catalog partition catalog partition 16, 20 client registration 24 Command Line Interface (CLI) avdb2 command 90 to 98 described 14, 90 examples 97 creating dataset 48 group 51 D Data Domain system 15, 47, 51, 87, 90, 95, 97 Data Domain system index number 95 database names 18, 58 database preparation 44 database recover options 18 dateset, creating 48 DB2 application, recovering 82 database partition backups 16, 44 instance 16 rollforward command 19, 20, 64, 65, 69 server, recovering 82 DB2 Universal Database 16 debugging option 87, 88 disaster recovery 82 DNS entries 23 downloading Avamar software for IBM AIX 27 Avamar software for Linux 38 Avamar software for Windows 34 dropped database 102 E EMC online support website 7 encryption technology 59 end of backup recovery 63, 81 end of logs recovery 62, 81 errors backing up 17, 103 failed to create backup of database 17 multi-partition backup 17 restoring 102 restoring a dropped database 102 excluding archive logs 16 G granular recovery 19, 20, 73 group, creating 51 I installation packages 22 installing Avamar Client for AIX 28 Avamar Client for Lunix 38 Avamar Client for Windows 34 EMC Avamar 6.1 for IBM DB2 User Guide 111 Index Avamar Plug-in for DB2 on AIX 30 Avamar Plug-in for DB2 on Linux 39 Avamar Plug-in for DB2 on Windows 36 L LOGARCHMETH1 setting 19, 73 logging options 94 M Microsoft Windows User Account Control (UAC) 34 N network hostname 23 non-catalog nodes. See non-catalog partitions non-catalog partitions 16, 17, 20, 70 O offline backups 16, 18, 44 offline database name 58 on-demand backup options 86 on-demand backups 16, 45 online backups 16, 18, 44 S scheduled backups 16, 48, 55 supported platforms 22 T table space size 75 table spaces 16 TEMPSPACE1 table space 16 U P packages 22 plug-in options debugging 87, 88 restores 87 setting 86 point-in-time recovery 62, 81 preinstallation requirements 23 R recovering database 61 DB2 application 82 DB2 server 82 retired clients 78 recovery types end of backup 18, 63, 81 end of logs 18, 62, 81 granular 19, 73 point-in-time 18, 62, 81 redirected restores 19, 66 registering Avamar Client for AIX 29 Avamar Client for Linux 39 Avamar Client for Windows 36 registration, Avamar client 24 requirements installation packages 22 platforms 22 restore CLI options 96 errors 102 plug-in options 87 types 19 112 restoring archive logs only 65 database only 64 database partitions 20 DB2 database partitions 70 offline backup 17, 58 online backup 65 online backup with archive logs 61 table spaces 19, 73 retention policy 46 retired clients, recovering 78 roll forward database options 18, 61 rollforward command 19, 20, 64, 65, 69 EMC Avamar 6.1 for IBM DB2 User Guide uninstalling Avamar Plug-in for DB2 on IBM AIX 32 Avamar Plug-in for DB2 on Linux 41 Avamar software on Windows 37 upgrading Avamar software on IBM AIX 34 Avamar software on Linux 41 Avamar software on Windows 37 User Account Control (UAC) 34 USERSPACE1 table space 16

Emc® Avamar® 6.1 For Ibm Db2 User Guide

Rating

Date

Size

Views

Categories

Share

Transcript

Forgot your password?.