Administration GUIDE. Sybase idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 176

Transcription

1 Administration GUIDE Sybase idataagent Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 176

2 User Guide - Sybase idataagent Table of Contents Overview Introduction Key Features Terminology System Requirements Getting Started Deployment on windows Remote Install Uning CommCell Console Interactive Install Deployment On unix Remote Install Uning CommCell Console Interactive Install Configuration Backup Restore Advanced Options Configuration Understanding the CommCell Console Managing Sybase Server Manually Creating a Master Database Managing Subclients Configuring User Accounts for Backups Configuring Streams for Backups Configuring Sybase ASE Cluster for a Single Node Modifying an Agent, Instance, or Subclient Deleting an Agent, Instance, or Subclient Backup Full Backups Transaction Log Backups Scheduling a Backup Published On: 11/19/2013 V10 Service Pack 4A Page 2 of 176

3 Managing Jobs Additional Options Browse Data Understanding the Restore Options Window Browse and Restore Latest Data Browse and Restore Data Before a Specified Backup Time Browse and Restore Data Between a Specified Backup Time Browse and Restore from Copies List Media Browse and Restore Using MediaAgent Restore Restoring the Sybase Server Restoring the Master Database Restoring System Databases Restoring Databases to a Point in Time Restoring Transaction Logs to a Point in Time Recovering a Database Restoring a Database to the Current State (Step-by-Step Restore) Renaming a Database Restoring Databases to a New Device Restoring Databases to a Different Sybase Server Instance Restoring the Sybase Server to a Different Path Scheduling a Restore Managing Restore Jobs Additional Restore Options data aging Getting Started Extended Retention Rules Disaster Recovery Planning for a Disaster Recovery Rebuilding the Operating System Restoring the Sybase Server Resolve and Restore Defective Devices and Suspected Databases Additional Operations Audit Trail Auxiliary Copy License Administration Online Help Links Operating System and Application Upgrades Operation Window Published On: 11/19/2013 V10 Service Pack 4A Page 3 of 176

4 Schedule Policy Storage Policy Uninstalling Components Command Line Configuration Backup Restore Best Practices Frequently Asked Questions Troubleshooting Backup Restore Published On: 11/19/2013 V10 Service Pack 4A Page 4 of 176

5 Overview - Sybase idataagent Table of Contents Introduction Key Features Full Range of Backup Options Efficient Job Management and Reporting Backup and Recovery Failovers Block Level Deduplication Terminology Introduction The Sybase idataagent provides an unique, simplified end-to-end backup and recovery solution for Sybase system and user databases in your enterprise. In addition to complete protection of the system databases which contain user database characteristics, file locations etc., it also provides more granular backup and recovery of your enterprise s data, related administration files and transaction logs. Key features Full Range of Backup and Recovery Options The Sybase idataagent provides the flexibility to backup the Sybase server which consists of system and user databases in different environments. This is very essential since the Sybase system and user databases are always subject to constant changes. You can perform a full or transaction log backup of the entire Sybase Server at any point of time. The following section describes the backups that can be performed in different environments. Database Backups You can backup both the system and userdefined databases. You can comprehensively backup all the databases in an instance or schedule backups for the individual databases. You can also autodiscover new databases to comprehensively manage the backup of all databases in your environment. Transaction Log Backups You also have the facility to backup only the transaction logs when the database is online. These logs can be applied to an online backup and recover the database to the current point-in-time. A transaction log backup contains only the new changes since the full or another transaction log backup. Each time a transaction log is backed up it is truncated to the exact time of the backup. No checkpoint is issued at this time, therefore dirty pages are not written to disk before or after a transaction log backup. Any transactions that are not completed at the time a transaction log backup is performed are rolled back during a restore involving a transaction log backup. Transaction Log Backup of a Damaged Database Published On: 11/19/2013 V10 Service Pack 4A Page 5 of 176

