Symantec NetBackup PureDisk Deduplication Option Guide

Transcription

1 Symantec NetBackup PureDisk Deduplication Option Guide Windows, Linux, and UNIX Release Revision 1

2 The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: Legal Notice Copyright 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, the Checkmark Logo and are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Symantec Corporation 350 Ellis Street Mountain View, CA Printed in the United States of America

4 Technical Support Contacting Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s support offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services For information about Symantec s support offerings, you can visit our website at the following URL: All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Customers with a current support agreement may access Technical Support information at the following URL: Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: Product release level

5 Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration Customer service If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Customer service information is available at the following URL: Customer Service is available to assist with non-technical questions, such as the following types of issues: Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs, DVDs, or manuals

6 Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America

7 Contents Technical Support... 4 Chapter 1 Overview About the NetBackup PureDisk Deduplication Option (PDDO) PDDO configuration examples About improvements to the synthetic backup process Chapter 2 Downloading the PDDO plug-in About downloading the PDDO plug-in Verifying your environment Verifying or installing the PDDO license on a NetBackup master server Downloading the PDDO plug-in to a media server Chapter 3 Chapter 4 Installing the PDDO plug-in on Linux and UNIX media servers About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool Installing the PDDO plug-in on Windows media servers About installing the PDDO plug-in on a Windows media server Performing an attended installation of the PDDO plug-in on a Windows media server Performing an unattended installation of the PDDO plug-in on a Windows media server... 35

8 8 Contents Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool Chapter 5 Configuring the PDDO plug-in in NetBackup Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface Verifying the NetBackup configuration and creating a NetBackup policy Configuring the PDDO plug-in for NetBackup optimized synthetic full backups Chapter 6 Using PureDisk as a NetBackup storage unit About the PDDO plug-in in the PureDisk administrative Web UI Adding an additional PureDisk storage pool to a NetBackup media server About configuring NetBackup lifecycle policies Disaster recovery configuration example About PureDisk garbage collection policies Retrieving job reports About job details reports About data mining reports About central reporting Displaying the agent dashboard About recovery of a PureDisk storage pool used as a PDDO plug-in Changing the storage pool authority password when PDDO is enabled About throttling PDDO replication and duplication jobs About reporting PureDisk resource usage to NetBackup Chapter 7 Seeding PDDO backups About seeding Configuring client seeding Configuring storage server seeding... 73

9 Contents 9 Appendix A Installing the PDDO plug-in on a clustered NetBackup media server Installing the PDDO plug-in on a clustered NetBackup media server Appendix B Repairing and removing a PDDO plug-in Repairing a PDDO plug-in on a Linux or UNIX media server Repairing a PDDO plug-in on a Windows media server About removing a PDDO plug-in Disconnecting the PureDisk storage pool from one media server that exists among many media servers Disconnecting the PureDisk storage pool from the last media server and removing the PureDisk storage pool from the NetBackup environment Removing a PDDO plug-in from a Linux or UNIX media server Removing a PDDO plug-in from a Windows media server Removing PDDO from the NetBackup catalog Appendix C Configuration file settings About the pd.conf file Editing the pd.conf file About pd.conf file settings About BANDWIDTH_LIMIT About OPTDUP_BANDWIDTH About bandwidthlimit About limiting bandwidth within a PureDisk environment About compression and encryption of backup images About compression and encryption of optimized duplicated data About log information About log information from NetBackup About log information from NetBackup or NetBackup Appendix D Troubleshooting Troubleshooting a failed PDDO configuration

10 10 Contents Appendix E Third-party legal notices Third-party legal notices for the Symantec NetBackup PureDisk product family Third-party trademarks for the Symantec NetBackup PureDisk product family Index Glossary

11 Chapter 1 Overview This chapter includes the following topics: About the NetBackup PureDisk Deduplication Option (PDDO) About improvements to the synthetic backup process About the NetBackup PureDisk Deduplication Option (PDDO) The NetBackup PureDisk Deduplication Option (PDDO) is a plug-in that uses the NetBackup OpenStorage API to enable NetBackup to write backups to a PureDisk storage pool. All the data that is written to a PureDisk storage pool is deduplicated. In general, deduplication is a method of retaining only one unique instance of backup data on storage media. Redundant data is replaced with a pointer to the unique data copy. Deduplication significantly reduces the amount of storage space for the NetBackup backup copies. All data that a PDDO agent or that a PureDisk backup client writes to a PureDisk storage pool are deduplicated. When two or more files share identical content, PureDisk breaks the files into segments and stores only one copy of each unique file segment. The following figure shows how deduplication works.

12 12 Overview About the NetBackup PureDisk Deduplication Option (PDDO) Figure 1-1 Client files to be backed up A File deduplication File 1 File 2 B C D E A B Q D L A B C D E Q L Data written to content routers Note the following in this figure: PureDisk breaks file 1 into segments A, B, C, D, and E. PureDisk breaks file 2 into segments A, B, Q, D, and L. PureDisk writes file segments A, B, C, D, and E from file 1, and file segments Q, and L from file 2 on its content routers only one time. PureDisk does not write file segments A, B, and D from file 2 to the content routers. Instead, PureDisk points to the unique data copies of file segments A, B, and D that were already written to the content routers from file 1. Note: When using PDDO to deduplicate database backups (Oracle, MS SQL, and MS Exchange), snapshot-based backups deduplicate better than stream-based backups. Before you install and implement the NetBackup PureDisk Deduplication Option, make sure that the following conditions are true: The PureDisk storage pool software is configured and functions normally. The NetBackup media server is configured and functions normally. You are familiar with the concepts and procedures that are described in the NetBackup AdvancedDisk Storage Solutions Guide, the Symantec NetBackup OpenStorage Solutions Guide for Disk, and your NetBackup administrator s guides. After you install a PureDisk storage pool, you can download the PureDisk agent software to a computer. Next you can configure it to assume one of the following roles: A backup and restore agent.

13 Overview About the NetBackup PureDisk Deduplication Option (PDDO) 13 You can configure a backup and restore agent on any client that PureDisk supports. The Symantec Technical Support compatibility matrix explains the platforms upon which you can configure a PureDisk backup and restore client. A PDDO plug-in. You can configure a PDDO plug-in on a NetBackup media server. The NetBackup media server can be a Linux, Solaris SPARC, IBM AIX, or Windows platform computer. After you configure the plug-in, the media server can use the PureDisk storage pool as a NetBackup OpenStorage disk pool. When you download the PureDisk agent software onto a NetBackup media server, the agent software detects the media server software. It issues the installation prompts that let you configure the agent as a PDDO plug-in. Make sure that you configure the media server software before you download the PureDisk agent software to the media server. See PDDO configuration examples on page 13. PDDO configuration examples The following examples describe PureDisk and NetBackup configurations. The examples do not show any PureDisk backup and restore clients as being directly attached to PureDisk. However, PureDisk can act both as a storage unit to NetBackup and as a backup repository for its own PureDisk clients. When the storage pools fill up, you can add additional content routers to hold additional backup data from NetBackup and from the PureDisk clients. Example 1: Deduplication See Example 1: Deduplication on page 13. Example 2: Multistreaming See Example 2: Multistreaming on page 14. Example 3: Replication See Example 3: Replication on page 15. Example 1: Deduplication Two NetBackup environments with the PDDO plug-in each backup two clients. NetBackup then sends backup data to the PureDisk storage pool for deduplication. The PureDisk storage pool also deduplicates the data from its client. The following figure shows how the PDDO plug-in works in this scenario to deduplicate data.

14 14 Overview About the NetBackup PureDisk Deduplication Option (PDDO) Figure 1-2 Deduplication NetBackup Client PureDisk Client NetBackup Client NetBackup Media Server + PDDO Deduplication Deduplication NetBackup Client Deduplication NetBackup Client NetBackup Media Server + PDDO PureDisk storage pool See PDDO configuration examples on page 13. Example 2: Multistreaming The NetBackup policy defines multiple data streams from the client to the NetBackup media server. NetBackup sends data to the PureDisk storage pool in multiple streams. The following figure shows how NetBackup multistreaming works in an environment that includes both NetBackup and PureDisk.

15 Overview About the NetBackup PureDisk Deduplication Option (PDDO) 15 Figure 1-3 Multistreaming NetBackup Client NetBackup Media Server + PDDO PureDisk storage pool See PDDO configuration examples on page 13. Example 3: Replication PureDisk s replication feature is similar to NetBackup s optimized duplication feature. Replication gives you more options if you need to restore data because you can restore from either storage pool. You can replicate the data from a given PureDisk storage pool to another PureDisk storage pool with one of the following features: PureDisk replication NetBackup optimized duplication Both features transfer only the changed data segments directly between the PureDisk storage pools. NetBackup media servers can restore data from either storage pool. When you replicate data between storage pools, you create a very efficient data transfer environment for disaster recovery scenarios. NetBackup does not keep track of PureDisk replicated images. Images can be imported into NetBackup. If you use optimized deduplication, the media server must be registered with both storage pools. The following figure shows how you can use PureDisk s replication feature with PDDO when you have two PureDisk storage pools.

16 16 Overview About improvements to the synthetic backup process Figure 1-4 Replication Restore Restore PureDisk storage pool NetBackup Client Backup NetBackup Media Server + PDDO Replication (Optimized duplication) Backup PureDisk storage pool See PDDO configuration examples on page 13. About improvements to the synthetic backup process Starting with PureDisk 6.6 and NetBackup 6.5.4, the process for creating synthetic backups is improved. The new process for creating optimized synthetic full backups is through the manipulation of NetBackup catalog metadata and PDDO data

17 Overview About improvements to the synthetic backup process 17 segment pointers. Only the metadata and pointers are manipulated. In the new optimized synthetic backup process, the backup image data is not read from disk, transported across the network, or manipulated. Using the new optimized synthetic full backup process allows the creation of full backups with a significant performance improvement. The optimized synthetic backup is then stored on a PDDO storage unit as an ordered collection of data segments representing a new full backup. The benefit of the optimized synthetic full backup is the ability to run a single full backup, and then only incremental backups from that point forward. Ongoing NetBackup incremental backups of only new or modified data allows users to quickly create a new full backup, at any point in time, by performing an optimized synthetic full backup. See About the NetBackup PureDisk Deduplication Option (PDDO) on page 11.

18 18 Overview About improvements to the synthetic backup process

19 Chapter 2 Downloading the PDDO plug-in This chapter includes the following topics: About downloading the PDDO plug-in Verifying your environment Verifying or installing the PDDO license on a NetBackup master server Downloading the PDDO plug-in to a media server About downloading the PDDO plug-in The PDDO plug-in software is available as a link from the storage pool authority landing page. The download process includes system verification steps and the actual download steps themselves. To download the PDDO plug-in 1 Verify your environment. See Verifying your environment on page Verify or install the PDDO license on a NetBackup master server. See Verifying or installing the PDDO license on a NetBackup master server on page Download the plug-in to a media server. See Downloading the PDDO plug-in to a media server on page 22.

20 20 Downloading the PDDO plug-in Verifying your environment Verifying your environment Before you download or install the PDDO plug-in, perform the following procedure. To verify your environment 1 Verify that NetBackup 6.5 or later is installed and configured on the media server that you want to use. To verify your release level, perform the following steps: Logon to the NetBackup Administration Console. Click Help. Click About NetBackup Administration Console. Visually inspect the number to the right of Version. Make sure that you can perform backups and restores with NetBackup. For information about how to configure NetBackup, see your NetBackup installation documentation. 2 Verify that the NetBackup media server upon which you want to install the PDDO client is a good candidate for this purpose. The hardware must be suited for both I/O and for computation. PDDO increases the computational load on a media server because it calculates data deduplication. Verify your media server s hardware capabilities to ensure an optimal PDDO configuration. 3 Verify that the PureDisk storage pool is configured and operational. The NetBackup interface refers to the PureDisk storage pool as a "storage server." Make sure that you can perform regular file backups from a client and restores to a client. Install a regular PureDisk backup and restore agent on a client computer to perform this test. Do not install the regular backup and restore client on the media server. Symantec does not support both a backup and restore client and a PDDO plug-in on one NetBackup media server. Information about how to install a PureDisk backup and restore client is available. See the PureDisk Client Installation Guide. 4 Verify or install the PDDO license. See Verifying or installing the PDDO license on a NetBackup master server on page 21.

21 Downloading the PDDO plug-in Verifying or installing the PDDO license on a NetBackup master server 21 Verifying or installing the PDDO license on a NetBackup master server The PDDO plug-in is a licensed NetBackup feature. Make sure that you have a PDDO license from your Symantec sales representative. The following procedure explains how to verify your NetBackup licenses and how to install the PDDO license if necessary. To verify or install the PDDO license on a NetBackup master server 1 Start the NetBackup Administration Console. 2 Click Help > License Keys. 3 If PureDisk Option is present in the Features column of the display, do not complete this procedure. Instead, download the PDDO plug-in. See Downloading the PDDO plug-in to a media server on page If PureDisk Option is not present in the Features column of the display, click the yellow star icon. 5 On the Add a New License Key pop-up window, type the PDDO license key you received from your Symantec sales representative. 6 Click Add (Windows interface) or OK (Java interface). 7 Make sure that the PureDisk Option license key appears in the display. 8 On the Add a New License Key pop-up window, type the Enterprise Disk license key you received from your Symantec sales representative. 9 Click Add (Windows interface) or OK (Java interface). 10 Make sure that the Enterprise Disk license key appears in the display. 11 Click Close. 12 Restart NetBackup s services. This task differs depending on your platform. For information about how to restart services, see your NetBackup documentation. 13 Download the PDDO plug-in. See Downloading the PDDO plug-in to a media server on page 22.

22 22 Downloading the PDDO plug-in Downloading the PDDO plug-in to a media server Downloading the PDDO plug-in to a media server The following procedure describes how to download the PDDO plug-in to a media server. To download the PDDO plug-in to a media server 1 Logon to the media server that you want to configure. Symantec supports the following media server platforms: Linux Solaris SPARC Solaris x64 IBM 32-bit AIX IBM 64-bit AIX Windows For more information about specific platform operating systems supported, see the NetBackup Operating System Compatibility List.

23 Downloading the PDDO plug-in Downloading the PDDO plug-in to a media server On the media server, open a browser window and type the following URL in the Address field: For URL, specify the URL to the storage pool authority. For example, in an all-in-one environment, it is the URL of the PureDisk node upon which you installed the PureDisk software. The following figure shows how the PureDisk opening page appears in your browser. 3 Under Downloads, select the correct OS type from the drop-down. 4 Right-click one of the agent links that describes the media server platform. The browser writes the agent software to the location you specify, as in the following examples: On Windows platforms, you can write the software to C:\temp or to the desktop. On Linux or UNIX platforms, you select the download directory. 5 Select one of the following links: pdagent-linux_2.6_x xxxx.run is for Linux media servers. pdagent-solaris_10_sparc xxxx.run is for Solaris SPARC 10 media servers.

24 24 Downloading the PDDO plug-in Downloading the PDDO plug-in to a media server pdagent-solaris_8_sparc xxxx.run is for Solaris SPARC 8 or 9 media servers. pdagent-solaris_10_x xxxx.run is for Solaris 10 x64 media servers. pdagent-aix_5.2_powerpc_x xxxx.run is for AIX 32-bit media servers pdagent-aix_5.3_powerpc_x xxxx.run is for AIX 64-bit media servers pdagent-windows_x xxxx.exe is for Windows 32-bit media servers. pdagent-windows_x86_ xxxx.exe is for Windows 64-bit media servers. To determine the type of hardware on your Windows system, right-click My Computer on the desktop. Select Properties. 6 Install the PDDO plug-in on your media server. For Linux or UNIX media servers: See About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server on page 25. For Windows media servers: See Performing an attended installation of the PDDO plug-in on a Windows media server on page 34.

25 Chapter 3 Installing the PDDO plug-in on Linux and UNIX media servers This chapter includes the following topics: About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server You can install the PDDO plug-in on a Linux media server or on a UNIX media server. Symantec supports both an attended, menu-driven installation method and an unattended, command-driven installation method. After you install the plug-in, you need to establish a connection between the NetBackup media server and the PureDisk storage pool. To install the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server 1 Install the plug-in.

26 26 Installing the PDDO plug-in on Linux and UNIX media servers Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server Use one of the following methods: Attended method. Use this method to use the interactive installation script to install the PDDO plug-in on a media server. See Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server on page 26. Unattended method. Use this method to install the PDDO plug-in on a media server without user intervention. See Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server on page Establish a connection between the media server and the storage pool. See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29. Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server The following procedure explains how to use the PDDO plug-in interactive installation script. Note: Complete the entire PDDO installation and configuration process in one step. Do not install NetBackup software during the PDDO installation or configuration process. You can install NetBackup patches or upgrades after you configure the PDDO plug-in in NetBackup.

