Read Symantec NetBackup PureDiskTM Getting Started Guide: Windows, Linux, and UNIX text version

Symantec NetBackup PureDiskTM Getting Started Guide

Windows, Linux, and UNIX

Release 6.6.0.2

Publication release 6.6.0.2, revision 1

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: 6.6.0.2, revision 1

Legal Notice

Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and PureDisk 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 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "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.

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

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 maintenance 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 Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week Advanced features, including Account Management Services

For information about Symantec's Maintenance Programs, you can visit our Web site at the following URL: www.symantec.com/techsupp/

Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ 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 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

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/

Customer service

Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with 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 maintenance contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

Maintenance agreement resources

If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows:

Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America [email protected] [email protected] [email protected]

Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following:

Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. Managed Security Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.

Consulting Services

Educational Services

To access more information about Enterprise services, please visit our Web site at the following URL: www.symantec.com Select your country or language from the site index.

Contents

Technical Support ............................................................................................... 4 Chapter 1 Product overview ................................................................. 13

About the PureDisk documentation set ............................................ Updating PureDisk manuals ........................................................... About PureDisk ........................................................................... About the major services in a PureDisk storage pool ..................... Example Storage Pool configuration .......................................... Installing and using PureDisk ......................................................... 13 14 15 16 18 19

Chapter 2

New features and product changes ................................. 21

New features for PureDisk 6.6 ........................................................ Support for Mac OS 10.5 and Mac OS 10.6 ................................... Optimized synthetic backups ................................................... Microsoft Exchange granular restore support .............................. Oracle database support .......................................................... Support for NTFS special file types ............................................ Improved deduplication of VMWare backups .............................. Audit log information ............................................................. PureDisk command line interface ............................................. Windows client installation wizard ........................................... Multistreaming replication ..................................................... Performance enhancements .................................................... Agent debug mode .................................................................. File restore without file overwrite ............................................. Availability of PureDisk operating system .................................. About support for 16 TB content routers .................................... PureDisk 6.6 product changes ......................................................... Administration WebUI ............................................................ PureDisk 6.6 installation and configuration changes ..................... Storage pool installation process .............................................. 21 21 22 22 22 22 23 23 23 23 23 24 24 24 24 24 25 25 25 25

8

Contents

Chapter 3

PureDisk hardware requirements .................................... 27

About hardware installation prerequisites ........................................ Server requirements ..................................................................... Example storage pool configurations ......................................... PDOS hardware compatibility ................................................... Hard disk speed recommendations for PureDisk 6.6 ..................... General PureDisk hardware requirements .................................. Understanding the consequences of disk write caching ................ RAID controllers and disk hardware .......................................... Node-specific hardware requirements ........................................ Capacity planning for nodes and services' databases ........................... Capacity planning for a storage pool .......................................... Metabase engine capacity planning ........................................... Content router capacity planning .............................................. Service databases capacity planning .......................................... High availability requirements ....................................................... High availability storage pool hardware requirements .................. Java administration console requirements .................................. VCS software requirements ...................................................... PureDisk software requirements ............................................... Network requirements ............................................................ Configuration examples .......................................................... Terminology ......................................................................... Planning a cluster .................................................................. Unsupported configurations .................................................... 27 27 28 31 32 33 34 35 37 41 41 43 44 46 47 48 48 49 50 50 52 53 55 55

Chapter 4

General prerequisites ......................................................... 57

About general prerequisites ........................................................... Client requirements ...................................................................... Backup and restore client platforms .......................................... PDDO client platforms ............................................................ Application agent requirements on Windows 2003 ............................. Application agent requirements on Windows 2008 ............................. Browser requirements ................................................................... Storage Foundation requirements ................................................... Software included with Storage Foundation ................................ Supported disks and other hardware .......................................... PureDisk Deduplication Option requirements .................................... NetBackup requirements for PureDisk features ................................. Licensing requirements ................................................................. User authentication requirements ................................................... Symantec Product Authentication Service requirements ..................... 58 58 58 59 59 60 60 61 61 61 62 63 64 64 64

Contents

9

Configuring brokers for PureDisk use ........................................ Firewall and networking requirements ............................................. Communication between client agents and the storage pool ........... Communication between the storage pool authority and other services .......................................................................... Communication between PureDisk and other applications ............. Replication and central reporting ports ...................................... Intraclient communication ...................................................... Changing security settings for Windows clients ................................. Changing security settings for Windows Server 2008 and Windows Server 2003 ....................................................... Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients ................................................. Enabling snapshotting on Windows 2000 clients ................................ Configuring backups and restores of network shared drives or UNC paths on Windows platforms .................................................... Configuring the PureDisk agent to run under the Microsoft Windows Backup Operator group ........................................ Configuring backups and restores of a NetApp filer on Windows platforms ............................................................................. Upgrade requirements ..................................................................

65 73 73 75 78 80 81 82 82 83 84 85 85 89 90

Chapter 5

Known problems and product limitations ..................... 91

About known problems ................................................................. Policies with post script actions may not display checkmarks in administration webUI after upgrades from 6.5.x to 6.6 and later .............................................................................. PureDisk does not support back up of DFS data ............................ Removing a disk from a disk group does not delete the partitions on the disk ...................................................................... Backup of encrypted files not supported ..................................... Installing PureDisk on a Domain Name Server ............................ Installation disk space requirements ......................................... Incorrect error message when WebUI session timeout is exceeded ........................................................................ Special characters in MS Exchange granular restore data .............. Restore and recovery of individual Oracle archive logs .................. Repair of non-default location install of PureDisk on Windows 2008 appears to crash ....................................................... File pattern exclude incorrectly saved as folder pattern ................. Lower than expected deduplication rates seen in NetBackup FlashBackup to PDDO ....................................................... 91

91 92 92 92 92 92 93 93 93 94 94 95

10

Contents

Configuration information may clear and the wizard may not advance during storage pool installation .............................. 95 Job Progress in job details tab does not refresh ............................ 95 The LDAP synchronization workflow may incorrectly report the maximum number of users supported is exceeded .................. 95 Incorrect log files displayed when expanding the archive log folder of an Oracle data selection ........................................ 96 PDDO Backup capacity not updating on Enterprise License Report ............................................................................ 96 Unable to edit or view storage pool level event escalation action when there is an agent level escalation action added to the same event ...................................................................... 96 Job Step Progress for Data Removal Job shows 0% complete even when job is finished .......................................................... 96 Services list appearing in narrow scroll window ........................... 96 Custom settings and enhancements in pd.conf file require additional attention when upgrading PDDO client .................. 97 Content router queue processing policy schedule reset after upgrade .......................................................................... 97 Users cannot edit data removal policies with a future date ............. 97 MS Exchange granular restore fails when time zone settings inconsistent .................................................................... 97 PureDisk workflow engine log file can grow and rapidly fill the /Storage partition ............................................................ 97 Data selection template incorrectly applied when created at storage pool level ............................................................. 98 PureDisk upgrade fails if there is insufficient space on the content router ............................................................................ 98 Documentation updates after the release .................................... 98 Files migrated by Remote Storage Service are retrieved at backup ........................................................................... 99 Agent updates fail on clients due to inadequate permissions .................................................................... 99 Cryptic messages ................................................................... 99 PureDisk reserved user IDs collide with some imported users .............................................................................. 99 PureDisk reserved patterns cause unexpected results .................. 100 I18N problems ..................................................................... 101 Erroneous errors in /Storage/log after installation ..................... 102 Need to commit changes in YaST if subsequent changes could conflict ......................................................................... 102 Restoring UNC files at the client level ...................................... 103 AIX 5.3 agent upgrade failures from PureDisk 6.2 to 6.5 ............... 103

Contents

11

Upgrading failures for some Linux or Solaris agents ................... Cannot install regular backup and restore agent on a Windows media server after you remove a PDDO agent ...................... Update client routing tables manually after interrupted content router rerouting job ........................................................ System policy for a Maintenance job hangs when PDDO is enabled ......................................................................... About PureDisk limitations .......................................................... Limitations for PureDisk 6.6 with NFS ...................................... File name and path limitations ................................................ Data selections limited to 16 million files .................................. Unsupported VMFS volumes .................................................. Data lock password blocks exports to NetBackup ........................ File size limitation ................................................................ Replicated PureDisk SPAR data cannot be exported to NetBackup .................................................................... Metabase engine limitations ................................................... I18N limitations ...................................................................

103 104 104 105 106 106 106 106 107 107 107 107 107 108

Appendix A

Third-party legal notices .................................................. 109

Third-party legal notices for Symantec NetBackup PureDisk .............. 109

Index ................................................................................................................... 111

12

Contents

Chapter

1

Product overview

This chapter includes the following topics:

About the PureDisk documentation set Updating PureDisk manuals About PureDisk Installing and using PureDisk

About the PureDisk documentation set

The PureDisk documentation set consists of several manuals. The manual set includes installation, best practices, and getting started guides, as well as a cluster planning worksheet. Symantec updates the PureDisk documentation on an as-needed basis. Access and download the PureDisk documentation on the Symantec Web site. To download updated PureDisk documentation

1

Go to the following Web site: http://www.symantec.com/enterprise/support/documentation.jsp?pid=52672

2 3 4

In the Version field, use the drop-down list to select the PureDisk 6.6 release level. In the Language field, use the drop-down list to select a language. Click the title of the manual you want.

14

Product overview Updating PureDisk manuals

5 6

In the new window that appears, click Download Now. Use your browser's tools to save the downloaded PDF file. Save the downloaded files as follows: Manual title

PureDisk Administrator's Guide PureDisk Backup Operator's Guide PureDisk Best Practices Guide

File name

PureDisk_Admin_Guide.pdf PureDisk_BackupOperator_Guide.pdf

PureDisk_BestPractices_Guide.pdf

PureDisk Client Installation Guide PureDisk_ClientInstall_Guide.pdf PureDisk Getting Started Guide PureDisk Deduplication Option Guide PureDisk_GettingStarted_Guide.pdf PureDisk_PDDO_Guide.pdf

PureDisk Storage Pool Installation PureDisk_StoragePoolInstall_Guide.pdf Guide PureDisk Command Line Interface Guide Cluster planning spreadsheet PureDisk_CLI_Guide.pdf

PureDisk_ClusterPlanning.xls

Updating PureDisk manuals

Click the Documentation section of login page to display PDF copies of the PureDisk user manuals. Use the following procedure to update the PDF files in the documentation directory. After you complete this procedure, the PDF files that you retrieve when you click the Documentation section of the login page are the revised manuals.

Product overview About PureDisk

15

To update the PureDisk manuals

1

Download updated PureDisk manuals: See "To download updated PureDisk documentation" on page 13.

2

(Optional) Use Linux commands to copy the existing PDF files to an archive directory. Perform this step if you have older versions of the documentation to save in a directory of your own choice.

3

On the storage pool authority, use Linux commands to write the downloaded PDF files to the following documentation directory:

/opt/pdweb/htdocs/documentation

Use the file names. These are the file names by which PureDisk retrieves the manuals when you click Documentation on the login page. See "About the PureDisk documentation set" on page 13.

About PureDisk

PureDisk provides an enterprise-level data deduplication environment. This software is ideally suited for a company that needs a centralized solution for bandwidth-optimized backups of data in remote offices and virtual environments. You also can use PureDisk to reduce the amount of backup data that is stored in a datacenter by NetBackup. When PureDisk performs a backup, it separates the file content from its metadata. PureDisk uses global deduplication technology to reduce the amount of backup data that it stores. It writes file content to secondary disk storage, and it writes file metadata to a distributed database that is called a metabase. The metadata consists of information about the file such as its owner, where it resides on a client, when it was created, and other information. The metadata also includes a unique fingerprint that identifies the file's content to PureDisk. The first step in backing up data is to create a data selection. A data selection specifies a list of files and directories that you want to include in a backup. You can back up a data selection on a regular basis by including it in a backup policy. Alternatively, you can make a quick one-time backup of a data selection. When you restore files, you restore the files or directories that you need. You do not need to restore an entire data selection. Identical files can reside on multiple clients in a PureDisk environment. However, the PureDisk global data deduplication capability ensures that if identical files exist, only one copy of the file's content resides in storage. PureDisk analyzes the content of each file and stores only one backup image for each unique file in the

16

Product overview About PureDisk

environment. When files change, PureDisk detects these changes by comparing the file fingerprints. When you install the PureDisk Deduplication Option (PDDO) plug-in on a NetBackup media server, you can deduplicate NetBackup data.

About the major services in a PureDisk storage pool

A PureDisk storage pool is a main data repository. When PureDisk backs up data, it writes backup copies of content and metadata to the disk storage that is attached to a storage pool. If you configure more than one storage pool, you can replicate the backup data from one storage pool to the other storage pool. A storage pool consists of one or more PureDisk nodes. A node is a server with the PureDisk operating system (PDOS) installed upon it. PDOS is a version of Linux based on SLES 10, SP2. More information about PDOS is available. See "PDOS hardware compatibility" on page 31. The installation package includes PDOS. After you install PDOS on all your nodes, you can install one or more PureDisk storage pool services on the nodes. Table 1-1 shows the roles for each PureDisk services. Table 1-1 Service

Storage pool authority

PureDisk software service roles Role

A storage pool authority manages a storage pool. For example, the storage pool authority manages policies and storage. You can configure one storage pool authority per storage pool. A metabase server manages queries on one or more metabase engines. You can configure one metabase server per storage pool. The metabase server in the storage pool manages the process by which PureDisk stores the metadata into one or more metabase engines. Metabase engines are the databases that retain each file's metadata permanently. After you remove a file's content from PureDisk storage, its metadata remains in the metabase engine. The metadata is kept for auditing purposes until you run a garbage collection policy.

Metabase server

Product overview About PureDisk

17

Table 1-1 Service

Metabase engine

PureDisk software service roles (continued) Role

When PureDisk backs up a file, it separates the file's metadata from the file's content. PureDisk writes the metadata to a metabase engine, and it writes the file's content to a content router. You can configure more than one metabase engine per storage pool. The following factors can influence your decision:

The number of clients. The number of files per client. The rate of change for your files. Two or more metabase engines improve performance.

The metabase engine also manages the communication between the clients and PureDisk. Content router When PureDisk backs up a file, it separates the file's metadata from the file's content. PureDisk writes the metadata to a metabase engine, and it writes the file's content to a content router. A content router stores and retrieves file content. PureDisk breaks larger files into segments and distributes the segments across the available content routers. You can configure more than one content router in a storage pool. PureDisk writes file content to a content router, so the content routers must be attached to a large disk group. The bulk of the disk storage in a storage pool hosts file content. NetBackup export engine The NetBackup export engine is a service. If you configure this service on a node, you can export content router data from a PureDisk storage pool to NetBackup. The export engine is an optional service. If you configure a PureDisk storage pool with multiple nodes, you can configure one export engine per node. Other PureDisk services can reside on a node with a NetBackup export engine. Alternatively, you can configure the export engine on a node by itself. If you configure multiple export engines on multiple nodes in your storage pool, you can use them to export data to NetBackup in parallel.

A PureDisk storage pool includes several clients that need to be backed up. When you configure your PureDisk environment, you install PureDisk agent software on the client, and you assign each client to a storage pool. The metabase engine

18

Product overview About PureDisk

maintains a connection to the agent on each client. The metabase engine sends backup, restore, and other job instructions to the agent through this connection.

Example Storage Pool configuration

For an example of a storage pool configuration with five nodes, see Figure 1-1. Figure 1-1 Example storage pool

Node_4 NetBackup export engine

Node_3 Content Router

Disk Storage Node_5 Metabase Engine

Node_1 Storage Pool Authority Metabase Server

Node_2 Content Router

Client

Client

Client

Client

Client

The services are distributed as follows:

Node_1 hosts the storage pool authority and the metabase server. Node_2 and Node_3 each host a content router.

Product overview Installing and using PureDisk

19

Node_4 hosts a NetBackup export engine. Node_5 hosts the metabase engine.

This example configuration does not include any passive nodes. If you want to enable high availability, you need to configure one or more passive nodes in your storage pool. The NetBackup export engine is an optional service.

Installing and using PureDisk

The PureDisk documentation explains the procedures that you need to install and configure PureDisk on your storage pool and on its clients. The documentation also explains how to back up and restore your clients and how to administer your storage pool. The following procedure explains the general installation procedures and notes where to look for information. To install and configure PureDisk

1

Familiarize yourself with the PureDisk product and plan your storage pool. See the PureDisk Getting Started Guide. Use the information in this manual, This guide contains general information about this PureDisk release. It also describes the software requirements and hardware requirements that your site needs to meet to install and configure PureDisk successfully.

2

Install the storage pool software. See the PureDisk Storage Pool Installation Guide. This guide describes how to configure the servers and disks in a PureDisk storage pool.

3

Install the PureDisk software on the clients. See the PureDisk Client Installation Guide. This guide describes how to install the client software and other types of PureDisk agent software. This guide also explains how to configure the initial set of users.

