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

Transcription

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

2 DB2 DBA Guide Table of Contents Overview System Requirements Getting Started - Backup Administrator Deployment On unix Configuration Getting Started - Database Administrator Prerequisites Configuration Backup Restore Data Retention Published On: 11/19/2013 V10 Service Pack 4A Page 2 of 73

3 Overview - DB2 DBA Overview Deployment - Windows Deployment - Windows Cluster Deployment - Unix Deployment - Unix Cluster Configuration Table of Contents Introduction Key Features Terminology Introduction 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. Key Features The DB2 idataagent offers the following features for database administrators: Ensure a seamless integration with Data Protection Suite's data protection using scripts to automatically configure your database. Perform DB2 commands for backup and restore operations using the load options. Perform backup and restore operations using the DB2 Control Center with vendor options. Schedule backup and restore operations using cron jobs, the DB2 Control Center and Data Protection Suite's CommCell Console. Greater control with new command line tools to query and restore data. 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. 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: Published On: 11/19/2013 V10 Service Pack 4A Page 3 of 73

4 Terminology The following terminology is used in the DB2 idataagent documentation: Client Instance Backupset Subclient The computer in which the idataagent is installed. The client computer contains the data to be secured. The DB2 instance that contains the DB2 databases. The DB2 database to be used for backup and restore operations The DB2 data to be backed up. Back to top Published On: 11/19/2013 V10 Service Pack 4A Page 4 of 73

5 System Requirements - DB2 idataagent System Requirements Supported Features License Requirements The following requirements are for the DB2 idataagent: Application/Operating System Architecture DB2 Universal Database 10.5/10.1/9.7/9.5/ bit on: AIX AIX 5.3*, 6.1, 7.1 *with technology level 6 (or higher) and runtime library xlc.rte 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 or above Red Hat Enterprise Linux 6 with glibc 2.12.x Red Hat Enterprise Linux 5.x with libstdc++ version or above Red Hat Enterprise Linux 5.x with glibc 2.5.x Red Hat Enterprise Linux 4.x with glibc 2.3.x Power PC x64 Power PC x64 x64 Supported only on versions 9.5 and 9.1. Red Hat Enterprise Linux/CentOS Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x x64 x64 SuSE Linux (SLES) SuSE Linux 11.x with glibc 2.9.x and above SuSE Linux 11 Enterprise Server with libstdc++ version or above SuSE Linux 10.x with glibc 2.4.x SuSE Linux 10 Enterprise Server with libstdc++ version or above SuSE Linux 10 Enterprise Server x64 Power PC x64 Power PC s390x 64-bit Z-Linux Red Hat Enterprise Linux Red Hat Enterprise Linux 6.x Red Hat Enterprise Linux 5.x Red Hat Enterprise Linux 4.x s390x 64-bit s390x 64-bit s390x 64-bit Supported only on versions 9.5 and 9.1. Solaris Solaris 11.x x64, Ultra5 or higher recommended Solaris 10.x with a minimum of SunOS (Sparc) Patch 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/ bit on: Linux Red Hat Enterprise Linux Red Hat Enterprise Linux 6.x with libstdc++ version or above Red Hat Enterprise Linux 6 with glibc 2.12.x Red Hat Enterprise Linux 5.x with libstdc++ version or above Red Hat Enterprise Linux 5 with glibc 2.6.x Red Hat Enterprise Linux 4.x with glibc 2.3.x Power PC x86 or compatible processors Power PC x86 or compatible processors x86 or compatible processors Supported only on versions 9.5 and 9.1. SuSE Linux (SLES) Published On: 11/19/2013 V10 Service Pack 4A Page 5 of 73

6 SuSE Linux 11.x with glibc 2.9.x and above SuSE Linux 11 Enterprise Server with libstdc++ version or above SuSE Linux 10.x with glibc 2.4.x SuSE Linux 10 Enterprise Server with libstdc++ version or above x86 or compatible processors Power PC x86 or compatible processors Power PC Windows Windows 2008 Microsoft Windows Server bit Editions Windows 2003 Microsoft Windows Server 2003 Editions with a minimum of Service Pack 2 Cluster - Support 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. Hard Drive 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 MB on Data Protection Suite install path including Job Results 1.97 MB on Job Results MB on Log location with debug Solaris Zones/Containers Support For a comprehensive list of supported components, see Unix Virtualization. AIX LPAR/WPAR Support Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported. Miscellaneous 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: System Requirements - Microsoft Windows File System idataagent System Requirements - AIX File System idataagent System Requirements - HP-UX File System idataagent System Requirements - Linux File System idataagent 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: File Name <directory>/<file_name>.te Content of the File The content of the file should be as follows: Published On: 11/19/2013 V10 Service Pack 4A Page 6 of 73

7 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 <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 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 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) 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) 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 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. libstdc++.so 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. Published On: 11/19/2013 V10 Service Pack 4A Page 7 of 73

8 Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable Published On: 11/19/2013 V10 Service Pack 4A Page 8 of 73