27 Installing the PDDO plug-in on Linux and UNIX media servers Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server 27 To install the PDDO plug-in on a Linux or UNIX media server by using an attended install 1 Use the cd(1) command to change to the directory to which you downloaded the software. 2 Run the installation command. The installation command that you run depends on the media server s platform, as follows: # sh pdagent-linux_2.6_x xxxx.run # sh pdagent-solaris_10_sparc xxxx.run # sh pdagent-solaris_8_sparc xxxx.run # sh pdagent-solaris_10_x xxxx.run # sh pdagent-aix_5.2_powerpc_x xxxx.run # sh pdagent-aix_5.3_powerpc_x xxxx.run For XXXX, substitute the build number that appears in your PureDisk opening page. 3 Type Y or y to confirm that you want to install the PDDO plug-in in response to the following prompt: => Do you want to install PDDO plug-in? [y/n] 4 Type the name of the directory into which you want to install the plug-in in response to the following prompt: => Where do you want to install PDDO plug-in? [/opt]: To accept the default directory of /opt, press Enter. 5 Type Y or y to confirm the installation directory in response to the following prompt: => Are you sure you want to install it in /opt? [y/n] 6 Monitor the output to ensure that the software installation completes. 7 (Conditional) Start NetBackup s services. Perform this step if NetBackup s services are not running. For information about how to start services, see your NetBackup documentation. 8 Establish a connection between the media server and the storage pool. See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29.

28 28 Installing the PDDO plug-in on Linux and UNIX media servers Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server To install the PDDO plug-in on a client with a minimum of user intervention, use an unattended, or silent, install. Note: Complete the entire PDDO installation and configuration process in one step. Do not install NetBackup software during the PDDO installation or configuration process. You can install NetBackup patches, upgrades, or releases after you configure the PDDO plug-in in NetBackup. To install the PDDO plug-in on a Linux or UNIX media server by using an unattended install 1 Use the cd(1) command to change to the directory to which you installed the software. 2 Run the installation command that corresponds to the client s platform, as follows: # sh pdagent-linux_2.6_x xxxx.run params # sh pdagent-solaris_10_sparc xxxx.run params # sh pdagent-solaris_8_sparc xxxx.run params # sh pdagent-solaris_10_x xxxx.run params # sh pdagent-aix_5.2_powerpc_x xxxx.run params # sh pdagent-aix_5.3_powerpc_x xxxx.run params The parameters are as follows: --silent Performs the following actions: Answers all installer questions rather than by prompting for input. Prompts you one time for information about an omitted parameter. If you provide an invalid answer, the installer exits. --nbpddo --path=path Specifies that you want to install the NetBackup PureDisk Deduplication Option plug-in. (Optional) Specifies the installation directory. Default is /opt. Note the following:

29 Installing the PDDO plug-in on Linux and UNIX media servers Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool 29 Use pdagent-solaris_8_sparc xxxx.run for both Solaris 9 and 8 operating systems. XXXX is the build number that appears in your PureDisk opening page. The following example shows a Linux installation command with all possible parameters: # sh pdagent-linux_2.6_x xxxx.run --silent --nbpddo --path=/opt/myspa 3 (Conditional) Start NetBackup s services. Perform this step if NetBackup s services are not running. For information about how to start services, see your NetBackup documentation. 4 Establish a connection between the media server and the storage pool. See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29. Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool This topic explains how to configure the PDDO plug-in on the media server, point the media server to a PureDisk storage pool, and create the PureDisk storage server. After you perform this procedure, the software initiates the following activities: Activates the PDDO plug-in as a client to the storage pool Registers the media server as a client to the storage pool Creates a PureDisk PDDO data selection Note: Do not delete the PDDO data selection. If you delete and then want to recreate this data selection, you need to reinstall the PDDO plug-in. You cannot recreate this data selection from the PureDisk administrative Web UI.

30 30 Installing the PDDO plug-in on Linux and UNIX media servers Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool To establish the PDDO connection between a UNIX NetBackup media server and the PureDisk storage pool 1 Change to the PDDO plug-in s bin directory. For example: # cd /install_directory/pdag/bin For install_directory, specify the directory in which you installed the PDDO plug-in. The default is /opt. 2 Type the following command to make NetBackup aware of the PureDisk storage pool and aware of the PDDO plug-in on the media server: # sh./pddocfg.sh --addspa --mediaserver=ms_addr --storageserver=spa_addr The arguments to this command are as follows: ms_addr Specifies the media server s FQDN, host name, or IP address. Symantec recommends that you type the full FQDN of the media server. For example, acctms.acme.com. spa_addr Specifies the PureDisk storage pool authority s FQDN (recommended), host name, or IP address. The storage pool authority identifies itself with this address. You also enter this address in a browser window to logon to the storage pool authority. If the storage pool authority is clustered, type the service FQDN, service host name, or service IP address. 3 Type the storage pool authority administrator s user ID in response to the following prompt: Enter the Storage Pool Authority administrator's user ID > For example: Enter the Storage Pool Authority administrator's user ID > root 4 Type the storage pool authority administrator s password in response to the following prompt: Enter the Storage Pool Authority administrator s password > PureDisk does not modify this password. It uses this password only to register the PDDO plug-in.

31 Installing the PDDO plug-in on Linux and UNIX media servers Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool 31 5 Retype the password for the storage pool authority in response to the following prompt: Retype password > 6 Examine the configuration messages. A successful configuration generates messages similar to the following: Storage server acme.com has been successfully created. pddocfg: INFO "nbdevconfig.exe -creatests" completed successfully pddocfg: INFO "tpconfig.exe -add" completed successfully pddocfg: INFO pddocfg completed successfully 7 Logon to the PureDisk administrative Web UI and click Manage > Agent. 8 In the left pane, verify that the PureDisk media server appears as a client in the PureDisk administrative Web UI. The following figure shows a department that is named Unknowndepartment with one client: PDDO. The PDDO data selection appears underneath the PDDO client. If that is the second media server to run the script, run the following command to confirm communication between NetBackup and PureDisk: bpstsinfo -si -sp PureDisk: -sn storage_pool_hostname 9 Proceed to the following section to configure the plug-in: See Configuring the PDDO plug-in in NetBackup on page 43.

32 32 Installing the PDDO plug-in on Linux and UNIX media servers Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool

33 Chapter 4 Installing the PDDO plug-in on Windows media servers This chapter includes the following topics: About installing the PDDO plug-in on a Windows media server Performing an attended installation of the PDDO plug-in on a Windows media server Performing an unattended installation of the PDDO plug-in on a Windows media server Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool About installing the PDDO plug-in on a Windows media server You can install the PDDO plug-in on a Windows media server. Symantec supports an attended, menu-driven installation method. After you install the plug-in, you need to establish a connection between the NetBackup media server and the PureDisk storage pool.

34 34 Installing the PDDO plug-in on Windows media servers Performing an attended installation of the PDDO plug-in on a Windows media server To install the PDDO plug-in on a NetBackup Windows media server 1 Install the plug-in. See Performing an attended installation of the PDDO plug-in on a Windows media server on page Establish a connection between the media server and the storage pool. See Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool on page 37. Performing an attended installation of the PDDO plug-in on a Windows media server The following procedure explains how to install the PDDO plug-in on a Windows media server using the installation wizard. Note: Complete the entire PDDO installation and configuration process in one step. Do not install NetBackup software during the PDDO installation or configuration process. You can install NetBackup patches or upgrades after you configure the PDDO plug-in in NetBackup. To install PDDO plug-in on a Windows media server by using an attended install 1 To start the installation wizard, click pdagent-windows_x xxxx.exe or pdagent-windows_x86_ xxxx.exe as appropriate. Substitute XXXX with the build number that appears in your PureDisk opening page. 2 On the Welcome page, click Next to start the installation. 3 On the License Agreement page, select I accept the terms of the license agreement and then click Next. The Agent Installation Method page appears. 4 Select the Enable PureDisk Deduplication Option to install the PDDO client. Select either a Typical or Custom installation method. A Typical installation installs all the PureDisk services in default directories. Typical is selected by default. A Custom installation enables you to install the PDDO plug-in in an alternate location. By default, the installer writes the software to the following location: C:\Program Files\Symantec\NetBackup PureDisk Agent

35 Installing the PDDO plug-in on Windows media servers Performing an unattended installation of the PDDO plug-in on a Windows media server 35 When the desired options are selected, click Next 5 If you selected Custom on the Agent Installation Method page, complete the Veritas NetBackup PureDisk Agent Features page. Perform the following steps: (Optional) Select SnapshotSupport and use the pull-down menu to disable or enable this feature. Snapshot support enables you to back up open files. (Optional) Click Change to change the installation path. The installer presents you with the Change current destination folder page. In the upper half of the page, use the icons and pull-downs to select a path. Or, in the lower half of the page, you can type an absolute path. Click OK when you finish on this page. Click Cancel to return to the Veritas NetBackup PureDisk Agent Features page. Click Next. On the Ready to install the program page, click Install. 6 To review the README information, confirm Display the READMEfile is selected. See Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool on page 37. Performing an unattended installation of the PDDO plug-in on a Windows media server To install the PDDO plug-in on a client with a minimum of user intervention, use an unattended, or silent, install. Note: Complete the entire PDDO installation and configuration process in one step. Do not install NetBackup software during the PDDO installation or configuration process. You can install NetBackup patches, upgrades, or releases after you configure the PDDO plug-in in NetBackup. To install the PDDO plug-in on a Windows media server by using an unattended install 1 Use the cd(1) command to change to the directory to which you installed the software. 2 Run the installation command that corresponds to the client s platform, as follows:

36 36 Installing the PDDO plug-in on Windows media servers Performing an unattended installation of the PDDO plug-in on a Windows media server C:>\pdagent-Windows_x XXXX.exe C:>\pdagent-Windows_x86_ XXXX.exe The parameters are as follows: --silent Performs the following actions: Answers all installer questions rather than prompting for input. Prompts you one time for information about an omitted parameter. If you provide an invalid answer, the installer exits. --spa=spa_addr --login=login For spa_addr, specify the FQDN (recommended), host name, or IP address of the storage pool authority. If the storage pool is clustered, specify the service FQDN, service host name, or service IP address. For login, specify the administrator s user ID on the storage pool authority. Information about PureDisk logon and password restrictions and guidelines is available. See the PureDisk Client Installation Guide. --passwd=passwd For passwd, specify the password for the administrator on the storage pool authority. Information about PureDisk logon and password restrictions and guidelines is available. See the PureDisk Client Installation Guide. --nbpddo --path=path Specifies that you want to install the NetBackup PureDisk Deduplication Option plug-in. (Optional) Specifies the installation directory. Default is /opt. Note the following: XXXX is the build number that appears in your PureDisk opening page. The following example shows a Windows x86 installation command with all possible parameters: pdagent-windows_x xxxx.exe --silent --spa=roadrunner.acme.com \ --login=beep --passwd=beep --nbpddo --path=/opt/myspa

37 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool 37 3 (Conditional) Start NetBackup s services. Perform this step if NetBackup s services are not running. For information about how to start services, see your NetBackup documentation. 4 Establish a connection between the media server and the storage pool. See Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool on page 37. Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool The procedure in this topic explains how to: configure the PDDO plug-in on the media server, point the media server to a PureDisk storage pool, and create the PureDisk storage server. After you perform this procedure, the software initiates the following activities: Activates the PDDO plug-in as a client to the storage pool Registers the media server as a client to the storage pool Creates a PureDisk PDDO data selection Note: Do not delete the PDDO data selection. If you delete it and then want to recreate this data selection, you must reinstall the PDDO plug-in. You cannot recreate this data selection from the PureDisk administrative Web UI. On a Windows platform media server, you can use either the NetBackup Windows interface or the NetBackup Java interface. Note: Be sure you've completed all steps from the Performing an attended installation topic before continuing with the following procedure. See Performing an unattended installation of the PDDO plug-in on a Windows media server on page 35.

38 38 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool To configure the PureDisk storage pool as a NetBackup storage server 1 Change to the PDDO plug-in s bin directory. Example 1. If you installed the software in the default directory, type the following commands: cd..\.. cd "Program Files\Symantec\NetBackup PureDisk Agent\bin" Example 2. If you installed in a directory other than the default, type the following commands: cd..\.. cd "install_path\netbackup PureDisk Agent\bin" For install_path, specify the directory in which you installed the PDDO plug-in.

39 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool 39 2 Type pddocfg.exe to start the PDDO storage server configuration tool wizard. You can also start the wizard by finding and double clicking on the pddocfg.exe file. The following image shows the PDDO Storage Server Configuration Tool interface. 3 In upper left, under Target, select one of the following: Add New Storage Server. This selection adds a PureDisk storage pool to the NetBackup configuration as a storage server. Update Storage Server. This selection updates the information for a particular storage server. Please be aware that at any time, you can click on Clear All on this page to clear all the fields. After you click on Clear All, you can retype your data.

40 40 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool 4 Complete any of the following fields that are available: NetBackup Media Server PureDisk Storage Server PureDisk Storage Server Administrator ID acctms.acme.com acme.spa1.com root PureDisk Storage Server Administrator Password 5 Click OK. On the INFO: storage server successfully configured window, click OK. That confirms the connection was established between the NetBackup media server and the PureDisk storage pool. If the configuration completed unsuccessfully, the system generates an explanatory message and writes an error log to C:\pddocfg.log. 6 Logon to the PureDisk administrative Web UI and click Manage > Agent.

41 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool 41 7 In the left pane, verify that the PureDisk media server appears as a client in the PureDisk administrative Web UI s Data Management tab. The following figure shows a department that is named Unknowndepartment with one client: PDDO. The PDDO data selection appears underneath the PDDO client. If that is the second media server to run the script, run the following command to confirm communication between NetBackup and PureDisk: bpstsinfo -si -sp PureDisk: -sn storage_pool_hostname 8 Configure the PDDO plug-in in NetBackup. See Configuring the PDDO plug-in in NetBackup on page 43.

42 42 Installing the PDDO plug-in on Windows media servers Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool

43 Chapter 5 Configuring the PDDO plug-in in NetBackup This chapter includes the following topics: Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface Verifying the NetBackup configuration and creating a NetBackup policy Configuring the PDDO plug-in for NetBackup optimized synthetic full backups Configuring the PDDO plug-in in NetBackup The PDDO plug-in is configured in NetBackup using either the Java interface or with the Windows interface. NetBackup s Java interface and Windows interface differ slightly. On Windows media servers, you can use either the Java interface or the Windows interface. On Linux and UNIX media servers, you can use only the Java interface. The following procedure explains how to configure the plug-in and how to create a policy to verify the configuration. To configure the PDDO plug-in on the media server, verify the configuration, and create a backup policy 1 Configure a NetBackup disk pool and storage unit. If you installed the PDDO plug-in on a Linux or UNIX media server, use the Java interface. Perform the following procedure:

44 44 Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface See Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface on page 44. If you installed the PDDO plug-in on a Windows media server, you can use either the Java interface or the Windows interface. Perform one of the following procedures: See Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface on page 44. See Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface on page Verify the NetBackup configuration and create a policy. See Verifying the NetBackup configuration and creating a NetBackup policy on page 48. Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface Use the following procedure to configure a PureDisk disk pool and a storage unit. You perform this procedure from the NetBackup Java interface on a Windows, Linux, or UNIX media server. To configure a NetBackup disk pool and storage unit in the NetBackup Java interface 1 Start the NetBackup Administration Console on the media server. 2 On the left menu pane, right-click Devices > Disk Pools. 3 Select New Disk Pool On the Welcome to the Disk Pool Configuration Wizard page, click Next. 5 On the Disk Pool page, in the Type pane, select PureDisk and click Next. 6 On the SelectStorageServer page, in the Storageserver pane, select a storage pool and click Next. If the page displays more than one PureDisk storage pool, select the one that corresponds to the PureDisk storage pool that you want to configure. The PureDisk storage pool s FQDN, host name, or IP address appears in the interface. NetBackup s interface refers to the PureDisk storage pool as a "storage server." 7 On the Select Volumes page, check PureDiskVolume, and then click Next. 8 On the Disk Pool Properties page, define the following parameters for this disk pool, and then click Next.