6 If a database fails and any data is lost, you will want to restore it to the point of failure. Sybase idataagent allows you to capture all transaction log events that occurred after the last backup job was performed. You can also protect the non-database files and profiles using the appropriate File System idataagent. Backup and Recovery Failovers In the event that a MediaAgent used for the backup or recovery operation fails, it is automatically resumed on alternate MediaAgents. In such cases, the backup or restore job will not restart from the beginning, but will resume from the point of failure. This is especially useful for backups and restores of large amount of data. In the event, that a network goes down, the backup and recovery jobs are resumed on alternate data paths. Similarly, in the event of a device failure, the jobs are automatically switched to alternate disk and tape drives. Efficient Job Management and Reporting You can view and verify the status of backup and recovery operations from the Job Controller and the Event Viewer within the CommCell Console. You can also track the status of the jobs using Reports, which can be saved and distributed. Generate reports for different aspects of data management. Customize the reports to display only the required data and save them to a specific location in different formats. For example, you can create a backup job summary report to view the completed backup jobs. You can schedule, generate and send the Reports via without user intervention. Block Level Deduplication Deduplication provides a smarter way to store data by identifying and eliminating the duplicate items in a data protection operation. Deduplication at the data block level compares blocks of data against each other. If an object (e.g., file, database) contains blocks of data that are identical to each other, then block level deduplication does not store the redundant data, which reduces the size of the object in storage. This reduces the size of the backup data copies on both the disk and tapes. Terminology The Sybase idataagent documentation uses the following terminology: Client Instance Subclient Device The computer in which the idataagent is installed and contains the data to be secured. The Sybase Server to be used for the backup and restore operations. The Sybase databases to be backed up. A physical storage locations in a disk such as a partition that is dedicated to holding the Sybase database. Where to go Next Install the Sybase idataagent Walks you through the process of installing the Sybase idataagent. Back to Top Published On: 11/19/2013 V10 Service Pack 4A Page 6 of 176

7 System Requirements - Sybase idataagent System Requirements Supported Features License Requirements The following requirements are for the Sybase idataagent: Application/Operating System Architecture Sybase ASE bit on: AIX AIX 7.1 Power PC (Includes IBM System p) AIX 6.1 Power PC (Includes IBM System p) HP-UX HP-UX 11i v3 (11.31) Itanium Linux Red Hat Enterprise Linux Red Hat Enterprise Linux 5.5, 5.6, 5.7 and 5.8 Red Hat Enterprise Linux/CentOS Red Hat Enterprise Linux/CentOS 6.x x64 SuSE Linux (SLES) SuSE Linux 11.x with glibc 2.9.x and above SuSE Linux 11.x with glibc 2.6.x Intel Pentium, Itanium, x64 or compatible processors x64 Solaris Solaris 10.x x64 Windows Windows 2008 Microsoft Windows Server 2008 R2 Editions All Windows-compatible processors supported Sybase ASE bit on: Windows Windows 2008 Microsoft Windows Server 2008 R2 Editions All Windows-compatible processors supported Sybase ASE bit on: AIX AIX 7.1 Power PC (Includes IBM System p) AIX 6.1 Power PC (Includes IBM System p) AIX 5.3 with technology level 6 (or higher) and runtime library xlc.rte or higher Power PC (Includes IBM System p) HP-UX HP-UX 11i v3 (11.31) Itanium HP-UX 11i v2 (11.23) Itanium Linux Red Hat Enterprise Linux/CentOS Red Hat Enterprise Linux/CentOS 6.x Red Hat Enterprise Linux/CentOS 5.x Red Hat Enterprise Linux/CentOS 4.x x64 x64 x64 SuSE Linux (SLES) Published On: 11/19/2013 V10 Service Pack 4A Page 7 of 176

