Database Administrator (DBA) GUIDE. DB2 idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 73

(1)

Database Administrator (DBA) GUIDE DB2 iDataAgent

(2)

DB2 DBA Guide

Overview

System Requirements

Getting Started - Backup Administrator

Deployment On unix

Configuration

Getting Started - Database Administrator

Prerequisites Configuration

Backup

Restore

Data Retention

Overview - DB2 DBA

Introduction

Key Features

Terminology

Data Protection Suite's DB2 iDataAgent offers you a simplified, end-to-end backup and recovery solution for DB2 data in your enterprise. It provides a greater control on your data as you can perform a granular backup and recovery of any specific or multiple tablespaces or archived logs of your database. You can effortlessly perform an out of place restore operations of your database or the redirected restores of tablespaces.

The DB2 iDataAgent offers the following features for database administrators:

z Ensure a seamless integration with Data Protection Suite's data protection using scripts to automatically configure your database. z Perform DB2 commands for backup and restore operations using the load options.

z Perform backup and restore operations using the DB2 Control Center with vendor options.

z Schedule backup and restore operations using cron jobs, the DB2 Control Center and Data Protection Suite's CommCell Console. z Greater control with new command line tools to query and restore data.

z Effective utilization of the resources using the Client Side Deduplication. You can also verify whether the MediaAgent contains a particular data block before sending it on to the network. This reduces the amount of storage needed in the backup media.

z Simplified management of the retention policy and automatic deletion of the backup images to retain the backup data using built in parameters and Data Protection Suite's registry key.

The following diagram illustrates Data Protection Suite's DB2 backups:

Overview Deployment - Windows Deployment - Windows Cluster Deployment - Unix Deployment - Unix Cluster Configuration

Introduction

(4)

The following terminology is used in the DB2 iDataAgent documentation:

Terminology

Client The computer in which the iDataAgent is installed. The client computer contains the data to be secured. Instance The DB2 instance that contains the DB2 databases.

Backupset The DB2 database to be used for backup and restore operations Subclient The DB2 data to be backed up.

(5)

System Requirements - DB2 iDataAgent

The following requirements are for the DB2 iDataAgent:

System Requirements Supported Features License Requirements

Application/Operating System

Architecture

DB2 Universal Database 10.5/10.1/9.7/9.5/9.1 64-bit on:

AIX AIX 5.3*, 6.1, 7.1

*with technology level 6 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

Power PC

HP-UX HP-UX 11i v3 (11.31) Itanium

HP-UX 11i v2 (11.23) Itanium

Linux Red Hat Enterprise Linux

Red Hat Enterprise Linux 6.x with libstdc++ version 4.2.4 or above Power PC

Red Hat Enterprise Linux 6 with glibc 2.12.x x64

Red Hat Enterprise Linux 5.x with glibc 2.5.x x64

Red Hat Enterprise Linux 4.x with glibc 2.3.x Supported only on versions 9.5 and 9.1.

x64

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x x64 Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x x64 SuSE Linux (SLES)

SuSE Linux 11.x with glibc 2.9.x and above x64

SuSE Linux 11 Enterprise Server with libstdc++ version 4.2.4 or above Power PC

SuSE Linux 10.x with glibc 2.4.x x64

SuSE Linux 10 Enterprise Server s390x 64-bit

Z-Linux Red Hat Enterprise Linux

Red Hat Enterprise Linux 6.x s390x 64-bit

Red Hat Enterprise Linux 5.x s390x 64-bit

Red Hat Enterprise Linux 4.x Supported only on versions 9.5 and 9.1.

s390x 64-bit

Solaris Solaris 11.x x64, Ultra5 or higher recommended

Solaris 10.x with a minimum of SunOS (Sparc) Patch 119963-14 x64, Ultra5 or higher recommended

Windows Windows 2008

Microsoft Windows Server 2008 x64 Editions *Core Editions not supported

Windows 2003

Microsoft Windows Server 2003 Editions with a minimum of Service Pack 2

DB2 Universal Database 10.5/9.7/9.5/9.1 32-bit on:

Linux Red Hat Enterprise Linux

Red Hat Enterprise Linux 6 with glibc 2.12.x x86 or compatible processors Red Hat Enterprise Linux 5.x with libstdc++ version 4.2.4 or above Power PC

Red Hat Enterprise Linux 5 with glibc 2.6.x x86 or compatible processors Red Hat Enterprise Linux 4.x with glibc 2.3.x

Supported only on versions 9.5 and 9.1.

x86 or compatible processors

(6)

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

Windows

888 MB on Data Protection Suite install path including Job Results and Log files 88 MB on Job Results

23.5 MB on Log File path (without debug)

Linux

568 MB on Data Protection Suite install path including Log Files and excluding Job Results 1 MB on Data Protection Suite Job Results.

34 MB on Log Files (without debug)

AIX

2228.30 MB on Data Protection Suite install path including Job Results 1.97 MB on Job Results

906.10 MB on Log location with debug

For a comprehensive list of supported components, see Unix Virtualization.

Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported.

The File System iDataAgent will be automatically installed during installation of this software, if it is not already installed. For System Requirements and install information specific to the File System iDataAgents, refer to:

z System Requirements - Microsoft Windows File System iDataAgent z System Requirements - AIX File System iDataAgent

z System Requirements - HP-UX File System iDataAgent z System Requirements - Linux File System iDataAgent z System Requirements - Solaris File System iDataAgent

On Solaris computers, the operating system must have been installed with at least the user level software option selected.