45 Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface 45 Specify a Disk Pool name. For example, you can specify dp_spa_in_building10 or some other identifier for the storage pool. After configuration, this name appears in NetBackup s list of disk pools. Information about the characters that you can use for this name is available. See the Symantec NetBackup OpenStorage Solutions Guide for Disk. (Optional) Type Comments. These can consist of extra identification, such as the location of the PureDisk storage pool, the owner of the system, and so on. Accept the default High water mark and Low water mark settings. PureDisk sends messages to NetBackup when it nears its storage capacity. 9 On the Summary page, review your specifications, and then click Next. 10 On the Disk Pool Configuration page, monitor the task s progress, and then click Next when the check mark appears to the left of the disk pool name. The check mark indicates that the NetBackup created the disk pool. 11 On the Storage Unit Option page, verify that the Create a Storage Unit that uses disk_pool_name is checked and click Next. 12 Complete the fields on the Storage Unit Creation - Enter details to create Storage Unit page, and then click Next. Define the following parameters for the storage unit: In the Storage unit name field, specify the storage unit name. For example, you can use acme.com-stu1. After configuration, this name appears in NetBackup s list of storage units in the NetBackup interface. In the Media Server pane, select Use any available media server in the disk pool or Use only the following media servers. Use the following information to make your selection: If you have only one media server, it does not matter which option you choose. If you have multiple media servers and you select Use any available media server to transport data, NetBackup chooses from among the available media servers for backups. Choose this option if you plan to add other media servers to this PureDisk storage pool in the future. You do not need to update the storage units at that time. If you have multiple media servers and you select Useonlytheselected media servers, NetBackup uses the specified media server(s) when it runs.

46 46 Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface Set the Maximum concurrent jobs to 40. Confirm the Maximum fragment size is set to The unit of measure is megabytes for this field, so this value equals 51,200 megabytes (or 50 gigabytes). In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units, and the New Storage Units display appears. On this display, confirm the Maximum fragment size field to Symantec recommends you do not modify this value. If the Maximumfragmentsize is set to a value greater than 51200, backups that attempts to write fragments greater than megabytes fail with an image size exceeded error. If you specify a smaller value, you incur more maintenance because there are more fragments, but there is less overhead per fragment. More information about these settings is available. See the Symantec NetBackup OpenStorage Solutions Guide for Disk. 13 Click Finish. 14 Complete and verify the NetBackup configuration. See Verifying the NetBackup configuration and creating a NetBackup policy on page 48. Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface Use the following procedure to configure a NetBackup disk pool and OpenStorage unit. You perform this procedure from the NetBackup Windows interface on a Windows media server. To configure a NetBackup disk pool and storage unit in the NetBackup Windows interface 1 Start the NetBackup Administration Console on the media server. 2 On the left menu pane, right-click Devices > Disk Pools. 3 Select New On the Welcome to the Disk Pool Configuration Wizard page, click Next. 5 On the Disk Pool page, in the Type pane, select PureDisk and click Next.

47 Configuring the PDDO plug-in in NetBackup Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface 47 6 On the SelectStorageServer page, in the Storageserver pane, select a storage pool and click Next. If the page displays more than one PureDisk storage pool, select the one that corresponds to the PureDisk storage pool that you want to configure. The PureDisk storage pool s FQDN, host name, or IP address appear in the interface. NetBackup s interface refers to the PureDisk storage pool as a "storage server." 7 On the Select Volumes page, check PureDiskVolume and click Next. 8 Complete the fields on the Disk Pool Properties page, and then click Next. Define the following parameters for this disk pool: Specify a Disk Pool name. For example, you can specify dp.spa.in.room101 or some other identifier for the storage pool. After configuration, this name appears in NetBackup s list of disk pools. (Optional) Type Comments. These can consist of extra identification, such as the location of the PureDisk storage pool, the owner of the system, and so on. Accept the default High water mark and Low water mark settings. PureDisk sends messages to NetBackup when it nears its storage capacity. TIP: To specify site-specific High water mark and the Low water mark settings, change these settings now. You can change this setting later in NetBackup, but it is easier and more efficient to specify these settings at this time. 9 On the Summary page, review your specifications, and then click Next. 10 On the Disk Pool Creation page, monitor the task s progress. Click Next when the check mark appears to the left of the disk pool name. The check mark indicates that the NetBackup created the disk pool. 11 On the Storage Unit creation - Choose to create a storage unit page, verify that the Create a Storage Unit that uses disk_pool_name is checked. Click Next. 12 Complete the fields on the Storage Unit Creation - Enter details to create NetBackup Storage Unit page, and then click Next. Define the following parameters for the storage unit: In the Storage unit name field, specify the storage unit name. For example, acme.com-stu. After configuration, this name appears in NetBackup s list of storage units in the NetBackup interface.

48 48 Configuring the PDDO plug-in in NetBackup Verifying the NetBackup configuration and creating a NetBackup policy In the Media Server pane, select Use any available media server to transport data or Use only the selected media servers. Use the following information to make your selection: If you have only one media server, it does not matter which option you choose. You may have more than one media server. If you select Use any available media server to transport data, NetBackup chooses from among the available media servers for backups. You may have more than one media server but select Use only the selected media servers. NetBackup then uses the specified media server(s) when it runs Set the Maximum concurrent jobs to 40. Confirm the Maximum fragment size is set to This value is 50 gigabytes. In the NetBackup Administration Console, select NetBackup Management > Storage > Storage Units, and the New Storage Units display appears. On this display, confirm the Maximum fragment size field to Symantec recommends you do not modify this value. If the Maximumfragmentsize is set to a value greater than 51200, backups that attempts to write fragments greater than megabytes fail with an image size exceeded error. If you specify a smaller value, you incur more maintenance because there are more fragments, but there is less overhead per fragment. More information about these settings is available. See the Symantec NetBackup OpenStorage Solutions Guide for Disk. 13 Click Finish. 14 Proceed to the following topic to complete the NetBackup configuration and verify it: See Verifying the NetBackup configuration and creating a NetBackup policy on page 48. Verifying the NetBackup configuration and creating a NetBackup policy The procedure in this topic explains how to verify that the PureDisk PDDO plug-in is configured properly in NetBackup. For more information about NetBackup operations, see your NetBackup documentation.

49 Configuring the PDDO plug-in in NetBackup Verifying the NetBackup configuration and creating a NetBackup policy 49 Note: Do not use the Backup Policy Configuration Wizard. You must create the policy manually. To verify the NetBackup configuration and create a NetBackup policy 1 Verify that the PureDisk storage unit that you configured appears in the NetBackup interface. For example, start the NetBackup Administration Console on the media server and perform the following tasks: Click DiskPools and make sure that the disk pool that you named appears in the list. See Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface on page 46. Review step 8 for help on disk pools. Click Storage Units and make sure that the storage unit that you named appears in the list. See Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface on page 46. Review step 12 for help on storage units. 2 In the NetBackup interface, in the left pane, right-click Policies and select New Policy... The Add a New Policy dialog box appears. 3 Type a name for this policy. 4 Create the NetBackup backup policy manually. NOTE: Do not use the Backup Policy Configuration Wizard. You must create the policy manually. When you create this policy, make sure to specify the following options: Disable compression Disable encryption If compression and encryption are enabled in NetBackup, the data is modified before it reaches PureDisk, and PureDisk cannot deduplicate it correctly. PureDisk compresses and encrypts the data once it is deduplicated. The next step explains how to enable compression and encryption.

50 50 Configuring the PDDO plug-in in NetBackup Configuring the PDDO plug-in for NetBackup optimized synthetic full backups 5 Edit the pd.conf file to enable compression and encryption, if required. Symantec recommends enabling compression to help conserve disk space your PureDisk environment. Perform this step if you need compression and encryption when NetBackup writes the backup images to the PureDisk disk pool. PureDisk s deduplication feature relies on the ability to detect similar patterns in files from one backup to the next. When you enable NetBackup encryption and compression, PureDisk cannot detect patterns in file content and deduplication effectiveness decreases. The pd.conf file is a configuration file on the media server. More information about how to specify settings in this file is available. See About the pd.conf file on page (Optional) Configure NetBackup for multistreaming. To run more than one job per NetBackup client, make sure to configure NetBackup to run more than one stream. For information about multistreaming, see your NetBackup documentation. 7 Run a manual backup and restore the files from the backup. If you can perform this backup and restore, then the configuration works properly. For information about NetBackup backups and restores, see your NetBackup documentation. See Configuring the PDDO plug-in for NetBackup optimized synthetic full backups on page 50. Configuring the PDDO plug-in for NetBackup optimized synthetic full backups The following procedure explains how to configure the PureDisk PDDO plug-in to store NetBackup optimized synthetic full backups. Some steps in the procedure are written in general terms. The following publications provide more information about general steps in this procedure: The NetBackup AdvancedDisk Storage Solutions Guide The Symantec NetBackup OpenStorage Solutions Guide for Disk The NetBackup Administrator's Guide, Volume 1 The NetBackup Administrator's Guide, Volume 2

51 Configuring the PDDO plug-in in NetBackup Configuring the PDDO plug-in for NetBackup optimized synthetic full backups 51 To configure the PureDisk PDDO plug-in to store NetBackup optimized synthetic full backups 1 Install and configure the PureDisk agent as a PureDisk Deduplication Option (PDDO) plug-in on a NetBackup media server. More information is available. See About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server on page 25. See About installing the PDDO plug-in on a Windows media server on page Configure the PureDisk storage pool to be all of the following NetBackup components. Make sure to configure the components in the order that is shown in the following list: A NetBackup storage server The PDDO plug-in installation instructions instruct you to run the pddocfg command near the end of the installation procedure. The pddocfg command configures the PureDisk storage pool as a NetBackup storage server. A NetBackup disk pool and a NetBackup storage unit See Configuring the NetBackup disk pool and storage unit in the NetBackup Java interface on page 44. See Configuring the NetBackup disk pool and storage unit in the NetBackup Windows interface on page Confirm the OptimizedImage flag is set to support optimized synthetic backups on each NetBackup storage server: nbdevquery liststs -U -storage_server STSname nbdevquery -listdp -U -dp DPname In the preceeding command, STSname is the name of the storage server and DPname is the name of the Disk Pool. The output from these commands contain the following text if the OptimizedImage flag is set: Flag : OptimizedImage 4 (Optional) Type the following commands on the media server to confirm that the OptimizedImage flag is set: nbdevquery -liststs -U nbdevquery -listdp -U

52 52 Configuring the PDDO plug-in in NetBackup Configuring the PDDO plug-in for NetBackup optimized synthetic full backups 5 Use the NetBackup interface to create a backup policy that includes full, incremental, and synthetic full backup schedules. When you configure the backups, make sure to configure them in the following order: On the Change Policy Wizard dialog box's Attributes tab, check Collect true image restore information and check with move detection. On the AddSchedule dialog box's Attributes tab, check Syntheticbackup. On the Scheduling tab, make sure to configure the full backup and the incremental backup to run before the synthetic full backup schedule runs. 6 After the backups run, examine the NetBackup Job Details information for the synthetic full backup schedule, and confirm that the optimized synthetic operation was performed. The NetBackup Job Details information includes the line Performing Optimized Synthetic Operation when NetBackup runs an optimized synthetic backup. See Configuring the PDDO plug-in in NetBackup on page 43.

53 Chapter 6 Using PureDisk as a NetBackup storage unit This chapter includes the following topics: About the PDDO plug-in in the PureDisk administrative Web UI Adding an additional PureDisk storage pool to a NetBackup media server About configuring NetBackup lifecycle policies Disaster recovery configuration example About PureDisk garbage collection policies Retrieving job reports About job details reports About data mining reports About central reporting Displaying the agent dashboard About recovery of a PureDisk storage pool used as a PDDO plug-in Changing the storage pool authority password when PDDO is enabled About throttling PDDO replication and duplication jobs About reporting PureDisk resource usage to NetBackup

54 54 Using PureDisk as a NetBackup storage unit About the PDDO plug-in in the PureDisk administrative Web UI About the PDDO plug-in in the PureDisk administrative Web UI This topic describes some of the operations that you can perform with a PureDisk storage pool after you configure it as a NetBackup storage unit. After you enable PDDO, the PureDisk administrative Web UI reflects jobs initiated both by NetBackup and by PureDisk. The following figure shows an example of a PureDisk display. Figure 6-1 PDDO client icon PDDO Activity Data selection icon Policies that affect this data selection Replication icon replication from another storage pool to here See Figure 6-1 on page 54. for the PureDisk displays of the following types of icons for PDDO plug-in activity: The client icon. Each PureDisk client appears in the PureDisk storage pool s administrative Web UI. The PDDO client icon represents all the media servers that are attached to this storage pool. No matter how many media servers you attach to this storage pool, only one PDDO client icon appears. The data selection icon.

55 Using PureDisk as a NetBackup storage unit Adding an additional PureDisk storage pool to a NetBackup media server 55 This icon represents data backups from one or more NetBackup media servers to this PureDisk storage pool. Only one data selection icon for the PDDO storage unit can exist. One or more policy icons. This display shows the policy icon System policy for data removal. By default, you specify data retention in the NetBackup policy. PureDisk removes expired data when the system policy for data removal runs. One or more replication data selection icons. These icons are [R] PDDO(n) icons. One icon exists for each PureDisk PDDO data selection that is replicated to this storage pool from another storage pool. This icon represents one or more of the following replication actions: A PureDisk replication from one storage pool to this storage pool. An optimized duplication action from one storage pool to this storage pool. NetBackup initiates this action, which is a form of replication. Do not use these icons to interpret specific system activity. If you specified optimized duplication in NetBackup, use the NetBackup interface to see if the job finished. If you specified replication in PureDisk, click the PureDisk Workflows tab and examine the replication activity from that tab. If you have two PureDisk storage pools, you might also notice [R][R] icons. These icons represent replication from one storage pool to another, and then back again. In the right column, PureDisk displays storage pool job activity. NetBackup initiates most of the jobs that are related to the PDDO storage unit. When you click a PDDO icon in the middle column, PureDisk changes the display in the right column to show job activity for that icon. See Adding an additional PureDisk storage pool to a NetBackup media server on page 55. Adding an additional PureDisk storage pool to a NetBackup media server A NetBackup media server can send data to more than one PureDisk storage pool. When a media server is configured to target two different PureDisk storage pools, you can run duplicate backups from NetBackup to both storage pools. The following procedure explains how to configure a media server to send backups to an additional PureDisk storage pool.

56 56 Using PureDisk as a NetBackup storage unit Adding an additional PureDisk storage pool to a NetBackup media server To add an additional PureDisk storage server to a NetBackup media server 1 Logon to the NetBackup media server. 2 Create the PureDisk storage server and add credentials. This step differs depending on your platform. (Linux or UNIX) At the system prompt, run the following command to create the PureDisk storage server and add credentials: # /opt/pdag/bin/pddocfg.sh --addspa --mediaserver=ms_addr --storageserver=spa_addr The arguments to this command are as follows: ms_addr Specifies the media server s FQDN, host name, or IP address. Symantec recommends that you type the full FQDN of the media server. For example, acctms.acme.com. spa_addr Specifies the PureDisk storage pool authority s FQDN (recommended), host name, or IP address. The storage pool authority identifies itself with this address. You also enter this address in a browser window to logon to the storage pool authority. If the storage pool authority is clustered, type the service FQDN, service host name, or service IP address. Type the storage pool authority administrator s user ID and password when the pddocfg command issues prompts for this information. (Windows) Configure the additional PureDisk storage server using steps 1 though 5 of the following procedure: See To configure the PureDisk storage pool as a NetBackup storage server on page 38. Under Target, specify Add New Storage Server.

57 Using PureDisk as a NetBackup storage unit About configuring NetBackup lifecycle policies 57 3 Verify the storage server in the NetBackup interface. The following figure shows an example environment with two PureDisk storage servers. 4 Verify NetBackup and create a NetBackup policy. See Verifying the NetBackup configuration and creating a NetBackup policy on page 48. About configuring NetBackup lifecycle policies When you configure two or more PureDisk storage pools as NetBackup disk pools, you also can configure a lifecycle policy. A NetBackup lifecycle policy is a storage plan for a set of backups. It lets you manage different kinds of data in your backups. A lifecycle policy specifies the following information: A list of destinations to which NetBackup writes copies of the backup images. NetBackup can initiate a duplication or optimized duplication between disk pools. If two or more of the disk pool destinations are PureDisk storage pools, NetBackup can perform this duplication as an optimized duplication.