20

Product overview Installing and using PureDisk

4

Specify data selections and configure backups. See the PureDisk Backup Operator's Guide. This guide describes how to create data selections and schedule PureDisk to back up your data selections. A data selection is a defined list of files and other data objects that you want to back up. After you specify data selections, you can back them up manually or you can schedule PureDisk to back them up according to a schedule.

5

Monitor, protect, and modify your storage pool as needs change. See the PureDisk Administrator's Guide. The topics in this guide include reporting, disaster recovery backups, system monitoring, and system expansion.

Chapter

2

New features and product changes

This chapter includes the following topics:

New features for PureDisk 6.6 PureDisk 6.6 product changes

New features for PureDisk 6.6

The following topics describe the features that are new to the PureDisk 6.6 release.

Support for Mac OS 10.5 and Mac OS 10.6

PureDisk 6.6 supports backups and restores of the Mac OS 10.5 and Mac OS 10.6 operating system. This does not require a separate PureDisk agent from the existing PureDisk Mac OS agent. PureDisk still does not support Mac OS file system Extended Attributes (EA). New in Mac OS 10.6, the contents of an executable binary are compressed and stored in the extended attributes to conserve file system space. This is not an issue for PureDisk backups since the Mac OS needs to maintain backwards compatibility with older Mac OS revisions. Backups continue to work on 10.6 as the operating system seamlessly decompresses the EA executable contents and passes the uncompressed data to the backup application. Since the restore activity restores the executables in their uncompressed format, the restore requires more space.

22

New features and product changes New features for PureDisk 6.6

Optimized synthetic backups

Starting with PureDisk 6.6 and NetBackup 6.5.4, the process for creating synthetic backups is improved. In a standard synthetic backup, after a full and at least one incremental, the data is copied from the most recent backup image on the disk to create a new full backup. The catalog is then updated with the information about this new backup. Depending on processor speed, disk speed, and the type of data that is backed up, that can be a long process. With the new optimized process, the synthetic full backup is created through manipulation of catalog metadata and data segment pointers only. NetBackup does not copy the data. The result is a faster backup process, with performance enhancement dependent on various factors including processor speed, memory and file size.

Microsoft Exchange granular restore support

PureDisk 6.6 can restore Exchange items below the database level. These items include: public folders and their contents, mailboxes and their contents, folders within mailboxes, and individual mailbox contents, such as email messages , calendar items, and so on. You can restore these items to their original locations or to an alternate server and path. See the PureDisk Backup Operator's Guide for more information about granular Exchange item restores.

Oracle database support

This release of PureDisk includes backup and restore support for Oracle databases. PureDisk supports versions 9i, and 10g, on Windows Server 2003 (32-bit and 64-bit extended) or Solaris SPARC version 9 and version 10 platforms. Key features include: the ability to start jobs from the PureDisk administrative Web UI or from the database client, multiple data stream support for optimum performance during backups, and Oracle RMAN Recovery Catalog support. More information about PureDisk's Oracle support is available in the PureDisk Backup Operator's Guide.

Support for NTFS special file types

PureDisk 6.6 supports backups and restores of the following Windows NT File System (NTFS) special file types:

Reparse points, such as files (for example, Enterprise Vault placeholders), volume mount and junction points, and symbolic links. Sparse files. Hard links.

New features and product changes New features for PureDisk 6.6

23

See the PureDisk Backup Operator's Guide for more information about backing up and restoring NTFS special file types.

Improved deduplication of VMWare backups

This release of PureDisk offers improved deduplication of NetBackup VMWare backups to PDDO storage through enhancements to the analysis of the backup stream. These enhancements detect more logical segments based on the files that are identified in the stream. Be aware that these improvements are only implemented on Windows servers with the PDDO plugin, not on Solaris or Linux. These improvements only occur on NTFS drives.

Audit log information

This release of PureDisk lets you retrieve audit log information for a storage pool. The information in the report includes a list of everyone who logged into PureDisk and the activities they performed. PureDisk generates this information in the Web UI. This information is available in a compressed (tgz) file format.

PureDisk command line interface

With this release, PureDisk implements a command line interface. More information about the command line interface can be found in the associated man pages. Use the man PureDisk_CLI command to see an overview of the command line interface.

Windows client installation wizard

An improved installation wizard is implemented for the PureDisk 6.6 Windows client installation. Windows platform agent installations now have two parts: agent installation and agent registration.

Multistreaming replication

PureDisk now support multistreaming of replication jobs in addition to multistreaming of regular backup and restore jobs. Enabling multistreaming entails altering the configuration file of the server agent on the source storage pool. The configuration parameters that are added in this release are as follows: maxretrycount, sleeptime, and maxsleeptime.

24

New features and product changes New features for PureDisk 6.6

Performance enhancements

PureDisk now groups more information together when it transfers data from the content routers to a client for a restore. This new method improves performance for most restores. Two new client agent configuration file fields have been added. You can change the values of these fields to further enhance restore performance for specific clients: MaxSegmentPrefetchSize and SegmentChunkSize. For more information on the use of these file fields, see the Tuning and optimization chapter in the Symantec NetBackup PureDisk Administrator's Guide.

Agent debug mode

When PureDisk is in debug mode, a PureDisk agent provides detailed log information for the job steps that run on that client agent or server agent. Also, when enabled, temporary scripts and log files remain in place on a client agent or server agent. Typically, PureDisk removes these files after they are no longer needed, but when you enable debug mode, PureDisk leaves them in place. For example, you can enable debug mode to troubleshoot failing jobs for a particular client agent. Typically, Symantec CFT or technical support requests that you enable this capability in the storage pool while troubleshooting. Do not enable debug mode for general use.

File restore without file overwrite

Starting with 6.6, PureDisk has the option to restore files without overwriting any previously existing files. Additionally, PureDisk can restore of files with a temporary name. For more information on this feature, please see the PureDisk Backup Operator's Guide.

Availability of PureDisk operating system

The PureDisk operating system (PDOS) has been updated to use SUSE Linux Enterprise Server 10 (SLES10), Service Pack 2. The source code is available from Symantec Technical Support upon request. For information on how to contact Symantec Technical Support, see: http://www.symantec.com/business/support/overview.jsp?pid=52672 and click on Contact Technical Support.

About support for 16 TB content routers

PureDisk supports content routers up to 16 TB.

New features and product changes PureDisk 6.6 product changes

25

This configuration is supported for PureDisk under the following conditions:

Minimum PureDisk version is 6.6. Early versions are not supported. Minimum of 20 GB RAM for an All-in-one node. Minimum of 16 GB RAM for a dedicated content router node.

This configuration is supported for PDDO under the following conditions:

Minimum PureDisk version is 6.5.1.2. Early versions are not supported. Minimum of 16 GB RAM.

PureDisk 6.6 product changes

This topic describes major changes in PureDisk release 6.6 that may affect your site practices.

Administration WebUI

PureDisk 6.6 introduces a new web user interface for the administration console. For more information about the new web UI, see the Symantec NetBackup PureDisk Backup Operator's Guide.

PureDisk 6.6 installation and configuration changes

PureDisk 6.6 includes changes to the PDOS installation process and the PureDisk application configuration process. When you install PDOS, you can use either the new PDOS installation wizard or the YaST- based installer that was included in previous releases. The new storage pool configuration wizard discovers information on its own and prompts you to supply node-specific details. For more information on the installation process, see the Symantec NetBackup PureDisk Storage Pool Installation Guide.

Storage pool installation process

PureDisk 6.6 introduces a new storage pool installation process. The new process consists of installing the PureDisk operating system (PDOS), preparing the node for storage pool installation, and running the storage pool installation wizard. For more information on the installation process, see the Symantec NetBackup PureDisk Storage Pool Installation Guide.

26

New features and product changes PureDisk 6.6 product changes

Chapter

3

PureDisk hardware requirements

This chapter includes the following topics:

About hardware installation prerequisites Server requirements Capacity planning for nodes and services' databases High availability requirements

About hardware installation prerequisites

This topic describes the hardware you are required to obtain and prepare before you begin to install the PureDisk software. This information only applies to PureDisk Remote Office Edition (PDROE). This does not apply to PureDisk Virtual Appliance (PDVA). This topic contains compatibility information, but for more details on compatibility, visit the following Web site: http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672

Server requirements

The PureDisk software lets you create a modularly scalable backup environment. You can install all the PureDisk services on one server. Alternatively, you can install PureDisk software on multiple servers to create multiple nodes. These multiple nodes increase the storage pool's capacity and performance because they balance the backup processing load.

28

PureDisk hardware requirements Server requirements

For each node, you can configure several services, but you cannot configure multiple instances of the same service on one node. For example, you can configure a storage pool authority service and a metabase server service on one node. But you cannot configure two metabase servers on the same node. The following topics present configuration examples, describe PDOS requirements, and describe the PureDisk service requirements. During an installation, you install PDOS on each server. Then you configure each server to assume one or more roles in a PureDisk environment. Additional example configurations and an explanation of the available PureDisk services are available: See "Example storage pool configurations" on page 28. See "PDOS hardware compatibility" on page 31. See "Hard disk speed recommendations for PureDisk 6.6" on page 32. See "General PureDisk hardware requirements" on page 33. See "Understanding the consequences of disk write caching " on page 34. See "RAID controllers and disk hardware" on page 35. See "Node-specific hardware requirements" on page 37.

Example storage pool configurations

The storage pools in these examples show a progression from the smallest PureDisk storage pool to a larger, modular storage pool. The examples show that as the need for backup capability grows, you can add content routers and metabase engines. If you add a passive node to any of these storage pools, you can enable high availability.

Example 1 - An all-in-one configuration

This example storage pool includes only one PureDisk node. This storage pool is appropriate for a small remote office or centralized environment. You can install all the PureDisk services on one node. In the future, you can add more nodes as needed to improve performance and expand capacity as described in examples 2, 3, and 4. The all-in-one node has the following services:

Storage pool authority Metabase server

PureDisk hardware requirements Server requirements

29

Metabase engine Content router

Example 2 - A two-node configuration

This example storage pool includes two PureDisk nodes. To improve storage pool performance, the storage pool authority and metabase services are installed on the first node. The separate content router node can store approximately 16 TB of optimized file content. Node 1 has the following services:

Storage pool authority Metabase server Metabase engine

Node 2 has the following service: Content router

Example 3 - A three-node configuration

This example storage pool includes three PureDisk nodes. When you configure two content routers on different nodes, you provide up to 16 TB of space to store optimized file content. Node 1 has the following services:

Storage pool authority Metabase server Metabase engine

Node 2 has the following service: Content router Node 3 has the following service: Content router

Example 4 - A five-node, high availability single-cluster configuration

This example storage pool includes five PureDisk nodes that are configured in a cluster. Node 1 has the following services:

Storage pool authority Metabase server Metabase engine

30

PureDisk hardware requirements Server requirements

Node 2 has the following service: Content router Node 3 has the following service: Content router Node 4 has the following service: Metabase engine Node 5 has the following service: Passive node Like the storage pool in example 3, the two content routers in this storage pool can accommodate up to 16 TB of file content. If you add another content router, you can increase the optimized file storage capacity. Node 4 is a dedicated metabase engine node. Each dedicated metabase engine can store the metadata of approximately 140 million file and version records that you want to retain. Node 1 hosts three services, and one of these services is a metabase engine. A metabase engine on a multiservice node can retain fewer file and version records than a metabase engine that resides on a node by itself. The metabase engine on node 1 can retain approximately 100 million file and version records. If you add another metabase engine, you can increase the number of files that the metabase can contain. For example, if you add another dedicated metabase engine, the expanded system now can store approximately 380 million file and version records. You can continue to add nodes to this cluster. All nodes that you add need to be configured for high availability. For example, you can add a NetBackup export engine. Note: Symantec recommends that you contact Symantec Consulting Services for the installation of a clustered, highly available PureDisk storage pool.

Example 5 - A three-node, high availability configuration

This example storage pool includes three PureDisk nodes that are configured in a cluster. Node 1 has the following services:

Storage pool authority Metabase server Metabase engine Content router

Node 2 has the following services:

Content router Metabase engine

PureDisk hardware requirements Server requirements

31

Node 3 has the following service: Passive node You can continue to add nodes to this cluster. All nodes that you add need to be configured for high availability. Note: Symantec recommends that you contact Symantec Consulting Services for the installation of a clustered, highly available PureDisk storage pool.

PDOS hardware compatibility

The server hardware must be capable of running SUSE Linux Enterprise Server 10 (SLES10), Service Pack 2, for AMD64 and Intel EM64T. PDOS is based on SLES10, SP2. To create PDOS, Symantec removed some packages from the standard SLES10, SP2, installation, and added some different packages. Symantec did not change the kernel or any other package or binary installed. Each server can be connected to internal storage, external disk storage, or both. For production installations, you must have at least two disks: a boot disk and a storage disk. The storage disk can consist of any of the following:

Direct-attached storage (DAS) over SATA, serial-attached SCSI (SAS), or SCSI. A storage area network (SAN) or disk array over fibre channel. A disk array over iSCSI. Symantec supports disk storage scheme for XFS file systems only. The VxFS file system does not support iSCSI disks. Do not use iSCSI disks to configure a highly available PureDisk storage pool.

PureDisk supports network-attached storage (NAS) over NFS only with NetApp Filers. No other NAS devices are supported. NAS storage should not be used for a highly available PureDisk storage pool. The amount of storage to attach to each PureDisk node depends on the roles that you want to assign to the PureDisk node. Information about the storage requirements for each PureDisk service is available. See "Metabase engine capacity planning" on page 43. See "Content router capacity planning" on page 44. See "Service databases capacity planning" on page 46. This topic explains when you can use the various types of disks in more detail when it describes the PureDisk services and their requirements. By default, PureDisk installs the Storage Foundation file system, VxFS, and installs the Storage Foundation Volume Manager , VxVM. Use a storage system that is compatible with the Veritas Storage Foundation 4.1 MP4. Use a host bus adaptor (HBA) that is compatible with SUSE Linux Enterprise Server 10 SP2 for AMD64 and Intel EM64T.

32

PureDisk hardware requirements Server requirements

For any hardware that SUSE Linux Enterprise Server for AMD64 and Intel EM64T does not support by default, obtain the drivers from the vendor. For more compatibility information, see the following Web sites:

More information about hardware compatibility with SUSE Linux Enterprise Server 10 SP2 and PDOS is available. http://www.novell.com/partnerguide/section/481.html More information about the list of arrays that VxVM supports in the Storage Foundation 4.1 MP4 release is available in the hardware compatibility. http://seer.entsupport.symantec.com/docs/289200.htm

Caution: The PureDisk node software that you install on a server overwrites any pre-existing information on that server. The server becomes a dedicated PureDisk node.

Hard disk speed recommendations for PureDisk 6.6

The read and write speeds of the hard disks in the storage pool affect overall PureDisk performance. To determine disk speed

1

To determine the speed of the drives in the storage pool, run the following command:

time (dd if=/dev/zero of=/Storage/data/xyz bs=64k count=409600; sync)

2

The output looks similar to the following:

409600+0 records in 409600+0 records out ---------------------speed=26843545600/110.9 = 225.5MB/sec

Computers with disk speeds greater than 200MB per second have optimal read and write performance for PureDisk. Computers with disk speeds between 150-200MB per second have sufficient read and write speed for PureDisk. Computers with disk speeds between 100-150MB per second have some operations with degraded performance.

PureDisk hardware requirements Server requirements

33

Computers with disk speeds less than 100MB per second experience poor performance. Improve disk reads and writes before installing and running PureDisk.

General PureDisk hardware requirements

Table 3-1 provides general information about the hardware requirements that pertain to all PureDisk nodes. Table 3-1 Hardware component

Processor

General requirements for hardware components Requirement

Each PureDisk node requires a processor that is compatible with Intel EM64T or AMD64 specifications. For best performance, Symantec recommends Intel Xeon (64 bit) or AMD Opteron processors. PDOS is not compatible with Itanium processors.

Network cards

Symantec recommends that you use enterprise-class GB Ethernet network interface cards (NICs), such as an Intel PRO or equivalent. PureDisk requires that each server that you configure contain at least one NIC.

Note: If the system has more than one NIC, PDOS chooses the

first NIC that it encounters that is connected to the network. PDOS does not consider NICs that are not connected to the network. Make sure that each network card is set to full duplex. To enable highly available PureDisk, each server that you want to include in a cluster requires three NICs. The additional NICs are needed for the cluster's private network. Do not configure an IP address on the additional two NICs. These additional NICs are used exclusively by the Veritas Cluster Server (VCS) software. PureDisk supports only static addresses. PureDisk does not support DHCP. Before installing PDOS, configure static addressing in your DHCP server for each computer on which you want to install PDOS. Removable media Symantec distributes the PureDisk 6.6 software on one DVD. Each node must have a DVD drive to facilitate software installation.

34

PureDisk hardware requirements Server requirements

Table 3-1 Hardware component

