emc avamar 6.0 for ibm db2 guide · pdf fileguide p/n 300-011-636 rev a01 emc corporation...

GUIDEP/N 300-011-636

REV A01

EMC CORPORATION

CORPORATE HEADQUARTERS:HOPKINTON, MA 01748-9103

1-508-435-1000WWW.EMC.COM

EMC® AVAMAR® 6.0FOR IBM DB2

EMC AVAMAR 6.0 FOR IBM DB2 GUIDE 2

Copyright and Trademark Notices

Copyright © 2002 - 2011 EMC Corporation. All rights reserved.

Published April, 2011

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.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

TABLE OF CONTENTS

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Scope and intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Avamar Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Safety admonitions and notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Capabilities and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Preinstallation checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Client registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing the Avamar for DB2 Client on IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Download Avamar AIX DB2 install packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Install and register the Avamar for AIX Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Install and configure the Avamar DB2 plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Uninstalling the Avamar for DB2 Client on IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Upgrading the Avamar for DB2 Client on IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing the Avamar for DB2 Client on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . 23

Install the Avamar for Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Register the Avamar for Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Install the Avamar Windows DB2 plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Uninstalling and upgrading the Avamar for DB2 Client on Microsoft Windows. . . . . . . . 27Installing the Avamar for DB2 Client on Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . 28

Download Avamar Linux DB2 install packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Install and register the Avamar for Linux Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Install and Configure the Avamar DB2 Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Uninstalling and upgrading the Avamar for DB2 Client on Red Hat Enterprise Linux. . . 31Upgrading the Avamar for DB2 Client on Red Hat Enterprise Linux. . . . . . . . . . . . . . . . 31


TABLE OF CONTENTS

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Database preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32On-demand backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Scheduling DB2 server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Creating a dataset for DB2 server backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Setting up scheduled DB2 server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Enabling scheduled DB2 server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Restore and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Database preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Restore overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Locating and selecting a backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Restoring from an offline backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Restoring from an online backup with archive logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Restoring and recovering the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Restoring only the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Restoring only the archive logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Restoring from an online backup without archive logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Appendix A — Plug-in Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Important terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62DB2 plug-in options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


PREFACE

Scope and intended audience

Scope. This guide describes how to install, configure, administer, and use the Avamar for DB2 Client.

Intended audience. The information in this guide is primarily intended for:

• System administrators who are responsible for installing software and maintaining servers and clients on a network

• Database administrators (DBAs) who are responsible for backing up and maintaining DB2 databases

Prerequisites. Persons using this guide should have current practical experience with the following:

• Operating system shell commands (root permission required)• The specific version of DB2 software currently deployed at the site

Product informationFor current documentation, release notes, software updates, information about EMC products, licensing, and service, go to the EMC Powerlink website at http://Powerlink.EMC.com.


Your commentsPREFACE

Avamar SupportBefore contacting EMC Technical Support, please go to the Avamar Support landing page at https://support.EMC.com/products/Avamar and:

• Refer to the Product Documentation • Check the listed Support Topics for:

• How-to's • Troubleshooting

• Search the Avamar Knowledge Base (KB) for applicable solutions using the convenient search engine:

• Enter the KB solution number (for example, esgxxxxxx) • Enter keywords

If none of the previous resources resolve your issue, many issues can be successfully resolved through live interactive chat. You can engage EMC Technical Support using live interactive chat by selecting Additional Resources > Live Chat on the Avamar Support landing page.

If more in-depth help is required, or if you have an existing open Service Request (SR), you can submit or review a service request through Powerlink:

• To review an existing SR, go to http://Powerlink.EMC.com and select Support > Request Support > View Service Requests

• To open a new SR, go to: http://Powerlink.EMC.com and select Support > Request Support > Create Service Request

EMC recommends that all Avamar systems have ConnectEMC and Email Home enabled to facilitate the best possible support. Systems with ConnectEMC configured and enabled will be able to automatically generate SRs when appropriate and as noted in this guide.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of our documentation. You may email comments to:

[email protected]

Please include the following information:

• Product name and version• Document name, part number, and revision (for example, A01)• Page numbers• Other details that will help us address the documentation issue


Typographic conventionsPREFACE

Typographic conventionsThe following table provides examples of standard typographic styles used in this guide to convey various kinds of information.

EXAMPLE DESCRIPTION

Click OK. orSelect File > Close.

Bold text denotes actual buttons, commands, menus, and options that initiate action.Sequential commands are separated by a greater-than (>) character. For example, the second example instructs you to select the Close command from the File menu.

Type: cd /tmp

Bold fixed-width text denotes shell commands that must be entered exactly as they appear.

--logfile=FILE All caps text often denotes a placeholder (token) for an actual value that must be supplied by the user. In this example, FILE would be an actual filename.

Installation Complete. Regular (not bold) fixed-width text denotes command shell messages, code, and file contents.


Safety admonitions and noticesPREFACE

Safety admonitions and noticesThe following safety admonitions and notices appear in this guide:

Danger safety admonitions indicate a hazardous situationwhich, if not avoided, will result in death or serious injury.

Warning safety admonitions indicate a hazardous situation which, if not avoided, could result in death or serious injury.

Caution safety admonitions indicate a hazardous situationwhich, if not avoided, could result in minor or moderateinjury.

IMPORTANT: Important notices contain information essential to software or hardware operation.

NOTE: Notes contain information intended to clarify a topic or procedure. Notes never contain information that will cause a failure if ignored.

TIP: Tips present optional information intended to improve your productivity or otherwise enhance your experience with the product. Tips never contain information that will cause a failure if ignored.


INTRODUCTION

EMC® Avamar® for DB2 provides a complete backup and restore solution for DB2 databases. Once a database has been backed up to the Avamar system, the entire database can be quickly restored without having to locate and mount tapes or optical media.