8 SuSE Linux 11.x with glibc 2.6.x SuSE Linux 10.x with glibc 2.4.x x64 x64 Solaris Solaris 10.x x64 Windows Windows 2008 Microsoft Windows Server 2008 R2 Editions All Windows-compatible processors supported Sybase ASE bit on: Linux Red Hat Enterprise Linux/CentOS Red Hat Enterprise Linux/CentOS 6.x Red Hat Enterprise Linux/CentOS 5.x Red Hat Enterprise Linux/CentOS 4.x Intel Pentium or compatible processors Intel Pentium or compatible processors Intel Pentium or compatible processors SuSE Linux (SLES) SuSE Linux 11.x with glibc 2.6.x SuSE Linux 10.x with glibc 2.4.x Intel Pentium or compatible processors Intel Pentium or compatible processors Windows Windows 2008 Microsoft Windows Server 2008 R2 Editions All Windows-compatible processors supported Windows 2003 Microsoft Windows Server bit Editions with a minimum of Service Pack 2 All Windows-compatible processors supported Sybase ASE 15.0.x 32-bit/64-bit on: AIX AIX bit Power PC (Includes IBM System p) AIX bit with technology level 6 and runtime library xlc.rte or higher Power PC (Includes IBM System p) HP-UX HP-UX 11i v3 (11.31) Itanium HP-UX 11i v2 (11.23) Itanium Linux Red Hat Enterprise Linux/CentOS Red Hat Enterprise Linux/CentOS 5.x Red Hat Enterprise Linux/CentOS 4.x Intel Pentium, x64 or compatible processors Intel Pentium, x64 or compatible processors SuSE Linux (SLES) SuSE Linux 11.x with glibc 2.6.x SuSE Linux 10.x with glibc 2.4.x Intel Pentium, x64 or compatible processors Intel Pentium, x64 or compatible processors Solaris Solaris 10.x with a minimum of SunOS (Sparc) Patch x64, Sparc T/M series Windows Windows 2008 Microsoft Windows Server 2008 Editions All Windows-compatible processors supported Windows 2003 Microsoft Windows Server 2003 Editions with a minimum of Service Pack 2 All Windows-compatible processors supported Published On: 11/19/2013 V10 Service Pack 4A Page 8 of 176

9 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 674 MB minimum of hard disk space for Data Protection Suite and Job Results 10 MB of additional hard disk space for log file growth 4 KB for Job Results Linux 584 MB minimum of hard disk space for Data Protection Suite and Job Results 1 MB for Job Results Solaris 2.73 GB minimum of hard disk space for Data Protection Suite and Job Results 34 MB for Job Results Solaris Zones/Containers Support Data Protection of data residing on global and non-global zones is supported. For a comprehensive list of supported components, see Unix Virtualization. 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 - AIX File System idataagent System Requirements - HP-UX File System idataagent System Requirements - Linux File System idataagent System Requirements - Solaris File System idataagent 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 where: <directory> is /usr/share/selinux/devel Content of the File The content of the file should be as follows: policy_module(<name>,<version>) ############################## Published On: 11/19/2013 V10 Service Pack 4A Page 9 of 176

10 <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 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]# Published On: 11/19/2013 V10 Service Pack 4A Page 10 of 176

11 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..net Framework.NET Framework 4.0 is automatically installed. Note that.net Framework 4.0 can co-exist with other versions of this software. 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. 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. 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 11 of 176

12 Supported Features - Sybase 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 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* Automatic Updates Backup/Archive Options Comments Automatic Updates Comments Differential Backup Full Backup Backward Compatibility Incremental Backup Other Backup Types Synthetic Full Backup Comments Version 8 Version 9 Transaction Log Do Not Truncate Log Comments Browse from Copy Published On: 11/19/2013 V10 Service Pack 4A Page 12 of 176

13 Browse 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 Clustering Command Line Interface CommCell Migration Content Indexing Data Aging Subclient Browse Use MediaAgent View All Versions Comments Unix Cluster Windows - Microsoft Cluster (MSCS) 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 MediaAgent Compression Data Encryption Data Multiplexing Comments Data Encryption Support Third-party Command Line Encryption Support Comments Multiplexing Comments For Data Multiplexing, Sybase does not support the multiplexing of streams "with each other" on to the same media when a data protection operation is performed using Published On: 11/19/2013 V10 Service Pack 4A Page 13 of 176