General requirements for hardware components (continued) Requirement

Uninterruptible power Use a UPS to protect the hardware in your PureDisk environment. supply (UPS) If you turn off a PureDisk storage node in any uncontrolled way, it can result in backup data corruption or data loss. If your UPS requires a USB, Ethernet, or serial port to connect to the PureDisk node, ensure that they are available on the node also. If you use an Ethernet port, Symantec recommends that you provide an additional port in the device. More information about the potential problems of a power loss is available. See "Understanding the consequences of disk write caching " on page 34.

Understanding the consequences of disk write caching

Storage devices such as hard disks, internal RAID controller cards, and disk arrays often have a write caching setting. If the disk has write caching enabled, this can boost disk performance, but that can be at the cost of data corruption if a power outage occurs. PureDisk stores its data in the /Storage directory and subdirectories. It is highly recommended to enable write caching for the devices on which the /Storage directory and subdirectories reside. But only if there are sufficient guarantees that the information in the memory caches cannot be lost due to a power outage. Write caching means that a device may queue the information that is written to it in a memory cache for a period of time before it writes it to disk. By doing that, a device can often optimize performance significantly. For example by combining adjacent write operations, by reordering write operations, and by avoiding repeated information overwrites in the same location on disk. Storage devices that use write caching often acknowledge to the operating system that a write operation has taken place immediately after the data is queued in their memory cache, but without having written it to the storage medium. Even a system-wide sync command may not cause the devices to write the information in their memory caches to disk. If a memory cache loses power, typically all information in it is lost. A power outage (including turning off a system or unplugging it) can cause data corruption if write caching is enabled. Files and directories may disappear, parts of files may become corrupt, the internal structure of file systems may be corrupted, and even

PureDisk hardware requirements Server requirements

35

changes to partition tables may be lost. Such corruption may have grave consequences for the integrity of the PureDisk data in the /Storage folder. Several ways exist to protect the data while it is enqueued in a write cache. For example, a storage device may contain a battery backup unit (BBU) that continues to supply power to its memory cache for a certain period of time after power outage. If power can be restored during this period, the storage device can write the information in the memory cache to the storage medium. Connecting the entire system to an uninterruptible power supply can be an additional safeguard. Some, but not all, RAID controllers automatically disable write caching if no battery backup unit is present, or if it has failed. RAID controllers may or may not turn off write caching for the hard disks they control. In some cases, write caching is turned on by default, even if there is no way to guarantee that the data in the memory caches can survive a power outage. For example, internal disks of a computer have write caching enabled by default. They usually cannot prevent data loss if their memory cache loses power. The PureDisk Operating System (PDOS) contains a tool that may help in determining if write caching is enabled. The tool is called sdparm. For example, for a system with /Storage on device /dev/sdb, sdparm may be able to show if write caching is enabled in the following way:

# sdparm -g WCE /dev/sdb /dev/sdb: ... WCE 1

Here, 1 means that write caching is enabled. 0 would be displayed if it was disabled. The sdparm and the hdparm tools do not work for all devices. Many devices have a BIOS or come with their own configuration tools in which the settings can be consulted and modified instead. Please consult the documentation of the devices for more information.

RAID controllers and disk hardware

Symantec recommends that you use Redundant Array of Independent Disks (RAID) technology for the disks you include in a PureDisk storage pool. You can use a hardware RAID controller, a software RAID that you configure through the Veritas Volume Manager (VxVM), or some other kind of RAID technology. This section describes the kind of RAID you need to use for disks in a PureDisk storage pool. Hardware RAID controllers can be more stable and are easier to maintain than software RAID. In addition, hardware RAID offers the following advantages:

Keeps the load off the server's CPU

36

PureDisk hardware requirements Server requirements

Easier to replace failed drives Usually faster than software RAID

In the following situations, however, consider using software RAID:

If the hardware RAID controller is of poor quality or slow. If the hardware RAID controller is not supported on PDOS. If the hardware RAID controller does not support array expansion.

Note: PureDisk has databases for the content router, metabase engine, and storage pool authority services. Symantec recommends that you do not use a RAID 6 configuration for the partitions on which those PureDisk databases reside. RAID 6 configurations cause the performance of the PureDisk databases to degrade significantly, which adversely affects the performance of PureDisk processes. The PureDisk storage pool configuration wizard helps you to configure one or more of the following storage partitions:

/Storage is the repository for database queue files. This partition is required. /Storage/data is the repository for all file content. This partition is optional. /Storage/databases hosts the services' databases. This partition is optional.

You can create /Storage and /Storage/data on the same partition, but you risk increased disk fragmentation in the /Storage/data directory. However, the benefit to creating one partition for both directories is that you do not lose space for the staging area. With one partition, you allocate more space for storing backup data. If you combine these partitions, use RAID 5. If you want to create a multinode storage pool, Symantec recommends that you configure each node's storage identically. The following tables summarize the three disk partitioning options for nodes in unclustered storage pools. Performance increases if you use option 2 or option 3. The following table summarizes the disk partitioning for a layout with a /Storage partition. Table 3-2 Mount point

/Storage

Option 1: /Storage partition RAID

RAID 0, RAID 1, or RAID 5

Services

All

I/O requirement

Needs normal I/O speed

Size

Up to 16 TB

PureDisk hardware requirements Server requirements

37

The following table summarizes the disk partitioning for a layout with a /Storage and a /Storage/data partition. Table 3-3 Mount point

/Storage

Option 2: /Storage + /Storage/data partitions RAID

RAID 0, RAID 1, or RAID 5 RAID 5

Services

All

I/O requirement

Needs normal I/O speed Needs normal I/O speed

Size

15% of the size of /Storage/data Up to 8 TB

/Storage/data

Content router

The following table summarizes the disk partitioning for a layout with a /Storage, a /Storage/data, and a /Storage/databases partition. Table 3-4 Mount point

/Storage

Option 3: /Storage + /Storage/data + /Storage/databases partitions RAID

RAID 0, RAID 1, or RAID 5 RAID 5

Services

All

I/O requirement

Needs normal I/O speed Needs normal I/O speed Needs fast I/O

Size

5% of the size of /Storage/data Up to 8 TB

/Storage/data

Content router

/Storage/databases Metabase engine, content router, storage pool authority

RAID 1

10% of the size of /Storage/data

Node-specific hardware requirements

The following topics describe hardware requirements as they pertain to individual nodes.

All-in-one PureDisk node requirements

The requirements for an all-in-one PureDisk node assume that the node includes a metabase engine and a content router service. In addition, it must meet the following requirements:

Two dual-core processors Higher-speed processors enhance system performance. Greater numbers of processors and cores do not enhance system performance. Error-correcting code (ECC) random-access memory (RAM)

38

PureDisk hardware requirements Server requirements

10 GB for an 8-TB all-in-one PureDisk node 4 GB for a 4-TB all-in-one PureDisk node

Internal disks or external disks The PDOS installer creates several partitions on the following disks:

The /, swap, and /boot partitions, which require 23 GB of disk space.

The /Storage partition, which requires between 250 GB and 8 TB of usable space after the RAID configuration. If you use only internal disks, PureDisk requires that they be at least 7,200 rpm IDE or SATA disks. SCSI, fibre channel, or serial-attached SCSI disks enhance PureDisk performance. If you use an external disk cabinet or SAN, you have both internal disks and external disks. The requirements for these disks are as follows:

PureDisk requires internal disks to be at least 7,200 rpm SCSI disks. PureDisk requires at least 250 GB to store the databases and the temporary backup data on the internal disks. More internal disk space enables PureDisk to back up a higher volume of daily incremental data at higher backup rates. PureDisk requires external disks to be at least 7,200 rpm IDE or SATA disks. PureDisk stores and retains up to 8 TB of unique data segments on an all-in-one node's external disks. For best performance, the PureDisk databases in /Storage/databases need to be on fast disks with RAID 1 protection. The backup data in /Storage/data can be on high-capacity disks with RAID 5 protection.

Be aware of the following limitations when you configure an all-in-one system:

The metabase engine on an all-in-one node can store 100 million file records and file version records. To back up more than 100 million files, plan to add an additional node for a second metabase engine. If you need more than 8 TB of disk space for your file content on storage, plan to add a node for another content router.

Content router node requirements

Plan to include one content router service for every 8 TB of addressable storage. One content router has a maximum capacity of 8 TB in which to store deduplicated data segments. A deduplicated data segment is a unique piece of file information. As PureDisk backs up file data, it uses its deduplication technology to store each piece of unique file content only one time. You can attach either internal disks or external disks to a content router.

PureDisk hardware requirements Server requirements

39

The following are the requirements for a node with only a content router:

One dual-core processor Higher-speed processors enhance system performance. Greater numbers of processors and cores do not enhance system performance. Error-correcting code (ECC) random-access memory (RAM)

4 GB for a 4-TB content router node. 8 GB for an 8-TB content router node. 10 GB for a content router node that also acts as the metabase engine node.

Internal disks or external disks. The PDOS installer creates several partitions.

The /, swap, and /boot partitions, which require 23 GB of disk space. The /Storage partition, which requires between 100 GB and 8 TB of usable space after the RAID configuration.

The following are the requirements for the /Storage partition:

If you use only internal disks, PureDisk requires them to be at least 7,200 rpm IDE or SATA disks. SCSI, fibre channel, or serial-attached SCSI disks enhance PureDisk performance. If you use an external disk cabinet or SAN, configure both internal disks and external disks as follows:

For the internal disks, PureDisk requires them to be at least 7,200 rpm SCSI or serial-attached SCSI disks with RAID 1. PureDisk requires 250 GB or more to store the content router database and the temporary backup data on the internal disks. More internal disk space lets you back up a higher volume of daily incremental data at higher speeds. For the external disks, PureDisk requires them to be at least 7,200 rpm IDE or SATA disks with RAID 5. PureDisk can store up to 8 TB of unique data segments on these disks.

To configure high availability, configure the /Storage partition on external disks that are visible to all active and passive nodes (shared).

Metabase engine node requirements

You can configure a metabase engine service on a dedicated, standalone node, or on a multiservice node with other PureDisk services. A metabase engine on a dedicated node can store records for more files and file versions than a metabase engine that you configure on a multiservice node, as follows:

40

PureDisk hardware requirements Server requirements

A metabase engine on a dedicated node can store the metadata of approximately 140 million file and version records. A metabase engine on a multiservice node can store the metadata for approximately 100 million file and file versions.

Depending on whether you configure your metabase engine(s) as dedicated nodes or as multiservice nodes, plan to include one metabase engine for every 140 million file and version records or every 100 million file and version records. You can attach a metabase engine node to either internal disks or external disks. The following are the requirements for a node with a dedicated metabase engine:

One dual-core processor Higher-speed processors enhance system performance. Greater numbers of processors and cores do not enhance system performance. 4 GB of ECC RAM Internal disks or external disks PureDisk requires metabase engine disks to be 7,200 rpm SCSI, fibre channel, or serial-attached SCSI disks with RAID 1. The PDOS installer creates the following partitions on these disks:

The /, swap, and /boot partitions, which require 23 GB of internal disk space. The /Storage partition, which requires between 250 GB and 300 GB of usable space after the RAID configuration.

To configure high availability, configure the /Storage partition on external disks that are visible to all active and passive nodes (shared).

Highly availability storage pool requirements

A highly available storage pool consists of at least one node that contains the PureDisk services and at least one passive node. Typically, you configure the PureDisk services on several nodes, and then you configure one or two passive nodes. The following are the high availability requirements:

All nodes in a cluster must have equivalent hardware capabilities. This requirement pertains to areas such as CPU performance, memory, etc. This requirement applies equally to both active nodes and passive nodes for the following reasons:

Any node must be able to act as a passive.

PureDisk hardware requirements Capacity planning for nodes and services' databases

41

If a formerly active node fails, it can be repaired and brought up again as a passive in the cluster.

Each node that you configure must be connected to external storage. The /Storage partition must be attached to external disks. You cannot configure high availability if any of your nodes use only internal disks. All the nodes must be able to access the /Storage partition on the external disks.

Capacity planning for nodes and services' databases

The following topics contain information about node-specific capacity and database needs. See "Capacity planning for a storage pool" on page 41. See "Metabase engine capacity planning" on page 43. See "Content router capacity planning" on page 44. See "Service databases capacity planning" on page 46.

Capacity planning for a storage pool

The following topics contain Symantec's recommendations for planning the whole storage pool.

Number of clients per storage pool

A PureDisk storage pool supports a maximum of 1000 clients. Consider installing one or more additional storage pools if you need to protect more than 1000 clients at a location. PureDisk performs data deduplication within a storage pool, not across storage pools. Plan to back up similar clients, which are more likely to have duplicate data, to the same storage pool for optimal data reduction.

Number of simultaneous backup streams

A PureDisk storage pool supports simultaneous backups of up to 300 streams. Consider grouping client backups according to a schedule that backs up a maximum of 300 streams simultaneously. You can increase the number of parallel streams to 1000 if you change the content router configuration and if you add 1 GB RAM to the content router nodes. If you need to run more than 1000 backup streams simultaneously, consider installing one or more additional storage pools. If you use the PureDisk

42

PureDisk hardware requirements Capacity planning for nodes and services' databases

Deduplication Option (PDDO), each NetBackup stream that is deduplicated in parallel consumes three PureDisk streams.

Number of backup jobs per client

PureDisk can back up millions of files per client. However, Symantec recommends that you retain no more than 8 million file records and version records in one data selection. When data selections include more than 8 million records in the metabase, they degrade backup job performance. PureDisk limits the number of records in one data selection to 16 million. You may need to retain more than 8 million files and versions per client. If so, create multiple data selections with a maximum of 8 million records per data selection. To protect all the client data, schedule the backup jobs for each of these data selections consecutively. Multiple data selections on one client have no negative effect on data deduplication. When you use the same segment size for data selections, PureDisk globally deduplicates the data across data selections on all clients in the storage pool. Consider the following example. A client has 500,000 files to back up. The daily file change rate for this client is 5%. The file change rate is equal to the sum of the number of new files + the number of modified files + the number of deleted files. You want to retain all of the backed up files and their versions for 60 days. Table 3-5 represents the example client that is described. Table 3-5 Data type

Initial full backup Incremental backup

Client backup estimation example Change

100% 5%

Data selection records

500,000 25,000

If you retain all of the files and their versions for 60 days before you remove the older versions, the records eventually grow to 2,000,000. The calculation is as follows: 500,000 + (60 × 25,000) = 2,000,000 records

Number of user accounts

You can create user accounts with user or administrator permissions to operate on the same storage pool. Do not create over 500 user accounts per storage pool. If you create over 500 user accounts, the responsiveness of the Web UI can degrade.

PureDisk hardware requirements Capacity planning for nodes and services' databases

43

Metabase engine capacity planning

You can configure a metabase engine service on either a dedicated, standalone node, or a multiservice node with other PureDisk services. A metabase engine on a dedicated node can store records for more files and file versions than a metabase engine that you configure on a multiservice node, as follows:

A metabase engine on a dedicated node can store the metadata of approximately 140 million file and version records. A metabase engine on a multiservice node can store the metadata for approximately 100 million file and file versions.

File metadata accumulates for every file and version that you retain in a PureDisk storage pool. Depending on whether you configure your metabase engine(s) as dedicated nodes or as a multiservice node, plan to include one metabase engine for every 140 million file records and version records or every 100 million file records and version records. To retain more than these recommended limits, configure more than one metabase engine. If you replicate data from one storage pool to another, PureDisk replicates the metabase engine's data, too. The target storage pool is the storage pool to which PureDisk writes replicated data. Make sure that the target storage pool has enough capacity in its metabase engine to store the following:

The copied data from the source storage pool. The regular, local backup data from its own clients.

To estimate the amount of storage to attach to a metabase engine, consider the following:

The number of files that you want to back up. This number represents all of the files that currently reside on the clients' primary storage. The rate at which the files are modified and added to the clients. PureDisk creates new records in the metabase engine's database when files are modified or added. Note that if a user deletes a file from source, PureDisk does not automatically delete the metabase entry for that file. You can configure policies for removing expired backup copies and their metabase information. (Optional) The amount of data you want PureDisk to replicate to this metabase engine from a remote storage pool. Consider this option only if you plan to enable replication.

44

PureDisk hardware requirements Capacity planning for nodes and services' databases

The retention period, which is amount of time you want to keep the metadata on the metabase engine.