System requirementsThis topic lists the supported configurations and hardware requirements that must be satisfied to successfully install and deploy the Avamar for DB2 Client backup and recovery solution. The Supported Configurations table also lists the correct Avamar for DB2 Client software installation package required for each DB2 version, host platform, and operating system.

Software

Before installation, review the EMC Avamar Compatibility and Interoperability

Matrix on Powerlink® (http://Powerlink.EMC.com) to ensure that Avamar software is compatible with the operating system and DB2 software.

Hardware

REQUIREMENT MINIMUM

RAM 64 MB.

Hard Drive Space 130 MB permanent hard drive space for software installation.The Avamar client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files.

Network Interface 10BaseT minimum; 100BaseT or higher recommended, configured with latest drivers for the platform.


http://Powerlink.EMC.com

http://Powerlink.EMC.com

Capabilities and limitationsINTRODUCTION

Capabilities and limitationsThis topic discusses current capabilities and limitations of the Avamar for DB2 Client.

Avamar for DB2 Client only supports one database instance per server. Avamar only supports backup of a single instance of DB2 on each

server. Attempting to back up multiple instances on the same server (regardless of version) fails.

Redirected restores must be to the same client. When performing a redirected restore, the restore target directory must be on the same client from which the backup was originally taken. Restores to other clients are not supported.


INSTALLATION AND CONFIGURATION

This chapter describes how to install and configure Avamar for DB2 Client software on the server that hosts the DB2 database. Five basic server platforms are supported:

• IBM AIX 5.2, 5.3 and 6.1 64-bit• Microsoft Windows 2003, 2008 R1, and 2008 R2 x64• Microsoft Windows Server 2003 32-bit• Red Hat Enterprise Linux 4 32-bit• Red Hat Enterprise Linux 4 and 5 64-bit• SuSE Linux 10 and 11 32-bit• SuSE Linux 10 and 11 64-bit

The Preinstallation checks (page 12) and Client registration (page 13) tasks apply to all server platforms. However, there are separate client installation procedures for each platform.

Software installation packages. The following table lists the software packages required to install Avamar for DB2 Client software. Each installation requires two software packages: the filesystem client and the DB2 plug-in.

OPERATING SYSTEM SOFTWARE INSTALLATION PACKAGES

IBM AIX 5.2 and 5.3 64-bit

• AvamarClient-aix5-ppc-VERSION.bff• AvamarDB2-aix5-ppc64-VERSION.bff

IBM AIX 6.1 64-bit • AvamarClient-aix6-ppc-VERSION.bff• AvamarDB2-aix6-ppc64-VERSION.bff

Microsoft Windows Server 2003 32-bit

• AvamarClient-windows-x86-VERSION.msi• AvamarDB2-windows-x86-VERSION.msi

Microsoft Windows 2003, 2008 R1 and 2008 R2 x64

• AvamarClient-windows-x86_64-VERSION.msi• AvamarDB2-windows-x86_64-VERSION.msi

Red Hat Enterprise Linux 4 32-bit

• AvamarClient-linux-rhel4-x86-VERSION.rpm• AvamarDB2-linux-rhel4-x86-VERSION.rpm


Preinstallation checksINSTALLATION AND CONFIGURATION

Preinstallation checksBefore you install any Avamar software, perform the following checks:

1. Ensure that you have operating system root privileges on the computer that hosts the DB2 server.

2. Ensure that DB2 is installed and functioning properly.

3. Ensure that the Avamar server is operational and present on the same network as the DB2 server.

You can verify this by opening a command shell on the DB2 server and typing the following:

ping AVAMARSERVER

where AVAMARSERVER is the network hostname (as defined in DNS) or IP address of the Avamar server.

4. Note the network hostname for the Avamar server and utility node. These DNS entries should have been added during deployment of the Avamar system.

Red Hat Enterprise Linux 4 and 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

SUSE Linux Enterprise Server 11 32-bit

• AvamarClient-linux-sles11-x86-VERSION.rpm• AvamarDB2-linux-sles11-x86-VERSION.rpm

SUSE Linux Enterprise Server 10 and 11 64-bit

• AvamarClient-linux-rhel4-x86_64-VERSION.rpm• AvamarDB2-linux-rhel4-x86_64-VERSION.rpm

OPERATING SYSTEM SOFTWARE INSTALLATION PACKAGES


Client registrationINSTALLATION AND CONFIGURATION

Client registrationYou must register the client to establish the client 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.

TIP: You can add this client to an existing Avamar domain, or you may also want to consider adding a domain to the Avamar system to segregate clients that perform DB2 backups from clients that back up physical filesystems. The EMC Avamar Administration Guide provides additional information.

4. Select Actions > Account Management > New Client.

The New Client dialog box appears.



5. Type the information for the client as discussed in the following table.

6. Click OK.

The New Client dialog box closes, and the new client appears in the Account Management tree pane.

7. Switch to the Administration window.

8. Click the Account Management tab.

9. Select the client that you added.

10.Select Actions > Account Management > New User(s) to create a user account for the client.

The New User dialog box appears.

11. Type the information for the user as discussed in the following table.

FIELD DESCRIPTION

New client name Name for the new client.IMPORTANT: To ensure error-free client registration, the Avamar client name must be the actual DB2 server network hostname as defined in DNS.

Contact Optional contact name.

Phone Optional contact telephone number.

Email Optional contact email address.

Location Optional contact location.

FIELD/OPTION DESCRIPTION

Authentication System

Select either the default internal Avamar Authentication System, or any external authentication system that you have configured to work with Avamar.

Everyone Select this option to designate privileges for all users on this client.



12.Click OK.

The following status message appears: User added.

13.Click OK.

The status message closes and the new user appears in the list of users for the client.

User Name Select this option and type the new username.IMPORTANT: If you are using an external authentication system, this must be the username that you use to log in to that system.

Role Select the backup and restore privilege for this user.

Password Type a password for the new user. Avamar passwords must be at least six characters long.If you are using an external authentication system, leave the box blank.

Confirm Type the password again to confirm that you did not type it incorrectly in the Password box.If you are using an external authentication system, leave the box blank.



Installing the Avamar for DB2 Client on IBM AIXINSTALLATION AND CONFIGURATION

Installing the Avamar for DB2 Client on IBM AIX

Task list. To install the Avamar for DB2 Client on supported IBM AIX platforms:

• Download Avamar AIX DB2 install packages (page 16)• Install and register the Avamar for AIX Client (page 17)• Install and configure the Avamar DB2 plug-In (page 19)

Download Avamar AIX DB2 install packages

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 automatically redirected to the Avamar secure web server.

3. If a security alert dialog box appears due to browser security settings, click Yes or OK to allow redirection to the Avamar secure web server.

The Secure Log On page appears.

4. Scroll down until the Downloads and Documents hyperlink is visible.

5. Click Downloads and Documents.

The Downloads and Documentation page appears.

6. Click the correct operating system hyperlink for the computer that hosts the DB2 server.

A directory listing appears.

7. Download the Avamar for AIX Client install package to a temporary install directory on the system.

8. Note the Avamar for AIX Client install package filename.

9. Download the Avamar DB2 plug-in install package to the same directory as the Avamar for AIX Client install package.

10.Note the Avamar DB2 plug-in install package filename.



Install and register the Avamar for AIX Client

User=root 1. Open a command shell and log in to the computer that hosts the DB2 server 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 and AvamarClient-aix5-ppc-VERSION.bff is the Avamar for AIX Client install package that you downloaded.

The following appears in the command shell:

+----------------------------------------------------------------------------+Pre-installation Verification...

+----------------------------------------------------------------------------+Verifying selections...doneVerifying requisites...doneResults...SUCCESSES---------

Filesets listed in this section passed pre-installationverification and will be installed.

Selected Filesets-----------------

AVMRclnt 6.0.100.580 # Avamar for AIX Client 6.0.100-580...

<< 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.0.100-580

. . . . . << Copyright notice for AVMRclnt >> . . . . . . .

This software is copyright EMC 2001-2011.

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 completeYou 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.logavagent Info <5417>: daemonized as process id 17444avagent.d Info: Client Agent started.



Finished processing all filesets. (Total time: 9 secs).

+----------------------------------------------------------------------------+Summaries:

+----------------------------------------------------------------------------+

Installation Summary--------------------

Name Level Part Event Result-----------------------------------------------------------------------------AVMRclnt 6.0.100-580 USR APPLY SUCCESS

3. Register the client with the Avamar server by typing:

/usr/local/avamar/bin/avregister


=== Client Registration and ActivationThis 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.


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.


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 the domain to use when registering this client.

IMPORTANT: 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.logavagent.d Info: Client activated successfully.avagent.d Info: startavagent Info <5241>: Logging to ///usr/local/avamar//var/avagent.logavagent Info <5417>: daemonized as process id 17620avagent.d Info: Server started.Registration Complete.



Install and configure the Avamar DB2 plug-In

IMPORTANT: You must Install and register the Avamar for AIX Client (page 17) before installing the Avamar DB2 Plug-In.

User=root 1. Ensure that you are still logged in to the computer that hosts the DB2 server as root.

2. Install the Avamar DB2 plug-in software by typing:

cd /tmp

geninstall -d AvamarDB2-aix5-ppc64-VERSION.bff all

where /tmp is the temporary install directory and AvamarDB2-aix5-ppc64-VERSION.bff is the Avamar DB2 plug-in install package that you downloaded.


+----------------------------------------------------------------------------+Pre-installation Verification...

+----------------------------------------------------------------------------+Verifying selections...doneVerifying requisites...doneResults...

SUCCESSES---------

Filesets listed in this section passed pre-installation verificationand will be installed.

Selected Filesets-----------------AvamarDB2-aix5-ppc64 6.0.100.580 # EMC Avamar client 6.0.100-580


+----------------------------------------------------------------------------+BUILDDATE Verification ...

+----------------------------------------------------------------------------+Verifying build dates...doneFILESET 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.0.100-580

. . . . . << Copyright notice for AvamarDB2-aix5-ppc64 >> . . . . . . .

This software is copyright EMC Corporation, EMC 2001-2011.

Please read and agree to the End User License Agreement whichwill 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/avamartotal 40-rw-r--r-- 1 root system 13638 Aug 19 10:51 AvamarClient-License.txtdrwxr-xr-x 2 205 staff 4096 Aug 19 10:55 bindrwxr-xr-x 2 205 staff 256 Aug 19 10:55 etcdrwxr-xr-x 2 205 staff 256 Aug 19 11:41 libdrwxr-xr-x 2 205 staff 256 Aug 19 10:55 lib64lrwxrwxrwx 1 root system 11 Aug 19 11:40 var -> /var/avamaravagent.d Info: Stopping Avamar Client Agent (avagent)...avagent.d Info: Client Agent stopped.avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent Info <5417>: daemonized as process id 618624avagent.d Info: Client Agent started.Installation completeYou 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:

+----------------------------------------------------------------------------+


Name Level Part Event Result-----------------------------------------------------------------------------AvamarDB2-aix5-ppc64 6.0.100-580 USR APPLY SUCCESS

3. Configure the DB2 plug-in software by typing:

/usr/local/avamar/bin/avdb2setup


This script will configure the EMC Avamar DB2 plugin

Enter path to Avamar Client installation [/usr/local/avamar]:

4. 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.

5. 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 /data02/db2qa is the home directory for the database instance owner.

6. 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)...