58 58 Using PureDisk as a NetBackup storage unit Disaster recovery configuration example The prescribed retention period for each copy. The lifecycle policies let you classify the data according to the data s backup requirements. The classifications make it easier to configure backups for data with different requirements. For example, data and financial data. For more information about lifecycle policies, see your NetBackup administration documentation. See Adding an additional PureDisk storage pool to a NetBackup media server on page 55. Disaster recovery configuration example This topic shows a configuration example and describes how you can recover data by using NetBackup and PureDisk. The following guidelines apply to the configuration: You can recover data from NetBackup through a restore. You may need to import the data to NetBackup before you perform the restore. An import updates the NetBackup catalog. After the import, NetBackup is aware of all the images that reside on the PureDisk storage pool. When you run a NetBackup backup or a duplication, these processes also update the NetBackup catalog. NetBackup images that are created with true image recovery (TIR) enabled, can be imported efficiently because NetBackup only needs to read the TIR file. NetBackup incremental and differential backups that are performed with TIR enabled increase the NetBackup catalog s size. Imports that are performed on the images that are backed up with TIR enabled are significantly faster than those performed without TIR enabled. You must install a PDDO client on a storage pool to allow NetBackup imports or restores from the storage pool. See the following figure for an example NetBackup configuration that includes two PureDisk storage pools and two NetBackup media servers:

59 Using PureDisk as a NetBackup storage unit Disaster recovery configuration example 59 Figure 6-2 Two NetBackup media servers and two PureDisk storage pools NetBackup Media Server 1 + PDDO NetBackup Media Server 2 Backups NetBackup optimized duplication PureDisk storage pool 1 PureDisk storage pool 2 Assume that the configuration has evolved through the following phases: In Phase 1, you configured the following: A PDDO client on both storage pool 1 and storage pool 2. Note that you did not configure media server 1 to write backups to storage pool 2. A backup policy on media server 1 that writes backups to PureDisk storage pool 1. Media server 2, which is not connected to any PureDisk storage pool. In Phase 2, you configured optimized duplication to copy the PDDO data selection from storage pool 1 to storage pool 2. As a result, data from media server 1 is now backed up to both storage pool 1 and storage pool 2. Select from the following options to recover data for media server 1:

60 60 Using PureDisk as a NetBackup storage unit About PureDisk garbage collection policies If media server 1 and storage pool 1 are down, you can import data from storage pool 2 to recover media server 1. As an alternative, you can install a PDDO plug-in on media server 2, and import the data from storage pool 2. If media server 1 is down, you can perform a catalog recovery on media server 1. Then you can perform a regular restore from storage pool 1. If storage pool 1 is down, you can import data from storage pool 2 to recover data to media server 1. In Phase 3, you configured a NetBackup lifecycle policy to duplicate the data between storage pool 1 and storage pool 2. This configuration has the following effects: The duplication takes less time to run because the data already exists on storage pool 2. If either storage pool 1 or storage pool 2 become unavailable, you can run restores seamlessly from the storage pool that is still running. See About configuring NetBackup lifecycle policies on page 57. About PureDisk garbage collection policies The PureDisk file data is separated into two components: the file data itself and the file metadata. The file data resides on the content routers, and the metadata resides in the metabase engine. A data removal policy might not remove all data that is related to expired NetBackup backup images. The completeness of the removal depends on other system processes. The PureDisk garbage collection policies are enabled by default to run once each month. The garbage collection policies remove unneeded files, links, and data fragments from PureDisk storage. This unneeded data can fill a storage pool and cause slower performance. You can use the PureDisk storage pool as a repository for other backup and restore clients. If you do, it is likely that you configured policies for metabase garbage collection. These policies are storage-pool-wide policies, and they also affect the PDDO data selection. If you use the PureDisk storage pool only as a PDDO OpenStorage plug-in, make sure to configure garbage collection policies for the storage pool. Information about how to configure one or more of the following policies is available in the PureDisk Administrator s Guide: Metabase garbage collection

61 Using PureDisk as a NetBackup storage unit Retrieving job reports 61 Retrieving job reports PureDisk generates reports about backups, replication, and other types of jobs that run with the PDDO data selection. The following procedures explain how to retrieve job reports from the PureDisk administrative Web UI. To retrieve job reports 1 Select Monitor > Jobs tab. 2 In the left pane, click the PDDO data selection icon. 3 (Optional) Expand the PDDO data selection icon until the job you want to see appears in the right pane. 4 In the right pane, click the Job ID number for the job you want to see. A Job Details report appears. Information about the Job Details report is available. See About job details reports on page 61. About job details reports A job details report is divided into the following four tabs: General, Details, Statistics, and a Job log. These tabs contain information in a format that is similar to the job details reports for other types of PureDisk jobs. The following figure shows the Statistics tab.

62 62 Using PureDisk as a NetBackup storage unit About job details reports Figure 6-3 Statistics tab for a PDDO backup job See Table 6-1 on page 62. for the descriptions that explain these statistics. Table 6-1 Statistic Lines in the Statistics tab for a PDDO backup job Description Global data reduction saving Bytes scanned during backup Media-server cache hit percentage Bytes transferred to content router Specifies the percentage of source data bytes that did not have to be transmitted to the content routers because of data reduction. Higher numbers correlate to more efficiency. Specifies the number of bytes that NetBackup sent to the PDDO plug-in to be scanned for deduplication. That is typically the entire NetBackup image size. Specifies the percentage of fingerprint lookups that were found in the media server cache. The system alses to performs remote lookups on the content router. Specifies the total number of bytes of unique data that were transferred to the storage pool s content routers after segmentation and compression. Includes data that is related to special files. For special files, PureDisk stores a special data object on the content routers to be able to restore these files.

63 Using PureDisk as a NetBackup storage unit About data mining reports 63 Table 6-1 Statistic Lines in the Statistics tab for a PDDO backup job (continued) Description Start date and time Stop date and time Backup time duration Specifies the date and time when the job began. Specifies the date and time when the job ended. Specifies the amount of time that elapsed between when the job started and when the job ended. For more information about these tabs, see the following manual: See the PureDisk Administrator s Guide. See Retrieving job reports on page 61. About data mining reports A data mining policy collects information about the files in a PureDisk storage pool. When you run a data mining policy from the administrative Web UI, PureDisk gathers information from the metabase server and summarizes the information in a table. This report uses data mining to extract and present information in report format and in XML format. A data mining report shows the effectiveness of PureDisk data deduplication. To obtain a data mining report, consult the PureDisk Administrator s Guide about the following topics: Enabling and scheduling the system policy for data mining. Permissions that are needed to run data mining reports. Obtaining data mining reports. The data mining reports that pertain to PDDO contain information that is similar to that found in other kinds of data mining reports. One field in these reports is unique to data mining: the Number of Files/Versions field. The Number of Files/Versions field contains a rough estimate of the number of NetBackup images that are stored on the content routers in the PureDisk storage pool. See About the PDDO plug-in in the PureDisk administrative Web UI on page 54. About central reporting The central reporting feature includes a Used capacity field. Please be aware the data in this field includes only the data that is consumed by PureDisk agent backups. It does not include the data that is consumed by PDDO data on a storage

64 64 Using PureDisk as a NetBackup storage unit Displaying the agent dashboard pool. Depending on the configuration of your environment, the difference between data that is consumed by PureDisk agent backups and the combined total of agent backups and PDDO data can be significant. See About the PDDO plug-in in the PureDisk administrative Web UI on page 54. Displaying the agent dashboard For a selected department or selected agent, the agent dashboard shows information about the running jobs and the jobs that completed most recently. To refresh the data in this dashboard, press function key F5. To display the agent dashboard 1 Click the Manage > Agent tab. 2 Expand the tree view in the left pane until the department or the agent you want appears. Click the plus sign (+) next to each entity to expand the tree. 3 Click on the department or the agent you want. 4 Click Agent Dashboard in the right pane. See About the PDDO plug-in in the PureDisk administrative Web UI on page 54. About recovery of a PureDisk storage pool used as a PDDO plug-in To recover a PureDisk storage pool that is used as a PDDO plug-in, use the same methods that you use to recover other PureDisk storage pools. See the PureDisk Administrator s Guide. Whether you need to perform additional recovery procedures depends on when the disaster occurred. Consider the following series of possible events: At time 1 (T1), you perform a PureDisk storage pool disaster recovery backup. At time 2 (T2), NetBackup writes backup data to the PureDisk storage pool. The PureDisk storage pool goes down. You recover the PureDisk storage pool. You use the storage pool backup that was taken at T1.

65 Using PureDisk as a NetBackup storage unit Changing the storage pool authority password when PDDO is enabled 65 NetBackup writes more backup data to the storage pool. NetBackup assumes that the data that it wrote to the storage pool at T2 is present on the storage pool. In reality, this data was overwritten when you restored the storage pool by using the backup from T1. Symantec recommends that you expire the NetBackup catalog images that were written to the PDDO storage unit at T2. This option ensures that as much data as possible is recoverable. You then can resume running your backups. You can expire the NetBackup catalog images either through NetBackup UI or through the NetBackup command line. Information about how to search the catalog and how to expire images is available. See the NetBackup Administrator s Guide, Volume I. You can think of a downed PDDO storage unit as a disk that failed and was rolled back. In this case, NetBackup still has the catalog information that points to that lost data. While other solutions may be available for your environment, Symantec recommends that you expire the images. See About the PDDO plug-in in the PureDisk administrative Web UI on page 54. Changing the storage pool authority password when PDDO is enabled The following procedures explain how to change the PureDisk storage pool authority root password when PDDO is enabled. To change the root user password on the storage pool authority 1 Logon to the PureDisk administrative Web UI as root. 2 Click the Settings > Configuration tab. 3 In the left pane, expand Configuration > User Management > Users. 4 Select the root user. 5 In the right pane, click Change Password. 6 In the Change Password panel, complete the New Password and Confirm Password fields and click Save. 7 Change the root user password on the media server. See To change the root user password on a Linux or UNIX media server on page 66. See To change the root user password on a Windows media server on page 66.

66 66 Using PureDisk as a NetBackup storage unit About throttling PDDO replication and duplication jobs To change the root user password on a Linux or UNIX media server 1 Logon to the media server as root. 2 Type the following command: # /usr/openv/volmgr/bin/tpconfig 3 Select 3) Credentials Configuration. 4 Select 3) OpenStorage Server. 5 Type the storage server s name, the root user s logon, and the root user s new password. 6 Edit from tpconfig. To change the root user password on a Windows media server 1 Logon to the media server as root. 2 Click Start > Run. 3 Type cmd and click Open. 4 Type the following command: C:\Program Files\Veritas\Volmgr\bin> tpconfig -update -storage_server SPA_name -stype PureDisk -sts_user_id root -password passwd For SPA_name, specify the name of the storage pool authority. For passwd, specify the root user s new password. 5 (Optional) Restart NetBackup services. See About the PDDO plug-in in the PureDisk administrative Web UI on page 54. About throttling PDDO replication and duplication jobs PureDisk monitors the load on the storage pool before it starts any additional PDDO > PDDO Auto Image Replication / optimized duplication jobs. PureDisk monitors the following parameters under the [replication] section of agent.cfg:

67 Using PureDisk as a NetBackup storage unit About reporting PureDisk resource usage to NetBackup 67 Available system memory This value represents the minimum amount of system memory in MB that must be free to allow a PDDO replication job to start. Default parameter value: min_memory_threshold=100 Considerations: The monitor excludes buffers and cache. This value is only checked on the source SPA. Number of concurrent PDDO duplication and replication jobs This value represents the maximum number of concurrent PDDO replication and duplication jobs. Default parameter value: max_pddo_job_count=150 Considerations: This value is only checked on the source SPA. Setting either of the above parameters to 0 disables the check. If the source SPA has insufficient memory or is already running too many concurrent jobs, it informs the NetBackup media server that it is busy. Once the source SPA is no longer overloaded, the job is started. When trying to start an Auto Image Replication job or optimized duplication job with an overloaded storage pool, the job will be in the active state. When the storage pool is no longer overloaded and the job starts, the job proceeds normally. Note: This feature requires the NetBackup media server be running at least NetBackup or higher. About reporting PureDisk resource usage to NetBackup PureDisk monitors the system state and sends an activity event to NetBackup when it detects an abnormal state. PureDisk uses the OST event channel to send the abnormal state event to NetBackup. Events are written to the NBU DB error log

68 68 Using PureDisk as a NetBackup storage unit About reporting PureDisk resource usage to NetBackup PureDisk monitors the following parameters under the [monitoring] section of agent.cfg: TLog age An event is generated if there are tlogs that are at least this old in the queue. Values are expressed in number of days. Default parameter value: tlogagelimit=3 Free memory An event is generated if the percentage of memory in use is equal to or exceeds this value. Default parameter value: memlimit=90 The monitor excludes buffers or cache. Swap space An event is generated if the percentage of swap in use is equal to or exceeds this value. Default parameter value: swaplimit=10 Free disk space PureDisk checks for free disk space on the root partition and the /Storage/data partition. An event is generated if the disk usage on / is equal to or exceeds rootlimit. An event is generated if the free disk space on /Storage/data exceeds the softlimit. rootlimit and softlimit do not take reserved blocks into account, so percentages calculated may differ slightly from those reported by df. Default parameter value: rootlimit=90 softlimit=90

69 Using PureDisk as a NetBackup storage unit About reporting PureDisk resource usage to NetBackup 69 Load average An event is generated if the load average over the past 15 minutes, divided by the number of cores on the system is equal to or exceeds loadavglimit. Default parameter value: loadavglimit=1.00 These parameters can be disabled by setting them equal to -1. To prevent repeat event notifications, PureDisk only generates an event when it detects a transition from a normal state to an abnormal one. Additionally, PureDisk also detects when a transition from an abnormal state to a normal occurs and generates an event. Note: This feature requires the NetBackup media server be running at least NetBackup or higher.

70 70 Using PureDisk as a NetBackup storage unit About reporting PureDisk resource usage to NetBackup

71 Chapter 7 Seeding PDDO backups This chapter includes the following topics: About seeding Configuring client seeding Configuring storage server seeding About seeding Seeding is the process of creating a fingerprint cache for a deduplication backup for a client which has not been previously backed up. By creating this cache, the deduplication process has a collection of data to check for duplicates. This process results in less data being transferred in the initial backup. Seeding can improve the backup speed of first client backups, especially for backups over a high latency WAN. The seeding process described in this section works with NetBackup and later and with appliances DAS and later. You configure seeding in one of two places: on the storage server or on the client. See Configuring client seeding on page 71. See Configuring storage server seeding on page 73. Configuring client seeding Use the following procedure to configure client seeding:

72 72 Seeding PDDO backups Configuring client seeding To set up seeding on new clients 1 Determine the source client name and policy name you want to use for seeding. Pick a good candidate for seeding the fingerprint cache in one of two ways. Clients with similar data are good candidates for seeding the fingerprint cache. If there are no similar clients, you can transfer the data from the new client to the storage server using a transfer drive. Then perform an initial backup of the data on the transfer drive. Once you have determined the method for seeding the fingerprint cache, make note of the client name and backup policy name you want to use for seeding. 2 Add the FP_CACHE_CLIENT_POLICY keyword pair to the pd.conf file on the new client. The pd.conf file resides in the following directories: /usr/openv/lib/ost-plugins/ (UNIX or Linux) install_path\veritas\netbackup\bin\ost-plugins (Windows) Edit the pd.conf file on the new client and include the keyword FP_CACHE_CLIENT_POLICY. The format for the keyword is: FP_CACHE_CLIENT_POLICY = client_host_machine,backup_policy_name,date Replace the three fields in the string as follows: client_host_machine: The name of the source seeding client. backup_policy_name: The name of the source seeding policy. date: The date when the seeding information expires. If the information is not expired, the seeding information is used for all backups, even after a full backup of the new client is performed. The format for date is mm/dd/yyyy. Example: In the following example, backups of the client use the information from the full_local_drives policy on the server_01 computer. The seeding information expires March 15, FP_CACHE_CLIENT_POLICY = server_01,full_local_drives,03/15/2012 More information about the pd.conf file is available. See About pd.conf file settings on page 93. See About seeding on page 71.

73 Seeding PDDO backups Configuring storage server seeding 73 Configuring storage server seeding When you enable seeding on the storage server, Symantec recommends using the seedutil utility. Use of the FP_CACHE_CLIENT_POLICY keyword affects all backup jobs. Symantec does not recommend use of the FP_CACHE_CLIENT_POLICY keyword on storage servers. The seedutil utility is a more flexible method to configure client seeding on a storage server. Run this utility on the storage server. The utility creates a special seeding directory in the PureDisk catalog for a client. The utility populates the directory with image references to another source client and policy s backup images. The special seeding directory appears in the PureDisk catalog as follows: PureDisk_Catalog_Home/#pdseed/client When a backup is run on a client, a check is made first to find images from the previous backup. If images are found, they are used for the cache. If no images are found for a previous backup, a second check is made to find images in this special seeding directory. Changes to the special seeding directory should be made using the seedutil program. Assuming default installation locations, this utility can be found at: /usr/openv/pdde/pdag/bin/seedutil (UNIX or Linux) C:\Program Files\Veritas\pdde\seedutil.exe (Windows) Full usage info for this tool is as follows: Usage: seedutil[-v log_level] [-seed -sclient source_client_name -spolicy policy_name -dclient destination_client_name[-backupid backup_id]] [-clear client_name] [-clear_all] [-list_clients] [-list_images client_name] [-help] Parameter -clear client_name -clear_all -list_clients -list_images client_name Description Clear the contents of the client_name directory in the seeding location. Clear the contents of the seeding directory. List the contents of the seeding directory. List the contents of the client_name directory. -seed -sclient source_client_name -spolicy policy_name -dclient destination_client_name Creates the links in the destination_client_name directory to all the *.img, *.fmk and *.hdr files found in the path client_name/policy_name.