If you configure multiple metabase engines, PureDisk assigns a client to a particular metabase engine. This assignment occurs when you register the client's agent with the storage pool authority. PureDisk stores all the data for a client on the client's assigned metabase engine. With replication enabled, PureDisk sends the metadata from a metabase engine in the source storage pool to a metabase engine in the target storage pool. For example, assume that storage pool A has one metabase engine and storage pool B has four metabase engines. You enable replication from storage pool A to storage pool B. How much data PureDisk writes to the four metabase engines in storage pool B depends on the available capacity on those metabase engines. When you create the replication policy, the metabase engine with the most available space in storage pool B receives all of the replicated data. If you have up to 100 million records (multiservice node) or 140 million records (dedicated node) per metabase engine, backup job performance can be affected. For this reason, you must keep the number of records per data selection to under 8 million. Information about how to limit the number of files in a data selection is available. See "Number of backup jobs per client" on page 42. A metabase engine includes a database. Information about database capacity needs is available. See "Service databases capacity planning" on page 46. Note: If you use PDDO, the metadata for each individual file is stored in the NetBackup catalog, not in the PureDisk metabase. For each NetBackup image that is stored in the PureDisk storage pool, PureDisk creates ten entries in the PureDisk metabase.

Content router capacity planning

The content routers store the file content that PureDisk backs up from client primary storage.

Planning for additional content routers

When PureDisk backs up a file, it breaks large files into segments, and it writes the segments to one or more content routers. The default segment size differs depending on the type of data that you want to back up. The default segment size is 128 KB for files and folders, Microsoft Exchange data, and Microsoft SQL data.

PureDisk hardware requirements Capacity planning for nodes and services' databases

45

The default segment size is 256 KB for system state and services data. By default, PureDisk does not segment any files that are smaller than the default segment size. For example, if you back up files and folders only, a content router can support 80,000,000 file segments with 8 TB of addressable storage. Your backup requirements may exceed 8 TB of content router disk space. If you need more space, you can create additional PureDisk nodes in your storage pool and install additional content routers on those nodes.

Disk space requirements for a content router

You can estimate the amount of storage to attach to a content router by considering the following:

The amount of file data you want to back up. This amount is the number of bytes of data that currently resides on the clients' primary storage. (Optional) The amount of data you want PureDisk to replicate to this storage pool from a remote storage pool. Consider this option only if this content router is part of the target storage pool to which the data is replicated. With replication enabled, PureDisk sends the data from a content router in one storage pool to all of the content routers in another storage pool PureDisk distributes the data to all content routers in the target storage pool evenly. Your target storage pool may have two or more content routers. Remember that the data each content router receives from the source storage pool is divided among all content routers in the target storage pool. For example, assume that storage pool A has one content router and storage pool B has four content routers. You enable replication from storage pool A to storage pool B. Because storage pool B has four content routers, each router receives one quarter of the data from storage pool A. The amount of data reduction. PureDisk reduces data during a backup by applying global data deduplication, file segmentation, and file compression technologies. For example, you can expect to see the following global data deduplication for Microsoft Office files:

75% for the initial backup 99% for daily incremental backups

As PureDisk backs up files from primary storage and writes files to content router storage, PureDisk typically reduces storage consumption to 25% of the

46

PureDisk hardware requirements Capacity planning for nodes and services' databases

original file size on primary storage at the first full backup. Consecutive PureDisk backups typically add only 1% of the average original file size to storage.

The retention period, which is the amount of time you want to keep backups on the content router

For example, assume that your site has 1,000 GB of source data to protect. You want to retain backup copies for 60 backup days. Use the following numbers to make the calculation:

Source data of 1,000 GB × 25% = 250 GB needed for the initial backup Source data of 1,000 GB × 1% = 10 GB needed for incremental backups 250 GB + (10 GB × 60 days) = 850 GB total storage needed

You might replicate this data to another storage pool with the same 60-day retention policy. Without filters applied, you must allocate another 850 GB of storage for this data in the other storage pool. PureDisk spreads the data equally over the number of content routers in the target storage pool. PureDisk applies its global data deduplication technology on replicated data. Therefore, the actual amount of storage that the other storage pool requires is likely to be less than 850 GB. You can monitor the storage pool log files and change your storage allocation as needed. A content router includes a database. See "Service databases capacity planning" on page 46.

Service databases capacity planning

The PureDisk metabase engine, content router, and storage pool authority services each have an internal database. Symantec recommends that you limit the size of a node database to less than 250 GB. Databases on dedicated metabase engine and content router nodes do not typically reach this limit. However, if you configure an all-in-one storage pool, the metabase engine, content router, and storage pool share a common database. If you configure an all-in-one node, you need to monitor the size of the database and add additional nodes if the databases reach their capacity. PureDisk creates one record in the metabase engine's internal database for each file during the initial backup. It adds a record when each file changes. The average length of a metadata record is 500 bytes. The actual metadata record length depends on the number of characters in the file name and the path.

PureDisk hardware requirements High availability requirements

47

For example, assume that across all the clients at your site, you have 20,000,000 files to back up. Of these files, 5% change on a daily basis. You want to retain all versions of these files for 60 days. Table 3-6 summarizes the information about the files at this site. Table 3-6 Data type

Source data Index in metabase 100%

Characteristics of file data to back up Change Internal database records

20,000,000 20,000,000 1,000,000

Daily incremental indexes in 5% metabase

If you retain all files and their versions for 60 days before you remove the older versions, the metabase engine records eventually grow to 80,000,000. The metabase engine eventually consumes 40 GB of disk space. The calculations are as follows: 20,000,000 + (60 × 1,000,000) = 80,000,000 records 80,000,000 records × 500 bytes per record = 40 GB of storage Note: If you use PDDO, the metadata for each individual file is stored in the NetBackup catalog, not in the PureDisk metabase. For each NetBackup image that is stored in the PureDisk storage pool, PureDisk creates only three entries in the PureDisk metabase.

High availability requirements

You can configure PureDisk services for high availability. PureDisk documentation uses the term highly available or clustered to refer to the storage pools that use the Veritas Cluster Server (VCS) software for high availability. In a highly available PureDisk storage pool, all services reside on nodes in one or more clusters. In the event of a malfunction, the VCS clustering software moves the service group from one node to another automatically and ensures high availability. Symantec supports the ability to configure highly available services at the time you perform the PureDisk initial installation and configuration. After you install and configure PureDisk, you cannot reconfigure that storage pool for high availability.

48

PureDisk hardware requirements High availability requirements

In a highly available PureDisk environment, you can configure one or more PureDisk services on a node. The services on a node comprise a service group. Each node contains a NIC that has a service FQDN assigned to it. The service FQDN of each node is wired to the PureDisk service group. PureDisk associates a storage pool's services with the service FQDN of the node upon with they are configured. When the service FQDN moves, VCS moves all the PureDisk services for that service FQDN. Note: Symantec recommends that you contact Symantec Consulting Services for the installation of a clustered, highly available PureDisk storage pool.

High availability storage pool hardware requirements

Make sure to design your PureDisk environment to meet the following general requirements:

One or more servers to act as primary, active nodes. One or more passive nodes. External storage on a SAN. The following additional information also applies to the SAN:

The PureDisk software installation package includes the Veritas Volume Manager (VxVM), the Veritas File System (VxFS), and the Veritas Cluster Server (VCS) software. The storage pool configuration wizard configures VCS, VxVM, and VxFS. You can configure either /Storage in one partition, or you can configure separate /Storage/data and /Storage/databases partitions. The SAN must include the disk devices that VxFS supports. PureDisk does not support iSCSI disks for high availability. More information about disk device compatibility is available. http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672 NAS storage should not be used for a highly available PureDisk storage pool.

Java administration console requirements

You can administer the PureDisk cluster through the Veritas Cluster Server Java console. This console is a graphical user interface. During the configuration process, you install the PureDisk storage pool software and then you configure the cluster software. After you configure the cluster software, you can install the

PureDisk hardware requirements High availability requirements

49

Java Console on a remote Linux or Windows system. The system from which you run the Java console must be a remote workstation. After installing the Java console on a remote computer, you can administer each node in the cluster remotely. The following are the minimum hardware requirements for the Java console:

A 300 MHz Pentium II processor. Symantec recommends a 400 MHz Pentium III processor. 256 MB RAM 800x600 display resolution A monitor with 8-bit color depth A graphics card capable of 2D images

The version of the Java 2 Runtime Environment (JRE) requires 32 MB of RAM. The JRE is supported on the Intel Pentium platforms that run the Linux kernel v2.2.12 and glibc v2.1.2-11 (or later). Symantec recommends that you use the following:

48 MB of RAM 16-bit color mode KDE and KWM window managers that are used with displays set to local hosts

To install the Java console on a Windows remote workstation

1 2

Insert the PDOS media into the remote workstation. Navigate to the following directory on the PDOS media:

D:\vcsmp3\windows\WindowsInstallers\WindowsClusterManager\EN

3

Run setup.exe.

To install the Java console on a Linux remote workstation

1 2

Insert the PDOS media into the remote workstation. Mount the PDOS the PDOS media using the following command:

mount /dev/cdrom /mnt

3

Run the installer using the following command: # /mnt/vcsmp3/cluster_management_console/installcmc

VCS software requirements

The VCS software enables high availability in a PureDisk environment.

50

PureDisk hardware requirements High availability requirements

The following documents explain the hardware prerequisites that must be met to install VCS in a PureDisk environment:

Veritas Cluster Server 4.1 Installation Guide for Linux Veritas Cluster Server 4.1 Release Notes for Linux

Make sure that you familiarize yourself with the VCS documentation before you begin to install the product. PureDisk Storage Pool Installation Guide

PureDisk software requirements

The PureDisk software distribution includes all the software that you need to configure a highly available PureDisk storage pool. No additional software requirements exist. This topic explains how a typical Veritas Cluster Server (VCS) solution is incorporated into the PureDisk software distribution package. VCS is a high availability solution for cluster configurations. In the context of PureDisk, VCS monitors the PureDisk services that reside on an individual server system, or node. Each cluster includes a passive node, which you initially configure without any hosted services. When VCS detects a hardware failure or a software failure, it restarts the services on the passive node. The Symantec Veritas SF (Storage Foundation) software typically includes the VCS software. The PureDisk package includes the SF software binaries and the VCS binaries. In addition, the PureDisk license includes the licenses for these additional products. The VCS Web UI conflicts with the PureDisk Web UI. Do not install the VCS Web UI. If you install the VCS Web interface, the subsequent PureDisk installation replaces it with the PureDisk Web UI. The PureDisk software distribution includes the VCS Java console. Use the VCS Java console to administer VCS. For more information about hardware compatibility, see the Storage Foundation hardware compatibility list on the Symantec Web site.

Network requirements

Each server node that you want to include in a cluster requires three NICs:

One NIC is required for the public network. Two additional NICs are required for the private heartbeat network.

These NICs must be connected to the private network NICs on the other nodes. The following list contains more information about these NICs and their roles:

PureDisk hardware requirements High availability requirements

51

The public NIC manages backups, restores, and typical PureDisk communications. This card also lets you access the node for installation, configuration, and typical system maintenance activities.

A host IP address and a host FQDN In a cluster, use these identifiers to contact the node for system maintenance activities from outside of PureDisk. This address is the administrative address. A service IP address and a service FQDN PureDisk associates all PureDisk services with this service IP address and service FQDN. In a cluster, when a failover occurs, VCS moves these identifiers, and their associated services, from an active node to a passive node.

The first private NIC detects and monitors the cluster heartbeat. This NIC also manages internode communication in the cluster. It connects the node to the cluster's private network. The private network is internal to the cluster. Do not configure an IP address or an FQDN on this NIC. If an IP address or FQDN are already configured on this NIC, unconfigure them. The VCS software requires exclusive use of these cards, and VCS does not use TCP/IP. The second private NIC detects and monitors a redundant heartbeat. This NIC connects the node to the cluster's second (redundant) private network. Connect this card to a switch that is different from the switch for the first private NIC. The private network is internal to the cluster. Do not configure an IP address or an FQDN on the private NIC. That is true for the other private NIC. If an IP address or FQDN are already configured on this NIC, unconfigure them. The VCS software requires exclusive use of these cards, and VCS does not use TCP/IP.

The following additional information describes how to configure network cards:

During typical operations, the nodes in a cluster ping each other. When VCS detects that a node is down, the cause can be a node malfunction or a network malfunction. If the network malfunctions, then card 2 and card 3 can appear to be malfunctioning. When the two private network links are down and VCS does not receive heartbeat from a node, it marks the node as DOWN. It excludes the node from the cluster. The cluster takes corrective action, which can initiate a failover. From node to node, make sure to connect all the NICs that form the two private networks.

52

PureDisk hardware requirements High availability requirements

Configuration examples

A PureDisk high availability configuration is similar to other high availability configurations that use Veritas Cluster Server . Figure 3-1 shows the network connections between the services in a VCS configuration. Figure 3-1 A four-node cluster

Client Workstation Public Network

Client Workstation

Private Network

VCS Nodes

Shared Storage

In this figure, the storage pool's four nodes are configured into one cluster. The cluster consists of three nodes that are configured with services and one passive node. In the event of a malfunction, the VCS fails over the services from the malfunctioning node to the passive node.

PureDisk hardware requirements High availability requirements

53

Figure 3-2 shows the network connections between the services in a different VCS configuration. Figure 3-2 A cluster with two private networks and one public network

VCS Private Network Two Ethernet Connections

Shared Disks sysA sysB

Public Network

Terminology

The documentation for highly available PureDisk includes the following terms:

Active node A node with PureDisk services configured and running on it. Compare to passive node. Two or more nodes with failover capability. At least one node must be configured as a passive node. The host IP address, the host name, and the host FQDN are the identifiers for a particular server node. These addresses are associated with the node hardware. These addresses reside on the public NIC in each node, and these are the address that an administrator can use for system administration purposes. For example, these are the addresses that you use to log into a node to perform system maintenance, to install PDOS, to install VCS, and to verify the state of the computer. In an unclustered storage pool, the service address is most likely the same as the host address, but that is not a requirement. Compare to service address.

Cluster

Host address

54

PureDisk hardware requirements High availability requirements

Passive node

In a highly available storage pool that is managed by VCS, a passive node is a node with PDOS and VCS software that is installed upon it but without any active services that are configured or running. A passive node can assume the role of an active node after a VCS failover. Compare to active node. A NIC that is reserved for internal, proprietary use. A VCS cluster requires two private NICs to monitor the state of the cluster. These NICs are not available for other use. Compare to public NIC. The service IP address, the service host name, and the service FQDN are the identifiers for the service group that resides on a particular node. When you configure VCS, you define the service addresses on the public NIC that resides in a node. VCS manages the service IP address as a service group. When a failover occurs, the VCS software moves the node's service group. That includes the PureDisk services and the node's service address, to a passive node. In an unclustered storage pool, the service address is most likely the same as the host address, but that is not a requirement. Compare to host address.

Private NIC

Service address

Public NIC

A NIC that is available for applications to use. Compare to private NIC. A VCS service group is a collection of resources that reside on one node and work together to provide application services. A service group typically includes multiple resources, both hardware and software, working together. If one resource in a service group fails, VCS moves all the resources in the service group to one of the passive nodes. When you use the storage pool configuration wizard, the PureDisk VCS resources that you need to configure are as follows:

Service group

The NIC The service address The disk group The disk volume The shared disk mount point The PureDisk services that are installed on the node

Shared disk

An external disk that is accessible to all PureDisk nodes but only one node has access at a time.

PureDisk hardware requirements High availability requirements

55

Virtual address

The virtual IP address, virtual host name, and virtual FQDN. These addresses are not connected to a specific computer or NIC. Incoming packets go to the virtual address, but all packets travel through real network interfaces. In a clustered storage pool, the service address is a virtual address. PureDisk requires you to add the virtual address to a node when you configure VCS. After installation, VCS controls the virtual address.

Planning a cluster

The following procedure can help you plan your highly available PureDisk configuration. Perform this procedure before you begin to install any PureDisk software. To plan the cluster

1

Complete the spreadsheet that is included in the following file in the puredisk/documentation directory of the PureDisk Application disk:

PureDisk_ClusterPlanning.xls

This spreadsheet requires that you obtain several types of information:

Network information about your default gateway, your NTP server, and etc. Disk groups and disk volumes names that you create for the cluster. Cluster information, including a unique ID for this cluster, a unique name for this cluster, etc. Network information for each node that includes public addressing information, service addressing information, and etc.

Your network administrator can help you complete this planning spreadsheet.

2

Read the installation information in the PureDisk Storage Pool Installation Guide.

Unsupported configurations

Symantec does not support the ability to convert a non-highly available storage pool to a highly available one. At installation time, you can configure a storage pool to be highly available or not. Within your backup infrastructure, you can mix and match both highly available and non-highly available storage pools. For example, you can configure a central

56

PureDisk hardware requirements High availability requirements

office's storage pool to be highly available, and you can configure remote office without the highly available feature.

Chapter

4

General prerequisites

This chapter includes the following topics:

About general prerequisites Client requirements Application agent requirements on Windows 2003 Application agent requirements on Windows 2008 Browser requirements Storage Foundation requirements PureDisk Deduplication Option requirements NetBackup requirements for PureDisk features Licensing requirements User authentication requirements Symantec Product Authentication Service requirements Firewall and networking requirements Changing security settings for Windows clients Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients Enabling snapshotting on Windows 2000 clients Configuring backups and restores of network shared drives or UNC paths on Windows platforms Configuring backups and restores of a NetApp filer on Windows platforms

