puredisk admin

Symantec NetBackupPureDisk™ Administrator'sGuide

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 usedonly in accordance with the terms of the agreement.

Documentation version: 6.6.0.2, revision 1

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and PureDisk are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec 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 OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas 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 inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, 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 Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-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 Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ 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 registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


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 resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 External directory service authentication . . . . . . . . . . . . . . . . . . . . . . 17

About external directory service authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Assumptions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18User accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Obtaining directory service information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Example Active Directory service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Example OpenLDAP directory service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

(Optional) Adding PureDisk groups to your directory service ... . . . . . . . . . . . . . 28(Optional) Verify TLS and copy the CA certificate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Verifying the server name .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Writing the certificate to the storage pool authority ... . . . . . . . . . . . . . . . . . . 30

Linking PureDisk to the external directory service ... . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configuring communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Managing user groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Enabling the PureDisk system policy that synchronizes PureDiskwith an external directory service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Completing the General tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Completing the Scheduling tab .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

About maintaining synchronization between PureDisk and an externaldirectory service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Adding, changing, or deleting users or groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Changing the youruserclass, yourloginattrib, or yournameattrib

variables in your directory service’s ldap.xml file ... . . . . . . . . . . . . . . . . . . . . . . 44Changing the yourdescriptionattrib variable or the yourmailattrib

variable in your directory service’s ldap.xml file ... . . . . . . . . . . . . . . . . . . . . . . . 44Disabling external authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Changing the TLS specification .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Modifying the base search path .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 2 Single-port communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

About single port communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Configuring single-port communication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring your domain name server (DNS) and firewall .. . . . . . . . . . . . . 51

Contents

Adding FQDNs to each service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Creating a new department with single-port settings ... . . . . . . . . . . . . . . . . . 53Specifying port number 443 as the default port in the

configuration file template ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56(Conditional) Configuring port 443 in replication policies ... . . . . . . . . . . . 57Installing agent software on the clients or moving clients ... . . . . . . . . . . . 58

Chapter 3 Data replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

About data replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59About data replication and PureDisk release levels ... . . . . . . . . . . . . . . . . . . . . . . . . . . 60About data replication policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Creating or editing a data replication policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Completing the General tab for a Replication policy ... . . . . . . . . . . . . . . . . . . . 63Completing the Data Selections tab for a Replication policy ... . . . . . . . . 64Completing the Scheduling tab for a Replication policy ... . . . . . . . . . . . . . . 66Completing the Parameters tab for a Replication policy ... . . . . . . . . . . . . . . 66

Replication jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Copying and deleting a replication policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Managing replicated data selections .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Viewing replicated data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Working with replicated agents and data selections .... . . . . . . . . . . . . . . . . . . 69Copying replicated data to clients on the destination storage

pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Restoring replicated data back to clients on the source storage

pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Restoring replicated Oracle data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Tuning replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 4 Exporting data to NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

About exporting data to NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Export limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Requirements for exporting data to NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . 74Requirements for restoring data from NetBackup .... . . . . . . . . . . . . . . . . . . . . 75Enabling and using the NetBackup export engine .... . . . . . . . . . . . . . . . . . . . . . 75

Configuring PureDisk and NetBackup for export capability ... . . . . . . . . . . . . . . . 75Configuring NetBackup to receive data exported from PureDisk

.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configuring PureDisk to export data to NetBackup .... . . . . . . . . . . . . . . . . . . . 84

Creating or editing an export to NetBackup policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Completing the General tab for an Export to NetBackup

policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Contents8

Completing the Data Selections tab for an Export to NetBackuppolicy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Completing the Scheduling tab for an Export to NetBackuppolicy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Completing the Parameters tab for an Export to NetBackuppolicy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

(Optional) Completing the Metadata tab for an Export toNetBackup policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Running an export to NetBackup policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Performing a point-in-time export to NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Troubleshooting export job failures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

NetBackup export engine log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Problems with inactive server agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Copying or deleting an export to NetBackup policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . 94Restoring from NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Restoring to a PureDisk client that is not a NetBackup client ... . . . . . . . . . . . . . 96Restoring to a PureDisk client that is also a NetBackup client ... . . . . . . . . . . . . 97

Chapter 5 Disaster recovery backup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

About disaster recovery backup procedures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99About performing disaster recovery backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About backing up your PureDisk environment using NetBackup .... . . . . . 101

Prerequisites for NetBackup disaster recovery backups .... . . . . . . . . . . . 102Configuring the NetBackup client software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Enabling NetBackup for PureDisk backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104About NetBackup policy names .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring PureDisk disaster recovery backup policies ... . . . . . . . . . . . . . . . . . 106Completing the General tab for a disaster recovery backup

policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Completing the Scheduling tab for a disaster recovery backup

policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Completing the Parameters tab for a disaster recovery backup

policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109About backing up your PureDisk environment using scripts ... . . . . . . . . . . . . 114

Prerequisites for script-based disaster recovery backups .... . . . . . . . . . 114PureDisk’s disaster recovery backup or restore script

examples ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Creating a backup script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Troubleshooting a disaster recovery backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Missing pdkeyutil file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Content router modes set incorrectly ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

9Contents

Chapter 6 Disaster recovery for unclustered storagepools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About restoring an unclustered PureDisk environment .... . . . . . . . . . . . . . . . . . 121When to restore your environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Restore overview for an unclustered storage pool ... . . . . . . . . . . . . . . . . . . . . 122

Reinstalling required software (unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . 123Reinstalling PDOS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124(Conditional) Reconfiguring the storage partitions on DAS/SAN

disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125(Conditional) Reconfiguring the storage partitions on iSCSI

disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Completing the software reinstallation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Performing a disaster recovery of an unclustered PureDisk storagepool from a NetBackup disaster recovery backup (NetBackup,unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133(Conditional) Cleaning up after a failed full disaster recovery

backup (NetBackup, unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . 134Using the DR_Restore_all script (NetBackup, unclustered

recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Performing a disaster recovery from a Samba backup (Samba,

unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138(Conditional) Recreate your topology information (Samba,

unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138(Conditional) Removing corrupted files from an incomplete

backup (Samba, unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140(Conditional) Preparing the storage pool authority node for

disaster recovery (Samba, unclustered recovery) ... . . . . . . . . . . . . . . . 141Using the DR_Restore_all script (Samba, unclustered

recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Performing a disaster recovery from a third-party product backup

(third-party, unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147(Conditional) Recreate your topology information (third-party,

unclustered recovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147(Conditional) Removing corrupted files from an incomplete full

disaster recovery backup (third-party, unclusteredrecovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

(Conditional) Preparing the storage pool authority node fordisaster recovery (third-party, unclustered recovery) ... . . . . . . . . . 150

Using the DR_Restore_all script (third-party, unclusteredrecovery) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Contents10

Chapter 7 Disaster recovery for clustered storage pools . . . . . . . . . . . . . 157

About restoring a clustered PureDisk environment .... . . . . . . . . . . . . . . . . . . . . . . . 157Recovering from a single-node failover ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Recovering one active node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Reinstalling the PDOS software and the VCS software .... . . . . . . . . . . . . . 160Recreating disks and volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Running the DR_Restore_all script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Recovering from a data storage corruption .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Recreate the storage partitions that failed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Recreating disks and volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Running the DR_Restore_all script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Recovering from a complete storage pool disaster (clustered, completestorage pool disaster) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Reinstalling PDOS and disabling the service groups .... . . . . . . . . . . . . . . . . 169Recreating disks and volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Running the DR_Restore_all script ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

(Conditional) Cleaning up after a failed full disaster recoverybackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Cleaning up after a failed full NetBackup disaster recovery backup

(clustered, complete storage pool disaster) ... . . . . . . . . . . . . . . . . . . . . . . . 172Cleaning up after a failed full Samba disaster recovery backup

(clustered, complete storage pool disaster) ... . . . . . . . . . . . . . . . . . . . . . . . 173Cleaning up after a failed full third-party product disaster

recovery backup (clustered, complete storage pooldisaster) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

(Conditional) Recreate your topology information .... . . . . . . . . . . . . . . . . . . . . . . . . 174(Conditional) Recreating the topology with current topology

information (Samba or third-party, clustered recovery) ... . . . . . . 174(Conditional) Recreating the topology without current topology

information (Samba or third-party, clustered recovery) ... . . . . . . 174Running the DR_Restore_all_script to recover the data ... . . . . . . . . . . . . . . . . . . 175

Recovering a PureDisk clustered storage pool from a NetBackupdisaster recovery backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Recovering a PureDisk clustered storage pool from a Sambadisaster recovery backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Recovering a PureDisk clustered storage pool from a third-partyproduct disaster recovery backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Chapter 8 Storage pool authority replication (SPAR) . . . . . . . . . . . . . . . . . . . 199

About storage pool authority replication (SPAR) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Disaster recovery strategies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Activating the local storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

11Contents

Enabling SPAR backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Completing the General tab for a SPA Replication .... . . . . . . . . . . . . . . . . . . 205Completing the Scheduling tab for a SPA Replication policy ... . . . . . . 206Completing the Parameters tab for a SPA Replication

policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Running a SPAR policy manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Restoring from a SPAR backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

About the RestoreSPASIO command .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Upgrading PureDisk with SPAR enabled .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Chapter 9 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

About reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Permissions and guidelines for running and viewing reports ... . . . . . . . . . . . 214Reports for a running job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Examining a running job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Restarting a backup job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

About policies and workflows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Types of workflows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Workflows in policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Obtaining detailed job reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218General tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Details tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Statistics tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Files tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Errors tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Job log tab for a Job Details report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

About Data mining reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Enabling a data mining policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Completing the General tab for a data mining policy ... . . . . . . . . . . . . . . . . 234Completing the Scheduling tab for a data mining policy ... . . . . . . . . . . . . 235Completing the Parameters tab for a data mining policy ... . . . . . . . . . . . 235

Running a data mining policy manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Obtaining data mining policy output - the data mining report ... . . . . . . . . . . 236

Interpreting the storage pool data reduction factor ... . . . . . . . . . . . . . . . . . . 238Effect of compression on data reduction .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Effects of segmentation on data reduction .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Obtaining data mining policy output - the Web service report ... . . . . . . . . . . 239Web service reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Job status Web service reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Dashboard Web service reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Importing report output into a spreadsheet ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

About Dashboard reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Contents12

Displaying the Capacity dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Displaying the Activity dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Displaying the Server agent dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Displaying the Client agent dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Central storage pool authority reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Displaying the Central Reporting dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . 254Updating the Central Reporting dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Chapter 10 Log files and auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

About the log file directory .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Content router log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Metabase engine log file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Workflow engine log file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Server agent log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270About international characters in log files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Audit trail reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Setting debugging mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Enabling debugging mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Disabling debugging mode .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Removing temporary debugging files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Chapter 11 Storage pool management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

About storage pool management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280About adding services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Adding a service to a node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Adding a new service on an existing node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Adding a new node and at least one new service on the new

node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Verifying and specifying content router capacity ... . . . . . . . . . . . . . . . . . . . . 285Adding a new passive node to a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Activating a new service in the storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Rerouting a content router and managing content routers ... . . . . . . . . . . . . . . 288

Planning for a new content router ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Permissions for rerouting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Disaster recovery backups and rerouting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Data replication policies and rerouting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Activating and deactivating content routers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Alleviating content router congestion .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Parallel and serial rerouting examples ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Rerouting the content routers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Troubleshooting a content router rerouting job .... . . . . . . . . . . . . . . . . . . . . . . 295

Deactivating a service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

13Contents

Preparing to deactivate a content router ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Deactivating a content router or NetBackup export engine .... . . . . . . . 298

Managing license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299About central reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Enabling a storage pool as a central storage pool ... . . . . . . . . . . . . . . . . . . . . . 301Adding a remote storage pool to a central storage pool ... . . . . . . . . . . . . . 301Disabling central reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Managing storage pools configured in the central storage

pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Rerouting a metabase engine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

(Optional) Gathering metabase engine capacityinformation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Preparing clients for rerouting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Preparing the old metabase engine for rerouting .... . . . . . . . . . . . . . . . . . . . . 307Adding the new metabase engine and recording its address ... . . . . . . . 307Rerouting the agents on the metabase engine .... . . . . . . . . . . . . . . . . . . . . . . . . 308Restarting the agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Verifying a metabase engine rerouting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

About clustered storage pool administration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Changing the PDOS administrator’s password .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Changing the PureDisk internal database and the LDAP administrator

passwords .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Increasing the number of client connections .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Adjusting the clock on a PureDisk node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Adjusting the Web UI time-out interval ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Stopping and starting processes on one PureDisk node

(unclustered) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Stopping all services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Starting all services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Starting all services without rebooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Stopping and starting individual services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Stopping and starting processes on one PureDisk node(clustered) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Stopping and starting processes in a multinode PureDisk storagepool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Restarting the Java run-time environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Chapter 12 Reconfiguring your PureDisk environment . . . . . . . . . . . . . . . . . . 321

About the configuration files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Examining configuration settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Editing the configuration files with the Web UI .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Contents14

Making a copy of a value set ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Navigating to a value in the configuration file copy .... . . . . . . . . . . . . . . . . 323Changing a configuration file value or deleting a configuration

file value .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Assigning the template and, optionally, pushing the configuration

file changes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Editing the configuration files with a text editor ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Updating the agent configuration files on a client ... . . . . . . . . . . . . . . . . . . . . . . . . . 327

Chapter 13 Tuning and optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Tuning backup and restore performance .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Editing an agent configuration file to improve backup and restore

performance .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Editing an agent configuration file to accommodate large

backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Multistreamed (parallel) backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Multistreamed (parallel) restores ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Segmentation options for backup jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Unexpected results ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Tuning replication performance .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Appendix A Installing the clustering software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

About the Veritas Cluster Server (VCS) software installation .... . . . . . . . . . . 341(Conditional) Examining the NICs for the private heartbeats ... . . . . . . . . . . . 343

Examining the NICs in this node for addressing .... . . . . . . . . . . . . . . . . . . . . . 343(Conditional) Removing addressing from the private heartbeat

NICs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Synchronizing passwords .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Generating the authentication key on each node .... . . . . . . . . . . . . . . . . . . . . 347Collect the SSH public keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Distributing the key file ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349(Optional) Verifying the SSH access ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Installing the Veritas Cluster Server (VCS) software .... . . . . . . . . . . . . . . . . . . . . . . 351Installing VCS 4.1 MP3 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Installing VCS 4.1 MP4 and VCS 4.1 MP4RP3 .... . . . . . . . . . . . . . . . . . . . . . . . . . 356

Configuring VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360(Conditional) Using YaST to create the storage partitions ... . . . . . . . . . . . . . . . 365

Starting YaST .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Creating the storage partitions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Appendix B Command Line Interface options for PureDisk . . . . . . . . . . . 369

15Contents

Appendix C Third-party legal notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

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

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Contents16

External directory serviceauthentication

This chapter includes the following topics:

■ About external directory service authentication

■ Obtaining directory service information

■ (Optional) Adding PureDisk groups to your directory service

■ (Optional) Verify TLS and copy the CA certificate

■ Linking PureDisk to the external directory service

■ Enabling the PureDisk system policy that synchronizes PureDisk with anexternal directory service

■ About maintaining synchronization between PureDisk and an external directoryservice

■ Adding, changing, or deleting users or groups

■ Changing the youruserclass, yourloginattrib, or yournameattrib variables inyour directory service’s ldap.xml file

■ Changing the yourdescriptionattrib variable or the yourmailattrib variable inyour directory service’s ldap.xml file

■ Disabling external authentication

■ Changing the TLS specification

■ Modifying the base search path

1Chapter

About external directory service authenticationBy default, PureDisk authenticates users through its internal OpenLDAP directoryservice. If you want to use only PureDisk’s internal OpenLDAP directory servicefor user authentication, you do not need to perform any additional configuration.

Alternatively, you can configure your site’s external OpenLDAP or Active Directoryservice for user authentication. PureDisk requires the following levels:

■ OpenLDAP, version 2.3.27

■ Active Directory, Microsoft Server 2008, Service Pack 1



The following process explains the tasks you need to complete to configure externaldirectory service authentication.

To configure external directory service configuration

1 Obtain directory service information.

See “Obtaining directory service information” on page 19.

2 (Optional) Add PureDisk groups to your directory service.

See “(Optional) Adding PureDisk groups to your directory service” on page 28.

3 (Optional) Verify transport layer security (TLS) and copy the certificateauthority’s certificate.

See “(Optional) Verify TLS and copy the CA certificate” on page 29.

4 Link PureDisk to the external directory service.

See “Linking PureDisk to the external directory service” on page 33.

5 Enable the PureDisk policy that synchronizes PureDisk with the directoryservice.

See “Enabling the PureDisk system policy that synchronizes PureDisk withan external directory service” on page 40.

AssumptionsThe procedures you need to perform to configure external authentication assumethat you are familiar with how your site’s OpenLDAP or Active Directory serviceis organized. The procedures also assume that your site’s directory serviceadministrator can provide you with information about how the directory serviceis configured.

External directory service authenticationAbout external directory service authentication

18

User accountsThe following information pertains to user accounts when external authenticationis enabled:

■ The EditLDAPServerConfiguration screen in the Web UI includes a checkboxlabeled Enable LDAP Authentication. When this box is checked, PureDiskauthenticates through an external directory service. When this box isunchecked, PureDisk authenticates through its internal OpenLDAP directoryservice. You cannot merge these directory services.PureDisk can use either its internal directory service or your external directoryservice, but it cannot use both at the same time. When PureDisk is configuredto authenticate through its internal directory service, only its local useraccounts are valid. However, when PureDisk is configured to use an externaldirectory service, only the accounts from that external directory service arevalid.

■ If the external service is down, you can authenticate from PureDisk’s internalOpenLDAP service. For example, the external directory service may be down.If you try to synchronize the external directory service, the job that runs thesystem policy for syncing external ldap users fails.

■ If you want to add PureDisk users and groups, add them in your directoryservice and import them into PureDisk. When authentication through anexternal directory service is enabled, you cannot create users and groupsdirectly in PureDisk.After you import users and groups from the external directory service, youneed to grant PureDisk permissions to those users and groups.

■ You cannot import a user with the root login property from an externaldirectory service. The root users for both PureDisk and for the externaldirectory service are always present and are always unique. By default, thePureDisk root user’s permissions and privileges are always the same. Theyremain the same regardless of whether authentication is through PureDisk’sinternal directory service or through an external directory service.

Obtaining directory service informationYour site’s directory service administrator can help you gather the informationthat you need to configure PureDisk to perform external user authentication. Thisadministrator can also help you analyze your site’s existing authenticationconfiguration.

The following procedure explains the information that you need to obtain fromyour site’s directory service administrator.

19External directory service authenticationObtaining directory service information

To obtain information about your site’s directory service

1 Obtain general information from your site’s external directory serviceadministrator.

The following table summarizes the information that you need to obtain. Youcan use the right column of the table to make notes about the requirements.

Site-speecific valueItem needed

__________________________________________Directory service host fully qualifieddomain name (FQDN) (preferred), hostname, or IP address.

__________________________________________Port number to the server that hosts thedirectory service

__________________________________________The ldapsearch(1) command and itsparameters that PureDisk needs to obtaina listing.

__________________________________________Copy of the certificate authority file.

__________________________________________The directory service administrator needsto put a copy of this file on the storagepool authority.

__________________________________________Common name of the certificate authorityfile.

2 (Conditional) Obtain TLS information from your site’s external directoryservice administrator.

Perform this step if your site requires TLS.

If your site has an Active Directory service, you need to convert the certificatefile you receive to PEM format. Instructions later in this process explain whenand how to perform the conversion.

3 Examine a listing from your directory service.

Each OpenLDAP or Active Directory service is unique. The directory servicesthemselves, their structures, and their schemas are site-specific and uniqueto their purpose. For this reason, you must examine the object classes andattributes in your directory service and map them to the PureDiskconfiguration information screens.

The following examples show directory service listings:

■ See “Example Active Directory service” on page 21.

External directory service authenticationObtaining directory service information

20

■ See “Example OpenLDAP directory service” on page 24.

4 Save your directory listing.

You need to use this listing later in the configuration process.

5 Proceed to one of the following topics:

■ If you want to add PureDisk user groups to your directory service at thistime, proceed to the following topic:See “(Optional) Adding PureDisk groups to your directory service”on page 28.

■ If TLS is required at your site, proceed to the following topic:See “(Optional) Verify TLS and copy the CA certificate” on page 29.

■ Otherwise, proceed to the following topic:See “Linking PureDisk to the external directory service” on page 33.

Example Active Directory serviceTable 1-1 shows the structure of an example Active Directory service.

Table 1-1 Active Directory service structure

Common namesOrganization unitsDomain controllerDomain controller

dc=com

dc=acme

ou=users

cn=Alice Munro

cn=Bob Cratchit

cn=Claire Clairmont

cn=Dave Bowman

ou=groups

cn=chicago

cn=atlanta

This directory service has two organizational units: users and groups.

You can use the ldapsearch(1) command to obtain a listing of this directoryservice. The command to obtain a listing of users and groups is as follows:


# ldapsearch -H ldap://100.100.100.101:389 -x \

-D "cn=Alice Munro,ou=users,dc=acme,dc=com" -W \

-b dc=acme,dc=com "(objectClass=*)" > /tmp/example.txt

If more directory entries exist in the same directory subtree, a command such asthe preceding example returns information about more than users and groups.The command writes its output to file example.txt. In the example file thatfollows, characters in bold represent definitions from this file that you need laterin the configuration process:

# extended LDIF

#

# LDAPv3

# base <dc=acme,dc=com> with scope subtree # base search path

# filter: (objectClass=*)

# requesting: ALL

#

# Alice Munro, users, acme.com

dn: CN=Alice Munro,OU=users,DC=acme,DC=com

objectClass: top

objectClass: person

objectClass: organizationalPerson

objectClass: user # youruserclass

objectClass: inetOrgPerson

cn: Alice Munro # yournameattrib

sn: Munro

description: Alice's Description # yourdescriptionattrib

givenName: Alice

distinguishedName: CN=Alice Munro,OU=users,DC=acme,DC=com

displayName: Alice

memberOf: CN=chicago,OU=groups,DC=acme,DC=com

uSNChanged: 21751

name: Alice Munro

sAMAccountName: alice.munro # yourloginattrib

userPrincipalName: [email protected]

mail: [email protected] # yourmailattrib

# Bob Cratchit, users, acme.com

dn: CN=Bob Cratchit,OU=users,DC=acme,DC=com

objectClass: top

objectClass: person



22

objectClass: user


cn: Bob Cratchit

sn: Cratchit

description: Bob's Description

givenName: Bob

distinguishedName: CN=Bob Cratchit,OU=users,DC=acme,DC=com

displayName: Bob Cratchit

memberOf: CN=chicago,OU=groups,DC=acme,DC=com

name: Bob Cratchit

sAMAccountName: bob.cratchit


mail: [email protected]

# Claire Clairmont, users, acme.com

dn: CN=Claire Clairmont,OU=users,DC=acme,DC=com

objectClass: top

objectClass: person


objectClass: user


cn: Claire Clairmont

sn: Clairmont

description: Claire's Description

givenName: Claire

distinguishedName: CN=Claire Clairmont,OU=users,DC=acme,DC=com

displayName: Claire Clairmont

memberOf: CN=atlanta,OU=groups,DC=acme,DC=com

name: Claire Clairmont

sAMAccountName: claire.clairmont



# Dave Bowman, users, acme.com

dn: CN=Dave Bowman,OU=users,DC=acme,DC=com

objectClass: top

objectClass: person


objectClass: user


cn: Dave Bowman

sn: Bowman

description: Dave's Description


givenName: Dave

distinguishedName: CN=Dave Bowman,OU=users,DC=acme,DC=com

displayName: Dave Bowman

memberOf: CN=atlanta,OU=groups,DC=acme,DC=com

name: Dave Bowman

sAMAccountName: dave.bowman



# chicago, groups, acme.com

dn: CN=chicago,OU=groups,DC=acme,DC=com

objectClass: top

objectClass: group # yourusergroupclass

sAMAccountName: chicago # yournameattrib

member: CN=Bob Cratchit,OU=users,DC=acme,DC=com # yourmemberattrib

member: CN=Alice Munro,OU=users,DC=acme,DC=com

distinguishedName: CN=chicago,OU=groups,DC=acme,DC=com

name: chicago

sAMAccountName: chicago

# atlanta, groups, acme.com

dn: CN=atlanta,OU=groups,DC=acme,DC=com

objectClass: top

objectClass: group

sAMAccountName: atlanta

member: CN=Dave Bowman,OU=users,DC=acme,DC=com

member: CN=Claire Clairmont,OU=users,DC=acme,DC=com

distinguishedName: CN=atlanta,OU=groups,DC=acme,DC=com

name: atlanta

sAMAccountName: atlanta

# search result

search: 7

result: 0 Success

# numResponses: 7

# numEntries: 6

Example OpenLDAP directory serviceTable 1-2 shows the structure of an example OpenLDAP directory service.


24

Table 1-2 OpenLDAP directory service structure

Common namesOrganizationalunits

Domain controllerDomain controller

dc=com

dc=marlins

ou=commuters

cn=Florence

Leeds

cn=Mary Evans

cn=Diana Goyer

cn=Adam Smith

cn=Eric Meyer

cn=Joe McKinley

ou=groups

cn=bikers

cn=drivers

This directory service has two organizational units: commuters and groups.

You can use the ldapsearch(1) command to obtain a listing of this directoryservice. The command to obtain a listing of the users and groups is as follows:

# ldapsearch -H ldap://100.100.100.100:389/ -x \

-D "cn=Diana Goyer,ou=commuters,dc=marlins,dc=com" -W \

-b "dc=marlins,dc=com" "(objectClass=*)">/tmp/example.txt

This example writes its output to file example.txt. In the example that follows,characters in bold represent the definitions that you need later in the configurationprocess. The external directory service authentication configuration proceduresuse examples from this listing. File example.txt is as follows:

# extended LDIF

#

# LDAPv3

# base <dc=marlins,dc=com> with scope subtree # base search path

# filter: (objectClass=*)


# requesting: ALL

#

# marlins.com

dn: dc=marlins,dc=com

dc: marlins

objectClass: domain

# commuters, marlins.com

dn: ou=commuters,dc=marlins,dc=com

ou: commuters

objectClass: organizationalUnit

# groups, marlins.com

dn: ou=groups,dc=marlins,dc=com

ou: groups

objectClass: organizationalUnit

# Florence Leeds, commuters, marlins.com

dn: cn=Florence Leeds,ou=commuters,dc=marlins,dc=com

mail: [email protected] # yourmailattrib

uid: fleeds # yourloginattrib

objectClass: inetOrgPerson # youruserclass

sn: Leeds

cn: Florence Leeds # yournameattrib

userPassword:: cGFzc3dvcmQ=

# Mary Evans, commuters, marlins.com

dn: cn=Mary Evans,ou=commuters,dc=marlins,dc=com


uid: mevans


sn: Evans

cn: Mary Evans


# Diana Goyer, commuters, marlins.com

dn: cn=Diana Goyer,ou=commuters,dc=marlins,dc=com


uid: dgoyer


sn: Goyer

cn: Diana Goyer


26


# Adam Smith, commuters, marlins.com

dn: cn=Adam Smith,ou=commuters,dc=marlins,dc=com


uid: asmith


sn: Smith

cn: Adam Smith


# Eric Meyer, commuters, marlins.com

dn: cn=Eric Meyer,ou=commuters,dc=marlins,dc=com


uid: emeyer


sn: Meyer

cn: Eric Meyer


# Joe McKinley, commuters, marlins.com

dn: cn=Joe McKinley,ou=commuters,dc=marlins,dc=com


uid: jmckinley


sn: McKinley

cn: Joe McKinley


# bikers, groups, marlins.com

dn: cn=bikers,ou=groups,dc=marlins,dc=com

objectClass: groupOfNames # yourusergroupclass

cn: bikers # yournameattrib

member: cn=Florence Leeds,ou=commuters,dc=marlins,dc=com # yourmemberattrib

member: cn=Mary Evans,ou=commuters,dc=marlins,dc=com

member: cn=Diana Goyer,ou=commuters,dc=marlins,dc=com

# drivers, groups, marlins.com

dn: cn=drivers,ou=groups,dc=marlins,dc=com

objectClass: groupOfNames

cn: drivers

member: cn=Adam Smith,ou=commuters,dc=marlins,dc=com

member: cn=Eric Meyer,ou=commuters,dc=marlins,dc=com


member: cn=Joe McKinley,ou=commuters,dc=marlins,dc=com

# search result

search: 2

result: 0 Success

# numResponses: 12

# numEntries: 11

(Optional) Adding PureDisk groups to your directoryservice

Perform this procedure if you want to create PureDisk user groups at this time.You can perform this procedure either now or after you complete the externaldirectory service authentication configuration. In this procedure, you create usersand groups that are specific to PureDisk operations.

You can configure PureDisk to authenticate some or all of the user groups thatare defined in your directory service. After you add, delete, or change user orgroup information in your directory service, run the PureDisk system policy. Thispolicy synchronizes external directory service users with PureDisk’s internaldirectory service. You can run the synchronization policy at any time after yourinitial configuration. If you configure users and groups specific to PureDisk now,you can see them in the Web UI immediately after you complete the configuration.

To create PureDisk users and groups

1 Edit your directory service and add one or more of the following typicalPureDisk user groups:

■ Administrators. Users with full administrative privileges.

■ Users. Users who can back up and restore data.

■ Reporters. Users who can run reports.

■ Installers. Users who can install PureDisk agents on client systems.

■ Backup operators. Users who can back up files for one storage pool butcannot restore or delete.

The following manual includes information about the different types ofpermissions that you can grant to users and user groups:

See the PureDisk Client Installation Guide.


■ If TLS is required at your site, proceed to the following topic:

External directory service authentication(Optional) Adding PureDisk groups to your directory service

28


■ Otherwise, proceed to the following topic:See “Linking PureDisk to the external directory service” on page 33.

(Optional) Verify TLS and copy the CA certificateYou can use TLS during the user authentication process, but PureDisk does notrequire TLS. If TLS is required, perform the following procedures. The directoryservice needs to authenticate to the storage pool authority. PureDisk does notsupport mutual authentication for situations in which the Active Directory serverand the storage pool authority need to authenticate to each other.

To verify TLS and copy the CA certificate

1 Verify the server name.

See “Verifying the server name” on page 29.

2 Write the certificate to the storage pool authority.

See “Writing the certificate to the storage pool authority” on page 30.

3 Proceed to the following topic:


Verifying the server nameThe following procedure explains how to verify the server name in the TLScertificate. When you use TLS, specify the common name whenever a procedurerequires you to provide the LDAP Server Host Name. Unresolvable commonnames are the most common cause of server certificate errors.

To verify the server name in the certificate

1 Obtain the certificate’s common name from your directory serviceadministrator.

2 Log into the storage pool authority node (unclustered) or storage poolauthority service (clustered) as root.

29External directory service authentication(Optional) Verify TLS and copy the CA certificate

3 Verify the common name by issuing a ping(8) command against thecertificate’s common name.

For example:

# ping mn.north.stars

PING mn.north.stars (100.100.100.101) 56(84) bytes of data.

64 bytes from mn.north.stars (100.100.100.101): icmp_seq=1 ttl=64 time=4.71 ms

64 bytes from mn.north.stars (100.100.100.101): icmp_seq=2 ttl=64 time=0.353 ms

4 (Conditional) Edit the /etc/hosts file.

Perform this step only if the previous step’s ping(8) command wasunsuccessful.

Add a line in the following format to the end of the /etc/hosts file:

ip_addr_of_external_directory_services common_name

For example, if the common name of your directory service certificate ismn.north.stars, the line should look like the following:

100.100.100.101 mn.north.stars

5 Proceed to the following:

See “Writing the certificate to the storage pool authority” on page 30.

Writing the certificate to the storage pool authorityThe following procedure explains how to write the certificate to the storage poolauthority node and verify the server-side authentication.

To write the certificate to the storage pool authority

1 Log into the storage pool authority node (unclustered) or storage poolauthority service (clustered) as root.

2 Copy one of the following certificate files to the appropriate directory on thestorage pool authority:

■ The cacert.pem file from an OpenLDAP server. cacert.pem is the defaultname for this file when it is generated by an OpenLDAP server. This filename can be different at your site.

■ The generated certificate from an Active Directory server.

The appropriate directory for the certificate file is as follows:

External directory service authentication(Optional) Verify TLS and copy the CA certificate

30

■ In an unclustered storage pool, Symantec recommends that you write thecertificate file to the /var/ldap/certstore/ directory, but you can writethis file to any directory.

■ In a clustered storage pool, Symantec recommends that you log into thestorage pool authority and write the certificate file to /Storage/var/keys.When you write the certificate file to /Storage, you ensure that thecertificate moves with the storage pool authority when a failover occurs.

You can use any file transfer program to copy the files.

3 (Conditional) Use the openssl(1) command and the x509(1) utility to convertthe Active Directory certificate to PEM format.

Perform this step only if an Active Directory service generated the certificate.You do not have to perform this step if an OpenLDAP directory servicegenerated the certificate.

The openssl(1) command and the x509(1) utility make the file compatiblewith OpenSSL.

Type the following command:

# /usr/bin/openssl x509 -inform DER -outform PEM -in file.cer -out file.pem

This command’s variables are as follows:

The name of the file that contains the Active Directorycertificate. This file name ends in.cer. Obtain this file fromyour site’s directory service administrator.

file.cer

The name of your certificate in the format that is compatiblewith OpenSSL. This file ends in .pem.

file.pem

4 Use the openssl(1) command and the s_client(1) program to test the portconnections and to verify that the SSL certificate operates correctly.


# /usr/bin/openssl s_client -connect FQDN:port -showcerts -state -CAfile cert_loc

This command’s variables are as follows:

31External directory service authentication(Optional) Verify TLS and copy the CA certificate

The directory service server’s FQDN and the port from whichyou imported the certificate. This variable takes the formatFQDN:port . Specify the following values:

■ For FQDN, specify the FQDN of the directory service server.

■ For port, specify the port that the directory service serveruses for incoming communication. By default, the value is636.

For example blink.acme.com:636.

FQDN: port

Specify the absolute path to the certificate file. This file is theone that you copied in step step 2.

For example: /var/ldap/certstore/mycertfile.pem.

cert_loc

External directory service authentication(Optional) Verify TLS and copy the CA certificate

32

5 Use the ldapsearch(1) command to test the connection between the storagepool authority and the directory service server.

The connection needs to be open to allow continued authentication activities.Type the command as follows:

This command has the following format:

# /usr/bin/ldapsearch -H ldaps://ds_serv:port -x -D "uid" -W -b base "(filter)"

For example:

# /usr/bin/ldapsearch -H ldaps://100.100.100.101:636 -x \

-D "cn=Alice Munro,ou=users,dc=acme,dc=com" -W \

-b ou=groups,dc=acme,dc=com "(objectClass=group)"

The command’s variables are as follows:

The FQDN, host name, or IP address of the directory serviceserver. Symantec recommends that you specify an FQDN.

ds_serv

The port the PureDisk uses for TLS communication. Thisport is the one where the external OpenLDAP server runsldaps. By default, the value is 636.

port

The distinguished name of the test user with which to bind.uid

The base search path.base

An object class name. The command searches for this objectclass name as a test.

filter

If the connection is open, it displays a listing of directory service serverinformation. If the command fails or generates messages, fix the connectivityproblems before you proceed.



Linking PureDisk to the external directory serviceUse the following procedures to link PureDisk and your external Active Directoryor OpenLDAP directory service.

33External directory service authenticationLinking PureDisk to the external directory service

To link PureDisk to the external directory service

1 Configure communication in the PureDisk Web UI.

See “Configuring communication” on page 34.

2 Manage user groups.

See “Managing user groups” on page 39.

Configuring communicationThe following procedure explains how to configure communication in the PureDiskWeb UI.

To configure communication in the PureDisk Web UI

1 Display the storage pool authority opening screen.

Open a browser window and type the following URL:

https://URL

For URL, specify the URL to the storage pool authority. For example, in anall-in-one environment, this value is the URL of the PureDisk node uponwhich you installed all the PureDisk software. For example,https://acme.mnbe.com.

2 Type your user name and password at the prompts on the login screen.

3 Click Settings > Configuration.

4 In the left pane, click the plus (+) sign to the left of LDAP server.

5 Select External LDAP.

The LDAP Server Configuration properties appear in the right pane.

6 Complete the Connection tab.

See “Completing the Connection tab” on page 34.

7 Complete the Mapping tab.

See “Completing the Mapping tab” on page 37.

8 Enable user group management.


Completing the Connection tabThe following procedure explains how to complete the fields on the Connectiontab.

External directory service authenticationLinking PureDisk to the external directory service

34

To complete the Connection tab

1 (Optional) Check the Enable LDAP Authentication box.

Perform this step if you want to enable an external OpenLDAP service or anexternal Active Directory service. A check in this box determines whetherPureDisk uses the default PureDisk OpenLDAP directory service or whetherPureDisk uses an external directory service, as follows:

■ If you want to enable PureDisk's internal OpenLDAP directory service,clear this box. By default, this box is clear.For example, if the external directory service goes down, clear this box.When this box is clear, PureDisk uses its internal authenticationmechanism, and users can continue to use PureDisk while the externaldirectory service is down.

■ If you want to enable an external OpenLDAP service or an external ActiveDirectory service, check this box.

2 Specify the LDAP Server Host Name.

The content of this field differs depending on whether or not you enabledtransport layer security (TLS), as follows:

■ When TLS is enable, specify the FQDN of the external OpenLDAP server.Note that this FQDN must match the common name that you specifiedwhen you created the certificate of your external OpenLDAP server. Ifyou do not have this information yet, obtain this name from your directoryservice administrator.

■ When TLS is not enabled, specify the FQDN or IP address of the serverupon which your external OpenLDAP or Active Directory service resides.If you want to enable single port communication between the nodes andclients in your PureDisk environment, Symantec recommends that youuse an FQDN for this field. For example: blinkie.acme.com.

3 Verify, and respecify if needed, the Port number that connects PureDisk tothe external OpenLDAP or Active Directory service.

The port to specify depends on whether TLS is enabled, as follows:

■ When TLS is enabled, the default security port is 636.

■ When TLS is not enabled, the default port is 389.

4 Check or clear the Enable TLS for LDAP Communication box.

A check in this box determines whether TLS is enabled. TLS encrypts datatransactions between your external directory service and PureDisk.


5 (Conditional) Specify the CA Certificate Location.

Perform this step if you checked Enable TLS for LDAP Communication.

Specify the full path to the file that contains the certificate authority thatPureDisk can use to verify the connection to the external directory serviceserver. This is the file you copied over from the external directory serviceserver to the storage pool authority, and typically, this file resides in/var/ldap/certstore/. Specify the location you configured in the followingprocedure:


This file must reside on the storage pool authority in PEM format.

6 Specify the User Distinguished Name.

The distinguished name of an external directory service administratoraccount. This administrator account does not need to have full privileges onthe directory service server. PureDisk requires only the search privilege.Contact your site’s directory service administrator to obtain this value.

7 In the Password field, specify the password for the UserDistinguishedName'saccount.

Contact your site's directory service administrator to obtain this password.

8 In the Service Type pull-down menu, select either Active Directory orOpenLDAP.

9 Specify the external directory service's Base Search Path.

This path specifies a directory in the external directory service beneath whichPureDisk beneath which PureDisk can find the entries that define all usergroups. Type the distinguished name into this field. Specify the highest entrythat is a common ancestor of the groups that you need.

Note that it is in a later procedure that you specify the individual groups thatdefine the users that you want to authenticate as PureDisk users. This laterprocedure is as follows:

See “To manage user groups” on page 40.

For example, assume that you want PureDisk to use the groups from theOpenLDAP marlins.com directory service. To specify all groups, examine theldapsearch(1) command output and complete the following steps:

■ Type the following into the box under the Base Search path label:

dc=marlins,dc=com

■ Click Add.


36

You can specify only one search path.


See “Completing the Mapping tab” on page 37.

Completing the Mapping tabThe following procedure explains how to complete the fields on the Mapping tab.The examples in this procedure refer to the values in examples.txt described inthe following:

See “Example OpenLDAP directory service” on page 24.

To complete the Mapping tab

1 Click the Mapping tab.

2 Gather the directory service listing that you obtained when you completedthe following procedure:

See “Obtaining directory service information” on page 19.

If you have not yet obtained a listing, generate one now. Keep this outputavailable to you. You might need the information in the listing to completethe Mapping tab.

For example, for a small configuration, obtain a copy of the ldapsearch(1)output. For a large configuration, you can use a directory browser such asthe one at the following location:

http://www.anl.gov/techtransfer/Software_Shop/LDAP/LDAP.html

The Symantec Corporation does not endorse, guarantee, or recommend anyparticular LDAP browser.


http://www.anl.gov/techtransfer/Software_Shop/LDAP/LDAP.html

3 Complete the fields under the User attributes heading.

The following table explains how to complete these fields.

Specify the attribute that defines theobject class for users on your externaldirectory service.

Active Directory example: user.

OpenLDAP example: inetOrgPerson.

User object class

Specify the attribute that uniquelyidentifies a user. The user ID for each useris unique.

Active Directory example:sAMAccountName.

OPenLDAP example: uid.

Login attribute

Specify the attribute that defines a user'sreal name. The is the login ID of a user.

Active Directory example: cn.

OpenLDAP example: cn.

Name attribute

(Optional) Specify the attribute for thedescriptive field. Some directory servicesdo not have this attribute.

Active Directory example:description.

OpenLDAP example: description.

Description attribute

(Optional) Specify the attribute thatdescribes the user's email address.

Active Directory example: mail.

OpenLDAP example: mail.

Email address attribute


38

4 Complete the fields under the Group attributes heading.

The following table explains how to complete these fields.

Specify the attribute that defines theobject class for groups on your externaldirectory service.

Active Directory example: group.

OpenLDAP example: groupOfNames.

Group object class

Specify the attribute that defines eachmember in the group.

Active Directory example: member.

OpenLDAP example: member.

Membership attribute

Specify the attribute that defines a usergroup.

Active Directory example:sAMAccountName.

OpenLDAP example: cn.

Name attribute

5 Click Save.

6 (Conditional) On the storage pool authority, edit the /etc/hosts file and adda line that allows the storage pool authority service to resolve the directoryserver using the name of this certificate.

Perform this step if you enabled TLS.

For example, assume that the common name of the certificate file isblinkie.acme.com. Note that this string is not the FQDN of the server uponwhich the directory resides. Add the following entry:

100.100.100.101 blinkie.acme.com



Managing user groupsThe following procedure explains how to manage user groups.


To manage user groups


2 In the left pane, click the plus (+) sign to the left of LDAP Server.


4 In the right pane, click Manage User Groups.

5 Complete the Manage User Groups pane.

In this screen, complete the following steps:

■ In the left-most box, under the Distinguished Name label, type thedistinguished name of a user group into this field. For example:CN=atlanta,OU=groups,DC=acme,DC=com orcn=bikers,ou=groups,dc=marlins,dc=com.

■ Click Add.

■ Repeat the preceding steps to add distinguished names for all the usergroups that PureDisk needs to authenticate.

■ Click Save.If the external directory service is down at the time you click Save,PureDisk generates the following message:

Error: Invalid Search Path


See “Enabling the PureDisk system policy that synchronizes PureDisk withan external directory service” on page 40.

Enabling the PureDisk system policy thatsynchronizes PureDisk with an external directoryservice

PureDisk lets you create several different policies for backups, data removal, andmany other purposes. However, for other tasks you only need one generic policy.PureDisk includes several system policies for these generic tasks. In most cases,you need to enable a system policy before PureDisk can run the policy. Theprocedure in this topic describes how to enable the system policy that cansynchronize the directory services. This synchronization ensures that PureDiskrecognizes the users and the groups that you add to the external directory service.

External directory service authenticationEnabling the PureDisk system policy that synchronizes PureDisk with an external directory service

40

During the synchronization, PureDisk does not synchronize user passwords. Thepasswords reside only in the external directory service files.

The PureDisk Web UI does not accept empty, bank passwords. Make sure that allusers you want to authenticate through an external directory service have anonblank password. A user with a blank password cannot log into the PureDiskWeb UI.

To enable the system policy for synchronization

1 Click Manage > Policies.

2 In the left pane, under MiscellaneousWorkflows, click the plus sign (+) nextto External LDAP server synchronization.

3 Select System policy for Syncing external LDAP users.

4 Complete the General tab.

Note: The General tab and the Scheduling tab include a Save option on eachtab. Do not click Save until you complete the fields on each tab. If you clickSave before you complete each tab, it saves the specifications you made upto that point and closes the dialog box. To complete more fields, open thedialog again in edit mode.

See “Completing the General tab” on page 41.

5 Complete the Scheduling tab.

See “Completing the Scheduling tab” on page 42.

Completing the General tabThis tab specifies the general characteristics for this policy.

To complete the General tab

1 (Optional) Type a new name for this policy in the Name field.

You do not need to rename this policy. The default name is System policyfor Syncing external LDAP users.

2 Select Enabled or Disabled.

This setting lets you control whether or not PureDisk runs the policy accordingto the schedule you specify in the Scheduling tab.

■ If you select Enabled, PureDisk runs the policy according to the schedule.

■ If you select Disabled, PureDisk does not run the policy according to theschedule. Disabled is the default.

41External directory service authenticationEnabling the PureDisk system policy that synchronizes PureDisk with an external directory service

For example, you might want to stop running this policy during a systemmaintenance period. If you select Disabled, you do not need to enterinformation in the Scheduling tab to suspend and then re-enable thispolicy.

3 Specify an escalation action.

PureDisk can notify you if replication does not complete within a specifiedtime. For example, you can configure PureDisk to send an email message toan individual if a replication policy workflow does not complete in an hour.

Select times in the Escalatewarningafter or the Escalateerrorandterminateafter drop-down boxes to specify the elapsed time. If the policy workflowdoes not complete before the warning timeout, PureDisk generates a warningevent. If the policy workflow does not complete before the error timeout,PureDisk generates an error event.

If you select either option, you must create a policy and an event escalationaction. These escalation actions define the email message, define its recipients,and associate the escalation action with the policy.

For information about policy and event escalations, see the following manual:

See the PureDisk Backup Operator’s Guide.


See “Completing the Scheduling tab” on page 42.

Completing the Scheduling tabFrom this tab, use the drop-down lists and check boxes to specify when the policyis to run.

To specify the schedule

1 Accept the system defaults or use the drop-down lists to specify when thepolicy is to run.

2 Click Save.

Aboutmaintaining synchronizationbetweenPureDiskand an external directory service

Over time you can change users or groups in your external directory service. Asusers and groups change, run the system policy that synchronizes the externaldirectory service with PureDisk. For information about this policy, see thefollowing:

External directory service authenticationAbout maintaining synchronization between PureDisk and an external directory service

42

See “Enabling the PureDisk system policy that synchronizes PureDisk with anexternal directory service” on page 40.

The following topics describe other changes you might need to make to yourauthentication configuration:

See “Adding, changing, or deleting users or groups” on page 43.

See “Changing the youruserclass, yourloginattrib, or yournameattrib variablesin your directory service’s ldap.xml file” on page 44.

Adding, changing, or deleting users or groupsIf you need to add, change, or delete users and groups in your external directoryservice, use the procedures that your directory service provides. After you makethe changes, however, ensure that you edit the appropriate group information inthe PureDisk Web UI. Then run the system policy for synchronizing externaldirectory service users.

For example, assume that you remove a user group from an Active Directoryservice and fail to remove that group’s distinguished name. PureDisk can generatemessages such as the following in the job log file for the synchronization job:

Start to load group cn=redfox,cn=users,dc=gerardtest,dc=local from

EXTERNAL LDAP

*** Error Message ***

0

severity: 6

server: 1000000

source: SPA-CLI_Component

description:

[2]ldap_read(): Search: No such object

*** End ***

You can use the same procedure to add or delete user groups. The procedure is asfollows:


43External directory service authenticationAdding, changing, or deleting users or groups

Changing the youruserclass, yourloginattrib, oryournameattrib variables in your directory service’sldap.xml file

If you change the youruserclass, yourloginattrib, or yournameattrib variablesin your directory service, you need to update PureDisk’s /etc/puredisk/ldap.xmlfile.

To change the youruserclass, yourloginattrib, or yournameattrib variables

1 Use your directory service’s methods to change the object class names inyour directory service source files.

2 Log into the storage pool authority node as root.

3 Edit file /etc/puredisk/ldap.xml to reflect the changes that you made toyour directory service.

4 Log into the PureDisk Web UI.


6 Under Miscellaneous Workflows, click the plus sign (+) next to ExternalLDAP server synchronization.

7 Select System policy for Syncing external LDAP users.

8 In the right pane, click Run policy.

Changing the yourdescriptionattrib variable or theyourmailattrib variable in your directory service’sldap.xml file

If you change theyourdescriptionattribvariable or theyourmailattribvariablein your directory service, you need to update PureDisk’s /etc/puredisk/ldap.xmlfile.

To change the yourdescriptionattrib variable or yourmailattrib variable

1 Use your directory service’s methods to change the object class names inyour directory service source files.


3 Edit file /etc/puredisk/ldap.xml to reflect the changes that you made toyour directory service.

External directory service authenticationChanging the youruserclass, yourloginattrib, or yournameattrib variables in your directory service’s ldap.xml file

44

4 Log into the PureDisk Web UI.

5 Click Settings > Configuration tab.

6 In the left pane, expand LDAP Server.


8 In the right pane, click Manage User Groups.

9 Select each group.

10 Click Remove.

11 Click Save.

12 Run the system policy for synchronizing external directory service users.

Complete the following steps:

■ Click Manage > Policies.

■ In the left pane, under Miscellaneous Workflows, click the plus sign (+)next to External LDAP server synchronization.

■ Select System policy for Syncing external LDAP users.

■ In the left pane, click Run policy.

13 Use the procedure in the following topic to add the user groups back:


14 Run the system policy for synchronizing external directory service usersagain.

The instructions for how to run this policy are in step 12.

Disabling external authenticationYou can disable external authentication and enable PureDisk’s internal OpenLDAPauthentication. You might want to change authentication if the external directoryservice is down or unavailable.

Note: If you disable external directory service authentication, PureDisk disablesTLS, too. If you re-enable external directory service authentication, remember tore-enable TLS at that time.

To change the authentication method


2 In the left pane, click the plus (+) sign to the left of LDAP Server.

45External directory service authenticationDisabling external authentication


4 In the right pane, clear the Enable LDAP Authentication box.

When this box is clear, PureDisk uses its internal directory service toauthenticate users.

5 Click Save.



■ Click Manage > Policies.



■ In the right pane, click Run policy.

Changing the TLS specificationYou can enable or disable your site’s TLS specification after its initial configuration.

To change the TLS specification




4 Change the specification, as follows:

■ To enable TLS, check the Enable TLS for LDAP Communication box.

■ To disable TLS, clear the Enable TLS for LDAP Communication box.

5 Click Save.

6 Log in to the storage pool authority as root.

7 Type the following command to restart pdweb:

# /etc/init.d/puredisk restart pdweb

Modifying the base search pathYou can modify the information in the Base Search Path field. You can use thisprocedure if you change the hierarchy in your external directory service.

External directory service authenticationChanging the TLS specification

46

To modify the base search path




4 In the right pane, in the Base Search Path field, change the search path.

5 Click Save.



■ Click Manage > Policies tab.



■ In the right pane, click Run policy.

47External directory service authenticationModifying the base search path

External directory service authenticationModifying the base search path

48

Single-port communication


■ About single port communication

■ Configuring single-port communication

About single port communicationSingle port communication directs all network communication through one TCP/IPport.

By default, network communication between clients and nodes occurs on multipleports. This communication requires multiple open ports between hosts. You mightwant to reconfigure your storage pool to use the single-port communicationfeature, depending on the security requirements at your site.

PureDisk supports multiport environments. However, storage pools that youmodify to use single port communication require fewer firewall ports to be openbetween PureDisk services and PureDisk clients.

You can implement single-port communication at any time, but this feature iseasier to implement right after an initial installation and before you run anybackups. The only prerequisite for this feature is that the storage pool be definedin terms of fully qualified domain names (FQDNs). If your storage pool is definedin terms of host names or IP addresses, perform the procedures for convertinghost names or IP addresses to FQDNs that the following manual describes:

See the PureDisk Administrator’s Guide.

Configuring single-port communicationThe examples in the reconfiguration procedure assume a storage pool with twoPureDisk nodes and two clients.

2Chapter

Table 2-1 shows the example storage pool.

Table 2-1 Example environment

IP addressEntity

IP-out1Client 1

IP-in3Client 2

IP-in4, IP-out2, IP-out3, IP-out4, IP-out5,IP-out6, and so on.

Firewall

IP-in1PureDisk node 1, which hosts the followingservices:

■ Content router 1

■ Controller 1

■ Metabase engine 1

■ Metabase server

■ NetBackup export engine

■ Storage pool authority

IP-in2PureDisk node 2, which hosts the followingservices:

■ Content router 2

■ Controller 2

■ Metabase engine 2

The preceding table uses the following abbreviations:

■ IP-inx is an IP address behind the firewall and in a private range. For example,100.100.100.100 through 100.100.100.024.

■ IP-outx is an IP address outside the firewall somewhere on the internet.

To configure single-port communication

1 Analyze the ports currently used and configure the firewall.

See “Configuring your domain name server (DNS) and firewall” on page 51.

2 Add an FQDN to each PureDisk service.

See “Adding FQDNs to each service” on page 53.

3 Create the department for which you want to use single-port communication.

See “Creating a new department with single-port settings” on page 53.

Single-port communicationConfiguring single-port communication

50

4 Edit the configuration and specify the single-port number.

See “Specifying port number 443 as the default port in the configuration filetemplate” on page 56.

5 (Conditional) Configure the single port in replication policies.

Perform this step if other storage pools replicate data to this storage pool.

See “(Conditional) Configuring port 443 in replication policies” on page 57.

6 Assign clients to the new department that uses single ports.

See “Installing agent software on the clients or moving clients” on page 58.

Configuring your domain name server (DNS) and firewallThe procedure in this topic helps you to analyze and configure your site’s DNSand firewall.

To configure your DNS and firewall

1 On your DNS, configure the ports that the storage pool uses.

Use your firewall software’s documentation to help you determine the inboundports and outbound ports that are in use at this time. Perform the followingtasks:

■ Determine which services are behind the firewall.

■ Make sure that the DNS can resolve the correct IP address regardless ofwhether the client is on the internet or behind the firewall.

The example storage pool uses the following ports:

Client 2 (inside thefirewall)

Client 1 (outside thefirewall)

DNS name (in FQDNformat)

IP-in1IP-out3PureDiskCR1.acme.com

IP-in2IP-out4PureDiskCR2.acme.com

IP-in1IP-out5PureDiskCTRL1.acme.com

IP-in2IP-out6PureDiskCTRL.acme.com2

IP-in1IP-out2PureDiskSPA.acme.com

IP-in1IP-out2PureDiskMBS.acme.com

51Single-port communicationConfiguring single-port communication

IP-in1IP-out7PureDiskDebug.acme.com

2 Configure the firewall to translate the IP addresses and outside ports to insideaddresses and inside ports.

Use your firewall software’s documentation to help you translate the ports.

In the example storage pool, the translations are as follows for the outsideports:

Outside portOutside IP

443IP-out2

443IP-out3

443IP-out4

443IP-out5

443IP-out6

443IP-out7

In the example storage pool, the translations are as follows for the insideports:

Inside portInside IP

443IP-in1

10082IP-in1

10082IP-in2

10101IP-in1

10101IP-in2

10087IP-in1


See “Adding FQDNs to each service” on page 53.


52

Adding FQDNs to each serviceThe following procedure explains how to add an FQDN to each service’sconfiguration information.

To add FQDN information for each service

1 Click Settings > Topology.

2 Expand all the items in the left pane so that PureDisk displays all storagepool services.

3 Select a service and add the FQDN information.

For example, select the first content router that appears and complete thefollowing steps:

■ Type the FQDN for this particular service into the Host Name (FQDN)field.This field accepts a host name, but to enable this feature, specify the FQDNfor this particular service.

■ Click Save.

4 Repeat step 3 for each content router, metabase engine, metabase server,storage pool authority, and NetBackup export engine service on every node.

Do not perform these steps for the metabase engines. For the metabaseengines, PureDisk updates the FQDN information automatically when youupdate the storage pool authority and the controller, respectively.


See “Creating a new department with single-port settings” on page 53.

Creating a new department with single-port settingsThe clients that you want to enable as single-port clients need a customizedconfiguration file and a department that is dedicated to single-port use. Theprocedures in this topic explain how to create a new department and how to applyclient configuration file templates to this new department.

PureDisk ignores any leading or trailing spaces that you specify in a departmentname.

Note: Make sure to add a new department. The single-port feature does not workif you add a new location.

Use the procedures in this topic as follows:


■ To implement the single-port feature for a new installationORTo implement the single-port feature for an existing installation in which theclients you want to enable as single-port clients reside in different departmentsPerform the following tasks:

■ Create a new department.See “(Conditional) Creating a new department” on page 54.

■ Create a new configuration template.See “Creating a new configuration template” on page 55.

■ Assign the new template to the new department.See “Assigning the a new configuration template to a new department”on page 55.

■ To implement the single-port feature in an existing storage pool when theclients to be enabled as single-port clients reside in the same department,perform the following tasks:

■ Create a new configuration template.See “Creating a new configuration template” on page 55.

■ Assign the new template to the new department.See “Assigning the a new configuration template to a new department”on page 55.

(Conditional) Creating a new departmentPerform the procedure in this topic under the following circumstances:

■ To implement the single-port feature for a new installation

■ To implement the single-port feature for an existing installation in which theclients you want to enable as single-port clients reside in different departments

To create a new department


2 In the left pane, expand User management > Departments.

3 Select Departments.

4 In the right pane, click Add Department.

5 In the Department Name field, type in a name for this new department.

For example, assume that you want to name this department for single portuse. You can call this department ATOPDept, which means All Through OnePort Department.


54

6 Click Add.


See “Creating a new configuration template” on page 55.

Creating a new configuration templateThis procedure explains how to create a new configuration template.

To create a new configuration template


2 In the left pane, expand Configuration file templates > PureDisk ClientAgent.

3 Select Default ValueSet for PureDisk Client Agent.

4 In the right pane, click Copy ValueSet.

5 In the left pane, select Copy of Default ValueSet for PureDisk Client Agent.

6 In the right pane, in the ValueSet Name (new) field, type a new name.

For example, ATOP Template.

7 Click Save.


See “Assigning the a new configuration template to a new department”on page 55.

Assigning the a new configuration template to a newdepartmentThis procedure explains how to assign a new configuration template to a newdepartment.

To assign the new configuration template to the new department



3 Select the new template you created in the following procedure:


For example, select ATOP Template.

4 In the right pane, click Assign Template.


5 Click the box to the left of the name of the new department.

For example, click to the left of ATOP Dept.

6 Click Assign.


See “Specifying port number 443 as the default port in the configuration filetemplate” on page 56.

Specifying port number 443 as the default port in the configurationfile template

The following procedure explains the configuration sections that you need to editto specify that PureDisk use single port 443 for client communication. This featuresupports single-port communication only through port 443.

After you specify port 443, you can install the agent software on your clients.When you install the agent software, specify the new department that you createdthat uses the single port. These new clients assume the specifications in the newconfiguration template that you assigned to the new department.

To specify port 443 as the default port



3 Expand the new template that you created in the following procedure:


For example, expand ATOP Template.

4 Expand the following objects:

■ contentrouter > port

■ ctrl > tcport

■ debug > dldport

5 Under the expanded contentrouter > port, select All OS: portnumber.

6 In the Value field, type 443.

7 Click Save.


56

8 Repeat the following steps to change the port value to 443 for the ctrl>tcportfield and the debug > dldport field:

Step 6

Step 7

9 Perform one of the following tasks:

■ (Conditional) Configure port 443 in replication policiesSee “(Conditional) Configuring port 443 in replication policies” on page 57.

■ Install the agent software on the clients or move the clientsSee “Installing agent software on the clients or moving clients” on page 58.

(Conditional) Configuring port 443 in replication policiesYou might have upgraded to PureDisk 6.6 and have replication policies on otherstorage pools. These policies may need to push data through port 443 to thisstorage pool. The following procedure explains how to configure such policies.

For example, assume that you have two storage pools. Their names are Remote

and Central. You have upgraded both storage pools to PureDisk 6.6, and youconfigured Central to use single-port communication. If you replicate data fromRemote to Central, you need to log into Remote and perform the followingprocedure.

To configure replication policies to send data to port 443

1 Log into the storage pool authority Web UI on the storage pool that replicatesdata.

For example, if you replicate data from storage pool Remote to storage poolCentral, log into storage pool Remote.


3 In the left pane, expand the tree to expose the replication policies that senddata to the other storage pool.

4 Complete the following steps to edit a replication policy:

■ Select a replication policy.

■ Click the Parameters tab.

■ Type 443 into the Communication Port field.

■ Click Save.


5 Repeat step 3 for each replication policy.


See “Installing agent software on the clients or moving clients” on page 58.

Installing agent software on the clients or moving clientsPerform one of the following procedures to assign clients to the department thatuses single ports. The procedure to use depends on whether you performed aninitial installation or an upgrade.

Installing agent software for an initial installationPerform the following procedure to enable single-port communication after aninitial installation.

To install the agent software and specify the name of the new department

◆ Use the procedures in the following manual to install the PureDisk agentsoftware on each new client:


When the software prompts you for a department name, specify the name ofthe new department you created that uses the single port.

Moving clients to the new department for an upgradePerform the following procedure to enable single-port communication after anupgrade.

To move clients to the new department

1 Click Manage > Agent.

2 In the left pane, expand the tree to expose the clients that you need to move.

3 Complete the following steps to edit each client and add the new department:

■ Select a client.

■ In the right pane, in the Properties: Agent panel, use the Departmentdrop-down list to select the department you created for single-portcommunication.

■ Click Save.

4 Repeat step 3 for each client that you need to move to the new department.


58

Data replication


■ About data replication

■ About data replication and PureDisk release levels

■ About data replication policies

■ Creating or editing a data replication policy

■ Replication jobs

■ Copying and deleting a replication policy

■ Managing replicated data selections

■ Tuning replication

About data replicationWhen PureDisk runs a data replication policy, it copies the backed up PureDiskdata selections from one storage pool to another storage pool. The data replicationprocess copies file data and file metadata. First, PureDisk takes a snapshot of thedata selection. Next, it copies the data within the snapshot to a different dataselection in a different storage pool.

For example, you can create a policy to replicate backed-up data selections froma small storage pool in a small office's location to a large storage pool in a centrallocation. If you have a work group in a small office that is connected to yourheadquarters over a relatively slow WAN, you can replicate data from that smalloffice to the headquarters location if you have a storage pool in both locations.The PureDisk storage pool in the small office is an all-in-one storage pool; all ofthe PureDisk services are installed on a single node. Your headquarters has other,larger storage pools. For safety and security reasons, a copy of all data must be

3Chapter

available at headquarters at all times. You can create a replication policy to copydata from the remote storage pool to the headquarters storage pool at regularintervals, such as nightly.

The data replication process does not copy system data such as data selectionsor policies that you configured. You can preserve this system data through storagepool authority replication. For more information about storage pool authorityreplication, see the following:

See “About storage pool authority replication (SPAR)” on page 199.

You can run a replication policy at any time. However, if the policy includes anydata selections that PureDisk has not yet backed up, the replication policy doesnot replicate those data selections. A replication policy copies only backed up dataselections.

Additionally, replication jobs and content router rerouting jobs cannot runsimultaneously. If you start a replication job and then start a rerouting job,PureDisk stops the replication job.

Note: If you experience replication job performance degradation and you have ahigh-latency communication network between the two storage pools, you canpossibly improve performance by changing some default TCP/IP settings. Formore information, see "About changing TCP/IP settings to improve replicationjob performance" in thePureDiskBestPracticesGuide, Chapter 5: Tuning PureDisk.

The following contain more information about replication:

■ See “About data replication and PureDisk release levels” on page 60.

■ See “About data replication policies” on page 61.

■ See “Creating or editing a data replication policy” on page 62.

■ See “Replication jobs” on page 68.

■ See “Copying and deleting a replication policy” on page 68.

■ See “Managing replicated data selections” on page 68.

■ See “Tuning replication” on page 71.

About data replication and PureDisk release levelsExamine the release level of each storage pool before you implement replication.To verify the PureDisk version of a storage pool, click About in the Web UI.

The rules for replication and release levels are as follows:

Data replicationAbout data replication and PureDisk release levels

60

■ You can replicate between storage pools if each storage pool is at the samerelease level.

■ You can replicate between storage pools when the destination storage pool isat a release level that is higher than the source storage pool. However,Symantec recommends that you install all your storage pools with the samePureDisk release.For example, Symantec supports replication between a source storage pool atthe PureDisk 6.5.x release level and a destination storage pool at the PureDisk6.6 release level. Symantec does not guarantee data integrity when you replicatebetween storage pools with other nonidentical release levels.

■ You cannot replicate between storage pools when the destination storage poolis at a release level that is lower than the source storage pool.

About data replication policiesTypically, you create data replication policies only after some backups havecompleted. Replication policies apply to a source storage pool. You can specifythe destination storage pool, but you cannot specify the name for the replicateddata selection(s) on the destination storage pool.

For more information about how to create data replication polices, see thefollowing:

See “Creating or editing a data replication policy” on page 62.

When you run a replication policy for the first time, PureDisk creates dataselections on the destination storage pool. You can create and run an additionalreplication policy that includes the data selections from the first policy. If yourun additional policies, PureDisk creates the additional data selections on thedestination storage pool.

For example, assume that a source storage pool runs replication policy AAA. PolicyAAA replicates data selections 111, 222, and 333 to a destination storage pool.PureDisk creates three data selections for the replication. Assume that you latercreate replication policy BBB to replicate data selection 111 again. PureDisk createsan additional data selection for data selection 111.

PureDisk keeps track of the data that has been replicated. Consequently, whenyou run a specific replication policy again, PureDisk forwards only the new datato the destination storage pool. Specifically, the new data is data that was addedto the data selection(s) since the previous policy run.

Any clients that own the source data selections are also replicated to thedestination storage pool. PureDisk displays the replicated clients and data

61Data replicationAbout data replication policies

selections with a special icon when you click Manage > Agent on the destinationstorage pool’s Web UI.

Note: You can delete data from a data selection when you run a removal policy.PureDisk does not remove this data automatically from a replicated data selection.PureDisk does not replicate delete actions. If you want to keep the source and thereplicated data selection identical, define similar removal policies for both dataselections.

After you create and run a policy to replicate data from a source storage pool toa destination storage pool, you can do the following:

■ View the replicated data on the destination storage pool.For more information about how to view replicated data, see the following:See “Replication jobs” on page 68.

■ Use restore functions to copy the replicated data to a client that is attachedto the destination storage pool.For more information about how to copy replicated data, see the following:See “Copying replicated data to clients on the destination storage pool”on page 70.

■ Restore the replicated data back to the original client or another client on thesource storage pool.For more information about how to restore replicated data, see the following:See “Restoring replicated data back to clients on the source storage pool”on page 70.

Creating or editing a data replication policyThe following procedure explains how to create a new data replication policy andhow to edit an existing data replication policy.

To create or edit a replication policy

1 Select Manage > Policies.

2 In the left pane, under Data Management Policies, click Replication.

3 Complete one of the following steps:

■ To create a policy, in the right pane click Create Policy.

■ To edit a policy, expand Replication and click a policy name.


See “Completing the General tab for a Replication policy” on page 63.

Data replicationCreating or editing a data replication policy

62

5 Complete the Data Selections tab.

See “Completing the Data Selections tab for a Replication policy” on page 64.


See “Completing the Scheduling tab for a Replication policy” on page 66.

7 Complete the Parameters tab.

See “Completing the Parameters tab for a Replication policy” on page 66.

8 Click Add.

Completing the General tab for a Replication policyThe following procedure explains how to complete this tab.


1 Type a name for this policy in the Name field.


This setting lets you control whether PureDisk runs the policy according tothe schedule you specify in the Scheduling tab, as in the following situations:

■ If you select Enabled, PureDisk runs the policy according to the schedule.

■ If you select Disabled, PureDisk does not run the policy according to theschedule. Disabled is the default.For example, you might want to stop running this policy during a systemmaintenance period. If you select Disabled, you do not need to enter

63Data replicationCreating or editing a data replication policy

information in the Scheduling tab to suspend and then reenable thispolicy.

3 (Optional) Specify an escalation action.

PureDisk can notify you if replication does not complete within a specifiedtime. For example, you can configure PureDisk to send an email message toan individual if a replication policy workflow does not complete in an hour.

Select times in the Escalatewarningafter or the Escalateerrorandterminateafter drop-down boxes to specify the elapsed time. If the policy workflowdoes not complete before the warning timeout, PureDisk generates a warningevent. If the policy workflow does not complete before the error timeout,PureDisk generates an error event.

If you select either option, you must create a policy and an event escalationaction. These escalation actions define the email message, define its recipients,and associate the escalation action with the policy.

For more information about policy and event escalations, see the following:


Completing the Data Selections tab for a Replication policyThe Data Selections tab displays a tree view. From this view, you can select oneor more data selections to include in the policy.

From this tab, you can also specify filters for PureDisk to apply to the dataselections you choose. You can filter on the data selection name or the description.You also can specify a data selection template as the filter. If you use a filter,PureDisk applies the filter when the policy runs.

To specify data selections

1 Click Data Selection.

2 Select a data selection type from the Data Selection Type drop-down list.


64

3 Expand the tree and select one or more data selections.

To make a selection, click in the box to the left of the label.

To select a number of data selections, select a storage pool or department.This action selects all data selections that exist under the storage pool ordepartment.

A data selection is associated with a client. PureDisk applies the policy to allselected data selections and the associated clients when you save the policy.

If a replication policy includes any data selections that belong to an inactiveclient, PureDisk replicates that inactive client’s data selections.

If you do not select a data selection in the tree, PureDisk uses all dataselections in the storage pool.

4 Decide whether you want to include all the data selections you checked instep 3.

Proceed as follows:

■ If you want to include all the data selections in the box, make sure thatInclude all data selections selected above is selected. Proceed to See“Completing the Scheduling tab for a Replication policy” on page 66.

■ If you want to exclude, or filter out some data selections, select Apply allinclusion rules below to dataselections selected above. Proceed to step5.

5 (Optional) Specify one of the following filter methods:

■ Fill in the Data selection name or Data selection description fields. Usewildcard characters (* and ?) to filter the data selections. You can filteron the data selection name field or on the data selection description field.For example, assume that the following data selection names exist andthat they were selected under a department in the tree:

U_*.jpg_files

W_*.jpg_files

W_*.xls_files

If you type *files in the Data selection name field, the policy backs upall three data selections.If you type W* in the field, the data selections for this policy include onlythe data selections that are named W_*.jpg_files and W_*.xls_files.

For more information on filtering, see the following:See the PureDisk Backup Operator’s Guide.


■ Select a template from the Dataselectionsbasedontemplate drop-downlist to specify an existing data selection template to use. PureDisk usesall data selections that it linked to the template. This action assumes thatthe template was previously applied to the client.

Completing the Scheduling tab for a Replication policyCreate a schedule that lets you save your key data items after any regular companyprocesses have updated the data.

For optimal performance, schedule removal policies for replicated data selectionson the destination storage pool to run at different times as the replication policyon the source storage pool.


1 Click Scheduling.

2 Select hourly, daily, weekly, or monthly to specify how frequently you wantthis policy to run.

3 Select schedule details.

The detail options that PureDisk displays depend on whether you selectedan hourly, daily, weekly, or monthly schedule in the preceding step.

Completing the Parameters tab for a Replication policyThe following procedure explains how to complete the Parameters tab.

To complete the Parameters tab

1 Click Parameters.

2 In the IP of the remote SPA field, type the IP address or the FQDN for thedestination (remote) storage pool.

Symantec recommends that you specify an FQDN.

3 In the Login remote SPA field, type the login ID for the destination (remote)storage pool.

4 In the Password remote SPA field, type the password for the destination(remote) storage pool.


66

5 (Optional) In the Communication Port field, type the open communicationport of the storage pool that is used for replication.

By default, this port is 10082. If you enabled single port communication,specify port number 443.

For more information about single ports, see the following:

See the PureDisk Storage Pool Installation Guide.

6 In the Type of Replication field, select one of the following:

■ Select Normal to include images of any new files or changed files sincethe full replication. Typically, you can select Normal.

■ Select Reverify all to provide a complete copy of all the files that werespecified in the data selection. Select Reverify all if you suspect that aproblem exists on your destination storage pool. For example, contentrouter corruption or a complete storage pool crash.

7 (Optional) Type a bandwidth size to use when files are transferred.

If you leave this field blank, PureDisk by default uses the maximum bandwidthfor the network.

This field lets you specify the maximum network bandwidth to use duringthe backup. For example, if you specify 50 Kbps, the agent uploads data atthat rate to the content routers. This number is an average. The peakbandwidth usage can be higher than the number specified, but the averagebandwidth usage cannot.

8 Check or clear the Force encryption box.

When you check this option, PureDisk encrypts and compresses the data overthe wire during transmission between the source storage pool and thedestination storage pool.

If you want the data to arrive at the destination storage pool in an encryptedstate, specify encryption in the backup policy on the source storage pool.

9 (Optional) In the Define backup window field, select a start time and endtime for the backup window from the drop-downs.

PureDisk queues the job at the time you specify in the Scheduling tab. Otherjobs in the queue might prevent PureDisk from running the job immediately.When you specify a start time and an end time, you ensure that the job doesnot start outside of this period. In addition, PureDisk stops the job if the jobdoes not end before the end time that you specify.

Make sure that the start time you specify falls within this replication window.


10 (Optional) Click Set as defaults.

If you select this option, PureDisk uses these settings for all replication policiesthat you create later.

11 Click Add to save the policy.

Replication jobsPureDisk runs replication jobs on the source storage pool.

PureDisk creates virtual agents on the destination (remote) storage pool whenyou implement replication. PureDisk runs the following types of jobs on virtualagents:

■ Imports of forwarded data during replication

■ Data removal

■ Maintenance

Copying and deleting a replication policyThe following procedure explains how to copy or delete a replication policy.

To copy or delete a replication policy

1 Select Manage > Policies.

2 In the left pane, under Data Management Policies, expand Replication.

To expand Replication, click the plus sign (+) to the left of the Replicationlabel.

3 Select the replication policy that you want to copy or delete.

4 In the right pane, click one of the following:

■ Copy Policy

■ Delete Policy

Managing replicated data selectionsThe following information pertains to managing replicated data selections:

■ See “Viewing replicated data” on page 69.

■ See “Working with replicated agents and data selections” on page 69.

Data replicationReplication jobs

68

■ See “Copying replicated data to clients on the destination storage pool”on page 70.

■ See “Restoring replicated data back to clients on the source storage pool”on page 70.

■ See “Restoring replicated Oracle data” on page 71.

Viewing replicated dataAfter you run a replication policy, the replicated client and its data selectionsappear in the destination (remote) storage pool's Web UI

The destination storage pool displays both information about its own clients andinformation about replicated data from other storage pools. PureDisk differentiatesreplicated client names and replicated data selection names. In the destinationstorage pool’s Web UI, an [R] icon to the left of the client name indicates areplicated data selection. PureDisk uses this icon on the destination storage poolfor replicated clients and replicated client data selections.

The following procedure explains how to view replicated data selections.

To view replicated data

1 Log on to the Web UI of the destination storage pool.


3 In the left pane, select the replicated client.

The icon for a replicated client includes [R] and the name of the client. Whenclick a client name, client information appears in the right pane.

Working with replicated agents and data selectionsThe first time PureDisk replicates a data selection, the replicated data selectionalways appears in the Unknown location and in the Unknown department.

The replicated data selection appears this way regardless of the location anddepartment that hosted the data selection on the source storage pool. You canmove the data selection to a different location and department after this firstreplication.

Never rename the Unknown location or the Unknown department. PureDisklooks for these containers when it replicates data selections. PureDisk puts thefirst of all replicated data selections in these containers.

69Data replicationManaging replicated data selections

Copying replicated data to clients on the destination storage poolThe following procedure explains how to copy replicated data.

To copy replicated data to clients on the destination storage pool





4 Use the PureDisk restore functions to copy the data.

For more information about how to restore data, see the following:


Restoring replicated data back to clients on the source storage poolYou can restore replicated data only to clients that are currently connected to thedestination storage pool.

You can replicate an MS Exchange, MS SQL, Oracle, Oracle UDJ, or System Stateand Services data selection to another storage pool. To restore data, treat theclient to which you want to restore the data as if it were an alternate client. Formore information about alternate client restores of application data, see thePureDisk Backup Operator’s Guide.

The following procedure assumes that the original client system can no longerbe used for some reason or the original data is corrupted.

To restore replicated data back to clients on the source storage pool

1 Install PureDisk on the client where you want to restore data.



This is the storage pool that received the replicated data from the sourcestorage pool.


Data replicationManaging replicated data selections

70



5 In the right pane, select Restore Files.

When you restore a data selection, select the new client of the source storagepool as the destination client.

See the PureDisk Backup Operator's Guide for information about how toperform the restore.

Restoring replicated Oracle dataYou need to perform some additional configuration steps if you want to restoreOracle data that you replicated to another storage pool. For more informationabout these configuration steps, see the PureDisk Backup Operator's Guide.

Tuning replicationPureDisk includes configuration parameters that you can manipulate in order totune replication performance. For information about tuning, see the following:

See “Tuning replication performance” on page 337.

71Data replicationTuning replication

Data replicationTuning replication

72

Exporting data toNetBackup


■ About exporting data to NetBackup

■ Configuring PureDisk and NetBackup for export capability

■ Creating or editing an export to NetBackup policy

■ Running an export to NetBackup policy

■ Performing a point-in-time export to NetBackup

■ Troubleshooting export job failures

■ Copying or deleting an export to NetBackup policy

■ Restoring from NetBackup

■ Restoring to a PureDisk client that is not a NetBackup client

■ Restoring to a PureDisk client that is also a NetBackup client

About exporting data to NetBackupThe NetBackup export engine lets you back up your PureDisk files to NetBackuptape or disk. The export engine lets you export a backed up Files and Folders dataselection from a PureDisk content router to NetBackup. NetBackup then catalogsthe data and writes it to tape or disk in NetBackup’s file format. You can use thesefiles for long-term data protection. If you ever delete the files from the originalclient or from PureDisk storage, you can restore them from NetBackup.

4Chapter

After you export the PureDisk files to NetBackup, you can treat these files as ifthey were native NetBackup files. From the NetBackup administration console,you can generate NetBackup reports, browse the files, and manage the files.

To restore the data that you exported to NetBackup, use the NetBackup proceduresthat are described in the NetBackup administration guides.

The following provide an overview of the NetBackup export engine:

■ See “Export limitations” on page 74.

■ See “Requirements for exporting data to NetBackup” on page 74.

■ See “Requirements for restoring data from NetBackup” on page 75.

■ See “Enabling and using the NetBackup export engine” on page 75.

Export limitationsThe PureDisk NetBackup export engine lets you export backed up PureDisk Filesand Folders data selections to NetBackup. The NetBackup export engine does notexport other PureDisk data selection types.

When you choose data selections for export, a tree structure appears in the WebUI , and you make your selection from the tree. Be aware that PureDisk exportsonly the Files and Folders data selections in the tree. For example, if you select astorage pool that has many types of data selections, PureDisk exports only theFiles and Folders data selections. In addition, if you choose to export replicateddata from a target storage pool, PureDisk exports only the replicated Files andFolders data selections.

Requirements for exporting data to NetBackupThe ability to export Files and Folders data selections from PureDisk to NetBackuprequires the following NetBackup software and licenses:

■ NetBackup 6.0 MP5 or later

■ NetBackup client

■ A NetBackup DataStore license and NetBackup client licenseWhen you export PureDisk data to NetBackup, you use a NetBackup DataStorepolicy. This feature requires that you install a NetBackup DataStore licenseon the NetBackup server. The PureDisk license key includes a NetBackupDataStore license.

Contact your Symantec sales representative to obtain the required software andlicense.

Exporting data to NetBackupAbout exporting data to NetBackup

74

Requirements for restoring data from NetBackupThe exported Files and Folders data selections become NetBackup files after youexport them. You can use NetBackup restore methods to restore the files. Thehost to which you restore the data selections must run NetBackup release 6.0 MP5or later.

When you restore the PureDisk data, you perform the restore from NetBackup,and you restore to NetBackup. If necessary, you can use a network transfer methodto move the data to the correct PureDisk client. If you want to put the files backunder PureDisk control again, use PureDisk to back them up.

Enabling and using the NetBackup export engineThe following explain how to enable and use the NetBackup export engine:

■ See “Configuring PureDisk and NetBackup for export capability” on page 75.

■ See “Creating or editing an export to NetBackup policy” on page 85.

■ See “Running an export to NetBackup policy” on page 91.

■ See “Performing a point-in-time export to NetBackup” on page 91.

■ See “Troubleshooting export job failures” on page 92.

■ See “Copying or deleting an export to NetBackup policy” on page 94.

■ See “Restoring from NetBackup” on page 94.

■ See “Restoring to a PureDisk client that is not a NetBackup client” on page 96.

■ See “Restoring to a PureDisk client that is also a NetBackup client” on page 97.

Configuring PureDisk and NetBackup for exportcapability

To enable the PureDisk export capability, you must configure both of the followingcomponents on the same PureDisk node:

■ The PureDisk NetBackup export engine.To configure this engine, install the PureDisk nbu service on this node. Whenyou install the nbu service, you enable this node to export data from thisPureDisk storage pool to a NetBackup environment. You can install the nbu

service at initial installation time, or you can add it later.

■ The NetBackup client software.These clients are distributed with NetBackup.

75Exporting data to NetBackupConfiguring PureDisk and NetBackup for export capability

You can configure the required software on its own dedicated node, or you canconfigure this software on a node with other PureDisk services.

Figure 4-1 shows the software that you need to configure to enable PureDiskexports to NetBackup.

Exporting data to NetBackupConfiguring PureDisk and NetBackup for export capability

76

Figure 4-1 Example environment for exporting PureDisk data to NetBackup

1

2

3

54

6

7

The figure shows a multinode PureDisk environment attached to a NetBackupenvironment, as follows:


ObjectLabel

PureDisk storage pool1

NetBackup environment2

PureDisk node_1, which hosts the following services:

■ Storage pool authority

■ Metabase server

■ Metabase engine



3

PureDisk node_2, which hosts a content router service4

PureDisk node_3, which hosts the following services:



5

PureDisk client kwiek.6

PureDisk client speedy.7

Both node_1 and node_3 host a PureDisk NetBackup export engine and theNetBackup client software. In this storage pool, node_3 can be a low-end computerbecause it only serves to transfer data. If you had an all-in-one PureDiskenvironment, you would have to install the NetBackup client on that one node.

The figure shows two clients: kwiek and speedy. The NetBackup export engineon node_1 exports data from kwiek. The NetBackup export engine on node_3

exports data from speedy.

To perform a direct restore of files from NetBackup to speedy, install theNetBackup client software on speedy. Configure the PureDisk environment first,and then configure NetBackup.

To configure PureDisk and NetBackup to export PureDisk data selections

◆ Complete the following procedures:

■ See “Configuring NetBackup to receive data exported from PureDisk ”on page 79.

■ See “Configuring PureDisk to export data to NetBackup” on page 84.


78

Configuring NetBackup to receive data exported from PureDiskThe procedure in this topic explains how to configure NetBackup to acceptPureDisk data.

To configure NetBackup for PureDisk export capability

1 Install the NetBackup Linux SUSE 2.6 client on each PureDisk node.

Both the PureDisk NetBackup export engine service and the NetBackup clientneed to be running together on the same PureDisk node or nodes.

When you install a NetBackup Linux client, the following message mightappear:

No [x]inetd process found.

Ignore this message. A later step in this procedure starts the xinetd daemon.

For information about how to install the NetBackup client, see the following:

See the NetBackup Installation Guide for UNIX and Linux.

2 (Conditional) For each PureDisk node, create a file for the host FQDN andanother file for the service FQDN in the altnames directory on the NetBackupmaster server.

Perform this step if the storage pool you want to back up is clustered.

This step is needed because the bp.conf file on each node contains thephysical host address. However, the backup process and the restore processuse the service address.

If necessary, create the altnames directory itself. Within the altnames

directory, use the touch(1) command to create a file for each node's hostFQDN and each node's service FQDN.

Example 1. To create the altnames directory on a UNIX master server, typethe following command:

# mkdir /usr/openv/netbackup/db/altnames

Example 2. Assume that you want to create file names in the altnames

directory of a UNIX NetBackup master server for the nodes in the followingtwo-node cluster:

■ Node 1 = allinone.acme.com (host FQDN) and allinones.acme.com

(service FQDN)

■ Node 2 = passive.acme.com (host FQDN) and passives.acme.com (serviceFQDN)


For the all-in-one node (node 1), type the following commands on the masterserver to create the correct files in the altnames directory:

# touch allinone.acme.com

# touch allinones.acme.com

For the passive node (node 2), type the following command on the masterserver to create the correct files in the altnames directory:

# touch passive.acme.com

# touch passives.acme.com

For more information about the altnames directory and creating files insidethe altnames directory, see the following:

See the NetBackup Administrator’s Guide, Volume I.

3 Determine if NetBackup access control (NBAC) is enabled in your NetBackupenvironment.

One way to tell if NBAC is enabled is to examine the bp.conf file. If theUSE_VXSS = AUTOMATIC or USE_VXSS = REQUIRED appear, then NBAC isenabled.

■ If NBAC is enabled, proceed to step 4.For more information about NBAC, see the NetBackup Security andEncryption Guide.

■ If NBAC is not enabled, proceed to step 6.

4 (Conditional) On the NetBackup master server, configure NBAC for thePureDisk nodes.

Perform this step if NBAC is enabled in your NetBackup environment.

Log into the NetBackup master server and complete the following steps:

■ Change to the directory where the bpnbat command resides.

On UNIX master servers, the bpnbat command resides in/usr/openv/netbackup/bin. On Windows master servers, the bpnbat

command resides in install_path\NetBackup\bin.

■ Type the following command to add the PureDisk node to NBAC:

bpnbat -addmachine


80

The bpnbat command prompts you for the machine name, prompts youto create an NBAC password, and prompts you to confirm the password.For the machine name, type the FQDN of the PureDisk node.

■ Change to the directory where the bpnbaz command resides.

On UNIX master servers, the bpnbaz command resides in/usr/openv/netbackup/bin/admincmd. On Windows master servers, thebpnbaz command resides in install_path\NetBackup\bin\admincmd.

■ Type the following commands to enable the PureDisk node to performaccess checks:

bpnbaz -allowauthorization pd_node_fqdn

Operation completed successfully.

■ Repeat the preceding bulleted steps for each PureDisk node that hosts aNetBackup client.

For example, type the following commands on a UNIX master server:

masterserver# cd /usr/openv/netbackup/bin

masterserver# bpnbat -addmachine

Machine Name: potato.idaho.com

Password: *****

Password: *****


masterserver# cd admincmd

masterserver# bpnbaz -allowauthorization potato.idaho.com


5 (Conditional) On the PureDisk node that hosts the NetBackup client software,install VxAT.

Perform this step if NBAC is enabled in your NetBackup environment.

■ Log into the PureDisk node as root.

■ Type the following commands to create NBAC credentials for the node:

puredisknode# cd /usr/openv/netbackup/bin/admincmd

puredisknode# bpnbat -loginmachine

■ Respond to the bpnbat command's prompts, which are as follows:

■ Does this machine use Dymanic Host Configuration Protocol

(DCHP)? (y/n)?


Type n, and press Enter.

■ Authentication Broker:

Specify the host name of the NetBackup authentication broker, andpress Enter.

■ Authentication port [Enter = default]:

Press Enter to use the default authentication port. If your NetBackupenvironment uses a site-specific authentication port, type that portnumber.

■ Machine name:

Type the FQDN of the PureDisk node, and press Enter.

■ Password:

Type the password you created in step 4, and press Enter.

■ Edit file bp.conf as follows:

■ Add entries for the NetBackup master server and the NetBackup mediaserver.

■ Set the USE_VXSS = and (optionally) the AUTHENTICATION_DOMAIN =

parameters as dictated by your site practices. You can set theseparameters through the NetBackup administrator interface or by usingcommands.

See your NetBackup administrator documentation for more informationabout how to edit the bp.conf file.

■ Repeat the preceding bulleted steps for each node that hosts a NetBackupclient.

For example:

puredisknode# cd /usr/openv/NetBackup/bin

puredisknode# bpnbat -loginmachine

Does this machine use Dynamic Host Configuration Protocol (DCHP)? (y/n)? n

Authentication Broker: colonel.flagg.com

Authentication port [Enter = default]:

Machine Name: potato.idaho.com

Password: *****



82

6 On each PureDisk node that you want to configure, make sure that the xinetddaemon is running.

Enter the following command to determine if xinetd is running:

# ps -aef |grep xinetd

If it is not running, enter the following command:

# /etc/init.d/xinetd start

To ensure that the xinetd daemon starts after you restart the system, typethe following command:

# chkconfig xinetd on

7 From a NetBackup administration console, create a DataStore policy with anApplication Backup Schedule.

A DataStore policy is a specific policy type. An Application Backup Scheduleis the default schedule. For information about how to create this policy, seethe NetBackup System Administrator’s Guide, Volume I.

The following are some guidelines for this policy:

■ When you create this policy, make sure to specify a schedule for 24 hoursa day and 7 days a week. This schedule leaves the policy open and availablefor whenever PureDisk needs to send data.

■ Remember the name of this policy. You need to specify this name whenyou create the PureDisk Export to NetBackup policy.

■ If you enable encryption, NetBackup asks you for a passphrase. NetBackupuses this passphrase for all data that you export from the client toNetBackup.

Ensure that you use the same passphrase for the following:

■ The NetBackup export engine

■ The client upon which the source files reside

■ All clients to which you might want to restore the exported data.

■ If you want to export data to NetBackup from a clustered PureDisk storagepool, specify the nodes upon which the NetBackup export engine serviceresides. In NetBackup, specify the fully qualified domain names (FQDNs)


of the physical host for these nodes. These are the FQDNs of the physicalnodes. Do not specify the service FQDNs.

Configuring PureDisk to export data to NetBackupThe following procedure explains how to configure PureDisk to export dataselections to NetBackup.

To configure a PureDisk environment to export data to NetBackup

1 Make sure that the NetBackup export engine service is included in the storagepool configuration, is installed on the node that you want to designate as theNetBackup export engine, and is activated.

You can specify the nbu as a service on more than one node.

For information about how to add a service, see the following:

■ See “About adding services” on page 280.

■ See “Adding a service to a node” on page 282.

For information about how to activate the NetBackup export engine service,see the following:

See “Troubleshooting export job failures” on page 92.

2 Use the procedure in the PureDisk Client Installation Guide to install andconfigure PureDisk on clients.

You can configure clients with any number of features. However, you cannotenable a data lock password on a client if you want to export that client’s datato NetBackup. If necessary, you can enable the data lock password for thatclient at install time. When the time comes to export data, you need to disablethe password.

Also note that client naming conventions differ between NetBackup andPureDisk. If the names of your PureDisk clients do not conform to NetBackup’sclient naming conventions, PureDisk transforms the client name to acompatible name. PureDisk changes the name internally, and you can see theresult in log files and messages. In addition, you can check the names in thefollowing file:

/Storage/var/NbuExportClientNameChanges.txt

By convention, NetBackup client names can include only the followingcharacters:

■ The uppercase English language alphabetic characters, A through Z

■ The lowercase English language alphabetic characters, a through z


84

■ The digits, 0 through 9

■ A period (.)

■ A hyphen (-)

■ An underscore (_)

Example 1: Assume that you have a PureDisk client named as follows:

my agent name is strider

PureDisk transforms this name to the following:

my_agent_name_is_strider

Example 2: Assume that you have two clients with the following names:

my agent name is strider

my agent_name*is strider

To avoid duplication, PureDisk adds a counter to the end of the second nameit encounters and transforms the names as follows:

my_agent_name_is_strider

my_agent_name_is_strider_2

3 Make sure that one or more data selections that you want to export have beencreated and backed up.

If no backed up data selections exist in the storage pool, use the instructionsin thePureDiskBackupOperator'sGuide to create one or more data selectionsand back them up to the storage pool.

4 Create a PureDisk policy to export data to NetBackup.

For information about how to create an export to NetBackup policy, see thefollowing:

See “Creating or editing an export to NetBackup policy” on page 85.

Creating or editing an export to NetBackup policyThe export process copies the data selections to NetBackup, but it leaves the dataon the content routers intact. You can have multiple export policies, but becausethe export is a single stream, only one export can occur at a time.

The following paragraphs explain how PureDisk manages export jobs:

85Exporting data to NetBackupCreating or editing an export to NetBackup policy

■ You can create multiple PureDisk export policies for a single NetBackup exportengine. PureDisk runs one export job per export policy at a time.

■ If you have two or more PureDisk export policies, these policies can send datato the same NetBackup DataStore policy. However, you are not limited to onlyone NetBackup DataStore policy. You can have multiple NetBackup DataStorepolicies.

■ PureDisk can run multiple export jobs simultaneously from multiple NetBackupexport engines if the data originated on two or more PureDisk clients. However,if the export jobs work with data that originated from a single PureDisk client,PureDisk runs the jobs one at a time.

Use the following procedure to create a PureDisk policy that can export Files andFolders data selections to NetBackup.

To create an Export to NetBackup policy


2 In the left pane, under DataManagementPolicies, click ExporttoNetBackup.

3 Complete one of the following steps:

■ To create a policy, in the right pane click Create Policy.

■ To edit a policy, expand Export to NetBackup and click a policy name.


See “Completing the General tab for an Export to NetBackup policy”on page 87.

5 Complete the Data Selections tab.

See “Completing the Data Selections tab for an Export to NetBackup policy”on page 88.


See “Completing the Scheduling tab for an Export to NetBackup policy”on page 89.


See “Completing the Parameters tab for an Export to NetBackup policy”on page 89.

8 Complete the Metadata tab.

See “(Optional) Completing the Metadata tab for an Export to NetBackuppolicy” on page 89.

9 Click Add when done.

Exporting data to NetBackupCreating or editing an export to NetBackup policy

86

Completing the General tab for an Export to NetBackup policyUse the following procedure to complete the General tab.


1 Type a name for this policy in the Policy Name field.


This setting lets you control whether PureDisk runs the policy according tothe schedule that you specify in the Scheduling tab. The following situationsillustrate how the settings might be used:

■ If you select Enabled, PureDisk runs the policy according to the schedule.This selection is the default.

■ If you select Disabled, PureDisk does not run the policy according to theschedule.One example of how to use Disabled is when you want to prevent thispolicy from running during a system maintenance period. However, youdo not want to enter information in the Scheduling tab to suspend andreenable this policy.

3 (Optional) Specify escalation times and actions.

PureDisk can notify you if a backup does not complete within a specified time.For example, you can configure PureDisk to send an email message to anindividual if a backup policy workflow does not complete in an hour.

Select times in the Escalatewarningafter or the Escalateerrorandterminateafter drop-down boxes to specify the elapsed time. If the policy workflowdoes not complete before the warning timeout (6 hours is the default value),PureDisk generates a warning message. If the policy workflow does notcomplete before the error timeout, PureDisk generates an error message andterminates the job. The default value for the error timeout is five days.

Do not set the time values low if the backup policy pertains to agents thathave to back up a large number of files. For example, on a system with 1.5million files, the scan step of a backup job typically takes 6 hours to complete.The amounts of time required needed for the other steps are more difficultto predict. They depend on the actual number of files that need to be uploaded.

In addition to selecting escalation times, you need to create a policy escalationaction and an event escalation action. These escalation actions define theemail message, define its recipients, and associate the escalation action withthe policy.

For information about policy escalation actions and event escalation actions,see the PureDisk Backup Operator’s Guide.


Completing the Data Selections tab for an Export to NetBackup policyIf you specify more than one data selection, PureDisk exports each Files andFolders data selection as a separate job. Use the following procedure to completethis tab.

To complete the Data Selections tab

1 Expand the tree and select one or more data selections.

PureDisk displays the Files and Folders data selections. To specify a numberof data selections, select a storage pool or department. This action selects alldata selections that exist under the storage pool or department.

PureDisk associates a data selection with a client. When you save the policy,PureDisk applies it to all specified data selections and the associated clients.

If you do not select at least one Files and Folders data selection, PureDiskbacks up all data selections in the storage pool.

If you do not select at least one item in the tree, PureDisk does not save thefilter.

2 Select Include all data selections selected above.

3 (Optional) Select Applyall inclusionrulesbelowtodata selections selectedabove.

Use one of the following filter methods:

■ Fill in the Data selection name or Data selection description fields withcharacters and wild cards (* and ?). This method filters the data selectionsbased on their names or their descriptions.For example, assume that the following data selection names exist andare selected under a department in the tree:

U_*.jpg_files

W_*.jpg_files

W_*.xls_files

If you type *files in the Data selection name field, the policy backs upall three data selections.If you type W* in the field, the data selections for this policy include onlythe data selections that are named W_*.jpg_files and W_*.xls_files.

For more information about filtering, see the following:See the PureDisk Backup Operator’s Guide.

■ (Conditional) Select a template from the Dataselectionsbasedontemplatedrop-down box to specify an existing data selection template to use.


88

This template applies to Files and Folders data selections only. The dataselection uses the data selection rules from the template. These rulesdetermine the files and directories to back up.You can select any data selection that you previously applied to the client.

Completing the Scheduling tab for an Export to NetBackup policyUse the following procedure to complete this tab.

To complete the Scheduling tab

1 Select hourly, daily, weekly, or monthly to specify how frequently you wantthis policy to run.

PureDisk runs the policy at the time you specify in the storage pool’s timezone.

2 Select the schedule details.

Base your selections on the frequency that you specified in the previous step.

Completing the Parameters tab for an Export to NetBackup policyThe following section explains how to complete this tab.

To complete the Parameters tab

1 In the NetBackup Policy Name field, specify the name of the NetBackupDataStore policy.

For more information about configuring NetBackup to accept PureDisk dataselections, see the following:

See “Configuring NetBackup to receive data exported from PureDisk ”on page 79.

2 In the PureDisk toNetBackupexport engine field, select the PureDisk nodewhere you installed the NetBackup client and the PureDisk NetBackup exportengine.

The node appears on the drop-down list.

(Optional) Completing the Metadata tab for an Export to NetBackuppolicy

Use the following procedure to complete this tab if you want to exclude certainfiles from the export. If you want to export entire data selections, do not specifyanything on this tab.


To complete the Metadata tab

1 Click Add to define a metadata inclusion rule for the policy.

You can specify any or all filters. A file must fulfill all of the specified rulesbefore PureDisk includes the file in the data selection.

2 In Rule name, type a name for this filter.

Tip: Use a U or a W as the first character in the filter name. It helps you toidentify whether the filter is for a UNIX or a Windows client.

3 In Folder name, type the complete path or a pattern of the folder where thefiles reside.

Tip: You can use characters and wildcards to specify both absolute folderpatterns and relative folder patterns.

4 In File name field, type a pattern that describes the files.

For more information and examples about filtering, see the PureDisk BackupOperator's Guide.

5 In Size, use the drop-down lists to specify a filter.

Base the choice on the size of the file. For example:

■ You can select a file size that is greater than or equal to 100 bytes and lessthan or equal to 500 bytes. In this case, PureDisk includes files that arefrom 100 bytes to 500 bytes.

■ You can select a file size that is less than or equal to 500 bytes. In thiscase, PureDisk includes files that are from 1 byte to 500 bytes in length.

■ You can select a file size that is greater than or equal to 100 bytes. In thiscase, PureDisk includes files that are 100 bytes or longer.

6 In Last Modification, use the drop-down lists to specify a filter.

Base this choice on the time the file was last modified. Select a date-based ortime-based boundary.

For example, if you specify January 20, 2009, in the Before field, the filterincludes all files that were modified before 12:01 AM on January 20, 2009.The filter includes the files that were modified any time of day on January19, 2009.

7 Click OK.


90

Caution: The filters in the Metadata tab of an Export to NetBackup policy let younarrow the list of files that you want PureDisk to export. If you do not definefilters, PureDisk exports all the files. When you specify filters in an Export toNetBackup policy, you might encounter occasional problems when you browsefiles in NetBackup Backup and Restore interface. The problems can occur withthe NetBackup images that PureDisk creates. If you do not find your exportedfiles when you use NetBackup's Backup and Restore interface, use the bplist(1M)NetBackup command line utility.

To edit or delete a metadata inclusion rule

1 Select a rule.

2 Select Edit and make changes to the filter rule, or select Remove.

Running an export to NetBackup policyThe export to NetBackup policy runs according to the schedule that you specifiedin the PureDisk policy when you created it.

The following procedure explains how to run the policy one time for a point-in-timeexport. To complete this procedure, you must have PureDisk restore permissions.

To run an export to NetBackup policy one time


2 In the left pane, under Data Management Policies, expand Export toNetBackup.

3 Select the policy you want to run.

4 In the right pane, click Run Policy.

The PureDisk Backup Operator’s Guide explains how to enable policyescalation actions and how to monitor policy runs. NetBackup writes log filesof its activity to /usr/openv/netbackup/logs/pdexport.

Performing a point-in-time export to NetBackupUse the following procedure to perform a one-time export of a backed up PureDiskFiles and Folders data selection to NetBackup. If you use this method, you stillneed to define a NetBackup DataStore policy. However, you do not need a PureDiskexport to NetBackup policy with this method.

91Exporting data to NetBackupRunning an export to NetBackup policy

To perform a point-in-time export to NetBackup

1 Verify that you have a NetBackup DataStore policy defined.

See “Configuring NetBackup to receive data exported from PureDisk ”on page 79.

2 Click Manage > Agents.

3 In the left pane, expand the tree to display the data selection that you wantto export.

4 Select the data selection that you want to export.

5 In the right pane, click Export Whole Data Selection.

6 Specify the following information in the Export files from agent dialog box:

The date when the data selection to be exported toNetBackup was backed up.

Date

The time when the data selection to be exported toNetBackup was backed up.

Time

Specify the name of the NetBackup DataStore policy.NetBackup Policy Name

Select the PureDisk NetBackup export engine in yourstorage pool that you want to use to perform theexport.

PureDisk to NetBackupExport Engine

7 Click Export files.

Caution: If the export job finds no backups that match the date specified, thejob runs and shows successful completion, but PureDisk exports nothing toNetBackup. This behavior differs from the behavior for regular backupsbecause regular backups fail if nothing is backed up.

Troubleshooting export job failuresThe following information can be helpful in troubleshooting NetBackup exportjobs:

■ See “NetBackup export engine log files” on page 93.

■ See “Problems with inactive server agents” on page 93.

Exporting data to NetBackupTroubleshooting export job failures

92

NetBackup export engine log filesTo enable logging for NetBackup export jobs, change the configuration file settings.The following procedure explains the configuration file fields to change. Forgeneral information about how to edit configuration files, see the following:

See “About the configuration files” on page 321.

To enable logging

1 Click Settings > Configuration > Configuration File Templates > PureDiskServer Agent > Default ValueSet for PureDisk Server Agent > debug >logging.

Set logging to either info (default), debug, or trace.

2 Click Settings > Configuration > Configuration File Templates > PureDiskServerAgent>DefaultValueSetforPureDiskServerAgent>debug>trace.

The trace field specifies the directory to which PureDisk writes the log file.The default is /Storage/log. Edit the trace field to specify an alternativedirectory.

Problems with inactive server agentsPureDisk cannot run any job that originates from a node with an inactive serveragent. If you have more than one NetBackup export engine, and an export job failsto run, ensure that all appropriate server nodes are active.

Specifically, PureDisk cannot run an export job if all of the following conditionsexist when you start the job:

■ You installed two or more NetBackup export engines on different PureDisknodes. PureDisk lets you install more than one NetBackup export engine in astorage pool. However, if the following three conditions also exist, an exportjob fails.

■ The server agent on one of the nodes that hosts a NetBackup export engine isinactive.

■ You have export policies for each of the NetBackup export engines.

■ Each export policy exports the same data selection.

In this situation, PureDisk cannot run the policies to export that specific dataselection. Even the export jobs that are scheduled to run on nodes with activeserver agents fail to run.

The server agent must always be active in order for PureDisk to run jobs for thatnode. However, in this scenario, an inactive server agent can affect the scheduledjobs on an active server agent.

93Exporting data to NetBackupTroubleshooting export job failures

To avoid this situation, ensure that each server agent on each node that hosts aNetBackup export engine is activated.

To activate a server agent


2 Expand the tree in the left pane so that it shows all the PureDisk services.

3 Select the service you want to start.

For example, select NBU Export Engine.

4 In the right pane, click Activate NetBackup Export Engine.

Copying or deleting an export to NetBackup policyThe following procedure explains how to copy or delete a policy that exports datato NetBackup.

To edit, copy, or delete a policy


2 In the tree pane, expand DataManagementPolicies>Export toNetBackup.

3 Select a policy.

4 In the right pane, click the action you want to perform.

Select from one of the following:

■ Delete Policy.

■ Copy Policy.A copy of the policy appears in the tree. The policy is in the disabled state.

Restoring from NetBackupNetBackup treats PureDisk data selections as if they were regular NetBackup files.During the export process, NetBackup creates catalog information. The NetBackupcatalog is a record of files and the names of the clients upon which the filesoriginated. When you export data from PureDisk to NetBackup, the client namethat NetBackup uses is the name of the client upon which the files originated.

Example 1. Figure 4-1 shows an export policy on node_3 that exports data fromspeedy to NetBackup. In NetBackup, the client name that appears in the NetBackupcatalog is speedy.

Exporting data to NetBackupCopying or deleting an export to NetBackup policy

94

Example 2. If you replicate a data selection and then export that data selectionfrom the destination storage pool, the destination storage pool displays the sourceclient's name. The source client's name appears in the following format:

[R] client_name (agx,stpy)

In the preceding client name format, the following are replaced:

■ client_name is the name of the client.

■ x is the agent identifier.

■ y is the storage pool identifier.

When you export a replicated data selection from the destination storage pool toNetBackup, NetBackup removes the [R] characters at the beginning, the agentID at the end, and the storage pool ID at the end.

For example, assume the following series of events:

■ You have two storage pools: my_spa and your_spa. A client named clientA isattached to my_spa.

■ You replicate clientA's backed-up data selections from my_spa to your_spa.If you look at your_spa's Web UI, clientA appears as follows:

[R] clientA (ag5,stp123).

■ You configure your_spa as a NetBackup client.

■ You export clientA's data selections from your_spa to NetBackup.

■ You restore clientA's data selections from NetBackup. When you want torestore the data selections from clientA, look for a client named clientA inthe NetBackup interface.

The NetBackup job monitor displays the name of the node that hosts the PureDiskNetBackup export engine and the NetBackup client. In Figure 4-1, the name thatappears in the job monitor depends on which export engine did the export. Thename is node_1 or node_3.

In the NetBackup catalog, the NetBackup policy that exports data from PureDiskto NetBackup is called a PureDisk-Export policy. The policy type number is 38.

For more information about how to restore files from NetBackup, see the following:


95Exporting data to NetBackupRestoring from NetBackup

Restoring to a PureDisk client that is not aNetBackupclient

The following procedure uses general terms to describe how to restore files fromNetBackup. This procedure assumes that you have not installed the NetBackupclient software on the PureDisk client.

To restore the files to the PureDisk environment

1 Log on to the PureDisk node that hosts the NetBackup client software.

If more than one node hosts NetBackup client software, log on to the node towhich you want to write the files.

2 Create a restore directory.

For example:

# mkdir restoredir

3 From the NetBackup administration console, use the NetBackup Backup,Archive, and Restore interface to perform a client-redirected restore.

The client-redirected restore is needed for the following reasons:

■ You can restore only to a system that hosts a NetBackup client.

■ The name of the NetBackup client appears in the NetBackup catalog. Notethat it is not the PureDisk client.Refer to Figure 4-1. This example shows that the clients speedy and kwiek

appear in the NetBackup catalog.

More information on how to enable a client-redirected restore is available.


For example, assume the following:

■ The PureDisk environment is depicted in Figure 4-1.

■ The name of the NetBackup policy that performed the export wasPDExport.

■ The name of the NetBackup master server is NBUMasterServer.

■ You want to write the files to their original location on the PureDisk nodethat is defined as the PureDisk NetBackup export engine (node_3). Thislocation was /bin/myfiles.

More information about restoring files to an alternate directory.See the NetBackup Administrator’s Guide, Volume I

Exporting data to NetBackupRestoring to a PureDisk client that is not a NetBackup client

96

4 Use a network method to move the files from the PureDisk node with theNetBackup client software to the PureDisk client that needs the files.

For example, you can use FTP to transfer the file.

This step writes the files to the client, but it does not put the files underPureDisk control. Perform the next step if you want to use PureDisk to backup the files again, which puts them under PureDisk control.

5 (Optional) Use PureDisk to back up the files.

This step puts the files back into the PureDisk environment.

More information on how to perform a backup is available.


Restoring to aPureDisk client that is also aNetBackupclient

The following procedure uses general terms to describe how to restore files fromNetBackup. This procedure assumes that you have installed the NetBackup clientsoftware on the PureDisk client.

To restore the files to the PureDisk environment

1 Log on to NetBackup.

2 From the NetBackup administration console, use the NetBackup Backup,Archive, and Restore interface to perform a restore directly to the client.

3 (Optional) Use PureDisk to back up the files.

This step puts the files back into the PureDisk environment.

More information on how to perform a backup is available.


97Exporting data to NetBackupRestoring to a PureDisk client that is also a NetBackup client

Exporting data to NetBackupRestoring to a PureDisk client that is also a NetBackup client

98

Disaster recovery backupprocedures


■ About disaster recovery backup procedures

■ About performing disaster recovery backups

■ About backing up your PureDisk environment using NetBackup

■ Configuring PureDisk disaster recovery backup policies

■ About backing up your PureDisk environment using scripts

■ Troubleshooting a disaster recovery backup

About disaster recovery backup proceduresA disaster recovery backup protects the data in your PureDisk environment. Youcan back up your storage pool data to NetBackup, to a Samba share, or to athird-party product. The PureDisk disaster recovery backup policies protect thefollowing types of PureDisk data:

■ The backup data on the content routers. The content routers are the repositoryfor backup files.

■ The spool area. This area is the buffer in which PureDisk stores data before itwrites the data to the content routers.

■ The PureDisk databases on the content routers, the metabase servers, themetabase engines, and the storage pool authority. Most PureDisk services havetheir own database, and there is one database management system that controlsall the service databases.

5Chapter

■ The PureDisk software configuration on the content routers, the metabaseservers, the metabase engines, and the storage pool authority.

For information on disaster recovery backups, see the following:

■ See “About performing disaster recovery backups” on page 100.

■ See “About backing up your PureDisk environment using NetBackup”on page 101.

■ See “About backing up your PureDisk environment using scripts” on page 114.

■ See “Configuring PureDisk disaster recovery backup policies” on page 106.

In addition to the preceding disaster recovery backup methods, PureDisk includesStorage Pool Authority Replication (SPAR). SPAR replicates storage poolconfiguration information from one all-in-one storage pool to another. Forinformation about SPAR, see the following:

See “About storage pool authority replication (SPAR)” on page 199.

If you need to recover from a disaster, use the PureDisk disaster recovery script,DR_Restore_all.sh. The disaster recovery method is the same regardless of whichdisaster recovery backup method you used. For information about the recoveryprocess, see the following:

■ See “About restoring an unclustered PureDisk environment” on page 121.

■ See “About restoring a clustered PureDisk environment” on page 157.

Note: To recover PureDisk when you have enabled the PureDisk deduplicationoption (PDDO), see the PureDisk Deduplication Option Guide. It containsPDDO-specific information, which includes how to avoid a potential data losssituation.

About performing disaster recovery backupsDepending on your backup method, the disaster recovery backup process is asfollows:

■ If you use NetBackup, PureDisk uses NetBackup backup policies to copy thedata to NetBackup storage. This method requires that you install NetBackupclient software on each node in the storage pool.See “About backing up your PureDisk environment using NetBackup”on page 101.

■ If you use a script, PureDisk calls the script that you provide.

You can use one of the following methods:

Disaster recovery backup proceduresAbout performing disaster recovery backups

100

■ You can write your own backup script.

■ You can use one of the scripts that PureDisk includes. You can also modifyone of these scripts.

■ You can write a script that invokes a third-party backup product.See “About backing up your PureDisk environment using scripts”on page 114.

When the disaster recovery backup policy runs, it preserves all data that you needto restore a PureDisk environment in the event of a disaster. A disaster recoverybackup ensures that you can return your environment to its previous state.

The following processes occur when the disaster recovery policy runs:

■ It backs up the metadata in the storage pool.

This backup includes the following data:

■ Storage pool authority database

■ The database(s) for the metabase engines

■ The topology files

■ It backs up the database on the content routers.

■ It creates a list of files in the spool area.For an incremental backup, it also creates a list of changed files and new fileson the content router. An incremental backup backs up new or changed contentrouter data from the last full backup.Your last full backup must be available for incremental backups.

■ It backs up the client data by using the backup method you specify. Client dataincludes the spool area, the new files, and the changed files on the contentrouters.

■ It backs up the configuration files on all nodes.

About backing up your PureDisk environment usingNetBackup

When you use NetBackup to perform PureDisk disaster recovery backups, youfirst need to create a NetBackup backup policy. PureDisk uses its own systempolicies to send the data to NetBackup. You can restore the data back to PureDiskby using the PureDisk disaster recovery scripts.

The following sections describe how to use NetBackup to back up your PureDiskenvironment.

101Disaster recovery backup proceduresAbout backing up your PureDisk environment using NetBackup

Prerequisites for NetBackup disaster recovery backupsVerify that your environment includes the following:

■ A separately mounted partition named /Storage. The separate mountingenables high performance and is a requirement for disaster recovery backups.

■ A network connection between every PureDisk node and a NetBackupenvironment. The NetBackup environment must be running NetBackup serversoftware at the 6.0 MP5 release level or greater.

■ A NetBackup client software package at the 6.0 MP5 release level or greater.Install this client software on every PureDisk node in the storage pool.

Note: Make sure that the NetBackup client software version number is thesame as the NetBackup environment version number.

For more information about how to install the software, see the following:See “Configuring the NetBackup client software” on page 102.

Configuring the NetBackup client softwareThe following procedure explains how to configure NetBackup client software.

To configure the NetBackup client software

1 Install the NetBackup Linux SUSE 2.6 client on each node in your PureDiskstorage pool.

If the storage pool is clustered, install the client on all nodes, including thepassive node.

For general information about how to install the NetBackup client, see theNetBackup Installation Guide for UNIX and Linux.

When you install the client software, use the fully qualified domain name(FQDN) for the client name. For example, answer n to the following shortname prompt:

Would you like to use "my_pdnode" as the

configured name of the NetBackup client? [y,n] (y) n

Enter the name of the NetBackup client: my_pdnode.my_domain.com

If you accept the short name during the install, edit the/usr/openv/netbackup/bp.conf file on each node and change the line thatidentifies the client. For example:

Disaster recovery backup proceduresAbout backing up your PureDisk environment using NetBackup

102

CLIENT_NAME=my_pdnode.my_domain.com

2 (Conditional) For each PureDisk node, create a file for the host FQDN andanother file for the service FQDN in the altnames directory on the NetBackupmaster server.

Perform this step if the storage pool you want to back up is clustered.

This step is needed because the bp.conf file on each node contains thephysical host address. However, the backup process and the restore processuse the service address.

If necessary, create the altnames directory itself. Within the directory, createa file of the following format for each node:

xxxxnode1.symc.be

Create these files for each node in the PureDisk storage pool.

Example 1.

To create the altnamesdirectory on a UNIX master server, type the followingcommand:

# mkdir /usr/openv/netbackup/db/altnames

Example 2.

Assume that you want to create file names in the altnames directory for thenodes in the following two-node cluster:

■ Node 1 = allinone.acme.com (host FQDN) and allinones.acme.com

(service FQDN)

■ Node 2 = passive.acme.com (host FQDN) and passives.acme.com (serviceFQDN)

To create a file in the altnames directory of a UNIX master server, you typethe following commands:

# touch allinone.acme.com

# touch allinones.acme.com

# touch passive.acme.com

# touch passives.acme.com


For information about the altnames directory and creating files inside thealtnames directory, see the NetBackup Administrator’s Guide, Volume I.

3 Verify that the xinetd daemon is running on each node.

This service ensures proper communication between the NetBackup masterserver and the Linux client. Type the following command to determine ifxinetd is running:

# ps -aef |grep xinetd

If it is not running, enter the following command:

# /etc/init.d/xinetd start

If you restart the system, type the following command to ensure that thexinetd daemon starts:

# /sbin/insserv /etc/init.d/xinetd

Enabling NetBackup for PureDisk backupsThe procedure in this topic uses general terms to describe how to create NetBackuppolicies for backing up PureDisk data. For more information about the specifictasks you need to perform when you create these policies, see the following:


To enable NetBackup to back up a PureDisk storage pool

1 Make sure that you have accurate topology and node identificationinformation for this storage pool.

This information might be needed during a disaster recovery. Make sure thatthe information on the cluster planning spreadsheet (for clustered storagepools) or on the installation worksheets (for unclustered storage pools) isaccurate.

2 Log on to the NetBackup administration console.

3 Create a NetBackup Standard policy with a user backup schedule.

This policy is for the PureDisk content router and spool area data.

When you create the NetBackup policies, note the following rules:

■ Observe the NetBackup policy naming rules.

Disaster recovery backup proceduresAbout backing up your PureDisk environment using NetBackup

104

For information about NetBackup policy names, see the following:See “About NetBackup policy names” on page 106.Remember the name of these NetBackup policies. You specify these namesagain when you create the PureDisk disaster recovery backup policies.When you create the NetBackup Standard policy, use the same FQDN forthe client that you specified when you installed the client. For example,use my_pdnode.my_domain.com to identify the client. The client namemust appear identically in the NetBackup policy and in the bp.conf fileon the PureDisk node.Make sure that all PureDisk nodes are included in the client list in theNetBackup Standard policy.If the storage pool is clustered, specify the node service FQDN in theNetBackup Standard policy. Do not specify the host address.If your PureDisk environment is set up with /Storagemounted on an NFSshare, make sure to check the option Follow NFS in the NetBackupStandard policy definition.

■ Entries are not required on the NetBackup Backup Selections tab.

■ Make sure that the schedule allows backups 24 hours a day and sevendays a week. This method allows PureDisk to send data to NetBackup atany time.

4 Create a NetBackup DataStore policy with an application backup schedule.

This policy is for the PureDisk metadata. Observe the same naming rulesregarding NetBackup policies, FQDNs, and so on as described in the following:

See “About NetBackup policy names” on page 106.

Make sure that all PureDisk nodes are included in the client list in theNetBackup DataStore policy.

5 Use the PureDisk Web UI to edit the following policies:

■ The System policy for full DR backup

■ The System policy for incremental DR backup

PureDisk includes these policies by default. When you edit these policies,enable them, specify information specific to your site, and optionally, createpolicy escalation actions for them.

Make sure that all PureDisk nodes are included in the client list in theNetBackup DataStore policy.

For more information about how to create PureDisk disaster recovery backuppolicies, see the following:

See “Configuring PureDisk disaster recovery backup policies” on page 106.


About NetBackup policy namesThe PureDisk Web UI does not verify that the policy names you enter comply withthe NetBackup naming conventions. As a consequence, you can possibly enter apolicy name in the disaster recovery backup policy that is not valid for NetBackup.Avoid this situation.

NetBackup enforces the following naming conventions for its policies:

■ Policy names cannot start with a dash (-).

■ Policy names cannot include space characters.

■ Policy names cannot include the characters / @ # * & ^

Configuring PureDisk disaster recovery backuppolicies

PureDisk includes the following disaster recovery backup policies:

■ A full disaster recovery backup policy, which backs up the entire storage pool.

■ An incremental disaster recovery backup policy, which backs up theinformation that changed since the last full or incremental backup ran.

You might need to experiment with your disaster recovery backup policy schedulesfor both full backups and incremental backups. A full backup takes longer tocomplete than an incremental backup.

For example, you might run a full disaster recovery backup one time each week.You might run incremental disaster recovery backups on the other days of theweek.

The exact schedule depends on several factors:

■ How much data is in your storage pool

■ How frequently you need to restore data

■ How quickly you need to restore data

The following procedure explains how to enable the backup policies.

Disaster recovery backup proceduresConfiguring PureDisk disaster recovery backup policies

106

To enable PureDisk disaster recovery backup policies

1 Log on to the storage pool and start the Web UI.

2 Verify that you configured NetBackup or scripts to back up your PureDiskstorage pool. Make sure that one of these backup structures is in place beforeyou enable the PureDisk disaster recovery backup policies.

For more information about how to create backups, see the following:

See “About backing up your PureDisk environment using NetBackup”on page 101.

See “About backing up your PureDisk environment using scripts” on page 114.


4 In the left pane, under StoragePoolManagementPolicies, expand DisasterRecovery Backup.

5 Select one of the following policies:

■ System policy for full DR backup

■ System policy for incremental DR backup

The procedures for enabling these policies are identical. In addition, the tabsand fields in the Web UI are the same for each of these policy types. Thesepolicies differ only in the type of backup that PureDisk runs when you enablethem.


See “Completing the General tab for a disaster recovery backup policy”on page 108.


See “Completing the Scheduling tab for a disaster recovery backup policy”on page 109.


See “Completing the Parameters tab for a disaster recovery backup policy”on page 109.

9 Click Save when done.

107Disaster recovery backup proceduresConfiguring PureDisk disaster recovery backup policies

10 (Optional) Create a policy escalation action for this policy.

The policy escalation action defines the event escalation email message andits recipients. Make sure to associate the escalation action with the policy.For more information, see the PureDisk Backup Operator's Guide.

11 (Optional) Repeat the preceding steps to configure the other policy type.

For example, after you configured a SystempolicyforfullDRbackup, repeatthe preceding steps but select System policy for incremental DR backup.

Completing the General tab for a disaster recovery backup policyThe following procedure explains how to complete the General tab.



Perform this step only if you want to rename this policy.


This setting lets you control whether PureDisk runs the policy according tothe Scheduling tab, as in the following situations:

■ If you select Enabled, PureDisk runs the policy according to the schedule.After you enable a policy, you can run the policy on a schedule or manually.

■ If you select Disabled, PureDisk does not run the policy according to theschedule. If a policy is disabled, PureDisk cannot run the policy accordingto a schedule, and you cannot run the policy manually. This selection isthe default.For example, if you want to stop running the policy during a systemmaintenance period select Disabled. You do not need to enter informationin the Scheduling tab to suspend and later reenable the policy.

3 (Optional) Select times in the Escalate warning after or the Escalate errorand terminate after drop-down lists.

These times specify the elapsed time before PureDisk sends an email message.

PureDisk can notify you if a backup does not complete within a specified time.These fields allow you to define the times for escalation actions.

For example, you can configure PureDisk to send an email message to anadministrator if the policy does not complete in eight hours.


108

Completing the Scheduling tab for a disaster recovery backup policyThe disaster recovery backup policy runs according to the schedule you specifywhen you edit the policy. The first time you run a disaster recovery backup policy,PureDisk performs a full backup. By definition, subsequent disaster recoverybackups are incremental backups.

See “Configuring PureDisk disaster recovery backup policies” on page 106.

The following procedure explains how to complete this tab.

To complete the Scheduling tab

◆ Select hourly, daily, weekly, or monthly schedule to specify how frequentlyyou want this policy to run.

You can also specify an exact start time to run the schedule.

The following are additional notes on scheduling disaster recovery backups:

■ Symantec recommends that you run disaster recovery backups when otherbackups are not running. You can run a disaster recovery backup at the sametime that regular system backups run. However, you cannot restore the datayou backed up during the regular system backup.

■ When you run a full disaster recovery backup, content router performancedegrades. This issue is due to increased file system activity. In extreme cases,a full backup can cause regular backup jobs to fail. Schedule full backups duringa time when other backups are not running.

■ You can customize the schedule to suit your site’s needs. You can experimentwith different schedules. You want to balance the frequency with which thispolicy runs and system resource usage.

■ If you want to run the policy only one time, select an active policy and clickRun Policy from the left pane. After the policy runs, open the General tabagain and disable the policy. If you do not disable the policy, it runs againaccording to the schedule that you specified in the Scheduling tab.

■ If you use NetBackup as your backup tool, make sure that you schedule thePureDisk backup policies to run during NetBackup’s open window. Symantecrecommends that you specify the NetBackup schedule to allow backups 24hours a day and seven days a week.

Completing the Parameters tab for a disaster recovery backup policyThis tab is divided into three sections. Each represents one of the three possiblemethods you can use to back up your PureDisk data.


Note:

Choose only one method to back up your PureDisk data (NetBackup, Samba Share,or Third Party Product). Then, complete all of the information fields for thatmethod. Do not complete any fields for the methods that you do not choose.

To choose a disaster recovery backup method

◆ Choose one of the following disaster recovery backup methods and followthe procedure associated with that backup method:

■ NetBackup. For information about how to complete the Parameters tabfor a NetBackup backup, see the following:See “Completing the Parameters tab on a Disaster recovery policy to backup PureDisk to a NetBackup environment” on page 110.

■ Samba. For information about how to complete the Parameters tab for aNetBackup backup, see the following:See “Completing the Parameters tab on a Disaster recovery policy to backup PureDisk to a Samba file system” on page 111.

■ Third party. For information about how to complete the Parameters tabfor a NetBackup backup, see the following:See “Completing the Parameters tab on a Disaster recovery policy to backup PureDisk to a third-party product” on page 112.

Completing the Parameters tab on a Disaster recovery policyto back up PureDisk to a NetBackup environmentThe following procedure explains how to complete the Parameters tab to backup PureDisk to a NetBackup environment.

Make sure you are familiar with how to create NetBackup policies. For informationabout how to create NetBackup policies, see theNetBackupAdministrator’sGuide,Volume I.

The following procedure describes how to use NetBackup to back up PureDiskdata.

To use NetBackup to back up PureDisk

1 Select Use NetBackup.

2 In the StandardPolicy field, type the name of the NetBackup standard policythat you configured to back up this data.

3 In the DataStore Policy field, type the name of the NetBackup DataStorepolicy that you configured to back up this data.


110

4 In the Number of Parallel streams drop-down list, select the number ofparallel streams that you specified when you created the NetBackup Standardpolicy.

5 Click Save.

Completing the Parameters tab on a Disaster recovery policyto back up PureDisk to a Samba file systemThe following procedure describes how to complete the Parameters tab to backup PureDisk data to a Samba file system on another computer.

To use a Samba share to back up PureDisk

1 Make sure that Samba is configured on the computer to which you want towrite the PureDisk backups.

2 Select Use Samba Share.

3 In the Full path of data backup program field, specify the full path and thename of the backup script that you want to use.

The /opt/pdconfigure/scripts/support/DR_BackupSampleScripts/

directory contains sample disaster recovery backup scripts.

Symantec recommends that you use the following scripts:

■ full_DR_backup.sh

■ incremental_DR_backup.sh

4 In the Directory Path Name field, specify the full path (mount point) to adirectory in which to write the backed up files.

Specify /DRdata in this field if the following are both true:

■ You used thefull_DR_backup.sh script or theincremental_DR_backup.shscript.

■ You did not modify the scripts.These scripts write to /DRdata. The write occurs even if the directory ismounted to another disk or partition. The script mounts to the directoryyou specify and writes to it.

Specify your own directory in this field if either of the following are true:

■ You do not use the full_DR_backup.sh script or theincremental_DR_backup.sh script.

■ You modified the scripts to write to a different directory. Make sure thatyour backup scripts write to the directory you specify. PureDisk does notmount this directory.


5 In the Share Name field, specify the name of a remote Samba shared filesystem.

Use the following format for the shared file system:

//hostname/sharename

These variables are as follows:

Specify the host name or IP address upon which the targetshared directory resides.

hostname

Specify the name of the shared directory on hostname.sharename

For example: //100.100.100.101/pde_dr_files

6 In the Workgroup / Domain field, specify the domain name.

7 In the User Name field, specify the Samba user name.

8 In the Password field, specify the Samba password.

9 Select UseEncryption to have PureDisk encrypt the configuration data beforeit writes the data.

UseEncryption does not cause segment data to be automatically encrypted.

10 Click Save.

11 (Conditional) Update or verify the storage pool’s topology information.

Perform this step if you selected Use Encryption in the previous step.

If you perform the backup with encryption enabled, make sure that you haveaccurate topology and node identification information. This information isneeded during a disaster recovery. Make sure that the information on thecluster planning spreadsheet (for clustered storage pools) or on the installationworksheets (for unclustered storage pools) is accurate.

Click Settings > Topology to examine the storage pool's topology.

Completing the Parameters tab on a Disaster recovery policyto back up PureDisk to a third-party productThe following procedure describes how to complete the Parameters tab to backup PureDisk data to a third-party product.


112

Caution: If you choose this method, be aware that you need to copy your backupsto a secondary host. If the primary host fails, you are likely to lose both the originalfiles and the backed up files that are written to the local directory.

To use a third-party product to back up PureDisk

1 Select Use Third Party Product.

2 In the Full path of data backup program field, specify the full path and thename of the backup script you want to use.

The /opt/pdconfigure/scripts/support/DR_BackupSampleScripts/

directory contains sample disaster recovery backup scripts.

Symantec recommends you use the following scripts:

■ full_DR_backup.sh

■ incremental_DR_backup.sh

3 In the Directory Path Name field, specify the full path to the directory inwhich to write the backed up files.

If you modified or did not use the full_DR_backup.sh script or theincremental_DR_backup.sh script, specify your own directory in this field .

If you used the full_DR_backup.sh script or the incremental_DR_backup.shscript and did not modify them, specify /DRdata in this field.

These scripts write to /DRdata. The write occurs even if the directory ismounted to another disk or partition. The script mounts to the directory youspecify and writes to it.

4 Select UseEncryption to have PureDisk encrypt the configuration data beforeit writes the data.

UseEncryption does not cause segment data to be automatically encrypted.

5 Click Save.

6 (Conditional) Update or verify the storage pool’s topology information.

Perform this step if you selected Use Encryption in the previous step.

If you perform the backup with encryption enabled, make sure that you haveaccurate topology and node identification information. This information isneeded during a disaster recovery. Make sure that the information on thecluster planning spreadsheet (for clustered storage pools) or on the installationworksheets (for unclustered storage pools) is accurate.

Click Settings > Topology to examine the storage pool's topology.


About backing up your PureDisk environment usingscripts

The following sections discuss how to use scripts for disaster recovery.

Your options are as follows:

■ Use one of the sample scripts that PureDisk provides. Alternatively, you cancustomize these scripts for your own site’s use.

■ Write your own backup script. This script can invoke a third-party backuptool.

Prerequisites for script-based disaster recovery backupsBefore you enable a disaster recovery policy, identify and create a repository forthe backup files that this policy creates. The repository can be a local file systemor a Samba shared file system.

For example, you can back up your PureDisk environment to a file system on aserver that is outside of the PureDisk environment. Such a file system must bewithin the Samba or shared file system.

If you write to a shared file system outside of the PureDisk storage pool, makesure of the following:

■ The server to which you want to write the PureDisk backup is connected tothe network.

■ A Samba shared file system is mounted on the computer to which you wantto write the backup.

■ The /Storage partition is mounted as a separate partition. The separatemounting enables high performance and is a requirement for disaster recoverybackups.

PureDisk’s disaster recovery backup or restore script examplesThe PureDisk installation software includes example backup scripts and examplerestore scripts. You do not need to modify them for use at your site.

However if you want to modify the scripts, examine the comments in the scriptfiles. The comments explain how to modify each one. The example scripts residein the following directory:

/opt/pdconfigure/scripts/support/DR_BackupSampleScripts/

Disaster recovery backup proceduresAbout backing up your PureDisk environment using scripts

114

Table 5-1 lists the scripts that are located in this directory and describes theirfunctions.

Table 5-1 Script examples

Script functionScript name

Performs a full backup of PureDisk environmentdata.

full_DR_backup.sh

Performs an incremental backup of PureDiskenvironment data.

incremental_DR_backup.sh

Restores data about the PureDisk environmentthat was saved to a Samba share or was saved bya third-party product.

For more information about how to restore anunclustered PureDisk environment, see thefollowing:

See “About restoring an unclustered PureDiskenvironment” on page 121.

For more information about how to restore aclustered PureDisk environment, see thefollowing:

See “About restoring a clustered PureDiskenvironment” on page 157.

DRrestore.sh

If you modify the scripts that PureDisk provides, the scripts are not protected.During a restore procedure, PureDisk overwrites the scripts if they remain in thedefault installation directory (/opt). You must place them in another directoryfor protection (for example, in /usr or /tmp).

Creating a backup scriptA disaster recovery backup script can back up the files directly, or it can run athird-party backup tool. The following procedure explains how to create a disasterrecovery script to back up the spool, new, and changed data on the content routers.

If you create your own scripts, the scripts are not protected. During a restoreprocedure, PureDisk overwrites the scripts if they remain in the default installationdirectory (/opt). You must place them in another directory for protection (forexample, in /usr or /tmp).

115Disaster recovery backup proceduresAbout backing up your PureDisk environment using scripts

To create a backup script

1 Use a text editor to create a backup script that backs up the data directly orcalls a backup product.

The backup script must perform the actual backup of the data. When youcreate the script, include the following options:

Used for an incremental backup.

Specifies that you want to back up the newcontainer directories that were created since thelast disaster recovery backup was performed.

--new listfile

Used for an incremental backup.

Specifies that you want to back up the containerdirectories that have changed since the lastdisaster recovery backup ran.

--changed listfile

Used for a full backup.

Specifies that you want to back up all containerdirectories.

--full listfile

The spool area on a content router is a bufferarea. It holds file data until PureDisk writes thedata to the content router.

--spool spool_files

Specifies the node which is to be backed up. Eachnode that runs this script supplies its own agentidentifier.

--agentid agent_id

Do not create actual files for listfile or spool_files. The disaster recoveryworkflow creates these files and provides them to the script.

If you run an incremental backup, and no full backup exists, PureDiskperforms a full backup.

The disaster recovery backup policy calls the script and runs it each timewith a different option, in the following order:

Backs up newly created container directories--new

Backs up the existing container directories thathave changed

--changed

Backs up both the new container directories andthe existing container directories that havechanged

--full

Disaster recovery backup proceduresAbout backing up your PureDisk environment using scripts

116

Backs up any files in the content router’s spoolarea

--spool

Specifies the agent identification of the nodethat is being backed up

--agentid

2 Copy the script you created to every content router in your environment.

Write this script to the same location on each content router. For example,/opt/external_scripts.

3 Copy the scripts to a backup directory for protection.

PureDisk overwrites the scripts during a restore, so write a copy to /usr or/tmp.

Troubleshooting a disaster recovery backupThe following describe how to troubleshoot failed disaster recovery backups:

■ See “Missing pdkeyutil file” on page 117.

■ See “Content router modes set incorrectly” on page 118.

Missing pdkeyutil fileThe pdkeyutil command enables encrypted disaster recovery backups to a localfile system or to a Samba shared file system.

One possible reason for disaster recovery backup job failure is the absence of apdkeyutil file. The installation procedure includes a step to enable this utility.If your backup failed, it might be because you did not enable this utility atinstallation time.

If your backup fails to run, examine the job details. To examine the job details,click Monitor > Jobs. In the right pane, click the Job Id number on the row thatincludes the disaster recovery backup workflow job.

If the pdkeyutil file does not exist, the following message appears in the Job logtab:

open(/Storage/var/keys/DR.key, ...) failed; No such file or directory (2)

To enable the pdkeyutil command, enter the following command on all activenodes:

117Disaster recovery backup proceduresTroubleshooting a disaster recovery backup

# /opt/pdag/bin/pdkeyutil -insert

The preceding command initiates a dialog session with the pdkeyutil utility. Theutility prompts you to specify a password for the encryption utility to use duringdisaster recovery backups and restores.

Remember the password that you type. You need this password to restore PureDiskstorage pool authority configuration files in the event of a disaster.

If you do not remember this password, you cannot complete the restore.

When you perform a restore, make sure to use the password that was in effectwhen your disaster recovery backup ran. If you have changed the password, ensurethat the password you specify is the same password that was used when thedisaster recovery backup ran.

To determine if the key is enabled, enter the following command:

# /opt/pdag/bin/pdkeyutil -display

This command displays the following if the key is enabled:

Key File version: 0

Key count: 1

1. Key creation date: 2006-08-29 (current key)

Key: 1bdd79b5dee3f6a80679893236e9194c

This command displays the following if no key is enabled:

Key File version: 0

Key count: 0

Content router modes set incorrectlyAfter a failed disaster recovery backup, the disaster recovery backup workflowattempts to reset the content router modes back to normal. However, dependingon the nature of the failure, these attempts can be unsuccessful.

After a failed disaster recovery backup, perform the following procedure.

To reset content router modes

1 Log into one of the content router nodes as root.

2 Type the following command:

# /opt/pdcr/bin/crcontrol --getmode

Disaster recovery backup proceduresTroubleshooting a disaster recovery backup

118

3 Examine the crcontrol command's output.

If the modes are set correctly, the output indicates that all modes =YES exceptfor REROUTE mode, which should be set to =NO.

The following output indicates that the modes are set correctly:

Mode : GET=Yes PUT=Yes DEREF=Yes SYSTEM=Yes STORAGED=Yes REROUTE=No

If the crcontrol command output for your content router is not set correctly,type the following command to set one or more modes manually:

# /opt/pdcr/bin/crcontrol -mode mode=Yes

For mode, type one of the following: GET, PUT, DEREF, SYSTEM, or STORAGED.

For example, if DEREF=Hold in your output, type the following command:

# /opt/pdcr/bin/crcontrol -mode DEREF=Yes

Do this for each mode that is not correctly set.

4 Repeat this procedure for each content router node in your storage pool.

119Disaster recovery backup proceduresTroubleshooting a disaster recovery backup

Disaster recovery backup proceduresTroubleshooting a disaster recovery backup

120

Disaster recovery forunclustered storage pools


■ About restoring an unclustered PureDisk environment

■ Reinstalling required software (unclustered recovery)

■ Performing a disaster recovery of an unclustered PureDisk storage pool froma NetBackup disaster recovery backup (NetBackup, unclustered recovery)

■ Performing a disaster recovery from a Samba backup (Samba, unclusteredrecovery)

■ Performing a disaster recovery from a third-party product backup (third-party,unclustered recovery)

About restoringanunclusteredPureDisk environmentPerform the procedures in this chapter when other methods to recover data havefailed. No matter how frequently you have performed disaster recovery backups,data loss is possible with any restore procedure. The following introductoryinformation introduces the PureDisk procedures that explain how to restore anunclustered PureDisk environment:

■ See “When to restore your environment” on page 122.

■ See “Restore overview for an unclustered storage pool” on page 122.

For information about how to perform disaster recovery backups and how tocreate PureDisk disaster recovery backup policies, see the following:


6Chapter

■ See “Configuring PureDisk disaster recovery backup policies” on page 106.

When to restore your environmentRestore your PureDisk environment when one or more of the following conditionsare present:

■ Other methods to restore an unclustered storage pool have failed.

■ One or more of your PureDisk nodes is down. That is, the hardware does notfunction and cannot be repaired.

■ Disks have crashed.

■ One or more of the databases appears to be corrupted.To determine their state, examine the log file in the following file:

/Storage/log/pddb/postgresql.log

Possible signs of a corrupted database are messages such as the following inthe log file:

FATAL: could not open file

"/Storage/databases/pddb/data/global/1262": No such file or

directory

LOG: could not open temporary statistics file

"/Storage/databases/pddb/data/global/pgstat.tmp.4391": No such

file or directory

Restore overview for an unclustered storage poolRegardless of the method you used to perform the disaster recovery backup, youcan use the DR_Restore_all.sh script to perform restores.

The PureDisk initiates the disaster recovery restore procedure when you type thefollowing command on the storage pool authority:

/opt/pdinstall/DR_Restore_all.sh

The DR_Restore_all.sh script performs the following actions:

■ Prompts for all of the information that is required to restore an entire storagepool.

■ Restores the data that was backed up.

Disaster recovery for unclustered storage poolsAbout restoring an unclustered PureDisk environment

122

■ Optimizes the content router restore. This action occurs when the disasteraffected only a subset of the content routers.The DR_Restore_all.sh script fully restores the /Storage/data directory ofall failed content router nodes.If the configuration includes any content routers that do not need to be fullyrecovered because no disaster occurred, the script performs minimal restores.The restores bring the content routers to a state that is consistent with thepoint in time of the last disaster recovery backup. Since the last backup wasdone, some data segments might have been removed or added.In these cases, the script does the following:

■ Restores all databases and configuration files.

■ Restores the segment containers so that they are consistent with the contentrouter databases.

■ Restores all segment containers that a removal job has changed or deletedsince last the backup.

To perform a disaster recovery of an unclustered storage pool

1 Reinstall the software on your storage pool.

Perform the following procedure:

■ See “Reinstalling required software (unclustered recovery)” on page 123.

2 Perform one of the following procedures, depending on the way you backedup your PureDisk environment.

■ See “Performing a disaster recovery of an unclustered PureDisk storagepool from a NetBackup disaster recovery backup (NetBackup, unclusteredrecovery)” on page 133.

■ See “Performing a disaster recovery from a Samba backup (Samba,unclustered recovery)” on page 138.

■ See “Performing a disaster recovery from a third-party product backup(third-party, unclustered recovery)” on page 147.

Reinstalling required software (unclustered recovery)Complete the following procedure to reinstall the software on the nodes thatfailed. For example, if a content router failed, install PDOS on that content routeronly.

123Disaster recovery for unclustered storage poolsReinstalling required software (unclustered recovery)

To reinstall the software

1 Install PDOS on the nodes that failed.


See “Reinstalling PDOS” on page 124.

2 Reconfigure your storage partitions.

Perform one of the following procedures:

■ See “(Conditional) Reconfiguring the storage partitions on DAS/SAN disks”on page 125.

■ See “(Conditional) Reconfiguring the storage partitions on iSCSI disks”on page 129.

3 Complete the software reinstallation.


See “Completing the software reinstallation” on page 132.

Reinstalling PDOSFor each node that failed, install PDOS and any PDOS updates you installed ontothe PDOS base release. The following procedure explains how to reinstall PDOS.

To reinstall PDOS on the nodes that failed

1 Install PDOS on each failed node.

Use the installation instructions in the PureDisk Storage Pool InstallationGuide.

2 (Conditional) Install PDOS updates on each failed node.

Perform this step if you installed any PDOS updates on the nodes before thedisaster.

Use the installation instructions in the update README file.

3 (Conditional) Perform intermediate installation tasks.

Perform this step if the node has special requirements. For example, if youneed to disable multipathing or if you need to configure iSCSI disks for thisnode, perform the additional steps in the chapter called 'Preparing to configurethe storage pool' in the PureDisk Storage Pool Configuration Guide.

4 Proceed to one of the following, depending on the disks attached to this node:

■ See “(Conditional) Reconfiguring the storage partitions on DAS/SAN disks”on page 125.

Disaster recovery for unclustered storage poolsReinstalling required software (unclustered recovery)

124

■ See “(Conditional) Reconfiguring the storage partitions on iSCSI disks”on page 129.

(Conditional) Reconfiguring the storage partitions on DAS/SAN disksPerform this procedure is your node uses DAS/SAN disks.

The following overview procedure explains how to configure the storage partitions.

To specify the storage partitions

1 Create disk groups.

See “Creating disk groups (DAS/SAN disks)” on page 125.

2 Configure the /Storage partition.

See “Configuring the /Storage partition (DAS/SAN disks)” on page 126.

3 (Optional) Configure the /Storage/data and /Storage/databases partition.

See “(Optional) Configuring the /Storage/data and the /Storage/databasespartition (DAS/SAN disks)” on page 127.

4 Complete the storage configuration.

See “Completing the storage configuration (DAS/SAN disks)” on page 128.

Creating disk groups (DAS/SAN disks)The following procedure explains how to start YaST and create disk groups.

To create disk groups

1 Type the following command to launch the SUSE Linux YaST configurationtool:

# yast

Type yast or YaST to start the interface. Do not type other combinations ofuppercase and lowercase letters.

2 In the YaST Control Center main page, select System > Partitioner.

3 Select Yes on the warning pop-up.

4 On the Expert Partitioner page, select VxVM.

5 On the CreateaDiskGroup pop-up, type your site-specific name for the diskgroup or accept the default.

6 Click OK.


7 On the Veritas Volume Manager: Disks Setup page, select a disk that youwant to include in the disk group.

8 Select Add Disk and press Return.

You can only add disks that are not yet partitioned. If you try to add a diskwith partitions, adding the disk to the disk group does not succeed. Delete allpartitions from the disk before you try to add partitions.

To delete all partitions on a disk, select Expert in the YaST interface andselect Delete Partition Table and Disk Label.

9 Repeat the following steps for all the disks that you want to include in thedisk group:

■ Step 7

■ Step 8

10 Click Next.


See “Configuring the /Storage partition (DAS/SAN disks)” on page 126.

Configuring the /Storage partition (DAS/SAN disks)The following procedure explains how to configure the /Storage partition.

To configure the /Storage partition

1 On the Veritas Volume Manager: Volumes page, click Add.

The Create Volume pop-up appears.

2 Decide whether you can create a VxFS file system or whether you need tocreate an XFS file system .

A VxFS file system is the recommended default. However, you might need toconfigure an XFS file system if VxFS does not support your disks. Proceed asfollows:

■ If your disks support VxFS, proceed to the next step to specify a volumename.

■ If your disks do not support VxFS, in the File System field, select XFSfrom the drop-down list.

3 In the Volume Name field, specify a name. For example, Storage.

4 In the Mount Point field, type /Storage. You must type this name becauseit is not in the drop-down list.

5 Click OK.


126

6 Click Next.


■ If you want to configure a /Storage/data or a /Storage/databases

partition to enhance performance, proceed to the following:See “(Optional) Configuring the /Storage/data and the /Storage/databasespartition (DAS/SAN disks)” on page 127.

Note: In a multinode storage pool, make sure to specify the samepartitioning scheme on each node.

■ If you do not want to configure additional partitions, proceed to thefollowing:See “Completing the storage configuration (DAS/SAN disks)” on page 128.

(Optional) Configuring the /Storage/data and the/Storage/databases partition (DAS/SAN disks)Perform the following procedure if you want to configure a /Storage/data anda /Storage/databases partition. Symantec does not require that you configurethese additional partitions, but these additional partitions can increase storagepool performance.

If you configure these additional partitions, configure them in one of the followingways:

■ Configure /Storage/data.

or

■ Configure /Storage/data and /Storage/databases.

To configure a /Storage/data and a /Storage/databases partition

1 Specify a partition for /Storage/data.

Perform the following steps:

■ On the Veritas Volume Manager: Volumes page, click Add.The Create Volume pop-up appears.

■ (Conditional) In the File System field, select XFS from the drop-down listif VxFS does not support your disk types. Make sure that you specify thesame file system for all storage partitions.

■ In the Volume Name field, specify Storage_data.

■ In the Size field, specify the size for this partition.


For more information, see the PureDisk Storage Pool Installation Guide.

■ In the Mount Point field, type /Storage/data. You must type this namebecause it is not in the drop-down list.

■ Click OK.

2 Specify a partition for /Storage/databases.


■ On the Veritas Volume Manager: Volumes page, click Add.The Create Volume pop-up appears.

■ (Conditional) In the File System field, select XFS from the drop-down listif VxFS does not support your disk types. Make sure that you specify thesame file system for all storage partitions.

■ In the Volume Name field, specify Storage_databases.

■ In the Size field, specify the size for this partition.For more information, see the PureDisk Storage Pool Installation Guide.

■ In the Mount Point field, type /Storage/databases. You must type thisname because it is not in the drop-down list.

■ Click OK.

3 Click Next.


See “Completing the storage configuration (DAS/SAN disks)” on page 128.

Completing the storage configuration (DAS/SAN disks)The following procedure explains how to finish the storage configuration.

To complete the storage configuration

1 On the Expert Partitioner page, inspect the information displayed.

Press the right-arrow key to display the Mount column. Make sure that theMount column is correct. If it is not, quit YaST and attempt the storageconfiguration again.

2 Click the icon in the lower right-hand corner.

Depending on the installation option that you used, this icon is either Applyor Finish.

3 On the Changes pop-up that appears, click Apply.


128

4 Select Finish.

5 Select Quit.

(Conditional) Reconfiguring the storage partitions on iSCSI disksPerform this procedure if your node uses iSCSI disks.

The following overview procedure explains how to configure the storage partitions.

To specify the storage partitions

1 Create disk groups.

See the following:

See “Creating disk groups (iSCSI disks)” on page 129.

2 Configure the /Storage partition.

See the following:

See “Configuring the /Storage partition (iSCSI disks)” on page 130.

3 (Optional) Configure the /Storage/data and /Storage/databasespartition.

See the following:

See “(Optional) Configuring the /Storage/data and the /Storage/databasespartitions (iSCSI disks)” on page 131.

4 Complete the storage configuration.

See the following:

See “Completing the storage configuration (iSCSI disks)” on page 132.

Creating disk groups (iSCSI disks)The following procedure explains how to start YaST and how to create disk groups.

To create disk groups

1 (Conditional) Type the following command to launch the SUSE Linux YaSTconfiguration tool:

# yast

Perform this step as needed.

Type yast or YaST to start the interface. Do not type other combinations ofuppercase and lowercase letters.

2 In the YaSTControlCenter main page, select System>Partitioner and pressEnter.



4 On the Expert Partitioner page, select LVM and press Enter.

5 On the Create a Volume Group pop-up, type your volume group name forthe disk group or accept the default.

6 Select OK and press Enter.

7 On the LogicalVolumeManager: PhysicalVolumeSetup page, select a diskthat you want to include in the disk group.

8 Select Add Volume and press Enter.


■ Step 7

■ Step 8

10 Select Next.


See “Configuring the /Storage partition (iSCSI disks)” on page 130.

Configuring the /Storage partition (iSCSI disks)The following procedure explains how to configure the /Storage partition.

To configure the /Storage partition

1 On the Logical Volume Manager: Logical Volumes page, select Add.

The Create Logical Volume pop-up appears.

2 In the File System field, select XFS from the drop-down list.

3 In the Logical Volume Name field, specify a name.

For example, Storage.

4 In the Size field, specify the size for this partition.

For information about how to configure the size for a partition, see thePureDisk Storage Pool Installation Guide.

5 In the Mount Point field, type /Storage.

You must type this name because it is not in the drop-down list.

6 Select OK and press Enter.

7 Select Next.

8 Proceed to one of the following:


130

■ If you want to configure the /Storage/data partition and the/Storage/databases partition, proceed to the following:

See “(Optional) Configuring the /Storage/data and the /Storage/databasespartitions (iSCSI disks)” on page 131.

■ If you do not want to configure the /Storage/data partition and the/Storage/databases partition, select Next, press Enter, and proceed tothe following:See “Completing the storage configuration (iSCSI disks)” on page 132.

(Optional) Configuring the /Storage/data and the/Storage/databases partitions (iSCSI disks)Perform the following procedure if you want to configure a /Storage/data anda /Storage/databases partition. Symantec does not require that you configurethese additional partitions, but these additional partitions can increase storagepool performance.

If you configure these additional partitions, create them in one of the followingways:

■ Create /Storage/data

or

■ Create both /Storage/data and /Storage/databases

To configure a /Storage/data and a /Storage/databases partition

1 Specify a partition for /Storage/data.

Perform the following steps to create a high-performance /Storage/data

partition:

■ On the Logical Volume Manager: Logical Volumes page, select Add.The Create Volume pop-up appears.

■ In the File System field, select XFS from the drop-down list.

■ In the Logical Volume Name field, specify Storage_data.

■ In the Size field, specify the size for this partition.For information about how to configure the size for a partition, see thePureDisk Storage Pool Installation Guide.

■ In the Mount Point field, type /Storage/data.


■ Select OK.

2 Specify a partition for /Storage/databases.


Perform the following steps to create a high-performance/Storage/databases partition:

■ On the Logical Volume Manager: Logical Volumes page, select Add.The Create Volume pop-up appears.

■ In the File System field, select XFS from the drop-down list.

■ In the Logical Volume Name field, specify Storage_databases.

■ In the Size field, specify the size for this partition.For information about how to configure the size for a partition, see thePureDisk Storage Pool Installation Guide.

■ In the Mount Point field, type /Storage/databases.


■ Select OK.

3 Select Next.


See “Completing the storage configuration (iSCSI disks)” on page 132.

Completing the storage configuration (iSCSI disks)The following procedure explains how to finish the storage configuration.

To complete the storage configuration

1 On the Expert Partitioner page, inspect the information displayed.

Press the right-arrow key to display the Mount column. Make sure that theMount column is correct. If it is not, quit YaST and attempt the storageconfiguration again.

2 Select Apply and press Enter.

3 On the Changes pop-up that appears, select Finish and press Enter.

4 Select Quit and press Enter.

Completing the software reinstallationThe following procedure explains how to complete the process of reinstalling yoursoftware on the failed nodes.


132

To complete the software reinstallation

1 (Conditional) Log in as root to the node that hosts the storage pool authorityservice and install the latest DR_Restore_all.sh script.

Perform this step if you added PureDisk application patches or updates toyour storage pool before the disaster.


# tar -C / -xf upgrade_tar_file ./opt/pdinstall/lib/DRRestoreAll.php

For upgrade_tar_file, specify the full path to the location of the latest updateor patch that your PureDisk environment was running. For example:

# tar -C / -xf /root/NB_PDE_6.6.1.17350.tar ./opt/pdistall/lib/DRRestoreAll.php

2 (Conditional) Install the NetBackup client software on all nodes that failed.

Perform this step if you write your disaster recovery backups to a NetBackupenvironment.


■ See “Performing a disaster recovery of an unclustered PureDisk storagepool from a NetBackup disaster recovery backup (NetBackup, unclusteredrecovery)” on page 133.

■ See “Performing a disaster recovery from a Samba backup (Samba,unclustered recovery)” on page 138.

■ See “Performing a disaster recovery from a third-party product backup(third-party, unclustered recovery)” on page 147.

Performing a disaster recovery of an unclusteredPureDisk storage pool from a NetBackup disasterrecovery backup (NetBackup, unclustered recovery)

The following procedure explains how to recover an unclustered PureDisk storagepool that was backed with NetBackup.

133Disaster recovery for unclustered storage poolsPerforming a disaster recovery of an unclustered PureDisk storage pool from a NetBackup disaster recovery backup

(NetBackup, unclustered recovery)

To perform a disaster recovery from a NetBackup disaster recovery backup

1 (Conditional) Clean up after a failed full disaster recovery backup.

See “(Conditional) Cleaning up after a failed full disaster recovery backup(NetBackup, unclustered recovery)” on page 134.

2 Use the DR_Restore_all script.

See “Using the DR_Restore_all script (NetBackup, unclustered recovery)”on page 134.

(Conditional) Cleaning up after a failed full disaster recovery backup(NetBackup, unclustered recovery)

Perform this procedure only if a previous full disaster recovery backup failed.

To expire the backup images from failed backups

◆ From the NetBackup interface, manually expire any NetBackup images thatare newer than the date of the last successful backup.

Symantec highly recommends that you purge any corrupted backup imagesfrom any unsuccessful backups before you try the restore. You can searchthe catalog and use the PureDisk server as the client name. Look for theimages that have the Standard and DataStore disaster recovery policies.

For information about how to search the catalog for images, see theNetBackupAdministrator’s Guide, Volume I.

Using the DR_Restore_all script (NetBackup, unclustered recovery)The DR_Restore_all script initiates a dialog with you. Answer the questions thatthe script displays.

To use the DR_Restore_all script

1 Make sure that all storage partitions are mounted.

For example, use the following mount(8) command to verify the mounts:

# mount | grep Storage

2 Run the disaster recovery script from the storage pool authority node.

From the PDOS command line, type the following command:

# /opt/pdinstall/DR_Restore_all.sh

Disaster recovery for unclustered storage poolsPerforming a disaster recovery of an unclustered PureDisk storage pool from a NetBackup disaster recovery backup(NetBackup, unclustered recovery)

134

3 Specify the method you used to back up PureDisk.

For example:

Please choose the method you used to do the Disaster Recovery

Backup

1. NetBackup

2. Samba Share

3. Local Directory

Backup Method (1|2|3): 1

4 Affirm whether you installed the NetBackup client on the node.

If you answer no, the script stops and you must restart the script after youinstall the NetBackup client software.

For example:

Is the NetBackup client installed on all nodes and pointing to

the NBU Server that was used to do the backups? [Yn]: y

5 Provide the full path of any upgrade patch files that need to be applied.

Please provide the location of the upgrade patch tar file.

For multiple patches, enter in the order they should be applied.

(leave blank for none) :

For example:

/root/NB_PDE_6.5.1.17630.tar

Leave blank and press Enter if there are no patches to apply.

To apply multiple upgrade patches, provide the latest that can be installedon top of the base version. Otherwise, provide the patch locations in the orderthe patches should be applied. This situation is applicable to EEBs.

Next, respond to the following prompt:

Are there any more patches that need to be applied? (Yn) :

Answer yes (y) to apply additional patches. Answer no (n) to continue withthe disaster recovery process.

6 Respond to the prompts regarding the topology file.

Directory /Storage/etc must contain the following files:



■ topology.ini or topology.ini.enc

■ topology_nodes.ini

If these files are not present, the script retrieves them. If topology.ini.encis present, the script issues the following prompt for the password:

topology.ini file needs to be decrypted before proceeding

enter aes-256-cbc decryption password:

Type the password that you use for the storage pool configuration wizard.

7 Examine the topology information the script displays and specify the nodesyou want to restore.

The script reads the topology file and presents a display like the followingexample:

STORAGE POOL TOPOLOGY

Node IP Address Services

---- ---------- ---------

1 10.80.62.1 spa mbe mbs cr nbu

2 10.80.62.2 cr

Node number(s): 1

The preceding example shows the topology that the script can restore in thisdisaster recovery operation. Examine this information for accuracy andspecify the node numbers that you want to restore. If you want to restoremore than one node, use commas to separate the node numbers.

If a node did not fail and you want to preserve the data on that node, do notspecify that node number. The restore procedure completely reinstalls thewhole topology. However, for the nodes that did not fail, the script hideseverything in /Storage by unmounting the mount points before it removesthe data.

After the reinstall is complete, the script performs the following actions:

■ Remounts those mount points

■ Restores all the data on the failed nodes

■ Restores all the databases on all the nodes

■ Restores any removed data. A data removal job might have been run sincethe last time the databases were backed up. For this reason, the script alsorestores the removed data on the nodes that did not fail. This actionsynchronizes the databases and data.

Disaster recovery for unclustered storage poolsPerforming a disaster recovery of an unclustered PureDisk storage pool from a NetBackup disaster recovery backup(NetBackup, unclustered recovery)

136

8 Respond to queries from the script regarding passwords.

The restore process can take hours to complete. As the script runs, you mightbe asked to specify the system passwords for the remote (or local) nodes. Thisprompt occurs early in the process during secure shell (SSH) authentication.

9 (Conditional) Respond to the queries that are displayed by the upgradepatches.

Refer to the README files that came with the upgrade patches for specificdetails about the queries.

Respond no to creating jobs for upgrading agents.

At the end of the upgrade installation, the script prompts you to encrypt thetopology.ini file. Answer no at this time to continue. You will have a chanceto encrypt the topology.ini file at the end of the disaster recovery process.

10 When the restore is complete, answer the prompts about encryption of thetopology.ini file.

For example:

Would you like to encrypt the topology.ini file? [Yn]:y

Encrypting /opt/pdinstall/topology.ini

enter aes-256-cbc encryption password: xxxx

Verifying - enter aes-256-cbc encryption password:


11 Observe the completion message.

When the operation completes successfully, the script displays the followingmessage:

Disaster recovery complete

12 (Conditional) Run the following script on the storage pool authority node toupgrade the security protocol:

# /opt/pdinstall/disable_sslv2.sh

Perform this step if you ran the disable_sslv2.sh script on this storage poolat any time. The disaster recovery restore does not enable this scriptautomatically.

Symantec recommends that you run the script unless PureDisk 6.5.x storagepools need to replicate to this storage pool.



13 Perform a full disaster recovery backup.

Make sure you perform a full disaster recovery backup before you performany file backups or perform any incremental disaster recovery backups.

14 (Conditional) Re-enable the NetBackup export engine on any nodes that hostedonly a NetBackup export engine service.

Perform this step only if you have a node that hosted only a NetBackup exportengine service.

For information about how to enable a NetBackup export engine, see thefollowing:

See “About exporting data to NetBackup” on page 73.

Performing a disaster recovery fromaSambabackup(Samba, unclustered recovery)

The following procedure explains how to recover an unclustered PureDisk storagepool that was backed up to a Samba backup.

To perform a disaster recovery from a Samba backup

1 (Conditional) Recreate your topology information.

See “(Conditional) Recreate your topology information (Samba, unclusteredrecovery)” on page 138.

2 (Conditional) Remove corrupted files from an incomplete backup.

See “(Conditional) Removing corrupted files from an incomplete backup(Samba, unclustered recovery)” on page 140.

3 (Conditional) Prepare the storage pool authority node for disaster recovery.

See “(Conditional) Preparing the storage pool authority node for disasterrecovery (Samba, unclustered recovery)” on page 141.

4 Use the DR_Restore_all script.

See “Using the DR_Restore_all script (Samba, unclustered recovery)”on page 141.

(Conditional) Recreate your topology information (Samba, unclusteredrecovery)

Perform one of the procedures in this section if you enabled encryption for yourdisaster recovery backups.

Disaster recovery for unclustered storage poolsPerforming a disaster recovery from a Samba backup (Samba, unclustered recovery)

138

You need your storage pool's topology information in order to perform the restore.Perform one of the following procedures:

■ See “(Conditional) Recreating the topology with current topology information(Samba, unclustered recovery)” on page 139.

■ See “(Conditional) Recreating the topology without current topologyinformation (Samba, unclustered recovery)” on page 139.

(Conditional) Recreating the topology with current topologyinformation (Samba, unclustered recovery)Perform the following procedure if all of the following conditions are true:

■ You enabled encryption in the PureDisk disaster recovery backup policy.

■ You have a backup copy of this storage pool’s topology and you can recreateit.

To recreate the topology when you have the storage pool’s topology information

◆ Enter the following command and follow the prompts to recreate this storagepool’s topology:

# /opt/pdinstall/edit_topology.sh

Your goal is to recreate the PureDisk topology so that it matches the topologythat existed before the disaster.

For information about the storage pool’s topology and node identificationinformation, see the worksheets that you completed during this storage pool’sinstallation.

(Conditional) Recreating the topologywithout current topologyinformation (Samba, unclustered recovery)Perform the following procedure if all of the following conditions are true:


■ You do not have a backup copy of this storage pool’s topology.

139Disaster recovery for unclustered storage poolsPerforming a disaster recovery from a Samba backup (Samba, unclustered recovery)

To recreate the topology without current topology information

1 Enter the following command and follow the prompts to recreate this storagepool’s topology:


Include only the storage pool authority in the topology.

Note: Make sure you enter the correct storage pool ID. Make sure that allpasswords you use during the disaster recovery process are the same as thosethat existed before the disaster occurred.

2 Enter the following command to install the new storage pool:

# /opt/pdinstall/install_newStoragePool.sh

3 Remove the following files:

/Storage/etc/topology.ini

/Storage/etc/topology_nodes.ini

The preceding files are not needed at this time. The disaster recovery scriptrestores these files from the backup.

(Conditional) Removing corrupted files from an incomplete backup(Samba, unclustered recovery)

Perform this procedure only if a previous full disaster recovery backup failed.

The PureDisk disaster recovery full backup scripts create a previous directoryat the root level of the share that contains the previous backup data. PureDiskcreates this directory at the start of the full backup and removes it at the end ofa successful backup.

If the backup fails, the previous directory still exists on the share. If this directoryexists at the start of another backup run, PureDisk preserves the contents. Itdeletes the current backup data (from the failed backup) before it starts the newbackup. PureDisk removes the previous directory only when a new full backupis successful.

If you need to do a disaster restore and the previous directory exists, move thecontents of this directory to the share’s root level. Then remove the previous

directory. The contents currently under the share are from a failed disasterrecovery backup because the previous directory exists.


140

To remove corrupted files from an incomplete backup

1 Search for a directory that is called previous in the root level of the share.The directory contains the previous backup data.

2 Move the contents of the previous directory to the root level of the share.

3 Remove the directory called previous.

(Conditional) Preparing the storage pool authority node for disasterrecovery (Samba, unclustered recovery)

Perform this procedure if the following statements are true:

■ You are NOT restoring the storage pool authority node of your PureDiskenvironment.

■ The PureDisk version you are restoring requires upgrade patches.

To prepare the storage pool authority node for disaster recovery

1 Log on to the storage pool authority node.

2 Change to the /opt/pdconfigure/var/nodesoftware directory.

3 Remove all files in this directory with the name patch-*.tgz.

You should now only have one file left with the namepuredisk-base_version.tgz, wherebase_version is the base version of yourPureDisk environment. If you were running 6.6.X.X, the file would bepuredisk-6.6.0.10534.tgz.

Using the DR_Restore_all script (Samba, unclustered recovery)The DR_Restore_all script initiates a dialog with you. You need to answer thequestions that the script displays.










For example:


Backup

1. NetBackup

2. Samba Share

3. Local Directory


4 Provide the information that PureDisk needs to mount the shared file system.

For example:

Please enter remote samba share (i.e.

//11.88.77.33/remoteSambaShare):

//rmns1.min.boston.com/PD_DRdata

5 Provide information about the local mount point.

The local mount point is the path name of a directory on which to mount theshare. If you used the DR_Restore_all script in the default PureDisk location,the mount point must be /DRdata.

Please enter local mount point (default: /DRdata):

If appropriate, press Enter to accept the default.

6 Provide authentication information.

This information includes the user name, password, and work group for theSamba share on the remote file server.

For example:

Please enter samba user name: pduser

Please enter samba password: pdpwd

Please enter samba workgroup: pdwgroup

Please enter location to restore CR data and spool area from

(default: /DRdata):


142

7 Type the full system path name to the disaster recovery script used to saveyour PureDisk data.

If you used the DR_Restore_all script in the default PureDisk location, pressreturn.

If you supplied your own restore script, PureDisk does not protect it. Thescripts are overwritten during a restore procedure if they remain in the defaultinstallation directory (/opt). You must write them to another directory forprotection (for example, in /usr or /tmp).

For example:

Please enter full path of customized DR restore script (default:

/opt/pdconfigure/scripts/support/DR_BackupSampleScripts/DRresto

re.sh):

8 Respond to the prompts regarding encryption.

If you used a pdkeyutil password to enable encryption of your disasterrecovery data during backup, supply the password that you specified.

If you did not use pdkeyutil, type no; the script does not ask you for apassword.

For example:

Was encryption used to do the Disaster Recovery Backup [Yn]: y

Please provide the pdkeyutil pass phrase: *******






For example:







10 Type the storage pool ID for the storage pool that you want to restore.

This ID is the value specified for the storagepoolid property in thetopology.ini file. This value is used to retrieve the topology file.

For example:

Please enter Storage Pool ID:












144



---- ---------- ---------


2 10.80.62.2 cr

Node number(s): 1







■ Restores the removed data. A data removal job might have been run sincethe last time the databases were backed up. For this reason, the script alsorestores the removed data on the nodes that did not fail. This methodsynchronizes the databases and data.


The restore process can take hours to complete. As the process runs, youmight be asked to specify the system passwords for the remote (or local)nodes. This prompt occurs early in the process during SSH authentication.

14 (Conditional) Respond to queries that are displayed by the upgrade patches.



At the end of the upgrade installation, the script prompts you to encrypt thetopology.ini file. Answer no at this time to continue. You have anotherchance to encrypt the topology.ini file at the end of the disaster recoveryprocess.



For example:




















146

Performing a disaster recovery from a third-partyproduct backup (third-party, unclustered recovery)

The following procedure explains how to recover an unclustered PureDisk storagepool that was backed up to a third-party product.

To perform a disaster recovery from a third-party product

1 (Conditional) Recreate your topology information.

See “(Conditional) Recreate your topology information (third-party,unclustered recovery)” on page 147.

2 (Conditional) Remove corrupted files from an incomplete full disaster recoverybackup.

See “(Conditional) Removing corrupted files from an incomplete full disasterrecovery backup (third-party, unclustered recovery)” on page 149.

3 (Conditional) Prepare the storage pool authority node for disaster recovery.

See “(Conditional) Preparing the storage pool authority node for disasterrecovery (third-party, unclustered recovery)” on page 150.

4 Run the DR_Restore_all script.

See “Using the DR_Restore_all script (third-party, unclustered recovery)”on page 150.

(Conditional) Recreate your topology information (third-party,unclustered recovery)

Perform one of the following procedures if you enabled encryption for your disasterrecovery backups.


■ See “(Conditional) Recreating the topology with current topology information(third-party, unclustered recovery)” on page 147.

■ See “(Conditional) Recreating the topology without current topologyinformation (third-party, unclustered recovery)” on page 148.

(Conditional) Recreating the topology with current topologyinformation (third-party, unclustered recovery)Perform the following procedure if all of the following conditions are true:


147Disaster recovery for unclustered storage poolsPerforming a disaster recovery from a third-party product backup (third-party, unclustered recovery)







(Conditional) Recreating the topologywithout current topologyinformation (third-party, unclustered recovery)Perform the following procedure if all of the following conditions are true:



Disaster recovery for unclustered storage poolsPerforming a disaster recovery from a third-party product backup (third-party, unclustered recovery)

148












(Conditional) Removing corrupted files from an incomplete full disasterrecovery backup (third-party, unclustered recovery)

Symantec recommends that you follow some procedure at your site to ensure thatthe complete contents of a disaster recovery backup are preserved. Thepreservation ensures consistent backup data.

For example, assume that you perform a full disaster recovery backup eachMonday. On the first Monday of the month, the backup runs without problems.On the second Monday of the month, the disaster recovery backup removes thecontents of the first Monday’s backup. However, the second full disaster recoverybackup fails. This failure leaves you without any consistent backup data.

See “(Conditional) Removing corrupted files from an incomplete backup (Samba,unclustered recovery)” on page 140.


To remove corrupted files from an incomplete full disaster recovery backup

1 Examine your backup repository.

2 Locate the last successful backup.

3 Remove any subsequent failed backups from the system.

(Conditional) Preparing the storage pool authority node for disasterrecovery (third-party, unclustered recovery)

Perform this procedure if the following statements are true:

■ You are NOT restoring the storage pool authority node of your PureDiskenvironment.

■ The PureDisk version you are restoring requires upgrade patches.

To prepare the storage pool authority node for disaster recovery


2 Change to the /opt/pdconfigure/var/nodesoftware directory.

3 Remove all files in this directory with the name patch-*.tgz.

You should now only have one file left with the namepuredisk-base_version.tgz, wherebase_version is the base version of yourPureDisk environment. If you were running 6.6.X.X, the file could bepuredisk-6.6.0.10534.tgz.

Using the DR_Restore_all script (third-party, unclustered recovery)The following procedure explains how to use the DR_Restore_all script.









150


For example:


Backup

1. NetBackup

2. Samba Share

3. Local Directory


4 Provide information about where the data to be restored is located.

Press Enter to accept the defaults for the following prompts:

Please enter location to restore metadata from (default:

/DRdata):

Please enter location to restore CR data and spool area from (default:

/DRdata):


If you used the DR_Restore_all script in the default PureDisk location, pressreturn.

If you supplied your own restore script, remember that the scripts are notprotected. The scripts are overwritten during a restore procedure if theyremain in the default installation directory (/opt). To prevent this problem,you must place them in another directory for protection, such as in /usr or/tmp.

For example:



re.sh):











For example:








This name is the value specified for the storagepoolid property in thetopology.ini file. This value is used to retrieve the topology file.

For example:












152




---- ---------- ---------


2 10.80.62.2 cr

Node number(s): 1







■ Restores the removed data. A data removal job might have been run sincethe last time the databases were backed up. In that case, the script alsorestores the removed data on the nodes that did not fail. This methodsynchronizes the databases and data.


The restore process can take hours to complete. As the script runs, you mightbe asked to specify the system passwords for the remote (or local) nodes. Thisprompt occurs early in the process during SSH authentication.





At the end of the upgrade installation, the script prompts you to encrypt thetopology.ini file. Answer no at this time to continue. You have a chance toencrypt the topology.ini file at the end of the disaster recovery process.


For example:














154


156

Disaster recovery forclustered storage pools


■ About restoring a clustered PureDisk environment

■ Recovering from a single-node failover

■ Recovering one active node

■ Recovering from a data storage corruption

■ Recovering from a complete storage pool disaster (clustered, complete storagepool disaster)

■ (Conditional) Cleaning up after a failed full disaster recovery backup

■ (Conditional) Recreate your topology information

■ Running the DR_Restore_all_script to recover the data

About restoring a clustered PureDisk environmentPerform the procedures in this chapter when other methods to recover data havefailed. No matter how frequently you have performed disaster recovery backups,data loss is possible with any restore procedure. When a clustered storage poolexperiences a disaster, determine the type of disaster the storage pool experienced.Clustered storage pool disasters can take on one of the following forms:

■ Single-node failover. In this scenario, only one node has failed. The storagepool is still functioning, but you need to recover the failed node so you can putit back into service.

7Chapter

■ One-node or multiple-node failure. In this scenario, at least one node in acluster has failed, but other nodes in the cluster are still running. In thisscenario, the storage pool has not experienced a complete disaster becausesome active nodes are still running. The disaster recovery procedure explainshow to recover one node. Repeat the procedure on other nodes if more thanone node has failed.

■ Data storage corruption. In this scenario, the shared disks that host /Storage,/Storage/data, and/or /Storage/databases are corrupt.

■ Complete disaster. In this scenario, all or most of the storage pool hasexperienced a disaster such as a computer-room flood or fire. You need torecover multiple nodes.

To perform a disaster recovery of a clustered storage pool

1 Prepare the failed nodes for recovery.

In most cases, no matter what kind of disaster occurred, you need to preparethe nodes before you run the disaster recovery script (DR_Restore_all.sh).Perform one of the following procedures, depending on type of disaster thatoccurred:

■ See “Recovering from a single-node failover” on page 159.

■ See “Recovering one active node” on page 160.

■ See “Recovering from a data storage corruption” on page 166.

■ See “Recovering from a complete storage pool disaster (clustered, completestorage pool disaster)” on page 169.


Perform the following procedure if a previous full disaster recovery backupfailed:

See “(Conditional) Cleaning up after a failed full disaster recovery backup”on page 172.

Disaster recovery for clustered storage poolsAbout restoring a clustered PureDisk environment

158

3 (Conditional) Recreate your topology.

Perform this step if you enable encryption during your disaster recoverybackups and if you backed up your storage pool to a Samba shared file systemor to a third-party product.

See “(Conditional) Recreate your topology information” on page 174.

4 Run the DR_Restore_all.sh script.

The script prompts you to specify information about the storage pool. Thescript's questions differ depending on the disaster recovery backup methodyou used.

See “Running the DR_Restore_all_script to recover the data” on page 175.

For information about how to perform disaster recovery backups and how tocreate PureDisk disaster recovery backup policies, see the following:


■ See “Enabling NetBackup for PureDisk backups” on page 104.

Some of the clustered disaster recovery procedures use PureDisk 6.5.x installationtools. The disaster recovery procedures assume some familiarity with these tools.For more information about these tools, see the PureDisk 6.5.1 version of thefollowing manual:

PureDisk Storage Pool Installation Guide.

Recovering from a single-node failoverThe Veritas Cluster Server (VCS) software ensures that the services on a failingnode migrate smoothly to one of the passive nodes automatically. Such situationsinclude solving node-specific hardware problems, general node maintenance, andso on. Alternately, an administrator can manually transfer services from an activenode to a passive node from the Cluster Manager Java console.

The following procedure explains how to recover the failed node and return it toservice.

159Disaster recovery for clustered storage poolsRecovering from a single-node failover

To recover a failed node

1 Use the following procedure to recover the failed node and return it to serviceas a passive node:

See “Adding a new passive node to a cluster” on page 286.

2 (Conditional) Reinstall the NetBackup client software on all failed nodes.

Perform this step if a NetBackup client was installed on the failed nodes beforethe disaster.

If you back up your storage pool to NetBackup or if you use the NetBackupexport engine, install the NetBackup client on the failed nodes now. Forinformation about how to install a NetBackup client, see your NetBackupdocumentation.

Recovering one active nodeIf you have several nodes in a clustered storage pool, it is possible for only one,two, or several active nodes to fail. In this scenario, at least one node in a clusterhas failed, but the storage pool has not experienced a complete disaster becausesome active nodes are still running. The following procedure explains how torecover a single active node. If more than one active node failed, repeat thisprocedure for each active node that failed.

To recover one active node

1 Reinstall the PDOS software and the VCS software.

See “Reinstalling the PDOS software and the VCS software” on page 160.

2 Recreate the disks and volumes.

See “Recreating disks and volumes” on page 162.


See “Running the DR_Restore_all script” on page 165.

Reinstalling the PDOS software and the VCS softwareThe following procedure explains how to reinstall PDOS and VCS on a failed node.

Disaster recovery for clustered storage poolsRecovering one active node

160

To reinstall PDOS and VCS on one active node

1 Locate this storage pool's cluster planning spreadsheet.

When the storage pool was installed initially, the person who performed theinstallation should have completed the PureDisk cluster planning spreadsheet.The spreadsheet is in a file named PureDisk_ClusterPlanning.xls. It canbe easier to restore a clustered storage pool if you have access to theinformation that is on the spreadsheet.

If you do not have completed cluster planning spreadsheet from this storagepool's initial installation, you can get a blank one from the following Website:

http://www.symantec.com/business/support/documentation.jsp?pid=52672

Alternatively, see file/opt/pdweb/htdocs/documentation/PureDisk_ClusterPlanning.xls fora new copy of this file.

2 Use the Cluster Manager Java Console to offline all service groups from allthe nodes.

From the Cluster Manager Java Console, right-click the cluster group, andselect Offline > All Systems.

3 Remove all service groups from all the nodes.

Right-click each group and select delete to prevent VCS from taking anyaction while you recover the PureDisk storage pool.

4 Reinstall PDOS on the failed nodes.

Use the PDOS installation information in the following manual:

PureDisk Storage Pool Installation Guide.

On the PDOS main menu, you can select either Install (to use the installationwizard) or you can select Expert (to perform the installation manually).

On each failed node, perform additional configuration steps as needed foryour environment. For example, make sure to consult the chapter called"Preparing to configure the storage pool" in the installation guide.

5 On each failed node, install the clustering software.

The following explains how to install VCS manually on PDOS 6.6:

See “About the Veritas Cluster Server (VCS) software installation” on page 341.

If you are familiar with the typical VCS installation procedure, be aware ofthe following differences:

161Disaster recovery for clustered storage poolsRecovering one active node

■ When the VCS installer prompts you to specify the nodes on which toinstall the software, specify only the failed nodes. Do not install VCS onthe nodes that do not need to be recovered.

■ If you install VCS on only one node, the VCS installer issues a warning.The warning asks you to confirm that you want to install only a single-nodecluster. Answer y.

■ At the end of the VCS 4.1 MP3 installation, the VCS installer asks you tospecify whether you are ready to configure VCS. Answer n.

6 For each node, type the following command to configure a service addresson the public NIC in the node:

# ip a a ip_address dev ethn

For ip_address, specify the service IP address of the service you want toconfigure. For n, specify the number of the public network interface card(NIC) on this node.

For example, on node1.acme.com, you could type the following command:

# ip a a 100.100.100.101 dev eth1

Note:Make sure to repeat this step on each active node, including the healthynodes. Because you removed the service groups for the entire storage pool,you need to recreate the service addresses for each node at this time.



Recreating disks and volumesThe following procedure explains how to recreate the disks, recreate the diskvolumes, and mount the disk volumes.

To recreate the disks and volumes

1 Reinitialize the node's disk volumes on all nodes, even those that did not fail.

Perform the following steps to import all nodes' disk volumes on all storagepool nodes:

■ Import the disk group that is associated with this node:

# vxdg import disk_group_name


162

For more information about this command, see the Veritas StorageFoundation documentation.

■ On each active node that you want to restore, type the following commandto start that node's disk volumes:

# vxvol -g disk_group_name startall

For more information about this command, see the Veritas StorageFoundation documentation.

■ Repeat the preceding steps on all nodes. Make sure to import and startthe disk volumes on all nodes in the storage pool, including those that didnot fail.

2 (Conditional) Type the following command to create the /Storage directory:

Perform this step on the failed node if the disks attached to the node crashedor if the /Storage directory does not exist.

# mkdir /Storage

3 (Conditional) Issue the mount(8) command to mount /Storage on this node.

Perform this step if you created the /Storage directory in the previous step.


mount -t vxfs /dev/vx/dsk/disk_group_name/volume_name /Storage

For disk_group_name and volume_name, specify the full hardware path tothe /Storage volume that you created on this node.

For example:

# mount -t vxfs /dev/vx/dsk/dg1/disk1 /Storage

As you mount /Storage on each node, make sure that the mount attaches toa different disk for each PureDisk node. Connect each node to a differentLUN.

4 (Conditional) Remove the existing topology files.

Perform this step if the node you want to recover is the storage pool authoritynode.

Remove the following files:




5 (Conditional) Create the /Storage/data directory.

Perform this step if a /Storage/data partition existed on this node beforethe disaster and this directory no longer exists.


# mkdir /Storage/data

6 (Conditional) Issue the mount(8) command to mount /Storage/data on thisnode.

Perform this step if you created a /Storage/data directory.


mount -t vxfs /dev/vx/dsk/disk_group_name/volume_name /Storage/data

For disk_group_name and volume_name, specify the full hardware path tothe /Storage/data volume that you created on this node.

7 (Conditional) Create the /Storage/databases directory.

Perform this step if a /Storage/databases partition existed on this nodebefore the disaster and this directory no longer exists.


# mkdir /Storage/databases

8 (Conditional) Issue the mount(8) command to mount /Storage/databases onthis node.

Perform this step if you created a /Storage/databases directory.


mount -t vxfs /dev/vx/dsk/disk_group_name/volume_name /Storage/databases

For disk_group_name and volume_name, specify the full hardware path tothe /Storage/databases volume that you created on this node.


164

9 (Conditional) Specify correct directory permissions for /Storage/databases.

Perform this step if you created a /Storage/databases partition.


# chown -R pddb.pddb /Storage/databases



Running the DR_Restore_all scriptThe following procedure explains how to complete the last disaster recoverypreparation steps and points you to the procedure that explains how to run theDR_Restore_all.sh script.

To run the DR_Restore_all.sh script










4 Run the DR_Restore_all.sh script to recover the data.



Recovering from a data storage corruptionIt is possible for the disks that host the storage partitions to become corrupted.You need to perform a disk corruption recovery if the following conditions arepresent:

■ The PureDisk software failed or if one or more of the databases appears to becorrupted. To determine the state of the databases, examine the log file in thefollowing directory:

/Storage/log/pddb/postgresql.log

Messages such as the following in the log file are possible signs of a corrupteddatabase:

FATAL: could not open file

"/Storage/databases/pddb/data/global/1262": No such file or

directory

LOG: could not open temporary statistics file

"/Storage/databases/pddb/data/global/pgstat.tmp.4391": No such

file or directory

■ /Storage failed or one or more disks have crashed.

■ When the storage pool generates unexpected results after a failover.

■ When a failover failed to complete.

The following procedure explains how to recover from a data storage corruptiondisaster.

To recover from a data storage corruption

1 Recreate the storage partitions that failed.

See “Recreate the storage partitions that failed” on page 166.





Recreate the storage partitions that failedThe following procedure explains how to recreate the storage partitions thatfailed.

Disaster recovery for clustered storage poolsRecovering from a data storage corruption

166

To recreate the storage partitions that failed

1 Clean the cluster service groups.


■ Log on to the Cluster Manager Java console.

■ Verify the state of the service groups.After a disaster, some service groups can be in the faulted state on one ormore nodes.

■ For each service group that has faulted, right-click the group and selectclear fault - auto to clear the faulted state of the service group.

■ Place all service groups offline.Include all service groups, even those service groups on the nodes thatthe disaster did not affect. Right-click each group and select offline -Anysystem to shut down PureDisk on all nodes.

■ Remove all service groups, even those that reside on the nodes that thedisaster did not affect.Right-click each group and select delete to prevent VCS from taking anyaction while you recover the PureDisk storage pool.

2 (Conditional) Replace the failed storage mounts.

Perform this step if necessary.

For example, replace the disk hardware that failed.

3 For each failed node, create new storage partitions to replace the crasheddisks.

Perform the following procedure if you had to replace the disk hardware:

See “(Conditional) Using YaST to create the storage partitions” on page 365.




167Disaster recovery for clustered storage poolsRecovering from a data storage corruption

To recreate disks and volumes

1 Perform the following procedure:





To run the DR_Restore_all script

1 (Conditional) Extract the storage pool software.

Perform this step if you replaced disk hardware that was attached to the nodethat hosted the storage pool authority service.

For example, if you mount the PureDisk software DVD to /cdrom, type thefollowing command:

# /cdrom/puredisk/install.sh --force





# ip a a 100.100.100.101 dev eth1


Disaster recovery for clustered storage poolsRecovering from a data storage corruption

168









Recovering from a complete storage pool disaster(clustered, complete storage pool disaster)

If your PureDisk nodes and shared storage have failed, you need to recover theentire storage pool. The following procedure explains how to recover all the nodesin a clustered storage pool.

To recover all the nodes in a clustered storage pool

1 Reinstall PDOS and disable the service groups.

See “Reinstalling PDOS and disabling the service groups” on page 169.





Reinstalling PDOS and disabling the service groupsThe following procedure explains how to reinstall PDOS, offline the service groups,and remove all the service groups.

169Disaster recovery for clustered storage poolsRecovering from a complete storage pool disaster (clustered, complete storage pool disaster)

To reinstall PDOS and disable the service groups

1 Reinstall PDOS on all nodes and run the storage pool configuration wizardto configure your storage pool.

Reinstall and reconfigure your environment as if this were a new installation.Make sure to configure your storage partitions, nodes, and services as theywere before the disaster. If you completed the cluster planning spreadsheetwhen you performed the initial installation, use it now to help you recreateyour topology.

For information about how to install PDOS and configure the PureDiskapplication, see the PureDisk Storage Pool Installation Guide.

2 Use the Cluster Manager Java Console to offline all service groups from allthe nodes.


3 Remove all service groups.

Right-click each group and select delete to prevent VCS from taking anyaction while you recover the PureDisk storage pool.




To recreate disks and volumes

1 Perform the following procedure:





Disaster recovery for clustered storage poolsRecovering from a complete storage pool disaster (clustered, complete storage pool disaster)

170

To run the DR_Restore_all script

1 Remove the following files from the storage pool authority node:

■ /Storage/etc/topology.ini

■ /Storage/etc/topology_nodes.ini





# ip a a 100.100.100.101 dev eth1








171Disaster recovery for clustered storage poolsRecovering from a complete storage pool disaster (clustered, complete storage pool disaster)






(Conditional) Cleaning up after a failed full disasterrecovery backup

Perform one of the following procedures only if a previous full disaster recoverybackup failed:

■ See “Cleaning up after a failed full NetBackup disaster recovery backup(clustered, complete storage pool disaster)” on page 172.

■ See “Cleaning up after a failed full Samba disaster recovery backup (clustered,complete storage pool disaster)” on page 173.

■ See “Cleaning up after a failed full third-party product disaster recovery backup(clustered, complete storage pool disaster)” on page 173.

Cleaning up after a failed full NetBackup disaster recovery backup(clustered, complete storage pool disaster)

To clean up after a failed full NetBackup disaster recovery backup, you must expire(or purge) corrupted backup images from previous failed backups.

To expire the backup images from failed backups

◆ From the NetBackup interface, manually expire any NetBackup images thatare newer than the date of the last successful backup.

Symantec highly recommends that you purge any corrupted backup imagesfrom any unsuccessful backups before you try the restore.

See the NetBackup Administrator’s Guide, Volume I for information on howto search the catalog for images.

You can search the catalog and use the PureDisk server as the client name.Look for the images that have the Standard and DataStore disaster recoverypolicies.

Disaster recovery for clustered storage pools(Conditional) Cleaning up after a failed full disaster recovery backup

172

Cleaning up after a failed full Samba disaster recovery backup(clustered, complete storage pool disaster)

To clean up after a failed full Samba disaster recovery backup, you must removeany remaining corrupted files from the incomplete backup.

The PureDisk disaster recovery full backup scripts create a previous directoryat the root level of the share that contains the previous backup data. PureDiskcreates this directory at the start of the full backup and removes it at the end ofa successful backup.

If the backup fails, the previous directory still exists on the share. If this directoryexists at the start of another backup run, PureDisk preserves the contents. Itdeletes the current backup data from the failed backup before it starts the newbackup. PureDisk removes the previous directory only when a new full backupis successful.


1 Search for a directory that is called previous in the root level of the sharethat contains the previous backup data.

2 Move the contents of the previous directory to the root level of the share.

3 Remove the directory called previous.

Cleaning up after a failed full third-party product disaster recoverybackup (clustered, complete storage pool disaster)

To clean up after a failed full third-party product disaster recovery backup, youmust remove any remaining corrupted files from the incomplete backup.

Symantec recommends that you follow some procedure at your site to ensure thatthe complete contents of a disaster recovery backup are preserved. Thepreservation ensures consistent backup data.

For example, assume that you perform a full disaster recovery backup eachMonday. On the first Monday of the month, the backup runs without problems.On the second Monday of the month, the disaster recovery backup removes thecontents of the first Monday’s backup. However, the second full disaster recoverybackup fails. This failure leaves you without any consistent backup data.


1 Examine your backup repository.

2 Locate the last successful backup.

3 Remove any subsequent failed backups from the system.

173Disaster recovery for clustered storage pools(Conditional) Cleaning up after a failed full disaster recovery backup

(Conditional) Recreate your topology informationPerform one of the procedures in this section if you enabled encryption for yourdisaster recovery backups.


■ See “(Conditional) Recreating the topology with current topology information(Samba or third-party, clustered recovery)” on page 174.

■ See “(Conditional) Recreating the topology without current topologyinformation (Samba or third-party, clustered recovery)” on page 174.

(Conditional) Recreating the topology with current topology information(Samba or third-party, clustered recovery)

Perform the following procedure if all of the following conditions are true:








(Conditional) Recreating the topology without current topologyinformation (Samba or third-party, clustered recovery)

Perform the following procedure if all of the following conditions are true:



Disaster recovery for clustered storage pools(Conditional) Recreate your topology information

174












Running theDR_Restore_all_script to recover thedataAfter you reinstall the PureDisk software that was destroyed in the disaster, yournext task is to run the DR_Restore_all.sh script. The DR_Restore_all.sh scriptperforms the following actions:

■ Prompts for all of the information that is required to restore an entire storagepool.

■ Restores the data that was backed up.

■ Optimizes the content router restore. This action occurs when the disasteraffected only a subset of the content routers.The DR_Restore_all.sh script fully restores the /Storage/data directory ofall failed content router nodes.If the configuration includes any content routers that do not need to be fullyrecovered because no diaster occurred, the script does minimal restores.The restores bring the content routers to a state that is consistent with thepoint in time of the last disaster recovery backup. Since the last backup wasdone, some data segments might have been removed or added.

175Disaster recovery for clustered storage poolsRunning the DR_Restore_all_script to recover the data

In these cases, the script does the following:

■ Restores all databases and configuration files.

■ Restores the segment containers so that they are consistent with the contentrouter databases.

■ Restores all segment containers that a removal job has changed or deletedsince last the backup.

■ Creates PureDisk service groups in VCS.

The DR_Restore_all.sh script prompts you to specify different informationdepending on the method you used to perform the disaster recovery backup.Proceed to one of the following, depending on your disaster recovery backupmethod:

■ See “Recovering a PureDisk clustered storage pool from a NetBackup disasterrecovery backup” on page 176.

■ See “Recovering a PureDisk clustered storage pool from a Samba disasterrecovery backup” on page 183.

■ See “Recovering a PureDisk clustered storage pool from a third-party productdisaster recovery backup” on page 191.

Recovering a PureDisk clustered storage pool from a NetBackupdisaster recovery backup

The following procedure explains how to recover a PureDisk clustered storagepool from a NetBackup disaster recovery backup.

To recover a PureDisk clustered storage pool from a NetBackup disaster recoverybackup

1 Run the DR_Restore_all script - phase 1.

See “Running the DR_Restore_all script - phase 1 (NetBackup, clusteredrecovery)” on page 177.


See “Running the DR_Restore_all script - phase 2 (NetBackup, clusteredrecovery)” on page 180.

3 Finish the restore.

See “Finishing the restore (NetBackup, clustered recovery)” on page 182.

Disaster recovery for clustered storage poolsRunning the DR_Restore_all_script to recover the data

176

Running the DR_Restore_all script - phase 1 (NetBackup,clustered recovery)During a disaster recovery, you need to run the DR_Restore_all.sh script in twophases. In phase 1, verify host and service address mappings. Rerun the scriptafter you verify that the host address and service address mappings match. Later,in phase 2, continue to answer the script’s prompts regarding the storage pool.

To verify the host and service address mappings

1 Log on to the storage pool authority node as root.

2 (Conditional) Make sure that the root_hash file exists on this node.

Perform this step if the storage pool uses an external root broker. For moreinformation about external root brokers, see the PureDisk Getting StartedGuide and the PureDisk Storage Pool Installation Guide.




4 Type the following command to run the disaster recovery script:



For example:


Backup

1. NetBackup

2. Samba Share

3. Local Directory



6 Affirm whether you installed the NetBackup client on the node.

If you answer n, the script stops, and you must restart the script after youinstall the NetBackup client software.

For example:

Is the NetBackup client installed on all nodes and pointing to

the NBU Server that was used to do the backups? [Yn]: y





For example:


For multiple upgrade patches that need to be applied, provide the latest thatcan be installed on top of the base version. Otherwise, provide in the orderthe patches should be applied (applicable to EEBs).









If these files are not present, the script issues the following prompt:

Please provide the virtual Fully Qualified Domain Name of your SPA:

Enter the service fully qualified domain name (FQDN) for the storage poolauthority (SPA) node. The script retrieves the files from the location youprovide.

If topology.ini.enc is present, the script issues the following prompt forthe password:


178




9 Observe the messages that the script produces and take one of the followingactions:

■ If the host and service mappings are synchronized properly with thetopology on the storage pool, the script continues. Proceed to the followingsection:See “Running the DR_Restore_all script - phase 2 (NetBackup, clusteredrecovery)” on page 180.

■ If the host and service mappings are not synchronized with the topologyon the storage pool, the script issues the following message and stops:

WARNING: You are running in a VCS environment. This means the topology_nodes.ini file

that has just been restored may be out of date. VCS failover events could have changed

the physical - service address mapping for nodes between the time the DR backup last ran

and now.

To verify these mappings, please run /opt/pdinstall/edit_topology.sh and select option

"Edit a node" to edit all PureDisk nodes and spare nodes in your topology. Verify that

for PureDisk nodes, the service address in the "Virtual IP/Hostname" entry is on the

same node as the physical address in the "IP/Hostname" entry. If not, update the

"IP/Hostname" entry to contain the correct physical address for the service address.

Verify that for spare nodes, the "IP/Hostname" entry is really the physical address of

a node that is currently acting as a spare node.

Also, select the option "Configure root broker" and verify that the root broker mapping

is correct.

Once you verified the physical - service address mapping is correct for all nodes, and

the root broker mapping, please run this script again.

Note: As the preceding warning message explains, at this time, it isimportant to run/opt/pdinstall/edit_topology.sh to start the topologyeditor. In the topology editor, for each node, select Edit a node, and clickOK. This action creates the required VCS configuration file on each node.

For example, failovers might have occurred between the time of the lastdisaster recovery backup and this restore. If so, the restore topology fileshave invalid host and service address mappings for the nodes of the storagepool.


Correct these inconsistencies and run the DR_Restore_all script again.

10 (Conditional) Verify the NIC identifiers and (conditionally) correct the NICidentifiers.

Perform this step if you reinstalled PDOS on any nodes.

When you reinstall PDOS, the NIC identifiers can be different from the NICidentifiers that existed in the previous PDOS installation.

Perform the following steps to verify and, if necessary, correct the NICidentifiers:

■ Log into the storage pool authority node and type the following commandto start the topology editor:


Use the topology editor to check and, if necessary, correct the NICidentifier for the public NIC. The topology editor displays informationabout the public NIC below the service addresses. You can changeinformation about the public NIC in the topology editor.

■ Open file /Storage/etc/topology_nodes.ini.

■ Search for the following keywords: firstprivate and secondprivate.

■ Verify that the ethn identifiers for firstprivate and secondprivate

point to the correct NICs.

■ (Conditional) Correct the ethn identifiers in the topology_nodes.ini file.

Perform this step if the ethn identifiers differ from those that existedwhen PDOS was installed initially.

Running the DR_Restore_all script - phase 2 (NetBackup,clustered recovery)In phase 2, the script restores the files from the backup. The DR_Restore_all.shscript initiates a dialog with you. You need to answer the questions that the scriptdisplays.

To restore a storage pool




180



---- ---------- ---------


2 10.80.62.2 cr

Node number(s): 1

The preceding example shows the topology that the script can restore in thisdisaster recovery operation. Examine this information for accuracy, andspecify all nodes for restore. Use commas to separate the node numbers.


■ Remounts the mount points.

■ Restores all the data on the failed nodes.

■ Restores all the databases on all the nodes.

■ Restores any removed data. A data removal job might have been run sincethe last time the databases were backed up. For this reason, the script alsorestores the removed data on the nodes that did not fail. This actionsynchronizes the databases and data.


The restore process can take hours to complete. As the script runs, you mightbe asked to specify the system passwords for the remote (or local) nodes. Thisprompt occurs early in the process during secure shell (SSH) authentication.

3 (Conditional) Respond to the queries from the upgrade patches.






For example:









Finishing the restore (NetBackup, clustered recovery)The following procedure explains the tasks you need to perform to finish therestore.

To finish the restore

1 On each content router node, log on as root.

2 Run the following command to change DEREF to Yes.

# /opt/pdcr/bin/crcontrol -m DEREF=Yes

3 Repeat the following steps until you have run this command on all contentrouter nodes:

■ Step 1

■ Step 2


182





5 (Conditional) Reenable the NetBackup export engine on any nodes that hostedonly a NetBackup export engine service.






Recovering a PureDisk clustered storage pool from a Samba disasterrecovery backup

The following procedure explains how to recover a PureDisk clustered storagepool from a disaster recovery backup that you wrote to Samba.

To recover aPureDisk clustered storagepool fromaSambadisaster recovery backup


See “Running the DR_Restore_all script - phase 1 (Samba, clustered recovery)”on page 184.


See “Running the DR_Restore_all script - phase 2 (Samba, clustered recovery)”on page 188.


See “Finishing the restore (Samba, clustered recovery)” on page 190.


Running theDR_Restore_all script - phase 1 (Samba, clusteredrecovery)During a disaster recovery, you need to run the DR_Restore_all.sh script in twophases. In this first phase, verify host and service address mappings. If the hostaddress and service address mappings do not match, the script exits and you needto correct the mappings. If necessary, rerun the script until the host and serviceaddress mappings match. Later, in phase 2, continue to answer the script’s promptsregarding the storage pool.











For example:


Backup

1. NetBackup

2. Samba Share

3. Local Directory


6 Provide the information that PureDisk needs to mount the shared file system.

For example:

Please enter remote samba share (i.e.

//11.88.77.33/remoteSambaShare):

//rmns1.min.boston.com/PD_DRdata


184

7 Provide information about the local mount point.

The local mount point is the path name of a directory on which to mount theshare. If you used the DR_restore_all script in the default PureDisk location,the mount point must be /DRdata.

Please enter local mount point (default: /DRdata):

If appropriate, press Enter to accept the default.

8 Provide authentication information.

This information includes the user name, password, and work group forSamba on the remote file server.

For example:

Please enter samba user name: pduser

Please enter samba password: pdpwd

Please enter samba workgroup: pdwgroup


(default: /DRdata):


If you used the DR_restore_all.sh script in the default PureDisk location,press Enter.

If you supplied your own restore script, PureDisk does not protect it. Thescripts are overwritten during a restore procedure if they remain in the defaultinstallation directory (/opt). You must write them to another directory forprotection, such as /usr or /tmp.

For example:



re.sh):





For example:







For example:








This ID is the value specified for the storagepoolid property in thetopology.ini file. This value is used to retrieve the topology file.

For example:







186






■ If the host and service mappings are synchronized properly with thetopology on the storage pool, the script continues. Proceed to the followingsection:See “Running the DR_Restore_all script - phase 2 (Samba, clusteredrecovery)” on page 188.





and now.









is correct.




For example, failovers might have occurred between the time of the lastdisaster recovery backup and this restore. If so, the restore topology files


have invalid host address and service address mappings for the nodes ofthe storage pool.Correct these inconsistencies and run the DR_Restore_all script again.














Running theDR_Restore_all script - phase 2 (Samba, clusteredrecovery)In phase 2, the script restores the files from the backup. The DR_Restore_all.shscript initiates a dialog with you. You need to answer the questions that the scriptdisplays.





188



---- ---------- ---------


2 10.80.62.2 cr

Node number(s): 1






■ Restores the removed data. A data removal job might have been run sincethe last time the databases were backed up. For this reason, the script alsorestores the removed data on the nodes that did not fail. This methodsynchronizes the databases and data.


The restore process can take hours to complete. As the process runs, youmight be asked to specify the system passwords for the remote (or local)nodes. This prompt occurs early in the process during SSH authentication.

3 (Conditional) Respond to the queries from the upgrade patches.






For example:









Finishing the restore (Samba, clustered recovery)The following procedure explains the tasks you need to perform to finish therestore.






■ Step 1

■ Step 2


190











Recovering a PureDisk clustered storage pool from a third-partyproduct disaster recovery backup

The following procedure explains how to recover a PureDisk clustered storagepool from a disaster recovery backup that you wrote to a third-party product.

To recover a PureDisk clustered storage pool from a third-party product disasterrecovery backup


See “Running the DR_Restore_all script - phase 1 (third-party, clusteredrecovery)” on page 192.


See “Running the DR_Restore_all script - phase 2 (third-party, clusteredrecovery)” on page 196.


See “Finishing the restore (third-party, clustered recovery)” on page 198.


Running the DR_Restore_all script - phase 1 (third-party,clustered recovery)During a disaster recovery, you need to run the DR_Restore_all.sh script in twophases. In this first phase, verify host and service address mappings. If the hostaddress and service address mappings do not match, the script exits and you needto correct the mappings. If necessary, rerun the script until the host address andservice address mappings match. Later, in phase 2, continue to answer the script’sprompts regarding the storage pool.











For example:


Backup

1. NetBackup

2. Samba Share

3. Local Directory


6 Provide information about where the data to be restored is located.

Press Enter to accept the defaults for the following prompts:

Please enter location to restore metadata from (default:

/DRdata):


(default: /DRdata):


192


If you used the DR_Restore_all.sh script in the default PureDisk location,press Enter.

If you supplied your own restore script, remember that the scripts are notprotected. The scripts are overwritten during a restore procedure if theyremain in the default installation directory (/opt). To prevent this problem,you must place them in another directory for protection (for example, in /usr

or /tmp).

For example:



re.sh):











For example:








This name is the value specified for the storagepoolid property in thetopology.ini file. This value is used to retrieve the topology file.

For example:












194

■ If the host and service mappings are synchronized properly with thetopology on the storage pool, the script continues. Proceed to the followingsection:See “Running the DR_Restore_all script - phase 2 (third-party, clusteredrecovery)” on page 196.





and now.









is correct.




For example, failovers might have occurred between the time of the lastdisaster recovery backup and this restore. If so, the restore topology fileshave invalid host and service address mappings for the nodes of the storagepool.Correct these inconsistencies and run theDR_Restore_all.sh script again.















Running the DR_Restore_all script - phase 2 (third-party,clustered recovery)In phase 2, the script restores the files from the backup. The DR_Restore_all.shscript initiates a dialog with you. You need to answer the questions that the scriptdisplays.


1 Examine the topology information that the script displays and specify thenodes you want to restore.




---- ---------- ---------


2 10.80.62.2 cr

Node number(s): 1



196





■ Restores the removed data. A data removal job might have been run sincethe last time the databases were backed up. In that case, the script alsorestores the removed data on the nodes that did not fail. This methodsynchronizes the databases and data.


The restore process can take hours to complete. As the script runs, you mightbe asked to specify the system passwords for the remote (or local) nodes. Thisprompt occurs early in the process during SSH authentication.






For example:










Finishing the restore (third-party, clustered recovery)The following procedure explains the tasks you need to perform to finish therestore.






■ Step 1

■ Step 2












198

Storage pool authorityreplication (SPAR)


■ About storage pool authority replication (SPAR)

■ Activating the local storage pool

■ Enabling SPAR backups

■ Running a SPAR policy manually

■ Restoring from a SPAR backup

About storage pool authority replication (SPAR)PureDisk enables you to replicate storage pool authority configuration informationfrom an all-in-one local storage pool to a main storage pool. This type of replicationis called storage pool authority replication (SPAR).

You can enable both SPAR and disaster recovery backups. If you enable both, youcan choose the disaster recovery method you want to use. For more informationabout when to use SPAR and when to use disaster recovery backup, see thefollowing:

■ See “Disaster recovery strategies” on page 201.

■ See “About disaster recovery backup procedures” on page 99.

8Chapter

Note: The main storage pool can be configured as a clustered storage pool.However, Symantec does not support SPAR for clustered local storage pools. WhenSPAR runs under cluster control, a failover moves all node functions to a passivenode. However, the failover does not move the SPAR feature that you enabled onthe original local storage pool authority node.

Figure 8-1 shows an example PureDisk environment with two storage pools.

Figure 8-1 SPAR example

SP_localPureDisk agent

SP_mainSPAR backup

SPAR restore

SP_local is a small, local storage pool in Duluth and SP_main is in a main officein Minneapolis. SPAR is implemented to back up system information fromSP_local to SP_main. The information in this section uses this exampleenvironment.

SPAR’s main benefit is that SPAR enables you to restart a storage pool and beginbacking up data soon after a disaster.

A SPAR recovery is best performed in the following circumstance:

■ You have an all-in-one local storage pool that is down completely.

■ You want to restore all your user information, data selection definitions, backuppolicies, and system policies. This data includes all the user data and storagepool data that enables client backups. This data does not include the backupdata or backup metadata.

■ You want to be able to start backing up data again very quickly.

SPAR differs from the other disaster recovery methods because SPAR does notrecover your backup data or metadata. A full disaster recovery can take severalhours or days, depending on how much data you backed up. SPAR recoveries arefaster. After a SPAR recovery, PureDisk sees the local storage pool as if it were anewly configured storage pool. The backups you perform immediately after aSPAR recovery are all full backups.

When you enable both comprehensive disaster recovery backups and SPAR, youcan choose the recovery method you want to use. If you perform a SPAR recovery,you can use full disaster recovery methods to restore your file data and metadata

Storage pool authority replication (SPAR)About storage pool authority replication (SPAR)

200

to an alternate storage pool. You need an alternate storage pool in thiscircumstance. A full disaster recovery to a local storage pool destroys all the datathat you backed up between the SPAR recovery and the time you performed thefull disaster recovery.

Note: If you experience replication job performance degradation and you have ahigh-latency communication network between the two storage pools, you canpossibly improve performance by changing some default TCP/IP settings. Formore information, see "About changing TCP/IP settings to improve replicationjob performance" in thePureDiskBestPracticesGuide, Chapter 5: Tuning PureDisk.

Disaster recovery strategiesSymantec recommends that you back up your PureDisk environment on a regularbasis.

PureDisk supports the following methods for disaster recovery:

■ Complete disaster recovery.This method uses a PureDisk policy that sends data to NetBackup or scriptsto back up and restore storage pool specifications, file data, and file metadata.For more information about complete disaster recovery, see the following:See “About disaster recovery backup procedures” on page 99.

■ Storage pool authority replication (SPAR).This method backs up and restores storage pool specifications, but not filedata or metadata.

Along with disaster recovery backups, you can replicate all your data selectionsto another storage pool. You can use the replicated data selections to restore aPureDisk storage pool. If you replicate all data selections to another storage pool,you can limit data loss after a disaster.

For information about data replication, see the following:

See “About data replication” on page 59.

The method that is best for your site depends on your configuration, practices,and disaster recovery goals.

Table 8-1 shows the characteristics of these two methods.

201Storage pool authority replication (SPAR)About storage pool authority replication (SPAR)

Table 8-1 Disaster recovery method comparison

SPARComplete disaster recoveryCharacteristic

Storage pool metadata.Storage pool metadata, file data,and file metadata.

Data restored

SPAR restores take much less timethan a complete disaster recovery.

Depends on the amount of data.This step can take hours.

Estimated restoretime

The protected storage pool mustbe an all-in-one, single-node,unclustered storage pool.

Any type of storage pool.Storage pool type

You want to restore the storagepool and back up the clients asquickly as possible.

You want to restore the storagepool and all backups.

Restore goal

Restores your storage pool users,accounts, data selections, policies,and all other storage poolconfiguration information. Thismethod does not restore any filedata or file metadata. After yourestore, you need to run backupsfor all your clients. Old or changeddata is no longer available.

Restores your storage pool to thestate it was in when the lastdisaster recovery backup was run.

State of restoredstorage pool

Activating the local storage poolTo implement the SPAR method successfully, the local storage pool must be aclient to the main storage pool.

The following procedure explains how to register the local storage pool as themain storage pool’s client. This procedure also configures the other aspects ofSPAR.

To register the local storage pool

1 In the local storage pool’s Web UI, click Settings > Topology.

2 In the left pane, select a local storage pool.

3 In the right pane, click Activate SPA Replication.

Storage pool authority replication (SPAR)Activating the local storage pool

202

4 Complete the display that appears.

The display requests the same information that you need to supply when youinstall an agent on the storage pool authority. These fields are as follows:

The root user’s login on the main storage pool authoritynode.

Login

The root user’s password on the main storage poolauthority node.

Password

The fully qualified domain name (FQDN) of the mainstorage pool.

Host name (FQDN)

Example:

SP_Main.acme.com

The local storage pool’s host name. Type this name as youwant it to appear in the main storage pool’s Web UI.

Storage pool name

The path to the Linux agent software on the main storagepool. This agent software is the same as the agent software

Binary Location

that you use for all other Linux PureDisk clients. You canspecify an IP address or a host name to identify the mainstorage pool.

In this field, do not specify the actual file in which the Linuxagent installation software resides. You specify the filename in the next field, Binary.

Example:

Assume that you installed the agent software packages inthe default location on SP_Main. The default location isas follows:

/opt/pdweb/htdocs/download/Linux_Clients

For the Binary Location field, use the fully qualifieddomain name (FQDN) and specify the following path:

https://SP_Main.acme.com/download/Linux_Clients

The name of the file that includes the Linux agentinstallation software on the main storage pool. The Binary

Binary

Location field’s content points to this file name. Forexample, pdagent-Linux_2.6_x86-6.2.0.5.run.

203Storage pool authority replication (SPAR)Activating the local storage pool

The path to which you want to install the Linux agent onthe local storage pool. For example, /opt/SPAR.

Caution: Do not specify the path to the primary serveragent on the local storage pool. For example, if the serveragent is in its default location, do not specify /opt in thisfield. This path is the location of the primary server agenton the local storage pool. Do not overwrite this file.

Path

The path to a dump directory on the local storage pool.PureDisk writes the local storage pool’s system informationto this location before it copies the system information tothe main storage pool. Do not specify an existing directory.Specify only a unique directory that SPAR can useexclusively.

Each time the SPAR policy runs, it overwrites this directory.When you perform a SPAR recovery, it restores the lastversion written.

For example, /Storage/SPAR.

Dump Path

5 Record the information you specified and keep it in a safe place.

If the local storage pool goes down, you need the information you specifiedon this screen to perform a restore. All the arguments to these fields appearon the main storage pool, except for the Path field. If a disaster occurs, youcan restore a downed local storage pool faster if you have this informationrecorded and stored safely.

6 Click Save.

After you click Save, PureDisk runs a job to activate the local storage pool asa client to the main storage pool.

After activation, the status of the two storage pools is as follows:

■ The local storage pool appears in the main storage pool’s list of clients.

■ Two agents reside on the local storage pool. The first is the local storagepool’s primary server agent. The second is an agent that connects thelocal storage pool to the main storage pool.

Enabling SPAR backupsPureDisk includes a system policy for SPAR. The following procedure explainshow to enable this policy. PureDisk creates the jobs to run this policy on the localsite.

Storage pool authority replication (SPAR)Enabling SPAR backups

204

To enable SPAR backups

1 On the local storage pool, click Manage > Policies.

2 In the right pane, under the Storage Pool Management Policies category,click the plus (+) sign to the left of SPA Replication.

3 Select System policy for SPA replication.

4 Complete the required information in the General tab.

See “Completing the General tab for a SPA Replication” on page 205.

5 Complete the required information in the Scheduling tab.

See “Completing the Scheduling tab for a SPA Replication policy” on page 206.

6 Complete the required information in the Parameters tab.

See “Completing the Parameters tab for a SPA Replication policy” on page 206.

7 Click Save.

Completing the General tab for a SPA ReplicationThis tab lets you name and define the policy.



You do not have to rename this policy.


This setting has the following options:

■ If you select Enabled, PureDisk runs the policy according to the schedulein the Scheduling tab.

■ If you select Disabled, PureDisk does not run the policy according to theschedule in the Scheduling tab. This selection is the default.You might use Disabled to stop this policy from running this policy duringa system maintenance period. Then, you would not need to enter

205Storage pool authority replication (SPAR)Enabling SPAR backups

information in the Scheduling tab to first suspend and later reenable thispolicy.

3 Select times in the Escalatewarningafter or the Escalateerrorandterminateafter drop-down boxes. These times specify the elapsed time before PureDisksends a message.

PureDisk can notify you if a policy does not complete its run within a specifiedtime. For example, you can configure PureDisk to send an email message toan administrator if a policy does not complete in an hour.

If you select either of these options, create a policy escalation action. Theaction defines the email message, defines its recipients, and associates theescalation action with the policy. For more information about policyescalations, see the PureDisk Backup Operator's Guide.

Completing the Scheduling tab for a SPA Replication policyFrom this tab, use the drop-down lists to specify when the policy is to run.


◆ Specify the schedule details that define how frequently you want the policyto run.

Completing the Parameters tab for a SPA Replication policyExamine the information on this tab and correct it if necessary.

To examine the parameters tab

1 (Conditional) Correct the information in these fields. Perform this step onlyif the fields contain incorrect information.

For example, if the URL, login, or password for the main storage pool everchange, correct the information in this tab.

2 Click Save.

Running a SPAR policy manuallyYou can run a SPAR policy according to a schedule. You can also use the followingprocedure to run a SPAR policy manually.

Storage pool authority replication (SPAR)Running a SPAR policy manually

206

To run a SPAR policy

1 On the local storage pool, click Manage > Policies.

2 In the left pane, under Storage Pool Management Policies, click the plus (+)sign to the left of SPA Replication.

3 Select system policy for spa replication.

4 (Conditional) Enable the policy.

You have to enable a policy before you can run it. In the right pane, clickEnabled and Save.


6 Examine the output.

Restoring from a SPAR backupThe RestoreSPAAIO.php command restores system data from a SPAR backup andre-establishes the client connection between the local storage pool and the mainstorage pool.

To restore system data from a SPAR backup

1 Gather the information you need to perform a SPAR restore.

2 Install the PureDisk Operating System (PDOS) on the local storage pool.

For more information about how to install PDOS, see the PureDisk StoragePool Installation Guide.

3 Use the storage pool configuration wizard to configure the PureDisk storagepool.

Configure the storage pool software on the local storage pool. For moreinformation about how to use the storage pool configuration wizard, see thePureDisk Storage Pool Installation Guide

Perform the following steps if the storage pool software does not function:

■ Remove the storage pool software’s previous upgrade package.The following is the directory you need to remove:

/etc/puredisk

■ Configure new storage pool software.During this reconfiguration, the installer proposes again a (new) randomstorage pool ID. Do not accept this proposed storage pool ID. Instead,specify the original storage pool ID. If you do not specify the original

207Storage pool authority replication (SPAR)Restoring from a SPAR backup

storage pool ID, the storage pool becomes inoperable after you performthe SPAR restore.When you configure the new storage pool software, specify the samepasswords that you specified during the previous configuration.

4 Deactivate the agent in the main storage pool that performed the SPAR.


■ Log in to the main storage pool’s Web UI.

■ In the left pane, click Settings > Topology.

■ Select the PureDisk agent that represents the PureDisk storage pool.

■ In the right pane, click Deactivate Agent.

5 Retrieve the information you used to configure SPAR initially.

See “To register the local storage pool” on page 202.

This procedure advises you to record the configuration information and storeit in a safe place. Retrieve this information now. You need this informationand some additional information to create the restore command.

A later step in this procedure directs you to use the RestoreSPAAIO.php

command to perform the restore. You can obtain information about many ofthis command’s arguments from the main storage pool. Other information,however, such as the install path to the SPAR client on the local storage poolis not recorded anywhere in PureDisk. If you have this information beforeyou begin, the restore command is easier to specify.

Storage pool authority replication (SPAR)Restoring from a SPAR backup

208

6 Log in to the local storage pool as root.

7 Use the RestoreSPAAIO.php command to perform the restore.

The restore command restores the local storage pool’s system informationand re-establishes the local storage pool’s client relationship to the mainstorage pool.

Refer to Table 8-2.

The figure shows the arguments to the RestoreSPAAIO.php command. Youcan type the arguments in any order, but the arguments must match youroriginal configuration.

The following example shows the command with all the required arguments:

# /opt/pdag/bin/php /opt/pdspa/cli/RestoreSPAAIO.php --ip SP_Main.acme.com

--login root --password root --hostname SP_local-Duluth

--binary pdagent-Linux_2.6_x86-6.2.0.5.run

--binaryloc https://SP_Main.acme.com/download/Linux_Clients/

--agentlocation /opt/SPAR --agentid 2 --dsid 2 --dumpdir /Storage/SPAR/

About the RestoreSPASIO commandThe following sections explain the arguments to theRestoreSPAAIO.php command.

Required arguments for the RestoreSPAAIO commandTable 8-2 shows the required arguments for the RestoreSPAAIO.php command.

Table 8-2 Required RestoreSPAAIO.php command arguments

MeaningArgument

Local storage pool authority’s agent ID as registered on themain storage pool. To obtain this information, perform thefollowing steps on the main storage pool:


2 In the right pane, select the local storage pool’s agenticon.

3 Note the number in the Storage Pool ID field.

--agentid

Full path to the directory in which the agent resided for theprevious SPAR backup. You specified this information in thePath field when you configured SPAR.

--agentlocation


Table 8-2 Required RestoreSPAAIO.php command arguments (continued)

MeaningArgument

File name for agent installer on the main storage pool. Youspecified this information in the Binary field when youconfigured SPAR.

--binary

Path to the agent installer on the main storage pool. Do notinclude the file name at the end of this path. You specifiedthis information in the Binary Location field when youconfigured SPAR.

--binaryloc

Data selection ID (DSID) of the data selection that PureDiskused to do the previous SPAR backup. To obtain thisinformation, perform the following steps on the main storagepool:


2 In the left pane, click the plus sign (+) to the left of thelocal storage pool’s agent icon.

3 Select the SPAR data selection.

4 Note the number in the ID field.

--dsid

Full path to the restore directory. Specify the same dumpdirectory that you used for the previous SPAR backup.

--dumpdir

Host name of the local storage pool as it appeared in the mainstorage pool’s Web UI for the previous SPAR backup.

--hostname

FQDN, host name, or IP address of the main storage pool.Specify a resolvable identifier.

--ip

Root user login to the main storage pool.--login

Root user password for the main storage pool.--password

(Optional) Runs command in debug mode.-d or --debug

(Optional) Runs command in silent mode.-s or --silent

(Optional) Runs command in verbose mode.-v or --verbose

Optional arguments for the RestoreSPAAIO commandTable 8-3 shows the optional arguments to the RestoreSPAAIO.php command.


210

Table 8-3 Optional RestoreSPAAIO.php command arguments

ArgumentParameter

(Optional) Displays PHP information at run time.--info

(Optional) Displays command help information.--help

Upgrading PureDisk with SPAR enabledYou must follow a strict order during the upgrade process if your environmentincludes two or more storage pools with SPAR enabled between them.

The order is as follows:

■ First, upgrade the storage pool from which you replicate the storage poolauthority.

■ Second, upgrade the storage pool to which you replicate the storage poolauthority.

For more information about upgrades, see the PureDisk Storage Pool InstallationGuide.



212

Reports


■ About reports

■ Permissions and guidelines for running and viewing reports

■ Reports for a running job

■ About policies and workflows

■ Obtaining detailed job reports

■ About Data mining reports

■ Enabling a data mining policy

■ Running a data mining policy manually

■ Obtaining data mining policy output - the data mining report

■ Obtaining data mining policy output - the Web service report

■ Web service reports

■ About Dashboard reports

■ Central storage pool authority reports

About reportsThe following explain how to run and display PureDisk reports:

■ See “Permissions and guidelines for running and viewing reports” on page 214.

■ See “Reports for a running job” on page 215.

■ See “About policies and workflows” on page 216.

9Chapter

■ See “Obtaining detailed job reports” on page 218.

■ See “About Data mining reports” on page 233.

■ See “Enabling a data mining policy” on page 234.

■ See “Running a data mining policy manually” on page 236.

■ See “Obtaining data mining policy output - the data mining report” on page 236.

■ See “Obtaining data mining policy output - the Web service report” on page 239.

■ See “Web service reports” on page 242.

■ See “About Dashboard reports” on page 249.

■ See “Central storage pool authority reports” on page 254.

Permissions and guidelines for running and viewingreports

The following factors determine whether a user can create reports and view reportresults with the permissions that they possess:

■ Permission to create reports. A user needs Report permission and Viewpermission to create reports.

■ A user in the reporters group and a user with Report permission can runreports and can run data mining policies. You can assign users to thereporters group only at the World level.

■ A user needs View permission at the storage pool level to retrieve datamining reports.

■ Permission to view reports. View permission determines how much informationthat user can see in a data mining report.For example, users with View permission at the storage pool level can viewinformation for the entire storage pool in data mining reports. If a user hasView permission only at the client level, they can see only that client'sinformation in a data mining report.

■ Permission to create reports about central storage pools. A user needs CentralReport permission at the storage pool level.

■ Root user permission. If a user logs in as root, PureDisk displays the Reportstab. Only root users can view the reports displayed from this tab.

Other factors can affect the availability of reporting data. For example, if yourestored a storage pool, wait about 15 minutes before accessing report data.

ReportsPermissions and guidelines for running and viewing reports

214

For more information about permissions, see the PureDisk Client InstallationGuide.

Reports for a running jobWhen you examine a running job, you can see the steps that PureDisk takes whenit runs. These individual steps are called workflow steps. The following sectionsshow how to examine a running job and explain the workflow steps.

For information about job reports for PureDisk deduplication jobs, see thePureDiskDeduplication Option Guide.

For information about examining a running job or restarting a job, see thefollowing:

■ See “Examining a running job” on page 215.

■ See “Restarting a backup job” on page 216.

Examining a running jobThe following procedure explains how to view job step information for runningjobs and for jobs that are in the queue.

To obtain a report on a running or queued job


2 In the left pane, select the storage pool.

3 In the right pane, select More Tasks and pull down Job Steps Report.

PureDisk displays the Job Steps Report.

4 Click one of the tabs to see different aspects of a job’s progress.

For example, click Job Steps with Problems to see job steps. Click one of thenumbers in the Job ID column to display more details about a specific job.

For more information about the job details displays, see the following:

See “Obtaining detailed job reports” on page 218.

If a data lock password is enabled on this agent, the Files and Errors tabsprompt you for the password when you attempt to view them.

For more information about the data lock password, see the PureDisk ClientInstallation Guide.

215ReportsReports for a running job

Restarting a backup jobIf a backup job fails or if you abort a job, you can use the following procedure torestart the job.

To restart a job

1 Click Monitor > Jobs.

2 (Optional) Narrow your search for the job you are interested in.

If there are many jobs in the right pane, you can narrow your search throughone of the following:

■ Specify information in the Look for field, pull down an object type fromthe in field, and click Find now to display only a subset of the defaultinformation.You can specify a string of characters to search for in the Look for field.For example, you can specify the full name of a client in the Lookfor field,and then you can select Agent Name from the in pull-down menu.

■ In the left pane, select a category from the ViewJobsBy pull-down menu.

3 Near the top of the right pane, click Restart job.

About policies and workflowsWhen you click Manage > Policies, the right pane of the Web UI displays backupjobs, restore jobs, and other jobs. The following describe policies and workflows:

■ See “Types of workflows” on page 216.

■ See “Workflows in policies” on page 217.

Types of workflowsA workflow is a collection of steps that PureDisk completes to accomplish a task.A policy is a special kind of workflow. To create a policy manually, or to edit apolicy, click Manage > Policies. The PureDisk Web UI categorizes policies andworkflows as follows:

■ Backup Policies

■ Data Management Policies

■ Storage Pool Management Policies

■ Restore Workflows

■ Miscellaneous Workflows

ReportsAbout policies and workflows

216

If you upgraded from a previous PureDisk release, you might also see the LegacyWorkflows category with one or more workflows beneath it. For example, thiscategory might contain the following workflows:

■ 6.5 Data selection removal workflow

■ 6.5 Rerouting Workflow

■ 6.5 MBDataMining workflow

Whether the Web UI displays any legacy workflows depends on the presence ofexisting workflows at the time of your upgrade. If you ran a data mining policybefore you applied an upgrade, the workflow appears in the Web UI after theupgrade is installed. You can examine the outcomes of these workflows, or youcan delete them.

Workflows in policiesA workflow step defines a PureDisk action. PureDisk accomplishes its work byrunning a series of workflow steps. The individual workflow steps are predefined,and each performs a specific action. When you use PureDisk to perform a backup,a restore, or any other kind of task, PureDisk completes that task by runningseveral workflows.

A policy defines a data management or maintenance action. Within a backuppolicy, for example, the schedule determines when the policy runs, the agentsand the data selections to back up, and other various parameters. PureDisk canstop processing after a timeout .

A timeout can occur in two different ways:

■ In a workflow step. PureDisk permits internal workflow steps to run only fora limited time.

■ In a policy. The General tab of a backup policy lets you specify the amount oftime a policy can run before PureDisk terminates the policy run.

PureDisk’s internal watchdog monitors workflow steps. In the case of a backuppolicy, the watchdog issues a message if the backup does not complete within thespecified backup window. The watchdog also issues messages for individualworkflow steps or policies that terminate. You can configure event monitoring tonotify you of these occurrences. For more information about how to configureevents, see the PureDisk Backup Operator’s Guide.

217ReportsAbout policies and workflows

Obtaining detailed job reportsThe following procedure explains how to obtain a detailed job report. This reportreturns information on a per job basis. By analyzing this report, you can determinehow efficiently PureDisk operates in your environment.

To obtain a report for a job that has finished


2 (Optional) Specify information in the Look for field, pull down an object typefrom the in field, and click Find now to display only a subset of the defaultinformation.

You can specify a string of characters to search for in the Look for field. Forexample, you can specify the full name of a client in the Look for field, andthen you can select Agent Name from the in pull-down menu.

3 In the right pane, in the Job ID column, click the number that correspondsto the job you want to examine.

An informational window appears with the several tabs. For example, thepop-up window includes the following tabs for a backup job:

Includes the job’s execution status, whether there were any errorsduring the job’s run, and when the job commenced.

General

Shows the status for each specific part of a job’s run. On this tab,you can see how PureDisk breaks a job apart for processing.

Details

Provides information on the number of processed files and thenumber of bytes of data that was transferred between the clientand the content router.

Statistics

Lists the files that the job backed up. Includes whether PureDiskbacked up the files successfully, the client upon which the fileresided, and the name of the file.

Files

Lists the files with the errors that PureDisk encountered whenit processed the job.

Errors

Shows the job step output.Job log

4 (Optional) Click one of the following tabs to perform additional actions:

■ Restart job

■ Stop job gracefully

■ Stop job immediately

ReportsObtaining detailed job reports

218

■ Delete job

General tab for a Job Details reportThe General tab summarizes a job’s activity. It includes information about whetherthe job completed successfully, the number of errors, the start time, and the finishtime.

Details tab for a Job Details reportThe Details tab shows the job steps PureDisk performed to complete the job. Selecta workflow step in the left column to view information about that step in the rightcolumn.

Some job steps generate more information than PureDisk can display in the rightpane of the Details tab.

To control the amount of information that appears in the right column, click thedrop-down menu that appears directly above the upper-left corner of the rightcolumn. Then, specify a different amount of information to display.

If the information in the right column exceeds the space allowed, PureDisk writesthe following message at the end of the output:

PureDisk truncated this log file. You can download the complete log

file from the Job log tab.

If you see this message, perform the procedure in the following section:

See “Examining lengthy job logs” on page 233.

Statistics tab for a Job Details reportPureDisk provides information on this tab for backup jobs, restore jobs, replicationjobs, and PDDO jobs.

Statistics for a backup jobThe statistics for a backup job pertain to all supported file types that were includedin the backup. The PureDisk Backup Operator’s Guide lists the file types thatPureDisk supports.

The Statistics tab for a backup job does not show information about unsupportedfiles or files that cannot be backed up at all. Unsupported file types are files thatare not supported by PureDisk, such as reparse points on Windows. Examples ofthe file types that cannot be backed up are doors and sockets on UNIX systems.

219ReportsObtaining detailed job reports

For efficiency reasons, PureDisk always uploads files smaller than 16 KB to thecontent router, even if they are already stored on the content router. Consequently,the backup statistics can be different from what you expect if you back up manyfiles smaller than 16 KB. For example, the data reduction factor can be lower thanexpected, or the number of bytes transferred can be higher than expected.

Table 9-1 contains information about how to interpret the statistics in a backupjob.

Table 9-1 Lines in the Statistics tab for a backup job

MeaningStatistic or heading

Data Reduction:

The percentage of source data bytes that did not have to betransmitted to the content routers because of data reduction.Higher numbers correlate to more efficiency.

Global data reductionsavings

The total number of bytes for the files that PureDisk backed updivided by the amount of bytes transferred to the contentrouters. Higher numbers correlate to more efficiency.

Global data reductionfactor

Data Uniqueness:

The number of backed up files that were globally unique, afterglobal data reduction, before segmentation, and beforecompression.

This statistic is the number of files that are unique in the groupof data selections under consideration. The files themselves areconsidered, but optimization through segmentation is notconsidered. For example, if a file resides on three differentclients, PureDisk stores the file only once and counts it onlyonce in this number. At the segment level, however, PureDiskperforms more optimization. A file segment can be present inmore than one file, and PureDisk stores that segment only once.

Unique files and foldersbacked up

The total number of bytes in the backed up files that wereglobally unique.

This statistic is the accumulated size of the unique filestransferred to the content routers. When encryption orcompression are enabled, it is the accumulated size of theencrypted or compressed unique files. The reported value alsoincludes all overhead bytes necessary for headers, alignment,and so on. The values in the Sourcebytesbackedup and Uniquebytes backed up fields are not always identical even if all filesbacked up are unique.

Unique bytes backed up


220

Table 9-1 Lines in the Statistics tab for a backup job (continued)


Source selection:

The number of files that meet the data selection inclusion andexclusion rules. Pertains to regular files only. This number doesnot include the number of special files, such as symbolic linksor device special files.

Files selected on source

The total number of bytes for the files that meet the dataselection inclusion and exclusion rules. Pertains to regular filesonly. This number does not include the volume of special files,such as symbolic links or device special files.

Bytes selected on source

The number of selected files that are new compared to theprevious backup run. Pertains to regular files only. This numberdoes not include the number of special files, such as symboliclinks or device special files.

Files new on source

The total number of bytes for the selected files that are newcompared to the previous backup run. Pertains to regular filesonly. This number does not include the volume of special files,such as symbolic links or device special files.

Bytes new on source

The number of selected files that were modified compared tothe previous backup run. Pertains to regular files only. Thisnumber does not include the number of special files, such assymbolic links or device special files.

Files modified on source

The total number of bytes for the selected files that weremodified compared to the previous backup run. This numberdoes not include the volume of special files, such as symboliclinks or device special files.

Bytes modified on source

The number of files that were not modified since the last backupran.

Files not modified onsource

The total number of bytes for the files that remained unchangedsince the last backup ran.

Bytes not modified onsource

The number of files that were deleted since the last backup ran.Files deleted on source

The total number of bytes for the files that were deleted sincethe last backup ran.

Bytes deleted on source

Network:


Table 9-1 Lines in the Statistics tab for a backup job (continued)


The rate at which PureDisk backed up the total volume of sourcedata. If only a small amount of unique data needs to be backedup, this number is higher. If the source data has never beenbacked up to PureDisk before, the number is lower.

Backup speed

The total number of bytes of unique data that were transferredto the storage pool’s content routers after segmentation andcompression. Includes data related to special files. For specialfiles, PureDisk stores a special data object on the content routersto be able to restore these files.

Bytes transferred

Protected Data:

The number of selected files that were backed up correctly. Thisis the sum of new, modified, and nonmodified files that arecorrectly backed up and do not contain errors.

Source files backed up

The total number of bytes for the selected files that were backedup correctly.

For information about the relationship of this field to the Uniquebytes backed up field, see the Unique bytes backed up fielddescription.

Source bytes backed up

The number of selected files that PureDisk could not back up.Source files with errors

The total number of bytes for the selected files that PureDiskcould not back up.

Source bytes with errors

Time:

The date and time that the job started.Start date/time

The date and time that the job ended.Stop date/time

The amount of time that elapsed between when the job startedand when the job ended.

Backup time duration

Notes:

■ Table 9-1 shows the statistics for one job. However, the data mining reports,when run at the storage pool level, show the data reduction factor for thestorage pool. The storage pool data reduction factor in the data mining reportsrepresents the volume of all data ever backed up to that storage pool, in bytes,that is retained and currently available for restores versus the amount of bytesconsumed on the content routers.


222

The storage pool data reduction factor differs from the statistics because thestatistics in the table are generated for only one job.More information is available about the data mining reports.See “About Data mining reports” on page 233.

■ Several factors can affect the Bytes transferred statistic. The data selectionmay contain a huge number of small files or have very small segment sizes.In these cases, the bytes transferred can be much larger than the on-sourcevalues.

The following additional information applies to this statistic:

■ If the backup includes only special files, the "...on source" statistics show0 files selected because there were no regular files to back up, but the Bytestransferred statistic can be a large number.

■ Compression has the greatest effect on the Bytes transferred statistic. Ifyou enable compression, the Bytes transferred statistic is usually lowerthan the Bytesselectedonsource statistic. The Bytestransferred statisticmight be higher if the data being transferred cannot be compressed. Datathat cannot be compressed includes data that is already compressed suchas movies, files in JPEG format, files in MP3 format, or files in ZIP format.For files that are already compressed, the compression is ineffective andmight result in a slight increase of the data to be transferred.

■ For a repeated backup, the Bytes transferred statistic should be muchlower than Bytesselectedonsource. The Bytesselectedonsource statisticis the sum of all bytes present in the data selection. For an initial backup,if you disable compression, the Bytestransferred statistic is usually higherthan the Bytes selected on source statistic because of the overhead in theinternal data format.

■ The rate of data change on the client affects the Bytestransferred statistic.The Bytes selected on source represents the sum of all bytes in the entiredata selection. If the data change rate is 100% (for example, if all fileschanged or it is a first-time backup) and you disable compression, the Bytestransferred statistic is always higher. If the change rate is less than 100%,Bytes transferred statistic is lower.

■ The file size affects the Bytes transferred statistic. As a performanceenhancement, PureDisk always transfers files for which the content of filesis smaller than the segment size. In this case, PureDisk does not performa prior-existence check on the content routers. This is in contrast to backupsfor file content that is larger than the segment size. PureDisk alwaysperforms a prior-existence check for files that are larger than the segmentsize.


Consequently, if a data selection consists mainly of files smaller than thesegment size, the number of bytes transferred can be higher than expected.For example, if PureDisk backs up an identical set of files on two differentclients, it would be logical to expect that the bytes transferred would below for the second client because the files already exist on the contentrouter. This is not the case, however.

■ Segmentation size and file size affect the Bytes transferred statistic.PureDisk uses a special data format to store the data on its content routers.This data format has a per-segment overhead of a 22-byte header, a 12-bytetrailer, 16 bytes per block of 32 KB of data, and up to 7 padding bytes. Thepadding bytes enable PureDisk to align the data according to its internaldata format, which requires data to be aligned on an 8-byte boundary.For example, if you have a segment of exactly 128 KB, the total dataoverhead is 34 + (4 * 16) = 96 bytes. As another example, if the segment is128 Kb - 1 byte long, the total data overhead is 96 + 1 padding byte = 97bytes.If the segment is smaller than 32 KB, the number of overhead bytes canvary between (32 + 16) = 48 and (32 + 16 + 7) = 55 bytes. If you disableencryption, the header is 14 bytes long instead of 22.

Statistics for a restore jobTable 9-2 shows how to interpret the information in the Statistics tab for a restorejob.

Table 9-2 Lines in the Statistics tab for a restore job

MeaningStatistic

Restore Selection:

The total number of files and directories that PureDisk restored.The Directorycount statistic reports the number of directoriesrestored.

Total files

The total number of bytes in all files and directories thatPureDisk restored.

Bytes total

Target:


224

Table 9-2 Lines in the Statistics tab for a restore job (continued)

MeaningStatistic

The number of new files that reside on the client after therestore is complete. If you restore to the original directory andoverwrite the original files, PureDisk reports that there are nonew files. If you restore the files to a different directory for thefirst time, PureDisk reports that all the files you restored arenew files on the client.

Files new on target

The number of bytes occupied by the restored files. This statisticis the number of bytes consumed by the files that are noted inthe Files new statistic.

Bytes new on target

The number of files that are different on PureDisk storage whencompared to the target directory for the restore. This numbercounts the number of files on the client source that havedifferent content when compared to the files you restored.

Files modified on target

The number of bytes occupied by the files in the Filesmodifiedon target statistic.

Bytes modified on target

The number of files that are identical on both PureDisk storageand on the target directory. For example, if this value is 0, thismeans that all the files you restored have changed since theywere backed up.

Files unmodified ontarget

The number of bytes occupied by the files in the Filesunmodified on target statistic.

Bytes unmodified ontarget

Network:

The number of bytes actually restored. If nothing has beenreplaced, the value is 0.

Bytes received by agent

The average transfer rate during the transmission of uniquedata.

Average restore rate

Data Uniqueness:

The number of items that PureDisk wrote to the target computer.This statistic is a count of the number of files, directories, andspecial files. It includes only the items that were different onthe target computer as compared to PureDisk storage. If nothinghas changed, this value is 0.

Unique items restored

Number of unique items that were included in this restore job.The count excludes directories and special files.

Unique items received



MeaningStatistic

Restore Failures:

The number of errors that were generated during the restore.Error count

The number of files that generated errors during the restoreand could not be restored.

Files with errors

The total number of bytes represented in files that had an errorand could not be restored. For example, if a 1-MB file could notbe restored due to an error, this statistic is 1 MB.

Bytes with errors

The total number of errors encountered when the job attemptedto restore ACLs. This value can be nonzero for a variety ofreasons. For example, the following conditions, and others, cancause ACL restore errors:

■ An ACL could not be found on storage

■ A parent directory does not allow restore of ACLs.

ACL errors

The number of files for which verification failed. This field isapplicable only if you backed up the files with verificationenabled.

Verification failures

Restore Successes:

The number of all unique directories in the path to each file thatPureDisk restored. Even if you restore only one file from adirectory, PureDisk includes that directory in this statistic

For example, assume that you restore the file1 and file2 fromthe following paths:

■ /a/b/c/file1

■ /a/b/d/file2

In this case, the Directory count is 4.

Directory count

(Linux and UNIX systems only) The number of block andcharacter device files restored. This value is always 0 onWindows systems.

Devices

(Linux and UNIX systems only) The number of symbolic linksrestored. This value is always 0 on Windows systems.

Symbolic links

(Linux and UNIX systems only) The number of hard linksrestored. This value is always 0 on Windows systems.

Hard links


226


MeaningStatistic

(Windows systems only) The number of ACLs restored. Thisvalue is always 0 on Linux and UNIX systems.

ACL

The number of files for which verification succeeded. This fieldis applicable only if you backed up the files with verificationenabled.

Verification successes

Time:




Restore time duration

Statistics for a replication jobTable 9-3 shows how to interpret the information in the Statistics tab for areplication job. Most of the statistics in the table are also reported for a PDDOreplication job; the table notes exceptions.

Table 9-3 Lines in the Statistics tab for a replication job

MeaningStatistic

Source selection:

The number of data objects replicated to the target storage poolthat were not included in a previously replicated PureDiskbackup.

Items new in source dataselection

The number of bytes replicated to the target storage pool thathave not been included in a previous PureDisk backup.

Bytes new in source dataselection

The number of data objects replicated that have been modifiedsince the previous replication. This number counts the numberof data objects on the source that have different content whencompared to the files you replicated at an earlier time.

Items modified in sourcedata selection

The number of bytes occupied by the data objects in the Itemsmodified in source data selection statistic.

Bytes modified in sourcedata selection

The number of data objects that were deleted from the sourcedata selection since the last replication.

Items deleted in sourcedata selection


Table 9-3 Lines in the Statistics tab for a replication job (continued)

MeaningStatistic

The number of bytes occupied by the data objects in the Itemsdeleted in source data selection statistic. This statistic is thetotal number of bytes deleted from the source data selection.

Not included in PDDO replication statistics.

Bytes deleted in sourcedata selection

Errors:

The number of data objects that generated errors during thereplication process.


Items with replicationerrors

The number of bytes of data in theItems with replication

errors statistic that generated errors during the replicationprocess.


Bytes with replicationerrors

Replicated Data:

The number of files, directories, or data items replicated to thetarget storage pool.

Items replicated

The number of bytes replicated to the target storage pool.Bytes replicated

Network:

The number of bytes transferred to the target storage pool. Thisstatistic includes bytes included in any overhead that was neededfor the transfer.

Bytes transferred

Time:




Replication timeduration

Statistics for a PDDO backup jobTable 9-4 shows how to interpret the information in the Statistics tab for a PDDOjob.


228

Table 9-4 Lines in the Statistics tab for a PDDO job

MeaningStatistic

DataReduction:

The percentage of source data bytes that did not have to be transmitted tothe content routers because of data reduction. Higher numbers correlate tomore efficiency.

Global datareductionsaving

SourceSelection:

The total number of bytes scanned by PDDO from the backup.Bytesscannedduringbackup

The percentage of backup data that PureDisk found in the media server'scache.

Mediaservercache hitpercentage

Network:

The number of bytes of new, nondeduplicated data that PureDisk sent to thecontent router for storage.

Bytestransferredto contentrouter

Time:

The date and time that the job started.Startdate/time

The date and time that the job ended.Stopdate/time

The amount of time that elapsed between when the job started and when thejob ended.

Backuptimeduration

Files tab for a Job Details reportFor a backup job, the Files tab provides information on the files that PureDiskbacked up from the client.


If a data lock password is enabled on an agent, this tab prompts you for thepassword when you attempt to view it. For more information about the data lockpassword, see the PureDisk Client Installation Guide.

The following information appears on this tab:

The name of the agent from which the data selection was backed up.Agent

The name of the data selection.Data selection

Specifies the folder that contains the file on the client.Folder

The name of the file that PureDisk backed up.File

The size of the file that PureDisk backed up.Size

The date and time that the file was last modified. Also see the Enablechangedetection backup feature. For more information about specificbackup features, see the PureDisk Backup Operator’s Guide.

Modified

A link you can click to restore the file.Download

This screen contains no information when PureDisk does not back up any files.This situation is possible for an incremental backup if files have not changed.

Tip: You can restore a file by clicking a Download link in the Download column.

Errors tab for a Job Details reportFor a backup job, the Errors tab provides a list of files that PureDisk did not backup due to reasons such as the file was open for editing or the file was deleted inbetween job steps. This tab does not display error messages that indicate why thejob failed.

If a data lock password is enabled on an agent, PureDisk prompts you for thepassword when you attempt to view the Errors tab. For more information aboutthe data lock password, see the PureDisk Client Installation Guide.

Job log tab for a Job Details reportThe Joblog tab displays information about job processing and any errors PureDiskencountered during processing.

The PureDisk agent cannot upload log files that are larger than 5 MB. PureDisktruncates log files that are larger than 5 MB.


230

Job log tab for a backup jobJob logs are available for different types of jobs. If errors occur during the backup,PureDisk displays message codes in the Job log tab.

Table 9-5 shows the message codes that PureDisk displays for a backup job.

Table 9-5 Message codes for a backup job

RemarkDescriptionError code

The job is queued.QUEUED1

The job step completed successfully.SUCCESS2

The job step failed.ERROR3

The job step is running.RUNNING4

A job step is preparing to run.READY_TO_RUN5

The job step ran successfully butencountered nonfatal errors.

SUCCESS_WITH_ERRORS6

The user stopped the job step.ABORTED_BY_USER7

The PureDisk watchdog stopped thejob step after the job step timed out.

ABORTED_BY_WATCHDOG8

The job is running, but the currentjob step is on hold.

RUNNING_HOLD9

Not all required fields werecalculated.

INCOMPLETE10

This local file type is not supported.UNKNOWN_LOCALLY100

File not found.NONEXISTING_LOCALLY101

Access denied. An ACL does notpermit read access.

UNREADABLE_LOCALLY102

On a restore operation, this messagemeans that the disk is full. Otherwise,this means that a parent directorydoes not allow write access.

UNWRITABLE_LOCALLY103

The file is locked by another process.Applies to Windows clients only.

LOCKED_LOCALLY104


Table 9-5 Message codes for a backup job (continued)

RemarkDescriptionError code

Could not connect to the contentrouter.

CR_CONNECTION_ERROR200

PureDisk could not find the metadatafor this file in the metabase engine.

NONEXISTENT_ON_SP201

One of the following conditions ispresent:

■ A read error occurred on thestorage pool.

■ The data selection does not allowread permission. This agent doesnot have read permission.

UNRETRIEVABLE_FROM_SP202

One of the following conditions ispresent:

■ A write error occurred on thestorage pool.

■ The data selection does not allowwrite permission. This agent doesnot have write permission.

UNWRITABLE_TO_SP203

This error is the generic contentrouter error. For more information,see the agent or the server logs.

UNKNOWN_CR_ERROR204

Unused.MB_CONNECTION_ERROR300

See 201.NONEXISTENT_ON_MB301

See 202.UNRETRIEVABLE_FROM_MB302

See 203.UNWRITABLE_TO_MB303

Pdweb not running. Generic error log.For more information, see the agentor server logs.

UNKNOWN_MB_ERROR304

Job log tab for a restore jobThe job log of a restore job can contain the following misleading message for thegetfiles step:

Bandwidth limit set to 0 KB/s via agent configuration


232

The value of 0 indicates that no limit is set. It does not mean that no data istransferred.

Examining lengthy job logsPureDisk truncates job logs that exceed its maximum display length. If thishappens, perform the following procedure to display job information in anotherwindow.

To examine lengthy job output

1 Click the Job log tab.

2 Click Download Whole Job Log.

This link appears above the upper-right corner of the right column.

3 On the pop-up window that appears, specify the interface you want to use todisplay the file.

For the display method you choose, you might need to insert return charactersbecause the return characters might not appear correctly in the display.

In some cases, the job log might exceed the display length for this window.The job log includes log information at the beginning and at the end, whichenables you to see what happened when the job started and when the jobfinished. In this case, PureDisk deletes repetitive information from the middleof the job log report.

About Data mining reportsA data mining policy collects information about all the files in a PureDisk storagepool. When you run a data mining policy from the Web UI, PureDisk gathersinformation from the metabase server for all data selections. It then summarizesthe information in a table. This report uses data mining to extract and presentinformation in report format and in XML format.

A data mining report displays information as of the last time a data mining policyran. If you move an agent to a different department, the data mining reportsreflect the updated department after you run a data mining policy again.

For example, if you move agent AGENT1 from location OLD to location NEW and thenclick DataMiningReport, AGENT1 appears in OLD. If you run a data mining policyand then click Data Mining Report, AGENT1 appears in NEW.

PureDisk provides a default data mining policy, but you must edit this policy andenable it.

233ReportsAbout Data mining reports

The following describe how to edit, run, manipulate, and read data from datamining policies:

■ See “Enabling a data mining policy” on page 234.

■ See “Running a data mining policy manually” on page 236.

■ See “Obtaining data mining policy output - the data mining report” on page 236.


Enabling a data mining policyThe following procedure explains how to enable a data mining policy.

To enable a data mining policy


2 In the left pane, under Storage Pool Management Policies, click the plus (+)sign to the left of Data Mining.

3 Select System policy for data mining.


See “Completing the General tab for a data mining policy” on page 234.


See “Completing the Scheduling tab for a data mining policy” on page 235.


See “Completing the Parameters tab for a data mining policy” on page 235.

7 Click Save.

Completing the General tab for a data mining policyThe General tab lets you name and define the policy.


1 (Optional) Type a new name for this policy in the Policy name field.

You do not have to rename this policy.


This setting has the following options:

■ If you select Enabled, PureDisk runs the policy according to the schedulein the Scheduling tab.

ReportsEnabling a data mining policy

234

■ If you select Disabled, PureDisk does not run the policy according to theschedule in the Scheduling tab. This value is the default.For example, you can use Disabled if you want to stop running this policyduring a system maintenance period, but you do not want to enterinformation in the Scheduling tab to suspend, and then reenable, thispolicy.

3 (Optional) Specify an escalation procedure.

Select times in the Escalatewarningafter or the Escalateerrorandterminateafter drop-down boxes to specify the elapsed time before PureDisk sends amessage.

PureDisk can notify you if an update does not complete within a specifiedtime. For example, you can configure PureDisk to send an email message toan administrator if a policy does not complete in an hour.

If you select either of these options, create a policy escalation action thatdefines the email message, defines its recipients, and associates the escalationaction with the policy. For more information, see the PureDisk BackupOperator’s Guide.

Completing the Scheduling tab for a data mining policyFrom the Scheduling tab, use the drop-down lists to specify when the policy is torun.


◆ Specify the schedule details that define how frequently you want the policyto run.

Completing the Parameters tab for a data mining policyFrom the Parameters tab, use the radio button to specify the format of your report.

To specify a report format

◆ Choose a report format of Light (default) or Full.

These settings specify whether PureDisk includes file extension informationin the reports. File extensions include .mp3, .doc, .txt, and so on.

When the Light setting is in effect, the report does not contain file extensions.

When the Full setting is in effect, the report includes all file extensioninformation. The Full setting also increases the load on the storage pool,particularly the metabase engines.

235ReportsEnabling a data mining policy

Running a data mining policy manuallyPureDisk creates one job for each metabase engine when you run a data miningpolicy. The Web UI displays information for each job when it runs.

To run a data mining policy


2 In the left pane, under StoragePoolManagementPolicies, click the plus sign(+) to the left of Data Mining.

3 Select System policy for data mining.

4 (Conditional) Enable the policy.

You must enable a policy before you can run it. If the policy is disabled, onthe General tab, click Enabled and click Save.



For information about how to examine the output, see one of the following:

See “Obtaining data mining policy output - the data mining report” on page 236.

See “Obtaining data mining policy output - the Web service report” on page 239.

Obtaining datamining policy output - the dataminingreport

A data mining policy gathers statistics about the files in a storage pool. You canuse the following procedure to tabulate the statistics into a report.

To retrieve information for a storage pool or data selection from a data miningpolicy

1 Make sure that you have the correct permissions to create and view reports.The data mining report shows only the data selections a user is entitled toview.

See “Permissions and guidelines for running and viewing reports” on page 214.

2 Make sure that a data mining policy has been run.

You can run the policy manually or you can configure PureDisk to run thepolicy on a schedule.

For information about how to run a data mining policy, see the following:

See “Running a data mining policy manually” on page 236.

ReportsRunning a data mining policy manually

236


4 In the left pane, select the scope of the data mining report.

You can obtain a data mining report on one of the following levels:

■ A storage pool

■ A location

■ A department

■ A client

■ A data selection

5 Click Data Mining Report in the right pane.

6 (Optional) Click Select in history in the upper right corner.

Perform this step if you want to view a data mining report from an earlierdata mining workflow. By default, PureDisk displays data mining informationfrom the most recent run of the data mining workflow.

The following list explains some of the information in the data mining report:

The volume of backup data, in bytes, on the content routersin this storage pool.

The information in this field is updated every 15 minutes.The output in this field might not account for the data thatwas added to storage during the last 15 minutes.

During installation, the agents are stored on the storagepool. Consequently, if you run a data mining policy beforeany backups have run, the report indicates that a smallamount of storage is already in use.

Total Storage PoolVolume Used

The volume of all data ever backed up to this storage pool,in bytes, that is retained and currently available for restoresdivided by the global storage pool volume.

See “Interpreting the storage pool data reduction factor”on page 238.

Total Storage Pool DataReduction Factor

The volume of files, in bytes, in this data selection on thesource client. This number includes all versions of all files.

Total size on source

The estimated data volume, in bytes, stored on the storagepool’s content routers for this data selection. This statisticis the source size of this data selection divided by thestorage pool data reduction factor.

Storage pool volumeused

237ReportsObtaining data mining policy output - the data mining report

Interpreting the storage pool data reduction factorThe data mining report shows the storage pool data reduction factor. This valueshows how much disk space the files consume on the storage pool content routersrelative to the amount of disk space that the files consumed on primary storage.

In the data mining reports display, the storage pool data reduction factor can be1 or a value greater than 1, as follows:

■ If this factor is 1, the backed up source files consume the same capacity on thestorage pool content routers as on the source clients.

■ If this factor is greater than 1, this value is the factor by which PureDisk hasreduced the source volume through data reduction before it writes to thecontent routers.

■ If this factor is less than 1, the backed up data consumes more space on thecontent routers compared to the backed up volume of the source files. Thiscan be due to compression and encryption overhead.

For example, assume that PureDisk backed up eight 10-MB files within a dataselection. The eight files had identical content, and this particular content is newto the storage pool. PureDisk determines that these identical files all have thesame fingerprint. Because they all have the same fingerprint, PureDisk storesonly one copy on the content routers.

The statistics are as follows:

■ The volume on source for this data selection is 8 X 10 MB = 80 MB (source size).

■ The volume on the storage pool for this data selection is 10 MB (storage poolsize).

■ The storage pool data reduction factor is 80/10 MB = 8.

Effect of compression on data reductionIf you enable compression for a data selection, the volume on the content routersis even lower, and the storage pool data reduction factor is higher.

Effects of segmentation on data reductionSegmentation affects data reduction because data reduction assumes that thesegment size for a file is the same every time you back it up. PureDisk might haveto re-segment a very large file every time it is backed up if the file grows or shrinksbetween backups. If the file is re-segmented over multiple backups, data reductionis less efficient.

ReportsObtaining data mining policy output - the data mining report

238

A smaller segment size can yield better data reduction rates. However, performancecan degrade because of the higher maintenance costs involved in managing alarger number of segments.

A larger segment size can yield better performance, but the data reduction ratecan degrade. Larger segments can also use a higher amount of disk space.

PureDisk considers the following factors when it segments the file:

■ The default segment size for the data selection type or the segment size youspecify.

■ The maximum number of segments allowed, which is 5,120 segments.

■ The maximum segment size allowed, which is 50 MB.

Obtaining datamining policy output - theWeb servicereport

After you run a data mining policy, you can display your output through the datamining Web service.

For information on how to obtain a data mining report, see the following:


To obtain a data mining Web service report, type the following into your browser:

https://url/spa/ws/ws_datamining.php?login=login&passwd=pwd&action=getReport&runid=num

Table 9-6 shows the arguments in the URL.

Table 9-6 Arguments in the data mining Web services reports

MeaningArgument

The URL for the storage pool authority. For example:100.100.100.100.

url

The storage pool authority administrator login. For example: root.login

The storage pool authority administrator password. For example:mypwd.

pwd

239ReportsObtaining data mining policy output - the Web service report

Table 9-6 Arguments in the data mining Web services reports (continued)

MeaningArgument

The number of the data mining policy run that you want to display inreport format. PureDisk retains the last 10 runs of the data miningworkflow.

For example, if you want to display the most recent policy run, specify1. If you want to display information from the policy run just beforethe most recent, specify 2. If you ran the data mining policy every dayfor the last 10 days and you want to display the oldest run, specify 10.

To verify the report output with data mining policy runs, compare thetimestamp in the header of the report with the times of your datamining policy runs.

num

When you run the Web service report to obtain data mining output, you retrieveinformation on all data selections in the storage pool. You cannot narrow thereport to include information for only one data selection.

Information about how to report on only one data selection is available.


For example, assume that you type the following URL:

https://valhalla.minnesota.com/spa/ws/ws_datamining.php?login=root&passwd=root&action=

getReport&runid=1

PureDisk returns output as follows:

This XML file does not appear to have any style information

associated with it. The document tree is shown below.

-<MBDatamining TimeStamp="2007-08-30 03:20:02 PM">

<filtre>*</filtre>

-<mbe_range_statistics>

-<mbe id="1">

-<dataselection id="4" dataselectionname="desktop" agentid="2"

agentname="TRAVELSCRABBLE" locationid="0" departmentid="0"

locationname="Unknown location" departmentname="Unknown department"

ostype="10">

<location name="Unknown location"/>

<department name="Unknown department"/>

<sizeOnSource_dataselection

unit="bytes">153405265</sizeOnSource_dataselection>

<sizeOnStoragePool_dataselection

unit="bytes">4176478208</sizeOnStoragePool_dataselection>

ReportsObtaining data mining policy output - the Web service report

240

-<ACCESSRANGE>

-<item id="-1 day">

<amountoffiles>13</amountoffiles>

<totalfilesize>33017267</totalfilesize>

</item>

-<item id="1 day-1 week">



</item>

-<item id="1 month-1 year">



</item>

-<item id="1 week-1 month">



</item>

</ACCESSRANGE>

-<MODRANGE>

-<item id="+1 year">



</item>

-<item id="-1 day">



</item>

-<item id="1 day-1 week">



</item>

-<item id="1 month-1 year">



</item>

-<item id="1 week-1 month">



</item>

</MODRANGE>

-<SIZERANGE>

-<item id="0-10KB">


241ReportsObtaining data mining policy output - the Web service report


</item>

-<item id="100KB-1MB">



</item>

-<item id="10KB-100KB">



</item>

-<item id="10MB-100MB">



</item>

-<item id="1MB-10MB">



</item>

</SIZERANGE>

-<TYPES>

-<item id="0">



</item>

</TYPES>

</dataselection>

</mbe>

</mbe_range_statistics>

-<dataselectionlist_SIS_reporting>

<global_storagepool_VOL

unit="bytes">4176478208</global_storagepool_VOL>

<global_storagepool_SIS>0.03673077108511</global_storagepool_SIS>

</dataselectionlist_SIS_reporting>

<MBDataminingHistory/>

</MBDatamining>

Web service reportsTo use the Web service reports you must type a URL into your browser to navigateto a Web service page. On this Web service page you enter login and passwordinformation, as well as a request for a specific report. The reports display in XML

ReportsWeb service reports

242

format. You can import the XML output to a spreadsheet. See the following sectionfor more information:

See “Importing report output into a spreadsheet” on page 249.

Caution: For security reasons, use a Web browser that uses POST requests, notGET requests, when retrieving Web service reports. For example, MicrosoftInternet Explorer does not use POST requests and is not secure.

You can also follow your spreadsheet’s instructions for importing the XML data.

For example, the following URL contains login information, password information,and a request for information about successful job runs:

https://100.100.100.100/spa/ws/ws_getsuccessfuljobs.php?login=root&passwd=root

Note: The Web UI URL parameters are case sensitive. Make sure you type themexactly as shown in this chapter. The ampersand (&) character acts as a separatorfor the fields in the URL. The bracket characters in the following sections [ ]

represent optional URL fields.

The following sections describe reports that you can obtain through the Webservices:

■ See “Job status Web service reports” on page 243.

■ See “Dashboard Web service reports” on page 246.


Job status Web service reportsYou can obtain the following types of job status reports from the Web servicereporting tool:

Information about jobs that exit successfully.ws_getsuccessfuljobs.php

Information about jobs that exited with a status ofPartial success.

ws_getpartialjobs.php

Information about jobs that exited with a status ofFailed.

ws_getfailedjobs.php

The URL format for a Web service report on job statuses is as follows:

https://url/spa/ws/web_service?login=login&passwd=pwd[&filter][&filter]

243ReportsWeb service reports


Table 9-7 Arguments in the job status Web services reports

MeaningArgument


url

Specifies the type of Web service. The job status reportsgenerate information about successful, partiallycompleted, and failed jobs. Type one of the following:

■ ws_getsuccessfuljobs.php

■ ws_getpartialjobs.php

■ ws_getfailedjobs.php

web_service

The storage pool authority administrator login. Forexample: root.

login

The storage pool authority administrator password. Forexample: mypwd.

pwd

(Optional) One or more filters. If you specify a filter, thereport displays only the data that matches the filter. Ifyou specify more than one filter, use the ampersand (&)character to separate each filter. The filter names arecase sensitive.

See Table 9-8 on page 244.

filter

Table 9-8 shows the filters you can specify on a Web service URL for the job statusreports.

Table 9-8 Filters for job status reports

MeaningFilter

Returns only jobs from the specified location. Forexample: Brussels.

locationName=name

Returns only jobs from the specified department. Forexample: hr.

departmentName=name


244

Table 9-8 Filters for job status reports (continued)

MeaningFilter

Returns only jobs that have a job ID that is equal to orgreater than the job ID you specify.

To find a job ID, click Details in the right pane for a jobthat has finished. The ID is on the General tab.

For example: 465.

fromJobID=id

Returns only jobs that started on or after the specifieddate. For example: 06-30-2007.

fromDate=mm-dd-yyyy

Returns only jobs that ended on or before the specifieddate. For example: 10-05-2007.

toDate=mm-dd-yyyy

Returns only jobs for a particular workflow. To see thelist of possible values forname, click Manage>Policiesand observe the left pane of the Web UI. This paneshows the list of possible policies and workflows. Specifythe policy or workflow name as shown in the Web UI.

Examples:

■ Data Removal

■ MS Exchange Backup

Note: Specify the workflow name exactly as shown inthe Web UI. The name is case sensitive.

workflowName=name

For example, assume that you want to examine statistics for restore jobs. You canenter the following URL:

https://100.100.100.100/spa/ws/ws_getsuccessfuljobs.php?login=root&passwd=root&workflo

wName=Files and Folders Restore

The following shows partial output:

<?xml version="1.0" encoding="iso-8859-1" ?>

- <jobs>

- <job>

<jobID>2</jobID>

<agentID>1000000</agentID>

<agentName>SPA</agentName>

<locationName>my location</locationName>

<departmentName>my department</departmentName>

<executionStatusID>2</executionStatusID>

<executionStatusName>SUCCESS</executionStatusName>


<workflow>Restore Workflow</workflow>

<scheduledStartTime>1151762912</scheduledStartTime>

<startDate>1151762916</startDate>

<finishDate>1151762970</finishDate>

<dataselectionID>2</dataselectionID>

<dataselectionName>reroute</dataselectionName>

<statistics />

</job>

- <job>

<jobID>4</jobID>

<agentID>1000000</agentID>

<agentName>SPA</agentName>

<locationName>my location</locationName>

<departmentName>my department</departmentName>

<executionStatusID>2</executionStatusID>

<executionStatusName>SUCCESS</executionStatusName>

<workflow>Restore Workflow</workflow>

<scheduledStartTime>1151763438</scheduledStartTime>

<startDate>1151763439</startDate>

<finishDate>1151763545</finishDate>

<dataselectionID>2</dataselectionID>

<dataselectionName>reroute</dataselectionName>

<statistics />

</job>

.

.

.

The preceding output has been truncated at the end for inclusion in this manual.

If you run a report that contains information about backup jobs, the informationPureDisk returns contains the same statistics that you can obtain from clickingData Mining Report in the left pane after a data mining workflow was run.

Dashboard Web service reportsThis dashboard report includes status information for all PureDisk client agents,server agents, and services in the storage pool. This report includes all theinformation that PureDisk generates for the dashboard reports.

See “About Dashboard reports” on page 249.

You can write an application to parse or extract pieces of information from thisreport’s output and show that in a Web page as a custom dashboard. Theinformation for this report is not generated in real time. PureDisk refreshes the


246

data every 15 minutes. The timestamp is shown at the beginning of the XMLreport.

The report is formatted in XML. The URL format is as follows:

https://url/spa/ws/ws_dashboard.php?login=login&passwd=pwd&filterType=type&filterID=id

&action=getDashBoard

Note: Type the preceding URL on one continuous line.


Table 9-9 Arguments in the Web services reports

MeaningArgument


url

The storage pool authority administrator login. For example: root.login

The storage pool authority administrator password. For example:mypwd.

pwd

The type of record on which you want to filter.

Specify agent.

type

To obtain this number for an agent, complete the following steps:

■ Click the Manage > Agent.

■ In the left pane, select an agent.

■ In the right pane, click Agent Dashboard.

Depending on the agent you choose, you might need to pull downMore Tasks and select Agent Dashboard.

■ Visually inspect the right pane to obtain the agent number fromthe Agent ID field.

Tip: Obtain this id number before you start to type the URL for theWeb service report. If you begin to type the report URL into a browser’saddress field, and have to click in the PureDisk Web UI to retrieve thisid information, you lose the information you typed into the addressfield. Alternatively, you can also retrieve the id in a different window.

id

For example, assume that you want to obtain a dashboard Web service report foran agent. You can enter the following URL:

https://valhalla.minnesota.com/spa/ws/ws_dashboard.php?login=root&passwd=root&filterTy

pe=agent&filterID=3&action=getDashBoard


The following shows partial output:

<DashBoard TimeStamp="2008-03-15 09:43:37">

<StoragePoolID>33</StoragePoolID>

<Name>valhalla</Name>

<Description/>

<Location id="1">mn</Location>

<SystemDS id="1">System DS for STP 33</SystemDS>

<SelectedAgent/>

<SelectedLocation/>

<SelectedDepartment/>

-

<Agents>

-

<Agent id="33000000">

<ID>33000000</ID>

<IsServerAgent>1</IsServerAgent>

<HostName>10.80.139.49</HostName>

<Description/>

<OSVariant id="">Not available</OSVariant>

<OSExtensions/>

<Status id="2">ACTIVE</Status>

<IPAddress>10.80.139.49</IPAddress>

<OS id="20">Linux</OS>

<Version>6.5.0.8987</Version>

<Department id="1">qe</Department>

<Location id="1">mn</Location>

<MetabaseEngine id="1"

agentid="33000000">10.80.139.49</MetabaseEngine>

<Controller id="1" agentid="33000000">10.80.139.49</Controller>

<ConnectionStatus>Connected</ConnectionStatus>

-

<ConnectionDetails>

<FromIP>10.80.139.49</FromIP>

<SessionID>pdagent</SessionID>

<Sent unit="MB">45.11</Sent>

<Received unit="MB">1.34</Received>

<Version/>

</ConnectionDetails>

-

<Jobs>

-

<Job id="77">


248

<JobID>77</JobID>

<AgentID>33000000</AgentID>

<Workflow id="13500">Maintenance</Workflow>

<Policy id="8">System policy for Maintenance</Policy>

<PolicyRunID>28</PolicyRunID>

<Scheduled>2008-03-15 06:20:01</Scheduled>

<Start>2008-03-15 06:20:03</Start>

<Stop>2008-03-15 06:20:23</Stop>

<Status id="2">SUCCESS</Status>

</Job>

</Jobs>

<JobSteps/>

-

<Statistics id="33000000" TimeStamp="2008-03-15 09:30:01"

xml:base="/Storage/var/stats_33000000.xml">

-

.

.

.

The preceding output has been truncated at the end for inclusion in this manual.

Importing report output into a spreadsheetYou can import the XML formatted output from a PureDisk Web service reportinto a spreadsheet, such as a Microsoft Excel spreadsheet. These instructions arewritten in general terms. For more information, see your spreadsheet’sdocumentation.

To import Web service data into a Microsoft Excel spreadsheet

1 Use your Web browser to save the output as an XML file.

2 Import the data into your spreadsheet.

For example, in Microsoft Excel, specify Data>ImportExternalData>ImportData. When it prompts you, specify the file to which you saved the XMLoutput.

About Dashboard reportsDashboards provide quick reports on system status and activity. These reportsare status reports on node capacity, storage pool activity, and agents.

The following sections describe how to obtain these reports:

249ReportsAbout Dashboard reports

■ See “Displaying the Capacity dashboard” on page 250.

■ See “Displaying the Activity dashboard” on page 251.

■ See “Displaying the Server agent dashboard” on page 252.

■ See “Displaying the Client agent dashboard” on page 253.

Dashboard reports are available when a central reporting storage pool authorityis installed.

See “Central storage pool authority reports” on page 254.

Displaying the Capacity dashboardThe capacity dashboard shows information about total and used capacity on thecontent router and metabase engine. For a content router, this dashboard showsthe total amount of space available to the content router in /Storage/data, theamount of used disk space, and the number of data segments already stored onthe content router. For a metabase engine, this report shows the amount of diskspace used by the latest version records only, by all version records, and thepercentage of disk space used.

PureDisk generates and updates the information for the capacity dashboard every15 minutes. Therefore, if you check the capacity dashboard immediately after abackup completes, the information in the display might not reflect the conditionsthat result from that backup.

ReportsAbout Dashboard reports

250

To display the capacity dashboard



3 In the right pane, click Capacity Dashboard.

The following figure shows an example capacity dashboard.

Displaying the Activity dashboardThe activity dashboard contains information about the PureDisk services that arerunning on all of the nodes in your storage pool.

To refresh the data in this dashboard, press function key F5.


To display the activity dashboard



3 In the right pane, click Activity dashboard.

The following figure shows an example activity dashboard.

Displaying the Server agent dashboardThe server agent dashboard shows current activity on the server agents that resideon the storage pool nodes. It displays information about the last completed job,all current jobs, and all current job steps.


ReportsAbout Dashboard reports

252

To display the server agent dashboard



3 In the right pane, click Server agent dashboard.

The following figure shows an example server agent dashboard.

Displaying the Client agent dashboardThe agent dashboard shows information about running jobs and the jobs thatcompleted most recently on a selected department or a selected agent.


To display the agent dashboard


2 Expand the tree view in the left pane until the department or agent you wantdisplays.

Click the plus sign (+) next to each entity to expand the tree.


3 Select a department or agent.

4 Click Agent Dashboard in the right pane.

The following figure shows an example agent dashboard.

Central storage pool authority reportsIn a large PureDisk environment, you can configure multiple storage pools. Youcan configure one of these storage pools to be the central storage pool. You canenable this capability at installation time or at a later date.

From the central storage pool authority, you can generate and view licensing andcapacity reports for all the storage pools in your environment. For moreinformation, see the user authentication information in the PureDisk GettingStarted Guide.

For more information about central reporting and the central reportingdashboards, see the following:

■ See “Displaying the Central Reporting dashboard” on page 254.

■ See “Updating the Central Reporting dashboard” on page 259.

■ See “About central reporting” on page 300.

Displaying the Central Reporting dashboardThe following procedure explains how to retrieve a dashboard report that containslicensing and capacity information.

ReportsCentral storage pool authority reports

254

To retrieve licensing and capacity information

1 Verify that you have the Central Report permission.

Only users with Central Report permissions have rights to view and updatethe reports. For more information about permissions, see thePureDiskClientInstallation Guide.

2 Click Settings > Central SPA.

3 In the left pane, click Storage Pool Management.

4 In the right pane, click Central SPA Dashboard.

5 Click one of the following tabs in the dashboard display:

■ Enterprise License Report (default view).See “Enterprise License Report tab” on page 255.

■ Storage Pools.See “Storage Pools tab” on page 257.

■ Licenses / Features.See “Licenses \ Features tab” on page 257.

■ Capacity Usage Report.See “Capacity Usage Report tab” on page 258.

Enterprise License Report tabThe Enterprise License Report tab displays a quick overview of your licensestatus. Table 9-10 explains the columns on this tab.

255ReportsCentral storage pool authority reports

Table 9-10 Enterprise License Report tab content

Information or dataColumn heading

Lists each individual feature license and liststhe PureDisk edition license that is installedon this storage pool. Certain PureDiskfeatures require separate licenses.

The report lists each edition or license in itsown, separate row. There can be only onePureDisk edition. There can be more thanone feature license; for example: WindowsApplication & Database Pack, StandardAgent, and so on.

This dashboard report does not includeinformation about the PureDiskDeduplication Option (PDDO). If PDDO isenabled in this storage pool, you can retrievereporting data from the NetBackup mediaserver.

Storage Edition / Agents

For a feature license row, this column liststhe number of clients that can use thisfeature.

For the PureDisk edition row, this columnlists the amount of front end data, on theclient, that you can protect with PureDiskbackups.

Licensed

For a feature license row, this column liststhe number of clients that currently use thisfeature.

For the PureDisk edition row, this columndisplays the amount of front end, clientstorage that this storage pool currentlyprotects.

Used

Displays alerts under the followingconditions:

■ When the used capacity is greater thanthe licensed capacity.

■ When the number of features used isgreater than the number of featureslicensed.

Alerts


256

Storage Pools tabThe Storage pools tab displays the connectivity status of all storage pools thatare registered to the central storage pool. Table 9-11 explains the columns on thistab.

Table 9-11 Storage Pools tab content


The name of each registered storage pool.SPA Name

The PureDisk release level that is installedon each registered storage pool.

SPA Version

The address of each registered storage pool.FQDN

An icon that represents the connectivitystatus between each registered storage pooland the central storage pool.

Connectivity status

The number of valid license keys that areinstalled on the registered storage pool. Youcan install the same license key on multiplestorage pools, but this report lists each keyonly once.

Active License keys

Licenses \ Features tabFor each registered storage pool, PureDisk displays all installed licenses in theLicenses \ Features tab. PureDisk updates license keys with time restrictionsbefore it displays the tab. Unlike the Storage Pools tab, the Licenses \ Featurestab can display a license key more than once. Table 9-12 explains the columns onthis tab.

Table 9-12 Licenses \ Features tab content


The license key content.License key

The feature that is enabled by that key row.Feature

The license key expiration date. If this fieldshows that a particular license is due toexpire, contact your Symantec salesrepresentative.

Expiry


Table 9-12 Licenses \ Features tab content (continued)


The capacity that is enabled by that licensekey. If this field shows that a particularlicense capacity is about to be exceeded,contact your Symantec sales representative.

Capacity

The computer upon which you installed thelicense key.

Locations

To view a licenses and features report for a particular license type or all types

◆ Use the Filter on feature pull-down menu to select a license type.

Your choices are as follows:

■ All

■ Premium Infrastructure

■ Windows Application & Database Pack

■ Standard Agent

Capacity Usage Report tabThis report shows total capacity statistics. The Last updated on column of thisreport shows the date of the last update for each storage pool.Table 9-13 explainsthe columns on this tab.

Table 9-13 Capacity Usage Report tab content


The name of each registered storage pool.SPA Name

The date and time when the report data wascreated.

Last updated on

The amount of front end, client storage thatthis storage pool currently protects. Thiscolumn does not describe the amount ofstorage occupied by backup data in thePureDisk storage pool.

Used capacity

The number of backup and restore or storagepool agents deployed in this storage pool.

Standard Agents


258

Table 9-13 Capacity Usage Report tab content (continued)


The number of application program agentsdeployed in this storage pool.

Windows application and database pack

Updating the Central Reporting dashboardPureDisk updates the license data for these reports daily. If you click the updatelink in each report, PureDisk updates the data from all the storage pools that areconfigured under the central storage pool. For example, you might want to updatelicense data after you delete license keys or add additional keys to increase yourlicensed capacity.

The update can take considerable time. If PureDisk does not receive a responsefrom a storage pool within the configured time period, PureDisk marks the storagepool as temporarily unavailable. If a storage pool is temporarily unavailable,PureDisk includes the last available information in the report. All reports showthe date of the last update.

To view the latest information

◆ Click update from any report.



260

Log files and auditing


■ About the log file directory

■ Audit trail reporting

■ Setting debugging mode

About the log file directoryPureDisk writes log files to the following directory on each PureDisk node:

/Storage/log

For each seven-day interval, PureDisk retains up to 1000 lines of logging messagesin the active log file in /Storage/log. Note that log files from PureDisk servicesare often greater than 5 MB in length, but PureDisk does not retain job log filesthat are greater than 5 MB in length.

PureDisk uses the standard Linux log rotation mechanism to rotate the audit logevery seven days. Log rotation ensures that the log files do not become too large.PureDisk moves old logging information into separate files and compresses thefiles to save space. PureDisk does not remove old log files. You can examine theold log files in /Storage/log. The old files are named/Storage/log/audit.log.1.bz2, /Storage/log/audit.log.2.bz2, and so on.The last 1000 lines of every log file are always accessible in the /Storage/log

directory.

The following describe log files:

■ See “Content router log files” on page 262.

■ See “Metabase engine log file” on page 265.

■ See “Workflow engine log file” on page 268.

10Chapter

■ See “Server agent log files” on page 270.

■ See “About international characters in log files” on page 272.

Content router log filesAll content routers log files are located in the /Storage/log/spoold/ directory.The following describe the content router log files:

■ See “The spoold.log file” on page 262.

■ See “The storaged.log file” on page 263.

■ See “Logging and debugging options” on page 264.

The spoold.log filePureDisk writes all incoming connections to the content router in the/Storage/log/spoold/spoold.log log file.

Example 1. The following is an incoming multistream backup (pdbackup.exe)from a 32-bit Windows agent, version 6.6.0.6792 (192.168.163.1) for data selection7:

January 17 16:10:11 INFO [1076910400]: Task Manager: started task 0 [thread 1079552320]

for 192.168.163.1:1636

January 17 16:10:11 INFO [1079552320]: Remote is using libcr Version 6.5.0.6792, Protocol

Version 6.1 running on

WIN32. Agent pdbackup.exe requesting access for DataSelection ID 7

Example 2. The following shows the metabase engine (192.168.163.132 = MBE IP)requesting a POList (MBE-CLI application) from system data selection 1:


for

192.168.163.132:51050



Linux-x86_64. Agent MBE-CLI requesting access for DataSelection ID 1

If you want an overview of all incoming single-stream backups (PutFiles), you cansearch the spoold.log file, as follows:

PureDisk:/Storage/log/spoold # grep -B 1 PutFiles spoold.log

Log files and auditingAbout the log file directory

262


for 192.168.163.1:3738



WIN32. Agent PutFiles requesting access for DataSelection ID 1

--


for 192.168.13.41:4438




--


for 192.168.163.14:1638




--


for 192.168.163.1:2201




In the preceding grep(1) command, the -B 1 parameter specifies to show the linebefore the match, so the connecting client IP address is also displayed.

The storaged.log filePureDisk records processing information related to the content router spoolerqueue, the content router database, and the /Storage/data directory in the/Storage/log/spoold/storaged.log log file.

For each transaction log, PureDisk logs the number of actions per type. Forexample:

August 25 14:58:45 INFO [1077967168]:

Queue processing triggered by external request.

August 25 14:58:45 INFO [1077967168]:

Starting sort of tlog file range 521 - 525.

August 25 14:58:45 INFO [1077967168]:

Finished sort of tlog file range 521 - 525 in 0 seconds.

263Log files and auditingAbout the log file directory

August 25 14:58:45 INFO [1077967168]:

Preparing to process transaction log /Storage/queue/sorted-521-525.tlog

August 25 14:58:45 INFO [1077967168]:

Synchronization for transaction log /Storage/queue/sorted-521-525.tlog started,

14306 transactions pending.

August 25 14:58:49 INFO [1077967168]:

Number of data store commits: 225

August 25 14:58:49 INFO [1077967168]:

Time required to build index on objects2 table: 0.211361

August 25 14:58:49 INFO [1077967168]:

Time required to drop objects table: 0.013812

August 25 14:58:49 INFO [1077967168]:

Time required to rename objects2 table to objects: 0.000773

August 25 14:58:49 INFO [1077967168]:

Transaction log 521-525 Completed. Expect: 14306 (0.82MB) Commit: 14306 (0.00MB) Retry: 0

Log: /Storage/queue/sorted-521-525.tlog SO: Add 0, Ref Add 14298, Ref Add Fail: 0,

Ref Del 0 DO: Add 0, Ref Add 0, Ref Add Fail: 0, Ref Del 4 TASK: Add 2, End 2, End All 0,

Del 0 DCID: SO 0, SO Fail 0, DO 0, DO Fail 0 MARKER: 0, Fail 0

August 25 14:58:49 INFO [1077967168]: Update last committed tlogid from 520 to 525

August 25 14:58:49 INFO [1077967168]: Start processing delayed operations of

'/Storage/queue/sorted-521-525.delayed'.

August 25 14:58:49 INFO [1077967168]: Completed processing of delayed operations of

'/Storage/queue/sorted-521-525.delayed'.

Logging and debugging optionsIf you want to increase logging in all content router log files, modify the contentrouter configuration file. For information about how to change configuration files,see the following:



264

To increase logging in all content router log files

1 In the PureDisk administrator Web UI, click Settings > Configuration >ConfigurationFileTemplates>PureDiskContentRouter>DefaultValueSetfor PureDisk ContentRouter > Logging > Logging.

2 Change the All OS: value to full,thread.

3 Type the following command to restart the content router:

# /etc/init.d/puredisk restart pdcr

If you want to specify that the log files include more information, include the--trace parameter when you restart the content router. For example:

# /etc/init.d/puredisk stop pdcr

# /opt/pdcr/bin/spoold --trace /Storage/log/spoold/trace.log

If you specified the --trace parameter, later you can specify the followingto disable tracing:

# /etc/init.d/puredisk restart pdcr

Metabase engine log fileThe metabase engine log file is located in /Storage/log/mbe.log.

Most of the information logged in the mbe.log file is related to the activity ofimporting information into the metabase engine database. Each metabase importis defined by a task ID, which consists of the data selection ID and the job stepstart time. For example,[Task [4-1200200137663]] is an import for data selection4, started on Sat Jan 12 22:55:37 2008, which is a converted UNIX time stamp.

The following example mbe.log file lists imports:

Sat Jan 12 22:51:33 CST 2008 <INFO> [Task [2-1200199892625]]

(DISPATCHER) Dispatcher has set a task to approved.


(DOWNLOAD 0) Download: A job has arrived!


(DOWNLOAD 0) Download: finished!





(SORT0) Starting sort for /Storage/tmp/pre57295.tmp




(SPLIT0) Starting to split


(SPLIT0) Splitting file


(SPLIT0) Generating dirfile


(SPLIT0) Done converting




(IMPORT0) ImportThread has work to do.


(IMPORT0) ImportThread going to import /Storage/tmp/bulkInsert57297


(IMPORT0) ImportThread going to import a raw POlist




(IMPORT0) Import done




(EVAL0) Evaluating DataSelection 2.


(EVAL0) No duplicate or minor PO's were detected.


(EVAL0) DataSelection 2 succesfully evaluated.

Sat Jan 12 22:51:55 CST 2008 <INFO> (DEPARTSERVLET) Task has

completed:Task [2-1200199892625]




(DOWNLOAD 0) Download: A job has arrived!


(DOWNLOAD 0) Download: finished!




(SORT1) Starting sort for /Storage/tmp/pre57303.tmp


266




(SPLIT0) Starting to split


(SPLIT0) Splitting file


(SPLIT0) Generating dirfile


(SPLIT0) Done converting




(IMPORT0) ImportThread has work to do.


(IMPORT0) ImportThread going to import /Storage/tmp/bulkInsert57305






(IMPORT0) Import done




(EVAL0) Evaluating DataSelection 4.


(EVAL0) No duplicate or minor PO's were detected.


(EVAL0) DataSelection 4 succesfully evaluated.

If your log file is large, you can search for the information you want. For example,type the following command to display all imports for data selection 7:

PureDisk:/Storage/log # grep 'Task \[7-' mbe.log

The metabase engine disk evaluator logs disk usage every 5 minutes. For example:

Thu Jan 17 17:28:57 CST 2008 <INFO> (DISKEVALUATOR0)

Evaluating left disk space


Diskspace used on partition with the metabase database is: 28.0%.


Diskspace used on partition with metabase tmp folder is: 28.0%.


Workflow engine log filePureDisk writes all workflow engine job, job step, and watchdog actions to file/Storage/log/pdwfe.log. The following describe the workflow engine log file:

■ See “The pdwfe.log file” on page 268.


The pdwfe.log fileThe following is an example log file:

Thu Jan 17 2008 14:07:16.948539 INFO (1075325248):

Agent 'PureDisk' (id: 379000000): no jobstep found

Thu Jan 17 2008 14:08:17.142203 INFO (1074268480):


Thu Jan 17 2008 14:09:19.524282 INFO (1074796864):


Thu Jan 17 2008 14:10:02.150714 INFO (1075853632):

Run Policy 'scheduled' (id :106)

Thu Jan 17 2008 14:10:02.178834 INFO (1075853632):

Job 24: Created 'Files and Folders Backup' for Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:02.782948 INFO (1075325248):

Job 24: Return Jobstep 'PrepareBackup.php' (id: 155) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:07.152421 INFO (1074268480):

Job 24: Update status of jobstep 155 from RUNNING to SUCCESS

Thu Jan 17 2008 14:10:07.703998 INFO (1074796864):

Job 24: Return Jobstep 'ScanFilesystem.php' (id: 156) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:08.499284 INFO (1075853632):

Agent 'ros2pc00' (id: 2): no jobstep found

Thu Jan 17 2008 14:10:09.478683 INFO (1075325248):


Thu Jan 17 2008 14:10:09.980596 INFO (1074268480):

Job 24: Return Jobstep 'PutFiles.php' (id: 157) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:10.784255 INFO (1074796864):

Agent 'ros2pc00' (id: 2): no jobstep found

The pdwfe.log file contains information about the following common workflowengine actions:

■ About the watchdog:

Thu Jan 17 2008 14:00:47.645449 INFO (1093708096): Running watch dog.

Thu Jan 17 2008 14:00:47.649075 INFO (1093708096): Watchdog Run successful.


268

■ About agents when they request the next job step (nextJobStep web service):

Thu Jan 17 2008 14:05:16.667128 INFO (1074796864):


■ About job steps distributed over agents:

Thu Jan 17 2008 14:10:02.782948 INFO (1075325248):

Job 24: Return Jobstep 'PrepareBackup.php' (id: 155) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:07.152421 INFO (1074268480):


You can retrieve log information related to a single job. For example, to obtainworkflow engine log information related to job ID 24, type the following command:

PureDisk:/Storage/log # grep 'Job 24' pdwfe.log

Thu Jan 17 2008 14:10:02.178834 INFO (1075853632): Job 24:

Created 'Files and Folders Backup' for Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:02.782948 INFO (1075325248): Job 24:

Return Jobstep 'PrepareBackup.php' (id: 155) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:07.152421 INFO (1074268480): Job 24:

Update status of jobstep 155 from RUNNING to SUCCESS

Thu Jan 17 2008 14:10:07.703998 INFO (1074796864): Job 24:

Return Jobstep 'ScanFilesystem.php' (id: 156) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:09.478683 INFO (1075325248): Job 24:


Thu Jan 17 2008 14:10:09.980596 INFO (1074268480): Job 24:

Return Jobstep 'PutFiles.php' (id: 157) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:11.406297 INFO (1075853632): Job 24:

Update Variables

Thu Jan 17 2008 14:10:11.411698 INFO (1075853632): Job 24:

Update Variables

Thu Jan 17 2008 14:10:11.739674 INFO (1074268480): Job 24:

Update Variables

Thu Jan 17 2008 14:10:12.770142 INFO (1074796864): Job 24:

Update Variables

Thu Jan 17 2008 14:10:12.974254 INFO (1075325248): Job 24:

Update Variables

Thu Jan 17 2008 14:10:12.998051 INFO (1075325248): Job 24:

Update Variables

Thu Jan 17 2008 14:10:14.314949 INFO (1074268480): Job 24:

Update status of jobstep 157 from RUNNING to SUCCESS_WITH_ERRORS


Thu Jan 17 2008 14:10:14.674194 INFO (1074796864): Job 24:

Return Jobstep 'MBImportAction.php' (id: 158) to Agent 'PureDisk' (id: 379000000)

Thu Jan 17 2008 14:10:24.548564 INFO (1074796864): Job 24:

Update Variables

Thu Jan 17 2008 14:10:24.732565 INFO (1075325248): Job 24:

Update Variables

Thu Jan 17 2008 14:10:25.044541 INFO (1075853632): Job 24:


Thu Jan 17 2008 14:10:25.428563 INFO (1074268480): Job 24:

Return Jobstep 'ProcessJobStatistics.php' (id: 159) to Agent 'PureDisk' (id: 379000000)

Thu Jan 17 2008 14:10:26.186136 INFO (1075325248): Job 24:

Update Variables

Thu Jan 17 2008 14:10:26.602925 INFO (1075853632): Job 24:


Thu Jan 17 2008 14:10:27.153563 INFO (1074796864): Job 24:

Return Jobstep 'FinishBackup.php' (id: 160) to Agent 'ros2pc00' (id: 2)

Thu Jan 17 2008 14:10:29.298115 INFO (1075853632): Job 24:


Thu Jan 17 2008 14:10:29.504469 INFO (1085315392): Job 24:

Process Workflow Engine Job Step 'markexit' (id :161)

Thu Jan 17 2008 14:10:29.514389 INFO (1085315392): Job 24:

Workflow Engine: Step 161 returns SUCCESS

Logging and debugging optionsYou can increase the amount of information that PureDisk writes to/Storage/log/pdwfe.log. To increase the amount of logging information thatPureDisk writes, log into the storage pool authority and type the followingcommands:

# /etc/init.d/puredisk stop pdworkflowd

# /opt/pdwfe/bin/pdwfe --trace

Server agent log filesPureDisk logs all server agent actions to /Storage/log/Agent.log. PureDisk logsall job step logs to /Storage/tmp/workflow.XXXX, where XXXX is the job stepID. The following describe the server agent log files:

■ See “The Agent.log file” on page 271.

■ See “The job step log” on page 271.



270

The Agent.log fileThe following is an example of an Agent.log file:

Thu Jan 17 2008 16:10:23.899687 INFO (1074796864):

Incoming request: kick

Thu Jan 17 2008 16:10:24.512531 INFO (1080609088):

Jobstep: ProcessJobStatistics.php

Thu Jan 17 2008 16:10:24.512951 INFO (1080609088):

Logfile path: '/Storage/tmp/workflow.172'

Thu Jan 17 2008 16:10:25.053758 INFO (1080609088):

Updating status for job step #172

Thu Jan 17 2008 16:10:25.054380 INFO (1080609088):

Upload logfile /Storage/tmp/workflow.172 (1382 bytes) using SPA webservice.

Thu Jan 17 2008 16:10:25.575934 INFO (1080609088):

Jobstep 172 successfully set to status 2

Thu Jan 17 2008 17:10:15.702997 INFO (1074268480):

Incoming request: kick

Thu Jan 17 2008 17:10:16.433983 INFO (1077438784):

Jobstep: MBImportAction.php

Thu Jan 17 2008 17:10:16.434432 INFO (1077438784):

Logfile path: '/Storage/tmp/workflow.178'

Thu Jan 17 2008 17:10:25.277339 INFO (1077438784):

Updating status for job step #178

Thu Jan 17 2008 17:10:25.278032 INFO (1077438784):

Upload logfile /Storage/tmp/workflow.178 (1445 bytes) using SPA webservice.

Thu Jan 17 2008 17:10:25.806503 INFO (1077438784):

Jobstep 178 successfully set to status 2

In this example, there are two job steps processes: ProcessJobStatistics andMBImportAction. All log lines that relate to these job steps have the same threadID: 1080609088 for ProcessJobStatistics and 1077438784 for MBImportAction.

The job step logEach job step that runs creates a job step log on the local agent. This log file isloaded in the administrator Web UI for the job details. The following procedureexplains how to find information about a job step.


To find a job step ID for a running job


2 In the right pane, click the number in the Job Id column that corresponds tothe job that contains the job step that you want to examine.

3 In the pop-up that appears, click the Details tab.

4 On the Details tab, click on the row that describes the job step you want toexamine.

5 On the left pane of the Details tab, note the jobid information.

If necessary, use the pull-down menu to select Normal (the default), Verbose,Very Verbose, or Show All to display differing amounts of information.

Logging and debugging optionsBy default, the PureDisk agent removes all job scripts and job logs when a job stepfinishes. If you want to retain these files on a particular client system, edit theagent.cfg file on that particular client.

The location of this file differs depending on your platform. For example, on aWindows client, agent.cfg is located in install_dir\ProgramFiles\Symantec\NetBackup PureDisk Agent\etc\agent.cfg. When you editthis file, go into the debug section, and set the debug parameter to 1.

About international characters in log filesThe PureDisk log files contain up to 1000 international characters under thefollowing conditions:

■ If you use international characters to specify names, descriptions, and otherlabels in the storage pool

■ If the PureDisk agent is installed on a localized client

PureDisk displays these characters correctly when you view log files, such as joblogs, through the Web UI. You can view the server logs stored in /Storage/log

on a PureDisk node. However, you might need to make some configuration changesdepending on where and how you want to view these log files.

These configuration changes are as follows:

■ If you log on to the PureDisk node with a secure shell connection (SSH) onLinux or UNIX, make sure you use a UTF-8 locale. For example, useen_US.UTF-8.


272

■ You can log on to the PureDisk node with a Windows terminal client such asPutty. Ensure that the terminal client uses the UTF-8 character set and a fontthat contains the international characters that you need to display.

■ If you log on to the PureDisk node directly through the console, PureDisk doesnot display international characters properly. Use one of the previous methodsto view log files with international characters.

Audit trail reportingThe audit trail report shows a list of users and storage pool activities. You mustbe logged in as root to retrieve audit log information.

Figure 10-1 Example audit trail report

273Log files and auditingAudit trail reporting

To generate an audit trail report


2 In the left pane, select World.

3 In the right pane, click Show Audit Trail or Download Audit Trail.

Alternatively, you can click ShowAuditTrail and then click DownloadAuditTrail if you decide later that you want to download the information.

The following information pertains to the output formats available to youfrom the right pane:

■ If you click Download Audit Trail, follow the instructions in the dialogboxes that appear. PureDisk downloads the report to a compressed filethat ends in .tgz.

■ If you click Show Audit Trail, the audit trail appears in the right pane.The following three icons appear above the Object Name column:

■ The printer icon. If you click the printer icon, follow the instructionsin the dialog boxes that appear to select a printer and send the reportto that printer.

■ The spreadsheet icon. If you click the spreadsheet icon, a dialog boxappears. Click OK. Follow the instructions in the next dialog box towrite or save these files.

■ The refresh button.

Setting debugging modeWhen you enable debugging mode through the PureDisk Web UI, a PureDisk agentprovides detailed log information on that client agent or server agent. Also, whenenabled, temporary scripts and log files remain in place on a client agent or serveragent. Typically, PureDisk removes these files after they are no longer needed,but when you enable debugging mode, PureDisk leaves them in place. For example,you can enable debugging mode to troubleshoot failing jobs for a particular clientagent.

Typically, Symantec CFT or technical support requests that you enable thiscapability in the storage pool while troubleshooting. Do not enable debuggingmode for general use.

The following procedures explain how to use debugging mode:

■ See “Enabling debugging mode” on page 275.

■ See “Disabling debugging mode” on page 276.

Log files and auditingSetting debugging mode

274

■ See “Removing temporary debugging files” on page 276.

Enabling debugging modeThe following procedures explain how to enable debugging mode on a client agentor on a server agent.

To enable debugging mode on a client agent


2 In the left pane, select the agent for which you want to enable debug mode.

3 In the right pane, pull down More Tasks, and select Set Debug Mode.

4 Run the job that you want to troubleshoot.

5 Analyze the log files.

The location of the temporary debugging files depends on your platform, asfollows:

■ On Windows platforms, PureDisk writes debugging files toinstall_dir\Symantec\NetBackup PureDisk Agent\tmp. For example,C:\ Program Files\Symantec\NetBackup PureDisk Agent\tmp.

■ Linux, UNIX, or MacOS, PureDisk writes debugging files to/opt/pdagent/tmp.

6 Disable debugging mode.

For information about how to disable debugging mode, see the following:

See “Disabling debugging mode” on page 276.

To enable debugging mode on a server agent


2 In the left pane, select the server agent for which you want to enable debugmode.

The node identifiers appear under the storage pool name. For example, ifthere are multiple server agents, multiple node identifiers appear under thestorage pool name in the left pane. The node identifier can be an FQDN, hostname, or IP address.

3 In the right pane, select Set Debug Mode.

4 Run the job that you want to troubleshoot.

275Log files and auditingSetting debugging mode

5 Analyze the log files in /Storage/tmp.

6 Disable debugging mode.

For information about how to disable debugging mode, see the following:

See “Disabling debugging mode” on page 276.

Disabling debugging modePerform the following procedure to disable debugging mode. If you restart anagent, that action also disables debugging mode.

To disable debugging mode on a client agent


2 In the left pane, select the agent for which you want to disable debug mode.

3 In the right pane, pull down More Tasks, and select Reset Debug Mode.

4 Remove the temporary debugging files.

For information about how to remove the temporary files, see the following:

See “Removing temporary debugging files” on page 276.

To disable debugging mode on a server agent


2 In the left pane, select the server agent for which you want to disabledebugging mode.

The node identifiers appear under the storage pool name. For example, ifthere are multiple server agents, multiple node identifiers appear under thestorage pool name in the left pane. The node identifier can be an FQDN, hostname, or IP address.

3 In the right pane, select Reset Debug Mode.

4 Remove the temporary debugging files.

For information about how to remove the temporary files, see the following:

See “Removing temporary debugging files” on page 276.

Removing temporary debugging filesBoth of the following procedures remove temporary debugging files from an agent.The second method takes more time and resources because it runs the Systempolicy for Maintenance on the storage pool.


276

To remove temporary files - method 1

1 Change to the directory that contains the temporary files.

The location of the temporary debugging files depends on your platform, asfollows:

■ On Windows platforms, PureDisk writes debugging files toinstall_dir\Symantec\NetBackup PureDisk Agent\tmp. For example C:\Program Files\Symantec\NetBackup PureDisk Agent\tmp.

■ Linux, UNIX, or MacOS, PureDisk writes debugging files to/opt/pdagent/tmp.

2 Use operating system commands to remove the temporary debugging files.

To remove temporary files - method 2


2 In the left pane, under Storage Pool Management Policies, expandMaintenance.

3 Select System policy for Maintenance.


This action runs the System policy for Maintenance on the entire storagepool, not just on the agent you debugged. The policy removes the scripts andthe temporary files that PureDisk writes to the agent during debugging.

277Log files and auditingSetting debugging mode


278

Storage pool management


■ About storage pool management

■ About adding services

■ Adding a service to a node

■ Activating a new service in the storage pool

■ Rerouting a content router and managing content routers

■ Deactivating a service

■ Managing license keys

■ About central reporting

■ Rerouting a metabase engine

■ About clustered storage pool administration

■ Changing the PDOS administrator’s password

■ Changing the PureDisk internal database and the LDAP administratorpasswords

■ Increasing the number of client connections

■ Adjusting the clock on a PureDisk node

■ Adjusting the Web UI time-out interval

■ Stopping and starting processes on one PureDisk node (unclustered)

■ Stopping and starting processes on one PureDisk node (clustered)

■ Stopping and starting processes in a multinode PureDisk storage pool

11Chapter

■ Restarting the Java run-time environment

About storage pool managementThe following describe how to perform tasks to manage stroage pool componentsand services:

■ See “About adding services” on page 280.


■ See “Activating a new service in the storage pool” on page 287.

■ See “Rerouting a content router and managing content routers” on page 288.

■ See “Deactivating a service” on page 296.

■ See “Managing license keys” on page 299.


■ See “Rerouting a metabase engine” on page 304.

■ See “About clustered storage pool administration” on page 310.

■ See “Changing the PDOS administrator’s password” on page 310.

■ See “Changing the PureDisk internal database and the LDAP administratorpasswords” on page 311.

■ See “Increasing the number of client connections” on page 311.

■ See “Adjusting the clock on a PureDisk node” on page 312.

■ See “Adjusting the Web UI time-out interval” on page 314.

■ See “Stopping and starting processes on one PureDisk node (unclustered)”on page 314.

■ See “Stopping and starting processes on one PureDisk node (clustered)”on page 317.

■ See “Stopping and starting processes in a multinode PureDisk storage pool”on page 318.

■ See “Restarting the Java run-time environment” on page 319.

About adding servicesYou might need to reconfigure your storage pool if your data protection needschange or if your PureDisk system reaches its capacity.

Storage pool managementAbout storage pool management

280

For example, you might need to add nodes or services. To determine when to addadditional services, perform the following tasks on a regular basis:

■ Examine events from the system monitor script.The system monitor script monitors system activity. By default, it runs everyfive minutes and sends a status message. To see the messages, click Monitor> Alerts & Notification. In the right pane, pull down Application, and typeMonitorStatistics in the Look for: field.

For more information, see the following:The PureDisk Backup Operator's Guide.

■ Display capacity dashboards.For more information, see the following:See “About Dashboard reports” on page 249.

For example, you might need to add the following additional services:

■ Metabase engine.One metabase engine service can support 1,000 clients. Add an additionalmetabase engine service if your site needs to support more than 1,000 clients.As you add new clients, PureDisk assigns them to the new metabase engine.It does not move clients from one metabase engine to another metabase engine.

■ Content router.Add an additional content router service if the /Storage/data partition fills.The system monitor script’s report and the capacity dashboard includeinformation on the disks that have reached their capacity. For more informationabout adding content routers and content router rerouting, see the following:See “Rerouting a content router and managing content routers” on page 288.

■ A NetBackup export engine.This service lets you send content router data to a NetBackup storage unit.

The following explain how to perform reconfiguration tasks:


■ See “Activating a new service in the storage pool” on page 287.

■ See “Rerouting a content router and managing content routers” on page 288.

■ See “Deactivating a service” on page 296.

■ See “Managing license keys” on page 299.


■ See “Rerouting a metabase engine” on page 304.

■ See “About clustered storage pool administration” on page 310.

281Storage pool managementAbout adding services

■ See “Changing the PDOS administrator’s password” on page 310.

■ See “Changing the PureDisk internal database and the LDAP administratorpasswords” on page 311.

■ See “Increasing the number of client connections” on page 311.

■ See “Adjusting the clock on a PureDisk node” on page 312.

■ See “Adjusting the Web UI time-out interval” on page 314.

Adding a service to a nodeYou can add a new service on a new, standalone node or on a node that presentlyhosts other services. The following explain how to add a new content router,metabase engine, or NetBackup export engine:

■ See “Adding a new service on an existing node” on page 282.

■ See “Adding a new node and at least one new service on the new node”on page 284.

■ See “Verifying and specifying content router capacity” on page 285.

■ See “Adding a new passive node to a cluster” on page 286.

For information about how to add services to an unclustered storage pool, see thefollowing:

Adding a new service on an existing nodeThe following procedure explains how to add a new service to an existing servicegroup on an existing node in a storage pool.

To add a new service on an existing node

1 (Conditional) Freeze the service group on the node to which you want to addthe new service.

Perform this step if the storage pool is clustered.

This action prevents VCS from failing over the node when it restarts theserver process. To freeze the node, use the Cluster Manager Java console.

2 In a browser window, type the following to start the storage pool configurationwizard:

http://URL/Installer

For URL, type the FQDN of the node that hosts the storage pool authorityservice.

Storage pool managementAdding a service to a node

282

3 Click Next on the wizard's pages until you arrive at the ServicesConfigurationpage.

4 On the Service Configuration page, perform the following steps:

■ Click Change.

■ Select the service you want to add.

■ Click Next when the Services Configuration page is complete.

5 Click Next until you arrive at the Implementation page.

6 On the Implementation page, click Finish.

7 (Conditional) Visually inspect the Cluster Manager Java Console Web UI andcheck for fault conditions.


VCS might have detected that the service is down. In this case, the resourcemight appear as faulted in the PureDisk Web UI.

If the resource appears as faulted, complete the following steps:

■ Right-click the resource and select Clear Fault - Auto.

■ After you clear the fault, the resource appears as Offline. Although it isstarted again, specify to VCS that you want it to monitor the resource. Toenable monitoring again, right-click the resource and select probe -node-name.

8 (Conditional) Visually inspect the Cluster Manager Java Console and makesure that all resources now appear with a status of Online.


9 (Conditional) In the Cluster Manager Java Console, right-click the servicegroup and select Unfreeze.


10 (Conditional) Verify that the service was added successfully.

Perform this step if you added a content router or a metabase engine.

Proceed as follows:

■ If you added a content router, see the following:See “Verifying and specifying content router capacity” on page 285.

■ If you added a metabase engine or a NetBackup export engine, see thefollowing:See “Activating a new service in the storage pool” on page 287.

283Storage pool managementAdding a service to a node

Adding a new node and at least one new service on the new nodeThe following procedure explains how to add a new node and a service.

When you add new nodes to a clustered storage pool, make sure to add them oneat a time.

To add a service to a new node

1 Install PDOS on the computer that you want to configure as a new node.

Use the instructions in the PureDisk Storage Pool InstallationGuide to installPDOS.




3 Click Next until you arrive at the Storage Pool Node Summary page.

4 Visually inspect the Storage Pool Node Summary page and determine if thenew node appears.

If the new node does not appear, click Add Node and add the node. Use theinstructions in the PureDisk Storage Pool Installation Guide to add the node.

5 Click Next until you arrive at the Storage Selection pages.

Use the instructions in the PureDisk Storage Pool Installation Guide toconfigure storage for this node. If no disks appear in the wizard, it might bebecause your disks need to be formatted or repartitioned.

6 Click Next until you arrive at the Services Configuration page.

Use the instructions in the PureDisk Storage Pool Installation Guide toconfigure services on this node.



9 (Conditional) If TCP/IP settings on the other nodes have been changed toimprove replication job performance, run the following script on the newnode:

# /opt/pdconfigure/scripts/support/tcp_tune.sh modify

10 (Conditional) Verify that the service was added successfully.

Perform this step if you added a content router or a metabase engine.


284

Proceed as follows:

■ If you added a content router, see the following:See “Verifying and specifying content router capacity” on page 285.

■ If you added a metabase engine or a NetBackup export engine, see thefollowing:See “Activating a new service in the storage pool” on page 287.

Verifying and specifying content router capacityPerform the procedure in this section under the following circumstances:

■ You added a content router to an existing storage pool.

■ You configured a new storage pool and your content routers have differentcapacities.

You do not need to perform this procedure if you added a metabase engine orNetBackup export engine.

PureDisk assumes that all content routers have the same storage capacity.However, you may have content routers each with different capacities. If you donot specify the content router capacities explicitly, the content router with thesmallest capacity fills up first. As a result, you must add another content routersooner.

To verify and specify content router capacity


2 In the left pane, expand the tree until you see all the content routers.

3 Select a content router.

4 In the right pane, visually inspect the Storage size (GB) field.

5 (Conditional) Specify the content router’s capacity in the Storage size (GB)field.

Perform this step if the displayed capacity is incorrect.

PureDisk uses the information in this field when it determines the fingerprintrange to assign to each content router. After you change this value, PureDiskredistributes the fingerprint ranges relative to the new capacity specifications.If the content routers already contain data, PureDisk redistributes the data,too.

6 Click Save to save your changes.

285Storage pool managementAdding a service to a node

7 Perform step 3 through step 6 for each content router in the storage pool.

8 Your next action depends on which type of service you changed or added, asfollows:

If you edited the information for an active content router, perform theprocedure in the following section:

See “Rerouting a content router and managing content routers” on page 288.

If you edited the information for the content routers that you installed aspart of a new storage pool, perform the procedure in the following section:


Adding a new passive node to a clusterPerform this procedure if you want to add an additional passive node to a cluster.The following procedure assumes that, as for all passive nodes, you do not intendto install any active services on this node. In this case, you want only to extendthe nodes available to the cluster for failover.

When you add new passive nodes to a clustered storage pool, make sure to addthem one at a time.

To add a new passive node to a cluster

1 Install PDOS on the computer that you want to configure as a new node.

Use the instructions in the PureDisk Storage Pool InstallationGuide to installPDOS.




3 Click Next until you arrive at the Storage Pool Node Summary page.

4 Visually inspect the Storage Pool Node Summary page and determine if thenew node appears.

If the new node does not appear, click Add Node and add the node. Use theinstructions in the PureDisk Storage Pool Installation Guide to add the node.

When the new node appears in the node summary, perform the followingsteps:

■ Select the node you want to configure as a passive node.


286

■ Click Edit Node.

■ In the Node Type pull-down menu, select Passive.

■ Click OK.



7 Type the following command to initialize the new passive node:

# /opt/pdinstall/prepare_additionalNode.sh addr[,addr,...]

For addr, type the IP address of the public NIC on the new node.

8 (Conditional) If TCP/IP settings on the other nodes have been changed toimprove replication job performance, run the following script on the nodeyou added:

# /opt/pdconfigure/scripts/support/tcp_tune.sh modify

9 Use the Cluster Manager Java Console to perform a manual failover to thenew node.

Symantec recommends that you test a manual failover to this new node at atime that is convenient in your schedule. When you perform a manual failover,your storage pool will be temporarily offline. See the instructions on how toperform a manual failover in the Veritas Cluster Server (VCS) documentation.

Activating a new service in the storage poolPerform this procedure to activate a new service in the storage pool.

To activate a new service in the storage pool


2 In the left pane, expand the tree view until you see the new service.

3 Select the new service.

4 In the right pane, click one of the following:

■ Activate Content Router

■ Activate Metabase Engine

■ Activate NetBackup Export Engine

If you added a new metabase engine or a new NetBackup export engine, youare finished. Do not complete the rest of this procedure.

287Storage pool managementActivating a new service in the storage pool

If you added a new content router, proceed to the next step.

5 (Conditional) If you added a new content router, confirm whether to reroutethe storage pool at this time.

Select one of the following options:

■ Yes, reroute now.This selection starts the rerouting process. Select this choice only afteryou activate all the content routers you intend to activate. You want toreroute only on time, and you want to reroute only after you activate allthe new content routers.

■ No, I want to continue making changes.If you select this choice, make your changes, activate additional contentrouters, and proceed to the following section:See “Rerouting a content router and managing content routers”on page 288.

Note: When you reroute the storage pool, PureDisk moves data betweencontent routers. This process requires some free storage space on each of thecontent routers. If a content router has no more storage available, yourrerouting might take much longer. Determine whether to run your dataselection removal policies and data removal policies to free some storagespace before you start the rerouting process.

6 (Conditional) Click OK.

Rerouting a content router and managing contentrouters

Rerouting distributes information to the content routers in a storage pool. Whenyou add a new content router, for example, you need to reroute all the storagepool's content routers in order to distribute the data evenly among the contentrouters.

The following sections provide information about planning content routers andrerouting content router data:

■ See “Planning for a new content router” on page 289.

■ See “Permissions for rerouting” on page 290.

■ See “Disaster recovery backups and rerouting” on page 290.

■ See “Data replication policies and rerouting” on page 290.

Storage pool managementRerouting a content router and managing content routers

288

■ See “Activating and deactivating content routers” on page 290.

■ See “Alleviating content router congestion” on page 291.

■ See “Parallel and serial rerouting examples” on page 292.

■ See “Rerouting the content routers” on page 294.

■ See “Troubleshooting a content router rerouting job” on page 295.

Planning for a new content routerAfter you add a new content router to a storage pool, you activate the new contentrouter and reroute the data on your content routers. The rerouting processredistributes the data evenly across all activated content routers in a storage pool.During the rerouting process, the content routers still send and receive data. Thesend/receive action can be done in parallel mode or in serial mode, as follows:

■ When parallel rerouting is performed, all content routers actively redistributedata simultaneously. Parallel rerouting is faster than serial rerouting, butparallel rerouting is not always possible.

■ When serial rerouting is performed, only one content router at a timeredistributes its data.

PureDisk’s ability to perform parallel rerouting depends on the following factors:

■ The current capacity of the content routers in the storage pool.If your content routers have very little excess capacity, PureDisk performsserial rerouting. PureDisk employs this method because it requires excesscapacity on each content router when it moves the data between contentrouters.If you receive warning messages from PureDisk about your content routercapacity, you can assume that the routers are near capacity. If your contentrouters are near capacity, PureDisk is more likely to perform serial routing.If your content routers are at a low capacity, PureDisk is more likely to performparallel rerouting. The excess capacity on the content routers allows PureDiskto move the data between content routers more efficiently.

■ The number of content routers you add to the storage pool.If possible, always add enough content routers to make parallel reroutingpossible. Generally, if you can double the number of content routers in a storagepool, you request parallel rerouting.For example, assume that you add only one content router to a storage poolthat contains three or more content routers. Each router is near capacity. Inthat case, PureDisk reroutes by using the serial method. However, if you addtwo or three content routers, you can request parallel rerouting. For moreinformation about rerouting, see the following:

289Storage pool managementRerouting a content router and managing content routers

See “Parallel and serial rerouting examples” on page 292.

Permissions for reroutingThe following permissions are required for a user to be able to reroute the contentrouters:

■ Topology management permission.

■ Activate & deactivate permission.

■ Reroute.

For information about permissions, see the PureDisk Client Installation Guide.

Disaster recovery backups and reroutingYou cannot run a disaster recovery backup while any content routers are in aninactive state. Before you add, activate, or deactivate a content router, considerwhether you want to perform a disaster recovery backup first.

Make sure the rerouting process completes before you run a disaster recoverybackup. Disaster recovery backups fail if any content router in the storage poolis in the inactive state.

Data replication policies and reroutingReplication jobs and content router rerouting jobs cannot run simultaneously. Ifyou start a replication job and then start a rerouting job, PureDisk stops thereplication job.

Activating and deactivating content routersIf you accidentally activate a content router, you do not have to reroute first. Aslong as the content router is in the Activationrequested state, you can deactivateit without rerouting.

Conversely, if you accidentally deactivate a content router, you can activate itwithout rerouting. However, the content router must still be in the Deactivationrequested state.

If the rerouting stopped for any reason, you need to correct the problem thatcaused the stoppage and restart the rerouting.

In this case, the content routers that you tried to activate or deactivate have oneof the following states:

■ Activation requested


290

You have requested activation of this content router, but have not yet startedrerouting.

■ Deactivation requestedYou have requested deactivation of this content router, but have not yet startedrerouting.

■ Activation pendingDuring rerouting, content routers that you have activated change from thestate "Activation requested" to "Activation pending" as soon as the actualrerouting of data starts.

■ Deactivation pendingDuring rerouting, content routers that you have deactivated change from thestate "Deactivation requested" to "Deactivation pending" as soon as the actualrerouting of data starts.

■ ActiveThis content router is active.

■ InactiveThis content router is inactive.

In this case, you can still make changes, either to activate or to deactivate thecontent router, before you start the rerouting process again. However, try to avoidsuch situations because they result in unnecessary data movement betweencontent routers.

Alleviating content router congestionPureDisk sends messages when the content routers start filling. These eventsappear when the system starts to fill up.

The following are the three message levels:

■ First level. The content routers have started to fill.

The Content Router is starting to run low on disk

space. Rerouting, data removal and/or garbage

collection is advised.

Message

■ Second level. Backups stop when the first content router in a storage poolreaches this level. This level is the warning threshold.


The Content Router has insufficient disk space to

accept new data. No new data will be accepted

until more disk space becomes available.

Rerouting, data removal and/or garbage collection

is needed urgently.

Message

■ Third level. Data from the spool area can continue to fill the content routerseven after the backups stop. The content routers are full.

The Content Router has insufficient disk space to

accept new data. No new data will be accepted

until more space becomes available. Rerouting,

data removal and/or garbage collection is needed

urgently. Manual intervention to temporarily free

disk space may become necessary.

Message

If your content routers fill up, perform one or more of the following actions:

■ First, run a data removal policy. If you know that you have a lot of unneededdata on the content router, this process frees up needed space. For informationon data removal policies, see the PureDisk Backup and Restore Guide.

■ Second, add another content router and reroute your data. Because you havefull content routers, this process is very slow. Use the procedures in thischapter, and perform this action if the data removal policy did not free upenough space.

■ Third, call Symantec technical support.

Parallel and serial rerouting examplesThe following summarizes the situations in which parallel and serial reroutingcan occur:

■ If you have little excess capacity in your content routers, PureDisk performsserial rerouting, regardless of how much more capacity you add.

■ If you have much excess capacity in your content routers and much newcapacity in the new content routers, Symantec recommends that you selectparallel rerouting.

While it is not possible to guarantee circumstances under which parallel reroutingalways occurs, the following provide example scenarios:

■ See “Example 1 - Serial rerouting scenario” on page 293.

■ See “Example 2 - Parallel rerouting scenario” on page 293.


292

■ See “Other rerouting examples” on page 293.

Example 1 - Serial rerouting scenarioAssume the following:

■ You have three 4-TB content routers. Their total maximum capacity is 12 TB.

■ Each content router is at 80% capacity. 9.6 TB of data reside on these threecontent routers. The routers have 2.4 TB of excess capacity today.

■ You want to add one more 4-TB content router.

In this case, the capacity you want to add (4 TB) is not significantly more than theexcess capacity that exists today (2.4 TB). PureDisk performs serial rerouting.

Example 2 - Parallel rerouting scenarioAssume the following:

■ You have four 500-GB content routers. Their total maximum capacity is 2000GB.

■ Each content router is at 50% capacity. 1000 GB of data reside on these fourcontent routers. The routers have 1000 GB of excess capacity today.

■ You want to add four more 500-GB content routers. These routers are toincrease the capacity of the storage pool by 2000 GB.

In this case, the capacity you want to add (2000 GB) is significantly more than theexcess capacity that exists today (1000 GB). Symantec recommends parallelrerouting.

Other rerouting examplesTable 11-1 shows some additional examples of parallel and serial reroutingsituations.

Table 11-1 Rerouting examples

Parallel or Serialrerouting?

Amount to addCurrent number ofcontent routers

Parallel11

Parallel1 or 22

Serial13 at high capacity

Parallel13 at low capacity


Table 11-1 Rerouting examples (continued)

Parallel or Serialrerouting?

Amount to addCurrent number ofcontent routers

Parallel2, 3, or 43

Serial14

Parallel44

Rerouting the content routersPerform this procedure if you added a new content router. This procedureredistributes the stored data over all the available, active content routers in thestorage pool.

To reroute data



3 Expand the storage pool until the PureDisk Web UI displays the content routeryou added.

4 Select the content router you added.

5 In the right pane, click Activate Content Router.

6 Specify whether you want to reroute now or later.

For example, respond Yes,reroutenow if you have added the last new contentrouter or the only new content router to this storage pool. Respond No,reroute later if you added more than one content router, and you need toactivate other new content routers.

7 (Conditional) In the left pane, select the storage pool.

Perform this step if the correct storage pool is not already selected.

8 (Conditional) In the right pane, click Reroute Content Router.

Perform this step if the correct storage pool was not already selected.


294

9 Wait for the rerouting process to complete.

This action redistributes the data across the content routers in the storagepool. PureDisk messages indicate whether you can perform parallel reroutingor serial rerouting. If possible, always choose parallel rerouting.

Rerouting can take some time to complete. For example, it can take severalhours to even several days, depending on the volume of data that needs tobe rerouted. If possible, keep other system activity, such as backup andremoval jobs, low during this activity.

Each content router receives a rerouting job. Look in the job table to makesure that all rerouting jobs complete successfully. If a job fails, analyze theproblem through the job log, correct the problem if possible, and retryrerouting as soon as possible. If the second try is unsuccessful, contact yourSymantec technical support representative.

10 (Optional) Enable an escalation action for the rerouting workflow.

Enable an escalation action if you want PureDisk to send you email if theworkflow does not complete in a reasonable amount of time.

For information about escalation actions, see thePureDiskBackupOperator'sGuide.


Perform a full disaster recovery backup at this time. Do not perform anincremental backup.

Troubleshooting a content router rerouting jobThe following procedure explains how to troubleshoot a failed rerouting job.

To troubleshoot a content router rerouting job

1 Retrieve the job log for the failed rerouting job.


■ Click Monitor > Jobs.

■ Click the job number of the failed rerouting job.

■ On the job details display, click Job Log.

2 Examine the job log for network errors or other environmental factors.


3 (Conditional) Fix external conditions.

If the job log noted network errors or environmental factors that contributedto the job's failure, remedy those conditions.

4 Rerun the rerouting job.

Even if there were no external conditions for you to remedy, run the job again.

If repeated efforts to remedy environmental problems and to run the jobsuccessfully have failed, please contact Symantec technical support.

Deactivating a serviceThe following procedure explains how to deactivate a content router or aNetBackup export engine in a storage pool. Other services cannot be deactivated.

Before you deactivate a content router, check the capacity of the other contentrouters in your storage pool. For information about how to check this capacity,see the following section:

Preparing to deactivate a content router

Preparing to deactivate a content routerAfter PureDisk deactivates a content router, it reroutes the storage pool todistribute the router’s data over the remaining content routers in the storagepool. Before you deactivate a content router, verify that there is enough storagespace on the remaining content routers to hold all the deactivated router’s data.Allow for a 10% to 20% margin.

If sufficient space is unavailable, do not deactivate the content router. Withoutsufficient space, the deactivation and subsequent rerouting fails. The failures canleave the entire storage pool in an inoperable state.

If you accidentally deactivate a content router but have not started rerouting yet,you can activate the content router again.

Use the following procedure to prepare for content router deactivation.

Storage pool managementDeactivating a service

296

To prepare to deactivate a content router

1 Display the capacity dashboard.

See “Displaying the Capacity dashboard” on page 250.

2 Review the following examples:

See “Example 1 - Content routers that can be rerouted” on page 297.

See “Example 2 - Content routers that cannot be rerouted” on page 297.

3 Examine the dashboard to determine whether remaining content routershave sufficient excess capacity to ensure that the rerouting can complete.

Example 1 - Content routers that can be reroutedAssume that you have a storage pool with the following three content routers:

■ Content router 1 has 1 TB capacity and is 60% filled. In other words, 600 GBare used, and 400 GB are free.



Option 1. Assume that you want to remove content router 2 by deactivating it andrerouting the storage pool. To reroute the storage pool, you must reroute the 1200GB of data on content router 2 to content routers 1 and 3. However, this approachcannot work because together content routers 1 and 3 have only 800 GB of freespace.

Option 2. Assume that you want to remove content router 3 or content router 1.For each of these content routers, ample free space exists on the remaining contentrouters to hold the 600 GB of data from the source.

Example 2 - Content routers that cannot be reroutedAssume that you have a storage pool with the following three content routers:




297Storage pool managementDeactivating a service

Assume that you want to remove content router 3 by deactivating it and reroutingthe storage pool. You must reroute and redistribute the 600 GB of data on contentrouter 3 to content router 1 and content router 2. Together, content router 1 andcontent router 2 have 600 GB free. The deactivation appears feasible. However,this plan is not feasible because the rerouting would fill each content router to100% capacity. The rerouting process requires that the host that receives the datahas a margin of excess capacity.

A content router always has an internal soft limit and an internal hard limit oncapacity. A content router requires a margin of excess capacity to function. Anotherreason for maintaining a margin is that the rerouting process is not always even.Content router 1 might receive 300 GB of data and reach its limit before contentrouter 2 received 100 GB of data. The rerouting process would fail even thoughcontent router 2 had excess capacity.

For more information about soft limits and hard limits, see the PureDisk BackupOperator's Guide.

Deactivating a content router or NetBackup export engineThe following procedure explains how to deactivate a content router or aNetBackup export engine.

To deactivate a service


2 Expand the tree in the left pane until you see the content router or NetBackupexport engine that you want to deactivate.

3 Select the service.

Warning: Ensure that sufficient capacity exists on the remaining contentrouters in your storage pool before you deactivate your content router andtry to reroute. Failure to ensure that the rerouting can complete might renderyour storage pool inoperable.

Before you proceed to the next step, ensure that you properly prepared todeactivate the content router.

See “Preparing to deactivate a content router” on page 296.

4 In the right pane, click DeactivateContentRouter or DeactivateNetBackupExport Engine.

For a content router, the status changes to Deactivation requested.

Storage pool managementDeactivating a service

298

For a NetBackup export engine, the status changes to Inactive. If youdeactivated a NetBackup export engine, proceed to the following step:

■ 8.

5 In the right pane, respond to the question about whether to reroute now orwhether you want to make more changes.

6 Select the storage pool.

7 In the right pane, click Reroute Content Router.

This selection starts the rerouting process, which redistributes data over allactive content routers. The process moves data from the content router inDeactivationrequested status to the content routers that you want to remainactive. Early in the rerouting process, the state of the content router changesfrom Deactivation requested to Deactivation pending. At the end of thererouting process, PureDisk sets its state to Inactive.

Wait for rerouting to complete successfully before proceeding to the nextstep.

For more information about the rerouting process, see the following:


8 (Conditional) Take offline the cluster group to which the active service belongs.

Perform this step only if the following are both true:

■ The storage pool is clustered.

■ This service is the only remaining active service on the node.


Managing license keysAfter you configure a PureDisk storage pool, you can add or change your PureDisklicense keys. If you configure a central reporting storage pool, you can see thelicense keys that are available for all storage pools in your configuration.

For more information about these reports and related central storage poolmanagement tasks, see the following:

See “Central storage pool authority reports” on page 254.

299Storage pool managementManaging license keys

To add a license key or view license key details


2 In the left pane, select License Management.

The right panel displays license key information. Continue with this procedureif you want to add a license key.

3 In the right pane, click Add Key.

4 In the Key field, type the license key.

5 Click Add.

If you try to add an expired license key, PureDisk generates the followingmessage:

Key not registered: No such file or directory

Check the expiration date for the key.

To delete a license key


2 In the left panel, expand License Management.

3 Select the license key that you want to delete.

4 In the right panel, click Delete Key.

5 To confirm the deletion, click OK on the window that appears.

About central reportingUsers with Central Report rights are allowed to add a storage pool or manage thelist of storage pools. For information about permissions, see the PureDisk ClientInstallation Guide.

If you enable central reporting, you can click Settings > Central SPA to retrievecentral reporting information. You can enable central reporting at installationtime, or you can use the following information to implement this feature at a laterdate:

■ See “Enabling a storage pool as a central storage pool” on page 301.

■ See “Adding a remote storage pool to a central storage pool” on page 301.

■ See “Disabling central reporting” on page 302.

■ See “Managing storage pools configured in the central storage pool” on page 303.

Storage pool managementAbout central reporting

300

Enabling a storage pool as a central storage poolThe storage pool configuration wizard lets you designate a storage pool as a centralstorage pool. From the central storage pool, you can add other storage pools tothe central storage pool’s reports. These reports contain information aboutlicensing and capacity.

After installation, you can use the procedure in this section to enable a storagepool as a central storage pool.

To designate a storage pool as a central storage pool

1 Make sure that the storage pool you want to designate as central is not alreadydesignated as a central storage pool.

Log on to the Web UI, click Settings and visually inspect the Web UI. If CentralSPA appears under Settings, this storage pool is already designated as acentral storage pool. Do not perform the remaining steps of this procedure.

If Central SPA does not appear under Settings, the storage pool is anindependent storage pool or a central storage pool manages it.

If you have a managed storage pool and you want to make it a central storagepool, you have the following choices:

■ You can disable the managed-to-central reporting relationship that iscurrently in effect.For the current central storage pool and for all of its managed storagepools, perform the procedure in the following section:See “Disabling central reporting” on page 302.

■ You can continue with this procedure and make this storage pool a centralstorage pool, too. A storage pool can be both a central storage pool andbe a storage pool that is included in another central storage pool’s reports.

2 Log on to the storage pool authority node as root.


# /opt/pdinstall/add_central_reporting.sh

4 Add one or more storage pools to this new central storage pool.

See “Adding a remote storage pool to a central storage pool” on page 301.

Adding a remote storage pool to a central storage poolThe following procedure explains how to add a remote storage pool to a centralstorage pool.

301Storage pool managementAbout central reporting

To add a storage pool to the central storage pool list

1 Make sure that the storage pool you want to use as a central storage pool isenabled as a central storage pool.

For information about how to designate a storage pool as a central storagepool, see the following:

See “Enabling a storage pool as a central storage pool” on page 301.


3 In the left pane, click Storage Pool Management.

4 In the right pane, click Add Remote SPA Entry.

5 Complete the following fields in right pane:

■ Storage pool name. The name of a storage pool that you want to manage.The storage pool you name here will be managed by the central storagepool.

■ Host name (FQDN). The FQDN (recommended) or host name of the storagepool authority service of the storage pool that you want to manage. Thisis the address of the other storage pool authority service.

■ Login. The login name of a valid user of the managed storage pool. Theuser must have Central Report rights.

■ Password. The password of that valid user of the managed storage pool.

6 Click Add.

When you add a storage pool, PureDisk queries for a list of other storagepools that are known (through replication) to that storage pool. PureDiskadds these linked storage pools to the central storage pool list.

Disabling central reportingUse the following procedure to disable central reporting.

To disable central reporting

1 Log on to the central storage pool authority node as root.


# /opt/pdinstall/del_central_reporting.sh

Storage pool managementAbout central reporting

302

Managing storage pools configured in the central storage poolThe following topics contain information about management tasks you mightneed to perform when you have a central storage pool:

■ See “Editing or deleting a storage pool in the central storage pool list”on page 303.

■ See “Starting the PureDisk Web UI for another storage pool in another window”on page 303.

■ See “Testing connections between storage pools” on page 304.

Editing or deleting a storage pool in the central storage poollistThe following procedures explain how to edit or delete a storage pool.

To edit a storage pool in the central storage pool list


2 In the left pane, select a storage pool.

3 Edit the fields.

4 Click Save.

To delete a storage pool from the central storage pool list



You cannot delete the central storage pool.

3 In the left pane, click Delete Remote SPA Entry.

Starting the PureDisk Web UI for another storage pool inanother windowThe following procedure explains how to start the PureDisk Web UI for anotherstorage pool. The two storage pools must be in a managed-to-central relationship.

To start the PureDisk Web UI for another storage pool in another window



3 In the right pane, select Manage Storage Pool.

4 Type the login and password to the other storage pool.

303Storage pool managementAbout central reporting

Testing connections between storage poolsPureDisk displays a storage pool that is no longer accessible in the middle panewith a unique status icon. A storage pool might not be accessible because ofconnection problems, because the storage pool was removed, and so on. PureDiskcollects this information when you add a storage pool to the list. PureDisk updatesthis information each time a license report is generated or when you click theTest Connection tab.

You can test the connectivity between all the storage pool authorities in a centralstorage pool’s list. The test verifies the link to the storage pool. The test does notverify any login credentials.

To test the connection to a storage pool in the central storage pool list



3 In the right pane, click Test Connection.

The Web UI displays a status message for the connection to the storage pool.

Rerouting a metabase engineYou can attach many clients to one metabase engine. However, as the metabaseengine becomes overloaded over time, you might need to add an additionalmetabase engine to your storage pool. You can examine the capacity of a metabaseengine, add a new metabase engine, and move agents to the new metabase engine.The process of moving existing agents to a new metabase engine is calledmetabaseengine rerouting.

Perform the following procedures to reroute a metabase engine:

■ See “(Optional) Gathering metabase engine capacity information” on page 305.

■ See “Preparing clients for rerouting” on page 305.

■ See “Preparing the old metabase engine for rerouting” on page 307.

■ See “Adding the new metabase engine and recording its address” on page 307.

■ See “Rerouting the agents on the metabase engine” on page 308.

■ See “Restarting the agent” on page 309.

■ See “Verifying a metabase engine rerouting” on page 309.

■ See “Troubleshooting” on page 310.

Storage pool managementRerouting a metabase engine

304

(Optional) Gathering metabase engine capacity informationA metabase engine capacity report indicates whether a metabase engine is fillingup. You need to obtain this information so you know which metabase engines toreroute. The following procedure explains how to determine metabase enginecapacity.

To gather metabase engine information

1 Log on to the storage pool authority Web UI.



4 In the right pane, click Capacity Dashboard.

5 Examine the information in the lower half of the CapacityDashboard reportunder MetaBase Engine Capacity Report.

If CurrentUsage is nearing 90%, consider whether to add another metabaseengine. At 90% of capacity, the metabase engine shuts down. After you addan additional metabase engine, you can reroute the metabase engines.

6 Prepare the clients for rerouting.

See “Preparing clients for rerouting” on page 305.

Preparing clients for reroutingBefore you start the rerouting, you need to choose the clients you want to move,collect client information, and stop the jobs on the clients you selected. Thefollowing procedure explains how to perform these tasks so you can run thererouting program that moves the clients from one metabase engine to another.

To gather client and metabase engine information

1 Decide which agents you want to move to a new metabase engine.


3 For each agent that you want to move to the new metabase engine, performthe following steps:

■ In the left pane, select an agent.

■ In the right pane, under More Tasks, click Agent Dashboard.

305Storage pool managementRerouting a metabase engine

4 For each agent that you want to move, record the agent ID information fromthe Agent Dashboard display.

For example, you can record the information below:

_________________________The ID field for the first agent

_________________________The ID field for the second agent

_________________________The ID field for the third agent

_________________________The ID field for the fourth agent


6 Select an agent that you want to move.

7 Examine the jobs for this agent and terminate any that are still running.

During the rerouting process, make sure that no jobs are running on theagents you want to move, including the following types of job workflows:

■ Files and Folders Backup

■ Full System Backup

■ MS Exchange Backup

■ MS SQL Backup

■ System State and Services Backup

■ UNC Path Backup

■ Data Removal

■ Export To NetBackup

If any jobs are running that use data selections that reside on the agents youwant to move, click Stop job gracefully to end them.


9 In the left pane, select the agent that you want to move.

10 In the right pane, under More Tasks, click Deactivate Agent.

11 Repeat step 5 through step 10 for each agent that you want to move.

12 Prepare the old metabase engine for rerouting.

See “Preparing the old metabase engine for rerouting” on page 307.


306

Preparing the old metabase engine for reroutingThe old metabase engine is the metabase engine from which you want to removeclients. During the rerouting process, no jobs can run on the old metabase engine.The following procedure explains how to find running jobs and terminate them.

To terminate running jobs on the old metabase engine


2 In the left pane, use the View jobs by pull-down menu to select Topology.

This action lets you select the metabase engine and display its jobs.

3 In the left pane, expand the tree and select the old metabase engine.

4 In the right pane, examine the running jobs and terminate any that are stillrunning.

During the rerouting process, no jobs can run on the old metabase engine.These jobs include the following types of workflows:

■ Disaster Recovery Backup

■ Data Mining

■ Server DB Maintenance

■ Replication

■ SPA Replication

If any jobs are running, click Stop job gracefully to end them.

5 Proceed to the following section:

See “Adding the new metabase engine and recording its address” on page 307.

Adding the new metabase engine and recording its addressThe following procedure explains how to add a new metabase engine service. Youcan add the new service to either an existing node or to a new node.

To add a new metabase engine and record its address

1 Add a new metabase engine to the storage pool.

See “About adding services” on page 280.


3 Expand the tree in the left pane until it displays all the storage pool services.

4 Select the new metabase engine server agent.


5 In the right pane, note the Agent Address field, and record the FQDN of thenew metabase engine.

Metabase engine node’s identification __________________________

6 Reroute the agents on the metabase engine.

See “Rerouting the agents on the metabase engine” on page 308.

Rerouting the agents on the metabase engineThe following procedure explains how to run the script to move the agents fromthe old metabase engine to the new metabase engine.

To reroute the metabase engine

1 Log on to the storage pool authority as root.

2 Type the following command to change to the PureDisk commands directory:

# cd /opt/pdspa/cli

3 Type the following command to start the rerouting:

# /opt/pdag/bin/php MBERerouting.php agent_id new_mbe_id

This command accepts the following arguments:

Specify the agent ID of one of the agents you want to move.

This command accepts one agent_id only. If you have to movemore than one agent to a new metabase engine, type a separateMBERerouting.php command for each agent.

agent_id

Specify the node identification for the new metabase engine. Thisvalue is the FQDN, host name, or IP address as it appears in theadministrative Web UI.

The rerouting script fails if you specify a host name and theidentifier in the Web UI is an IP address (or vice versa).

new_mbe_id

4 Answer the prompts from the script.

For example, the script prompts you to confirm that you want to continuewith the rerouting process.

5 Observe the completion messages.

Make sure the rerouting completes before you start any new jobs for theagents you moved.


308

As part of its work, the script performs the following actions:

■ Activates the agents that now reside on the new metabase engine.

■ Updates the agent configuration files.

■ Copies the data selections from the original metabase engine to the newmetabase engine.

6 Restart the agent

Information about how to restart the agent is available.

See “Restarting the agent” on page 309.

Restarting the agentUse one of the following procedures to restart the agent service on a client thatyou moved to a new metabase engine.

To restart the agent service on a Windows client

1 Log on to the client system as an administrator.

2 Click Start > Settings > Control Panel > Administrative Tools > Services.

3 In the Services window, locate and select the Veritas NetBackup PureDiskClient Agent service.

4 Click Restart to restart the service.

To restart the agent service on a Linux or UNIX client

1 Log on to the client system as root.


# /etc/init.d/pdagent restart

Verifying a metabase engine reroutingComplete the following procedure to verify that agents are attached to the newmetabase engine.

To verify rerouting


2 In the left pane, select an agent.


3 In the right pane, look for MetabaseEngine: and make sure that the agent isattached to the new metabase engine.

4 Test the new configuration by running a manual backup from this agent.

TroubleshootingYou might need to abort a metabase engine rerouting job or a metabase enginererouting job might fail. The following procedure returns a storage pool to thestate it was in before you started a metabase engine rerouting job.

To troubleshoot a failed metabase rerouting job

1 Log on to the storage pool authority as root.

2 Type the following command to change to the PureDisk commands directory:

# cd /opt/pdspa/cli

3 Type the following command to start the rerouting:

# /opt/pdag/bin/php MBEHeal.php

About clustered storage pool administrationIf you installed a clustered storage pool, you can administer the storage pool fromthe Veritas cluster manager Java console. For example, you can use this consoleto initiate failovers.

Some reservations apply to failovers. Most notably, active PureDisk jobs mightfail during a failover. Symantec suggests that you verify ongoing storage poolactivity in the PureDisk Web UI before you initiate a failover and after anunexpected failover.

For more information about cluster administration, see theVeritasCluster ServerUser’s Guide.

Changing the PDOS administrator’s passwordThe following procedure explains how to change the administrator (root) user’spassword on a PureDisk node. This procedure applies for multinode and all-in-onestorage pools.

Storage pool managementAbout clustered storage pool administration

310

To change the PDOS administrator’s password

1 Log on to the node as root.

If the storage pool is clustered, log on to the physical computer hardware.

2 Type the following command to reset the password in the operating system:

# passwd

When the command issues prompts, type the old and new passwords.

Changing the PureDisk internal database and theLDAP administrator passwords

Depending on your site practices, or your security status, you might need toregenerate passwords for the PureDisk internal database or for the LDAPadministrator. These passwords are internal. At configuration time, the storagepool configuration wizards sets them to a random, internal value.

The following procedure explains how to change the following passwords:

■ PureDisk database password

■ LDAP administrator password

To change a PureDisk database and authentication password




2 Click Next until you arrive at the Regenerate Passwords page.

3 Click Regenerate Passwords.

4 Wait for the process to complete.

5 Click Cancel.

Increasing the number of client connectionsBy default, PureDisk permits 300 client connections to one content router. If thecontent router has enough available physical memory, you might be able to

311Storage pool managementChanging the PureDisk internal database and the LDAP administrator passwords

increase the number of client connections. Each content router requires a certainamount of memory per client, and this calculation is as follows:

(2 X segment_size) + 512KB

512 KB is the stack size for the client thread.

The following procedure explains how to increase the number of clients.

To increase the number of clients


2 In the left pane, expand Configuration File Templates > PureDiskContentRouter > Default ValueSet for PureDisk ContentRouter >ContentRouter > MaxConnections > All OS:number.

3 Select All OS:number.

4 In the right pane, in the Value field, increase the present number to thenumber of clients + 5.

Five slots are reserved. The maximum value you can specify is 8192.

5 Click Save.

6 In the left pane, select TaskThreadStackSize.

7 In the right pane, select Add Configuration File Value.

8 On the Properties: Configuration File Value screen, change the Value fieldto 256 and click Add.

This value is the stack size for client threads.

9 Restart the content router.

For information about how to restart the content router or other processessee the following:



■ See “Stopping and starting processes in a multinode PureDisk storagepool” on page 318.

Adjusting the clock on a PureDisk nodePureDisk requires synchronization of the time setting between the different nodesin a storage pool. The synchronization relies upon an NTP server, which in normal

Storage pool managementAdjusting the clock on a PureDisk node

312

operation guarantees that all nodes have the time setting. However, the time ona PureDisk node can become incorrect in exceptional cases, such as when the NTPserver fails or the connection between the storage pool and the NTP server fails.

If you notice an incorrect time setting on a PureDisk node, use the followingprocedure to adjust the clock in a safe way.

To adjust the clock on a PureDisk node if the time difference is less than one day

1 Stop all PureDisk services on the node.

Typically, this action causes running jobs to fail. For information about howto stop and start processes, see the following:




2 (Conditional) Make sure that the NTP server works properly and can bereached from the node.

Perform this step if the node you want to fix hosts the storage pool authorityservice.

3 Adjust the time on the node.

4 Start the PureDisk processes on the node.

For information about how to stop and start processes, see the following:




To adjust the clock on a PureDisk node if the time difference is more than one day

◆ Contact Symantec technical support.

313Storage pool managementAdjusting the clock on a PureDisk node

Adjusting the Web UI time-out intervalAfter a period of inactivity, the PureDisk administrator Web UI logs a user out.By default, PureDisk logs a user out after 30 minutes of inactivity. The followingprocedure explains how to set the interval to a different value.

To adjust the time-out interval


2 Open file /opt/pdgui/tomcat/webapps/PureDisk/WEB-INF/web.xml.

3 Search for the following string:

<session-timeout>30</session-timeout>

4 Change 30 to a different value.

This value is expressed in minutes.

5 Save file /opt/pdgui/tomcat/webapps/PureDisk/WEB-INF/web.xml.

Stopping and starting processes on one PureDisknode (unclustered)

You can stop or start individual services or all services.

Use caution when you start or stop individual services. Symantec recommendsthat when you stop or start services, specify an action, but do not specify a list ofservices. In this case, PureDisk performs the action on all services, and all servicesstart and stop in the correct order.

Symantec recommends that you start or stop individual services only when thePureDisk documentation directs you or when a Symantec technical support directsyou.

Stopping all servicesThe following procedure explains how to stop all services.

Storage pool managementAdjusting the Web UI time-out interval

314

To stop all services

◆ Type the following command to stop all services:

# /etc/init.d/puredisk stop

For example, assume that you had to abort the installation of a PureDiskenvironment. Before trying to install the software again, you need to stop allthe services on the host. You can enter the preceding command to stop allservices correctly before you try to reinstall the environment.

Starting all servicesThe following procedure explains how to start all services.

To start all services

◆ Type the following command to start all services:

# /etc/init.d/puredisk start

Starting all services without rebootingIf you reboot a PureDisk node, the system restarts all PureDisk services on thenode. The following procedure explains how to stop and restart PureDisk servicesmanually.

To restart PureDisk processes

◆ Type the following command to restart all PureDisk processes:

# /etc/init.d/puredisk restart

Stopping and starting individual servicesThe following procedure explains how to stop or start individual services.

To stop or start individual services

◆ Use the following command to stop or start individual services:

/etc/init.d/puredisk action [service] [service] ...

The arguments are as follows:

315Storage pool managementStopping and starting processes on one PureDisk node (unclustered)

Specifies the operation to be performed on the service. Specifyone of the following:

■ start. Starts the specified services.

■ stop. Stops the specified services.

■ restart. Stops and then starts specified services. The systemrestarts the services, but it does not enumerate in its messageswhich services it restarts.

■ reload. Reloads the configuration files for the specifiedservices and starts them if they are not already started.

■ status. Displays the status of the specified services.

action

Optional. Use caution when you specify individual servicespecifications.

If you do not specify any services, the command affects allservices. This syntax is the preferred way to use this command.If you want to specify individual services, specify them in theorder that they appear in the following lists.

If you want to stop more than one service, enter a space characterbetween each service. Stop them in the following order:

■ pdworkflowd. The PureDisk workflow daemon.

■ pdcr. The PureDisk content router.

■ pdagent. The PureDisk server agent.

■ pdctrl. The PureDisk controller.

■ pdweb. The PureDisk web server.

■ pddb. The PureDisk database service.

■ pdmemcached. The memcache daemon.

If you want to start more than one service, enter a space characterbetween each service. Start them in the following order:

■ pdmemcached. The memcache daemon.

■ pddb. The PureDisk database service.

■ pdweb. The PureDisk web server.

■ pdctrl. The PureDisk controller.

■ pdagent. The PureDisk server agent.

■ pdcr. The PureDisk content router.

■ pdworkflowd. The PureDisk workflow daemon.

For example:

# /etc/init.d/puredisk start pdcr pdagent

service

Storage pool managementStopping and starting processes on one PureDisk node (unclustered)

316

Stopping and starting processes on one PureDisknode (clustered)

The procedure to stop or start processes on one PureDisk node in a clusteredstorage pool is similar to the procedure for a node in an unclustered storage pool.The difference is that you need to freeze the node while the node’s processes arestopped. That is, if you stop one or more PureDisk services, the entire resourcegroup must remain frozen until you start the services again.

For example, assume that you want to stop PureDisk processes on node1 in yourstorage pool. The services on node1 appear in the Cluster Manager Java Consoleas pd_group1, and you want to restart one or more services on that node.

To stop and start services on example node 1, which is known to VCS as pd_group1

1 In the Cluster Manager Java Console, right-click pd_group1 and select FreezeTemporary.

This action prevents pd_group1 from failing over when VCS detects that someservices are down.

2 Use a PureDisk procedure to stop or restart the services on that node.

For more information, see:

See “Stopping and starting processes on one PureDisk node (unclustered)”on page 314.

3 Visually inspect the Cluster Manager Java Console Web UI and check for faultconditions.

Depending on how long ago the PureDisk service went down, VCS might havedetected that the service is down. In this case, the resource might appear asfaulted in the PureDisk Web UI. If this is the case, complete the followingsteps:

■ Right-click that resource and select Clear Fault - Auto.

■ After you clear the fault, the resource appears as Offline. Although itstarts again, specify to VCS that you want it to monitor the resource. Toenable monitoring again, right-click the resource and select probe-node1.This assumes that node1’s other services are online currently.

4 Visually inspect the display and make sure that all resources of pd_group1now appear with a status of Online.

5 Right-click the resource group (pd_group1) and select Unfreeze.

This action unfreezes the node.

317Storage pool managementStopping and starting processes on one PureDisk node (clustered)

Stopping and starting processes in a multinodePureDisk storage pool

You can stop and start processes in a multinode PureDisk storage pool. Thisprocedure is the same for clustered and unclustered storage pools with theexception of the steps to freeze and unfreeze the cluster.

To stop services in a multinode PureDisk storage pool

1 (Conditional) Freeze the cluster.


This action prevents VCS from failing over the node. To freeze the cluster,use the Cluster Manager Java console, and freeze all the service groups.

2 Stop the services on all the non-storage pool authority nodes first.

The order in which you stop these nodes does not matter, but do not stop thestorage pool authority node at this time.


3 Stop the services on the storage pool authority node.


4 Perform the maintenance operations that you need to perform.

5 Restart services.

See “To start services in a multinode PureDisk storage pool” on page 318.

To start services in a multinode PureDisk storage pool

1 Start the services on the storage pool authority node.

See “Starting all services without rebooting” on page 315.

2 Start the services on all the non-storage pool authority nodes.

See “Starting all services without rebooting” on page 315.

If the storage pool is not clustered, stop here. Do not perform the rest of thesteps in this procedure.

If the storage pool is clustered, complete the rest of the steps in this procedure.

3 Visually inspect the Cluster Manager Java Console Web UI and check for faultconditions.

Depending on how long ago the PureDisk service went down, VCS might havedetected that the service is down. In this case, the resource might appear as

Storage pool managementStopping and starting processes in a multinode PureDisk storage pool

318

faulted in the PureDisk Web UI. If this is the case, complete the followingsteps:

■ Right-click that resource and select Clear Fault - Auto.

■ After you clear the fault, the resource appears as Offline. Although itstarts again, specify to VCS that you want it to monitor the resource. Toenable monitoring again, right-click the resource and select probe -node.This assumes that node’s other services are online currently.

4 Visually inspect the display and make sure that all resources of resource_groupnow appear with a status of Online.

5 Right-click a resource_group and select Unfreeze.

This action unfreezes the resource group. Perform this step for all resourcegroups.

Restarting the Java run-time environmentIf you cannot log onto the PureDisk administrator Web UI, one cause might bethat the Java run-time environment (JRE) has failed. The following procedureexplains how to restart the JRE.

To restart the JRE

1 Log onto the node that hosts the storage pool authority as root.


# /etc/init.d/puredisk status

319Storage pool managementRestarting the Java run-time environment


Example output is as follows:

Checking for LDAP-server running

Checking for VxATd daemon running

Checking for PureDisk Memory Cache Daemon running

Checking for PureDisk Database Server running

Checking for PureDisk WebServer running

Checking for PureDisk Controller running

Checking for PureDisk Controller Monitor running

Checking for PureDisk Server Agent running

Checking for PureDisk ContentRouter running

Checking for PureDisk Workflow Engine running

Checking for PureDisk MetabaseEngine unused

Checking for PureDisk JAVA GUI unused

Checking for CRON daemon running

The preceding output indicates that a metabase engine is also installed onthis node. The status for both the metabase engine and the JAVA GUI are setto unused. This output indicates that the JRE has failed.

4 Type the following command to restart PureDisk:

# /etc/init.d/puredisk start

Storage pool managementRestarting the Java run-time environment

320

Reconfiguring yourPureDisk environment


■ About the configuration files

■ Examining configuration settings

■ Editing the configuration files with the Web UI

■ Editing the configuration files with a text editor

■ Updating the agent configuration files on a client

About the configuration filesThe PureDisk configuration file templates that you see under Settings >Configuration let you change some of the default values that PureDisk uses. Youcan edit and change the configuration fields at any time. However, before youpush your changes to the storage pool, make sure that the system is quiet. Makesure no backups are running because when PureDisk propagates the changes, itrestarts the agents.

For information about configuration, see the following:

■ See “Examining configuration settings” on page 322.

■ See “Editing the configuration files with the Web UI” on page 322.

■ See “Editing the configuration files with a text editor” on page 326.

■ See “Editing an agent configuration file to improve backup and restoreperformance” on page 332.

12Chapter

■ See “Editing an agent configuration file to accommodate large backups”on page 333.

■ See “Updating the agent configuration files on a client” on page 327.

■ For parameters that you can use to tune PureDisk, see the PureDisk BestPractices Guide.

Examining configuration settingsThe configuration file is divided into several sections and subsections. To see thefile templates presented graphically, use the Web UI and examine the entriesunder Settings > Configuration > Configuration File Templates.

The following procedure explains how to examine configuration file sections.

To examine the configuration file sections


2 In the left pane, click the plus sign (+) to the left of Configuration filetemplates.

3 Expand one of the PureDisk templates.

For example, expand PureDisk Storage Pool Authority > Default ValueSetfor PureDisk Storage Pool Authority > watchdog > interval.

4 Click All OS.

Examine the information in the Value field.

Editing the configuration files with the Web UIYou can edit the configuration values. Typically, you edit the configuration filevalues only when directed to do so by a PureDisk procedure.

To edit your configuration

1 Make a copy of the default value set you want to change.

See “Making a copy of a value set” on page 323.

2 Navigate to a configuration value in the copy of the value set.

See “Navigating to a value in the configuration file copy” on page 323.

Reconfiguring your PureDisk environmentExamining configuration settings

322

3 Changing a configuration value or deleting a configuration value.

See “Changing a configuration file value or deleting a configuration file value”on page 324.

4 Assign the new template and, optionally, push the configuration file changes.

You can assign the template and wait to push the changes, or you can assignthe template and push the changes in one operation.

See “Assigning the template and, optionally, pushing the configuration filechanges” on page 325.

Making a copy of a value setUse the following procedure to copy a value set.

To make a copy of a value set


2 In the left pane, expand Configuration File Templates.

3 Expand an agent or service.

For example, expand PureDisk Client Agent.

4 Select the default value set.

For example, select Default ValueSet for PureDisk Client Agent.

5 In the right pane, click Copy ValueSet.

You can make only one copy of the default value set.

6 In the left pane, select the copy of the value set.

7 (Optional) In the right pane, in the Value set name (new) field, type a newname for the copy of the value set.

Alternatively, you can decide to accept the default name.

8 Click Save.

9 Visually inspect the left panel to check that the copy appears.


See “Navigating to a value in the configuration file copy” on page 323.

Navigating to a value in the configuration file copyUse the following procedure to navigate to a configuration file value in theconfiguration file copy.

323Reconfiguring your PureDisk environmentEditing the configuration files with the Web UI

Note:Do not edit a line if its default value contains brace characters. For exampleAll OS:{{$agentid}}.These are system variables.

To navigate to the content of a configuration file field

1 (Conditional) Click Settings > Configuration.

Perform this step if the copy of the default value set does not already appearin the left pane.

2 (Conditional) In the left pane, click the plus sign (+) to the left of Configurationfile templates.


3 (Conditional) Expand the configuration file template so that you can see thecopy of the default value set.


4 Select the copy of the default value set you want to change.


See “Changing a configuration file value or deleting a configuration file value”on page 324.

Changing a configuration file value or deleting a configuration filevalue

By default, some configuration file values are unspecified. Other configurationvalues might have values that you want to change. You can change values, andyou can also delete values.

After you delete a value, you cannot add it back. For example, if you want to deletePureDisk Client Agent > Copy of Default ValueSet for PureDisk Client Agent >mail > smtpserver2 > All OS:, you cannot add it back later if your site gets anadditional SMTP server. For this reason, the PureDisk Web UI asks you to confirmyour action when you click Delete Configuration File Value.

Reconfiguring your PureDisk environmentEditing the configuration files with the Web UI

324

To change or delete a configuration file value

1 In the left pane, expand the value set and select a line.

For example, expand PureDisk Client Agent > Copy of Default ValueSet forPureDisk Client Agent > progress > showicon > All OS:1.

2 In the right pane, edit the Value field or click DeleteConfigurationFileValue.

If you clicked DeleteConfigurationFileValue, the Web UI asks you to confirmyour action. After you delete a value, you cannot add it back.

For example, by default, the showicon value is set to 1, which is enabled. Itshows the icon on the client while PureDisk does backups. To disable the icon,change the value to 0.

3 Click Save.


See “Assigning the template and, optionally, pushing the configuration filechanges” on page 325.

Assigning the template and, optionally, pushing the configuration filechanges

After you edit the configuration, you can perform operations to test the newconfiguration. After the tests finish, however, you need to push the configurationfile changes you made to the PureDisk system services in order for the changesto become permanent. If you do not push your configuration file changes, PureDiskthe values revert to their previous settings the next time you push theconfiguration file changes.

The following procedure explains how to propagate configuration file changes tothe storage pool.

To update PureDisk services

1 (Conditional) Click Settings > Configuration.

Perform this step if the copy of the value sets does not already appear in theleft pane.

2 In the left pane, click the plus sign (+) to the left of Configuration FileTemplates.

Perform this step if the copy of the value set does not already appear in theleft pane.

325Reconfiguring your PureDisk environmentEditing the configuration files with the Web UI

3 (Conditional) Expand the tree in the left pane and select value set copy.

Perform this step if the copy of the value set does not already appear in theleft pane.

For example, select PureDisk Client Agent > Copy of Default ValueSet forPureDisk Client Agent.

4 In the right pane, click Assign template.

5 Select the entities that you want to use this value set.

6 Click Assign.

7 (Conditional) Click Push Configuration Files.

Perform this step if you want the changes you made to become permanent.

The list of members should include the services you selected in 5.

PureDisk monitors the configuration files that are pushed to each agent andchecks if the value set has changed. PureDisk performs this check and createsupdate jobs only if the value set has changed since the last update job ran foreach agent. For example, if you push a value set to an agent twice withoutchanging the value set, PureDisk creates only one job.

If you use the Force option, the server-side change checking is ignored andan update job is always created.

8 (Conditional) Click Push.

Perform this step if you also performed step 7.

Confirm your actions in the dialog boxes that appear.

Editing the configuration files with a text editorThe configuration files are ASCII files. You can edit these files with any text editor.The files themselves contain descriptions for each field. You can also use the WebUI to determine sections and field content for each configuration file.

Note: If you edit these files with a text editor, you cannot push them to the storagepool. Also, any subsequent changes that you make with the Web UI overwrite themanual changes you made with a text editor. Symantec recommends that you usethis method only if instructed to do so by a Symantec technical supportrepresentative.

Table 12-1 shows the locations of these ASCII files.

Reconfiguring your PureDisk environmentEditing the configuration files with a text editor

326

Table 12-1 Configuration file locations

LocationConfiguration file

/etc/puredisk/spa.cfgStorage pool authority

/etc/puredisk/contentrouter.cfgContent router

/etc/puredisk/pdmbs.cfgMetabase server

/etc/puredisk/pdmbe.cfgMetabase engine

/etc/puredisk/pdctrl.cfgController

/etc/puredisk/agent.cfgPureDisk node agent

Updating the agent configuration files on a clientRegardless of how you installed and registered an agent the first time, you canchange the agent configuration on a client, as follows:

To retrieve a new configuration file, see the following procedure:

See “To retrieve a new configuration file for a client” on page 328.

To change the data lock password, see the following procedure:

See “To reset the data lock password on a client” on page 329.

For information about the parameters and arguments that the pdregister

command uses, see the Windows and UNIX installation chapters of the PureDiskClient Installation Guide.

The procedure To retrieve a new configuration file for a client explains how toupdate an agent configuration file in the following situations:

■ Example 1.A client system crashes or has been reimaged. In this case, you can reregisterthe client on the storage pool authority. The original configuration file iscompletely lost.

Assume the following series of events:

■ A user installs the PureDisk agent software on a client.

■ The client system crashes.

■ The user reinstalls the operating system software on the client.

■ The user can run the pdregister command as shown in this procedure torestore the configuration file for this particular client.

327Reconfiguring your PureDisk environmentUpdating the agent configuration files on a client

■ Example 2.You accidentally make erroneous edits to a configuration file.You might change configuration file parameters and later want to revert tothe original configuration file. If the old configuration file exists and has avalid agent ID, you can obtain a new copy from the storage pool authority.

■ Example 3 (Linux only).If you have SPAR enabled and you need to retrieve a new configuration file.SPAR enables you to replicate storage pool information from a remote storagepool to a main storage pool. The remote storage pool acts as a client to themain storage pool.For more information about how to use SPAR, see thePureDiskAdministrator’sGuide.

In the following procedure, the format for the pdregister command is showngenerically for MS Windows or UNIX clients. The .exe suffix applies only toWindows clients.

To retrieve a new configuration file for a client

1 Invoke the PureDisk Web UI and make sure that the client appears in the listof clients in the left pane when you select Manage > Agent.

Do not perform this procedure if the client is not registered on the storagepool currently.

2 Log on to the client system as root (Linux or UNIX platforms) or as theadministrator (Windows platforms).

3 Change to the directory into which you installed the agent software.

On Linux and UNIX platforms, change toinstall_path/pdag/bin. The defaultis /opt/pdag/bin.

On Windows platforms, change to the directory into which you installed theagent. By default, this directory is C:\Program Files\Symantec\NetBackup

PureDisk Agent\bin.

4 Run the pdregister command.

To retrieve a new agent configuration file from the storage pool authority,type the command with the following parameters:

pdregister[.exe] --action=configfile -–type=Agent --login=login --passwd=pwd \

--url=https://yourspa/spa/ws --todisk --agentid=id [--productname=SPARR]

This set of parameters assumes that the original configuration file iscompletely lost. To ensure that PureDisk recognizes this client, you need tospecify the agent ID.

Reconfiguring your PureDisk environmentUpdating the agent configuration files on a client

328

(Linux only) Specify --productname=SPARR if SPAR is enabled, and this hostis a client to a main storage pool. Make sure that the logon and passwordbelong to a user that has Agent Management permissions.

To retrieve a new agent configuration file from the storage pool authorityand overwrite an existing configuration file, type the command with thefollowing parameters:

pdregister[.exe] --action=configfile -–type=Agent --url=https://yourspa/spa/ws

--todisk [--productname=SPARR]

This set of parameters assumes that the original configuration file still resideson the client. Your intent is to restore it to the form it has on the storage poolauthority. You do not need to specify the agent ID or the logon credentials.

More information about the parameters and arguments that pdregisteraccepts is available.

See the PureDisk Client Installation Guide

5 (Conditional) Activate the agent.

Perform this step if the agent is not activated.

More information about how to activate the agent is available.

See the PureDisk Client Installation Guide

To reset the data lock password on a client

1 Invoke the PureDisk Web UI and make sure that the client appears in the listof clients when you click Manage > Agent.

Do not perform this procedure if the client is not registered on the storagepool currently.

2 Log on to the client system as root for UNIX clients and as admin for MSWindows clients.

329Reconfiguring your PureDisk environmentUpdating the agent configuration files on a client

3 Change to the directory into which you installed the agent software.

On Linux and UNIX platforms, change toinstall_path/pdag/bin. The defaultis /opt/pdag/bin.

On Windows platforms, change to the directory into which you installed theagent. By default, this directory is C:\Program Files\Symantec\NetBackup

PureDisk Agent\bin.

4 Type the following command to reset the data lock password:

pdregister[.exe] --action=replacedatalockpassword --type=Agent --login=login \

--passwd=pwd --url=https://yourspa/spa/ws --olddatalockpasswd="old_pwd" \

--datalockpasswd="pwd"

Make sure that the logon and password belong to a user that has AgentManagement permissions.

Reconfiguring your PureDisk environmentUpdating the agent configuration files on a client

330

Tuning and optimization


■ Tuning backup and restore performance

■ Tuning replication performance

Tuning backup and restore performanceYou can improve PureDisk backup and restore performance. In some cases, youcan use multistreamed backups, multistreamed restores, and segmentation optionsfor backup jobs. PureDisk lets you optimize the communication between the clientand the content router, and this optimization can increase backup and restoreperformance.

The following information explains how to implement these optimizations:

■ See “Editing an agent configuration file to improve backup and restoreperformance” on page 332.

■ See “Editing an agent configuration file to accommodate large backups”on page 333.

■ See “Multistreamed (parallel) backups” on page 334.

■ See “Multistreamed (parallel) restores” on page 335.

■ See “Segmentation options for backup jobs” on page 336.

Any changes you make to these the configuration files are considered to be anadvanced operation, and you need to measure your results after each change.These changes require testing and experimentation. When you measureperformance, measure the time for the putfiles job step, not total job time.

If your backups and restore jobs seem slow, try increasing the number of streamsand checking the resulting performance. In some cases, performance can be betterif you use fewer streams.

13Chapter

Editing an agent configuration file to improve backup and restoreperformance

The default agent settings in the configuration files do not enable multistreamingof backups or restores. By default, there is no segmentation threshold value andno list of segmentation file types.

You can change the default configuration file settings. Symantec recommendsthat you set segmentation parameters in the Web UI and only vary the agentconfiguration parameters for special client situations. For example, you mighthave some clients on slow network lines. To improve performance, you can usemultistreaming or the segmentation options.

For information about changing configuration files, see the following:


To tune backup performance

◆ To tune backup performance, you can edit the following settings underSettings>Configuration>ConfigurationFileTemplates>PureDiskClientAgent > Default ValueSet for PureDisk Client Agent > backup:

■ DontSegmentTypes.The default value is an empty list, All OS:.

■ DontSegmentThreshold.The default value is All OS:0.

■ maxstreams.The default value is All OS:1.

■ MaxRetryCountSpecifies the maximum number of times that the backup job can attemptto send each file in the event of network errors. Specify any positiveinteger. The default is 5. The backup job stops and issues an error the firsttime it encounters a file that cannot be transmitted and the retry counthas been exceeded.

For information about the segmentation parameters, see the following:

■ The PureDisk Backup Operator’s Guide.

■ See “Segmentation options for backup jobs” on page 336.

To tune restore performance

◆ To tune restore performance, you can edit the following settings underSettings>Configuration>ConfigurationFileTemplates>PureDiskClientAgent > Default ValueSet for PureDisk Client Agent > restore:

Tuning and optimizationTuning backup and restore performance

332

■ maxstreams.The default value is All OS:1.

■ MaxSegmentPrefetchSize. Specifies the number of bytes to prefetchduring a restore. The default is 16MiB. Valid units are B, KiB (1024), MiB,GiB, KB (1000), MB, and GB.When set to zero (0), PureDisk disables prefetching. During restore,PureDisk fetches only one data segment at a time. This behavior is identicalto the default restore behavior before PureDisk 6.6.If you restore to a client that is very low on memory, and you want toensure that memory use is low during the restore job, you can set thisvalue to zero (0) or to a value that is less than zero.

■ SegmentChunkSize. Specifies the number of bytes of data to transferover the network from the server to the client at one time. The default is32KiB. Valid units are B, KiB (1024), MiB, KB (1000), and MB.The range for this setting is from 1KiB through 16 MiB.This setting has no effect if MaxSegmentPrefetchSize is set to zero (0).

Editing an agent configuration file to accommodate large backupsDuring a backup, the agent gathers a list of the files to be backed up. On Linuxand UNIX clients, the agent writes these lists to the following directories:

■ /opt/pdag/var

■ /opt/pdag/tmp

During very large backups, these lists can grow beyond the space that you allocatedto the / partition, which is typically kept relatively small. If you expect this spaceproblem might happen on a client, use the following procedure to modify theagent configuration file on that system.

Note: Repeat this procedure each time you update the agent configuration filesthrough the Web UI. The repetition is necessary because updates through theWeb UI overwrite all agent configuration files.

333Tuning and optimizationTuning backup and restore performance

To modify the agent configuration to accommodate large backups

1 Type the following command to stop the agent service:

# /opt/pdag/bin/pdagent --stop

2 Open the agent configuration file in a text editor.

For example:

# vi /etc/puredisk/agent.cfg

3 In the [paths] section, type new paths for the following parameters:

var

temp

The new paths must be full paths, not relative paths. They must refer to apartition large enough for the backups.

4 Save and close the file.

5 Type the following command to start the agent service:

# /opt/pdag/bin/pdagent

Multistreamed (parallel) backupsA backup job can have multiple threads. When the job runs, PureDisk might notalways use the maximum number of backup streams that you specify. When a jobstarts, PureDisk determines the total amount of data to upload. Based on thelength of the data entries list and the number of streams requested, PureDiskdetermines and initializes the optimal number of threads.

After PureDisk validates the input data list, it uses the following rules to properlydistribute data entries across the requested number of data streams:

■ If the number of data entries is less than the number of requested streams, asingle stream backup is used.

■ If the number of data entries is less than 4096 per stream, they are balancedacross the streams.

■ If the number of data entries are more than 4096 per stream, each stream isgiven 4096 data entries. As each stream finishes, it is given the next 4096 dataentries until no entries remain.

For multistreamed backup jobs, a distinction is made between transient and fatalerror conditions. An example of a transient error condition is a temporary loss


334

of connection with remote storage. Examples of fatal error conditions are anempty routing table, an invalid data selection ID, or an out-of-memory error.

If you use multiple backup streams, the behavior of the Sorting option is slightlychanged. This occurs, for example, if you set Number of backup streams in theParameters tab of a backup policy to 2 or more.

If you enable both sorting and multistreaming, the PureDisk agent first sorts thecomplete list of files by their size. It then distributes small chunks of the sortedlist over the available stream. For this reason, and because PureDisk backs upmultiple files at one time, the order in which it backs up the files cannot matchexactly the order of the files in the sorted list.

For large backups, the trend of the backup order is still as expected (smallest filesfirst), but for small backups of only a few files, there may be some anomalies.

If you run too many parallel backup streams, you can overload the client system.If you overload the client, one of the following occurs:

■ The backups might fail with a status of SUCCESS_WITH_ERRORS. In this case,not all files are transferred, and there is no obvious error in the log file.

■ PureDisk might display the following message:

Insufficient system resources exist to complete the requested service

You might need to experiment with more than one approach to performancetuning, or you might need to use different combinations of streams and segmentsize values. The exact values depend on the specific client and its hardwareconfiguration.

Symantec recommends that you start with a small number of streams and thatyou increase max_streams only if the backup performance is unacceptable. Atsome point, if you increase max_streams, performance does not improve. Amax_streams value that is too large provides no benefit, can overload the clientsystem, and can cause backups to fail.

Multistreamed (parallel) restoresA restore job can have multiple threads. When the job runs, PureDisk might notalways use the maximum number of restore streams that you specify. When a jobstarts, PureDisk determines the total amount of data to upload. Based on thelength of the data entries list and the number of streams requested, PureDiskdetermines and initializes the optimal number of threads.

PureDisk validates the data list. After the validation, if it determines that thenumber of data entries is fewer than three per stream, it uses a single streamrestore.

335Tuning and optimizationTuning backup and restore performance

Segmentation options for backup jobsThe following sections describe the segmentation options you can use to reducethe number of segments that are used to transmit backup files to a PureDiskcontent router:

■ See “Segmentation threshold value” on page 336.

■ See “File-type segmentation” on page 336.

By editing these segmentation values, you might be able to improve performance.A difference in backup performance is more noticeable if there is a high latencyon the connection between the agent and the content router(s).

Note: If these two options are not set identically on all agents, the effectivenessof PureDisk deduplication option (PDDO) can be reduced. If you enable PDDO, theMATCH_PDRO parameter is enabled by default. When enabled, the MATCH_PDRO

parameter specifies that the PureDisk calculate the segment size based on the filesize, which is the same method by which PureDisk calculates the segment sizefor a typical backup.

Segmentation threshold valueA segmentation threshold value can be set in the Web UI or in the agentconfiguration file.

When a PureDisk agent transfers a file to a content router, it checks whether thefile is smaller than the segmentation threshold value. If the file is smaller, the fileis transmitted in only one segment. If the file is larger than the maximum segmentsize, it is transmitted in multiple segments. However, each segment is themaximum segment size, except that the last might be smaller.

The segmentation threshold value cannot be set to a value greater than themaximum segment size, or smaller than twice the default segment size.

File-type segmentationA comma-separated list of file types (identified by file name suffixes) can be setin the UI or in the agent configuration file.

As a PureDisk agent transfers a file to a content router, it checks whether thefile’s suffix is contained in this list. If the suffix is in the list, the file is transmittedin only one segment. If the file is larger than the maximum segment size, it is stilltransmitted in multiple segments. However, each segment is the maximumsegment size , except possibly the last segment.


336

Unexpected resultsMultiple backup streams or restore streams can have the following unexpectedresults:

■ Multistreaming can increase the load on content routers.

■ With some fast network or hardware configurations, multistreaming can slowthe performance of other backup or restore jobs.For example, if the PureDisk metabase is on the same node as a content router,the metabase import step can take longer. The content router might not havecompleted its processing, because the spool is filled faster than the contentrouter empties it. This delay of the metabase import can lead to a longer totalbackup time, but during that time, the client and the wire are idle.

■ Multistreaming can stop other agents from connecting to a content routerbecause each job stream needs one of the limited connections (limited to 300).

■ Client backup and restore performance might be affected if all parallel streamsdo central-processor-bound fingerprint calculations.

■ If you run too many parallel backup streams, you can overload the clientsystem. When this occurs, the system generates the following error: Unableto resolve host name. PureDisk generates this error because each backupstream has its own content router context. Because of the unique contexts,each stream makes DNS address lookups for the content router address(es).If the content router does not get a response from DNS lookups in one minute,it reports this error.If backups have many streams, DNS lookups can fail when the central processorusage is high and some streams are not rescheduled fast enough.

■ If you add multistreaming after the CPU/wire is full, you see no performanceincrease.

Tuning replication performancePureDisk lets you tune replication performance. All tuning is accomplished throughchanging configuration parameters on the source storage pool. You can setPureDisk parameters to tune the following aspects of replication:

■ Parallelism. To increase parallelism in PDDO replication, set the maxstreamsparameter to a larger value. The higher the value of the maxstreams parameter,the more parallelism is obtained. The valid range is from 1 to 10 streams.

■ Bandwidth. If you need to limit the bandwidth used between storage poolsduring replication, you can set the bandwidthlimit parameter. PureDisk usesonly the amount of bandwidth specified in this parameter. Every stream uses

337Tuning and optimizationTuning replication performance

the specified bandwidth value. For example, if you use 4 streams and abandwidth of 200 KB, PureDisk uses 800 KB of bandwidth between storagepools during replication.

■ Network errors. If you want to minimize the effect of network errors onreplication, you can use the following parameters: maxretrycount, sleeptime,and maxsleeptime.For example, the replication process might not be able to complete because ofnetwork errors. In this case, you can specify the number of times that thesource storage pool needs to wait before trying to send the data again to thedestination storage pool. Depending on network conditions, you might specifyto wait a few seconds or wait a few minutes.

To tune replication performance

1 Log into the Web UI of the source storage pool.

2 Click Settings > Configuration > Configuration File Templates > PureDiskServer Agent > Default ValueSet for PureDisk Server Agent > replication.

3 Change the values for one or more of the following configuration parametersunder replication:

■ bandwidthlimit. Specifies the bandwidth limit, between the storage pools,for the replication activity, in KB/sec. If you set this parameter to zero (0),you specify unlimited bandwidth. The default is 0 (disabled).

■ maxretrycount. Specifies the maximum number of times that the PureDiskreplication workflow can attempt to send data. Specify any positive integer.The default is 10.

■ maxsleeptime. Specifies the maximum amount of time, in seconds, thatthe replication workflow is permitted to sleep between retries. Specifyany positive integer. The default is 60.

■ maxstreams. Specifies the maximum number of PDDO replication streamsper replication job. The maximum value is 10; if you set this parameterto a value greater than 10, PureDisk uses 10 streams per replication job.Specify any positive integer. The default is 4.

■ sleeptime. Specifies the number of seconds that the replication workflowcan sleep between 2 retries. Specify any positive integer. The default is10.

The delayeddosize and maxsocachesize parameters also affect replication, butSymantec recommends that you do not reset these parameters without theassistance of Symantec Technical Support staff.

For information about how to edit the configuration file parameters, see thefollowing:

Tuning and optimizationTuning replication performance

338


339Tuning and optimizationTuning replication performance

Tuning and optimizationTuning replication performance

340

Installing the clusteringsoftware

This appendix includes the following topics:

■ About the Veritas Cluster Server (VCS) software installation

■ (Conditional) Examining the NICs for the private heartbeats

■ Synchronizing passwords

■ Installing the Veritas Cluster Server (VCS) software

■ Configuring VCS

■ (Conditional) Using YaST to create the storage partitions

About the Veritas Cluster Server (VCS) softwareinstallation

The information in this topic describes how to install VCS manually during aclustered storage pool disaster recovery. Do not use the information in this topicfor PureDisk 6.6 initial installations or for upgrades. The information in thePureDisk Storage Pool Installation Guide describes how to install and upgradePureDisk storage pools, and it presents the PureDisk 6.6 wizard-based automatedinstallation method.

The following figure shows an example cluster:

Figure A-1.

You can refer to this figure for terminology and general information when youinstall the VCS software on the failed nodes. The figure shows the NIC information

AAppendix

for each node, explains each node's role in the storage pool, shows the publicnetwork, and shows the heartbeat networks.

Figure A-1 Example three-node cluster

node 1 - all-in-one

NIC 1:Host IP: 100.100.100.100Host FQDN: node1.acme.comVirtual IP: 100.100.100.101Virtual FQDN: node1v.acme.com

NIC 2:Attached to private network. No IPs.


node 2 - metabase engine +content router

NIC 1:Host IP: 100.100.100.110Host FQDN: node2.acme.comVirtual IP: 100.100.100.111Virtual FQDN: node2v.acme.com



node3 - Spare

NIC 1:Host IP: 100.100.100.120Host FQDN: node3.acme.comVirtual IP:Virtual FQDN:



SAN

First heartbeat network

First public network

Second heartbeatnetwork

The following describe how to install the VCS software on a failed cluster node:

■ See “(Conditional) Examining the NICs for the private heartbeats” on page 343.

Installing the clustering softwareAbout the Veritas Cluster Server (VCS) software installation

342

■ See “Synchronizing passwords” on page 347.

■ See “Installing the Veritas Cluster Server (VCS) software” on page 351.

■ See “Configuring VCS” on page 360.

■ See “(Conditional) Using YaST to create the storage partitions” on page 365.

(Conditional) Examining the NICs for the privateheartbeats

Perform these procedures in the following situations:

■ If you do not have this storage pool's cluster planning spreadsheet.

■ If you installed new NICs in the failed nodes as part of your disaster recovery.

PureDisk requires that two NICs in each node be configured without addressing.These NICs are for the cluster’s private heartbeat. The following proceduresexplain how to examine the NICs in each node and remove the addressing, ifneeded, from two of the NICs.

Examining the NICs in this node for addressingThis procedure explains how to examine each NIC for existing addresses. Thisprocedure also explains how to remove the addresses from the two NICs neededfor the private heartbeat.

For each node that you want to include in a cluster, PureDisk requires that twoNICs be configured without any addressing. These two NICs comprise the privatenetwork that VCS uses to monitor the cluster’s heartbeat.

Repeat the following procedure for each node.

To examine the NICs

1 Log into one of the nodes.

2 Type the ip a(8) command to retrieve the NIC information for this node.

The output of the ip a(8) command includes each NIC’s MAC address in thelink/ether field.

343Installing the clustering software(Conditional) Examining the NICs for the private heartbeats

3 Examine the ip a(8) command output.

The following two examples show a correctly configured node and anincorrectly configured node.

Example 1 - correctly configured NICs:

# ip a

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

inet6 ::1/128 scope host

valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100

link/ether 00:11:43:e4:0b:2a brd ff:ff:ff:ff:ff:ff

inet 10.80.92.102/21 brd 10.80.95.255 scope global eth0 # << note the IP addr

inet6 fec0::80:211:43ff:fee4:b2a/64 scope site dynamic

valid_lft 2591999sec preferred_lft 604799sec

inet6 fe80::211:43ff:fee4:b2a/64 scope link


3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000

link/ether 00:11:43:e4:0b:2b brd ff:ff:ff:ff:ff:ff

4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000

link/ether 00:04:23:b0:4f:86 brd ff:ff:ff:ff:ff:ff

5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000

link/ether 00:04:23:b0:4f:87 brd ff:ff:ff:ff:ff:ff

6: sit0: <NOARP> mtu 1480 qdisc noop

link/sit 0.0.0.0 brd 0.0.0.0

Example 2 - incorrectly configured NICs:

# ip a

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

inet6 ::1/128 scope host










Installing the clustering software(Conditional) Examining the NICs for the private heartbeats

344














5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000

link/ether 00:11:43:e4:0b:2b brd ff:ff:ff:ff:ff:ff

6: sit0: <NOARP> mtu 1480 qdisc noop

link/sit 0.0.0.0 brd 0.0.0.0

In example 2, you can use eth0 for the node’s public NIC. You need to removethe addressing from eth1 and eth2 so you can use these NICs for the privateheartbeat.

4 Record the NIC information and the MAC address information from the ip

a(8) command output.

The YaST interface identifies each NIC by its MAC address. You need to knowthe MAC addresses of the two NICs that you want to use for the privateheartbeat.

Make sure you gathered this information and recorded it on the planningspreadsheet, PureDisk_ClusterPlanning.xls.

5 Proceed with the installation as follows, depending on your situation:

CircumstanceProceed to ...

If the following conditions are true, theaddressing on this node is correct:

■ Only one NIC on this node isconfigured with an IP address.

■ The two other NICs on this node arenot configured with addressing.

Go back to the following step and repeatthis procedure for the next node:

■ Step 1

Step 1

of this procedure.

345Installing the clustering software(Conditional) Examining the NICs for the private heartbeats


If you installed new NICs in the failednodes as part of your disaster recovery.

See “(Conditional) Removing addressingfrom the private heartbeat NICs”on page 346.

If the NICs for each node's privateheartbeat are configured withoutaddressing and you do not have to edit the/etc/hosts file to configurecommunication.

See “Synchronizing passwords”on page 347.

(Conditional) Removing addressing from the private heartbeat NICsPerform the following procedure if you installed new NICs in the failed nodes aspart of your disaster recovery. This procedure removes addressing from one ortwo NICs in this node.

To remove addressing

1 Launch YaST and display the NetworkCardConfigurationOverview screen.

Perform the following steps, to launch the YaST interface:

■ At a command prompt, type the following command to launch the SUSELinux YaST configuration tool.

# yast

■ In the YaST Control Center main screen, select Network Devices >Network Card.

■ On the Network Setup Method Screen, select Traditional Method withifup and select Next.

2 On the Network Card Configuration Overview screen, highlight one of theNICs that you want to use for the heartbeat and select Edit.

In the bottom pane, the Device Name field identifies each NIC by its MACaddress. Select one of the secondary NICs in this node. Do not select theprimary NIC upon which you have configured the host address (theadministrative address) as part of the PDOS installation procedure.

3 On the NetworkAddressSetup screen, select NoneAddressSetup and selectNext.

4 Repeat the following steps to configure None Address Setup on the secondprivate NIC:

Installing the clustering software(Conditional) Examining the NICs for the private heartbeats

346

■ Step 2

■ Step 3

5 Select Finish.

6 Select Quit.

7 Proceed to one of the following, depending on your situation:


If you need to log into another node andconfigure the private heartbeat NICs inthat node without any addressing.

See “(Conditional) Examining the NICs forthe private heartbeats” on page 343.

If the NICs for each node's privateheartbeat are configured withoutaddressing and you do not have to edit the/etc/hosts file to configurecommunication.

See “Synchronizing passwords”on page 347.

Synchronizing passwordsPerform the following procedures to synchronize and distribute the passwordson all the nodes in your cluster.

Generating the authentication key on each nodeThe following procedure explains how to generate an authentication key fromthe node that you want to use as the storage pool authority node.

To generate an authentication key

1 Log into the node you want to use as the storage pool authority node.

2 Type the following ssh-keygen(1) command and respond to its prompts:

# ssh-keygen -t rsa

This command creates an authentication key. It issues several prompts, asfollows:

■ Press Enter at the following prompt to save the file in the default location:

Generating public/private rsa key pair.

Enter file in which to save the key (/root/.ssh/id_rsa):

347Installing the clustering softwareSynchronizing passwords

■ Press Enter to create an empty pass phrase at the following prompt:

Enter passphrase (empty for no passphrase):

■ Press Enter again to confirm the empty pass phrase at the followingprompt:

Enter same passphrase again:

■ Read the command summary. For example:

Your identification has been saved in /root/.ssh/id_rsa.

Your public key has been saved in /root/.ssh/id_rsa.pub.

The key fingerprint is:

85:66:10:cc:c8:6a:b3:c0:6a:69:85:32:5c:ed:fb:64 root@sr2e

Make sure to issue this command on each node in the cluster.

3 Log into another node.

4 Repeat the following steps until you have issued the ssh-keygen(1) commandon each node in the cluster:

■ Step 2

■ Step 3

Note: Make sure to issue the ssh-keygen(1) command on each node.


See “Collect the SSH public keys” on page 348.

Collect the SSH public keysThe following procedure configures the trust that the VCS installer needs beforeit can push the software to all the nodes in the cluster.

Installing the clustering softwareSynchronizing passwords

348

To collect the secure keys

1 Log into the node that you want to use for the storage pool authority node.

2 Issue the following ssh(1) command from this node to generate a public keyand write it to a file:

ssh FQDN_of_this_node cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

For example:

node1:# ssh node1.acme.com cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

This command initiates a dialog. Depending on your environment, thiscommand can issue different questions. Respond with y or yes to the prompts,and enter the root password for the node in response to the password prompts.For example, respond with y or yes if the commands detect preexisting keyfiles and ask whether to overwrite them.

3 Issue the following ssh(1) command from this node to another node:

ssh FQDN_of_another_node cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

4 Repeat the following step for each node in the cluster:

■ Step 3

Your goal is to issue the ssh(1) command from this node to all the other nodes.

For example, when finished, the following commands might appear on yourscreen for a three-node cluster:





See “Distributing the key file” on page 349.

Distributing the key fileThe following procedure explains how to distribute the key. This procedure ensuresthat you can upgrade the cluster’s software from whatever node happens to bethe storage pool authority node in the future.

349Installing the clustering softwareSynchronizing passwords

To distribute the key to the other nodes

1 Use the scp(1) command to distribute the authorized_keys file to all theother nodes.

For example:

scp ~/.ssh/authorized_keys root@node:~/.ssh/authorized_keys

For node, specify the host FQDN of one of the other nodes.

2 Repeat the following step and issue the scp(1) command to copy the key fileto each of the other nodes:

■ Step 1


■ If you want to verify the SSH access, proceed to the following:See “(Optional) Verifying the SSH access” on page 350.

■ If you want to start installing the VCS software, proceed to the following:See “Installing the Veritas Cluster Server (VCS) software” on page 351.

(Optional) Verifying the SSH accessThe following procedure explains how to verify that SSH can access the local nodein addition to other nodes without encountering password prompts.

To verifying SSH access

1 Log into any one of the nodes.

2 Type the following command to test connectivity:

ssh host_FQDN_of_this_node w

For example, you can issue the following command from the storage poolauthority node in the cluster:

# ssh node1.acme.com w

3 (Conditional) Respond yes to the following prompt if it appears:

Are you sure you want to continue connecting (yes, no) ? yes

4 Analyze the output from this command as follows:

■ In a correctly configured cluster, the output from this command includesinformation about users, the system load, and so on.

Installing the clustering softwareSynchronizing passwords

350

■ In an incorrectly configured cluster, the output from this command is aprompt for a password.

5 Type additional ssh(1) commands from this node to each of the other nodes.

Use the ssh(1) command format from the following step, but specify the hostFQDN of another node:

■ Step 2

6 Repeat the following step for each of the other nodes in the cluster:

■ Step 5

7 Log into another node.

8 Repeat the following steps for each of the other nodes in the cluster:

■ Step 2through

■ Step 6


See “Installing the Veritas Cluster Server (VCS) software” on page 351.

Installing the Veritas Cluster Server (VCS) softwareThe following procedures explain how to install the VCS software.

Installing VCS 4.1 MP3Perform this procedure on the node you want to use as the storage pool authority.The installer automatically pushes the software to all nodes and installs thesoftware on all nodes.

The following notes pertain to this procedure and are explained at the appropriatesteps in the procedure:

■ This procedure uses the VCS menu-driven installer. After you make a selectionon the menu, press Enter. Many of the prompts propose a default. If you wantto accept the default, press Enter.

■ PDOS does not use all of the services on the VCS disk, so do not install allservices. For example, do not respond with Y, y, or Enter when the scriptprompts you to install the following VCS services:

■ VRTSvcsApache

■ VRTScssim

351Installing the clustering softwareInstalling the Veritas Cluster Server (VCS) software

PureDisk does not use these VCS services.

■ Do not respond with Y, y, or Enter when the script prompts you to configureVCS. A later procedure requires you to configure VCS with a configurationscript that is tuned to PureDisk.

Caution: Read the instructions that accompany each step in the followingprocedure. You cannot install VCS in a PureDisk environment by pressing Y, y, orEnter in response to each prompt. The result is an installation that is notcompatible with PureDisk. The procedure explains when to decline installationof unnecessary or incompatible components.

To install VCS 4.1 MP3

1 Insert the PureDisk software disk into a drive on that is capable of reading aDVD.

You can insert the disk into a drive that is attached to the storage poolauthority or into a drive that is attached to the failed node.

2 (Conditional) Type commands to mount the disk.

For example:

# mkdir /cdrom

# mount /dev/cdrom /cdrom

On a few hardware platforms, the cdrom device /dev/cdrom is not availableby default. If your device cannot find /dev/cdrom, see the troubleshootinginformation in the PureDisk Storage Pool Installation Guide.

3 Type the following command to change to the mount directory:

# cd /cdrom/vcsmp3

4 Type the following command to start the installer:

# ./installer

Installing the clustering softwareInstalling the Veritas Cluster Server (VCS) software

352

5 Respond to the script’s preliminary prompts as the following table describes:

NotesRecommended actionPrompt

Choice I indicates that you want toinstall a product.

Type I and press Enter..Enter a Selection :[I,C,L,P,U,D,Q,?]

Choice 1 indicates that you want toinstall the Veritas Cluster server.

Type 1 and press Enter..Select a product toinstall: [1-5,b,q]

Specify the FQDNs of the nodes youneed to recover. Do not specify theFQDNs of the nodes you do not needto recover.

Specify these as a space-separated listof FQDNs. Type the node FQDNs asyou specified them in the/etc/hosts file. For example:node1.acme.com

node2.acme.com

node3.acme.com

Type the unique host FQDNs for eachnode in the cluster. Use a space toseparate each FQDN.

Enter the system namesseparated by spaces onwhich to install VCS:

The installer generates messagesregarding a preinstallation systemcheck. Press Enter after the finalmessage, which indicates success.

Press Enter..Initial system checkcompletedsuccessfully.

The installer generates messagesregarding RPMs. Press Enter afterthe final message, which indicatessuccess.

Press Enter..VERITASInfrastructure rpmsinstalledsuccessfully.

6 Respond to the script’s licensing prompts as the following table describes:



The PDOS installer installed thelicense keys that you need for VCS.The VCS installer checks the licensekeys on all nodes in the cluster insequence and prompts you to installmore keys.

Take one of the following actions todecline the opportunity to installmore keys:

■ Press Enter.

■ Type n.

■ Type no.

You do not need to install more keys.

Press Enter.

(Make sure to press Enter inresponse to the prompt for eachnode.)

Do you want to enteranother license key fornode? [y,n,q,?] (n)

Press Enter.VCS licensing verifiedsuccessfully.Press [Enter] to continue:

Press Enter.VCS licensing completedsuccessfully.

7 Respond to the script’s package prompts regarding optional packages as thefollowing table describes:


View the RPM descriptions and selectoptional RPMs.

Type 3 and press Enter.Select the optional rpmsto be installed on allsystems? [1-3,q,?] (1)

PressEnter to install theVRTSvcsmnpackage.

Press Enter.Do you want to installthe VRTSvcsmn rpm on allsystems? [y,n,q] (y)

Do not install the VRTSvcsApachepackage.

Type n and press Enter.Do you want to installthe VRTSvcsApache rpm onall systems? [y,n,q] (y)

PressEnter to install theVRTSvcsdcdocumentation package.

Press Enter.Do you want to installthe VRTSvcsdc rpm on allsystems? [y,n,q] (y)


354

Press Enter to install the VRTScscmCluster Manager Java consolepackage. Symantec does not supportthe Cluster Manager Web console onPDOS platforms.

Press Enter.Do you want to installthe VRTScscm rpm on allsystems? [y,n,q] (y)

Do not install the Veritas ClusterServer Simulator package.

Type n and press Enter.Do you want to installthe VRTScssim rpm on allsystems? [y,n,q] (y)

The installer displays the list ofpackages to install after the followingheading:

Installer will install thefollowing VCS rpms:

Review the list of packages. Thefollowing packages should NOT be onthe list:

■ VRTSvcsApache

■ VRTScssim

Review the information that appearsand press Enter.

Press [Enter] to continue:

The installer displays the output frominstallation checks after the followingheading:

Checking systeminstallation requirements:

Review the information that appearsand press Enter.


Do not configure VCS at this time.Type n and press Enter.Are you ready toconfigure VCS?[y,n,q] (y)

Press Enter to install the clusterserver on all nodes simultaneously.

Press Enter.Would you like to installCluster Server on allsystems simultaneously?[y,n,q,?] (y)

The installer displays progressmessages.

Review the displayed information andpress Enter.

Cluster Serverinstallation completedsuccessfully.



You do not need to take any action tocorrect your configuration becausepersistent naming is guaranteedthrough /etc/udev/rules.d/

30-net_persistent_names.rules.

You can safely ignore any warningmessages that pertain toPERSISTENT_NAME.

Press Enter. several times inresponse to the PERSISTENT_NAMEmessages.


Decide whether to read the READMEfile and respond accordingly.

Press Enter

or

Type n and press Enter.

The README.1st file hasmore information aboutVCS. Read it Now? [y,n,q](y)

8 Enter commands to unmount and eject the PureDisk software disk.

For example:

# cd /

# umount /cdrom

# eject

9 Remove the disk.


See “Installing VCS 4.1 MP4 and VCS 4.1 MP4RP3” on page 356.

Caution: Do not reboot now. Install VCS 4.1 MP4 before you reboot.

Installing VCS 4.1 MP4 and VCS 4.1 MP4RP3The following procedure explains how to install VCS 4.1 MP4 and VCS 4.1 MP4RP3.


356

To install VCS 4.1 MP4 and VCS 4.1 MP4RP3

1 Put the PureDisk software disk into a drive that is capable of reading a DVD.

You can insert the disk into a drive that is attached to the storage poolauthority or into a drive that is attached to the failed node.

2 Type the following commands to mount the disk:

# mount /dev/cdrom /cdrom

# cd /cdrom/vcsmp4

On a few hardware platforms, the cdrom device /dev/cdrom is not availableby default. If your device cannot find /dev/cdrom, see the troubleshootinginformation in the PureDisk Storage Pool Installation Guide.

3 Type the following command to start the installer:

# ./installmp

4 Respond to the script’s prompts regarding the cluster as the following tabledescribes:


Specify the FQDNs of the nodes youneed to recover. Do not specify theFQDNs of the nodes you do not needto recover.

Specify a space-separated list ofFQDNs. Symantec recommends thatyou specify FQDNs. You also canspecify IP addresses. Type the nodeFQDNs as you specified them in the/etc/hosts file. For example:node1.acme.com

node2.acme.com

node3.acme.com


Enter the system namesseparated by spaces onwhich to install VERITASMaintenance Pack 4:

The installer displays the output fromcommunication checks after thefollowing heading:

Checking systemcommunication:

Press Enter.Press [Enter] to continue:


5 Respond to the script’s prompts regarding node-specific installationcharacteristics as the following table describes:


When the installer checks theupgrade requirements, it generateswarning messages about the followingpackages:

■ VRTSvxvmcommon

■ VRTSvxvmplatform

■ VRTSvxfscommon

■ VRTSvxfsplatform

Type y to continue with theinstallation in response to themessage about each of thesepackages.

Some of these messages indicate thata package of a more recent version(4.1.40.00) is installed. Thesemessages appear because of a PDOSpatch. Type y and press Enter tocontinue in response to each prompt.

Type y and press Enter.

The installer prompts you to stop theprocesses on each node. Confirm thestop for each node.

Press Enter.Do you want to stop theseprocesses and installpatches on node?[y,n,q] (y)

Note:The script repeats these questions for each node in the cluster. Respondto the prompts for each node.


358

6 Respond to the script’s prompts regarding completion as follows:



Upgrade requirement checkscompleted successfully.


You want to install the cluster serverupgrades on all nodes simultaneously.

Press Enter.Would you like to upgradeVERITAS Maintenance Pack4 rpms on all systemssimultaneously?[y,n,q,?] (y)

This step completes the installation.Press Enter.VERITAS Maintenance Pack4 installation completedsuccessfully.


7 Log into one of the failed nodes as root.

8 Type the following command to install VCS 4.1 MP4RP3:

# rpm -Uvh /opt/pdinstall/lib/vcs/MP4RP3/*.rpm

9 Repeat the following steps to install VCS 4.1 MP4RP3 on all failed nodes:

■ Step 7

■ Step 8

10 Unmount and eject the CD.

For example:

# cd /

# umount /cdrom

# eject


See “Configuring VCS” on page 360.


Configuring VCSUse the following procedure to configure VCS. The first steps require you to gatherinformation about the cluster. You need to specify unique information for thiscluster.

To configure VCS

1 Refer to this storage pool's cluster planning spreadsheet to confirm both theunique name for this cluster and the cluster ID number.

Note:The cluster ID number must be unique on your public network. Conflictswith existing cluster IDs can generate unpredictable results. The cluster IDnumber you specify in this procedure must be the same as the cluster ID thatthe storage pool already uses.

2 Log into the node that you want to configure as the storage pool authoritynode.

3 Change to the directory where the installation software resides.

For example:

# cd /opt/VRTS/install

4 Enter the following command to start the installation program:

# ./installvcs -configure

Installing the clustering softwareConfiguring VCS

360

5 Respond to the script's prompts.

In your responses, specify all nodes. Include the nodes you need to recover,the nodes you do not need to recover, and the passive nodes.

Respond to the script’s preliminary prompts as the following table describes:


Specify a space-separated list ofFQDNs. Type the node FQDNs as youspecified them in the /etc/hostsfile. For example: node1.acme.comnode2.acme.com

node3.acme.com


Enter the system namesseparated by spaces onwhich to configure VCS:


Checking systemcommunication:


Do not enter additional license keys.Press Enter.VCS licensing verifiedsuccessfully.


Stop the VCS processes.Press Enter.Do you want to stop VCSprocesses? [y,n,q] (y)

The script stops all VCS processes.Press Enter.VCS processes are stopped


The script displays information abouthow to respond to its prompts.

Press Enter.No configuration changesare made to the systemsuntil all configurationquestions are completedand confirmed.


361Installing the clustering softwareConfiguring VCS

6 Respond to the script’s cluster name and cluster ID configuration promptsas the following table describes:


This name must be unique on yournetwork. You cannot include spacesor numbers in this name.

Type a unique name for this cluster.Enter the unique clustername:

This number must be unique on yournetwork.

Type a unique ID number for thiscluster.

Enter the unique ClusterID number between0-65535: [b,?]

Caution: Before you proceed to the next step, make sure to record the uniquecluster name and the unique cluster ID for this cluster.

7 Specify heartbeat information and respond to the prompts about yourconfiguration that the installer detects.

Note: The installer’s prompts differ depending on your configuration. Thefollowing is an example session.

For example:

Discovering NICs on node1 .........................................................

discovered eth0 inet6 eth1 inet6 eth2 sit0

Enter the NIC for the first private heartbeat link on node1: [b,?] eth0

eth0 is probably active as a public NIC on node1

Are you sure you want to use eth0 for the first private heartbeat link? [y,n,q,b,?] (n)

y

Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y)

Enter the NIC for the second private heartbeat link on node1: [b,?] eth2

eth2 is probably active as a public NIC on node1

Are you sure you want to use eth2 for the second private heartbeat link? [y,n,q,b,?]

(n) y

Would you like to configure a third private heartbeat link? [y,n,q,b,?] (n)


362

8 Press Enter to confirm that you do not want to configure a third privateheartbeat on the primary NIC.

For example:

Do you want to configure an additional low priority heartbeat link? [y,n,q,b,?] (n)

9 In response to the prompt regarding the NICs on the other nodes, type y orn and press Enter.

When you type y, you affirm that each node contains NICs in the same order.

When you type n, you request that the system reissue the same prompts foreach node in the cluster. This prompt sequence differs for each installationdepending on your configuration.

Are you using the same NICs for private heartbeat links on all systems? [y,n,q,b,?] (y)

y

10 Press Enter to confirm the cluster information.

For example:

Cluster information verification:

Cluster Name: pdvcs1

Cluster ID Number: 1

Private Heartbeat NICs for node1: link1=eth0 link2=eth2



Is this information correct? [y,n,q] (y)

363Installing the clustering softwareConfiguring VCS

11 Respond to the script’s closing questions as the following table describes:


Do not configure Cluster Manager.Symantec does not support theCluster Manager on PDOS platforms.

Type n and press Enter.Do you want to configureCluster Manager (WebConsole) [y,n,q] (y)

Symantec supports the ClusterManager Java Console on PDOSplatforms, which you configure in alater procedure.

Do not configure SMTPType n and press Enter.Do you want to configureSMTP notification?[y,n,q] (y)

Do not configure SNMP.Type n and press Enter.Do you want to configureSNMP notification?[y,n,q] (y)

Press Enter to disregard allPERSISTENT_NAME messages foreach node and NIC.

Press Enter. several times inresponse to the PERSISTENT_NAMEmessages.


You do not need to take any action tocorrect your configuration becausepersistent naming is guaranteedthrough /etc/udev/rules.d/

30-net_persistent_names.rules.

You can safely ignore any warningmessages that pertain toPERSISTENT_NAME.

Press Enter.Cluster Server configuredsuccessfully.


Press Enter.Cluster Server wasstarted successfully.



364

Decide whether to read the READMEfile and respond accordingly.

Press Enter

or

Type n and press Enter.

The README.1st file hasmore information aboutVCS. Read it Now?[y,n,q] (y)

12 Type the following command to check the status of the open links:

# lltstat -n

The output returns a table that shows the link statuses. The output includesa line for each node and a link for each private heartbeat on each node. TheLINKS field shows the number of private heartbeats per node. Each one shouldbe in the OPEN state.

13 Repeat the following step on each node in the clustered storage pool:

■ Step 12


See “(Conditional) Using YaST to create the storage partitions” on page 365.

(Conditional) Using YaST to create the storagepartitions

Perform this procedure if the disks attached to the node you want to restore alsocrashed. In this case, you need to recreate your storage partitions. If the disksattached to the node you want to restore did not crash, you do not need to recreateyour storage partitions.

The following procedures explain how to use the YaST interface to create the/Storage partition.

You need to create storage partitions on only the active nodes. Recreate the storagepartitions just as they were before the disaster. In other words, create a /Storagepartition, and, if necessary, create a /Storage/data partition and a/Storage/databases partition, too. You do not need to create storage partitionson a passive node.

Starting YaSTThe following procedure explains how to start YaST.

365Installing the clustering software(Conditional) Using YaST to create the storage partitions

To invoke YaST

1 Log into one of the active nodes.

The active nodes are those upon which you want to install PureDisk services.

2 Type the following command to launch the SUSE Linux YaST configurationtool:

# yast

You can type yast or YaST to invoke the interface. Do not type othercombinations of uppercase and lowercase letters.

3 In the YaST Control Center main screen, select System > Partitioner.


5 On the Expert Partitioner screen, select VxVM.

6 (Conditional) Select Add Group.

You have the option to select Add Group only when at least one group isconfigured currently.

7 On the Create a Disk Group pop-up, type a unique name for the disk groupon this node.

8 Select OK.

9 On the Veritas Volume Manager: Disks Setup screen, highlight a disk thatyou want to include in the disk group.

10 Highlight Add Disk and press Return.

You can only add disks that are not yet partitioned. If you try to add a diskwith partitions, adding the disk to the disk group does not succeed. Delete allpartitions from the disk before you try to add partitions.

To delete all partitions on a disk, select Expert in the YaST interface andselect Delete Partition Table and Disk Label.

11 On the Add a name for the disk pop-up, type a name for the disk.

12 Select OK.


■ Step 9

■ Step 12

Installing the clustering software(Conditional) Using YaST to create the storage partitions

366

14 Select Next.


See “Creating the storage partitions” on page 367.

Creating the storage partitionsThe following procedure explains how to create /Storage.

To create /Storage

1 On the Veritas Volume Manager: Volumes screen, select Add.

The Create Volume pop-up appears.

2 On the Create Volume pop-up, in the Volume Name field, specify Storage.

Note: Do not specify a size or a mount point.

3 Select OK.

4 Select Next.

5 (Conditional) Create a /Storage/data partition.

Perform the following steps to create a /Storage/data partition if this nodehad a /Storage/data partition before the disaster:

■ On the Veritas Volume Manager: Volumes screen, select Add.The Create Volume pop-up appears.

■ On the Create Volume pop-up, in the Volume Name field, specifyStorage_data.


■ Select OK.

■ Select Next.

6 (Conditional) Create a /Storage/databases partition.

Perform the following steps to create a /Storage/databases partition if thisnode had a /Storage/databases partition before the disaster:

■ On the Veritas Volume Manager: Volumes screen, select Add.The Create Volume pop-up appears.

367Installing the clustering software(Conditional) Using YaST to create the storage partitions

■ On the Create Volume pop-up, in the Volume Name field, specifyStorage_databases.


■ Select OK.

■ Select Next.

7 Select Apply.

8 On the Changes pop-up that appears, select Apply.

9 Select Quit.

10 Select Quit (again).

11 (Optional) Reboot the node.

Perform this step if you want to test it for reboot persistence.

12 Type the following command to view the disk summary for this node:

# vxdisk -o alldgs list

Installing the clustering software(Conditional) Using YaST to create the storage partitions

368

Command Line Interfaceoptions for PureDisk

BAppendix

General MAN page for PureDisk CLIGeneral MAN page for PureDisk CLI – A text-based interface for managingSymantec NetBackup PureDisk.

DESCRIPTIONNetBackup PureDisk offers customers a software-based data deduplication solutionthat integrates with NetBackup. It provides customers with the critical featuresrequired to protect all their data – from remote office to virtual environment todatacenter. It reduces the size of backups with a deduplication engine that can bedeployed for storage reduction. It uses integration with NetBackup, for bandwidthreduction using PureDisk clients. An open architecture allows customers to easilydeploy and scale NetBackup PureDisk using standard storage and servers.

NOTES■ The command line interface commands are found only on the storage pool

authority in the /opt/pdcli/calls directory.

■ All man pages that are associated with the commands are located in the/opt/pdcli/man directory.

■ Precede special symbols in arguments with an escape character. In the bashshell, use the single quotation mark (') to accomplish that. See the example.Example: '"any argument can fit in here, even arguments with a ¦

symbol"'

■ The command line interface commands can be used to script activities. Be surethe first command that is entered in the script is the pdlogonuser command.If you do not run pdlogonuser, you are prompted for a user name and passwordbefore each command is executed.

■ The contents of all man pages are collected in a PDF format for offline viewing.See the PureDisk Command Line Interface Guide.

PUREDISK COMMANDS GROUPED BY FUNCTIONGeneral commands

■ pdactivateagent - Activates the agent software on a client computer.

■ pdbackup - Creates a backup job for the client specified.

■ pdbackupstop - Used to stop any running job.

Command Line Interface options for PureDiskGeneral MAN page for PureDisk CLI

370

■ pddeactivateagent - Deactivates the agent software on a client computer soit is no longer backed up by active PureDisk policies.

■ pdexit - Removes any locally saved credentials.

■ pdexport2nbu - Exports a data selection to a NetBackup files list for use witha NetBackup policy.

■ pdfindfiles - Used to find the files that have been backed up.

■ pdlogonuser - Saves the credentials locally to avoid interaction during calls.

■ pdpasswd - Used to set or change a user password.

■ pdrestore - Start a restore job from the specified parameters.

■ pdrunpolicy - Executes the specified policy.

■ pdstatlicensing - Collects and displays extra information about the licensekeys.

■ pdupgrade - Used to initiate the upgrade of client software on the specifiedclient.

Create functions

■ pdcreatebackuppolicy - Creates a new backup policy.

■ pdcreatedataremovalpolicy - Creates a policy to remove data from a contentrouter.

■ pdcreatedepartment - Creates a new department that is used to organize clientsystems.

■ pdcreateds - Creates a new selection of files and directories on a PureDiskclient for backup.

■ pdcreatedstemplate - Used to create data selection templates.

■ pdcreateeventescalation - Creates a new event escalation .

■ pdcreategroup - Creates a new group that is used to organize users with thesame permissions.

■ pdcreatelocation - Creates a new logical grouping for one or moredepartments.

■ pdcreatembgarbagecollectionpolicy - Creates a new metabase garbagecollection policy.

■ pdcreatepolicyescalation - Creates a new policy escalation.

■ pdcreatepolicyescalationaction - Creates a new policy escalation action.

371Command Line Interface options for PureDiskGeneral MAN page for PureDisk CLI

■ pdcreatereplicationpolicy - Creates a new replication policy.

■ pdcreatesmtpeventescalationaction - Creates an SMTP event escalationaction.

■ pdcreatesnmpeventescalationaction - Creates an SNMP event escalationaction.

■ pdcreateuser - Creates a new user within PureDisk that can be assigned rightsand permissions.

Delete functions

■ pddeleteagent - Deletes an agent from the PureDisk database.

■ pddeletedepartment - Deletes a department from the storage pool authority(SPA).

■ pddeleteds - Deletes a data selection from a PureDisk policy.

■ pddeletedstemplate - Deletes a data selection template.

■ pddeleteeventescalation - Unbinds an event escalation action from theagent or the storage pool.

■ pddeleteeventescalationaction - Deletes an SMTP action or SNMP action.

■ pddeletegroup - Deletes a user group from the storage pool authority (SPA).

■ pddeletejob - Raises an error and tries to kill the job. If the job is running, itdoes not delete the job. If the job is not running, it deletes the job.

■ pddeletelicense - Deletes a license key.

■ pddeletelocation - Deletes a location from the storage pool authority (SPA).

■ pddeletepolicy - Deletes a policy.

■ pddeletepolicyescalation - Links a policy with a policy escalation action.

■ pddeletepolicyescalationaction - Deletes a policy escalation action.

■ pddeleteuser - Deletes a user from the storage pool authority (SPA).

Get functions

■ pdgetagent - Provides additional information about the agent object specified.

■ pdgetdepartment - Provides additional information about the departmentobject specified.

■ pdgetds - Provides additional information about the data selection objectspecified.


372

■ pdgetdstemplate - Provides information about the data selection templatespecified.

■ pdgeteventescalation - Provides information about the event escalationspecified.

■ pdgeteventescalationaction - Provides information about the eventescalation action specified.

■ pdgetgroup - Provides additional information about the group object specified.

■ pdgetjob - Provides additional information about the job object specified.

■ pdgetjobstat - Retrieves the job statistics from the PureDisk database.

■ pdgetjobsteps - Used to list the steps that are associated with the specifiedjob.

■ pdgetlicense - Collects information about the specified license key.

■ pdgetlocation - Provides additional information about the location objectspecified.

■ pdgetpolicy - Provides additional information about the policy object specified.

■ pdgetpolicyescalation - Provides information about the policy escalationobject.

■ pdgetpolicyescalationaction - Provides information about the policyescalation action.

■ pdgetstoragepool - Provides information about the storage pool.

■ pdgetuser - Provides information about the user object specified.

List functions

■ pdlistagent - Displays all agents that are associated with a particular PureDiskenvironment.

■ pdlistdepartment - Displays all departments that are associated with aparticular PureDisk environment.

■ pdlistds - Displays all data selections that are associated with a particularPureDisk environment.

■ pdlistdstemplate - Displays all the data selection templates.

■ pdlistevent - Displays all events that are associated with a particular PureDiskenvironment.

■ pdlisteventescalation - Displays all the event escalations.


■ pdlisteventescalationaction - Displays a list of all the event escalationactions.

■ pdlistgroup - Displays all the user groups that are associated with a particularPureDisk environment.

■ pdlistjob - Displays all jobs that are associated with a particular PureDiskenvironment.

■ pdlistlicense - Displays all the installed license keys.

■ pdlistlocation - Displays all the locations that are associated with a particularPureDisk environment.

■ pdlistpolicy - Displays all the policies that are associated with a particularPureDisk environment.

■ pdlistpolicyescalation - Displays the policy escalations that are attachedto a policy.

■ pdlistpolicyescalationaction - Displays all the actions that are attachedto a policy.

■ pdlistuser - Displays all the users that are associated with a particularPureDisk environment.

Set functions

■ pdsetagent - Changes and updates the details that are associated with anexisting agent.

■ pdsetbackuppolicy - Change the parameters of an existing backup policy.

■ pdsetcrgarbagecollectionpolicy - Change the parameters of an existingcontent router garbage collection policy.

■ pdsetdatalock - Resets the data lock password.

■ pdsetdataminingpolicy - Change the parameters of an existing data miningpolicy.

■ pdsetdataremovalpolicy - Change the parameters of an existing data removalpolicy.

■ pdsetdebugagent - Change the debugging parameters for the agent.

■ pdsetdepartment - Changes and updates the details that are associated withan existing department.

■ pdsetds - Changes and updates the details that are associated with an existingdata selection.


374

■ pdsetdsremovalpolicy - Change the parameters of an existing data selectionremoval policy.

■ pdsetdstemplate - Changes and updates a data selection template.

■ pdseteventescalationaction - Change the parameters of an existingescalation action.

■ pdsetgroup - Changes and updates the details that are associated with anexisting user group.

■ pdsetlicense - Adds a license key.

■ pdsetlocation - Changes and updates the details that are associated with anexisting location.

■ pdsetmaintenancepolicy - Change the parameters of an existing maintenancepolicy.

■ pdsetmbgarbagecollectionpolicy - Change the parameters of an existingmetabase garbage collection policy.

■ pdsetperm - Sets the permissions for a user.

■ pdsetpolicyescalationaction - Change the parameters of an existing policyescalation action.

■ pdsetreplicationpolicy - Change the parameters of an existing replicationpolicy.

■ pdsetserverdbmaintenancepolicy - Change the parameters of an existingserver database maintenance policy.

■ pdsetstoragepool - Changes and updates the specified parameters for astorage pool.

■ pdsetuser - Changes and updates the details that are associated with anexisting user.



376

Third-party legal notices

This appendix includes the following topics:

■ Third-party legal notices for Symantec NetBackup PureDisk

Third-party legal notices for Symantec NetBackupPureDisk

Active Directory, Excel, Internet Explorer, Microsoft, Windows, Windows NT, andWindows Server are either registered trademarks or trademarks of MicrosoftCorporation in the United States and other countries.

AIX, IBM, PowerPC, and Tivoli are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both.

All SPARC trademarks are used under license and are trademarks or registeredtrademarks of SPARC International, Inc., in the United States and other countries.Products bearing SPARC trademarks are based upon an architecture developedby 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 ofIntel Corporation or its subsidiaries in the United States and other countries.

Java, Sun, and Solaris are trademarks or registered trademarks of SunMicrosystems, Inc., in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States and othercountries.

Mac OS is a trademark of Apple Inc., registered in the U.S. and other countries.

CAppendix

NetApp is a registered trademark of Network Appliance, Inc. in the U.S. and othercountries.

Novell and SUSE are registered trademarks of Novell, Inc., in the United Statesand other countries.

OpenLDAP is a registered trademark of the OpenLDAP Foundation.

Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc., in theUnited States and other countries.

UNIX is a registered trademark of The Open Group.

VMware, vSphere, and the VMware "boxes" logo and design are trademarks orregistered trademark of VMware, Inc., in the United States and other countries.

Third-party software may be recommended, distributed, embedded, or bundledwith this Symantec product. Such third-party software is licensed separately byits copyright holder. All third-party copyrights associated with this product arelisted in the Third Party Legal Notices document, which is accessible from thePureDisk Web UI.

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

378

AAccessing a managed storage pool 303ACL errors restore job statistic 224ACL restore job statistic 224activating a new PureDisk component 287Activating a server agent 92adding PureDisk components 280authentication key 347, 349Average restore rate restore job statistic 224

BBackup job statistics 219Backup speed backup job statistic 219Backup time duration backup job statistic 219Backup time duration PDDO backup job statistic 228Bytes deleted in source data selection replication job

statistic 227Bytes deleted on source backup job statistic 219Bytes modified in source data selection replication

job statistic 227Bytes modified on source backup job statistic 219Bytes modified on target restore job statistic 224Bytes new in source data selection replication job

statistic 227Bytes new on source backup job statistic 219Bytes new on target restore job statistic 224Bytes not modified on source backup job statistic 219Bytes received by agent restore job statistic 224Bytes replicated replication job statistic 227Bytes scanned during backup PDDO backup job

statistic 228Bytes selected on source backup job statistic 219Bytes total restore job statistic 224Bytes transferred backup job statistic 219Bytes transferred replication job statistic 227Bytes transferred to content router PDDO backup job

statistic 228Bytes unmodified on target restore job statistic 224Bytes with errors restore job statistic 224Bytes with replication errors replication job

statistic 227

Ccentral storage pool

disabling 302enabling 301managing 303testing connections 304

clusteringadministering a storage pool 310also see disaster recovery - clustered storage

pools 157configuration example 341examining NICs for addressing 343installing VCS 4.1 MP3 software 351installing VCS 4.1 MP4 software 356removing addressing from NICs 346synchronizing passwords 347VCS software requirements 341

configuration filesediting agent configuration files for large

backups 333editing ASCII files 326editing through Web UI 322pushing changes 325updating agent configuration files 327

configuringsee reconfiguring PureDisk 321

configuring SPAR 201–202copying a replication policy 68

Ddashboard reports 249data lock password

export to NetBackup 84files tab 215

data mining reports 233data replication

copying replicated data 70managing replicated data selections 68policies

copying and deleting 68creating 61

Index

data replication (continued)policies (continued)

full replication 66incremental replication 66scheduling 66viewing replication jobs 68

restoring replicated data 70understanding 59using replicated data 68viewing replicated data selections 68

data selectionremoval policies

scheduling 42date replication policy

creating 62editing 62

deleting a replication policy 68Devices restore job statistic 224Directory count restore job statistic 224disaster recovery

backup procedurescreating backup or restore scripts 115policies 106troubleshooting 117using NetBackup 100–101using scripts 100, 114

clustered storage poolsDR_Restore_all script 175restoring PureDisk 157

strategies 201unclustered storage pools

DR_Restore_all script 122restore examples 122restoring PureDisk 121

DR_Restore_all script 122, 175

EError count restore job statistic 224export engine

see NetBackup - export engine 73external directory service authentication

adding PureDisk groups 19changing TLS specification 46disabling 45introduction 18linking with PureDisk 33maintaining PureDisk groups 43modifying the base search path 46synchronizing with PureDisk 40, 42

external directory service authentication (continued)verifying TLS 29

Ffile-type segmentation 336Files deleted on source backup job statistic 219Files modified on source backup job statistic 219Files modified on target restore job statistic 224Files new on source backup job statistic 219Files new on target restore job statistic 224Files not modified on source backup job statistic 219Files selected on source backup job statistic 219Files unmodified on target restore job statistic 224Files with errors restore job statistic 224

GGlobal data reduction factor backup job statistic 219Global data reduction saving PDDO backup job

statistic 228Global data reduction savings backup job statistic 219

HHard links restore job statistic 224

Iinternational characters 272Items deleted in source data selection replication job

statistic 227Items modified in source data selection replication

job statistic 227Items new in source data selection replication job

statistic 227Items replicated replication job statistic 227Items with replication errors replication job

statistic 227

Llicense keys

adding and removing 299report generation 304required 74viewing in reports 259

log files 261

MManaged storage pool

Accessing 303

Index380

Media server cache hit percentage PDDO backup jobstatistic 228

metabase enginererouting 304

multistreamed (parallel) backups 334multistreamed (parallel) restores 335multistreamed replication 337

NNetBackup

disaster recovery 100–101export engine 73

adding the service 280configuring 75exporting Files and Folders data

selections 85job failures 92point-in-time export 91restoring 94server agents and export jobs 92

NICsexamining for existing addresses 343removing addressing 346

Ooptimization 331, 337

Ppassword synchronization 347PDDO backup job statistics 228pdkeyutil utility 117PDOS

changing the password 310performance optimization

file-type segmentation 336multistreamed (parallel) backups 334multistreamed (parallel) restores 335segmentation options for backup jobs 336segmentation threshold values 336

policiesdata mining 233data replication 61disaster recovery backup procedures 106exports to NetBackup 85NetBackup DataStore 91run once 66, 109

processesstopping and starting on a multinode PureDisk

storage pool 318stopping and starting on a PureDisk node

(clustered) 317stopping and starting on a PureDisk node

(unclustered) 314PureDisk Web UI

Starting an additional 303

Rreconfiguring PureDisk

editing agent configuration files for largebackups 333

editing configuration files 322overview 321updating agent configuration files 327

recovery from a disaster 121, 157removing a content router 296replication

see data replication 59see storage pool authority replication

(SPAR) 199Replication job statistics 227Replication time duration replication job statistic 227replication tuning 337reports

central storage pool 254, 301central storage pool test connection 304dashboards 249, 254data mining 233finished job 218for a running job 215overview 214permissions 214web service 242

rerouting a metabase engine 304Restore job statistics 224Restore time duration restore job statistic 224RestoreSPASIO command 209restoring from NetBackup 94retrieving information from a data mining policy 236

Ssegmentation options for backup jobs 336segmentation threshold value 336server agents

activating 92

381Index

single port communication 49single port communications 66SIS

see data deduplication 238Source bytes backed up backup job statistic 219Source bytes with errors backup job statistic 219Source files backed up backup job statistic 219Source files with errors backup job statistic 219SSH public keys 348, 350Start date/time backup job statistic 219Start date/time PDDO backup job statistic 228Start date/time replication job statistic 227Start date/time restore job statistic 224Starting another PureDisk Web UI 303Statistics for a backup job 219Statistics for a PDDO backup job 228Statistics for a replication job 227Statistics for a restore job 224Stop date/time backup job statistic 219Stop date/time PDDO backup job statistic 228Stop date/time replication job statistic 227Stop date/time restore job statistic 224stopping and starting processes

multinode PureDisk storage pool 318PureDisk node (clustered) 317PureDisk node (unclustered) 314

storage pool authority replication (SPAR)disaster recovery strategies 201enabling backups 204example 199RestoreSPASIO command 209restoring 207running a SPAR policy manually 206upgrading PureDisk with SPAR enabled 211

storage pool managementactivating a new PureDisk service 287adding and removing license keys 299adding PureDisk components 280adjusting the clock on a PureDisk node 312administering a clustered storage pool 310changing database or LDAP admin

passwords 311changing the PDOS password 310disabling central reporting 302enabling central reporting 301increasing the number of client connections 311license key report generation 304managing in the central storage pool 303removing a content router 296

storage pool management (continued)rerouting a metabase engine 304testing connections 304

storage poolsstopping and starting processes 318

Symbolic links restore job statistic 224

TTime-out interval, adjusting 314Total files restore job statistic 224troubleshooting

NetBackup export engine jobs 92tuning 331, 337

UUnique bytes backed up backup job statistic 219Unique files and folders backed up backup job

statistic 219Unique items received restore job statistic 224Unique items restored restore job statistic 224user authentication

root broker 254

VVCS

configuring 360installing VCS 4.1 MP3 software 351installing VCS 4.1 MP4 software 356preparing to install 341

Verification failures restore job statistic 224Verification successes restore job statistic 224

Wweb service reports 242Web UI

Starting an additional 303

YYaST 365

Index382

puredisk admin

Documents