74 74 Seeding PDDO backups Configuring storage server seeding Parameter Description -seed -sclient source_client_name -spolicy policy_name -dclient destination_client_name -backupid backup_id Creates the links in the destination_client_name directory to all the *.img, *.fmk and *.hdr files found in the path client_name/policy_name that have backup_id in their names. -v log_level Runs the utility in verbose mode. The larger the value for log_level, the more verbose the log file. Acceptable values for log_level are: 1 Error 2 Warning 3 Infomational 4 Debug 5 Trace The most common options are -seed, -list_images and -clear. For example, assume that you have a new remote client, remote_client1, you want to back up for the first time. Data for the client was copied to a transfer drive and backed up locally to the media server media1, using the transfer_drive policy. To configure seeding for two new clients 1 Run the following command on the media server to set up a special seeding directory using the transfer_drive backup images for the client: $ seedutil -seed -sclient media1 -spolicy transfer_drive -dclient remote_client1 2 Verify that the seeding directory has been populated for the client: $ seedutil -list_images remote_client1 3 Run backups for remote_client1. 4 Clean up the special seeding directory. $ seedutil -clear remote_client1 Clear the special seeding directory once a successful backup completes. The source backup images that are referenced in the special seeding directory are not expired until they are no longer referenced. To help with this process, the special seeding directory for a client is automatically cleared whenever an image expires in NetBackup for that client. It is good practice to explicitly clean up the special seeding directory when it is no longer needed.

75 Seeding PDDO backups Configuring storage server seeding 75 NetBackup chooses the directory for fingerprint cache loading in the following order: 1. Client and policy defined in FP_CACHE_CLIENT_POLICY, if it is not expired 2. Client and policy from previous backup 3. Special seeding directory, if no images from previous backup were found The following flow chart shows the order in which fingerprint cache is loaded:

76 76 Seeding PDDO backups Configuring storage server seeding Start Is the client seeding directory specified? Yes Use the specified client seeding directory No Does the default directory contain full backup image information? Yes Use the default cache directory No Does the seeding directory exist for the client? No NOTE: This results in low cache hits. Yes Use the client s seeding directory See About seeding on page 71.

77 Appendix A Installing the PDDO plug-in on a clustered NetBackup media server This appendix includes the following topics: Installing the PDDO plug-in on a clustered NetBackup media server Installing the PDDO plug-in on a clustered NetBackup media server The following procedure explains how to install the PDDO plug-in on a clustered media server in general terms. Note: Remember to use the media server s local host name instead of it cluster virtual name for the installation and configuration.

78 78 Installing the PDDO plug-in on a clustered NetBackup media server Installing the PDDO plug-in on a clustered NetBackup media server To install a PDDO plug-in on a clustered NetBackup media server 1 Plan your configuration and download the PDDO plug-in to the NetBackup media server s active node. See About improvements to the synthetic backup process on page 16. See Downloading the PDDO plug-in to a media server on page On the active media server, install the PDDO plug-in and establish a connection between the active media server and the storage pool. Use the procedures in one of the following platform-specific topic: See About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server on page 25. or See Performing an attended installation of the PDDO plug-in on a Windows media server on page On the active media server node, configure the PDDO plug-in in NetBackup. Use the procedures in the following topic: See Configuring the PDDO plug-in in NetBackup on page Failover the NetBackup service group to another node. 5 Install the PDDO plug-in on the node to which you failed over. Use the procedure in one of the following platform-specific topics: See Performing an attended installation of the PDDO plug-in on a Linux or UNIX media server on page 26. See Performing an unattended installation of the PDDO plug-in on a Linux or UNIX media server on page 28. See Performing an attended installation of the PDDO plug-in on a Windows media server on page Establish a connection between the failover media server node and the storage pool. Use the procedure in one of the following platform-specific topics: See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29. See Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool on page 37. When you complete these procedures, examine the configuration messages in step 6.

79 Installing the PDDO plug-in on a clustered NetBackup media server Installing the PDDO plug-in on a clustered NetBackup media server 79 See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29. These messages are different for the failover media server node. You can expect the output to be similar to the following: /opt/pdag/bin/pddocfg.sh: INFO: "pdregister --action register" completed successfully Mon Apr :30: INFO ( ): Dataselection has been created. /opt/pdag/bin/pddocfg.sh: INFO: "pdregister --action createds" completed successfully Failed to create storage server storageserver.acme.com, cannot connect on socket /opt/pdag/bin/pddocfg.sh: ERROR: "nbdevconfig -creatests" failed You can disregard the Failed to create storage server message because you already created the storage server on the other node when it was active. You do not need to complete the remainder of this procedure. It directs you to logon to the administrative Web UI and verify the presence of the PDDO client and data selection.

80 80 Installing the PDDO plug-in on a clustered NetBackup media server Installing the PDDO plug-in on a clustered NetBackup media server

81 Appendix B Repairing and removing a PDDO plug-in This appendix includes the following topics: Repairing a PDDO plug-in on a Linux or UNIX media server Repairing a PDDO plug-in on a Windows media server About removing a PDDO plug-in Repairing a PDDO plug-in on a Linux or UNIX media server The following procedure explains how to repair a PDDO plug-in on a Linux or UNIX media server. To repair a PDDO plug-in on a Linux or UNIX media server 1 Logon to the media server as root. 2 Stop NetBackup services. For information about how to stop services, see your NetBackup documentation. 3 Run the installer again. See About installing the PDDO plug-in on a NetBackup Linux media server or a NetBackup UNIX media server on page Start NetBackup services. For information about how to start services, see your NetBackup documentation.

82 82 Repairing and removing a PDDO plug-in Repairing a PDDO plug-in on a Windows media server Repairing a PDDO plug-in on a Windows media server The following procedure explains how to repair a PDDO plug-in on a Windows media server. To repair a PDDO plug-in on a Windows media server 1 Logon to the media server as administrator. 2 Stop NetBackup services. For information about how to stop services, see your NetBackup documentation. 3 Click one of the following icons to start the installation wizard: pdagent-windows_x xxxx.exe pdagent-windows_x86_ xxxx.exe 4 On the Welcome page, click Next. 5 On the Program Maintenance page, click Repair. 6 On the Ready to Install the Program page, click Install. 7 On the Installation Complete page, click Finish. 8 Start NetBackup services. For information about how to start services, see your NetBackup documentation. See About removing a PDDO plug-in on page 82. About removing a PDDO plug-in The procedures that you need to perform when you remove the plug-in differ depending on the following: Your reasons for removing the plug-in The number of media servers in your NetBackup environment that currently host a PDDO plug-in The following topics describe how to remove a PDDO plug-in from a NetBackup media server: Disconnecting the PureDisk storage pool from one media server that exists among many media servers See Disconnecting the PureDisk storage pool from one media server that exists among many media servers on page 83.

83 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 83 Disconnecting the PureDisk storage pool from the last media server and removing the PureDisk storage pool from the NetBackup environment See Disconnecting the PureDisk storage pool from the last media server and removing the PureDisk storage pool from the NetBackup environment on page 87. Removing a PDDO plug-in from a Linux or UNIX media server See Removing a PDDO plug-in from a Linux or UNIX media server on page 88. Removing a PDDO plug-in from a Windows media server See Removing a PDDO plug-in from a Windows media server on page 89. Removing the PureDisk information from the NetBackup catalog See Removing PDDO from the NetBackup catalog on page 89. Disconnecting the PureDisk storage pool from one media server that exists among many media servers The procedures in this topic explain how to retire and then remove the PDDO plug-in from one media server. This action disconnects the media server from the PureDisk storage pool. Perform the following procedures only if you have other NetBackup media servers in the environment that you can leave in a running and an operational state. After you perform these procedures, NetBackup distributes this media server s load to other media servers in the environment. These other media servers assume the backup load that NetBackup would have assigned to this media server when NetBackup tried to communicate with PureDisk. Do not perform the procedures in this topic under the following circumstances: This server is the last, and only, media server in your NetBackup environment. Instead, perform the procedure in the following topic to remove the PDDO capabilities from your only media server: See Disconnecting the PureDisk storage pool from the last media server and removing the PureDisk storage pool from the NetBackup environment on page 87. You intend to reinstall a PureDisk plug-in. You intend to remove an existing PureDisk plug-in and install a new PureDisk plug-in immediately after the removal. For example, you might upgrade a plug-in. More information about reinstalling and upgrading the PDDO plug-in exists. See the Upgrading PDDO clients topic in the Symantec NetBackup PureDisk Storage Pool Installation Guide.

84 84 Repairing and removing a PDDO plug-in About removing a PDDO plug-in The procedures in this topic are as follows: Dispense with the backup images that reside on the PureDisk storage pool. See To dispense with the backup images that reside on the PureDisk storage pool on page 84. Verify connections to the media server. If a policy is configured to send data to only one media server, that policy stops working when you delete the media server. Perform this procedure to find and respecify the policies that send data to the media server you want to delete. See To verify the PureDisk storage unit s media server connections on page 85. Remove a storage pool from a media server. See To remove the PureDisk storage pool from one media server on page 86. To dispense with the backup images that reside on the PureDisk storage pool 1 Decide if you want to destroy or to preserve the backup images that this media server wrote to this PureDisk storage pool. 2 Start the NetBackup Administration Console. 3 (Conditional) Destroy the current backup images. Warning: Perform this step only if you want to permanently destroy the backup images on this PureDisk storage pool. Use the Catalog utility to expire the backup images that reside on the PureDisk disk pool. This action removes the images from the NetBackup catalog. NetBackup subsequently removes the images from the disk pool.

85 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 85 4 (Conditional) Preserve the current backup images. Perform this step only if you want to retain the data on the PureDisk storage pool for later import into NetBackup. Use the bpexpdate(1m) command to expire the backup images from the NetBackup catalog but retain the data on the PureDisk storage pool. On Windows systems, specify the bpexpdate command with the following parameters: \install_path\bpexpdate -stype PureDisk -dp disk_pool_name -nodelete On Linux or UNIX systems, specify the bpexpdate command with the following parameters: # /usr/openv/bpexpdate -stype PureDisk -dp disk_pool_name -nodelete If the images are replicated to another PureDisk storage pool, import the exported images to another system. For example, you can import the images into a new NetBackup domain. Alternatively, you can perform catalog cleanup, recovery, and troubleshooting activities on the current NetBackup domain and reimport the images back to that original domain. 5 Verify that the storage unit and media server are connected. See To verify the PureDisk storage unit s media server connections on page 85. To verify the PureDisk storage unit s media server connections 1 Start the NetBackup Administration Console. 2 Click Storage > Storage Units. 3 Double-click the PureDisk storage unit. The Change Storage Unit page appears. 4 Review the following media servers specifications: If Use any available media server to transport data is selected, proceed to the following procedure: See To remove the PureDisk storage pool from one media server on page 86. If Use only the selected media servers is selected, proceed to the next step.

86 86 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 5 Examine the policies that send data to this media server, and respecify the policies to send data to a different media server. 6 Remove the PureDisk storage pool from one media server. See To remove the PureDisk storage pool from one media server on page 86. To remove the PureDisk storage pool from one media server 1 For every NetBackup storage unit that specifies that media server, clear the checkbox that specifies the media server. This step is not required if the storage unit is configured to use any available media server. 2 Use the tpconfig command to delete the storage pool authority credentials on the media server. The following is the path to the tpconfig command: Linux/UNIX: /usr/openv/volmgr/bin Windows: install_path\program Files\VERITAS\Volmgr\bin To delete the credentials, enter the following command: tpconfig -delete -storage_server server_name -stype PureDisk -sts_user_id user_id The following describe the options that require arguments: -storage_server server_name. The host name of the storage server. -stype PureDisk. A string that identifies the storage server type. For PDDO, this string is PureDisk. -sts_user_id user_id. The user name that is used to log into the storage server. If the storage server did not require logon credentials, enter the dummy credentials that were configured. If the host failed and is unavailable, you can use the tpconfig device configuration utility in menu mode to delete the credentials. However, you must run the tpconfig utility on a UNIX or Linux NetBackup server. For procedures, see the NetBackup Administrator s Guide for UNIX and Linux, Volume II. 3 Remove the PDDO plug-in from the media server. Use one of the following procedures, depending on the operating system platform of your media server: See Removing a PDDO plug-in from a Linux or UNIX media server on page 88. See Removing a PDDO plug-in from a Windows media server on page 89.

87 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 87 See About removing a PDDO plug-in on page 82. Disconnecting the PureDisk storage pool from the last media server and removing the PureDisk storage pool from the NetBackup environment This procedure deletes the NetBackup data mover and the NetBackup storage server that were associated with this particular PureDisk storage pool. After you complete this procedure, NetBackup can no longer send backups to the PureDisk storage pool or restore data from the PureDisk storage pool. Perform this procedure if all of the following conditions are true: You want to eliminate a particular PureDisk storage pool completely from a NetBackup environment. You have performed the following procedure on all but the last media server in your NetBackup environment. See Disconnecting the PureDisk storage pool from one media server that exists among many media servers on page 83. You have the PDDO plug-in installed on the last remaining media server. Do not perform this procedure if any of the following are true: You have a PDDO plug-in currently installed on more than one media server in your NetBackup environment. Instead, perform the following procedure. See Disconnecting the PureDisk storage pool from one media server that exists among many media servers on page 83. You intend to reinstall a PureDisk plug-in on this media server for upgrade purposes. To remove the PureDisk storage pool from NetBackup 1 Perform this procedure while the PureDisk storage pool is still connected to a media server. See To dispense with the backup images that reside on the PureDisk storage pool on page 84. This procedure explains how to destroy or preserve the data currently on the PureDisk storage pool that you want to remove. 2 Perform the procedure called Deleting an OpenStorage disk pool in the Symantec NetBackup OpenStorage Solutions Guide for Disk. 3 Perform the procedure called To retire an OpenStorage data mover in the Symantec NetBackup OpenStorage Solutions Guide for Disk.

88 88 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 4 Perform the procedure called Deleting an OpenStorage storage server in the Symantec NetBackup OpenStorage Solutions Guide for Disk. 5 Proceed to one of the following topics, depending on the operating system platform of your media server: See Removing a PDDO plug-in from a Linux or UNIX media server on page 88. See Removing a PDDO plug-in from a Windows media server on page 89. See About removing a PDDO plug-in on page 82. Removing a PDDO plug-in from a Linux or UNIX media server The following procedure explains how to remove a PDDO plug-in from a Linux or UNIX media server. Perform this procedure if you want to remove a PDDO plug-in. To remove a PDDO plug-in from a Linux or UNIX media server 1 Stop NetBackup services. For information about how to stop services, see your NetBackup documentation. 2 Type the following command to remove the software: # sh /install_path/pdag/bin/uninstall.sh For install_path, specify the path to where the PDDO plug-in is installed. The default is /opt. 3 Respond y to the following warning message: WARNING: If you remove the PDDO plug-in, NetBackup operations can fail. See the PureDisk Client Installation Guide for information about how to remove the PureDisk Deduplication Option software. => Do you want to continue? [y/n] y 4 Start NetBackup services. For information about how to start services, see your NetBackup documentation. 5 Remove PDDO from the NetBackup catalog. More information is available about this topic. See Removing PDDO from the NetBackup catalog on page 89.