58

General prerequisites About general prerequisites

Upgrade requirements

About general prerequisites

This topic describes the hardware and software that you are required to obtain and prepare before you begin to install the PureDisk software. PureDisk interoperates with additional Symantec software products and third-party software products. This topic contains compatibility information, but for more details on compatibility, visit the following Web site: http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672

Client requirements

You can install the PureDisk agent on a client as either a backup and restore agent or as a PDDO agent. For the specific client operating system levels that PureDisk supports, see the hardware compatibility matrix at the following Web site: http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672 The following requirements apply to all clients:

Each client must have a network connection to the storage pool authority node and to all other PureDisk nodes. A client needs at least 100 MB of available free space to install and run the PureDisk agent.

Backup and restore client platforms

You can install a PureDisk backup and restore agent on the following client platforms:

AIX HP-UX Linux Mac OS Solaris SPARC Windows 2000 Server Windows 2000 Professional

General prerequisites Application agent requirements on Windows 2003

59

Windows 2003 Server Windows XP Windows Server 2008

The following requirements apply to back up and restore clients:

For Windows clients, Symantec strongly recommends that you follow Microsoft's recommendations and upgrade to the latest patches. The minimum requirements are as follows:

For Windows 2003 platforms, confirm that SP1, SP2 or both is installed on each client computer. For Windows XP 64-bit platforms, confirm that SP2 is installed on each client computer.

During backups, a client stores lists of files that were backed up previously. PureDisk writes this file list to the client's temporary directory. An entry in this list consumes an average of 200 bytes, depending on the average path length and the file name length on the client. Up to three separate lists can exist on a client. For example, a client that backs up 1 million files stores three lists of 1 million files each. This operation requires 600 MB of disk space on the client. PureDisk uses a snapshotting technology to back up open files. See "Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients" on page 83.

PDDO client platforms

You can install a PureDisk PDDO agent on the following NetBackup media server client platforms:

Windows media servers Solaris SPARC Linux

Application agent requirements on Windows 2003

The PureDisk Windows client supports backups and restores for the following Windows application agents on Windows 2003 Server platforms:

Microsoft Exchange Server 2003 databases Microsoft Exchange Server 2007 databases

60

General prerequisites Application agent requirements on Windows 2008

Microsoft SQL Server 2000 databases Microsoft SQL Server 2005 databases Oracle databases versions 9i and 10g System state and services files on Windows 2003 Server and Windows XP 64-bit agents

The PureDisk Windows agent software includes these application agents. PureDisk uses the snapshotting technology to back up open files. See "Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients" on page 83.

Application agent requirements on Windows 2008

The PureDisk Windows client supports backups and restores for the following Windows application agents on Windows 2008 Server platforms:

Microsoft Exchange Server 2007 Service Pack 1 databases Microsoft SQL Server 2005 Service Pack 2 databases System state and services files on Windows 2008 Server and Windows XP 64-bit agents

The PureDisk Windows agent software includes these application agents. PureDisk uses the snapshotting technology to back up open files. See "Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients" on page 83.

Browser requirements

The PureDisk graphical user interface is Web-based . You can use the Web UI on any screen resolution of 1280 × 1024 pixels or higher. For an optimal user experience, Symantec advises that you maximize the browser window or use a higher screen resolution. Be aware that pop-up blocking must be disabled for the storage pool authority URL. The Web UI is compatible with the following browsers:

Microsoft Internet Explorer version 6 or 7. PureDisk does not support Internet Explorer version 8 at this time, however it may be used with Compatibility View turned on.

General prerequisites Storage Foundation requirements

61

Mozilla, which includes Firefox version 2 or 3.

In addition, PureDisk requires the Java platform version 6.

Storage Foundation requirements

PureDisk includes the Veritas Storage Foundation 4.1 MP4 software for Linux. The PDOS installation process explains how to use these products with PureDisk.

Software included with Storage Foundation

The Storage Foundation software that PDOS includes is as follows:

Veritas Volume Manager (VxVM) and Veritas Enterprise Administrator (VEA) The PDOS installation procedure installs VxVM and VEA automatically. Do not try to configure these items separately from PDOS. Veritas File System (VxFS) You can configure the VxFS file system if your disk types permit. PureDisk supports some disk types that are not compatible with VxFS. Symantec recommends that you use the VxFS file system with PureDisk if VxFS supports your disk types.

For information about hardware compatibility, see the Storage Foundation and PureDisk hardware compatibility lists. For information about how to use the Storage Foundation software, see the Storage Foundation documentation.

Supported disks and other hardware

VxVM supports dynamic multi-pathing (DMP). The DMP feature balances I/O across all available paths between the server and the storage devices to improve performance and availability. Some hardware vendors provide their own tools for multipathing, but Symantec recommends that you use VxVM's multipathing capability. VxVM includes some Array Support Libraries (ASLs) and drivers by default. If you have an array that needs a nondefault driver, download the ASL or APM separately and install the ASL or APM afterwards. Refer to the Storage Foundation hardware compatibility list to determine whether your array is supported or whether you need to download the ASL or APM. For example, if you have an EMC CLARiiON Cx00 array and you want to use it with PureDisk, install the ASL after you install PureDisk. VxVM makes all the internal changes.

62

General prerequisites PureDisk Deduplication Option requirements

For more information, visit the following Web sites:

For the ASL http://support.veritas.com/docs/286207 For the APM http://support.veritas.com/docs/283057

For general information about the Storage Foundation software, visit the following Web site: http://www.symantec.com/business/products/ otherresources.jsp?pcid=2245&pvid=203_1 For information about the arrays that VxVM supports, see the Storage Foundation 4.1 hardware compatibility list at the following Web site: http://entsupport.symantec.com/docs/277905

PureDisk Deduplication Option requirements

The PureDisk Deduplication Option (PDDO) enables you to configure a PureDisk storage pool as a NetBackup OpenStorage unit. The NetBackup OpenStorage API enables NetBackup to communicate with PureDisk. When you install the PDDO plug-in on a NetBackup media server, you enable NetBackup to write backups to a PureDisk storage pool. All data in a PureDisk storage pool is deduplicated, which reduces the amount of space that is needed for the NetBackup backup copies. Before you begin to install the PureDisk agent as a PDDO plug-in, make sure that the target server meets the following requirements:

Verify that the NetBackup media server where 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. Verify that you have all required licenses.

The PureDisk license that you used to install your PureDisk storage pool. Install this PureDisk license on your NetBackup media server. The NetBackup OpenStorage Disk Option license. If you do not already have this license installed in your NetBackup environment, obtain and install this license on the NetBackup master server and the NetBackup media server before you attempt to install and configure the PDDO plug-in.

General prerequisites NetBackup requirements for PureDisk features

63

For information about the NetBackup OpenStorage Disk Option License, see Symantec NetBackup Shared Storage Guide.

Verify that the media server is configured with NetBackup 6.5 or later. Verify that the media server meets the PureDisk PDDO client requirements. You can install the PDDO software on NetBackup Windows, Linux, and Solaris SPARC media servers. For more information about this requirement, see the following resources:

The PureDisk hardware compatibility list. http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672 See "Client requirements" on page 58.

NetBackup requirements for PureDisk features

PureDisk has some features that interoperate with NetBackup. These features require that you install a NetBackup DataStore license on the NetBackup server. The PureDisk license key includes a NetBackup DataStore license. The PureDisk features that interoperate with NetBackup are as follows:

The NetBackup export engine This feature lets you copy a backed up data selection from a PureDisk content router to NetBackup. NetBackup catalogs the data and copies it to tape or disk. After you export the PureDisk files to NetBackup, log into a NetBackup Administration Console . Treat these files as if they were native NetBackup files. From the administration console, you can generate NetBackup reports, browse the files, and manage the files. The NetBackup export engine requires you to install the NetBackup 6.0 MP5 or later software in your NetBackup environment. In addition, install the NetBackup client on at least one node in your PureDisk storage pool. For information about this feature, see the PureDisk Administrator's Guide. NetBackup disaster recovery This feature lets you write PureDisk disaster recovery backups to NetBackup. Symantec recommends that you use NetBackup to perform disaster recovery backups. Without NetBackup, you should implement a disaster recovery plan that copies files to a Samba shared file system or to a local file system. The NetBackup disaster recovery feature requires you to install the NetBackup 6.0 MP5 or later software in your NetBackup environment. It requires you to install the NetBackup 6.5 client software or NetBackup 6.0 MP5 client software on every node in your PureDisk storage pool.

64

General prerequisites Licensing requirements

For information about this feature, see the PureDisk Administrator's Guide.

PDDO More information about prerequisites and an introduction to this feature is available. See "PureDisk Deduplication Option requirements" on page 62. For comprehensive information about how to install and use the PDDO plug-in, see the PureDisk Deduplication Option Guide.

Licensing requirements

PureDisk requires a license key to install a server, to activate clients, and to activate application agents. Your Symantec representative can provide you with any information you require concerning PureDisk licensing.

User authentication requirements

By default, PureDisk authenticates users through its own internal OpenLDAP directory service. You can configure PureDisk to authenticate users through an external OpenLDAP or Active Directory service. You can configure PureDisk to authenticate users through an external directory service. You must verify that the software version level of your directory service is compatible with this PureDisk release. More information is available about supported levels of the OpenLDAP or Active Directory service. See the Symantec Technical Support Web site's compatibility matrix at the following Web site: http://www.symantec.com/business/support/ compatibility.jsp?language=english&view=comp&pid=52672

Symantec Product Authentication Service requirements

PureDisk requires that you configure the Symantec Product Authentication Service. The Symantec Product Authentication Service authenticates users and provides a single sign-on for Web UI use. The single sign-on capability allows users to log into one application and have access to multiple Web UIs. For example, users can log on one time to either PureDisk or Veritas Backup Reporter (VBR).

General prerequisites Symantec Product Authentication Service requirements

65

When you install a PureDisk storage pool, the installation software prompts you to specify a root broker and one or more authentication brokers. The authentication service uses these brokers. To use a root broker that is already installed on a host on your company's network, ensure that the host satisfies the following requirements:

The host has a network connection to the storage pool that you want to configure. The host is running the Symantec Product Authentication Service software, revision 4.3.28.0 or greater.

This service uses one network-wide root broker and several authentication brokers. Each authentication broker communicates with a root broker to provide trust in the user identities that other authentication brokers have verified. Authentication brokers support the default PureDisk internal OpenLDAP directory service and the optional external OpenLDAP and Active Directory services. More information is available on synchronization. See "User authentication requirements" on page 64. For background and more detailed information about using this authentication service, refer to the Symantec Product Authentication and Authorization guide.

Configuring brokers for PureDisk use

Symantec strongly recommends that you install only one root broker on your enterprise network. When you use the storage pool configuration wizard, you select the root broker type for the storage pool. A PureDisk storage pool can use another product's root broker services. Before you begin to install any PureDisk software, determine if you can use a root broker that already exists on your network. Caution: Do not install multiple root brokers in your network. Symantec recommends that there be only one root broker in an enterprise network. If you configure more than one root broker in your environment, single sign-on is not possible. Also, multiple root brokers require additional expert configuration to provide user authentication. For example, assume that you installed a root broker for use by NetBackup, or some other Symantec product on your network. Now you want to install PureDisk on the same network. You can configure your PureDisk storage pools to use that existing root broker.

66

General prerequisites Symantec Product Authentication Service requirements

PureDisk installs an authentication broker (AB) on every PureDisk storage pool authority. The authentication broker communicates with the network's root broker to provide trust in the user identities that other authentication brokers verified. This topic describes how the brokers interoperate in a Symantec software network. Use this information in this topic to plan your security configuration now. Figure 4-1 is a flow chart that can help you plan and configure brokers. Your path through the chart varies based on the number of storage pools you install and where your root broker is installed in your environment. Figure 4-1

Start

Planning a PureDisk broker deployment

Is a root broker installed on the network?

No

See "About local root broker configuration"

Yes

Is the root broker installed on a PureDIsk storage pool?

Yes

See "About local root broker and remote authentication broker configuration"

No

See "About external root broker configuration"

The following topics explain the relationships between the brokers and how to specify these relationships when you install a PureDisk storage pool. You may

General prerequisites Symantec Product Authentication Service requirements

67

find it useful to refer to the information about the broker configuration in the PureDisk Storage Pool Installation Guide.

About local root broker configuration

The local root broker configuration installs a root broker on a PureDisk storage pool. Plan to use the local root broker option when both of the following points are true:

You have not yet installed and configured a root broker anywhere in your PureDisk environment No root broker that you want to use exists on your network.

In a local root broker configuration, a PureDisk storage pool has both a root broker and an authentication broker installed. Other Symantec products and other storage pools that you install subsequently on the network can use this root broker. Choose only one PureDisk storage pool to host a root broker. If you plan to configure a PureDisk central storage pool for reporting, this storage pool is a good choice to host a shared root broker. Figure 4-2 Storage Pool Install using the Local option

Storage pool installation using the Local option

PureDisk storage pool

Root broker + authentication broker

68

General prerequisites Symantec Product Authentication Service requirements

About local root broker and remote authentication broker configuration

The local root broker and remote authentication broker configuration installs a local root broker on a storage pool. It also installs several authentication brokers on the other storage pools. Note: Install only one local root broker in a PureDisk storage pool. Configure all other storage pools in your environment to use this single root broker. Plan to use the local root broker and remote root authentication broker option when both of the following points are true:

You plan to install more than one storage pool You have no other Symantec product on the network that has a root broker

To see three storage pools and locations for root brokers and authentication brokers, refer to Figure 4-3.

General prerequisites Symantec Product Authentication Service requirements

69

Figure 4-3

Local root broker + remote authentication brokers

Storage pool installation using the Local option

PureDisk storage pool A

Root broker + authentication broker Storage pool installation using the Remote option

PureDisk storage pool C

Root broker + authentication broker Storage pool installation using the Remote option

PureDisk storage pool B

Root broker + authentication broker

Figure 4-3 shows the local and the remote broker configuration. The local and the remote broker configuration has the following features:

Storage pool A has a root broker and an authentication broker installed. The broker was installed as a local broker. This storage pool is the first one installed

70

General prerequisites Symantec Product Authentication Service requirements

on the Symantec network. The storage pool is also the first software that you installed on the Symantec network with an authentication broker.

Storage pools B and C reside on the same network and have only authentication brokers installed. You configured these storage pools after you configured storage pool A. The authentication brokers on storage pools B and C communicate with and run under control of the shared root broker on storage pool A.

When you use the storage pool configuration wizard to configure these storage pools, configure them as follows:

For the first storage pool you configure, specify a local root broker. This method installs a root broker and an authentication broker on that PureDisk storage pool. Configure this storage pool first. For the other storage pools, specify a remote root broker. This option installs only an authentication broker on these storage pools. Configure these storage pools after you configure the storage pool with the local root broker. For these and all subsequent storage pools you add, specify a remote root broker. This configuration option uses the existing root broker that was installed on the first storage pool. It installs only an authentication broker on any new additional storage pools. When you configure a storage pool to use a remote root broker, the wizard prompts you to specify the following information about the storage pool that hosts the local root broker:

The fully qualified domain name of the storage pool authority. The root broker password.

About external root broker configuration

To install storage pools on a network that already uses the Symantec Product Authentication Service , plan to install an external broker on all storage pools. An external broker configuration uses a root broker that was previously installed and is available somewhere outside of all your PureDisk storage pools. This external host is not a PureDisk node. For example, this root broker can be one that VBR also uses. When you configure a storage pool to use an external root broker, PureDisk installs only an authentication broker on each storage pool. The authentication broker on each storage pool communicates with the root broker on the external host. If you decide to use an existing external root broker, consider the following points:

Configure all of your PureDisk storage pools to use the same external root broker.

General prerequisites Symantec Product Authentication Service requirements

71

Ensure that the external host has a network connection to the storage pool you are configure. Any version of the authentication broker can communicate with any version of the root broker. Therefore, you can upgrade the software version of the external root broker safely. Specify an external root broker when you use the storage pool configuration wizard.

Figure 4-4 shows two storage pools, X and Y, that use an external root broker. This root broker is installed on host C, which is not part of a PureDisk storage pool.

72

General prerequisites Symantec Product Authentication Service requirements

Figure 4-4

Storage pools that use an external root broker

Root broker installation on a non-PureDisk host

Non-PureDisk host C

Root broker Storage pool installation using the External option

PureDisk storage pool Y

Authentication broker

Storage pool installation using the External option

PureDisk storage pool X

Authentication broker

Figure 4-4 shows an example of using an external root broker. To configure an authentication mechanism with an external root broker, you need information about the external host before you begin to install PureDisk. To collect

General prerequisites Firewall and networking requirements

73

the required information about the root broker and its external host see the PureDisk Storage Pool Installation Guide.

Firewall and networking requirements