Uninstalling the Avamar for DB2 Client on IBM AIXINSTALLATION AND CONFIGURATION

avagent.d Info: Client Agent stopped.avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent Info <5417>: daemonized as process id 479284avagent.d Info: Client Agent started.

Uninstalling the Avamar for DB2 Client on IBM AIXUser=root 1. Open a command shell and log in to the computer that hosts the DB2

server as root.

2. Uninstall the Avamar DB2 plug-in software by typing:

lslpp -l | grep Avamar

The following appears in the command shell:AvamarClient-aix5-ppc VERSION COMMITTED EMC Avamar client VERSIONAvamarDB2-aix5-ppc64 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...doneVerifying requisites...doneResults...

SUCCESSES---------

Filesets listed in this section passed pre-deinstall verificationand will be removed.

Selected Filesets-----------------AvamarDB2-aix5-ppc64 6.0.100.580 # EMC Avamar client 6.0.100-580...



1 Selected to be deinstalled, of which: 1 Passed pre-deinstall verification

----1 Total to be deinstalled

+----------------------------------------------------------------------------+Deinstalling Software...

+----------------------------------------------------------------------------+

installp: DEINSTALLING software for: AvamarDB2-aix5-ppc64 VERSION


+----------------------------------------------------------------------------+Summaries:

+----------------------------------------------------------------------------+



Uninstalling the Avamar for DB2 Client on IBM AIXINSTALLATION AND CONFIGURATION

Name Level Part Event Result-----------------------------------------------------------------------------AvamarDB2-aix5-ppc64 6.0.100-580 USR DEINSTALL SUCCESS

4. Uninstall the Avamar for AIX Client 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.doneVerifying requisites...doneResults...

SUCCESSES---------

Filesets listed in this section passed pre-deinstall verificationand will be removed.

Selected Filesets-----------------AvamarClient-aix5-ppc 6.0.100.580 # EMC Avamar client 6.0.100-580...



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


+----------------------------------------------------------------------------+Summaries:

+----------------------------------------------------------------------------+

Installation Summary--------------------Name Level Part Event Result-----------------------------------------------------------------------------AvamarClient-aix5-ppc 6.0.100-580 USR DEINSTALL SUCCESS


Installing the Avamar for DB2 Client on Microsoft WindowsINSTALLATION AND CONFIGURATION

Upgrading the Avamar for DB2 Client on IBM AIXTo upgrade the Avamar for AIX Client and Avamar DB2 plug-in software, uninstall the old software and install the new software.

Installing the Avamar for DB2 Client on Microsoft Windows

Task list. To install the Avamar for DB2 Client on supported Microsoft Windows platforms:

• Install the Avamar for Windows Client (page 23)• Register the Avamar for Windows Client (page 25)• Install the Avamar Windows DB2 plug-in (page 26)

Windows Server 2008 and 2008 R2 with User Account Control. In Windows Server 2008, Microsoft added the User Account Control (UAC) feature. UAC is designed to provide additional operating system security by preventing software from being installed with administrator privileges, unless an administrator authorizes the elevated privileges.

Starting the Avamar for Windows Client installer with normal account privileges does not install the software correctly on a computer with a default implementation of UAC. Instead, run the installer with elevated administrative privileges to correctly install the software.

This interim solution is included in the following installation procedures.

Install the Avamar for Windows Client



http://AVAMARSERVER








6. Click the correct operating system hyperlink for the client computer.




7. Do one of the following:

IMPORTANT: For computers with UAC, you must download the install package to a temporary directory. Do not open it in place. Windows Server 2008 and 2008 R2 with User Account Control (page 23) provides additonal information.

8. Start the installer using one of the methods in the following table.

The installation 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.

IF DO THIS

You are installing on a 32-bit Microsoft Windows Server platform.

Select the AvamarClient-windows-x86-VERSION.msi install package.


Select the AvamarClient-windows-x86_64-VERSION.msi install package.

IF DO THIS

You are installing on a non-UAC computer and want to run the installation file in place.

Open the installation file in place on the server.

You are installing on a non-UAC computer and want to download and run the installation file.

Download the installation file to a temporary directory on the computer.

You are installing on a UAC computer.

1. In Windows, right-click the Command Prompt icon and select Run as administrator.

2. 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.

3. On a single line, type the following command to launch the installer by typing:msiexec /i AvamarClient-windows-x86_64-VERSION.msi

where VERSION is the version number of the available install package.



Register the Avamar for Windows Client

Before or restore files on the DB2 server, you must register it with the Avamar system.

To register the client:

1. Right-click the Avamar client system tray icon.

A menu appears.

2. Select Activate.

The Activate Client Setup dialog box appears.

3. Type the following:

4. Click OK.

FIELD DESCRIPTION

Administrator Server Address

Administrator server network hostname as defined in DNS.

Client Domain Avamar domain where you want this client to reside.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.IMPORTANT: If entering a subdomain (for example, clients/windows), 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.



Install the Avamar Windows DB2 plug-in



http://AVAMARSERVER











8. Either open the installation file in place (on the server) or double-click the downloaded installation file.

The InstallShield Wizard appears.

9. Follow the instructions in the wizard.

10.Click Finish to complete the installation procedure.

IF DO THIS


Select the AvamarDB2-windows-x86-VERSION.msi install package.


Select the AvamarDB2-windows-x86_64-VERSION.msi install package.


Uninstalling and upgrading the Avamar for DB2 Client on Microsoft WindowsINSTALLATION AND CONFIGURATION

Uninstalling and upgrading the Avamar for DB2 Client on Microsoft Windows

You do not have to uninstall earlier versions of Avamar for DB2 Client software from Microsoft Windows before you install a new version. If you attempt to install the Avamar for DB2 Client on a server where it is already installed, you are prompted during installation whether to upgrade to the new version or remove the earlier 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 for DB2 Client.


Installing the Avamar for DB2 Client on Red Hat Enterprise LinuxINSTALLATION AND CONFIGURATION