9 Supported Features - DB2 idataagent System Requirements Supported Features License Requirements The following table lists the features that are supported by this Agent. 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 Advanced File System idataagent Options Alerts and Monitoring Automatic Updates Backup/Archive Options Comments Automatic File System Multi-Streaming On Demand Data Protection Operation Restore by Jobs Restore Data Using a Map File Comments Global Alerts Job-Based Alerts* Comments Automatic Updates Comments Differential Backup Full Backup Incremental Backup Other Backup Types Synthetic Full Backup Comments Delta Backup; see Incremental Backups Backward Compatibility Browse Version 8 Version 9 Comments 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 Clustering View All Versions Comments Unix Cluster Windows - Microsoft Cluster (MSCS) Published On: 11/19/2013 V10 Service Pack 4A Page 9 of 73

10 Command Line Interface CommCell Migration Content Indexing Data Aging Windows - Non-Microsoft Cluster Comments Command Line Interface Comments CommCell Migration Comments Offline Content Indexing Comments Basic Retention Rules Deleting a Job Extended Retention Rules Retaining a Job Unique Data Aging Rules Data Compression Comments Client Compression Hardware Compression Extended Retention Rules are supported for offline/online fulls. MediaAgent Compression Data Encryption Comments Data Encryption Support Third-party Command Line Encryption Support Data Multiplexing Deduplication Comments Multiplexing Comments MediaAgent Deduplication Source Deduplication Erase Backup/Archived Data Global Filters Installation Comments Erase Data by Browsing Erase Stubs Comments Global Filters Comments Custom Package Decoupled Install Remote Install Restore Only Agents Silent Install Installing 32-bit Components on a Microsoft Windows x64 Platform Job Restart - Data Protection Comments Install 32-bit On x64 Comments Not Restartable Restarts from the Beginning Restarts from the Beginning of the Database * Job Restart - Data Recovery Restarts from the Point-of-Failure Comments Not Restartable Restarts from the Beginning Restarts from the Beginning of the Database Restarts from the Point-of-Failure Comments List Media Associated with a Specific Backup Set or Third-party command line operations are Not Restartable. * DB2 IntelliSnap backup copy operations can be restartable from the point-of-failure. Published On: 11/19/2013 V10 Service Pack 4A Page 10 of 73

11 List Media Multi Instancing Optimized Scan Pre/Post Processes Restore/Recover/Retrieve Destinations Instance List Media Associated with Index List Media Associated with Specific Files and/or Folders List Media Associated with Specific Jobs Comments Multi Instance Comments Optimized Scan Comments Pre/Post Process with Data Protection and Recovery Comments 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 Out-of-place 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 Restore/Recover/Retrieve Overwrite Options Schedule Policy Comments 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 Agent Specific Data Protection Schedule Policy All Agent Types Schedule Policy Storage Policies Subclient Policies Upgrade Comments Incremental Storage Policy* Standard Storage Policies Comments SubClient Policy Comments Netware - Local Unix - Remote (Push) Unix/Linux - Local Unix/Linux - Silent Unix/Linux/Macintosh - Local Incremental Storage Policy does not support Transaction Log backups for this agent. Unix/Linux/Macintosh - Silent Upgrade from CommCell Console Windows - Local Windows - Remote (Push) Published On: 11/19/2013 V10 Service Pack 4A Page 11 of 73

12 Windows - Silent User Administration and Security Comments Backup Set/Archive Set Instance Subclient Comments Additional features are listed below: Activity Control Auxiliary Copy CommCell Console GridStor Log Files Operation window IntelliSnap Backup VaultTracker Enterprise Cloud Storage Deconfigure/Reconfigure Components Languages MediaAgent Scheduling Snapshot Engines VaultTracker Restore/Recover/Retrieve - Other Options Job Restart - Data Collection Published On: 11/19/2013 V10 Service Pack 4A Page 12 of 73

13 Getting Started - Backup Administrator Overview Deployment - Windows Deployment - Windows Cluster Deployment - Unix Deployment - Unix Cluster Configuration Where to Install 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. Planning Your Installation 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. Before You Begin 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. 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 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 If you are installing the software in a clustered environment, make sure to install the software using the same installation path on Published On: 11/19/2013 V10 Service Pack 4A Page 13 of 73

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. 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. 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. 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. 17. In the Client Group Selection dialog box, select a DB2 Client Group, and then click Next. This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups. 18. In the Global Filter Options dialog box, click Next. This agent does not support Global Filters. 19. In the Policy Selection dialog box, select a storage policy from the Storage Policy list. Click Next. 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 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. If you are installing the software in a clustered environment, ensure that the DB2 Archive path resides on a shared drive. 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. If you are installing the software in a clustered environment, ensure that the DB2 Retrieve path resides on a shared drive. 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. If you are installing the software in a clustered environment, ensure that the DB2 Audit Error Path resides on a shared drive. Published On: 11/19/2013 V10 Service Pack 4A Page 14 of 73