SELinux

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create an SELinux policy module, perform the following steps as user "root": 1. Create the following files in the /usr/share/selinux/devel directory:

SuSE Linux 11.x with glibc 2.9.x and above x86 or compatible processors

SuSE Linux 10.x with glibc 2.4.x x86 or compatible processors

SuSE Linux 10 Enterprise Server with libstdc++ version 4.2.4 or above Power PC Windows Windows 2008

Microsoft Windows Server 2008 32-bit Editions Windows 2003

Microsoft Windows Server 2003 Editions with a minimum of Service Pack 2

Cluster - Support

Hard Drive

Solaris Zones/Containers Support

AIX LPAR/WPAR Support

Miscellaneous

File Name Content of the File

(7)

2. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

[root]# make backup_IDA.pp

Compiling targeted backup_IDA module

/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp /usr/bin/checkmodule: policy configuration loaded

/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod Creating targeted backup_IDA.pp policy package

rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc [root]# semodule -i backup_IDA.pp

[root]#

3. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

Microsoft Visual C++

Microsoft Visual C++ 2010 and 2008 Redistributable Packages are automatically installed. Note that these Visual C++ Redistributable Packages can co-exist with other versions of this software.

.NET Framework

.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.

On Linux, if you have installed libstdc++.so.6, make sure to install the compat-stdlibc++ rpm containing libstdc++.so.5 also. DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with a specific application or operating system.

where:

<directory> is /usr/share/selinux/devel <file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

policy_module(<name>,<version>) ############################## where:

<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

<version> is the version of the policy module. It can be any number, such as 1.0.0.

For Example: While creating a policy module for the backup_IDA application, you can use the following content. policy_module(backup_IDA,1.0.0)

<directory>/<file_name>.fc where:

<directory> is /usr/share/selinux/devel <file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