89 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 89 See About removing a PDDO plug-in on page 82. Removing a PDDO plug-in from a Windows media server The following procedure explains how to remove a PDDO plug-in from a Windows media server. Perform this procedure if you want to remove a PDDO plug-in. To remove a PDDO plug-in from a Windows media server 1 Stop NetBackup services. For information about how to stop services, see your NetBackup documentation. 2 In the Windows interface, click Start > Settings > Control Panel > Add or Remove Programs. 3 Select Symantec NetBackup PureDisk Agent. 4 Click Remove. 5 Open the Microsoft Registry Editor (Start > Run > regedt32). 6 Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData. 7 Delete any references to the PDDO agent. 8 Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec. 9 Delete the PureDisk registry entry if it is present. 10 Start NetBackup services. For information about how to start services, see your NetBackup documentation. 11 Remove PDDO from the NetBackup catalog. More information is available about this topic. See Removing PDDO from the NetBackup catalog on page 89. See About removing a PDDO plug-in on page 82. Removing PDDO from the NetBackup catalog The following procedure explains how to remove any references to PureDisk from the NetBackup catalog. To delete PureDisk from the NetBackup catalog 1 Expire images in NetBackup. 2 Delete the PureDisk storage pool in NetBackup.

90 90 Repairing and removing a PDDO plug-in About removing a PDDO plug-in 3 Delete the PureDisk disk pool in NetBackup. 4 Delete any old storage_server_name.cfg files. These files are in /usr/openv/lib/ost-plugins for UNIX and Linux and in <install_path>\netbackup\bin\ost-plugins for Windows. For example, if the name of the PDDO server you removed was pddo_server_01, look for a pddo_server_01.cfg file. 5 Verify the PureDisk storage credentials are removed using the tpconfig command. Run the tpconfig command from the volmgr/bin directory. tpconfig -dsh -stype PureDisk The command displays all PureDisk open storage credentials. The credentials consist of the PDDO server name and the associated user name. If the credentials are still present, use the tpconfig command to remove them. tpconfig -delete -storage_server server_name -stype PureDisk -sts_user_id user_name Example: tpconfig -delete -storage_server pddo_server_01 -stype PureDisk -sts_user_id root 6 Delete the old PDDO storage pool with the nbdevconfig command. nbdevconfig -deletests -storage_server server_name -stype PureDisk Example: nbdevconfig -deletests -storage_server pddo_server_01 -stype PureDisk 7 Determine if there are any residual names still present on the system using the nbemmcmd. The nbemmcmd command displays information about known hosts so look for the host name of the deleted PDDO server. nbemmcmd -listhosts If the host name is still present, use the nbemmcmd to delete it from the EMM database. nbemmcmd -deletehost -machinename server_name -machinetype ndmp Example: nbemmcmd -deletehost -machinename pddo_server_01 -machinetype ndmp See About removing a PDDO plug-in on page 82.

91 Appendix C Configuration file settings This appendix includes the following topics: About the pd.conf file Editing the pd.conf file About pd.conf file settings About BANDWIDTH_LIMIT About OPTDUP_BANDWIDTH About bandwidthlimit About limiting bandwidth within a PureDisk environment About compression and encryption of backup images About compression and encryption of optimized duplicated data About log information About log information from NetBackup About log information from NetBackup or NetBackup About the pd.conf file After installation, the following files reside on the NetBackup client and the NetBackup media server: pd.conf, which includes several settings such as debugging and encryption. pd.conf.template, which is a backup file for pd.conf. Immediately after installation, this file is identical to pd.conf. This file s purpose is to act as a template file with the default configuration settings. If you edit pd.conf and