14 Deduplication MediaAgent Deduplication Source Deduplication the CommCell Console. However, the streams will be multiplexed when the operation is performed using the Command Line Interface or RMAN commands. 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 Restarts from the Point-of- Failure Comments You cannot restart the jobs on an upgraded CommServe Job Restart - Data Recovery Not Restartable Restarts from the Beginning Restarts from the Beginning of the Database Restarts from the Point-of- Failure Comments You cannot restart the jobs on an upgraded CommServe List Media Multi Instancing Optimized Scan List Media Associated with a Specific Backup Set or 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 Ensure that there is no overlapping subclient content across instances before commencing data protection operations. If there is an overlap of subclient content, data loss may occur. Published On: 11/19/2013 V10 Service Pack 4A Page 14 of 176

15 Pre/Post Processes Restore/Recover/Retrieve Destinations Restore/Recover/Retrieve Options 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 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 See Advanced Restore for this idataagent. Restore/Recover/Retrieve Overwrite Options Schedule Policy Storage Policies Skip Errors and Continue Use Exact Index Use MediaAgent 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 Comments Incremental Storage Policy* Standard Storage Policies Subclient Policies Comments SubClient Policy Comments Published On: 11/19/2013 V10 Service Pack 4A Page 15 of 176

16 Upgrade User Administration and Security 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 Windows - Remote (Push) Windows - Silent 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 16 of 176

17 Getting Started - Sybase idataagent Deployment - Windows Deployment - Unix Deployment - Cluster Configuration Backup Restore Where to Install Install the software on a Windows computer on which the Sybase server resides. In a clustered environment, install the software on the physical computer. The computer will be added as a client in the CommCell as soon as the installation completes successfully. Planning Your Installation The software installation may require a system reboot if a pending rename operation from a previously installed application is found in the operating system, 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: Remote Install Using CommCell Console Use this procedure to install remotely on a client computer. Method 2: Interactive Install Use this procedure to install the software by specifying installation settings and options. Method 1: Remote Install Using CommCell Console 1. Open CommCell Console: Click Start and point to All Programs. Click HDPS. Click Backup and Recovery Administrative Console. 2. From the CommCell Browser, click Tools Add/Remove Software Install Software. Published On: 11/19/2013 V10 Service Pack 4A Page 17 of 176

18 3. Click Next. 4. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 18 of 176