15 23. In the Installer dialog box, click OK. 24. In the Completion Report dialog box, click Reboot Now. 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. 25. To create a storage policy, you must have configured a library in the CommCell. If you do not already have a library configured, go to Disk Library Creation. 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 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. Published On: 11/19/2013 V10 Service Pack 4A Page 15 of 73

16 Default Options Selected During Standard Install Listed below are the default options that are not selected while performing the Standard Install. 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. Components installed by default during Standard Install Listed below are the components that are installed by default while performing the Standard Install: SELECTED PACKAGE COMPONENTS INSTALLED DB2 Agent DB2 idataagent File System Core Windows File System Method 2: Interactive install - Custom 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. Published On: 11/19/2013 V10 Service Pack 4A Page 16 of 73

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 Do not use the following characters when specifying the destination path: / : *? " < > # It is recommended that you use alphanumeric characters only 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. 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. 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. 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. This screen will not appear if the default port numbers are not used for CommCell communication. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 17 of 73

18 Click Next. 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. 18. In the Client Group Selection dialog box, select a DB2 Client Group, and then click Next. This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups. 19. In the Global Filter Options dialog box, click Next. This agent does not support Global Filters. 20. In the Policy Selection dialog box, select a storage policy from the Storage Policy list. Click Next. 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 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. If you are installing the software in a clustered environment, ensure that the DB2 Archive path resides on a shared drive. 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. If you are installing the software in a clustered environment, ensure that the DB2 Retrieve path resides on a shared drive. 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. If you are installing the software in a clustered environment, ensure that the DB2 Audit Error Path resides on a shared drive. 24. In the Installer dialog box, click OK. 25. In the Completion Report dialog box, click Reboot Now. 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. 26. To create a storage policy, you must have configured a library in the CommCell. If you do not already have a library configured, go to Disk Library Creation. 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 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. Published On: 11/19/2013 V10 Service Pack 4A Page 18 of 73

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. Additional Installation Methods 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. Published On: 11/19/2013 V10 Service Pack 4A Page 19 of 73

20 Getting Started - Backup Administrator Overview Deployment - Windows Deployment - Windows Cluster Deployment - Unix Deployment - Unix Cluster Configuration SKIP THIS PAGE IF YOU ARE NOT INSTALLING THIS AGENT ON A MICROSOFT CLUSTER. CLICK DEPLOYMENT. TO CONTINUE WITH THE Steps involved in installing the DB2 idataagent in a Clustered environment: 1. Install the software on physical Nodes 2. Configure the Cluster Group Client Before You Begin System Requirements Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in 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 Download the latest software package to perform the install. 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. 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 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. Published On: 11/19/2013 V10 Service Pack 4A Page 20 of 73

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 Do not use the following characters when specifying the destination path: / : *? " < > # It is recommended that you use alphanumeric characters only In a clustered environment, the software must be installed to the same path on all the nodes. Published On: 11/19/2013 V10 Service Pack 4A Page 21 of 73

22 8. Click Install. The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 22 of 73

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. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 23 of 73

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. 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. 15. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers. Click Next. This screen will not appear if the default port numbers are not used for CommCell communication. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 24 of 73

25 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. 18. Select a Client Group. Click Next. This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups. 19. Click Next. This agent does not support Global Filters. 20. Select a storage policy from the Storage Policy list. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 25 of 73

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. If you are installing the software in a clustered environment, ensure that the DB2 Archive path resides on a shared drive. 22. Enter the DB2 Retrieve Path or click Browse to select a location to store the DB2 retrieve files. If you are installing the software in a clustered environment, ensure that the DB2 Retrieve path resides on a shared drive. 23. Enter the DB2 Audit Error Path or click Browse to select a location to store the Db2 audit error files. If you are installing the software in a clustered environment, ensure that the DB2 Audit Error Path resides on a shared drive. Published On: 11/19/2013 V10 Service Pack 4A Page 26 of 73

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. Published On: 11/19/2013 V10 Service Pack 4A Page 27 of 73

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. 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. The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. 28. Click Finish. This screen may look different from the example shown. Click Reboot Now if it prompts for a reboot. Published On: 11/19/2013 V10 Service Pack 4A Page 28 of 73

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. Configure 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. The Host name of the cluster group client should not be used by any existing client in your CommCell. Host Name is the fully qualified domain name of the cluster group. See the screenshot below for reference. Published On: 11/19/2013 V10 Service Pack 4A Page 29 of 73

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. 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. 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. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 30 of 73

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. Ensure that the Job Results Directory resides on a shared clustered drive. 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. 7. Click OK. The cluster group client is successfully created. Configuring Storage Policy 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. If you do not already have a library configured, go to Disk Library Creation. 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 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. Published On: 11/19/2013 V10 Service Pack 4A Page 31 of 73

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. Additional Installation Methods Remote Install Deploy the software from CommCell Console on multiple clients. Published On: 11/19/2013 V10 Service Pack 4A Page 32 of 73