92 92 Configuration file settings Editing the pd.conf file later want to return pd.conf to its default settings, you can copy pd.conf.template to pd.conf. On Linux and UNIX platforms, these files reside in the following locations: /usr/openv/lib/ost-plugins/pd.conf /usr/openv/lib/ost-plugins/pd.conf.template On Windows platforms, these files reside in the following locations: install_path\veritas\netbackup\bin\ost-plugins\pd.conf install_path\veritas\netbackup\bin\ost-plugins\pd.conf.template See About pd.conf file settings on page 93. See Editing the pd.conf file on page 92. Editing the pd.conf file The default pd.conf file contains lines of comments. The following procedure explains how to change the settings when you want to enable more verbose logging. Note: The spaces to the left and right of the = sign in the pd.conf file are significant. Make sure that the space characters appear in the file after you edit the file. To edit the pd.conf file 1 Logon to the media server. 2 Use a text editor to open file pd.conf. 3 Remove the pound character (#) in column 1 from each line that you want to edit. 4 Specify a new value for each setting that you want to change. The spaces to the left and right of the = sign are significant. Make sure that the space characters appear in the file after you edit the file. More information about valid values is available. See About pd.conf file settings on page Close the file. See About the pd.conf file on page 91.

93 Configuration file settings About pd.conf file settings 93 About pd.conf file settings The following table lists the information that you can use to specify new values for settings in the pd.conf file. Table C-1 pd.conf file values Setting Default value Possible values Action BACKUPRESTORERANGE N/A N/A Allows an application server to use a specific NIC for backups and restores. The BACKUPRESTORERANGE value is specified in one of two ways. You can use Classless Inter-Domain Routing (CIDR) format. For example: BACKUPRESTORERANGE= /31 means IP addresses and are used for replication. You can enter multiple IP addresses that are separated with commas. For example: BACKUPRESTORERANGE= , means IP addresses and are used.

94 94 Configuration file settings About pd.conf file settings Table C-1 pd.conf file values (continued) Setting Default value Possible values Action BANDWIDTH_LIMIT 0 0 (default - no limit) to the practical system limit. Determines the maximum bandwidth that is allowed when backing up or restoring data between: The NetBackup client and a PDDO or an MSDP storage pool. The NetBackup media server and a PDDO or an MSDP storage pool. In the case of MSDP, the value applies only to the media servers that are used for deduplication. The value does not apply to the actual media server with MSDP. It also determines the maximum bandwidth between two PDDO storage pools during PDDO replication. The value is specified in kilobytes per second and applies on a per connection basis. The default is no limit. Symantec recommends setting this value to 0 (zero). More information about BANDWIDTH_LIMIT is available. See About BANDWIDTH_LIMIT on page 99. COMPRESSION 1 0 (off) or 1 (on) Specifies whether you want compression. By default, compression is enabled. If you want to disable compression, specify zero in this file. Symantec recommends setting this value to 1 See About compression and encryption of backup images on page 104. DEBUGLOG C:\pdplugin.log (Windows) Any path Writes the debugging log file, pdplugin.log, to the specified location. or /tmp/pdplugin.log (UNIX) If you request that log information be written to this file, remember to monitor the file. This file can grow to a significant size and fill the partition.

95 Configuration file settings About pd.conf file settings 95 Table C-1 pd.conf file values (continued) Setting Default value Possible values Action DONT_SEGMENT_TYPES N/A Any file extension Allows a list of file name extensions to be specified. Files in the backup stream having on of these extensions are given a single segment if smaller than 16MB. Larger files are deduplicated using the maximum 16MB segment size. Example: DONT_SEGMENT_TYPES = mp3,avi The purpose of the setting is to not waste effort analyzing and managing many segments within a file type which do not globally deduplicate. ENCRYPTION 0 0 (off) (default) or 1 (on) Specifies whether you want encryption. By default files are not encrypted. If you want encryption, specify one in this file. Symantec recommends setting this value to 0 (zero). See About compression and encryption of backup images on page 104.

96 96 Configuration file settings About pd.conf file settings Table C-1 pd.conf file values (continued) Setting Default value Possible values Action FP_CACHE_CLIENT_POLICY N/A N/A Used to specify a source fingerprint cache for the initial backup of a client. Use of this keyword improves the deduplication rate for initial backups and results in less data being transferred in the initial backup. The format for the keyword is: FP_CACHE_CLIENT_POLICY=client_host_machine,backup_policy_name,date Replace the three fields in the string as follows: client_host_machine: The name of the source seeding client. backup_policy_name: The name of the source seeding policy. date: The date when the seeding information expires. If the information is not expired, the seeding information is used for all backups, even after a full backup of the new client is performed. The format for date is mm/dd/yyyy. Note: This keyword only works with NetBackup and later and with appliances DAS and later. LOCAL_SETTINGS 0 0 (off) (default) or 1 (on) Allows the local values in the pd.conf file to override the default values. This setting must be enable for change to SEGKSIZE, MINFILE_KSIZE, MATCH_PDRO, and DONT_SEGMENT_TYPES to take affect. For the changes to take effect, LOCAL_SETTINGS = 1 must be set. LOGLEVEL 0 0 (default) and 5 through 10. Specifies the amount of logging that is written to the debugging log file. See About log information on page 105. PureDisk does not do any logging when the LOGLEVEL value is set from 0 to 4. Note: Do not change this setting unless told to do so by a Symantec Technical Support representative.

97 Configuration file settings About pd.conf file settings 97 Table C-1 pd.conf file values (continued) Setting Default value Possible values Action MAX_IMG_MBSIZE 50,000 0 to 50,000 This keyword is reserved for internal use. Note: Do not change this setting unless told to do so by a Symantec representative. MAX_LOG_MBSIZE OPT_DUP_WAIT_INTERVAL OPTDUP_BANDWITH to maximum file size supported by the operating system From 0 to the practical system limit. 0 (no limit) (default) to the practical system limit. Controls how large the pdplugin.log file becomes before a new log file is created. The value is specified in megabytes. When log files become too big, they are difficult to open, copy, and view. When log files are too small, you may have difficulty locating specific events or problems. The wait time between checks for job completion between the PDDO client and the PureDisk storage pool authority. The value is expressed in seconds. Determines the maximum bandwidth that is allowed when you replicate data (optimized-duplication) between a source and a destination storage pool. The value is specified in KBytes/second. The default is no limit (0). The OPTDUP_BANDWIDTH parameter affects only the jobs that originate from the media server upon which this parameter is set. If you use a value greater than the result is a bandwidth limit of KBytes/second. A value of 0 indicates that no restrictions are enforced on the bandwidth that are used by PureDisk. More information about OPTDUP_BANDWITH is available See About OPTDUP_BANDWIDTH on page 100.

98 98 Configuration file settings About pd.conf file settings Table C-1 pd.conf file values (continued) Setting Default value Possible values Action OPTDUP_COMPRESSION 1 1 (on) (default) or 0 (off) Determines if the optimized duplication data is compressed before transmission over the network. The default is compressed (1). If the target content router does not specify the compression setting, this value is used to control compression of optimized deduplication operations. If the target content router s contentrouter.cfg file specifies compression or no compression, then the OPTDUP_COMPRESSION setting is overridden. More information about compression is available. See About compression and encryption of optimized duplicated data on page 104. OPTDUP_ENCRYPTION 1 1 (on) (default) or 0 (off) Determines if the data being replicated is encrypted before it is sent out over the network. The default is encrypted (1). If the target content router does not specify the encryption setting, this value is used to control encryption of optimized deduplication operations. If the target content router s contentrouter.cfg file specifies encryption or no encryption, then the OPTDUP_ENCRYPTION setting is overridden. Symantec recommends setting this value to 1. More information about encryption is available. See About compression and encryption of optimized duplicated data on page 104. OPTDUP_TIMEOUT N/A Value expressed in minutes Specifies the number of minutes before the optimized duplication times out. Indicated in minutes. SEGKSIZE 128 N/A This keyword is reserved for internal use. Warning: Changing this value can lead to reduced capacity and decreased performance. Do not modify this setting unless directed by Symantec.

99 Configuration file settings About BANDWIDTH_LIMIT 99 Table C-1 pd.conf file values (continued) Setting Default value Possible values Action WS_RETRYCOUNT WS_TIMEOUT From 0 to the practical system limit. From 0 to the practical system limit. The WS_RETRYCOUNT parameter lets you configure the number of retries that are attempted in case the Web service fails out or times out. The default value is 3. The WS_TIMEOUT parameter lets you increase or decrease the timeout value for Web service calls made from NetBackup media servers to PureDisk storage units. The value is expressed in seconds. The default value is 120 seconds. Example. When you specify the MAX_LOG_MBSIZE parameter, rather than creating one large log file that is over 1 GB in size, the system creates multiple log files, as follows: For example, instead of the computer creating one file over 1 GB in size, multiple log files are created, as shown: -rw-rw-rw- 1 root root Aug 30 09: _0_pdplugin.log -rw-rw-rw- 1 root root Aug 30 09: _1_pdplugin.log -rw-rw-rw- 1 root root Aug 30 11: _2_pdplugin.log See About the pd.conf file on page 91. About BANDWIDTH_LIMIT The BANDWIDTH_LIMIT value determines the maximum bandwidth that is allowed when backing up or restoring data between: The NetBackup client and a PDDO or an MSDP storage pool. The NetBackup media server and a PDDO or an MSDP storage pool. In the case of MSDP, the value applies only to the media servers that are used for deduplication. The value does not apply to the actual media server with MSDP. This value does not affect optimized duplications. It determines the maximum bandwidth between two PDDO storage pools during PDDO replication. The value is specified in kilobytes per second not kilobits per second. It is a per job limit not a total limit to the system.

100 100 Configuration file settings About OPTDUP_BANDWIDTH If you have a T1 line that is 1544 kbps and you want the backup to use 20% of the bandwidth, multiply 1544 by 0.2, and multiple the resulting value by *0.2= *0.125=38 You need to specify BANDWIDTH_LIMIT=38 in pd.conf file not BANDWIDTH_LIMIT=308. When BANDWIDTH_LIMIT=X, PureDisk sends out X*1024 bytes of data. PureDisk then sleeps for about one second before it sends the next X*1024 bytes of data. This behavior is to make sure that the network usage is within the specified limit in every second. For example, when BANDWIDTH_LIMIT=38, PureDisk sends out 38*1024 bytes of data and then waits about one second. Then PureDisk sends the next 38*1024 bytes of data. The BANDWIDTH_LIMIT value that is specified in the pd.conf file applies on a per connection basis. If you specified BANDWIDTH_LIMIT=38 and have two replication jobs, a maximum of 2*(38*1024) bytes of data are sent every second. When determining how much bandwidth to use, divide the bandwidth limit by the number of replication jobs. If you have a total of N concurrent jobs, divide the bandwidth limit by N. So if you want to limit the bandwidth usage to 38 kilobytes per second and you expect two replication jobs, specify BANDWIDTH_LIMIT=19. You can limit the maximum number of replication jobs by creating setting the maximum concurrency value for the NetBackup storage unit. You can set the BANDWIDTH_LIMIT value in the pd.conf file of both client computers and media servers. The value only affects the streams that are local to where the value is specified. If you specify the BANDWIDTH_LIMIT value on the media server, each stream on that media server is limited to the specified amount of bandwidth when it sends data to the content router. If you specify the BANDWIDTH_LIMIT value on a client, for client directed actions, each stream on that client is limited to the specified amount of bandwidth when it sends data to the content router. See About the pd.conf file on page 91. About OPTDUP_BANDWIDTH OPTDUP_BANDWITH limits the replication bandwidth that is used between the source computer and the destination or the target NetBackup deduplication pools when performing optimized deduplication. Either PDDO or MSDP can be the destination

101 Configuration file settings About bandwidthlimit 101 or the target pool. When OPTDUP_BANDWITH is specified on the computer initiating the optimized deduplication, the parameter is passed to the computer sending the data. While both OPTDUP_BANDWITH and BANDWIDTH_LIMIT affect bandwidth, the values affect different operations. Setting the OPTDUP_BANDWIDTH parameter on a NetBackup client has no effect since NetBackup clients don t initiate optimized duplication. The setting applies on a per connection basis. If you have a bandwidth limit of 30 KB/s and 2 duplication jobs running simultaneously, you may send more than 30KB/s of data through the network. The OPTDUP_BANDWIDTH parameter only affects the replication that originates from the media server where it is set. See About the pd.conf file on page 91. About bandwidthlimit The bandwidthlimit value controls replication bandwidth for the entire PureDisk environment. The bandwidthlimit value is set in the agent.cfg file. The bandwidthlimit value is set in kilobytes per second. The agent.cfg file is located in storage_path/etc/puredisk for UNIX/Linux and in storage_path\etc\puredisk for Windows. When you set the bandwidthlimit parameter on the PureDisk storage pool, it applies to all of the storage pool's replication jobs to all storage pools. Note: The bandwidthlimit value was introduced in the following software versions: PureDisk 6.6.3a, Deduplication Appliance Software 1.4.1, and NetBackup The NetBackup environment must be at NetBackup for the bandwidthlimit value to control bandwidth. The bandwidthlimit parameter is different from the BANDWIDTH_LIMIT parameter. Changing the BANDWIDTH_LIMIT parameter does not affect the entire PureDisk replication environment. Since the bandwidthlimit value applies to the entire PureDisk environment, the value bandwidthlimit=30 indicates all PureDisk replication jobs within the environment can use a total of 30 KB/s of bandwidth. See About limiting bandwidth within a PureDisk environment on page 102.

102 102 Configuration file settings About limiting bandwidth within a PureDisk environment About limiting bandwidth within a PureDisk environment Bandwidth usage within PureDisk is dependent on three variables and the PureDisk activity. Table C-2 Variable Bandwidth throttling variables Details BANDWIDTH_LIMIT The BANDWIDTH_LIMIT value is used to control the bandwidth that is used by backup and restore operations between a NetBackup media server or client and PDDDO or MSDP. The BANDWIDTH_LIMIT variable is the only variable that affects bandwidth usage for backup and restore operations. The value is set in the pd.conf file. The value is expressed in kilobytes per second (KB/s). The value is used on a per job or per connection basis. More information about the BANDWIDTH_LIMIT value is available. See About BANDWIDTH_LIMIT on page 99. OPTDUP_BANDWIDTH The OPTDUP_BANDWIDTH value is used to control bandwidth that is used by optimized deduplication operations. The OPTDUP_BANDWIDTH variable is one of two variables that affect bandwidth usage for optimized deduplication operations. The value is set in the pd.conf file. The value is expressed in kilobytes per second (KB/s). The value is used on a per job or per connection basis. More information about the OPTDUP_BANDWIDTH value is available. See About OPTDUP_BANDWIDTH on page 100.

103 Configuration file settings About limiting bandwidth within a PureDisk environment 103 Table C-2 Variable Bandwidth throttling variables (continued) Details bandwidthlimit The bandwidthlimit value is used to control bandwidth that is used by optimized deduplication operations. The bandwidthlimit variable is one of two variables that affect bandwidth usage for optimized deduplication operations. The value is set in the agent.cfg file. The value is expressed in kilobytes per second (KB/s). The value is used for the entire PureDisk replication environment. More information about the bandwidthlimit value is available. See About bandwidthlimit on page 101. When you attempt to throttle bandwidth, you must know which activity you want to control before you can adjust the variables. Since BANDWIDTH_LIMIT only affects back up and restore operations, that is the only variable you need to adjust. If you want to control bandwidth for optimized deduplications, use OPTDUP_BANDWIDTH when you want to control bandwidth on a per job basis. You must change the bandwidthlimit value if you want to control bandwidth for the entire PureDisk environment. Note: Please be aware the bandwidthlimit parameter is different from the BANDWIDTH_LIMIT parameter. Changing the BANDWIDTH_LIMIT parameter does not affect the entire PureDisk replication environment. Since both OPTDUP_BANDWIDTH and bandwidthlimit affect bandwidth for optimized deduplications, it is important to understand how the values interact when both are used in the same environment. The following examples details the interaction of the two values. Example 1. For the following settings, the result is that every replication stream has unlimited bandwidth: In agent.cfg, bandwidthlimit=0. In pd.conf, OPTDUP_BANDWIDTH=0. Example 2. For the following settings, the result is that replication streams have a total of 30 KB/s of bandwidth available to share: In agent.cfg, bandwidthlimit=30.

104 104 Configuration file settings About compression and encryption of backup images In pd.conf, OPTDUP_BANDWIDTH=0. Example 3. For the following settings, the result is that replication streams have a total of 30 KB/s of bandwidth available to share: In agent.cfg, bandwidthlimit=30. In pd.conf, OPTDUP_BANDWIDTH=50. Example 4. For the following settings, the result is that replication streams that originate from the media server with OPTDUP_BANDWIDTH=20 are each limited to 20 KB/s. All other replication streams have unlimited bandwidth. The settings are as follows: In agent.cfg, bandwidthlimit=0. In pd.conf, OPTDUP_BANDWIDTH=20. See About the pd.conf file on page 91. About compression and encryption of backup images When you specify compression or encryption in a NetBackup policy, NetBackup compresses or encrypts the files on the client. Then, it writes the backup images to the media server. When you write these backup images to a media server, PureDisk cannot deduplicate the files. Symantec recommends that you disable compression and encryption in the NetBackup policies that write to PureDisk disk pools. You can enable compression and encryption on both media servers and client computers. Enable compression and encryption on the computer where deduplication occurs. In order for NetBackup to compress or encrypt the deduplicated images, specify compression or encryption in the media server s pd.conf file. To enable compression, set COMPRESSION = 1 in the pd.conf file. To enable encryption, set ENCRYPTION = 1 in the pd.conf file. See About the pd.conf file on page 91. About compression and encryption of optimized duplicated data Depending on the state of the data, the data may need to be either uncompressed or decrypted before the optimized deduplication process. Use the following table to understand the process.

105 Configuration file settings About log information 105 Table C-3 Status of data on the source computer Replication requirements on the media server Action taken Compressed but not encrypted Compressed and encrypted The encryption engine decompresses the data and then encrypts and compresses it. Not compressed but encrypted Compressed and encrypted The encryption engine decrypts the data and then encrypts and compresses it. Compressed and encrypted Compressed and encrypted Uncompressed and unencrypted Uncompressed and unencrypted Compressed and encrypted Compression and encryption is not specified. Compression and encryption is not specified. Compressed but not encrypted. No action taken. Data is sent through the optimize deduplication process without passing through the encryption engine. The data is, however, both encrypted and compressed, since it is encrypted and compressed on the source computer. No action taken. Data is sent through the optimize deduplication process without passing through the encryption engine. The data is, however, both encrypted and compressed, since it is encrypted and compressed on the source computer. No action taken. Data is sent through the optimize deduplication process without passing through the encryption engine. The data remains uncompressed and unencrypted. The encryption engine compresses the data and but does not encrypt it. See About the pd.conf file on page 91. About log information To obtain log information from NetBackup regarding backups to the PureDisk storage pool, review the log files or NetBackup s Job Details report. For specific system-related log information, see the following topics: Log information from NetBackup See About log information from NetBackup on page 106. Log information from NetBackup or NetBackup 6.5.0

106 106 Configuration file settings About log information from NetBackup See About log information from NetBackup or NetBackup on page 106. See About the pd.conf file on page 91. About log information from NetBackup To view a detailed log report, double-click a completed backup job that wrote to the PureDisk storage pool. For more information about how to obtain a job details report, see your NetBackup documentation. This report identifies deduplication rates for the PureDisk storage server in the dedup field. The following example shows what appears in a Job Details report from a NetBackup system: 04/22/ :10:11 - Info mediaserver.acme.com (pid=24510) StorageServer=PureDisk:storageserver.acme.com; Report=PDDO Stats for (storageserver.acme.com): scanned: 36 KB, stream rate: 0.06 MB/sec, CR sent: 1 KB, dedup: 97.2%, cache hits: 1 (9.1%) See About log information on page 105. About log information from NetBackup or NetBackup You can obtain PDDO backup statistics from the bptm log file. This output identifies deduplication rates for the PureDisk storage server in the dedup field. The following example shows what appears in a bptm log file from NetBackup 6.5 on a Windows system: 14:20: [ ] <16> storageserver.acme.com: PDDO Stats for (storageserver.acme.com): scanned: 36 KB, stream rate: 0.04 MB/sec, CR sent: 0 KB, dedup: 100.0%, cache hits: 1 (9.1%) See About log information on page 105.

107 Appendix D Troubleshooting This appendix includes the following topics: Troubleshooting a failed PDDO configuration Troubleshooting a failed PDDO configuration If NetBackup issues errors or if the installation fails, use one or more of the procedures in this topic to resolve the problem.

108 108 Troubleshooting Troubleshooting a failed PDDO configuration To troubleshoot a failed configuration - part 1 1 Restart the NetBackup remote monitor and manager service, nbrmms, and verify that it is running. For information about how to restart nbrmms, see your NetBackup documentation. 2 Verify that NetBackup can load the PDDO plug-in. Type one of the following commands as appropriate to the server: On Linux or UNIX media servers, type the following command: # /usr/openv/netbackup/bin/admincmd/bpstsinfo -pi On Windows media servers, type the following command: C:Program Files\Veritas\NetBackup\bin\admincmd\bpstsinfo -pi The bpstsinfo command generates an output that contains the following block of information on a correctly configured system: Plugin Name: libstspipdmt.so Prefix: PureDisk: Label: OpenStorage PureDisk Plugin Build Version: 9 Build Version Minor: 4 Operating Version: 9 Vendor Version: :55:00 Feb Make sure that the line Prefix: PureDisk: appears in the output.

109 Troubleshooting Troubleshooting a failed PDDO configuration 109 To troubleshoot a failed configuration - part 2 1 Enable configuration logging. On Linux or UNIX media servers, type the following command: # mkdir -p /usr/openv/volmgr/debug/tpcommand On Windows media servers, type the following commands: C:> cd "Program Files\Veritas\Volmgr\bin" C:Program Files\Veritas\Volmgr\bin> mkdir tpcommand 2 Run the pddocfg command. For Linux or UNIX: See Establishing the PDDO connection between a Linux media server or a UNIX NetBackup media server and the PureDisk storage pool on page 29. For Windows: See Establishing a connection between a Windows NetBackup media server and the PureDisk storage pool on page Examine the messages that the pddocfg command writes to the log file in directory /usr/openv/volmgr/tpcommand. If failure messages appear in the log file, the pddocfg command failed after or during the ndevconfig or tpconfig phase. Remove directory /usr/openv/volmgr/tpcommand when you finish examining the file for failure messages. If failure messages do not appear in the log file, proceed to the next step.

110 110 Troubleshooting Troubleshooting a failed PDDO configuration 4 Examine /usr/openv/lib/ost-plugins to verify that there is a file called spa.cfg. spa is the host name of the storage pool authority that you used as storage server. 5 Type the following command to examine the file in /opt/pdag/var/rt and verify that the routing table files for the storage pool ID are present: # ls /opt/pdag/var/rt On a Windows media server, type the following command: C:\Program Files\Symantec\NetBackup PureDisk Agent\var\rt Two files should reside in this directory. For example, in a correctly configured Linux system, this command returns output similar to the following: 111.current 111.recommended In this example, 111 is the storage pool ID. To verify that NetBackup can communicate with the PDDO plug-in 1 Type the following command to verify that NetBackup can communicate with the PDDO plug-in: # /usr/openv/netbackup/bin/admincmd/bpstsinfo -si -sp PureDisk: -sn spa On a Windows media server, type the following command: C:Program Files\Veritas\NetBackup\bin\admincmd\bpstsinfo -pi For spa, specify the name of the storage server. On a correctly configured Linux or UNIX system, the output is similar to the following: /usr/openv/netbackup/bin/admincmd/bpstsinfo -si -sp PureDisk: -sn myspa Server Info: Server Name: PureDisk:myspa Supported Stream Formats: [ ] Server Flags: (STS_SRV_ASYNC STS_SRV_IMAGELIST STS_SRV_CRED STS_SRV_CONRW) Maximum Connections: 0 Current Connections: 1 Supported Interfaces: [

111 Troubleshooting Troubleshooting a failed PDDO configuration 111 ] Supported Credentials: [ ] On a correctly configured Windows system, the output is similar to the following: Server Info: Server Name: PureDisk:myspa Supported Stream Formats: [ ] STS_SRV_CONRW) Server Flags: (STS_SRV_ASYNC STS_SRV_IMAGELIST STS_SRV_CRED Maximum Connections: 0 Current Connections: 1 Supported Interfaces: [ ] Supported Credentials: [ ] 2 If NetBackup cannot communicate to the PDDO plug-in using bpstsinfo and the pddocfg command completed successfully, enable NetBackup logging at the verbose 5 level. Then rerun the bpstsinfo command and check the NetBackup log located in the following directory: /usr/openv/netbackup/logs/admin For more information about how to enable NetBackup logging, see your NetBackup documentation.

112 112 Troubleshooting Troubleshooting a failed PDDO configuration To restart the NetBackup disk pool graphical user interface wizard 1 If the bpstsinfo succeeds but the NetBackup disk pool graphical user interface wizard fails, close the wizard, if necessary, and then restart it. 2 If the wizard still fails after you restart it, enable logging. On a Linux or UNIX media server, use a text editor to edit the file /usr/openv/lib/ost-plugins/pd.conf In the pd.conf file, un-comment the following lines: LOGLEVEL = 10 DEBUGLOG = /tmp/pdplugin.log On a Windows media server, use a text editor to edit the file C:\Program Files\Veritas\NetBackup\bin\ost-plugins\pd.conf In the pd.conf file, un-comment the following lines: LOGLEVEL = 10 DEBUGLOG = C:\pdplugin.log 3 Run the wizard again and check the pdplugin.log file. If the wizard continues to fail, something similar to the following should be seen in the log file: 11/04/08 12:24:13 [19545] [3] pi_open_server_v7 exit ( :authorization failure) 0 If the wizard works, something like the following should be seen in the log file: 11/04/08 12:24:12 [19544] [3] pi_open_server_v7 exit (0:OK) 0 4 Disable PDDO logging when you finish. Logging affects performance. Alternatively, you can set the LOGLEVEL down. Valid log levels range from 1 (error) to 10 (very verbose).

113 Appendix E Third-party legal notices This appendix includes the following topics: Third-party legal notices for the Symantec NetBackup PureDisk product family Third-party trademarks for the Symantec NetBackup PureDisk product family Third-party legal notices for the Symantec NetBackup PureDisk product family Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in NetBackup Product Family Third-party Legal Notices. Third-party trademarks for the Symantec NetBackup PureDisk product family Active Directory, Excel, Hyper-V, Internet Explorer, Microsoft, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. AIX, IBM, PowerPC, and Tivoli are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. AMD is a trademark of Advanced Micro Devices, Inc.

114 114 Third-party legal notices Third-party trademarks for the Symantec NetBackup PureDisk product family Firefox and Mozilla are registered trademarks of the Mozilla Foundation. Intel, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java, Sun, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States and other countries. Mac OS is a trademark of Apple Inc., registered in the U.S. and other countries. Nessus is a trademark of Tenable Network Security, Inc. NetApp is a registered trademark of Network Appliance, Inc. in the U.S. and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. OpenLDAP is a registered trademark of the OpenLDAP Foundation. Oracle is a registered trademark of Oracle and/or its affiliates. Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc., in the United States and other countries. UNIX is a registered trademark of The Open Group. VMware, vsphere, and the VMware "boxes" logo and design are trademarks or registered trademark of VMware, Inc., in the United States and other countries.

115 Index A agent dashboard display 64 agents installing PureDisk agent on Windows clients 28, 35 B backup images compression and encryption 104 bandwidth throttling throttling bandwidth 102 BANDWIDTH_LIMIT value 99 bandwidthlimit value 101 C central reporting 63 change the root user password on the storage pool authority 65 clients distributing software to 22 unattended installation on Windows 28, 35 compression and encryption backup images 104 optimized deduplicated 104 configuration example disaster recovery 58 configuration examples PDDO 13 configure NetBackup disk pool and OpenStorage unit 46 configuring NetBackup lifecycle policies 57 PureDisk disk pool and storage unit 44 D data mining reports 63 deduplication example 13 disaster recovery configuration example 58 disconnecting from one media server PureDisk storage pool 83 displaying agent dashboard 64 downloading PDDO plug-in 19 downloading to a media server PDDO plug-in 22 E editing pd.conf file 92 environment verify 20 examples deduplication 13 multistreaming 14 replication 15 F failed PDDO configuration troubleshooting 107 G garbage collection policies PureDisk 60 I improvements synthetic backup process 16 information log 105

116 116 Index installation clients distributing software to 22 unattended for clients for Windows clients 28, 35 installing on a clustered NetBackup media server PDDO plug-in 77 J job details reports 61 job report retrieval 61 L Linux or UNIX media server 89 removing a PDDO plug-in 88 repairing a PDDO plug-in 81 log information 105 log information NetBackup or NetBackup NetBackup M multistreaming example 14 N NetBackup or NetBackup log information 106 NetBackup log information 106 NetBackup configuration verification 48 NetBackup disk pool and OpenStorage unit configure 46 NetBackup lifecycle policies configuring 57 NetBackup media server adding an additional PureDisk storage pool 55 NetBackup policy creating 48 NetBackup PureDisk Deduplication Option (PDDO) overview 11 O OPTDUP_BANDWIDTH value 100 optimized deduplicated compression and encryption 104 overview NetBackup PureDisk Deduplication Option (PDDO) 11 product 11 P pd.conf file editing 92 locations 91 settings 93 pdag command client installation on Windows 28, 35 PDDO configuration examples 13 PDDO connection between a Linux media server or UNIX NetBackup media server and PureDisk storage pool 29 PDDO license verifying or installing 21 PDDO plug-in attended install on a Linux or UNIX media server 26 attended installation on a Windows media server 34 configure to store NetBackup optimized synthetic full backups 50 configured in NetBackup 43 downloading 19 downloading to a media server 22 in PureDisk administrative Web UI 54 installation on a Windows media server 33 installing on a clustered NetBackup media server 77 installing on NetBackup Linux media server or NetBackup UNIX media server 25 removal 82 removing a PDDO plug-in 89 removing from a Linux or UNIX media server 88 removing from a Windows media server 89 repairing on a Linux or UNIX media server 81 repairing on a Windows media server 82 unattended install on a Linux or UNIX media server 28

117 Index 117 PDDO plug-in (continued) unattended installation on a Windows media server 35 PureDisk garbage collection policies 60 PureDisk agent installing on Windows clients client 28, 35 PureDisk disk pool and storage unit configuring 44 PureDisk storage pool adding additional one to NetBackup media server 55 connection with a Windows NetBackup media server 37 disconnecting from one media server 83 removing from NetBackup environment 87 PureDisk storage pool used as PDDO plug-in recovery 64 R recovery PureDisk storage pool used as a PDDO plug-in 64 removal PDDO plug-in 82 removing from NetBackup environment PureDisk storage pool 87 replication example 15 reports data mining 63 job details 61 retrieving job reports 61 V value BANDWIDTH_LIMIT 99 bandwidthlimit 101 OPTDUP_BANDWIDTH 100 verification NetBackup configuration 48 verify environment 20 verifying or installing PDDO license 21 W Windows media server 89 PDDO plug-in attended installation 34 PDDO plug-in installation 33 PDDO plug-in unattended installation 35 removing a PDDO plug-in 89 repairing a PDDO plug-in 82 S settings pd.conf file 93 storage pool authority change the root user password 65 synthetic backup process improvements 16 T troubleshooting failed PDDO configuration 107

118 118 Index

119 Glossary absolute path ACL (access control list) active agent active node Agent Files and Folders data selection All-in-one storage pool alternate client ATOP (All Through One Port) attended installation authentication broker backup backup operator backup streams backup window CA (Certificate Authority) The location of a given file or directory on a file system regardless of the current working directory. The information that identifies specific users or groups and their access privileges for a particular file or directory. The PureDisk software that is enabled for use within a PureDisk environment. The PureDisk agent (the software) is installed on clients (the hardware). The nodes in a high availability cluster on which services are running. A collection of files, folders, or directories to be backed up. PureDisk creates this data selection automatically when you perform a full system backup. A PureDisk storage pool with all PureDisk services installed on one node. A client other than the source client that receives restored files. If the data is not restored to the original client, the client that is designated to receive the data is the alternate client. See single-port communication. An installation that requires active interaction with a person. The process that communicates with a root broker to verify user identities. A process where selected files on a computer drive are copied and stored on a reliable form of media. A user or a group of users with the rights to initiate client backups. A connection between the PureDisk client and the PureDisk content router through which data is sent. In case of multistreaming, the client establishes multiple connections to the same content router and distributes the total volume of backup data over all available connections. Multistreamed backups (vs. single streamed) increase the aggregated throughput from client to content router, thus allowing backups to finish sooner. The timeframe in which backups are permitted. A trusted third-party organization or company that issues digital certificates that are used to create digital signatures and public-private key pairs. The role of the CA in this process is to guarantee that the entity granting the unique certificate

120 120 Glossary is, in fact, who it claims to be. This means that the CA usually has an arrangement with the requesting entity to confirm a claimed identity. CAs are a critical component in data security and electronic commerce because they guarantee that the two parties exchanging information are really who they claim to be. central reporting CIFS (Common Internet File System) cluster common root configuration files content router content router garbage collection CSV (comma-separated variable) file data lock password data mining data removal data selection A PureDisk feature in which one or more storage pools send reporting data to another storage pool. A protocol that defines a standard for remote file access. CIFS allows users with different platforms and computers can share files. A set of hosts (each termed a node) that share a set of disks and are connected by a set of redundant heartbeat networks. A shared directory structure. Common root is a concept applicable to data restore. When the user restores the data, there is a Do not restore common root option. The user can enable or disable the feature. The files that define PureDisk s methods and assumptions. A custom configuration file for each component is created automatically by the storage pool authority. It is pushed out to the component for which this file is created. If you need to tune any of the default PureDisk processes, you can edit the configuration files. A service that stores and retrieves file content. PureDisk breaks larger files into segments and distributes the segments across the available content routers. The process of removing unneeded data objects and files from the content router. This workflow removes files and objects that cannot be removed during the normal data removal process. A text file that uses commas as data delimiters. An option that allows the administrator to require users to enter a password before they perform certain operations. These operations include any operation that exposes directory names, directory content, file names, or file content. The process of collecting information about all the files in a PureDisk storage pool. The process of removing old and unneeded versions of the files that PureDisk previously backed up. A list of files, directories, or other data objects that you want PureDisk to back up. They can be used to specify files and folders, databases, system information, and other types of data. After a data selection is created, it can be backed up automatically (through a policy) or on demand (initiated by a backup operator).

121 Glossary 121 data selection removal data selection template deduplication department disabled data selection disabled policy disaster recovery DMP (dynamic multipathing) enabled data selection enabled policy escalation action event event escalation action exclude files exclusion rules expert installation method The process of removing the entire data selection (including file content data) from the content router. This process also removes the associated metadata information from the metabase engine. A pattern that is used for creating the list of files, directories, or other data objects for PureDisk to back up. Templates can be developed that include or exclude certain file types, or that back up a specific directory. PureDisk includes some default data selection templates. The process of dividing a file into segments, comparing each segment with the previously stored file segments, and then storing only the unique segments. Deduplication significantly reduces the amount of data that is stored because redundant data is replaced with a pointer to the unique data copy. A logical collection of client systems. A data selection that PureDisk ignores when it performs policy-based actions. If a policy includes deactivated data objects, the policy does not include them when the policy runs. A policy that exists in the PureDisk environment but that is currently not activated. No jobs are created for this policy. The process of restoring information from a backup after the original data was lost (due to a disaster) or deleted. An input/output (I/O) enhancement technique that balances I/O across many available paths from the computer to the storage device to improve performance and availability. An activated list of files, directories, or other data objects that PureDisk uses for back ups and other policy-based actions. A policy that exists in the PureDisk environment that is currently activated and run according to a schedule. PureDisk automatically creates jobs to run this policy. A defined procedure that takes place when an event occurs. A significant occurrence in a system or application that a program detects. Events typically trigger actions, such as sending a user notification or adding a log entry. A defined procedure that takes place when a specific notable occurrence takes place. A listing of files or file patterns that are not included in a data selection. The means by which PureDisk determines the files or folders that should not be part of a given data selection. See also inclusion rules. The process of loading the PDLinux software onto a computer with multiple hard drives where none of the options is predefined.

122 122 Glossary external authentication failover A credential verification authority that resides on a computer that is not part of a PureDisk storage pool. The process of moving services from the active node in a cluster to a passive one. file change rate file pattern file system browsing Files and Folders data selection fingerprint folder pattern FQDN (fully qualified domain name) garbage collection HCL (hardware compatibility list) heartbeat high availability host address inactive agent include files inclusion rules inheritance job The frequency with which files on a client system are modified. A character sequence that includes wild cards and instructs PureDisk to select multiple files based on the character sequence. The ability to search through a graphic representation of a computer system s file structure. A data selection that is used to back up files, folders, and directories. A unique sequence of digits identifying a file or a file segment. The fingerprint of a file or segment is computed from the file or segment s content and is unique for that file or segment. An absolute path that may contain wild cards and instructs PureDisk to select folders based on the character sequence. An unambiguous domain name that specifies the exact location of a computer within the domain's hierarchy. The process of removing stale data or records from PureDisk that cannot be removed during the normal data removal process. A document that indicates the various components that are known to work with a given software product. A signal sent at regular intervals to indicate that a host and its connections are operating normally. A system or a resource that is continuously operational. The TCP/IP address of a computer. A client computer that is registered to the storage pool authority, but which is not yet acknowledged as part of the PureDisk environment. A listing of files or file patterns that are included in a data selection. The means by which PureDisk determines the files to consider as part of a given backup. See also exclusion rules. The process of receiving attributes from a parent object, such as a template. An operation that has been scheduled for processing. Jobs contain source or destination information, settings, and a schedule.

123 Glossary 123 LDAP (Lightweight Directory Access Protocol) location mapped network drive mapping file metabase metabase engine metabase garbage collection metabase server metadata Microsoft Exchange data selection Microsoft SQL data selection multinode storage pool A software protocol that enables anyone to locate organizations, individuals, and other resources such as files and devices in a network, whether on the Internet or on a corporate intranet. LDAP is a lightweight (smaller amount of code) version of Directory Access Protocol (DAP), which is part of X.500, a standard for directory services in a network. A logical grouping of one or more departments. A location does not need to be a physical or a geographic location. A persistent connection within Microsoft Windows to a shared directory on a remote server that is assigned a drive letter. The drive mapping may or may not survive a restart, depending on how it is configured. A two-column file that lists both IP addresses and fully qualified domain names (FQDNs) for each node. Mapping files are used when redefining a PureDisk environment to use either FQDNs or IP addresses. A distributed database that contains all the metadata about the files that are backed up by PureDisk. The service that maintains and manages file metadata information in the metabase database. During backup, the PureDisk agent records all relevant metadata information (the file attributes) of each file it backs up. File attributes include the file name, its location, its size, its type, and so on. The metabase engine stores these metadata records in its database. The metabase engine manages an inventory of all files that are backed up. The process of removing the stale, unneeded information from the metabase that cannot be removed during the normal data removal process. The service that redirects metabase queries to the correct metabase engine(s). Each metabase engine in the storage pool is responsible for managing the metadata records from a group of agents. Queries for a file or files do not go directly to the metabase engine but instead are directed to the metabase server. The metabase server redirects the query to the metabase engine that manages the metadata records of the agent that made the query or to which the query is associated. In some cases the metabase server may have to redirect the incoming query to multiple metabase engines. Structural data describing the attributes of files on a disk. A predefined data selection within PureDisk that backs up Microsoft Exchange server databases. A predefined data selection within PureDisk that backs up Microsoft SQL server databases. A storage pool that includes more than one PDLinux server node and can be clustered.

124 124 Glossary multistreaming NetBackup export engine network drive node OpenLDAP (Open Lightweight Directory Access Protocol) Oracle data selection parallel rerouting passive node path PDDO (PureDisk deduplication option) PDLinux (PureDisk Linux) policy policy escalation action private network private NIC public network public NIC registration The process of establishing multiple connections to the content router for the purposes of backing up data faster. An optional service that allows backed up PureDisk Files and Folders data selections to be exported to NetBackup. The NetBackup export engine does not export other PureDisk data selection types. A directory on a remote server that is designated as shared. A computer in a storage pool that hosts PDLinux and other PureDisk services. A network protocol that is designed to work on TCP/IP stacks. It extracts information from a hierarchical directory such as X.500. This software gives users a single tool to find a particular piece of information. For example, a user can find a user name, an address, security certificate, or other contact information. A predefined data selection within PureDisk that backs up Oracle databases. The process of redistributing data among the content routers in a PureDisk storage pool. All content routers are actively involved in the redistribution at the same time. Any node in a highly available, clustered environment that is not running PureDisk services. The directory location of a given file or directory on a file system. Paths can be either relative or absolute. A plug-in that uses the NetBackup OpenStorage API to enable NetBackup to write backups to a PureDisk storage pool. All NetBackup data that is written to a PureDisk storage pool is deduplicated. The operating system that hosts the PureDisk application. Symantec developed PDLinux based on SUSE Linux Enterprise Server. A method for managing backup jobs and strategies. Policies contain settings for jobs. A procedure that is defined to take place when a specific policy event (such as a backup failure) takes place. A computer network that is accessible only by other servers, not by the general user base. A network interface card that communicates to a private network. A computer network that is accessible to the general user base. A network interface card that communicates to a public network. The process of enrolling with the storage pool authority.

125 Glossary 125 relative path replication rerouting resource name root broker segment segmentation segmentation threshold serial rerouting service service address service group shared disk shared folder silent installation single port communication The directory location of a given file or directory on a file system that depends on the current working directory. The process of copying backed up data selections from one storage pool to another storage pool. The process of redistributing data over all available content routers. When the process finishes, each content router stores a volume of data proportional to its relative capacity. Rerouting is necessary when a new content router is activated, or an existing content router is deactivated. The unique identifier for a service on a PureDisk node. The authentication authority in the network. A root broker is local when it resides on the same physical computer as the PureDisk storage pool authority. A root broker is remote when it resides on a different PureDisk computer in the network. A root broker is external when it does not reside on any PureDisk computer within the storage pool. A piece of a file. The process of breaking a file down into smaller pieces for backup. The maximum allowable size for a file fragment. The process of redistributing data among the content routers in a PureDisk storage pool. Only one content router redistributes data at a time. A PureDisk software component. The possible services are as follows: content router, metabase engine, metabase server, storage pool authority, and NetBackup export engine. The TCP/IP address associated with a service group. A collection of PureDisk services. A physical hard drive on a computer that can be remotely accessed from another computer. In a highly available cluster, the shared disk is normally a drive that does not physically reside in any of the cluster nodes. Any resources that can failover among cluster nodes must reside on a shared disk. A network directory, to which multiple users have read and write access, used to exchange files with other users. An installation in which the user sees no indication that the installation is occurring. The user is not prompted to enter any information and the user does not see status messages. See also attended installation. A PureDisk feature that directs all network communication through one port. Storage pools that implement single-port communication require fewer firewall ports to be open between PureDisk service agents and clients.

126 126 Glossary snapshot SPA (storage pool authority) SPAR (storage pool authority replication) storage pool stream SUSE System State and Services data selection template inheritance TLS (transport security layer) topology unattended install UNC path data selection user user group vacuuming VCS (Veritas cluster server) A consistent point-in-time view of a volume that is used as the reference point for the backup operation. After a snapshot is created, the primary data can continue being modified without affecting the backup operation. The service that manages a storage pool. The replication of storage pool authority configuration information from an all-in-one local storage pool to a main storage pool. The main data repository in PureDisk. PureDisk writes backup copies of content and metadata to the disk storage that is associated with a storage pool. A storage pool consists of one or more PureDisk nodes. A sequence of digital data. A distribution of Linux software. The name is an acronym for the German phrase Software-und System-Entwicklung (Software and system development). A data selection that is used to back up Microsoft system data on Windows platforms. The process of receiving attributes from a parent template. An encrypted protocol that provides secure communications in the PureDisk environment. The types of PureDisk services that a storage pool includes. All storage pool topologies include one or more of the following services: storage pool authority, content router, metabase engine, metabase server. A controller is installed on a metabase engine. Optionally, a storage pool can also include a NetBackup export engine. An installation that does not require human interaction. A data selection that backs up data on a CIFS network drive on a Windows client. Also use this data selection to indicate the path for a NetApp Filer. An individual with rights to access your protected network resources. Users are defined by creating a user account that consists of a unique user name and authentication method. A collection of users with identical permissions. These users can perform common functions within a PureDisk environment. The process of cleaning up and optimizing a database. Vacuuming removes the records that are no longer needed and results in better database performance. High-availability cluster software developed by Symantec for UNIX, Linux, and Windows platforms.

127 Glossary 127 VEA (Veritas Enterprise Administrator) CommandCentral Console VSP (Volume Shapshot Provider) A separate middleware server used by the SAN Access Layer and other processes to provide client-server communication. The VEA infrastructure enables software components to share information about objects, manage those objects, and effect change on those objects. A graphical user interface that displays reports and other information for users of CommandCentral Service through a standard Web browser. The Console provides a central point to manage cost analysis and chargeback for services, managing workflow, displaying and managing reports, and other tasks. Symantec software that backs up open files. PureDisk uses VSP on Windows 2000 clients. VSS (Volume Shadow Copy Service) VxVM (Veritas Volume Manager) wildcard character workflow XFS (Extended File System) YaST (Yet another Setup Tool) A set of application programming interfaces (APIs) that creates a framework. Within this framework, volume backups and application write can occur at the same time. PureDisk uses Microsoft s VSS technology to back up open files on Windows 2003 and Windows XP clients. A Symantec product installed on storage clients that enables management of physical disks as logical devices. It enhances data storage management by controlling space allocation, performance, data availability, device installation, and system monitoring of private and shared systems. A symbol that enables multiple matching values to be returned based on a shared feature. Two wildcards are available: the question mark (?) and the asterisk (*). The question mark stands for any single character, and the asterisk stands for any character string of any length. For example, the file specification *.* returns all files, regardless of their file names; the file specification *.sc? would return all file names that have a three-character extension beginning with sc (such as compusrv.scr, compusrv.scx, and so on). A collection of steps that the software completes to accomplish a task. A journaling file system that you can configure on a PureDisk node. The operating system installation tool for SUSE Linux.

128 128 Glossary