19 5. Click Manually Select Computers. Click Next. 6. Enter the fully qualified domain name of the client computer. For example: mycomputer.mydomain.mycompany.com Click Next. Do not use space and the following characters when specifying the Host Name: \ `~!_@#$%^&*()+=<>/?,[]{}:;'" Published On: 11/19/2013 V10 Service Pack 4A Page 19 of 176

20 7. Choose one of the following: Click Next if you want to use the default cache location Click Override Software Cache and specify a new location in the Software Cache box and then click Next The software cache is the location from where the remote install program installs the software. This screen will not appear if the remote cache is not configured. For more information, see Managing Cache - Remote Cache. 8. Specify the User Name and Password that must be used to access the client computer, and then click Next. The user must be an Administrator or a member of the Administrator group on that computer. Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on that client, click Next without specifying the account information. Published On: 11/19/2013 V10 Service Pack 4A Page 20 of 176

21 9. Click Sybase under Databases. Click Next. 10. Select the following: Select a client group from the available Client Groups, and then click Add. From the Global Filters list, select one of the following: Use Cell level Policy to inherit the global filter policy configuration set for the CommCell. Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell. Do not use Global Filters if you plan to define specific filters for the Agent. From the Storage Policy To Use list, select a storage policy. 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. If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 19. Published On: 11/19/2013 V10 Service Pack 4A Page 21 of 176

22 11. Specify the Sybase ASE Library Path and then click Next. 12. Click Next. If necessary you can select additional options. Click the Help button to get more information on the available options. Published On: 11/19/2013 V10 Service Pack 4A Page 22 of 176

23 13. Click Next. If necessary you can select optional settings. Click the Help button to get more information on the available options. 14. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 23 of 176

24 15. Select Immediate. Click Next. 16. Click Finish. This screen will reflect the components you selected for install, and may look different from the example shown. Published On: 11/19/2013 V10 Service Pack 4A Page 24 of 176

25 17. You can track the progress of the job from the Job Controller window of the CommCell console. From the Home menu, click Job Controller. Once the job is complete, view the job details from the Admin Job History. Right-click the <CommServe>, point to View and then click Admin Job History. Click Select Install/Upgrade/Remove/Repair Software. Click OK. Published On: 11/19/2013 V10 Service Pack 4A Page 25 of 176

26 You can view the following by right-clicking the job: Details of the job Option to Resubmit the job Events associated with the job Logs associated with the job Option to send the Logs associated with the job 18. If you have installed on a clustered computer, make sure to install the software on all the physical nodes and then follow the steps described in Cluster Configuration. 19. 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 folder. button to select the 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. Published On: 11/19/2013 V10 Service Pack 4A Page 26 of 176

27 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. 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. Method 2: Interactive 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. Click I accept the terms in the license agreement. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 27 of 176

28 4. Click Custom. Click Next. 5. Click Select components to install on this computer and click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 28 of 176

29 6. Expand Database, and then click Sybase. 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 Published On: 11/19/2013 V10 Service Pack 4A Page 29 of 176

30 8. Click Browse to select the Sybase ASE Library Path. The Sybase ASE (Adaptive Server Enterprise) server library is generally located under the Sybase ASE server install directory. Click Next. 9. Click Install. The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. Published On: 11/19/2013 V10 Service Pack 4A Page 30 of 176

31 10. Click Yes. 11. Click Next. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 31 of 176

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

33 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. You will get this screen if you did not configure the firewall settings in step 11. Published On: 11/19/2013 V10 Service Pack 4A Page 33 of 176

34 17. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion 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. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 34 of 176

35 19. Click Next. This agent does not support Global Filters. 20. Select a storage policy from the Storage Policy list. Click Next. If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 23. Published On: 11/19/2013 V10 Service Pack 4A Page 35 of 176

36 21. Click OK. 22. Click Reboot Now. This screen will reflect the components you selected for install, and may look different from the example shown. If you already have a storage policy selected in step 18, click to proceed to the Configuration section. If you do not have Storage Policy created, continue with the following step. 23. 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... Published On: 11/19/2013 V10 Service Pack 4A Page 36 of 176

37 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 folder. button to select the 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 37 of 176

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

39 Getting Started - Sybase idataagent Deployment - Windows Deployment - Unix Deployment - Cluster Configuration Backup Restore Where to Install Install the software on a UNIX computer on which the Sybase server resides. For Solaris, software can be installed on one of the following: Unix computer hosting the global zone on which Sybase server resides, and satisfies the minimum requirements specified in the System Requirements. Unix computer in a non global zone on which Sybase server resides, and satisfies the minimum requirements specified in the system requirements. In a clustered environment, install the software on the physical computer. The computer will be added as a client in the CommCell as soon as the installation completes successfully. 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: Remote Install Using CommCell Console Use this procedure to install remotely on a client computer. Method 2: Interactive Install Use this procedure to install the software using the custom installation options. Method 1: Remote Install Using CommCell Console 1. Open CommCell Console: Click Start and point to All Programs. Click HDPS. Click Backup and Recovery Administrative Console. 2. From the CommCell Browser, click Tools Add/Remove Software Install Software. Published On: 11/19/2013 V10 Service Pack 4A Page 39 of 176

40 3. Click Next. 4. Select Unix and Linux. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 40 of 176

41 5. Click Manually Select Computers. Click Next. 6. Enter the fully qualified domain name of the client computer. For example: mycomputer.mydomain.mycompany.com Click Next. Do not use space and the following characters when specifying the Host Name: \ `~!_@#$%^&*()+=<>/?,[]{}:;'" Published On: 11/19/2013 V10 Service Pack 4A Page 41 of 176