The content of the file should be as follows:

Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libIndexing.so -- gen_context (system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libSnooper.so -- gen_context (system_u:object_r:texrel_shlib_t,s0)

(8)

(9)

Supported Features - DB2 iDataAgent

The following table lists the features that are supported by this Agent.

System Requirements Supported Features License Requirements

Feature

Sub-Feature

Support Comments

Advanced Backup/Archive Options Data tab - Catalog Data tab - Verify Synthetic Full Job Retry tab

Media tab - Allow other Schedule to use Media Set Media tab - Mark Media Full on Success Media tab - Reserve Resources Before Scan Media tab - Start New Media

Startup tab VaultTracking tab Comments

Advanced File System iDataAgent Options Automatic File System Multi-Streaming On Demand Data Protection Operation Restore by Jobs

Restore Data Using a Map File Comments

Alerts and Monitoring Global Alerts Job-Based Alerts* Comments

Automatic Updates Automatic Updates

Comments Backup/Archive Options Differential Backup

Full Backup Incremental Backup Other Backup Types Synthetic Full Backup

Comments Delta Backup; seeIncremental Backups

Backward Compatibility Version 8

Version 9 Comments

Browse Browse from Copy Precedence

Browse the Latest Data Browse Using Filters Exclude Data Before Find

Full Backup Transparent Browse Image Browse

No Image Browse Page Size Specify Browse Path Specify Browse Time Subclient Browse Use MediaAgent View All Versions Comments

Clustering Unix Cluster

(10)

Windows - Non-Microsoft Cluster Comments

Command Line Interface Command Line Interface Comments

CommCell Migration CommCell Migration

Comments

Content Indexing Offline Content Indexing Comments

Data Aging Basic Retention Rules

Deleting a Job Extended Retention Rules Retaining a Job Unique Data Aging Rules

Comments Extended Retention Rules are supported for offline/online

fulls.

Data Compression Client Compression

Hardware Compression MediaAgent Compression Comments

Data Encryption Data Encryption Support

Third-party Command Line Encryption Support Comments

Data Multiplexing Multiplexing

Comments

Deduplication MediaAgent Deduplication

Source Deduplication Comments

Erase Backup/Archived Data Erase Data by Browsing Erase Stubs Comments

Global Filters Global Filters

Comments

Installation Custom Package

Decoupled Install Remote Install Restore Only Agents Silent Install Comments Installing 32-bit Components on a Microsoft

Windows x64 Platform

Install 32-bit On x64

Comments Job Restart - Data Protection Not Restartable

Restarts from the Beginning

Restarts from the Beginning of the Database * Restarts from the Point-of-Failure

Comments Third-party command line operations are Not Restartable.

* DB2 IntelliSnap backup copy operations can be restartable from the point-of-failure.

Job Restart - Data Recovery Not Restartable

Restarts from the Beginning

Restarts from the Beginning of the Database Restarts from the Point-of-Failure Comments

(11)

List Media Instance

List Media Associated with Index

List Media Associated with Specific Files and/or Folders

List Media Associated with Specific Jobs Comments

Multi Instancing Multi Instance

Comments

Optimized Scan Optimized Scan

Comments

Pre/Post Processes Pre/Post Process with Data Protection and Recovery Comments

Restore/Recover/Retrieve Destinations Cross-Application Restores (Different Application version) Cross-Platform Restores - Different Operating System

Cross-Platform Restores - Same Operating System - Different Version

In-place Restore - Same path/ destination - Same Client

Out-of-place Restore - Different path/ destination Outofplace Restore Same path/ destination -Different Client

Restore Data Using a Map File

Restore to Network Drive /NFS-Mounted File System

Comments See Restore Destinations for this iDataAgent.

Restore/Recover/Retrieve Options Automatic Detection of Regular Expressions Filter Data From Recover Operations Rename/ Redirect Files on Restore Restore Data Using Wildcard Expressions Restore Data with Pre/Post Processes Restore from Copies

Skip Errors and Continue Use Exact Index Use MediaAgent Comments Restore/Recover/Retrieve Overwrite Options Overwrite Files

Overwrite if file on media is newer Restore only if target exists Unconditional Overwrite

Unconditionally overwrite only if target is a DataArchiver stub

Comments

Schedule Policy Agent Specific Data Protection Schedule Policy All Agent Types Schedule Policy

Comments

Storage Policies Incremental Storage Policy* Standard Storage Policies

Comments Incremental Storage Policy does not support Transaction

Log backups for this agent. Subclient Policies SubClient Policy

Comments

Upgrade Netware - Local

Unix - Remote (Push) Unix/Linux - Local Unix/Linux - Silent Unix/Linux/Macintosh - Local Unix/Linux/Macintosh - Silent Upgrade from CommCell Console Windows - Local

(12)

Additional features are listed below:

Windows - Silent Comments

User Administration and Security Backup Set/Archive Set Instance

Subclient Comments

Activity Control Deconfigure/Reconfigure Components

Auxiliary Copy Languages

CommCell Console MediaAgent

GridStor Scheduling

Log Files Snapshot Engines

Operation window VaultTracker

IntelliSnap Backup Restore/Recover/Retrieve - Other Options

VaultTracker Enterprise Job Restart - Data Collection Cloud Storage

(13)

Getting Started - Backup Administrator

Install the software on a Windows computer on which the DB2 server resides. As soon as you complete the installation, the Windows computer will be added as a client in the CommCell.

If a pending rename operation from a previously installed application is found in the operating system, the software installation may require a system reboot. Hence, plan your installation at a convenient time.

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Download Software Packages

Download the latest software package to perform the install.

1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer. 2. Run SetupAll.exe from the Software Installation Discs.

3. In the License Agreement dialog box, click I accept the terms in the license agreement, and then click Next. 4. In the Install Type dialog box, click Standard, and then click Next.

5. In the Installation Options dialog box, click Join an Existing CommCell, and then click Next. 6. In the Select Platforms dialog box, expand the Database folder, and then click DB2.

Click Next.

7. In the Destination Folder dialog box, verify the default location for software installation. Click Next. If necessary, click Browse... to change the default location.

{ Do not install the software to a mapped network drive

{ Do not use the following characters when specifying the destination path: / : * ? " < > | # { It is recommended that you use alphanumeric characters only

Where to Install

Planning Your Installation

Before You Begin

Installation

The software can be installed using one of the following methods: Method 1: Interactive Install - Standard

Use this procedure to install the software using the standard installation options. Method 2: Interactive Install - Custom

Use this procedure to install the software by specifying installation settings and options.

Method 1: Interactive Install - Standard

(14)

8. In the Summary dialog box, verify all the components that you have selected for installation, and then click Next. 9. In the Installer dialog box, click Yes.

10. In the Prerequisites dialog box, click Reboot Now. The installation will automatically resume after the reboot. If the install program does not automatically resume, run SetupAll.exe from the Software Installation Discs. 11. In the Install dialog box, click Next.

12. In the CommServe Name dialog box, enter the fully qualified domain name of the CommServe in the CommServe Host Name box. { When you specify the CommServe Host Name, do not use the space and the following characters:

\|`~!@#$%^&*()+=<>/?,[]{}:;'" Click Next.

13. In the Communication Interface Name dialog box, enter the following:

{ The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

If necessary you can also type a new (friendly) name for the client in this box. This name will be used in the CommCell and will also be displayed in the CommCell Console. Do not use spaces when specifying a new name for the client.

{ The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card). If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe. Click Next.

14. In the Port Number Selection dialog box, the default port numbers used for CommCell communication are displayed. If necessary, you can modify the port numbers. Click Next.

15. In the Windows Firewall Configuration dialog box, select one of the following options: { If you do not want to disable Windows Firewall, click Next.

{ If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next. For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

16. In the Windows Firewall Exclusion List dialog box, select Add programs to the Windows Firewall Exclusion List to add the CommCell programs and services to the Windows Firewall Exclusion List.

Click Next.

17. In the Client Group Selection dialog box, select a DB2 Client Group, and then click Next.

18. In the Global Filter Options dialog box, click Next.

19. In the Policy Selection dialog box, select a storage policy from the Storage Policy list. Click Next.

20. In the DB2 Archive Path dialog box, enter the DB2 Archive Path or click Browse to select a storage location for the DB2 archive files.

21. In the DB2 Retrieve Path dialog box, enter the DB2 Retrieve Path or click Browse to select a storage location for the DB2 retrieve files.

22. In the DB2 Audit Error Path dialog box, enter the DB2 Audit Error Path or click Browse to select a storage location for the DB2 audit error files. all the nodes.

If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the same name as previously specified.

This screen will not appear if the default port numbers are not used for CommCell communication.

It is recommended to select this option even if the Windows firewall is disabled. This will allow the CommCell programs and services to function without any interruption if the Windows firewall is enabled at a later time.

This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.

This agent does not support Global Filters.

Make sure to select the storage policy even if the file system iDataAgent is not selected during the installation. If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 25.

If you are installing the software in a clustered environment, ensure that the DB2 Archive path resides on a shared drive.

If you are installing the software in a clustered environment, ensure that the DB2 Retrieve path resides on a shared drive.

(15)

23. In the Installer dialog box, click OK.

24. In the Completion Report dialog box, click Reboot Now.

25. To create a storage policy, you must have configured a library in the CommCell. z If you do not already have a library configured, go to Disk Library Creation. z If you have a library configured, go to Storage Policy Creation.

DISK LIBRARY CREATION:

1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Add and then click Disk Library...

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library... 2. From the Add Disk Library dialog box, specify the following:

In the Name box, specify name of the disk library. From the MediaAgent list, select the MediaAgent. Perform one of the following:

Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder. Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Password and Verify Password box, type the password to access the network share.

In the Folder box, type the mount path or click button to select a mount path. Click OK.

3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Click to proceed to the Configuration section.

Storage Policy Creation

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below: Select the Storage Policy type as Data Protection and Archiving and click Next.

Enter the name in the Storage Policy Name box and click Next.

From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next. Ensure that you select a library attached to a MediaAgent operating in the current release.

From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next. For the device streams and the retention criteria information, click Next to accept default values.

Select Yes to enable deduplication for the primary copy.

From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next. Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Click to proceed to the Configuration section.

If you already have a storage policy selected in step 20, click to proceed to the Configuration section. If you have to create a Storage Policy, continue with the following step.

(16)

Default Options Selected During Standard Install

Listed below are the default options that are not selected while performing the Standard Install.

Components installed by default during Standard Install

Listed below are the components that are installed by default while performing the Standard Install:

1. Log on to the client computer as an Administrator or as a member of the Administrator group on that computer. 2. Run SetupAll.exe from the Software Installation Discs.

3. In the License Agreement dialog box, click I accept the terms in the license agreement, and then click Next. 4. In the Install Type dialog box, click Custom, and then click Next.

5. In the Custom Install Type dialog box, click Select components to install on this computer, and then click Next. 6. In the Select Platforms dialog box, expand the Database folder, and then click DB2.

Click Next.

OPTION

ENABLED / DISABLED

DESCRIPTION

Add programs to the Windows Firewall Exclusion List

Disabled This option allows you to add Data Protection Suite programs to the Windows Firewall exclusion list.

This option is not selected.

Global Filter Options

Disabled DB2 iDataAgent does not support Global Filters. This option is not selected.

SELECTED PACKAGE

COMPONENTS INSTALLED

DB2 Agent

_z _{DB2 iDataAgent}

z File System Core z Windows File System

(17)

7. In the Destination Folder dialog box, verify the default location for software installation. Click Next. If necessary, click Browse... to change the default location.

{ Do not install the software to a mapped network drive

8. In the Summary dialog box, verify all the components that you have selected for installation, and then click Next. 9. In the Installer dialog box, click Yes.

10. In the Prerequisites dialog box, click Reboot Now. The installation will automatically resume after the reboot. If the install program does not automatically resume, run SetupAll.exe from the Software Installation Discs. 11. In the Install dialog box, click Next.

12. In the Firewall Configuration dialog box, select one of the following: { If the firewall configuration is not required, click Next.

{ If this computer and the CommServe is separated by a firewall, click Configure firewall services. For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

13. In the CommServe Name dialog box, enter the fully qualified domain name of the CommServe in the CommServe Host Name box. { When you specify the CommServe Host Name, do not use the space and the following characters:

\|`~!@#$%^&*()+=<>/?,[]{}:;'" Click Next.

14. In the Communication Interface Name dialog box, enter the following:

{ The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

{ The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card). If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe. Click Next.

15. In the Port Number Selection dialog box, the default port numbers used for CommCell communication are displayed. If necessary, you can modify the port numbers. Click Next.

16. In the Windows Firewall Configuration dialog box, select one of the following options: { If you do not want to disable Windows Firewall, click Next.

{ If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

17. In the Windows Firewall Exclusion List dialog box, select Add programs to the Windows Firewall Exclusion List to add the CommCell programs and services to the Windows Firewall Exclusion List.

If you are installing the software in a clustered environment, make sure to install the software using the same installation path on all the nodes.

If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the same name as previously specified.

(18)

Click Next.

18. In the Client Group Selection dialog box, select a DB2 Client Group, and then click Next.

19. In the Global Filter Options dialog box, click Next.

20. In the Policy Selection dialog box, select a storage policy from the Storage Policy list. Click Next.

21. In the DB2 Archive Path dialog box, enter the DB2 Archive Path or click Browse to select a storage location for the DB2 archive files.

22. In the DB2 Retrieve Path dialog box, enter the DB2 Retrieve Path or click Browse to select a storage location for the DB2 retrieve files.

23. In the DB2 Audit Error Path dialog box, enter the DB2 Audit Error Path or click Browse to select a storage location for the DB2 audit error files.

24. In the Installer dialog box, click OK.

25. In the Completion Report dialog box, click Reboot Now.

26. To create a storage policy, you must have configured a library in the CommCell. z If you do not already have a library configured, go to Disk Library Creation. z If you have a library configured, go to Storage Policy Creation.

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library... 2. From the Add Disk Library dialog box, specify the following:

In the Name box, specify name of the disk library. From the MediaAgent list, select the MediaAgent. Perform one of the following:

Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder. Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Folder box, type the mount path or click button to select a mount path. Click OK.

3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Click to proceed to the Configuration section.

Storage Policy Creation

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

It is recommended to select this option even if the Windows firewall is disabled. This will allow the CommCell programs and services to function without any interruption if the Windows firewall is enabled at a later time.

This agent does not support Global Filters.

Make sure to select the storage policy even if the file system iDataAgent is not selected during the installation. If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 26.

If you are installing the software in a clustered environment, ensure that the DB2 Audit Error Path resides on a shared drive.

If you already have a storage policy selected in step 20, click to proceed to the Configuration section. If you have to create the Storage Policy, continue with the following step.

(19)

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below: Select the Storage Policy type as Data Protection and Archiving and click Next.

Enter the name in the Storage Policy Name box and click Next.

From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next. Ensure that you select a library attached to a MediaAgent operating in the current release.

From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next. For the device streams and the retention criteria information, click Next to accept default values.

Select Yes to enable deduplication for the primary copy.

From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next. Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Click to proceed to the Configuration section.

Custom Package

Create a compact software package for quick deployment to multiple clients.

Remote Install

Deploy the software from CommCell Console on multiple clients.

Silent Install

Deploy the software silently on multiple clients.

Decoupled Install

Install the software first and later register the client in the CommCell.

Installing Restore Only Agents

Setup a client in the CommCell for restore purposes.

Additional Installation Methods

(20)

Getting Started - Backup Administrator

SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A MICROSOFT CLUSTER. CLICK

TO CONTINUE WITH THE DEPLOYMENT.

Steps involved in installing the DB2 iDataAgent in a Clustered environment: 1. Install the software on physical Nodes

2. Configure the Cluster Group Client

System Requirements

Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.

Download Software Packages

Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.

1. From the active node of the cluster group, log on to the physical computer as an Administrator or as a member of the Administrator group on that computer. 2. Run SetupAll.exe from the Software Installation Discs.

3. Click I accept the terms in the license agreement. Click Next.

4. Click Custom. Click Next.

Before You Begin

Install the software on physical Nodes

If you do not wish to protect physical nodes with a specific agent, you can install that agent in 'restore only' mode, doing so will prevent the consumption of additional license per node. See Installing Restore Only Agents for more information. Alternatively, you can release license from the CommCell Console for a specific agent after installing it on the physical nodes. Refer to Releasing a License section to see the procedure for releasing a license.

The software can be installed on the Physical nodes using the following method: Method : Interactive Installation

Use this procedure to Install the software on the physical nodes from the active node of a cluster group.

Interactive Installation

(21)

5. Click Select components to install on this computer and click Next.

6. Expand Database, and then click DB2. Click Next.

7. Verify the default location for software installation. Click Next.

If necessary, click Browse... to change the default location. { Do not install the software to a mapped network drive

(22)

8. Click Install.

9. Click Yes.

10. Click Reboot Now. The installation will automatically resume after the reboot.

If the install program does not automatically resume, run SetupAll.exe from the Software Installation Discs.

11. Click Next.

The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.

(23)

12. Select one of the following:

{ If firewall configuration is not required, click Next.

{ If this computer and the CommServe is separated by a firewall, click Configure firewall services. For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

13. Enter the fully qualified domain name of the CommServe in the CommServe Host Name box. { Do not use space and the following characters when specifying the CommServe Host Name:

\|`~!@#$%^&*()+=<>/?,[]{}:;'" Click Next.

14. Enter the following:

{ The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

(24)

{ The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card). If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe. Click Next.

15. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers. Click Next.

16. Select one of the following options:

{ If you do not want to disable Windows Firewall, click Next.

{ If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

17. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List. If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the

same name as previously specified.

(25)

Click Next.

18. Select a Client Group. Click Next.

19. Click Next.

20. Select a storage policy from the Storage Policy list. Click Next.

This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list.

It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time.

(26)

If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring storage Policy section.

21. Enter the DB2 Archive Path or click Browse to select a location to store the DB2 archive files.

22. Enter the DB2 Retrieve Path or click Browse to select a location to store the DB2 retrieve files.

23. Enter the DB2 Audit Error Path or click Browse to select a location to store the Db2 audit error files.

(27)

24. Click Yes.

When you click Yes, the software automatically retrieves the list of nodes to which the current active node can failover.

25. Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list. Once you complete your selections, click Next.

The list of Preferred Nodes displays all the nodes found in the cluster; from this list, you are required to select the cluster nodes configured to host this cluster group server.

26. Specify User Name and Password of the Domain Administrator account to perform the remote install on the cluster nodes you selected in the previous step. Click Next.

The Domain Administrator user account that you specify here must have Administrator rights on all the cluster nodes that you selected in the previous step.

(28)

The Installer tries to install the software on all the nodes (physical computers) that you selected in step 25. The progress of the remote install for the cluster nodes is displayed on the Remote Install Progress screen.

27. Click Finish.

28. Click Finish.

z If the software is not installed successfully on any of the passive nodes selected in step 25, or if any passive node is not available during the installation, a separate installation from the CommCell Console needs to be performed on that node in order to prepare it for a failover protection. For remote install instructions, see Remote Install.

z The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.

(29)

After installing the software successfully on all the physical computers that host the Cluster Group, you must configure the Cluster Group Client from the CommCell Console. The following section describes the steps involved in configuring the Cluster Group Client.

1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Windows Cluster.

2. In the Client Name box, type a name for the cluster group. The Client name can be any unique name. In the Host Name box, type the fully qualified domain name of the cluster group.

Host Name is the fully qualified domain name of the cluster group. See the screenshot below for reference.

Configure the Cluster Group Client

(30)

3. Review the cluster group information and click Finish.

Advanced Client Properties window is displayed now.

4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab. All the Windows clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary Agents from the Available list, and then click Add > to move the client to the Selected list.

5. Click the Agents tab.

Select the Agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list. If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click the Cluster Group Configuration tab on the Advanced Client Properties dialog box.

In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an Agent is not installed on all the nodes, then the Agents selection tab on the Advanced Client Properties window will display the Agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using Remote install procedure.

(31)

6. Click the Job Configuration tab.

Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

Click OK.

7. Click OK.

The cluster group client is successfully created.

If you do not have Storage Policy created, continue with the following step. To create a storage policy, you must have a library configured in the CommCell. z If you do not already have a library configured, go to Disk Library Creation. z If you have a library configured, go to Storage Policy Creation.

1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Addand then click Disk Library...

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library... 2. From the Add Disk Library dialog box, specify the following:

{ In the Name box, specify name of the disk library. { From the MediaAgent list, select the MediaAgent. Perform one of the following:

{ Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder. { Select Network Path, if you wish to specify a network path as the target share.

In the Connect As box, type the user name.

In the Password and Verify Password box, type the password to access the network share. z Ensure that the Job Results Directory resides on a shared clustered drive.

z In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.

(32)

In the Folder box, type the mount path or click button to select a mount path. { Click OK.

3. The newly created disk library will be displayed under Libraries node. Storage Policy Creation

1. From the CommCell Browser, navigate to Policies.

2. Right-click the Storage Policies and then click New Storage Policy.

3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below: { Select the Storage Policy type as Data Protection and Archiving and click Next.

{ Enter the name in the Storage Policy Name box and click Next.

{ From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next. Ensure that you select a library attached to a MediaAgent operating in the current release.

{ From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next. { For the device streams and the retention criteria information, click Next to accept default values.

{ Select Yes to enable deduplication for the primary copy.

{ From the MediaAgent list, click the name of the MediaAgent that will be used to host the Deduplication Database (DDB).

In the Location box, type the name of the folder in which the DDB must be located or click the Browse button to select the folder and then click Next. { Review the details and click Finish to create the Storage Policy.

Remote Install

Deploy the software from CommCell Console on multiple clients.

(33)

Getting Started - Backup Administrator

SKIP THIS PAGE IF YOU ARE NOT INSTALLING ON A UNIX CLIENT.

Install the software on a computer that you want to back up. As soon as you complete the installation, the computer on which you have installed the software will be added as a client in the CommCell.

System Requirements

Download Software Packages

1. Log on to the client computer as root. If you are installing the software from the Software Installation Discs, run the following command to mount the CD:

Run the following command from the Software Installation Package or mount point:

2. The product banner and other information is displayed. Press Enter.

3. Read the license agreement. Type y and press Enter.

4. In the Selecting Unix Setup Task dialog, type the number of a setup task in the list, and press Enter.

5. In the Setting Client/Physical Machine Host Name dialog, the default network interface name of the client computer is displayed if the computer has only one network interface (NIC card). Press Enter to accept.

{ If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe, and then press Enter.

6. In the Setting Client Name dialog, the local name of the client computer is displayed. Press Enter to accept.

{ If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will be used in the CommCell and will also be displayed in the CommCell Console.

{ Do not use spaces when specifying a new name for the client.

Where to Install

Before You Begin

Installation

mount -t iso9660,udf /dev/cdrom /mnt/cdrom

./cvpkgadd

You can also run this command as a SUDO user with root privileges:

For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install. ./sudo cvpkgadd

Selecting Unix Setup Task

Please select a setup task you want to perform from the list below: Advanced options provide extra setup features such as creating custom package, recording/replaying user selections and installing External Data Connector software.

1) Install data protection agents on this computer 2) Advanced options

3) Exit this menu Your choice: [1]

Setting Client/Physical Machine Host Name

We found one network interface available on your machine. We will associate it with the client being installed, and it will also be used by the CommServe to connect to the client. Note that you will be able to additionally customize Datapipe Interface Pairs used for the backup data traffic later in the Data Protection Suite Java GUI. Please check the interface name below, and make corrections if necessary:

Client/Physical Machine Host Name: [myclient.company.com]

(34)

7. In the Selecting Modules to Install dialog, type the number associated with the DB2 iDataAgent and press Enter.

8. In the extended Selecting Modules to Install dialog that is displayed after typing the number associated with the DB2 iDataAgent, type d for Done, and then press Enter.

9. In the Configuration for Laptop or Desktop dialog, select the default option no, and press Enter.

10. In the Install Agents for Restore Only dialog, select the default option no, and press Enter.

11. In the Preparing Installation Directory dialog, verify the default path for software installation, and then press Enter. If necessary, enter a path to modify the default path and press Enter.

{ Do not install the software to a mapped network drive { Do not use the following characters when specifying the path:

!@#$%^&*():/?\

{ It is recommended that you use alphanumeric characters only Please specify the client name for this machine.

It does not have to be the network host name: you can enter any word here without spaces. The only requirement is that it must be unique on the CommServe.

Physical Machine Client name: [myclient]

Selecting Modules to Install.

[ ] 1) UNIX File System Basic [1002] [CVGxBase] [ ] 2) UNIX File System Advanced [1101] [CVGxIDA] [ ] 3) MediaAgent [1301] [CVGxMA]

[ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA] [ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA] [ ] 6) SAP for Oracle [1205] [CVGxOrSAP] [ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB] [ ] 8) Informix iDataAgent [1201] [CVGxIfIDA] [ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA] [ ] 10) DB2 iDataAgent [1207] [CVGxDB2] [ ] 11) MySQL iDataAgent [1208] [CVGxMySQL] [ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]

[ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA] >) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help] Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 10

Selecting Modules to Install.

[ ] 1) UNIX File System Basic [1002] [CVGxBase] [ ] 2) UNIX File System Advanced [1101] [CVGxIDA] [ ] 3) MediaAgent [1301] [CVGxMA]

[ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA] [ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA] [ ] 6) SAP for Oracle [1205] [CVGxOrSAP] [ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB] [ ] 8) Informix iDataAgent [1201] [CVGxIfIDA] [ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA] [X] 10) DB2 iDataAgent [1207] [CVGxDB2] [ ] 11) MySQL iDataAgent [1208] [CVGxMySQL] [ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]

[ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA] >) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help] Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

Deciding if to Config for Laptop or Desktop Backups

Do you want to configure the iDataAgent for laptop or desktop backups?

Config for Laptop or Desktop Backups? [no]

Deciding if to Install Agents for Restore Only

Do you want to install the agents for restore only without consuming licenses?

Install Agents for Restore Only? [no]

If you are installing the software in a clustered environment, install the software using the same path on all nodes.

Preparing Installation Directory

Please specify where you want us to install Data Protection Suite binaries.

It must be a local directory or NFS and there should be at least 281MB of free space available. All files will be installed in a "hds" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/hds".

(35)

12. In the Preparing Log Directory dialog, verify the default path for log files, and then press Enter. If necessary, enter a path to modify the default path and press Enter.

{ Do not use the following characters when specifying the path: !@#$%^&*():/?\

{ It is recommended that you use alphanumeric characters only

{ All the modules installed on the computer will store the log files in this directory.

13. In the Deciding If to Use a Unix Group dialog, select the default option Yes, and then press Enter.

14. In the Setting Unix Group dialog, type the Group name, and then press Enter to continue.

15. In the Setting Access Permissions for Group and other Users dialog, select the numbers associated with the access permissions, type d for done, and then press Enter.

16. In the Setting Instance Port Number of cvd dialog, the default port number used for CommCell communication is displayed. If necessary, you can modify the port number. Press Enter.

Preparing Log Directory

Please specify where you want to keep Data Protection Suite log files.

It must be a local directory or NFS share and there should be at least 100MB of free space available. All log files will be created in a "hds/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/hds/Log_Files".

Log Directory: [/var/log]

Deciding If to Use a Unix Group

Most of Data Protection Suite processes run with root privileges, but some are launched by databases and inherit database access rights. To make sure that registry and log files can be written to by both kinds of processes we can either make such files world-writeable or we can grant write access only to processes belonging to a particular group, e.g. a "hds" or a "dba" group.

We highly recommend now that you create a new user group and enter its name in the next setup screen. If you choose not to assign a dedicated group to Data Protection Suite processes, you will need to specify the access permissions later.

If you're planning to backup Oracle DB you should use "dba" group. Would you like to assign a specific group to Software? [yes]

Setting Unix Group

Please enter the name of the group which will be assigned to all Data Protection Suite files and on behalf of which all Data Protection Suite processes will run.

In most of the cases it's a good idea to create a dedicated "hds" group.

However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.

Group name: testgrp1 REMINDER

If you are planning to install Data Protection Suite Informix, DB2, Sybase or Lotus Notes iDataAgent, please make sure to include Informix, DB2, etc. users into group "testgrp1"..

Press <ENTER> to continue...

Setting Access Permissions for Group and Other Users Installer will assign full access rights to root user for all installed Data Protection Suite files and its processes.

For group and any other users, you can specify the access permissions now.

If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install Data Protection Suite agents involving third party software protection.

[X] 1) Allow read permission to group users [X] 2) Allow write permission to group users [X] 3) Allow execute permission to group users [X] 4) Allow read permission to other users [ ] 5) Allow write permission to other users [X] 6) Allow execute permission to other users

Setting Instance Port Number of cvd

Every instance of Data Protection Suite should use a unique set of network ports to avoid interfering with other instances running on the same machine.

The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine. Please enter the port numbers.

(36)

17. In the Setting Instance Port Number of EvMgrC dialog, the default port number used for CommCell communication is displayed. If necessary, you can modify the port number. Press Enter.

18. In the Deciding If to Configure Firewall dialog, you can perform one of the following:

{ If firewall configuration is not required, press Enter.

{ If this computer and the CommServe is separated by a firewall, type Yes and then press Enter. For firewall options and configuration instructions, see Firewall Configuration.

19. In the Setting CommServe Host Name dialog, type the fully qualified domain of the CommServe host name, and then press Enter.

{ Do not use space and the following characters when specifying the CommServe Host Name: \|`~!@#$%^&*()+=<>/?,[]{}:;'"

20. In the Specifying If the CommServe Per-Client Certificate is Enabled dialog, type no and then press Enter if you have not enabled per-client certificate on CommServe. If you have enabled the per-client certificate on CommServe, type yes, and then press Enter.

21. In the Selecting How to Set Commcell Level Global Filters dialog, select one of the following:

{ 1- To inherit the global filter policy configuration set for the CommCell.

{ 2- To apply the global filters policy to the default subclient regardless of the policy set for the CommCell.

{ 3- If you plan to define specific filters for the Agent. Press Enter.

22. In the Selecting Client Computer Groups dialog, type the appropriate number to select the Client Group, and then press Enter.

Port Number for CVD : [8400]

Setting Instance Port Number of EvMgrC

Every instance of Data Protection Suite should use a unique set of network ports to avoid interfering with other instances running on the same machine.

The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine. Please enter the port numbers.

Port Number for CVD: 8400 Port Number for EvMgrC: [8402]

Deciding If to Configure Firewall

You need to configure firewall settings if there is a firewall between this client and the CommServe.

Is there a firewall between this client and the CommServe? [no]

Setting CommServe Host Name

Please specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.

CommServe Host Name: mycommserve.company.com

Specifying If CommServe Per-Client Certificate is Enabled

If you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy, you need to provide installer with a Temp Certificate.

This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and copying/pasting generated certificate to a local file accessible from this installer.

Have you enabled per-client certificate authentication on CommServe? [no]

Selecting How to Set Commcell Level Global Filters

Commcell Level Global Filters are set through Data Protection Suite GUI's Control Panel in order to filter out certain directories or files from backup Commcell-widely.

If you turn on the Global filters, they will be effective to the default subclient.There are three options you can choose to set the filters. Please select how to set the Global Filters for the default subclient?

1) Use Cell level policy 2) Always use Global filters 3) Do not use Global filters Your Choice: [1]

(37)

23. In the extended Selecting Client Computer Groups dialog that is displayed after typing the appropriate client group, type d for Done, and then press Enter.

24. In Deciding if to Configure Storage Policy dialog, type the default option no, and then pressEnter.

If you do not have a Storage Policy created, the following message will be displayed. You may not be prompted for user input. You can create the Storage Policy later in step 27.

25. In the Path for storing the DB2 Logs that are archived dialog, enter the path name, and then press Enter. The db2Archive/db2AuditError/db2Retrieve subfolders will be created under this path.

26. To create a storage policy, you must have configured a library in the CommCell.

z If you do not already have a library configured, go to Disk Library Creation.

z If you have a library configured, go to Storage Policy Creation. Disk Library Creation:

Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library... 2. From the Add Disk Library dialog box, specify the following:

{ In the Name box, specify name of the disk library.

{ From the MediaAgent list, select the MediaAgent. Perform one of the following:

{ Select Local Path if you wish to specify a local path in the MediaAgent computer.

In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder.

{ Select Network Path, if you wish to specify a network path as the target share. In the Connect As box, type the user name.

In the Folder box, type the mount path or click button to select a mount path.

Selecting Client Computer Groups

Client Group(s) is currently configured on CommServe

mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.

[ ] 1) Client Grp1

[a=all n=none r=reverse q=quit d=done >=next <=previous ?=help] Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 1

Selecting Client Computer Groups

Client Group(s) is currently configured on CommServe

mycommserve.company.com. Please choose the group(s) that you want to add this client myclient.company.com to.

[X] 1) Client Grp1

Deciding if to Configure Storage Policy

Would you like to configure Storage Policy on this client? Configure? [no]

Adjusting modes and permissions of files...done. Starting Data Protection Suite services...done. Thank you for choosing Data Protection Suite.

There seem to be no Storage Policies configured on the CommServe. Before you can run any backups of this IDA, you will need to install a MediaAgent, create a Storage Policy and assign it to all

subclients..

Select the storage policy even if the File System iDataAgent is not selected during the installation.

Please provide a path where directories for storing DB2 logs that are archived

(during log archiving) and retrieved (during restore) will be created..

Enter path: /db2/logs

If you have already selected a storage policy, click to proceed to the Configuration section. If you have to create a Storage Policy, continue with the following step.

Database Administrator (DBA) GUIDE. DB2 idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 73

DB2 DBA Guide

Overview

System Requirements

Getting Started - Backup Administrator

Getting Started - Database Administrator

Backup

Restore

Data Retention

Table of Contents

Overview - DB2 DBA

Introduction

Key Features

Terminology

Table of Contents

Introduction

Terminology

System Requirements - DB2 iDataAgent

Application/Operating System

Architecture

DB2 Universal Database 10.5/10.1/9.7/9.5/9.1 64-bit on:

DB2 Universal Database 10.5/9.7/9.5/9.1 32-bit on:

Windows

Linux

AIX

SELinux

Cluster - Support

Hard Drive

Solaris Zones/Containers Support

AIX LPAR/WPAR Support

Miscellaneous

Microsoft Visual C++

.NET Framework

Supported Features - DB2 iDataAgent

Feature

Sub-Feature

Support Comments

Getting Started - Backup Administrator

System Requirements

Download Software Packages

Where to Install

Planning Your Installation

Before You Begin

Installation

Method 1: Interactive Install - Standard

Default Options Selected During Standard Install

Components installed by default during Standard Install

OPTION

ENABLED / DISABLED

DESCRIPTION

Add programs to the Windows Firewall Exclusion List

Global Filter Options

SELECTED PACKAGE

COMPONENTS INSTALLED

DB2 Agent

Custom Package

Remote Install

Silent Install

Decoupled Install

Installing Restore Only Agents

Additional Installation Methods

Getting Started - Backup Administrator

SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A MICROSOFT CLUSTER. CLICK

System Requirements

Network TCP Port Requirements

License Requirements

Download Software Packages

Before You Begin

Install the software on physical Nodes

Interactive Installation

Configure the Cluster Group Client

Remote Install

Getting Started - Backup Administrator

SKIP THIS PAGE IF YOU ARE NOT INSTALLING ON A UNIX CLIENT.

System Requirements

Download Software Packages

Where to Install

Before You Begin

Installation