Installing the Avamar for DB2 Client on Red Hat Enterprise Linux

Task list. To install the Avamar for DB2 Client on supported Red Hat Enterprise Linux platforms:

• Download Avamar Linux DB2 install packages (page 28)• Install and register the Avamar for Linux Client (page 29)• Install and Configure the Avamar DB2 Plug-In (page 30)

Download Avamar Linux DB2 install packages

1. Log in to the computer on which to install this software.


http://AVAMARSERVER

where AVAMARSERVER is the Avamar server network hostname (as defined in DNS) or IP address.




4. Scroll down until the Documents and Downloads hyperlink is visible.

5. Click Documents and Downloads.

The Documents and Downloads page appears.


A directory listing appears

7. Download the Avamar for Linux Client install package to a temporary install directory on the system.

8. Note the Avamar for Linux Client install package filename.

9. Download the Avamar DB2 plug-in install package to the same directory as the Avamar for Linux Client install package.

10.Note the Avamar DB2 plug-in install package filename.



Install and register the Avamar for Linux Client


2. Install the Avamar for Linux Client software by typing:

cd /tmp

rpm -ivh AvamarClient-linux-rhel4-x86_64-VERSION.rpm

where /tmp is the temporary install directory and AvamarClient-linux-rhel4-x86_64-VERSION.rpm is the Avamar for Linux Client install package that you downloaded (page 28).


########################################### [100%]########################################### [100%]Installation completeYou 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.logavagent Info <5417>: daemonized as process id 2066avagent.d Info: Client Agent started.

3. Register and activate this client with the Avamar server by typing:

/usr/local/avamar/bin/avregister


=== Client Registration and ActivationThis 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 the domain to use when registering this client.

IMPORTANT: If typing a subdomain (for example, clients/MyClients), 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).


avagent.d Info: Client Agent stopped. [ OK ]avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent.d Info: Client activated successfully. [ OK ]avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent Info <5417>: daemonized as process id 3385avagent.d Info: Client Agent started. [ OK ]Registration Complete.



Install and Configure the Avamar DB2 Plug-In

IMPORTANT: You must Install and register the Avamar for Linux Client (page 29) before installing the Avamar DB2 plug-in.

User=root 1. Ensure that you are still logged in to the computer that hosts the DB2 server as root.

2. Install the Avamar DB2 plug-in software by typing:

cd /tmp

rpm -ivh AvamarDB2-linux-rhel4-x86_64-VERSION.rpm

where /tmp is the temporary install directory and AvamarDB2-linux-rhel4-x86_64-VERSION.rpm is the Avamar for Linux Client install package that you downloaded (page 28).


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.logavagent Info <5417>: daemonized as process id 23351avagent Info: Client Agent started.Installation completeYou may run /usr/local/avamar/bin/avdb2setup to configure this module to backup to the dpn.

3. Configure the DB2 plug-in 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]:

4. 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.

5. 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.

6. 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...


Upgrading the Avamar for DB2 Client on Red Hat Enterprise LinuxINSTALLATION AND CONFIGURATION

avagent.d Info: Stopping Avamar Client Agent (avagent)...avagent.d Info: Client Agent stopped.avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent Info <5417>: daemonized as process id 479284avagent.d Info: Client Agent started.

Uninstalling and upgrading the Avamar for DB2 Client on Red Hat Enterprise Linux


2. List installed Avamar software by typing:

rpm -qa | grep Av


AvamarClient-VERSIONAvamarDB2-VERSION

3. Note the full package names.

4. Uninstall the Avamar DB2 plug-in by typing:

rpm -e AvamarDB2-VERSION

where AvamarDB2-VERSION is the Avamar DB2 plug-in install package returned in step 2.


Removing the AvamarDB2 librariesavagent Info: Stopping Avamar Client Agent (avagent)...avagent Info: Client Agent stopped.avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.logavagent Info <5417>: daemonized as process id 23888avagent Info: Client Agent started.

5. Uninstall the Avamar for Linux Client by typing:

rpm -e AvamarClient-VERSION

where AvamarClient-VERSION is the Avamar software install package returned in step 2.


avagent.d Info: Client Agent stopped.

Upgrading the Avamar for DB2 Client on Red Hat Enterprise Linux

To upgrade the Avamar for Linux Client and Avamar DB2 plug-in software, uninstall the old software and install the new software. Use of the Linux software upgrade command (rpm -Uh) is not supported.


BACKUP

This chapter describes how to use the Avamar for DB2 Client to back up an entire database.

Database preparationThis topic explains how to prepare the database for offline or online backups.

Offline backups. To perform offline backups of a DB2 database, ensure that the no application is connected to the database when the operation begins and that no clients attempt to connect to the database for the duration of the backup operation.

IMPORTANT: 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. Type the following command on the DB2 server:

db2 update db cfg for DATABASE-NAME using LOGRETAIN ON

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 as an on-demand backup option.


On-demand backupBACKUP

On-demand backupThe Avamar for DB2 Client offers three types of backups:

• Offline backups• Online backups that contain archive logs• Online backups without archive logs

To perform an on-demand backup:

1. Prepare the database according to the instructions in Database preparation (page 32).

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 Clients tree, select the DB2 server to back up.

5. Leave the Browse for Files, Folders or Directories option selected.

6. In the tree, select the DB2 plug-in.

7. Click the DB2 instance folder.

A list of databases appears to the right.

8. Select the database to back up.

9. Select Actions > Backup Now.

The On Demand Backup Options dialog box appears.



10.Select a retention setting for the backup.

11.Select the encryption method for client/server data transfer during this backup. Choices are:

12.Click More Options.

The Backup Command Line Options dialog box appears.

13.Choose whether to perform an online or offline database backup by selecting or clearing the Create an ONLINE backup checkbox.