42 7. Choose one of the following: Click Next if you want to use the default cache location Click Override Software Cache and specify a new location in the Software Cache box and then click Next The software cache is the location from where the remote install program installs the software. This screen will not appear if the remote cache is not configured. For more information, see Managing Cache - Remote Cache. 8. Specify the User Name and Password that must be used to access the client computer, and then click Next. You can also specify the SUDO user credentials here, provided that the user is an Administrator or a member of the Administrator group with root privileges on that computer. For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install. Account information is required while performing remote installs for the first time on a client. For subsequent remote installs on that client, click Next without specifying the account information. Published On: 11/19/2013 V10 Service Pack 4A Page 42 of 176

43 9. Click Sybase. Click Next. 10. Select the following: Select a client group from the available Client Groups, and then click Add. From the Global Filters list, select one of the following: Use Cell level Policy to inherit the global filter policy configuration set for the CommCell. Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell. Do not use Global Filters if you plan to define specific filters for the Agent. From the Storage Policy To Use list, select a storage policy. 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. If you do not have a Storage Policy, the list will not be displayed. You can create the Storage Policy later in step 20. Published On: 11/19/2013 V10 Service Pack 4A Page 43 of 176

44 11. Specify the Sybase ASE Library Path and then click Next. 12. Click Next. If necessary you can select additional options. Click the Help button to get more information on the available options. Published On: 11/19/2013 V10 Service Pack 4A Page 44 of 176

45 13. Specify a name for the Unix Group and click Next. If necessary you can select advanced options. Click the Help button to get more information on the available options. 14. Click Next. If necessary you can select additional options. Click the Help button to get more information on the available options. Published On: 11/19/2013 V10 Service Pack 4A Page 45 of 176

46 15. 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. 16. Select Immediate. Click Next. Published On: 11/19/2013 V10 Service Pack 4A Page 46 of 176

47 17. Click Finish. This screen will reflect the components you selected for install, and may look different from the example shown. 18. You can track the progress of the job from the Job Controller window of the CommCell console. From the Home menu, click Job Controller. Once the job is complete, view the job details from the Admin Job History. Right-click the <CommServe>, point to View and then click Admin Job History. Click Select Install/Upgrade/Remove/Repair Software. Click OK. Published On: 11/19/2013 V10 Service Pack 4A Page 47 of 176

48 You can view the following by right-clicking the job: Details of the job Option to Resubmit the job Events associated with the job Logs associated with the job Option to send the Logs associated with the job 19. If you have installed on a clustered computer, make sure to install the software on all the physical nodes and then follow the steps described in Cluster Configuration. 20. 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: Published On: 11/19/2013 V10 Service Pack 4A Page 48 of 176

49 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 folder. button to select the 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. 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. Published On: 11/19/2013 V10 Service Pack 4A Page 49 of 176

50 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. Method 2: Interactive Install 1. Logon to the client computer as root. 2. If you are installing the software from the Software Installation Discs, run the following command to mount the CD: mount -t iso9660,udf /dev/cdrom /mnt/cdrom Run the following command from the Software Installation Package or mount point:./cvpkgadd You can also run this command as a SUDO user with root privileges:./sudo cvpkgadd 3. Press Enter. For steps to add a SUDO user to /etc/sudoers, see Frequently Asked Questions - Install. Selecting Setup Type Please select how you want to perform the setup. 1) CUSTOM - I want to answer all questions interactively 2) QUICK - I just want to answer a few key questions 3) AUTOMATIC - Let the setup decide on everything 4) MY WAY - Please use my prepared answers in /etc/play.xml 5) Exit Published On: 11/19/2013 V10 Service Pack 4A Page 50 of 176

51 I want setup in this way: [1] 4. The product banner and other information is displayed. Press Enter. 5. Read the license agreement. Type y and press Enter. 6. Press Enter. 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] 7. 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. The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown. 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] 8. 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. Setting Client Name 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] 9. Type the number associated with the Sybase idataagent and press Enter. Selecting Modules to Install. Published On: 11/19/2013 V10 Service Pack 4A Page 51 of 176