You configure the firewalls that protect PureDisk clients to permit network connections to all of the PureDisk nodes in a storage pool. Symantec strongly recommends that you deny connectivity between the clients and IP addresses outside of the PureDisk node addresses. If you add PureDisk nodes to expand a storage pool, enable connectivity between the PureDisk clients and the new PureDisk nodes. PureDisk relies on the accessibility of several ports between the clients and the PureDisk nodes. Be aware of the following information regarding firewalls and ports:

Firewalls can exist in the communication path between the clients and the PureDisk nodes. Use the port information in this section to configure the environment to allow these connections. If the Symantec Client Firewall is installed on a client, the PureDisk agent cannot run backup jobs with default settings. For information on the firewall settings, see the PureDisk Client Installation Guide. If personal firewall software is active on a client with the PureDisk agent installed, configure it to allow network connections as detailed in the following sections. All Web servers that accept connections on the HTTPS port, including PureDisk nodes, are potentially vulnerable to denial of service attacks. PureDisk nodes that are accessible to clients outside your corporate network should follow industry best practices when configuring firewalls and routers. This minimizes your risk of a successful denial-of-service attack .

If the connectivity requirements are not met and your firewall performs a passive drop, PureDisk does not generate a message that describes this situation. Your connection times out without notification.

Communication between client agents and the storage pool

Figure 4-5 shows the ports that the PureDisk nodes use for communication between client agents and the storage pool.

74

General prerequisites Firewall and networking requirements

Figure 4-5

PureDisk communication between client agents and a storage pool

Job management 443

Storage pool authority

Metadata checks 443

Metabase server 53

DNS server

Control management 10101 Metabase engine

10082 Data

Content router

Table 4-1 shows the communication ports.

General prerequisites Firewall and networking requirements

75

Table 4-1 Source

Client agents

Ports between client agents and their storage pool Port

10101

Destination

Controller

Protocol

TCP

Purpose and notes

Registers, authenticates, and controls. A metabase engine always hosts a controller service. Sends data. Checks and updates actions on the client side.

Client agents Client agents

Content router Storage pool authority Metabase server

10082 443 (HTTPS)

TCP TCP

Client agents

DNS server

53

UDP and TCP

Used when you install PureDisk with FQDNs or hostnames. Not used if you install PureDisk with IP addresses.

Communication between the storage pool authority and other services

Each service on a PureDisk node requires certain incoming ports to be open. The nodes themselves do not monitor the specific ports that the other nodes use to send information. Therefore, the ports need to be open to all communication. Figure 4-6 shows all the ports that need to be open on each PureDisk node.

76

General prerequisites Firewall and networking requirements

Figure 4-6

Storage pool authority communication

Administrator's host system 22, 443 2821

Root broker host

Storage pool authority and WebUI 21, 123, 443 21, 123, 443 22, 10101 21, 123, 443 Metabase engine 10101, 10085 22 10082 22, 10082

Content router 10101 Metabase server 10082

10101

Clients

General prerequisites Firewall and networking requirements

77

Note: For communication purposes, PureDisk interoperates with a NetBackup export engine service as if it were on its own self-hosted node. A gateway for this service needs to be on each node. Table 4-2 shows the communication ports. Table 4-2 Source Destination Ports between the storage pool authority node and other services Port

21

Protocol

TCP

Purpose and notes

Facilitates any PDOS upgrades.

All PureDisk node Storage pool services authority Storage pool authority Administrator's host system

All PureDisk node 22 (SSH) services Storage pool authority 22 (SSH)

TCP

Facilitates the PureDisk installation, upgrades, and maintenance. Performs inquiries.

TCP

All PureDisk node Storage pool services authority All PureDisk node Storage pool services authority Administrator's host system Storage pool authority Storage pool authority Root broker host

123

TCP and UDP

Synchronize time using ntpd service.

443 (HTTPS)

TCP

Monitors the communication among all other services. Connects to storage pool authority and then to PureDisk Web UI. Authentication between each node. Authentication from the storage pool authority to the broker. Exchanges data. Processes any queries on data selections. This port should be open only on metabase engine nodes. Controls the client agent software on the clients. Client agents and server agents connect to the storage pool through the controller. Facilitates any database dumps. Used only when disaster recovery through a Samba or CIFS share is implemented.

443 (HTTPS)

TCP

2821

TCP

All PureDisk nodes Content router Metabase server Metabase engine

10082 10085

TCP TCP

All PureDisk nodes Metabase engine and all clients

10101

TCP

All PureDisk node Samba shared file 137, 138, 139, TCP services (not system and 445 shown in figure)

78

General prerequisites Firewall and networking requirements

Table 4-2

Ports between the storage pool authority node and other services (continued) Port

10087

Source

Destination

Protocol

UDP

Purpose and notes

Facilitates debugging with the debug logging daemon (DLD).

All PureDisk node Storage pool services (not authority node shown in figure) All PureDisk node NetBackup services

NetBackup ports

Facilitates any disaster recovery through NetBackup. This communication is bidirectional. Used only when disaster recovery through NetBackup is implemented. See NetBackup documentation for protocols.

NetBackup Export NetBackup Engine gateways

NetBackup ports

Facilitates any exports to NetBackup. This communication is bidirectional. Used only when the NetBackup export engine is implemented. See NetBackup documentation for protocols.

Communication between PureDisk and other applications

Figure 4-7 shows the ports that are involved in communication between PureDisk and other applications.

General prerequisites Firewall and networking requirements

79

Figure 4-7

Communication between PureDisk and other applications

NetBackup

13724

123

NTP server

All PureDisk node services 53 (UDP)

53 (UDP)

DNS server

Administrator's host system

SNMP server

161

10087

DL daemon

SMTP server

25

Storage pool authority and server agents

10443 Veritas Backup Reporter (VBR)

2148 Veritas Enterprise Administrator (VEA)

14141 Veritas Cluster Server (VCS)

Table 4-3 provides more details about the ports that are used in communications between PureDisk and other applications. Table 4-3 Source

Storage pool authority

Ports between PureDisk and other applications Port

25

Destination

SMTP server

Protocol

TCP

Purpose and notes

Email notification for events.

80

General prerequisites Firewall and networking requirements

Table 4-3 Source Destination

Ports between PureDisk and other applications (continued) Port

53 (DNS)

Protocol

TCP UDP

Purpose and notes

Allows any management interventions. This communication is bidirectional. Used when you install PureDisk with FQDNs or host names. Not used if you install PureDisk with IP addresses.

All PureDisk node Corporate DNS services and server administrator's host system

All PureDisk node NTP client services

123

TCP

Synchronizes the local time to an external NTP server. This synchronization ensures that all server nodes are on the same clock. Traps SNMP packets.

Storage pool authority Any computer. For example, the administrator's desktop.

SNMP server

161

UDP

PureDisk nodes with the Veritas Enterprise Administrator (VEA) installed upon them Storage pool authority PureDisk nodes with the Veritas Cluster Server (VCS) installed upon them

2148

FTP UDP

VEA server.

Veritas Backup Reporter (VBR) Any computer. For example, the administrator's desktop.

10443

TCP

Facilitates the communication between VBR and the storage pool authority. VCS Java client.

14141

FTP

Replication and central reporting ports

Table 4-4 shows the ports that are involved in the communication between one storage pool and other storage pools. Table 4-4 Source

Metabase engine on the source storage pool

Replication and central reporting ports Port

443

Destination

Storage pool authority on the destination storage pool

Protocol

TCP

Purpose and notes

Facilitates PureDisk replication.

General prerequisites Firewall and networking requirements

81

Table 4-4 Source

Metabase engine on the source storage pool

Replication and central reporting ports (continued) Port Protocol

TCP

Destination

Purpose and notes

Communicates with the destination storage pool during replication. The metabase engine of the source storage pool contacts the storage pool authority of the destination storage pool. It retrieves data selection mapping, creates replication jobs, and performs additional functions. The metabase engine of the source storage pool contacts the content router of the destination storage pool to transfer data.

Content router on 10082 the destination storage pool

Central storage pool authority node

Centrally managed 443 (HTTPS) storage pool authority nodes

TCP

Facilitates the central reports. Used by the central reporting feature. The central storage pool uses Web service calls to retrieve license and capacity information. That obtains the information from the storage pools that are included in the central reporting storage pool authority's reports.

Intraclient communication

PureDisk uses port 7325 for interprocess communication such as file snapshotting through VSP and VSS. Table 4-5 provides the details about this port. Table 4-5 Source

Any Windows client

Intraclient communication ports on Windows clients Port

7325

Destination

The same Windows client

Protocol

TCP UDP

Purpose and Notes

Manages snapshotting. The following operations use this port: Files and Folders backups when snapshotting is enabled. All MS Exchange and MS SQL backups and restores.

System State and Services operations are not affected.

82

General prerequisites Changing security settings for Windows clients

If port 7325 is used for another purpose, edit the

%SystemRoot%\system32\drivers\etc\services file and add lines at the end to

specify a different port number. For example:

puredisk-ss puredisk-ss 7326/tcp 7326/udp

Ensure that you include a newline character at the end of the last line that you add so that Windows recognizes it.

Changing security settings for Windows clients

The following information applies if you use the PureDisk agent on a Windows 2003 or a Windows XP platform. It explains how to configure your system to meet the PureDisk network requirements. When Symantec Client Firewall and the Windows PureDisk agent are both installed, the firewall may report that the agent tries to listen to the Internet. This message occurs because when the agent connects, it listens on a random port for 1 millisecond. Either ignore the firewall warning or configure the firewall to always trust pdengine.exe. For more information about how to configure a firewall, see the PureDisk Client Installation Guide.

Changing security settings for Windows Server 2008 and Windows Server 2003

The default security settings in Windows Server 2008 and Windows Server 2003 prevent proper access to the storage pool authority Web UI. The settings also disallow the download of the PureDisk agent software. You can change the security settings in Internet Explorer. Use one or both of the following procedures to configure Internet Explorer. To change the security settings in Internet Explorer

1 2 3

Open Internet Explorer. Click Tools > Internet Options > Advanced. Clear the Do not save encrypted pages to disk check box in the Security section.

To enable Web UI access in Internet Explorer 6 on Windows Server 2008 and Windows Server 2003

1 2

Open Internet Explorer. Select Tools > Internet Options > Security > Trusted sites

General prerequisites Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients

83

3 4

Click the Sites option. Add the IP address or host name of the storage pool authority and the PureDisk nodes.

Changing security settings for Windows XP with service pack 2

The tightened security settings in Windows XP with service pack 2 require that you to revisit some system settings for the PureDisk storage pool authority Web UI. After you install service pack 2, the operating system activates the Windows firewall if it does not detect a third-party firewall on the system. In that case, the integrated Windows firewall blocks connections to the storage pool authority. Configure the firewall in such a way that the storage pool authority Web UI can get through. As an alternative, you can deactivate the integrated firewall, but then you need to configure a third-party firewall to protect the agent host. Internet security settings are more elaborate after service pack 2 is installed, and they affect the way PureDisk installs and upgrades its agents. A new setting controls the display of download prompts before an actual download starts. By default, no prompts are allowed, and this restriction prevents the PureDisk storage pool authority Web UI from downloading the PureDisk agent file. Use the following procedure to correct this situation. To enable the PureDisk storage pool authority Web UI to download files to an agent host

1 2 3 4

Open the Internet Options dialog box by selecting Tools > Internet Options from the Internet Explorer toolbar. Click the Security tab. Click Internet and click Custom Level to open the Security Settings dialog box. Scroll down to the Downloads section and set Automatic prompting for file downloads to Enable. Note that if you enable only the File Download setting, that does not fix the problem.

Enabling snapshot backups on Windows Server 2008, Windows Server 2003 or on Windows XP clients

PureDisk uses Microsoft's VSS technology to back up open files on Windows Server 2008, Windows Server 2003 or on Windows XP clients. Microsoft supports VSS on Windows Server 2008, Windows Server 2003 or on Windows XP platforms. On

84

General prerequisites Enabling snapshotting on Windows 2000 clients

Windows XP platforms, the snapshot configuration attributes are not supported. You can configure VSS through the Microsoft VSS configuration dialog boxes. For VSS to work properly, make sure Windows clients have the following items:

One local NTFS volume on the target system being snapped The snapshotting feature is supported only on NTFS volumes. The snapshotting software does not support other file system types. 300 MB or more of free disk space on the volume to be snapped This requirement is very strict. Snapshots fail with less free space. Correct firewall configuration If firewall software is enabled on a client and you enable VSS when you perform backups, the backup may fail at the Make snapshots step. The message PureDisk writes is vss_cmd_tool unexpectedly terminated with exit status 6007. This condition arises when the firewall blocks the PureDisk VSS application vss_cmd_tool.exe. Make sure that client firewalls do not block vss_cmd_tool.exe.

To ensure that you have all the latest VSS updates or to verify your VSS binaries, visit the following Web site: http://support.microsoft.com/kb/833167 To download updates, visit the following Web site: http://www.windowsupdate.com The preceding requirements are Microsoft Shadow Copy requirements. VSS enforces these requirements. No workarounds exist for these requirements. If clients do not meet these requirements, VSS returns the following message: VSS_E_INSUFFICIENT_STORAGE. By default, the Windows agent install process installs a copy of the Symantec Veritas Frozen Image (VxFI) software. Because VxFI is a required service for VSS, do not disable the VxFI package installation when you install the PureDisk agent on Windows agents.

Enabling snapshotting on Windows 2000 clients

PureDisk uses Symantec's Volume Snapshot Provider (VSP) technology to back up open files on Windows 2000 clients. The snapshotting software requires that there be one local NTFS volume on the target system being snapped. The snapshotting feature is supported only on NTFS volumes. The snapshotting software does not support other file system types.

General prerequisites Configuring backups and restores of network shared drives or UNC paths on Windows platforms

85

For general information about VSP, see the NetBackup Administrator's Guide, Volume 1. For information about how to use VSP to back up files with PureDisk, see the PureDisk Administrator's Guide.

Configuring backups and restores of network shared drives or UNC paths on Windows platforms

If you plan to use PureDisk to back up a network shared drive or UNC paths on Windows platforms, you must first configure the PureDisk agent to run under the Microsoft Windows Backup Operator group. See "Configuring the PureDisk agent to run under the Microsoft Windows Backup Operator group" on page 85.

Configuring the PureDisk agent to run under the Microsoft Windows Backup Operator group

By default on Windows platforms, the PureDisk client agent runs under LocalSystem. The following procedures configure users to run under Backup Operator and change the PureDisk agent to run under Backup Operator. Note: These procedures apply to the Windows XP operating system, but are similar on other Windows platforms. For the specific procedures that apply to Windows 2003 platforms or Windows 2000 platforms, see your Microsoft documentation. When you run backups under Backup Operator, PureDisk sets the permissions it needs for the agent to run and to read all of the ACL settings. For security purposes, the change also limits the user permissions that are allowed. Perform all of the following procedures to configure PureDisk users to run under Backup Operator:

See "To add users to the backup operator group" on page 86. See "To add the Manage auditing and security log rights for users who are added to the Backup Operator group" on page 86. See "To grant write permissions to users who are added to the Backup Operator group" on page 87. See "To change the PureDisk service to run under the Backup Operator group for each user" on page 88.

86

General prerequisites Configuring backups and restores of network shared drives or UNC paths on Windows platforms

Adding users to the backup operator group

The backup operator group is a predefined group within Microsoft Windows that has the appropriate rights to backup files. To add users to the backup operator group

1 2 3 4 5 6 7 8

Set up user accounts. Right-click My Computer and select Manage. Click Local Users and Groups. Double-click Groups to open the folder. Right-click Backup Operators. Choose Add to Group... . Click Add... . Specify a user name under which the pdagent service can run. To browse for a user name, use the following procedure:

Click Locations. Select the domain for the user name that you want to add. Click Advanced... . Click Find Now. Select a user name from the list. Click OK.

9

Click OK.

10 Click OK.

Managing Auditing and Security rights for the users that are backup operators

Add the PureDisk users to the group of users that have rights to manage the auditing and security logs. To add the Manage auditing and security log rights for users who are added to the Backup Operator group

1 2 3 4

Click Start. Click Control Panel. Double-click Administrative Tools. Double-click Local Security Policy.

General prerequisites Configuring backups and restores of network shared drives or UNC paths on Windows platforms

87

5 6 7 8

Click Security Settings > Local Policies > User Rights Assignment. Double-click Manage auditing and security log. Click Add User or Group. Specify the user name under which the pdagent service can run. To browse for a user name, use the following procedure:

Click Locations. Select the domain for the user name that you want to add. Click OK. Click Advanced... . Click Find Now. Select a user name from the list. Select the name you specified in the following procedure: See "Adding users to the backup operator group" on page 86. Click OK.

9

Click OK.

10 Click OK. 11 Close the Local Security Settings window.

Granting write permissions to users in the Backup Operator group