Retention period To automatically delete this backup from the Avamar server after a specific number of days, weeks, months, or years, select this option and type the number of days, weeks, months, or years.

End date To automatically delete this backup from the Avamar server on a specific calendar date, select this option and browse to that date on the calendar.

No end date To keep this backup for as long as this client remains active in the Avamar server, select this option.

High Strongest available encryption setting for that specific client platform.

Medium Medium strength encryption.

None No encryption.

NOTE: The exact encryption technology and bit strength used for any given client/server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information.



14. 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.

IMPORTANT: If you exclude archive logs from the database backup, ensure that archive logs files are included in filesystem backups. Failure to do so might result in loss of data.

15. Type the Instance Admin Username and Instance Admin Password.

16.Click OK to return to the On Demand Backup Options dialog box.

17.Click OK again.

The On Demand Backup Options dialog box closes.

18.Click View Details to view details of the backup or click Close.


Scheduling DB2 server backupsBACKUP

Scheduling DB2 server backups

Task list. To back up the DB2 server on a regular schedule:

• Create a dataset for DB2 server backups (page 36).• Set up scheduled DB2 server backups (page 39) by:

• Creating a dedicated group for DB2 backups.• Adding the DB2 server to this new group.• Assigning the new dataset to this new group.• Assigning a schedule to this new group.• Assigning a retention policy to this new group.

• Enable backups for the group (page 44).

A thorough discussion of groups, group policy, datasets, schedules, and retention policies is beyond the scope of this publication. The EMC Avamar Administration Guide provides additional information.

Creating a dataset for DB2 server backups

1. Start Avamar Administrator and log in to the root domain as an administrative user.

2. Select Tools > Manage Datasets.

3. The Manage All Datasets window appears.



4. Click New.

The New Dataset dialog box appears.

5. Type a name for the dataset.

IMPORTANT: Do not use any of the following characters in the dataset name: asterisk (*), forward slash (/), backward slash (\), colon (:), semicolon (;), question mark (?), greater-than sign (>), less-than sign (<), or vertical bar (|).

6. Click the Source Data tab.

7. Select Enter Explicitly.

8. Select the correct DB2 plug-in from the Select Plug-In Type list.

9. Click ...

The Select Files And/Or Folders dialog box appears.

10. In the Clients tree, select the DB2 server.

11.Select the DB2 plug-in.



12.Select the database to back up with this dataset.

13.Click OK.

The Select Files And/Or Folders dialog box closes.The remaining dialog box tabs are used to set optional parameters such as exclude and include list entries and optional plug-in commands. However, the DB2 plug-in does not support include or exclude lists in datasets.

14.Click the Options tab.

15.Choose whether to perform an online or offline database backup by selecting or clearing the Create an ONLINE backup checkbox.

16. 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.

IMPORTANT: If you do not include archive logs in the database backup, ensure that archive logs files are included in file system backups. Failure to do so might result in loss of data.


18.Click OK.



Setting up scheduled DB2 server backups

1. In Avamar Administrator, click the Policy launcher button.

The Policy window appears.

2. Select Actions > New Group.

The New Group wizard appears.

3. Select or type the information in the following table.


Name Type a name for the group.IMPORTANT: Do not use any of the following characters in the group name: asterisk (*), forward slash (/), backward slash (\), colon (:), semicolon (;), question mark (?), greater-than sign (>), less-than sign (<), or vertical bar (|).



The remaining wizard screens are used to select a dataset, schedule, and retention policy, as well as build a client list for this group.

You can click Finish at any time. Doing so causes the new group to be created using system default settings and an empty client list. You can change those settings by editing the group properties.

Disabled This option is selected by default. Clear this option to immediately use this group to take regularly scheduled client backups.

Encryption Method

This is the group encryption method that is used by all members of this group for client/server network communications unless it is overridden at the client level. Choices are:

High Strongest available encryption setting for that specific client platform.

Medium Medium strength encryption.

None No encryption.

NOTE: The exact encryption technology and bit strength used for any given client-server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information.

Override Schedule

Select this option to override the assigned schedule for this group.You can also skip the next scheduled backup entirely (Skip Next Backup) or perform the next scheduled backup one time only (Run Next Backup Once).

Domain Location in the Avamar server where this group should reside.




4. Click Next.

The next New Group wizard screen appears.

5. Select the dataset that you defined for the group during Creating a dataset for DB2 server backups (page 36) from the Select an Existing Dataset list.

6. Click Next.


7. Select a schedule for the group from the Select an Existing Schedule list.



NOTE: 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.

8. Click Next.


9. Select a retention policy for the group from the Select an Existing Retention Policy list.

NOTE: 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.



10.Click Next.

The final New Group wizard screen appears.

This screen is used to build a list of clients that are members of the group. In this case, the group contains only one client, the DB2 server.

11.Select the DB2 server from the client list.

12.Click Finish.

The New Group wizard closes and the new group appears in the Policy window.



Enabling scheduled DB2 server backups

1. Start Avamar Administrator and log in to the root domain as an administrative user.

2. Click the Policy launcher button.

The Policy window appears.

3. Click the Policy Management tab.

4. Click the Groups tab.

5. Select the group that you created in the previous procedure (the group that now contains only the DB2 server).

6. Select Actions > Group > Disable Group.

This clears the Disable Group option on the Actions > Group menu.

A confirmation message appears.

7. Click Yes to enable this group.


RESTORE AND RECOVERY

This chapter describes how to use the Avamar for DB2 Client to restore an entire database, and roll the database forward (recover it) 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

Database preparationTo perform offline restores of a DB2 database, ensure that the database is idle when the operation begins and that no clients attempt to connect to the database for the duration restore operation.

Restore overviewThe procedure that you use to restore a DB2 database from Avamar backups depends on the type of backup used to back up the database:

• Restoring from an offline backup (page 47)• Restoring from an online backup with archive logs (page 50)• Restoring from an online backup without archive logs (page 59)