Confirm the user you added to the backup operators group has write permissions. This is the user you added in the following procedure: See "Adding users to the backup operator group" on page 86. To grant write permissions to users who are added to the Backup Operator group

1

Ensure that the user account has write access to the agent's working directory. This location can vary depending on where PureDisk is installed.

2

Open a Windows Explorer window. Tip: One way is to right-click Start and select Explore.

3

Right-click Program Files in the directory where the PureDisk agent is installed and select Sharing and Security. The default installation directory is C:\Program Files. Click the Security tab.

4

88

General prerequisites Configuring backups and restores of network shared drives or UNC paths on Windows platforms

5 6

Click Add. Specify a user name under which the pdagent service can run. To browse for a user name, use the following procedure:

Click Locations. Select the domain for the user name you want to add. Click OK. Click Advanced... . Click Find Now. Select a user name from the list. Select the name that you specified in the following procedure: See "Adding users to the backup operator group" on page 86. Click OK.

7 8 9

Click OK. In the box titled Group or user names, click the user you added. In the box titled Permissions for user_name, click in the Write box in the Allow column. Verify that a check mark appears in the box.

10 Click OK.

Changing the PureDisk service to run under the Backup Operator group for each user.

For PureDisk to run properly, you must change the PureDisk agent to run as a user with Backup Operator rights. To change the PureDisk service to run under the Backup Operator group for each user

1 2 3 4 5

Click Start > Run. At the Open: prompt, type services.msc. Right-click Veritas NetBackup PureDisk Client Agent and select Properties on the pull-down menu. Click the Log On tab. Select This Account.

General prerequisites Configuring backups and restores of a NetApp filer on Windows platforms

89

6

Specify the name of the user that you added in the following procedure: See "Adding users to the backup operator group" on page 86. Either type the domain name for the user name or click Browse and follow the browse prompts.

7 8 9

Type and retype your password. Click OK when this tab is complete. Click Restart to restart the PureDisk client service.

Configuring backups and restores of a NetApp filer on Windows platforms

To back up a NetApp filer using UNC Paths in PureDisk, all of the following prerequisites must be met:

If the data to be backed up resides in a volume or Qtree on the NetApp filer, it must be shared using CIFS on the filer and be visible to the windows client, as a UNC path (Universal Naming Convention in the format \\server_name\share_name). When you configure a volume or Qtree on a NetApp filer, multiple security styles are available.

UNIX Mixed NTFS

To successfully perform backups and restores of the NetApp Filer on a Windows client configure the security style on the volume or Qtree as Mixed or NTFS. If the configured security style at backup is UNIX and the restore style is UNIX or Mixed, errors can occur when PureDisk restores the files. If the configured security style at restore is UNIX, errors occur when PureDisk restores each file.

The PureDisk client service must be logged on as an account that is part of the Backup Operators group and has access to the NetApp CIFS share to be backed up. The account should allow the PureDisk client to view the volume or Qtree on the NetApp filer where the backup or restore is to be performed. The PureDisk client service must not be logged on as the local system account. If you attempt to back up or restore files from a NetApp filer and the service is logged on as the local system account, the backup or restore fails. In Microsoft Windows properly configure the PureDisk client service. More information on this topic is available:

90

General prerequisites Upgrade requirements

See "Configuring the PureDisk agent to run under the Microsoft Windows Backup Operator group" on page 85.

For snapshot-based backups of a NetApp filer, the PureDisk client must have access to each NetApp filer on which a snapshot is to be created. This authorization is set using a PureDisk client command.

C:\Program Files\Symantec\NetBackup PureDisk Agent\bin\pdusercfg --netapp=add --hostname=netapp_filer_host_name --username=user_id --password=password

In the previous command:

netapp_filer_host_name is the name of the NetApp filer. user_id is the name of administrative user on the NetApp filer. password is the password for the administrative user.

The --netapp parameter to the pdusercfg utility accepts the following additional arguments:

--netapp=delete, which deletes an entry from the configuration. --netapp=list, which lists all entries in the configuration. --netapp=update, which updates an existing entry.

Upgrade requirements

More information about how to upgrade a PureDisk storage pool to PureDisk 6.6, including upgrade requirements, is available. See the PureDisk Storage Pool Installation Guide.

Chapter

5

Known problems and product limitations

This chapter includes the following topics:

About known problems About PureDisk limitations

About known problems

The following topics summarize the problems that are known to exist in the PureDisk 6.6 software.

Policies with post script actions may not display checkmarks in administration webUI after upgrades from 6.5.x to 6.6 and later

After upgrading from PureDisk 6.5.x to PureDisk 6.6 and later, the Run post script only if the job ends with option is not shown as selected for Success or Success with error. It does show correctly if the Error option was selected. In 6.5.x, there was only the Error option for running post scripts. Post scripts always ran after successful policies in 6.5.x. Although neither success option is selected, the script runs as configured in PureDisk 6.5.x until the next time the policy is saved. Once the policy is saved without making any changes to the checkboxes, the post script does not run correctly. To resolve this issue, open any policy that has scripts configured to run after the policy runs, specify the correct options, and save the policy.

92

Known problems and product limitations About known problems

PureDisk does not support back up of DFS data

PureDisk is not designed to back up Distributed File System (DFS) data. PureDisk may appear to follow and back up DFS shares. The data is not, however, protected. That is by design. DFS data is commonly protected through the use of a Volume Snapshot Service (VSS) writer. File system backups should automatically skip DFS data. More information is available. http://support.veritas.com/docs/327423

Removing a disk from a disk group does not delete the partitions on the disk

After removing a disk from a disk group, the previously defined disk partitions still exist. The disk cannot be added to another disk group until all partitions are deleted. The storage pool installation wizard handles the partition deletion and disk removal. This should only be an issue when performing disk removal manually through YaST. For more information on how to set up and remove disks from disk groups, see the Symantec NetBackup PureDisk Storage Pool Installation Guide.

Backup of encrypted files not supported

PureDisk does not support the backup and restore of encrypted files and folders at this time. Attempts to backup encrypted information fails with the following message:

Warning: 71: process folder: 'File Name' is an encrypted folder. Encrypted files and folders are not supported.

The job fails with a SUCCESS_WITH_ERROR message.

Installing PureDisk on a Domain Name Server

Installing the PureDisk agent on a machine running a domain name (DNS) server requires the configuration of a dependency after the client installation finishes. The user must set a dependency between the PureDisk agent and the DNS service. The dependency allows the PureDisk hostname to resolve correctly when the computer starts.

Installation disk space requirements

When you specify a custom location for the PureDisk agent binaries, the installation wizard incorrectly reports the space that is required to complete the installation. PureDisk uses various third party components that in a typical installation are installed to a common location. In a custom installation, the

Known problems and product limitations About known problems

93

common files are installed to the non-default location specified. The installation wizard projects less than 50 MB of data to be installed in the custom location, but more than 70 MB is installed. If there is insufficient space to complete the installation, the install could begin writing data to the custom location, and then generate an out of space error message.

Incorrect error message when WebUI session timeout is exceeded

If the WebUI window is left inactive for longer than the session timeout value, selecting any activity in the WebUI correctly causes the window to close. The original logon window remains displayed, and incorrectly shows the error message "Invalid user name or password". More information about the adjusting the WebUI timeout interval is available in the Symantec NetBackup PureDisk Administrator's Guide.

Special characters in MS Exchange granular restore data

When you browse MS Exchange granular backups, some characters are converted to different characters and are displayed differently than the original email message. The following characters are changed:

The tilde (~) appears as ~0. The forward slash (/) appears as ~1. The backslash (\) appear as ~0.

That is expected behavior. All data is protected. When you search for mailbox items with these characters, it is necessary to use the ~0 and the ~1 characters in the search box.

Restore and recovery of individual Oracle archive logs

When you run a normal Oracle data selection restore and recovery using PureDisk, RMAN restores the archived logs required for recovery automatically. However, in some cases, you might be required to restore one or more logs. By default when you start a restore of archived logs from the administrative WebUI, PureDisk restores archived logs for the last 1 day to the default original location. In order to restore archive logs from the administrative Web UI, it is necessary to do separate backups of only the archive log folder. Create a separate data selection that includes only the archive logs folder and run a backup. When you restore from this data selection, do not modify any of the options in the

94

Known problems and product limitations About known problems

administrative web UI, since any changes are likely to cause an error. Just launch the restore with the default options. To change this behavior, specify the following options in the Agent.cfg file:

[oracle] arch_restoredest=alternate_location

With the arch_restoredest option, archive logs are restored to the alternate location that you specify. If RMAN determines that the requested logs exist already on the disk, it restores the logs even if the alternate location is specified.

[oracle] arch_restorefrom=from_clause

With the arch_restorefrom option, you can specify all archived logs or a range of archived logs for restore.

arch_restorefrom=all arch_restorefrom=all Specify this option to restore all archived logs.

arch_restorefrom=from logseq=seq_start thread=thread_number

Specify this option to restore archived logs from the log sequence start number (logseq=seq_start) and the thread number (thread=thread_number) that you provide. Subsequent archive logs are all restored.

arch_restorefrom=from logseq=seq_start until logseq=seq_end thread=thread_number

Specify this option to restore archived logs from the log sequence start number (logseq=seq_start) and the thread number (thread=thread_number) to the log sequence end number (logseq=seq_end) that you provide.

Repair of non-default location install of PureDisk on Windows 2008 appears to crash

Attempts to repair a PureDisk installation to a non-default location on a Windows 2008 server appears to fail. A variety of messages appear depending on the files that are missing or corrupt. Clicking the Close the program option allows the repair to complete successfully.

File pattern exclude incorrectly saved as folder pattern

When you add an exclude rule to a data selection, if you only enter a file pattern, PureDisk incorrectly saves this pattern as the folder pattern. If you put a / or *

Known problems and product limitations About known problems

95

in the file pattern field and left the folder pattern field empty, PureDisk saves the data selection as excluding / or *. To prevent problems, be sure to enter both a folder pattern and a file pattern for all excludes. Entering both a folder pattern and a file pattern eliminates this problem.

Lower than expected deduplication rates seen in NetBackup FlashBackup to PDDO

The deduplication rates for NetBackup FlashBackup to PDDO may be lower than expected. For a partition level flash backup, the less disk space that is allocated, the greater the change of a lower the deduplication rate. This is because in a partition level backup, the deduplication occurs on file boundaries. The unallocated space does not fall consistently on 128K boundaries. As a result, unallocated space does not deduplicate as well, and this affects the overall deduplication rate.

Configuration information may clear and the wizard may not advance during storage pool installation

On the Storage Pool Details page of the storage pool configuration wizard, the configuration information may clear and the wizard may not advance during installation. In addition, after clicking Next, the wizard may not advance. Symantec was unable to consistently reproduce the issue or determine a root cause. To resolve this problem navigate to: http://storage_pool_authority_ip_address/Installer Then restart the storage pool configuration wizard.

Job Progress in job details tab does not refresh

For an active job, select Monitor > Jobs, then the Job ID number, then click the Details tab. The Job Progress bar does not automatically refresh as the job progresses. To get the overall job progress bar to update, either press F5 or change to a different tab, and then change back.

The LDAP synchronization workflow may incorrectly report the maximum number of users supported is exceeded

The following error message may be reported when you attempt a synchronization with LDAP: "The supported number of users 500 has been exceeded." This message appears even though there are less than 500 users. To resolve this issue, remove all your groups from the "Manage groups" dialog, run the synchronization. Then add the groups back and run the synchronization again.

96

Known problems and product limitations About known problems

Incorrect log files displayed when expanding the archive log folder of an Oracle data selection

The log list may be incorrect when you expand the Archive Logs folder in an Oracle data selection. That does not affect the functionality of Oracle backups, since PureDisk supports only the backup of all log files. The list of log files can be incorrect if the database is recovered using control file.

PDDO Backup capacity not updating on Enterprise License Report

The PureDisk Deduplication Option backup capacity is not updated on the Enterprise License Report. Click Reports > Central SPA Dashboard > Enterprise License Report to see the report.

Unable to edit or view storage pool level event escalation action when there is an agent level escalation action added to the same event

When an event escalation action is added at both the agent and the storage pool authority level for the same event, attempts to edit the storage pool authority level action causes the WebUI to stop responding. To prevent this problem, create separate events for both the storage pool authority level and the agent level event escalation actions. That allows users to edit storage pool authority level action and modify any severity levels. If you want to continue using the same event to have storage pool authority and agent level actions configured, delete the existing storage pool level event action. This deletes the incorrectly referenced agent event escalation action. Then recreate the agent event escalation action. This prevents the issue from reoccurring.

Job Step Progress for Data Removal Job shows 0% complete even when job is finished

The Job Step Progress for a Data Removal Job shows 0% complete when the Job Progress shows the job is 100% complete. As a result, no logging information is displayed on the right side of the window. Job details can be viewed by clicking on the Job Log tab.

Services list appearing in narrow scroll window

Clicking Change in the Services Configuration section of the storage pool installation wizard causes all the services to appear in a narrow scroll window. Click Cancel or Help to list all the available services.

Known problems and product limitations About known problems

97

Custom settings and enhancements in pd.conf file require additional attention when upgrading PDDO client

PureDisk 6.6 introduced several changes to the pd.conf file, including the addition of the LOCAL_SETTINGS option. Changes to SEGKSIZE, MINFILE_KSIZE, MATCH_PDRO, and DONT_SEGMENT_TYPES in the local pd.conf file do not override the default values unless LOCAL_SETTINGS is enabled. Taking advantage of the new settings in the pd.conf file without losing any custom settings requires additional steps. Please review the Upgrading PureDisk software section of the Symantec NetBackup PureDisk Storage Pool Installation Guide for complete platform specific details.

Content router queue processing policy schedule reset after upgrade

After upgrading to PureDisk 6.6, the schedule for the system policy for content router queue processing is reset back to the default. The default schedule is twice a day at 12:00 A.M. and 12:00 P.M. If your environment requires this policy to run more often or at different times, change these settings after upgrading.

Users cannot edit data removal policies with a future date

Data removal policies with a future date (January 19, 2038) can be saved. The Web UI shows an error message whenever the user tries to view the policy again. The user is unable to edit the policy to correct the date. To resolve this issue, run the following script once:

/opt/pdag/bin/php /opt/PDOS/UpdateDRPolicies.php

MS Exchange granular restore fails when time zone settings inconsistent

The restore of MS Exchange items fails when the time zone setting is not consistent with the time zone setting on the PureDisk agent. If the system time is not within the same time zone, you are not able to browse and select MS Exchange items for restore. For example, if you set the system time on the PureDisk agent to 10:00 A.M. (local time in India) and the time zone to US CST (U.S. Central Standard Time), restores of Microsoft Exchange items fail.

PureDisk workflow engine log file can grow and rapidly fill the /Storage partition

When the workflow engine is running and the database (pddb) is not running, the workflow engine's log file (/Storage/log/pdwfe.log) may grow rapidly and fill the /Storage partition. To resolve this issue, do the following:

98

Known problems and product limitations About known problems

Preventing the pdwfe.log from growing rapidly

1 2

(Conditional) Freeze the PureDisk service groups for the clustered PureDisk server. Stop PureDisk.

# /etc/init.d/puredisk stop

3

Remove the large log file.

# rm /Storage/log/pdwfe.log

4

Start PureDisk.

# /etc/init.d/puredisk start

5 6

(Conditional) Unfreeze and online the PureDisk service groups for the clustered PureDisk server. Verify that the database server is running.

# /etc/init.d/puredisk status pddb

Data selection template incorrectly applied when created at storage pool level

When a data selection template is created and applied it at the storage pool level, the template is applied to all agents, including PDDO agents. This does not affect the functionality of backups and restores and PDDO agents can successfully backup data.

PureDisk upgrade fails if there is insufficient space on the content router

If the upgrade of the PureDisk software causes the content router to exceed 90% capacity, the upgrade fails. Before upgrading your content routers, review their capacity. If one or more content router is above 80% usage, consider running data removal before starting the upgrade. When usage approaches 90%, you need to free up more space before attempting the upgrade. The upgrade could fail to store new client agents on the content routers if you start the upgrade without checking this condition.

Documentation updates after the release

Symantec updates the PureDisk documentation on an as-needed basis. The most recently updated documentation for this release is available at the following Web site:

Known problems and product limitations About known problems

99

http://www.symantec.com/business/support/documentation.jsp?pid=52672 Symantec recommends that you check this Web site for updates before you install PureDisk and perform backups.

Files migrated by Remote Storage Service are retrieved at backup

Some server editions of Windows have a feature called Remote Storage Service. This service allows files to be migrated automatically from disk to remote storage media like tape. On the disk, a placeholder replaces these migrated files. The PureDisk agent does not recognize these files as being migrated. During a backup, the agent reads the content in the files. This read forces the Remote Storage Service to retrieve the files from remote storage and restore them. PureDisk should back up the placeholder instead of the actual file to which the placeholder refers.

Agent updates fail on clients due to inadequate permissions