You can restore the database to its original location or to a different location (also known as "redirected restore").

In each of these scenarios, you must first locate and select the correct backup in the system (page 46), and then perform the correct restore procedure.


Locating and selecting a backupRESTORE AND RECOVERY

Locating and selecting a backupBefore you can perform any restore procedure, you must locate and select the correct backup in the system.

1. In Avamar Administrator, click the Backup & Restore launcher button.

The Backup and Restore window appears.

2. Click the Select for Restore tab.

3. In the Clients tree, select the DB2 server.

4. Click the By Date tab.

A browsable calendar appears for locating backups in the Avamar server.

5. In the Backup History pane, browse to a valid backup date in the calendar.

Dates highlighted in yellow indicate that a backup was performed on that date.

6. Select a backup from the backups list to the right of the calendar.

The contents list below the Backup History pane is populated.

7. Click the DB2 instance folder.

A list of database backups appears to the right. The prefix in the filename for a database backup indicates the type of backup, as discussed in the following table.

8. Select the database backup to restore.

If you are restoring one or more databases to their original locations, then you can select more than one database. However, if you are restoring the database to a different location (that is, redirected restore), then you can select only one database.

TYPE OF BACKUPFILENAME

PREFIX EXAMPLE FILENAME

Offline c- c-DB-NAME

Online with archive logs hl- hl-DB-NAME

Online without archive logs h- h-DB-NAME


Restoring from an offline backupRESTORE AND RECOVERY

Restoring from an offline backup1. Locate and select the offline backup in the system, as discussed in Locating

and selecting a backup (page 46).

This database is prefixed with "c-." For example: c-DB-NAME.

2. Select Actions > Restore Now.

The Restore Options dialog box appears.


IMPORTANT: If performing a redirected restore, the restore target directory must be on the same client from which the backup was originally taken. Restores to other clients are not supported.

IF DO THIS

You are restoring one or more databases to their original location.

Select Restore everything to its original location.

You are restoring the database to a different location (that is, redirected restore).

Select Restore everything to a different location.



4. If you selected Restore everything to a different location in step 3, then browse the filesystem to specify the location for the restored database in the Absolute Destination field and do one of the following:

IF DO THIS

You are restoring to a Windows DB2 client

In the Absolute Destination field, type the drive letter where you want to restore the database. For example, C:\.During the restore, DB2 creates the following directory structure and restores the database to it:

DRIVE\INSTANCE\NODEwhere DRIVE is the drive letter entered in the Absolute Destination field, INSTANCE is the database instance name, and NODE is the database node name.

You are restoring to an AIX or Linux DB2 client

In the Absolute Destination field, type the full path to the directory where you want to restore the database. For example, /home/db2inst/ or /local/databases.The directory should have the same owner and group attributes as the database owner.During the restore, DB2 creates the following directory structure and restores the database to it:

PATH/INSTANCE/NODEwhere PATH is the path entered in the Absolute Destination field, INSTANCE is the database instance name, and NODE is the database node name.



5. Click More Options.

The Restore Command Line Options dialog box appears.

6. Select the Restore Only option.


8. If you selected Restore everything to a different location in step 3, type a new name for the database in the Database Name field. Otherwise, leave this field emtpy.

9. Click OK.

The Restore Command Line Options dialog box closes.

10.Switch to the Restore Options dialog box and click OK.

The Restore Options dialog box closes.

11.Click View Details to view details of the restore or click Close.


Restoring from an online backup with archive logsRESTORE AND RECOVERY

Restoring from an online backup with archive logsIf you have an online backup that contains archive logs, then you can restore both the database and the archive logs, and automatically roll the database forward (recover it) 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

Alternatively, you can restore only the database or only the archive logs.

Restoring and recovering the database

To restore both the database and the archive logs, and automatically roll the database forward (recover it):

1. Locate and select the correct online backup that contains archive logs, as discussed in Locating and selecting a backup (page 46).

This database is prefixed with "hl-." For example: hl-DB-NAME.




IF DO THIS









IF DO THIS




You are restoring to an AIX or Linux DB2 client







6. Select the Restore and Recover option.

7. From the Type of Recovery list, choose the point to recover to.

IFRECOVERING TO DO THIS

The end of the backup (DB2 9.5 and later)

Select End of Backup.

The end of the archive logs Select End of logs.

A specific point in time Select Point In Time, Then type a valid recovery date and time in the Date and Time field using yyyy-mm-dd hh:mm:ss format. Time should be in the time zone of the client system.The entry can be truncated to the desired precision level. For example, minutes and seconds can be omitted for convenience.



8. In the Directory path to restore archive logs field, type the full path of a top-level destination directory (folder) to which to restore the archive logs.

The restore operation automatically creates a subdirectory at this location to which the archive logs are written. This new subdirectory is named:BACKUP-IMAGE-NAME-TIMESTAMPwhere BACKUP-IMAGE-NAME and TIMESTAMP are the backup image name and restore timestamp, respectively.

NOTE: Specify the path to which to restore the archive logs even if you select the Restore and Recover option.


10. If you selected Restore everything to a different location in step 3, type a new name for the database in the Database Name field.

11.Click OK.







Restoring only the database







IF DO THIS











IF DO THIS




You are restoring to a AIX or Linux DB2 client







9. Click OK.





12.Wait for the restore to complete.

13.Restore the archive logs from a filesystem backup to the SQLOGDIR directory (that is, the directory location stored by the DB2 SQLOGDIR variable).

14.Manually roll the database forward to the desired point in time by issuing a rollforward command on the DB2 server.

This is an example of a command that rolls the database forward to the end of the archive logs (it applies all the logs):

db2 rollforward db DB-NAME to end of logs and complete

where DB-NAME is the database name.