On Windows clients, agent update jobs can fail if the user under which the PureDisk agent service runs is changed after the install. The problem occurs if the PureDisk agent service is configured to run under a user account with the following attributes:

It is part of the Backup Operators group It is not a local system account nor an administrator account.

Even if this user is given write access to the C:\Program Files directory, agent update jobs for this agent fail.

Cryptic messages

In several instances, user actions can cause PureDisk to generate some messages that are difficult to understand.

PureDisk reserved user IDs collide with some imported users

PureDisk reserves some user IDs and group IDs for internal use. You cannot import an ID from an external directory service that is identical to an ID that is reserved for use by PureDisk. You must identify external directory IDs that collide with PureDisk IDs. Do that before you enable TLS or link PureDisk to the external directory service. The reserved IDs are as follows:

The IDs for the internal PureDisk users. The IDs for the PureDisk agents.

100

Known problems and product limitations About known problems

To identify users and groups in your directory service that duplicate reserved PureDisk IDs, log into the storage pool authority as root and check for login IDs that are reserved for PureDisk's internal use. PureDisk has a limited list of agent ID accounts for its own internal use. None of the external directory service user IDs that you import can be the same as one of these internal PureDisk agent IDs. Run the following command on your PureDisk storage pool authority to obtain the list of internal user IDs that PureDisk reserves for its own use:

# /usr/bin/ldapsearch -x -D cn=admin,dc=puredisk -w password -b ou=users,dc=puredisk \ "(objectClass=PurediskUser)" | grep uid

For password, specify the password for PureDisk's internal OpenLDAP administrator account. The storage pool configuration wizard prompts you to define this password when you configure your storage pool. For example:

# /usr/bin/ldapsearch -x -D cn=admin,dc=puredisk -w root -b ou=users,dc=puredisk \ "(objectClass=PurediskUser)" | grep uid

This command returns the following list of reserved user IDs:

uid: uid: uid: uid: uid: uid: uid: root agent_23000000 agent_2 userA userB userC userD

Examine the output from the ldapsearch(1) command for user accounts with invalid characters. If a user account contains invalid characters, you cannot import that user account into PureDisk's internal OpenLDAP directory service. The list of invalid characters is as follows: (, ), <, and >.

PureDisk reserved patterns cause unexpected results

Internally, PureDisk uses the patterns in the following format to store data selections rules and file names: [0xhh]

Known problems and product limitations About known problems

101

In the preceding pattern, hh is a two-digit hexadecimal number. For example, 02, a3, FF. Consequently, you cannot use these patterns in data selection rules, in file names, or in any directory names that you specify in search terms. Use of the patterns generates unexpected results. For example, data selection rules may not match the wanted file name or directory names, and searches may not return the expected files.

I18N problems

PureDisk 6.6 offers better support for international characters than was present in earlier releases. PureDisk fully supports the Windows file systems. It fully supports all Linux and UNIX variants that use either a UTF8 locale or the C locale.

Double-byte characters do not display properly

PureDisk lets you view backed up files from a browser and download them to restore. When you perform this operation from Internet Explorer and use the Save As ... dialog box, the browser displays the file name as garbled characters. To remedy this problem, rename the file. This problem does not occur in alternate browsers such as Firefox.

Files downloaded through Web UI exhibit problems with international characters

The Find Files dialog box lets you download a file from the search results list. When you click a download link in Internet Explorer, the Save as ... dialog box can suggest an abnormal file name instead of the expected name. This error occurred only in a very few specific cases that involved both of the following:

The file name contained international characters. The file name that started with Copy of, which is the case when you create a copy of a file through Windows Explorer.

The problem only occurred with Internet Explorer, not with the Firefox browser. As a workaround, you can edit the file name in the Save as ... dialog box before you save the file.

Inability to restore from a localized Mac OS X path

You cannot restore a Mac OS X directory with a localized name. That is, directory restores fail if the directory name contains international characters. The restore

102

Known problems and product limitations About known problems

fails if, in the restore dialog, you explicitly selected the localized directory for restore. This defect does not apply to the directory names that do not contain international characters. As a workaround, you can restore from the root directory or from a nonlocalized higher-level directory.

PureDisk use of month/day/year format in log files

The agent log files always use the month/day/year format. This format is not internationalized.

Oracle backup of data files or tablespace names containing non-ASCII characters fail

PureDisk cannot back up Oracle data files or tablespaces with names containing non-ASCII character fail. Attempts fail with a failed to prepare statement error message.

Browsing for Oracle data files or tablespace names containing non-ASCII characters fails

The PureDisk WebUI does not let you browse for Oracle data files or tablespace names which contain non-ASCII characters. The names display incorrectly and cannot be backed up.

Erroneous errors in /Storage/log after installation

During installation, PureDisk may write error message to the files in /Storage/log. The writes occur because not all components are available at the same time during the installation process. These errors do not indicate any real problem and can be ignored. These messages may also appear in the Web UI.

Need to commit changes in YaST if subsequent changes could conflict

When you edit a disk group through the YaST interface, YaST queues the changes that you made. It does not implement them until you commit the changes. For this reason, an error for an invalid change often only appears at implementation time, not while you make the change. For example, an error occurs after the following sequence of events:

You create a disk group with one disk and commit this change. You add a second disk to the group, remove the first disk, and then commit these changes.

Known problems and product limitations About known problems

103

To work around this behavior, complete the following steps instead:

Create a disk group with one disk and commit this change. Add a second disk to the group and commit this change. Remove the first disk and commit this change.

Another way to work around the error is to first delete the disk group, and then create a new one with only the second disk. Note: This issue occurs only when using YaST, and not with the new storage pool installer wizard.

Restoring UNC files at the client level

When you restore files at the client level and selecting All Files and Folders in the Restore Files dialog box, the restore of files that are backed up by using UNC Paths data selections fail. To restore files from UNC Paths data selections, use the Find Files feature or select the individual data selections in the Restore Files dialog.

AIX 5.3 agent upgrade failures from PureDisk 6.2 to 6.5

An agent upgrade of PureDisk from level 6.2 (plus any EEBs) or level 6.2.1 (plus any EEBs) to 6.5 does not complete if the AIX agent is running at patch level 5300-5. This problem does not occur on earlier AIX patch levels. If you are upgrading from any level of 6.2, you must upgrade to 6.5 before upgrading to 6.6. The workaround for this problem is to perform the upgrade directly from the client computer. See the PureDisk Client Installation Guide.

Upgrading failures for some Linux or Solaris agents

If you install a Linux or Solaris agent in a location other than the default location and provide a path name that contains spaces, the agent upgrade job fails for the following upgrades:

From PureDisk 6.2 + EEBs to 6.5 From PureDisk 6.2.1 + EEBs to 6.5

If you are upgrading from any level of 6.2, you must upgrade to 6.5 before upgrading to 6.6. The workaround for this problem is to perform the upgrade directly from the client computer.

104

Known problems and product limitations About known problems

See the PureDisk Client Installation Guide.

Cannot install regular backup and restore agent on a Windows media server after you remove a PDDO agent

After you remove a PDDO agent from a Windows media server, you may not be able to install a regular PureDisk backup and restore agent on that same media server. The PDDO agent removal scripts can, under certain circumstances, fail to delete product files. This incomplete removal can cause the install script to present the Install PureDisk Deduplication Option check box as selected and not available. To remedy the problem, cancel the installation and install the PureDisk agent. See "Installing a PureDisk Agent after removing the PDDO agent." on page 104.

Installing a PureDisk Agent after removing the PDDO agent.

The installation procedure for the PureDisk agent is different after you remove the PDDO agent. To install a backup and restore agent after you remove a PDDO agent

1 2 3

Cancel the installation of the regular backup and restore agent. Reboot the Windows media server. Examine the content of the NetBackup OST plug-in directory, which is \install_path\bin\ost-plugins. For install_path, specify the NetBackup product files directory.

4

(Conditional) Remove file libstspipd.dll. Perform this step if file libstspipd.dll resides in the product files directory.

5

Restart the PureDisk agent install program.

Update client routing tables manually after interrupted content router rerouting job

If a client is disconnected from a storage pool for a long time during a content router rerouting job, the consequences are as follows:

The routing tables on the clients are not updated. Restores to the clients can fail.

Consider the following series of events:

Known problems and product limitations About known problems

105

Your storage pool contains a storage pool authority, one content router, and some clients. The storage pool contains some backup data. You add a new content router to this storage pool and initiate a content router rerouting job. The storage pool loses its connection to one or more clients before the rerouting job completes. If the connection is lost for a long time, the rerouting job cannot update the client-side routing tables. After these clients reconnect, backups from these clients are successful. However, restores to this client fail because the client routing tables are not updated.

To resolve this problem, use one of the following methods to update the client routing tables manually:

Restart the PureDisk agent on the client For information about how to stop and restart the PureDisk agent on a client, see the PureDisk Client Installation Guide. From the Web UI, push the routing tables

Select Setting > Topology. In the left pane, select the storage pool. In the right pane, click Push Routing Tables.

System policy for a Maintenance job hangs when PDDO is enabled

The default settings for the System policy for Maintenance cause the maintenance job to hang in the presence of a PDDO agent. To work around this problem, perform one of the following procedures. To let the job time out on its own:

Ignore the job and let PureDisk's internal watchdog terminate the job.

To terminate the job manually:

1 2 3

Select Monitor > Jobs tab. In the right pane, select the Maintenance job. Click Stop gracefully or Stop immediately.

To edit the System policy for Maintenance:

1 2

Select Manage > Policies. In the left pane, under Storage Pool Management Policies, expand Maintenance and click System policy for Maintenance.

106

Known problems and product limitations About PureDisk limitations

3 4 5 6

Select the System policy for Maintenance. Click the Parameters tab. Clear the Delete old tmp Files check box. Click Save. If you choose to edit the System policy for Maintenance, remember to re-edit this policy periodically and check the Delete old tmp Files check box. When this box is checked, the maintenance policy cleans up the temporary files that accumulate on all systems:

About PureDisk limitations

The following topics describe PureDisk limitations.

Limitations for PureDisk 6.6 with NFS

NFS is supported in a PureDisk environment with the following limitations and requirements:

NFS is allowed only on NetApp filers. PureDisk supports only NFS version 3. NFS can only be mounted for the content router data (/Storage/data) with the following synchronization options:

mount -t nfs -o rw, sync, server_name mount_point rw, bg, hard, rsize=32768, wsize=32768, vers=3, proto=tcp

NFS is not supported for high availability. Disaster recovery is not supported for NFS partitions.

File name and path limitations

PureDisk supports file names 256 characters long and path names 32,768 characters long.

Data selections limited to 16 million files

When you create a data selection, you cannot include more than 16 million files. If a data selection contains more than 16 million files, PureDisk generates a critical warning event and stops the backup. Symantec recommends that you limit the number of files in a data selection to 8 million.

Known problems and product limitations About PureDisk limitations

107

These recommendations refer to the number of files that are online in the file system that you want to back up. It also includes the number of file versions that you want to retain on storage. More information about data selection limits is available. See "Number of backup jobs per client" on page 42.

Unsupported VMFS volumes

PureDisk cannot back up VMFS volumes from the VMware ESX Server management console.

Data lock password blocks exports to NetBackup

If a data lock password is enabled on a client, that client cannot export data to NetBackup. The data lock prevents an administrator or a service provider from accessing the data in the storage pool. The administrator on the client system can remove the data lock password if it is necessary to export that client's data to NetBackup.

File size limitation

PureDisk supports a theoretical maximum file size of four petabytes.

Replicated PureDisk SPAR data cannot be exported to NetBackup

You can export replicated Files and Folders data selections from a source storage pool to a target storage pool. PureDisk does not export other data selection types to NetBackup. SPAR backups use Files and Folders data selections, but PureDisk does not export SPAR backups to NetBackup.

Metabase engine limitations

The metabase engine has the following limitations:

In a one-node, all-in-one storage pool, the metabase engine can hold a maximum of 100 million records. One record corresponds to one file version. In a multinode storage pool with a metabase engine installed alone on one of the individual nodes, the metabase engine can hold a maximum of 140 million records. One record corresponds to one file version.

108

Known problems and product limitations About PureDisk limitations

I18N limitations

The following are the known I18N limitations:

Non-UTF8 encoding display errors

If a Linux or UNIX client's file system is not configured with UTF8 encoding or C-locale encoding, PureDisk still provides complete backup and restore support. However, for these unsupported locales, the PureDisk Web UI displays the names of files and directories that are backed up from this client as byte sequences. If you restore files or directories to the original client, the problem affects only the Web UI. It does not affect how PureDisk restores these files and directories.

Installation of PureDisk client in a localized MacOS, UNIX, or Windows directory results in a non-functioning client

You can install a PureDisk client into a localized directory, but the client does not function properly.

Localized user passwords and data lock passwords are not supported

You cannot specify localized user passwords or data lock passwords. See the PureDisk Client Installation Guide.

Exchange granular restore limitations for I18N mailboxes and folders

MS Exchange granular restore is not supported if the MS Exchange 2003 storage group, database name, or mailbox is in wide characters. If the containing folder is in ASCII or high ASCII, MS Exchange granular restore browsing and restore work. If the containing folder is in ASCII but contains contents that are in wide character, PureDisk can restore the containing folder and all its wide character contents. You will not, however, be able to browse the folders inside the ASCII folder that are in wide characters.

Appendix

A

Third-party legal notices

This appendix includes the following topics:

Third-party legal notices for Symantec NetBackup PureDisk

Third-party legal notices for Symantec NetBackup PureDisk

Active Directory, Excel, 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. 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.

110

Third-party legal notices Third-party legal notices for Symantec NetBackup PureDisk

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. 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 and the VMware "boxes" logo and design are trademarks or registered trademark of VMware, Inc., in the United States and other countries. 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 the Third Party Legal Notices document, which is accessible from the PureDisk Web UI.

Index

A

all-in-one node configuration example 28 application agent requirements 59­60

content router capacity planning 44 role 17 content router node requirements 38

B

browsers requirements 60 supported 60

D

data repository. See storage pool data selection 15 documentation updates 13

C

capacity planning clusters 55 content router 44 metabase engine 43 number of clients 41 service databases 46 storage pool 41 clients backup and restore client platforms 58 capacity planning 41 PDDO client platforms 59 requirements 58 clustering configuration examples 52 planning 55 PureDisk software requirements 50 requirements 47 terminology 53 VCS software requirements 49 configuration overview 18 unsupported capabilities 55 configuration examples all-in-one node 28 cluster configurations 52 four-node 29 three-node 29 two-node 29 connectivity 73

E

enabling on Windows clients 83 examples cluster configurations 52 storage pool configuration 28

F

fingerprint overview 15 four-node configuration example 29

H

hardware compatibility clients 58 PDOS 31 hardware requirements clients 58 content router node 38 general 33 metabase engine node 39 power supply (UPS) 34 processors 33 removable media 33 high availability. See clustering

I

installation requirements 58

J

Java administration console requirements 48

112

Index

L

license key requirements 64 Linux hardware compatibility 31

M

metabase engine capacity planning 43 requirements 39 role 17 metabase server role 16 metadata overview 15

N

NetBackup export engine overview 17 network card (NIC) requirements 33 nodes configuration examples 29 overview 18

requirements (continued) browsers 60 clients 58 clustering 47, 50 content router node 38 hardware 33 installation 58 Java administration console 48 license key 64 metabase engine 39 Storage Foundation 61 storage pool 48 VCS 49

S

server installation requirements 27 service database capacity planning 46 single instance store overview 15 snapshotting on Windows 2000 clients 84 on Windows 2003/XP clients 83 Storage Foundation requirements 61 storage pool capacity planning 41 major services 16 overview 16 requirements 48 storage pool authority 16 SUSE Linux hardware compatibility 31

O

overview configuration 18 data selection 15 fingerprint 15 metadata 15 product components 16 services 16 single instance store 15 storage pool 16

P

PDDO client platforms 59 PDOS hardware compatibility 31 personal firewalls on clients 73 ports 73 power supply (UPS) requirements 34 processor requirements 33 product components overview 16

T

three-node configuration example 29 two-node configuration example 29

U

uninterruptible power supply (UPS) requirements 34 unsupported configurations 55 updates to documentation 13

V

VCS requirements 49 VSP on Windows clients 84 VSS on Windows clients 83

R

RAID configuration 35 removable media requirements 33 repository. See storage pool requirements application agents 59­60

Index

113

W

Web browsers supported 60 Windows clients enabling VSP 84 enabling VSS 83

Information

Symantec NetBackup PureDiskTM Getting Started Guide: Windows, Linux, and UNIX

113 pages

Find more like this

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

830686


You might also be interested in

BETA
DeskView.book
Richardson International Cultivates Modern Data Management & Virtual Server Protection With Commvault Simpana Software
Symantec NetBackup PureDiskTM Best Practices Guide: Windows, Linux, and UNIX
Resume for Michael Bowman