If the rollforward operation is not executed, subsequent backup and restore operations involving the Avamar DB2 plug-in fail with an error message advising that the database must be rolled forward.



Restoring only the archive logs

If you have an online backup that contains archive logs, you can restore only the archive logs (not the database).

To restore only the archive logs from an online backup:







IF DO THIS

You are restoring the archive logs to their original location.


You are restoring the archive logs to a different location (that is, redirected restore).




4. If you selected Restore everything to a different location in step 3, then browse the filesystem to specify the full path of a top-level destination directory (folder) to which to restore the archive logs.




6. Select the Restore only archive logs from ONLINE backup option.

7. If you selected Restore everything to its original location in step 3, then in the Directory path to restore archive logs field, type the full path of a top-level destination directory (folder) to which to restore the archive logs.



9. Click OK.






Restoring from an online backup without archive logsRESTORE AND RECOVERY

Restoring from an online backup without archive logsIf you have an online backup that does not contain archive logs, then you can 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 from an online backup without archive logs:

1. Locate and select the correct online backup without archive logs, as discussed in Locating and selecting a backup (page 46).

This database is prefixed with "h-." For example: h-DB-NAME.





IF DO THIS











IF DO THIS




You are restoring to a AIX or Linux DB2 client







9. Click OK.



11.Wait for the restore to complete.

12.Restore the archive logs from a filesystem backup to the SQLOGDIR directory (that is, the directory location stored by the DB2 SQLOGDIR variable).

13.Manually roll the database forward to the desired point in time by issuing a rollforward command on the DB2 server.

This is an example of a command that rolls the database forward to the end of the archive logs (it applies all the logs):

db2 rollforward db DB-NAME to end of logs and complete

where DB-NAME is the database name.

If the rollforward operation is not executed, subsequent backup and restore operations involving the Avamar DB2 plug-in fail with an error message advising that the database must be rolled forward.


APPENDIX A — PLUG-IN OPTIONS

Important terms and conceptsPlug-in options provide additional control of backups and restores. These options are context-sensitive to both the operation being performed and the specific plug-in selected for that operation.

You can specify these options during on-demand backup and restore operations, or persistently set the options in datasets for scheduled backups.

Backup or restore option dialog boxes automatically appear when you initiate on-demand backups or restores, respectively.

When you create a new dataset, the new dataset wizard offers an opportunity to configure persistent backup plug-in option settings for that dataset.

To view or set plug-in options for an existing dataset:

1. In Avamar Administrator, select Tools > Manage Datasets.

The Manage All Datasets window appears.

2. Select a dataset from the list and click Edit.

The Edit Dataset dialog box appears.

3. Click the Options tab.

4. Set the plug-in options either using the graphical controls or by typing option names and values as free text.

Setting plug-in options using graphical controls. Click the Options tab and select a plug-in to display options for the plug-in.

These settings are represented by graphical controls such as options, radio buttons, list boxes, and so forth.

The advantage of using graphical controls to set plug-in options is that you cannot type an option name or value incorrectly. Only valid states are shown.

To set advanced options that are normally only necessary to debug an Avamar system, click Show Advanced Options. The advanced options are shown in red.


DB2 plug-in optionsAPPENDIX A — PLUG-IN OPTIONS

Typing option names and values as free text. You can also set plug-in options by typing option names and values as free text.

Click More to expand the dialog box to include Enter Attribute and Attribute Value fields, which can be used to input plug-in options and values as free text.

However, it must be understood that no error checking or validation is performed on these free text entries. In addition, free text entries override settings made by way of the graphical controls.

DB2 plug-in optionsThis topic describes the available options for the following Avamar AIX DB2 plug-ins:

• AIX DB2• Windows DB2• Linux DB2

Backup options

SETTING DESCRIPTION

Create an ONLINE backup

If selected, the database can be backed up while it is operational. This is also known as a “hot backup”.IMPORTANT: DB2 Archive Logging must already be enabled to successfully perform online backups.

Exclude archive logs in ONLINE backup

IMPORTANT: By default, the archive logs are included in the backup. If you do not include the archive logs in the backup, select Exclude archive logs in ONLINE backup. However, if you do not include archive logs in the database backup, ensure that archive logs are included in filesystem backups. Failure to do so might result in loss of data.

Instance Admin Username

Instance Admin Password

Password for the Instance Admin Username.

AD

VA

NC

ED

OP

TIO

NS Enable debugging messages

If selected, maximum information is written to log files.IMPORTANT: If selected, very large log files are created.



Restore options

SETTING DESCRIPTION

RE

CO

VE

R O

R R

ES

TO

RE

Restore and Recover For online backups that have archive logs, restores both the database and the archive logs, and rolls the database forward (recovers it). If this option is selected, you must select one of the options from the Type of Recovery list and specify a value in the Directory path to restore archive logs field.

Restore Only Performs only a restore of the backups (no recovery). 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 image. It does not restore the database.

RE

CO

VE

RY

TY

PE

Type of Recovery When the Restore and Recover option is selected, select a recovery option from the list:

End of Logs The database is rolled forward until the end of the archive logs.

Point In Time The database is rolled forward until a certain point in time, which should be specified in the Date and Time field.

End of Backup The database is rolled 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 in yyyy-mm-dd hh:mm:ss format in this field. The time should be in the timezone of the client system.The entry can be truncated to the desired precision level. For example, minutes and seconds can be omitted for convenience.

GE

NE

RA

L

Instance Admin Username

Instance Admin Password

Password for the Instance Admin Username.

Database Name If Restore everything to a different location is selected (redirected restore), then specify the new name for the database in this field.

Directory path to restore archive logs

Full path to the location on the target filesystem to which archive logs are written.



AD

VA

NC

ED

OP

TIO

NS Enable debugging

messagesIf selected, maximum information is written to log files.IMPORTANT: If selected, very large log files are created.

SETTING DESCRIPTION
