You are on page 1of 214

Symantec NetBackup PureDisk™ Storage Pool Installation Guide

Windows, Linux, and UNIX

Release 6.6

Publication release 6.6, revision 3

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 6.6, revision 3

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

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

Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec’s maintenance offerings include the following:

A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week Advanced features, including Account Management Services

■ ■ ■

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

Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support information at the following URL: www.symantec.com/techsupp/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:
■ ■ ■ ■

Product release level Hardware information Available memory, disk space, and NIC information Operating system

gateway.com/techsupp/ Customer service Customer service information is available at the following URL: www. access our technical support Web page at the following URL: www.symantec.symantec. and IP address information Problem description: ■ ■ ■ Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key. such as address or name changes General product information (features.com/techsupp/ Customer Service is available to assist with the following types of issues: ■ ■ ■ ■ ■ ■ ■ ■ ■ Questions regarding product licensing or serialization Product registration updates.■ ■ ■ ■ Version and patch level Network topology Router. 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 .

and global insight. which enable you to manage your business risks proactively. please visit our Web site at the following URL: www. Middle-East.com Additional enterprise services Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge. and countermeasures to prevent attacks before they occur.symantec. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment. security education. and awareness communication programs.com Select your country or language from the site index. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks. security certification. Each is focused on establishing and maintaining the integrity and availability of your IT resources. monitoring. and Africa North America and Latin America customercare_apac@symantec. expertise. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. . Managed Security Services These services remove the burden of managing and monitoring security devices and events. please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan Europe. Educational Services provide a full array of technical training. implementation. design. Consulting Services Educational Services To access more information about Enterprise services.com supportsolutions@symantec.Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement. comprehensive threat analysis.com semea@symantec. ensuring rapid response to real threats. and management capabilities.

........................................................... Completing the Network Configuration page ............................. Completing the Installation Settings page ...... File system configuration ............................................. swap........................................ Completing the PureDisk Node Configuration page ........................................... Performing a PureDisk initial installation ....... and / partitions ................................. (Optional) Choosing an installation method and cleaning a node that hosted PDOS previously .................................................................................................... Initiating a manual PDOS installation ...................... Choosing an installation method . Completing the Symantec EULA page ................................................................ Completing the Preparing the System for Automated Installation page ................................................................ Configuring an environment for specific features .... 39 40 40 41 42 ................................................................................................... 25 26 28 29 Chapter 3 Installing PDOS with the installation wizard ...... Manual installation process overview ...........................Contents Technical Support .................. Preparing to install PDOS .................... 31 32 32 34 36 36 Chapter 4 Installing PDOS manually .................................................... Third-party components ........................................... Configuring the /boot......................................... Chapter 2 Installing the PureDisk operating system ......................................... 31 About the PDOS installation wizard ..............................................5 administrators ................. Performing a PureDisk upgrade .. 39 About installing PDOS manually .................................................... PureDisk 6................................................................6 installation information for PureDisk 6........... 4 Chapter 1 Installation overview ..................................................... 25 About PureDisk operating system (PDOS) installations ...................................................................... 15 15 15 17 20 23 23 23 About PureDisk installations ............. Types of storage pools ............................................................................................................................................

........................................... Configuring a node with /Storage................ (Conditional) Configuring an iSCSI environment ............. RAID configuration alternatives .................. (Conditional) Preparing to configure a clustered PureDisk storage pool ...... swap.................................................................................... /etc/resolv.................... and /Storage/databases partitions .............8 Contents About the /boot..... Gathering information for a storage pool ......... Storage partition configuration tool alternatives....... and / partitions ............................................. Preparing to configure a remote root broker ......................................... 55 56 58 58 59 60 61 62 62 63 63 64 64 65 65 66 66 67 71 71 73 75 ................................. 42 42 44 46 47 48 50 53 Chapter 5 Preparing to configure the storage pool .................... Configuring a node with a /Storage partition .................. Verifying hardware and (conditionally) downloading additional software ..................................... 55 About preparing to configure the storage pool ........................ and volume manager alternatives .....conf file .... (Conditional) Disabling multipathing ....................... Verifying hardware compatibility.......... (Conditional) Updating the /etc/hosts file on the PDOS nodes ....................................................................................................... Gathering NIC information ....... Configuring the /boot................................. (Conditional) Editing the /etc/resolv...................................... Examining the NICs in this node for addressing .... Specifying the host name... file system alternatives........ (Conditional) Editing client networking information ............................................................................................................................................... Configuring a node with a /Storage and a /Storage/data partition ................................. and miscellaneous settings ....................... Verifying the installation ............................................................................................................................... Reviewing the Veritas Cluster Server (VCS) requirements ........... /Storage/data...................................................................... and / partitions ..... downloading additional software...................... Configuring static addressing ....................................................................................... (Conditional) Preparing a remote root broker or an external root broker . and client networking files ... Planning the storage partitions (DAS/SAN disks) .............. networking.......................... Configuring addressing ......................................... Preparing to configure an external root broker ........ and disabling multipathing .............. swap................................ Completing an Expert installation ........................ (Conditional) Editing the /etc/hosts files........................................conf file........................................

.. 94 Completing the Storage Pool Node Summary subpage ............. 86 Characters prohibited in storage pool configuration file fields ....................... 107 Completing the Root Broker Configuration page ............................................................................................................................ 89 Starting the storage pool configuration wizard ...................................................... 98 Reference information for the Storage Selection subpages ...... 88 Cancel button effects ........ 91 Completing the Add Additional License Key subpage ............................................................ 108 Completing the Selection Summary page ... (Conditional) Installing the Veritas Cluster Manager Java Console ............................................................................ 110 Completing the Implementation page .......... Installing a Cluster Manager Java Console Windows client ................................................ 96 Configuring disk groups .................................... 111 115 115 116 ...... 85 About configuring the storage pool ........... 96 Completing the Storage Selection pages .................................................................Contents 9 Verifying iSCSI prerequisites .................... 110 Chapter 7 Completing the installation .............................. 81 Chapter 6 Configuring the storage pool ............................ 76 Planning the storage partitions ........... 89 Completing the Welcome page ........................................................... Installing a Cluster Manager Java Console Linux client .. 94 Completing the Add New Node subpage ............................................................................................................................................................................................ 91 Completing the Storage Pool Details page ... 111 Completing the storage pool installation .................................................................. 90 Completing the PureDisk Licenses pages ................................................................................................................................... 91 Completing the License Key Management page ........................... 107 Completing the Services Configuration page for a clustered storage pool ................................. 85 Configuring the storage pool ........ 75 Configuring the second NIC for the iSCSI network ........................................................................................................ 106 Completing the Services Configuration page for an unclustered storage pool ............................................... 92 Completing the Node Selection pages ................. 105 Completing the Cluster Details subpage .............. 100 (Conditional) Completing the Cluster Option pages ........ 105 Completing the Services Configuration page ............... 95 Completing the Edit Node subpage ................................................. 105 Completing the Cluster Heartbeat Configuration subpage ................................................. 97 Configuring disk volumes and mount points ..................

.................... (Conditional) Adding new license keys .6 ................ 119 About upgrading to PureDisk 6............................................................ Upgrading PDDO clients on NetBackup Windows media servers ...................... Upgrading the storage pool software to PureDisk 6.......6 .................. 119 120 120 121 122 123 125 126 126 128 128 129 130 132 134 134 135 137 138 138 139 139 Appendix A Navigating the YaST2 interface ........................................................ Installation worksheets ......... Upgrading standard clients manually ........10 Contents Installing the Cluster Manager Java Console administrator software ............................................................................................................ Applying updates after you upgrade to PureDisk 6.......................................6 .................................6 .......................... 143 144 144 145 145 ................................................................................................... Addressing transaction log messages .......................................... Obtaining the agent ID numbers ...................................................................................... Upgrading the operating system software to PDOS 6............................................. Starting the PDOS upgrade ................................................. Upgrading PureDisk agent software on clients .................................................................... 143 About the installation worksheets ....................... The PureDisk 6.................................................................... Finishing the upgrade ................. Completing the PDOS upgrade ...................... Fixing a failed upgrade .................................................................................. Performing the PDOS upgrade .......................... 141 About the YaST2 interface .......................... Upgrading PDDO clients on NetBackup Linux and UNIX media servers .. Performing an upgrade .............. 117 Chapter 8 Upgrading PureDisk software ................................................................................................. Prioritizing storage pool upgrades ............ Verifying the environment .............................................................................................. Upgrade effects .................................... Initiating the storage pool software upgrade .........................6 upgrade path ............................................................................................................................................................................................ YaST2 navigation key sequences ........................... Troubleshooting and notes ......... Function keys ......................... Starting YaST2 ................. Obtaining the storage pool ID number ........ 141 141 142 142 Appendix B Installation worksheets (unclustered) ...................... Worksheet 1 .................................................................................

................. Adding. 183 About troubleshooting PureDisk installations ................................................................................. Changing the TLS specification ...................Contents 11 Worksheet 2 ............................................................. Modifying the base search path ............................................................................... or deleting users or groups ..... Example Active Directory service ....................................................... Configuring communication ...................................... Worksheet 3 ......xml file .... Example OpenLDAP directory service ............................................................................ Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service .......................................... Worksheet 5 ............................................................... About maintaining synchronization between PureDisk and an external directory service ........ Disabling external authentication ....................................................................................................................... Changing the yourdescriptionattrib variable or the yourmailattrib variable in your directory service’s ldap............................ Writing the certificate to the storage pool authority .............................. 151 About external directory service authentication ...............................xml file .............. Changing the youruserclass................................. 183 184 184 185 ............................................................................ or yournameattrib variables in your directory service’s ldap.............. Obtaining directory service information . Verifying the server name ........ Worksheet 6 ..... changing..... Assumptions ................................ Managing user groups .............. Worksheet 4 ................................................................................... I/O errors causing system hangs during installation ........................................................................... (Optional) Adding PureDisk groups to your directory service .................. User accounts .. 152 152 153 153 155 159 162 163 163 164 167 168 173 174 175 176 176 177 178 178 179 180 180 Appendix D Troubleshooting .................... yourloginattrib......... Completing the Scheduling tab ......................................................................... Troubleshooting a PureDisk operating system (PDOS) installation ........... Linking PureDisk to the external directory service ...................................................................................................................................................................................................................... Completing the General tab .......... 146 146 147 148 149 Appendix C Configuring external directory service authentication ....................................... Errors caused by disk misconfiguration ........................................ (Optional) Verify TLS and copy the CA certificate ............................................................................................

........................................................................................................................ 185 185 186 186 187 187 188 188 188 188 189 190 191 193 193 194 195 Appendix E Using Veritas Storage Foundation tools with PureDisk ........ 199 About single port communication ............................... Troubleshooting mount errors on /mnt/cdrom ......................... Stopping all services ........................................................................................................ (Conditional) Redefine the PureDisk storage pool to use FQDNs ......................................................................... Starting all services without rebooting .................................................... Stopping and starting a multinode PureDisk storage pool .................................. Configuring your domain name server (DNS) and firewall ..... 198 About VxVM’s role in a PureDisk storage pool .......... Stopping and starting processes on one PureDisk node (clustered) ........................................................... Adding FQDNs to each service ............................. Generating new passwords for the internal database and for the LDAP administrator ........................................................................... Troubleshooting a storage pool installation ........... Stopping and starting individual services ................................................ Replacing network information cards (NICs) and updating the device name in clustered storage pools ............................................................. (Conditional) Configuring port 443 in replication policies ................................... Configuring a /dev/cdrom device .............. Starting all services . Stopping and starting processes on one PureDisk node (unclustered) ............................... 197 Installing the VEA client software on a Windows client ........... Configuring single-port communication .......................................................................................................................... Specifying port number 443 as the default port in the configuration file template .............................................. Installing agent software on the clients or moving clients ............................... 198 Appendix F Configuring single port communication ................................... Error caused by a stopped VxVM driver .............................. Resolving errors caused by a previous Windows installation on a partition ................................. Creating a new department with single-port settings .. Restarting the Java run-time environment ................................ 197 About the Veritas Enterprise Administrator’s role in a PureDisk storage pool ................................................. Starting PDOS in rescue mode .....12 Contents Errors caused by a lack of disk space .......................................................................................... 199 200 201 202 204 204 207 208 209 .......................................................

.................................. 211 Index ........................Contents 13 Installing agent software for an initial installation ............................................... 213 ... 211 Third-party legal notices for Symantec NetBackup PureDisk ................................................................. 209 Appendix G Third-party legal notices ........................ 209 Moving clients to the new department for an upgrade .....................

14 Contents .

Chapter 1 Installation overview This chapter includes the following topics: ■ ■ ■ ■ ■ About PureDisk installations PureDisk 6. See “Performing a PureDisk initial installation” on page 17.5 administrators” on page 15.6 installation information for PureDisk 6. See “Performing a PureDisk upgrade” on page 23. .5 administrators Performing a PureDisk initial installation Performing a PureDisk upgrade Third-party components About PureDisk installations The PureDisk Storage Pool Installation Guide explains how to install a storage pool for the first time and how to upgrade an existing storage pool.5 installation procedure.6 installation procedure is significantly different from the PureDisk 6. See “Third-party components” on page 23.5 administrators The PureDisk 6.6 installation information for PureDisk 6. ■ ■ ■ PureDisk 6. The following topics provide more information about the installation process and upgrade process: ■ See “PureDisk 6.6 installation information for PureDisk 6.

Run edit_topology.16 Installation overview PureDisk 6. be aware of the differences shown in the following table: PureDisk 6. and other storage pool features.sh to install the storage pool software.sh on all nodes to configure cluster service groups.5 procedure From the software CDs. You can use the Veritas Enterprise Administrator (VEA) to configure more complicated storage systems.5 installation procedure. From the PDOS main menu.sh to configure the storage pool features. (Conditional) Run cluster_config. Alternatively. VCS (optionally).sh to push your configuration to the storage pool.1 MP4. Do not configure any storage. If you want to install a new PureDisk 6.6 storage pool. If you have PureDisk installation experience that you gained from a previous PureDisk release.6 procedure From the software DVD. install PDOS on a single-node or on multiple nodes. PureDisk 6.6 installation information for PureDisk 6. including the configuration of the storage subsystem. The new wizards eliminate the need for you to specify information multiple times. (Conditional) Run the Veritas Cluster Server (VCS) installation and configuration scripts. and so on.6: .5 administrators The new PDOS installation wizard and the new storage pool configuration wizard guide you through the entire installation and configuration process. you can use the VEA to configure your storage partitions. you can use the Install (wizard) or Expert (manual) method to install PDOS. Run install_newStoragePool. For example.1 MP3 and VCA 4. the wizard helps you configure authentication. and you are familiar with the PureDisk 6. Run install. Run the storage pool configuration wizard to configure the storage partitions and the storage pool features. clustering. observe the following guidelines when you install PureDisk 6. Configure VCS. The wizards guide you through the deployment process. install PDOS and configure storage. PureDisk services. multinode configuration. Install VCS 4.

For both types of installations. Symantec recommends that you avoid choosing the Expert option on the PDOS main menu. The Expert option is intended for broken hardware or unconventional hardware platforms only. The PDOS 6. . Figure 1-1 shows the major steps in the installation process.Installation overview Performing a PureDisk initial installation 17 ■ Do not configure your storage partitions during the PDOS installation.6 installation wizard installs VxVM at the end of the PDOS installation. You can use the storage pool configuration wizard or VEA to configure the storage partitions after the PDOS installation. Performing a PureDisk initial installation The PureDisk installation process lets you install either a highly available. clustered storage pool or an unclustered storage pool. ■ For information about VEA. the installation process is identical. Symantec recommends that you use the PDOS installation wizard to install PDOS. select the Install option on the PDOS main menu. see the following: ■ See “About the Veritas Enterprise Administrator’s role in a PureDisk storage pool” on page 197. To start the PDOS installation wizard.

Start the storage pool configuration wizard. select one of the following methods: Install (recommended) Expert Prepare the nodes for the storage pool installation. The following list explains the installation process in more detail: . See the chapter called “Preparing to configure the storage pool” in the Storage Pool Installation Guide. On the PDOS installer’s main menu. Attach clients and start backing up files.18 Installation overview Performing a PureDisk initial installation Figure 1-1 Storage pool installation steps Install PDOS on each node. and use the wizard to configure the PureDisk application.

The PDOS main menu displays several installation options. If you need more information. This method uses the PDOS installer.6 software DVD. and other tasks. Symantec recommends that you use the Install PDOS installation method. use one of the following two methods: ■ The Install method. ■ The PureDisk software installation process assumes knowledge of Linux system installation procedures. This method uses the SUSE Linux YaST installation tool.novell.com/documentation/sles10 The following provides more information about the initial installation process: ■ ■ See “Types of storage pools” on page 20. Please read through the instructions in the following manuals before you begin an installation: ■ ■ The PureDisk Getting Started Guide This manual. For more information about how to configure the storage pool. These other tasks can prepare the node for clustering. specifying clustering options. see the following: See “About installing PDOS manually” on page 39. including how to specify network configurations and how to partition disks. the PureDisk Storage Pool Installation Guide. Run the storage pool configuration wizard to configure PureDisk on the PDOS nodes. storage configuration. For production purposes. Make sure to review the following before you start the storage pool configuration wizard: See “About preparing to configure the storage pool” on page 55.Installation overview Performing a PureDisk initial installation 19 ■ Install PDOS from the PureDisk 6. can prepare the nodes to use iSCSI disks in the storage pool. and so on. For more information about how to install PDOS. see the following: See “Starting the storage pool configuration wizard” on page 89. . You might need to perform other tasks on the nodes after you install PDOS but before you run the storage pool configuration wizard. network information. see the SUSE Linux Enterprise Server 10 SP2 documentation on the following Novell documentation Web site: www. The Expert method. The installer prompts you for node addresses. The configuration wizard guides you through licensing. ■ ■ Perform additional tasks on the nodes to prepare them for the storage pool configuration wizard. and so on. See “Configuring an environment for specific features” on page 23.

The storage pool configuration wizard installs the PureDisk application on each node. a passive node receives services from a failing node. A clustered storage pool is a highly available multinode storage pool. Figure 1-2 shows an unclustered two-node storage pool example and shows the services that reside on both nodes. first install PDOS on the one node. the storage pool configuration wizard does not display the clustering pages to you during your configuration session. . The Veritas Cluster Server (VCS) software ensures that the cluster can failover. To configure a multinode storage pool. however. single-node storage pool. you run the storage pool installation wizard from the node you want to use for the storage pool authority. Later. A multinode. The installation process puts all PureDisk services on the single node.20 Installation overview Performing a PureDisk initial installation Types of storage pools PureDisk storage pools can be of any of the following types: ■ An all-in-one. A clustered storage pool. so no clustering software is included in the installation. The storage pool configuration wizard prompts you to designate some nodes as active nodes and to designate other nodes as passive nodes. You cannot. first install PDOS on each node. During a failover. You can add additional nodes to any kind of storage pool if your processing needs change. To configure an all-in-one storage pool. The PureDisk storage pool configuration wizard installs the VCS software for you automatically during the wizard session. the nodes cannot failover in case of a disaster. transform an unclustered storage pool into a clustered storage pool. These nodes are as follows: ■ ■ ■ ■ An active node hosts PDOS and other PureDisk services. Clustering must be enabled when you create the storage pool. This kind of a storage pool is not highly available. When you configure this kind of storage pool. you configure the PureDisk application to run on the node. The failover feature guarantees that the storage pool is always up and running. Later. You need at least one passive node in a highly available storage pool. In an unclustered storage pool. unclustered storage pool. A passive node hosts PDOS but no other services.

.Installation overview Performing a PureDisk initial installation 21 Figure 1-2 An unclustered two-node storage pool Node 1: Storage pool authority Metabase server Node 2: Content router Metabase engine NetBackup Export Engine Figure 1-3 shows a clustered three-node storage pool and shows the services that reside on the nodes.

Two others form the private heartbeat monitor. Node 3: Passive node .22 Installation overview Performing a PureDisk initial installation Figure 1-3 A clustered three-node storage pool Node 1: Storage pool authority Metabase server Metabase engine Content router Three network connections per node: Node 2: Content router Metabase engine NetBackup export engine One connects the cluster to the public network.

High availability. Other features are easier to implement at storage pool creation time. configure that storage pool to be highly available when you install the product initially. and Tomcat software are among the third-party components that PureDisk includes in its architecture. you use the storage pool configuration wizard to configure the services on the nodes into service groups. If you want to implement the following features. do not upgrade third-party components to a newer version. see the following: See “About single port communication” on page 199. Single-port communication. When you implement high availability in a storage pool. If you need a highly available storage pool. For more information about this feature. Java. High availability must be configured when you create the storage pool. also referred to as all through one port. ■ ■ Performing a PureDisk upgrade If you want to upgrade an existing PureDisk environment to PureDisk 6.6. Symantec also provides you with upgrades or patches . This feature includes the NetBackup export engine and the NetBackup disaster recovery methods. Apache. Symantec monitors the releases of these third-party products.6” on page 119. The second node hosts an extra content router. and a NetBackup export engine. The services in the group can automatically failover from one node to the other. perform the following upgrade instructions: See “About upgrading to PureDisk 6. If you want to implement high availability. PHP. Configuring an environment for specific features The PureDisk interfaces provide flexibility in terms of how you configure a storage pool. the first node is an all-in-one system. PostgreSQL. configure your storage pool for these features at installation time: ■ NetBackup interoperation. PureDisk requires that you attach all PureDisk nodes to external disks. Symantec does not support the ability to install a PureDisk storage pool and then reconfigure that storage pool for high availability. an extra metabase engine. As an administrator.Installation overview Performing a PureDisk upgrade 23 In Figure 1-3. The third node is a passive node. Third-party components PureDisk uses third-party components as a part of its architecture.

performance. and stability problems that can affect PureDisk functions. .24 Installation overview Third-party components to address the vulnerabilities.

Chapter 2 Installing the PureDisk operating system This chapter includes the following topics: ■ ■ ■ About PureDisk operating system (PDOS) installations Preparing to install PDOS (Optional) Choosing an installation method and cleaning a node that hosted PDOS previously Choosing an installation method ■ About PureDisk operating system (PDOS) installations Install the PDOS software on every computer that you plan to use as a PureDisk node. When the installation procedure instructs you to create the /Storage partition. first install PDOS on all the computers that you want to use in the storage pool. You can configure one computer to host a content router and another computer to host all the other services. . If you have several computers. you can deploy PureDisk as follows: ■ If you have two computers. Make sure that you reserve /Storage for PureDisk’s exclusive use. Do not write data to this partition. including the passive nodes. To configure the cluster. Linux is case sensitive. Remember to install PDOS on both computers before you install any services. Later in the installation process. make sure to type an uppercase S. For example. you can create a clustered storage pool. you can distribute the PureDisk services over the two computers. you install the clustering software. PureDisk expects this partition to be named with an uppercase S. ■ The PDOS installation procedure assumes knowledge of Linux disk partitioning.

. 4 Gather installation information. You can enable write caching on your external RAID. make sure that the information in the cache memory cannot be lost due to a power interruption. you can configure static addressing for a node during the PDOS installation. The following list shows the information that the PDOS installer prompts you to supply: ■ The password for the root user on this computer. ■ Preparing to install PDOS The following procedure explains how to prepare a computer for a PDOS installation. To use a hardware RAID. Unplug all other network cards that are cabled to your network. Symantec recommends that you use RAID technology. Make sure that you are familiar with the information about write caching in the PureDisk Getting Started Guide. See “Choosing an installation method” on page 29. 3 Make sure that only the active network card for this server node is connected to the network.26 Installing the PureDisk operating system Preparing to install PDOS The following contain information about PDOS installations: ■ ■ See “Preparing to install PDOS” on page 26. If you enable write caching. Perform this step if you want the node to use DHCP addressing. A power interruption can lead to data loss. Your alternative is a software RAID. To prepare a computer for a PDOS installation 1 (Optional) Configure a hardware RAID controller for the disks that are attached to the node. Alternatively. 2 (Conditional) Configure a static address on the DHCP server. configure it now. You reconnect the network cards before you run the storage pool configuration wizard. and it requires you to create additional information during the installation process. The PDOS installer prompts you for network information. This password cannot contain the pipe character (|) or the equal sign character (=). See “(Optional) Choosing an installation method and cleaning a node that hosted PDOS previously” on page 28.

Clustered storage pools are multinode storage pools. Symantec requires that you configure the storage pool authority node first. . The storage pool authority node's FQDN. During the PDOS installation process. The IP address for this computer. the installer prompts you to specify a password for the storage pool authority installer.Installing the PureDisk operating system Preparing to install PDOS 27 ■ ■ ■ ■ The FQDN for this computer. you use this password to log into the storage pool authority installer. The IP address of your site's primary and (optionally) secondary DNS servers. The root password for the computer that you want to designate as the storage pool authority node. ■ ■ ■ ■ 5 Insert the PureDisk software disk into a drive that is capable of reading a DVD. If you want to configure a multinode or clustered storage pool. Make sure that this node is the node you want to use for this storage pool's storage pool authority. For a multinode storage pool. This action registers the node with the storage pool authority. The netmask for this computer. The SPA Installer Password. Later. Symantec requires that you install PDOS first on the computer that you want to use for the storage pool authority node. The primary and (optionally) secondary search domains for each computer. the installer prompts for the storage pool authority node's FQDN when you install PDOS on the non-storage pool authority nodes.

(Optional) Choosing an installation method and cleaning a node that hosted PDOS previously Perform this procedure if the following are true: ■ ■ PDOS has been installed on this node previously. See “(Optional) Choosing an installation method and cleaning a node that hosted PDOS previously” on page 28. type the following command: # dd if=/dev/zero of=/dev/<disk> bs=1 count=100 4 Repeat the following step for every disk that is attached to this node: ■ Step 3 . At the system prompt. You want to perform an Install installation or a Onedisk installation. Circumstance If you want to install PDOS on a computer that has hosted PDOS previously. If you want to install PDOS on a computer that has never hosted PDOS. see the following: See “Choosing an installation method” on page 29. To clean a node before you perform an Install installation or a Onedisk installation 1 2 3 Use the arrow keys to select Install or Onedisk and press Enter. See “Choosing an installation method” on page 29.. Type the following command: # reboot 7 Proceed to one of the following topics: Proceed to .28 Installing the PureDisk operating system (Optional) Choosing an installation method and cleaning a node that hosted PDOS previously 6 Boot the computer. For information about these installation methods.. When the Enter PureDisk OS Root Password pop-up window appears. press Ctrl+Alt+F2.

Installing the PureDisk operating system Choosing an installation method 29 5 6 Press Ctrl+Alt+F7. Select this option if you performed an installation. These steps include loading the PDOS software from the CD-ROM drive. and completing the configuration process. Select this option to install PDOS on one internal disk. but you did not remove the PureDisk software disk from the drive. Select this option if the server has several disks in an external storage cabinet. The Onedisk method configures the internal disk automatically. ■ ■ ■ ■ During installation. Select the Expert option only if the Install option failed. The Onedisk option configures the storage partition automatically. Select this option if you have PDOS installed on this node and you need to upgrade PDOS. Use the Onedisk option when the computer has no external storage. Expert. OS_Upgrade. The Onedisk option is suited to computers that have an internal RAID system configured into one internal disk. Proceed to the following: See “Completing the Preparing the System for Automated Installation page” on page 32. You configure the storage partition during the storage pool installation process. Onedisk. rebooting from the hard disk. including the storage partition. Symantec recommends the Install option for general production use. This method uses the YaST interface and is not menu-driven. Choosing an installation method The following procedure explains how to choose an installation method and begin the installation. customize the PDOS installation. The following table shows the default Onedisk partitioning scheme: . of any type. Select this option if the server has any number of disks. You can use the Onedisk option for unclustered demonstration storage pools. Install. the system goes through several installation steps. The Expert option requires you to install PDOS. To choose an installation method 1 Use the arrow keys and press Enter to choose one of the following PDOS installation methods: ■ Boot from Hard Disk. and run additional scripts. Select the Expert option only if the Install option does not work.

you use the storage pool configuration wizard to configure /Storage on the external disks.30 Installing the PureDisk operating system Choosing an installation method Mount point /boot / swap /Storage Size 100 MB 10 GB 12 GB rest File system EXT3 EXT3 swap VxFS The Install method partitions the /boot. /. the PureDisk installer automatically installs the Veritas Volume Manager (VxVM) software. Circumstance See “About the PDOS installation wizard” If you selected the Onedisk or Install on page 31. If you selected the Expert option. . The following table shows the default Install partitioning scheme: Mount point /boot / swap Size 100 MB 10 GB 12 GB File system EXT3 EXT3 swap In the preceding tables. and swap partitions automatically on the internal disk.. By default. After you complete the PureDisk installation. Symantec recommends that you do not decrease these sizes manually. option.. the partition sizes for the Onedisk and Install options are minimum sizes. you can use VxVM commands to manage the disk volumes. 2 Proceed to one of the following: Proceed to . See “About installing PDOS manually” on page 39. Later. Do not attempt to install VxVM separately.

See “Completing the Symantec EULA page” on page 36. When you select either Onedisk or Install from the PDOS main menu. See “Completing the PureDisk Node Configuration page” on page 34. See “Completing the Installation Settings page” on page 36. the PDOS installer starts the installation wizard.Chapter 3 Installing PDOS with the installation wizard This chapter includes the following topics: ■ ■ ■ ■ ■ ■ About the PDOS installation wizard Completing the Preparing the System for Automated Installation page Completing the Network Configuration page Completing the PureDisk Node Configuration page Completing the Symantec EULA page Completing the Installation Settings page About the PDOS installation wizard The following procedures describe how to use the PDOS installation wizard. See “Completing the Network Configuration page” on page 32. The following procedures explain how to use the PDOS installation wizard: ■ See “Completing the Preparing the System for Automated Installation page” on page 32. ■ ■ ■ ■ .

To complete the Preparing the System for Automated Installation page 1 On the Enter PureDisk OS Root Password pop-up window. If you want to install a clustered storage pool. Completing the Preparing the System for Automated Installation page The following procedure explains how to complete the Preparing System for Automated Installation page. A later step prompts you to specify a password for the PureDisk application itself. . The password can contain any number of characters. a DNS is required. but it cannot contain the pipe (|) character or the equal sign (=) character. 2 Click OK. Completing the Network Configuration page The following procedure explains how to complete the Network Configuration page. specify the password you want to use for the root user on this PDOS node.32 Installing PDOS with the installation wizard Completing the Preparing the System for Automated Installation page Note: Symantec recommends that each PureDisk node use a Domain Name Server (DNS) at your site. The password you need to provide here is the operating system's root password. Type the password in both password fields.

Perform this step if you did not check Use DHCP?. 3 (Conditional) Type the node's IP address into the IP Address field. PureDisk supports DHCP servers that are configured with static addressing. Additional configuration steps are required. configure this node with static addressing in the DHCP server.conf file.Installing PDOS with the installation wizard Completing the Network Configuration page 33 To complete the Network Configuration page 1 Type this node's Fully Qualified Domain Name (FQDN) into the Fully Qualified Domain Name (FQDN) field. 2 (Conditional) Check Use DHCP?. Additional configuration steps are required. type a temporary FQDN into this field. This temporary FQDN is used only for the purpose of this wizard session and is replaced later by an actual FQDN. 5 (Conditional) Type the IP address of your site's primary DNS server into the DNS Server 1 field. If you have a DHCP server. however. however. . /etc/resolv. 6 (Optional) Type the IP address of your site's secondary DNS server into the DNS Server 2 field.conf file. Make sure to perform the following procedure after your PDOS installation is complete: See “(Conditional) Editing the /etc/hosts files. Make sure to perform the following procedure after your PDOS installation is complete: See “(Conditional) Editing the /etc/hosts files. Perform this step if you did not check Use DHCP?. 4 (Conditional) Type the node's netmask into the Netmask field. Symantec recommends that you configure PureDisk with FQDNs. and client networking files” on page 64. Perform this step if you did not check Use DHCP?. If your site uses domain name service but you did not secure a valid DNS name for this node. If your site uses domain name service but you did not secure a valid DNS server name for this node with your site's network administrator. Check the Use DHCP box if this node uses a DHCP server that you configured with static addressing. and client networking files” on page 64. /etc/resolv. you can still configure this node with domain name service.

■ .34 Installing PDOS with the installation wizard Completing the PureDisk Node Configuration page 7 (Conditional) Type the primary search domain for this node into the Search Domain 1 field. type a temporary search domain into this field. Symantec requires that you configure the storage pool authority node first. See “To complete the PureDisk Node Configuration page for a node that is not the storage pool authority node ” on page 35. Perform this step if you did not check Use DHCP? If you do not have a DNS. If you want to configure a multinode storage pool or a clustered storage pool. 10 Verify that only this node's active network card is connected to the network Completing the PureDisk Node Configuration page The following procedure explains how to complete the PureDisk Node Configuration page. This temporary search domain is used only for the purpose of this wizard session and is replaced later by an actual search domain. The PureDisk Node Configuration page requires you to declare the storage pool authority node. however. Use one of the following procedures to complete the PureDisk Node Configuration page: ■ See “To complete the PureDisk Node Configuration page for the storage pool authority node” on page 35. Check this box only once during the entire process of configuring multiple nodes for a multinode storage pool or a clustered storage pool. 8 9 (Optional) Type the secondary search domain for this node into the Search Domain 2 field. Make sure to perform the following procedure after your PDOS installation is complete: See “(Conditional) Editing the /etc/hosts files. and client networking files” on page 64. Note: There can be only one storage pool authority node in a storage pool. and click OK on the verification pop-up window.conf file. Check this box only when you install PDOS on the storage pool authority node. /etc/resolv. Additional configuration steps are required. Click Next. There can be only one storage pool authority node in a storage pool.

you can specify the FQDN during the storage pool configuration process. Check this box only when you install PDOS on the storage pool authority node. but it cannot contain the pipe (|) character or the equal sign (=) character. PureDisk uses this password as follows: ■ You need to specify this password to log into the storage pool configuration wizard. If you want to configure a multinode storage pool or a clustered storage pool. If you do not specify the storage pool authority's FQDN at this time. You cannot type a host name or an IP address into this field. Note: There can be only one storage pool authority node in a storage pool. 3 4 Type the password of the root user for the storage pool authority node into the SPA root Password field. The password can contain any number of characters. (Optional) Type the FQDN of the storage pool authority node into the SPA Fully Qualified Domain Name field. Click Next.Installing PDOS with the installation wizard Completing the PureDisk Node Configuration page 35 To complete the PureDisk Node Configuration page for the storage pool authority node 1 Check the box on this page to declare this node as the storage pool authority node. To complete the PureDisk Node Configuration page for a node that is not the storage pool authority node 1 2 Do not check the box that declares this node as a storage pool authority node. Symantec requires that you configure the storage pool authority node first. Remember this password or record it in a safe place. Symantec recommends that you specify the storage pool authority's FQDN at this time. . Check this box only once during the entire process of configuring multiple nodes for a multinode storage pool or clustered storage pool. The storage pool configuration wizard uses this password to encrypt the storage pool topology file. 2 Type a password into the SPA Installer Password field. This action registers the node to the storage pool authority. ■ 3 Click Next.

Click Accept. I agree to the End User License Agreement. If you need to change the Software setting to compile custom. In some cases. perform the following steps: ■ ■ ■ ■ Click Software. the installer writes messages to your display. click C/C++ Compiler and Tools. Click Accept. Note: DO NOT attempt to log on at the manual1 login: prompt. 3 4 On the Confirm Installation pop-up window. ■ ■ If the setting are correct. third-party. The final installation messages can differ. click Install. The differences depend on whether you installed PDOS on the storage pool authority node and on whether the installer issued any errors during installation. Wait for the final installation messages. click Accept and proceed to step 3. The node reboots itself twice and performs initialization steps. Symantec recommends that you accept the settings on this page. Decide whether the settings are correct. To complete the Symantec EULA page 1 2 Click Yes. This prompt is part of the system initialization. Under Development.36 Installing PDOS with the installation wizard Completing the Symantec EULA page Completing the Symantec EULA page The following procedure explains how to complete the Symantec EULA page. Click Next. This step describes the final installation messages that the installer issues. To complete the Installation Settings page 1 2 Review the settings on this page. Completing the Installation Settings page The following procedure explains how to complete the Installation Settings page. or vendor-supplied kernel modules. you might need to change the Software setting as described in the following procedure. The messages . Wait for the PDOS installation to complete. If any errors occurred during installation.

* To create a clustered or multinode storage pool: * Record the storage pool installer’s URL for later use. * If this is the last node in the storage pool and you want to enable high availability: * Insert the PureDisk software disk into the SPA node.6. go to http://ip_addr/Installer now. * Install PDOS on the additional nodes at this time. spa_node login: ■ On a node that is not the storage pool authority node. * To create a storage pool all on one node.6. message. go to http://ip_addr/Installer. the final messages are similar to the following: Welcome to PDOS 6. node login: .x! To configure the storage pool. the final messages are similar to the following: Welcome to PDOS 6.Installing PDOS with the installation wizard Completing the Installation Settings page 37 appear before the final Welcome . ■ On the storage pool authority node..x. * Type the storage pool installer's URL into your browser now.x..x! Install PDOS on all nodes before you configure the storage pool. * If this is the last node in the storage pool and you do not want to enable high availability * Type the storage pool installer's URL into your browser now. For troubleshooting information see the following: See “About troubleshooting PureDisk installations” on page 183.

include in an all-in-one the storage pool. unclustered storage pool.. troubleshoot the problem. Follow your vendor's instructions. 6 Proceed to one of the following: Proceed to . .38 Installing PDOS with the installation wizard Completing the Installation Settings page 5 Install custom. Perform this procedure on all computers in all multinode storage pools. or vendor-supplied kernel modules. third-party. If you need to install PDOS on more nodes. If the installation failed. whether they are clustered or unclustered. See “About PureDisk operating system (PDOS) installations” on page 25. You need to install PDOS on all nodes before you install the clustering software or the storage pool software. Circumstance See “About configuring the storage pool” If this node is the only node you want to on page 85.. See “About troubleshooting PureDisk installations” on page 183. OR If this node is the last node upon which you need to install PDOS for a multinode.

networking. and / partitions Specifying the host name. After you select the Expert option. See the SUSE Linux Enterprise Server 10 SP 2 documentation at the following Web site: www. the system presents you with the YaST interface.com/documentation/sles10 The following describe how to install PDOS manually: ■ See “File system configuration” on page 40. You can use the YaST interface to configure partitioning. swap. network addressing.novell. the list of users.Chapter 4 Installing PDOS manually This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ About installing PDOS manually Initiating a manual PDOS installation Configuring the /boot. and miscellaneous settings Configuring addressing Completing an Expert installation Verifying the installation About installing PDOS manually The Expert installation option requires you to specify all the configuration settings for the server yourself. . The Expert installation method uses the SUSE YaST interface. see one of the following sources: ■ ■ See “About the YaST2 interface” on page 141. and other specifications. For more information about this interface.

40 Installing PDOS manually About installing PDOS manually ■ See “Manual installation process overview” on page 40. VxVM requires two separate. The system issues messages about VxVM and VxFS daemons and drivers. See “Specifying the host name. 5 Complete the installation.sh. To perform a manual PDOS installation 1 Initiate the installation. The post-installation script enables VxVM and VxFS operations. Depending on the equipment you have. and / partitions” on page 42. and / partitions. 3 Specify the host name. 2 Configure the /boot. . File system configuration Do not try to configure VxVM or VxFS during an Expert installation. the following occurs: ■ ■ The final reboot fails. 4 Configure addressing. See “Initiating a manual PDOS installation” on page 41. Manual installation process overview Because each installation is different. some steps in the installation procedure are written in general terms. swap. See “Configuring addressing” on page 46. The following procedure explains how to perform an Expert installation. The disk partitions that this manual describes are recommended layouts. Toward the end of the installation process. 6 Verify the installation. pdos-postinstall. swap. you might have to alter the disk layout prescribed here. networking. physical disk devices. See “Completing an Expert installation” on page 50. the installation instructions direct you to run a post-installation script. and miscellaneous settings. If you attempt to configure VxVM or VxFS during the installation. See “Configuring the /boot. networking. and miscellaneous settings” on page 44. You might need to specify additional settings in YaST to satisfy your site practices. See “Verifying the installation” on page 53.

accept the license agreement and select Next. Click Partitioning 8 9 On the Suggested Partitioning Screen. Through YasT. Use YaST to configure all aspects of the PureDisk node. assume that a menu item appears as follows: Change To select this item. and / partitions” on page 42. ■ 2 3 4 5 On the Language page. type Alt-c. perform the following steps: ■ ■ Inspect the display to make sure that your selections are recorded. swap. On the Installation Mode page. On the second License Agreement page. specify English(US) and select Next.Installing PDOS manually Initiating a manual PDOS installation 41 Initiating a manual PDOS installation The following procedure explains how to initiate a manual PDOS installation. Most of the pages require that you select Next or type Alt-n to proceed to the next page. select New Installation and select Next. press Alt plus the underlined letter or the selected letter in the item’s name. select Custom Partitioning (for 11 Proceed to the following: See “Configuring the /boot. and the other aspects of the node. . For example. After you select Expert. the YaST2 interface appears. select Create Custom Partition Setup and select Next. 10 On the Preparing Hard Disk: Step 1 page. accept the license agreement and select Next. experts) and select Next. Do not select Include Add-on Products. Click OK on the warning message that pops up. On the first License Agreement page. The following are some navigation notes for the YaST2 interface: ■ To select a menu item on the YaST2 interface. you configure the partitioning. the network addressing. 6 7 On the Clock and Time Zone page. On the Installation Settings page. click Next. To initiate a manual PDOS installation 1 Use arrow keys to select Expert on the PDOS menu and press Enter. the list of users.

swap. The following table shows the disk partitions you need to create for the /boot. The following procedure explains how to configure the /boot. About the /boot. See “Configuring the /boot. ■ Complete the following steps: . File system Configure as EXT3. If you choose other file systems. swap. and /: ■ ■ See “About the /boot. and / partitions The following explains how to create the disk partitions for /boot. and / partitions” on page 42. and / partitions. swap. Configure as 10 GB or more. swap. swap. and / 1 (Conditional) Delete existing partitions. you can configure this partition so that / uses the remaining free space on the boot disk. swap.42 Installing PDOS manually Configuring the /boot. Configure as 12 GB. Perform this step under the following conditions: ■ You need to re-use a disk that is currently configured into disk partitions for another application. swap. delete the existing disk partitions. For Configure as EXT3. if you reinstall PDOS on a node. and / partitions The Expert installation method does not automatically configure any disk partitions. and / Size Configure as 100 MB. Configuring the /boot. swap. example. Configure as swap. and / partitions. swap. and / partitions Symantec recommends that you specify an EXT3 or swap file system as shown in the following procedure. and / partitions Configuring the /boot. swap. performance degrades and maintenance is more difficult. Table 4-1 Mount point /boot swap / Disk partition layouts for /boot. To create partitions for /boot. and / partitions” on page 42. PDOS has ever been installed on this node before. In other words. swap.

■ ■ ■ ■ ■ 5 Complete the following steps to create a partition for /: ■ Click Create. in the Format pane. select the disk. In the Mount Point field. On the Really delete all partitions on disk_name? pop up. type +100MB to create a 100-MB partition for /boot. select Ext3. type +12GB to create a 12-GB partition for swap. select Primary. in the Format pane. select /boot from the drop-down list. On the Create a Primary Partition on disk_name page. (Conditional) On the Disk to Partition pop-up. in the Format field. select Swap. 2 3 On the Expert Partitioner page. and / partitions 43 ■ ■ ■ On the Expert Partitioner page. YaST presents this option to you only if you can select from multiple disks. In the Size pane. in the End box. Click OK. select the disk upon which you want to create the partition and click OK. select Primary. . On the Create a Primary Partition on disk_name page.Installing PDOS manually Configuring the /boot. Make sure to select each disk that is attached to this node. in the Format field. Click Delete. swap. select the disk upon which you want to create the partition and click OK. Click OK. and delete the partitions for each disk. On the Partition Type pop-up. Click OK. click Create. On the Partition Type pop-up. YaST presents this option to you only if you can select from multiple disks. click Yes. ■ ■ ■ ■ ■ ■ 4 Complete the following steps to create a partition for swap: ■ ■ Click Create. In the Size pane. Click OK. Complete the following steps to create a partition for /boot: ■ (Conditional) On the Disk to Partition pop-up. in the End box.

select the disk upon which you want to create the partition and click OK. networking. This action allocates the rest of this disk for storage. accept the default size. Click OK. type the size for this partition. Specifying the host name. and miscellaneous settings” on page 44. The system copies the files from the DVD and formats the disks. networking. Type the domain name. On the Installation Settings page. type +10GB.44 Installing PDOS manually Specifying the host name. and networking information. On the Confirm Installation pop-up window. If you plan to create the storage partitions on a separate disk. and miscellaneous settings ■ (Conditional) On the Disk to Partition pop-up. 10 Proceed to the following: See “Specifying the host name. and miscellaneous settings 1 On the Hostname and Domain name page. To specify the host name. select Ext3. networking. If you need to put the storage partitions on this disk. On the Partition Type pop-up. select Primary. select this line and press the space bar. ■ ■ ■ ■ ■ 6 7 8 Click Finish. 9 Allow the system to boot automatically from the hard disk. On the Create a Primary Partition on disk_name page. too. Click OK. in the Format pane. perform the following steps: ■ ■ ■ Type a unique host name. password. This activity can take a few minutes. The system boots and presents you with the YaST interface. . and miscellaneous settings The following procedure explains how to specify the host name. In the Size pane. YaST presents this option to you only if you can select from multiple disks. in the Format field. Deselect Change Hostname via DHCP. in the End box. examine the settings and select Accept. select Install. To perform this step. networking.

retype the password to confirm. tab to No to skip the test and select Next. however. and select Next. decide whether or not to read the release notes and select Next. or Windows Domain. for the following reasons: ■ The installer needs to be able to push the software to the nodes during the installation. Select Next (again). select Skip Configuration and select Next. The guidelines for this password are as follows: ■ ■ ■ ■ ■ Eight characters or more in length At least one uppercase character At least one numerical character At least one nonalphabetic numerical character Not based on a word in an English dictionary 3 On the Network Configuration page. 4 5 6 On the Test Internet Connection page. select Yes. This step disables the firewall. networking. Select Start-Up and Service Start. PureDisk creates its own firewall. 7 8 On the New Local User page. ■ ■ ■ Select Next. Do not choose NIS. In the Empty User Login pop-up that appears. On the Installation Settings page. type the password for the root user. select Local and select Next. select Next. 9 At the Release Notes page. Select Firewall and press Enter. LDAP. Set Service Start to Manually. This action leaves an empty user name. On the User Authentication Method page. 2 On the Password for System Administrator "root" page. . specify the following: ■ ■ ■ ■ Select Change. and miscellaneous settings 45 ■ Select Next. You need to disable the firewall during installation.Installing PDOS manually Specifying the host name. After the installation is complete. You need to enable a secure shell (SSH) connection to each node.

Configuring addressing This procedure explains how to configure static addressing on the only. Note: Because of a PDOS limitation. In this later procedure. 11 At the Installation Completed page. NIC in this node. 13 Wait while the system completes the installation. When you use static addressing. If your DHCP server is configured to use DHCP reservations. If the system seems to hang after it displays Skipped services at runlevel 3. 15 Proceed to the following: See “Configuring addressing” on page 46. select Skip Configuration. 14 At the login: prompt. PureDisk does not support dynamic addressing. If you intend to configure this node in a cluster. you configure the two NICs for the private heartbeat without addressing later. deselect Clone this System for Autoyast at the bottom of your page. PureDisk supports Dynamic Host Configuration Protocol (DHCP) only if resolves to a static address. use this procedure to verify your configuration settings. . make sure that you have set appropriate static addresses for the node's primary NIC in your DHCP server. you configure no addressing on the two NICs for the cluster’s private heartbeat and on all unused NICs. 12 Select Finish. The following explain how to configure addressing: ■ See “Gathering NIC information” on page 47. log in as root. If you use a DHCP server. or primary. press Enter to display the login: prompt. If the Update Name Servers and search list via DHCP option is grayed out while it is selected. and select Next.46 Installing PDOS manually Configuring addressing 10 (Optional) If the Hardware Configuration page appears. The procedures in this topic guide you through the configuration process in a way that avoids this problem. You can start YaST at a later date to add peripherals. the Update Name Servers and search list via DHCP option is grayed out in the Hostname and Name Server Configuration page. you cannot combine static addressing with DHCP. you cannot disable it.

The domain for this network. ________________________________________ ________________________________________ ________________________________________ ________________________________________ The IP address of the DNS server or name ________________________________________ server. The subnet mask. ________________________________________ ________________________________________ Note: You need to specify an FQDN or a host name in several places. You cannot include an underscore character (_) in these fields. The IP address of the default gateway. . The domain name for this computer on network. The public host name of the NIC.xls. Information needed The MAC address. To include this node in a clustered storage pool. make sure that you gathered this information and recorded it on the planning spreadsheet. To include this node in an unclustered storage pool.Installing PDOS manually Configuring addressing 47 ■ See “Configuring static addressing” on page 48. but it is useful to have if you have more than one NIC in this node. The public IP address of the NIC. contact your network administrator for the information in the following table. NIC data ________________________________________ Note: You do not need to enter this information. PureDisk_ClusterPlanning. Gathering NIC information The following procedure explains how to gather the information you need to configure static addressing on this node. To gather NIC information 1 Record information about the primary NIC in this computer. Use the ip(8) command to retrieve this information.

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. .UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.92.102/21 brd 10.0.0.0 2 Proceed to the following: See “Configuring static addressing” on page 48.0.MULTICAST. Configuring static addressing The following procedures explain how to launch YaST and how to configure static addressing for the primary NIC in this node.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.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST. To configure this node for a clustered storage pool.80.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.BROADCAST.0.255 scope global eth0 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 valid_lft forever preferred_lft forever 3: eth1: <NO-CARRIER.0 brd 0.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. do not configure any addressing on the private heartbeat NICs at this time.0.80.95. The following is example ip(8) command output: # ip a 1: lo: <LOOPBACK.48 Installing PDOS manually Configuring addressing You can obtain some of the information you need from the ip(8) command and its a option.0. Note: The procedures in this topic assume that your network is not configured to use DCHP for host names and name servers.

Press Tab to position the cursor at the Domain Name field. select Modify. and FQDNs. Press Tab to position the cursor at Change Hostname via DHCP. (Conditional) On the pop-up that appears. type a unique host name. and press Enter. but each node must have a unique host name. Perform this step if the pop-up appears. and press Enter to deselect it. the service addresses. leave this field blank. select Network Devices > Network Card and press Enter. perform the following steps: ■ In the Hostname field. 6 On the Hostname and Name Server Configuration page. you need to perform some extra configuration steps after you install PDOS. Press Tab to position the cursor at Name Server 1. In this case. the Device Name field identifies each NIC by its MAC address. select the NIC upon which you want to configure the host address. select the primary NIC and select Edit. and type the IP address of the DNS server or the name server. 4 5 Tab to Hostname and Name Server and press Enter. To configure static addressing 1 2 3 In the YaST Control Center main page. Make sure to perform the following procedure after your PDOS installation is complete: ■ ■ ■ .Installing PDOS manually Configuring addressing 49 To launch YaST ◆ Type the following command to launch the SUSE Linux YaST configuration tool: # yast You can type yast or YaST to start the interface. Do not type other combinations of uppercase and lowercase letters. and type the domain name for this network. select Traditional Method with ifup and select Next. The default PDOS host name is PureDisk. On the Network Card Configuration Overview page. In the bottom pane. On the Network Setup Method page. To include this node in a cluster. If you do not have a DNS.

12 On the Network Address Setup page. select Next. and type the IP address that you want to assign to the node’s primary NIC. ■ (Optional) Type additional IP addresses for the Name Server 2 field and the Name Server 3 field. 14 Select Quit. specify the IP address of the default gateway and select OK. 15 Proceed to the following: See “Completing an Expert installation” on page 50. Tab to the Subnet Mask. and press Enter to deselect it. Tab to OK and press Enter.50 Installing PDOS manually Completing an Expert installation See “(Conditional) Editing the /etc/hosts files. 10 On the Network Address Setup page. 13 Select Finish. as necessary.conf file. Completing an Expert installation The following procedure explains how to complete an Expert installation. 11 On the Routing Configuration page. and client networking files” on page 64. Press the Tab key until you select the IP Address field. ■ ■ 7 8 9 On the Network Address Setup page. select Routing and press Enter. /etc/resolv. Do not use Classless Interdomain Routing (CIDR) notation. Press Tab to position the cursor at Update Name Servers and search list via DHCP. . select Static Address Setup. and accept the default subnet mask or type your own subnet mask.

Enter the SPA's root password: Type the password of the root user on the storage pool authority node. The storage pool configuration wizard prompts you for this password when you start the wizard. the installer writes messages to your display.sh If the system returns VxVM startup failure messages. The final installation messages differ. 2 Respond to the system prompts regarding this node's relationship to the storage pool authority. If you want to configure a multinode storage pool or a clustered storage pool. the prompt is as follows: Enter the SPA Installer Password: Specify the password that you want to use when you log into the storage pool configuration wizard. The differences depend on whether you installed PDOS on the storage pool authority node and on whether PureDisk issued any errors during installation. The messages . In response to the following prompt. This password can be of any length. the prompts are as follows: Enter the SPA's Fully Qualified Domain Name: Specify the FQDN of the storage pool authority node. but it must not include the pipe (|) or the equal sign (=) characters. If any errors occurred during installation. 4 Wait for the PDOS installation to complete. These prompts differ depending on whether you want to configure this node as the storage pool authority node: ■ If this node is the storage pool authority node. ■ If this node is not the storage pool authority node.Installing PDOS manually Completing an Expert installation 51 To complete an Expert installation 1 Type the following command to run the post-installation script: # /opt/PDOS/install/preparepdos. and press Enter: Is this server the PureDisk SPA? (y/n): 3 Respond to the prompts for information about the storage pool authority node. type y or n. Symantec requires that you configure the storage pool authority node first. disregard them.

For troubleshooting information see the following: See “About troubleshooting PureDisk installations” on page 183. * Install PDOS on the additional nodes at this time. * If this is the last node in the storage pool and you want to enable high availability: * Insert the PureDisk software disk into the SPA node. * Type the storage pool installer's URL into your browser now. * To create a clustered or multinode storage pool: * Record the storage pool installer’s URL for later use.x! To configure the storage pool.x.6. the final messages are similar to the following: Welcome to PDOS 6..x! Install PDOS on all nodes before you configure the storage pool. go to http://ip_addr/Installer now. * To create a storage pool all on one node. message.6. * If this is the last node in the storage pool and you do not want to enable high availability: * Type the storage pool installer's URL into your browser now. the final messages are similar to the following: Welcome to PDOS 6. go to http://ip_addr/Installer. spa_node login: ■ On a node that is not the storage pool authority node.x. ■ On the storage pool authority node.52 Installing PDOS manually Completing an Expert installation appear before the final Welcome . node login: ..

3 Type the following command to check the partitions: # df -hl Make sure that the output shows the following: ■ ■ ■ A rootfs file system A / partition A boot partition 4 Use the ping(1) command to verify the connection to another server on the network. a local host. or the node itself. Verifying the installation The following procedure explains how to verify the PDOS installation. third-party. or vendor-supplied kernel modules. contact your hardware or your software vendor for instructions. Note: You might need to add drivers to support hardware components that are not included by default in SUSE Linux Enterprise Server 10 SP2. To verify the installation 1 (Optional) Create other accounts on the server. as follows: ■ If this node is the first node you configured. ping one of the other storage pool nodes. 2 (Optional) Install custom. If you need to add drivers. Follow your vendor's instructions. ■ . Make sure that the drivers are SUSE Linux Enterprise Server 10 SP2 certified. If this node is at least the second node you configured. ping a gateway address. Use the YaST2 interface to add more users or change accounts according to your site practices.Installing PDOS manually Verifying the installation 53 5 Type the following command to reboot: # reboot 6 Proceed to the following topic: See “Verifying the installation” on page 53.

a network ping(1) between nodes must work perfectly. include in an all-in-one the storage pool. See “About troubleshooting PureDisk installations” on page 183. 6 Proceed to one of the following topics. That is. whether they are clustered or unclustered. the icmp echo should not be blocked and routers in between nodes should not rate limit ping(1). troubleshoot the problem. You need to install PDOS on all nodes before you install the clustering software or the storage pool software.54 Installing PDOS manually Verifying the installation For a PureDisk installation to work properly.. OR If this is the last node upon which you need to install PDOS for a multinode. perform the procedure in the following topic: See “Configuring static addressing” on page 48. Proceed to . depending on your situation. If the installation failed. start YaST2 again and check your network card settings. Circumstance See “About configuring the storage pool” If this node is the only node you want to on page 85. 5 Verify the DNS entries in YaST2. If the ping(1) command is unsuccessful. If the DNS entries are no longer present. Return to here after you reset the DNS entries. See “About PureDisk operating system (PDOS) installations” on page 25. unclustered storage pool. This information applies to all multinode storage pools.. . If you need to install PDOS on more nodes.

you might not need to complete all these procedures. and disabling multipathing Planning the storage partitions (DAS/SAN disks) (Conditional) Editing the /etc/hosts files.conf file. Depending on your environment and how you want to configure your storage pool. Review each of the following procedures. you might need to perform some manual procedures before you start the storage pool configuration wizard. downloading additional software. .Chapter 5 Preparing to configure the storage pool This chapter includes the following topics: ■ ■ ■ About preparing to configure the storage pool Gathering information for a storage pool Verifying hardware compatibility. however. /etc/resolv. downloading additional software. and complete the procedure if necessary: ■ ■ See “Gathering information for a storage pool” on page 56. and client networking files (Conditional) Preparing a remote root broker or an external root broker (Conditional) Preparing to configure a clustered PureDisk storage pool (Conditional) Configuring an iSCSI environment ■ ■ ■ ■ ■ About preparing to configure the storage pool Depending on your environment. See “Verifying hardware compatibility. and disabling multipathing” on page 58.

you need to gather some information and you need to make plans. The following list shows the fields for which you must supply information: ■ The SPA installer password. see the following: See “(Conditional) Preparing a remote root broker or an external root broker” on page 66. The FQDN of the site NTP server. If you prepare your installation now. Before you start the storage pool configuration wizard. Provide this information only if you decide not to configure a local root broker.conf file. The host (hardware) FQDN of each node that you want to configure in the storage pool. however. Symantec recommends an NTP server for production environments. you can make your session with the wizard more efficient. To gather storage pool information ◆ Collect the information you need to configure the storage pool. You specified this password during the PDOS installation. See “(Conditional) Configuring an iSCSI environment” on page 75. See “(Conditional) Editing the /etc/hosts files. For other information. the wizard presents installation options in a pull-down menu.56 Preparing to configure the storage pool Gathering information for a storage pool ■ ■ See “Planning the storage partitions (DAS/SAN disks)” on page 60. and client networking files” on page 64. /etc/resolv. The installation can complete without an NTP server specification. The storage pool name. ■ ■ ■ Gathering information for a storage pool The configuration wizard includes defaults for some information. (Conditional) Remote or external root broker information. ■ ■ ■ ■ ■ ■ . See “(Conditional) Preparing to configure a clustered PureDisk storage pool” on page 71. The license key(s) that you obtained from your Symantec sales representative. See “(Conditional) Preparing a remote root broker or an external root broker” on page 66. The FQDN of the site SMTP server. For more information.

This password is not the password that users need to provide when they log into the installed PureDisk storage pool.min. storage. (Conditional) Additional cluster information. ■ ■ The names of disk groups and disk volumes. and (conditionally) cluster information. You do not need this information for the passive nodes. Service FQDNs and the netmasks for each active node in the cluster. the service FQDN for this node could be acme2s.com. The storage pool configuration wizard prompts you for this password. including the following: ■ ■ ■ The cluster administrator's login name and password.com. The following has more information about planning disk groups. This password is the password that the administrator will use to log into the administrator Web UI after the storage pool is configured. ■ . The password can contain any number of characters. You can obtain this information from your network administrator. but it cannot contain the pipe (|) character or the equal sign (=) character. The storage pool configuration wizard discovers the disks attached to each node and displays the disks you can use to create disk groups and volumes.min. volumes. You need to supply disk group names and create volumes for the storage partitions. You specified these passwords during the PDOS installation in response to the Enter PureDisk root password prompt. To plan your storage pool ◆ Plan password. (Conditional) The cluster name. (Conditional) The administrator password for the Veritas Cluster Manager Java Console.Preparing to configure the storage pool Gathering information for a storage pool 57 ■ The root password for PDOS on each node that you want to configure in the storage pool. The following procedure shows the information that you need to plan before you start the storage pool configuration wizard. and mount points: See “Planning the storage partitions (DAS/SAN disks)” on page 60. The following list shows the fields for which you must create information: ■ The following passwords: ■ The storage pool authority password. which is a name you specify at installation time. if a node's hardware host FQDN is acme2. For example. The storage pool configuration wizard prompts you for this password only if you specified to configure a clustered storage pool.

■ Verifying hardware and (conditionally) downloading additional software The following procedure explains how to verify your hardware and.symantec. Determine whether your disks support DMP. . Take one of the following actions: ■ If your disk hardware appears on the hardware compatibility list. ■ 3 On the Veritas Storage Foundation hardware compatibility list. VxVM supports DMP by default for your hardware. an X appears in the VxVM column. If your disk hardware does not appear on the hardware compatibility list. To verify hardware compatibility 1 Display the Veritas Storage Foundation hardware compatibility list from the following Web site: ftp://exftpp. and disabling multipathing The following procedures how to analyze your hardware and prepare it to host the storage pool software: ■ See “Verifying hardware and (conditionally) downloading additional software” on page 58. and disabling multipathing Verifying hardware compatibility. download additional software.pdf 2 Look for your disk hardware in the Veritas Storage Foundation hardware compatibility list. downloading additional software. VxVM does not support dynamic multipathing (DMP) for your disks. See “(Conditional) Disabling multipathing” on page 59. DMP is a performance enhancement that enables more than one path from PDOS to the LUN or device. Proceed to the next step in this procedure. if needed.com/pub/support/products/VolumeManager_UNIX/277905. in the row for your disk hardware. Proceed to the following topic: See “(Conditional) Disabling multipathing” on page 59. as follows: ■ If an X appears in the DMP column for your hardware. Do not perform the rest of this procedure. Proceed to the following: See “(Conditional) Disabling multipathing” on page 59.58 Preparing to configure the storage pool Verifying hardware compatibility. look in the DMP column. downloading additional software.

and use the instructions on the download page to install the software. 5 Press Enter to return to the main menu. 4 Examine the information that YaST displays under the following heading: Devices excluded from multipathing by vxdmp: ■ If the following information appears. download additional array support library (ASLs) and/or additional advanced power management (APM) software. The following procedure explains how to disable multipathing and prevent conflicts with VxVM. Follow the download link on the Web page. To disable multipathing 1 2 Log into the node as root. and disabling multipathing 59 ■ If letters other than X appear in the DMP column. Proceed to the next step in this procedure. the system might have enabled multipathing by default. type 19 and press Enter. Perform this step only if the hardware compatibility list indicates that your disk hardware requires additional software. (Conditional) Disabling multipathing Perform the procedure in this topic if the hardware verification procedure revealed that VxVM does not support DMP for this node’s external disks. This action selects List currently suppressed/non-multipath devices.Preparing to configure the storage pool Verifying hardware compatibility. Depending on the disks that you attached to this node. do not complete this procedure: All devices have been excluded from multipathing by vxdmp ■ If any other information appears. downloading additional software. or contact Symantec Technical Support. continue on and complete this procedure. 4 (Conditional) Download and install the ASL and/or APM software. Type the following command: # vxdiskadm 3 On the Volume Manager Support Operations screen. .

press Enter to continue. 14 Type the following command: # vxdiskadm 15 On the Volume Enter. 7 On the Exclude Devices screen. . Planning the storage partitions (DAS/SAN disks) PureDisk lets you configure one or more of the following storage partitions: ■ /Storage is the repository for log files and database queue files. 18 Press q . On the Exclude controllers from DMP screen. 12 Reboot the node. type 17 and press Enter. 10 At the Continue 11 At the Hit RETURN to continue prompt. 16 Verify that all devices are excluded. This partition is required. type all and press Enter. type 19 and press This action selects List currently suppressed/non-multipath devices. and press Enter to quit. This action accepts the default of y and continues.. Manager Support Operations screen. operation? . type 5 and press Enter. 13 Log into the node as root.60 Preparing to configure the storage pool Planning the storage partitions (DAS/SAN disks) 6 On the Volume Manager Support Operations screen. type y and press Enter. 8 9 On the Volume Manager Device Operations screen.. press Enter. prompt. This action selects Prevent multipathing/Suppress devices from VxVM’s view. The display should contain the following heading and status: Devices excluded from multipathing by vxdmp: All devices have been excluded from multipathing by vxdmp 17 Press Enter to return to the main menu.

If any nodes are attached to iSCSI disks.Preparing to configure the storage pool Planning the storage partitions (DAS/SAN disks) 61 ■ /Storage/data is the repository for all file content. You can create /Storage and /Storage/data on the same partition. This partition is optional. If you combine these partitions. If you want to create a clustered storage pool. See “Configuring a node with a /Storage and a /Storage/data partition” on page 62. Symantec recommends that you configure each node’s storage identically. ■ Configuring a node with a /Storage partition The following table summarizes the disk partitioning for a node with only a /Storage partition. This partition is optional. Performance increases if you configure a /Storage/data and/or a /Storage/databases partition in addition to a /Storage partition. Symantec recommends that you create the /Storage/data partition on large. With one partition. For performance reasons. ■ /Storage/databases hosts the services’ databases. Note: The procedures for planning DAS/SAN storage differ from the procedures for planning to use iSCSI disks. proceed to the following: See “(Conditional) Configuring an iSCSI environment” on page 75. but you risk increased disk fragmentation in the /Storage/data directory. external. you allocate more space to store backup data. The following summarize the three disk partitioning options: ■ ■ See “Configuring a node with a /Storage partition” on page 61. /Storage/data. If you want to create a multinode storage pool. You can use the left-most column in the tables to record the disk groups you plan to use for each partition. configure each partition on shared storage. and /Storage/databases partitions” on page 62. However. if you create one partition for both directories. the benefit is that you do not lose space for the staging area. . storage. The following topics consist of tables and more details about the partitions. See “Configuring a node with /Storage. use RAID 5.

storage pool authority 10% of the size of /Storage/data . and /Storage/databases. Table 5-3 Disk group name Mount point Option 3: /Storage + /Storage/data + /Storage/databases partitions Services RAID All I/O requirement Size 5% of the size of /Storage/data Up to 8 TB /Storage RAID 0. RAID 1. and /Storage/databases partitions The following table summarizes the disk partitioning for a node with partitions for /Storage. or RAID 5 speed Needs normal I/O speed /Storage/data Content RAID 5 router Configuring a node with /Storage. Needs normal I/O or RAID 5 speed RAID 5 Needs normal I/O speed Needs fast I/O /Storage/data Content router /Storage/databases Metabase RAID 1 engine. or RAID 5 I/O requirement Needs normal I/O speed Size Up to 8 TB Configuring a node with a /Storage and a /Storage/data partition The following table summarizes the disk partitioning for a node with partitions for /Storage and /Storage/data partition. a /Storage/data. RAID 1. /Storage/data. Table 5-2 Disk group name Mount point /Storage Option 2: /Storage + /Storage/data partitions Services RAID All I/O requirement Size 15% of the size of /Storage/data Up to 8 TB RAID 0. RAID Needs normal I/O 1.62 Preparing to configure the storage pool Planning the storage partitions (DAS/SAN disks) Table 5-1 Disk group name Mount point /Storage Option 1: /Storage partition Services RAID All RAID 0. content router.

The PDOS installation wizard automatically installs VEA on each node. VxFS and VxVM are required if you want to create a clustered storage pool. hardware RAID offers the following advantages: ■ ■ ■ Keeps the load off the server's CPU Easier to replace failed drives Usually faster than software RAID In the following situations. When you run the storage pool configuration wizard. file system alternatives. you can use YaST or the Veritas Enterprise Administrator (VEA). the wizard creates an XFS file system and installs an LVM volume manager. Hardware RAID controllers can be more stable and are easier to maintain than software RAID. When you type the partition names. see the following: See “About the Veritas Enterprise Administrator’s role in a PureDisk storage pool” on page 197. . the wizard detects the types of disks attached to each node. consider using software RAID: ■ ■ ■ If the hardware RAID controller is of poor quality or slow. If the hardware RAID controller does not support array expansion. If VxFS does not support your disk types.Preparing to configure the storage pool Planning the storage partitions (DAS/SAN disks) 63 Storage partition configuration tool alternatives. As an alternative to the wizard. For more information about VEA. The disk partition specifications are case sensitive. If the hardware RAID controller is not supported on PDOS. however. If possible. the wizard creates a VxFS file system and installs the VxVM volume manager. RAID configuration alternatives Symantec recommends that you use Redundant Array of Independent Disks (RAID) technology for the disks you include in a PureDisk storage pool. In addition. and volume manager alternatives The storage pool configuration wizard detects the disks attached to your nodes and guides you through the storage partition creation process. or some other kind of RAID technology. You cannot use an XFS file system in a clustered storage pool. You can use a hardware RAID controller. type them exactly as shown in the procedure.

64 Preparing to configure the storage pool (Conditional) Editing the /etc/hosts files. The following procedure explains how to edit the /etc/hosts file on each PDOS node.conf file. the node's FQDN is not in a DNS directory. RAID 6 configurations cause the performance of the PureDisk databases to degrade significantly. metabase engine. which adversely affects the performance of PureDisk processes. /etc/resolv. and client networking files Perform one or more of the following procedures if you did not specify a domain name server (DNS) when you installed PDOS on each node or if you were not able to obtain a valid FQDN from your network administrator. To update the /etc/hosts file on the PDOS nodes 1 2 Log into a node as root. Symantec highly recommends that you create correct DNS entries for all PureDisk installations.conf file” on page 65. In these cases. .conf file. (Conditional) Updating the /etc/hosts file on the PDOS nodes Perform the following procedure if you did not specify a domain name server (DNS) when you installed PDOS on each node or if you did not get a valid FQDN entry on your DNS. and storage pool authority services. and client networking files Note: PureDisk has databases for the content router. (Conditional) Editing the /etc/hosts files. Use a text editor to open file /etc/hosts. See “(Conditional) Editing the /etc/resolv. See “(Conditional) Editing client networking information” on page 65. Symantec recommends that you do not use a RAID 6 configuration for the partitions on which those PureDisk databases reside. /etc/resolv. The procedures are as follows: ■ ■ ■ See “(Conditional) Updating the /etc/hosts file on the PDOS nodes” on page 64.

102 PureDisk3.conf file Perform the following procedure if you do not have a DNS at your site.100. The following procedure explains how to update each client's networking information.com PureDisk Example 2. Look for the line that starts with the letters search.com PureDisk2 102.100. If you have a multinode storage pool. and host name.conf. The following procedure explains how to update the /etc/resolv. /etc/resolv.Preparing to configure the storage pool (Conditional) Editing the /etc/hosts files.min. and the host name of each node in your storage pool to one line in the file.conf file.min. Repeat the previous steps on each node in your storage pool.com PureDisk1 101. the FQDN. Each node must have identical /etc/hosts file entries that contain the node's IP address.100 PureDisk1. FQDN.conf file 1 2 3 4 5 Log into a node as root. The resulting file might look as follows: 100.101 PureDisk2.101.com PureDisk3 4 Repeat the previous steps on each node in your storage pool.min. . add a line similar to the following: 100.102.conf file. Example 1. add a line for each node. (Conditional) Editing client networking information Perform the following procedure if you did not specify a domain name server (DNS) when you installed PDOS on each node or if you did not get a valid FQDN entry on your DNS.min. (Conditional) Editing the /etc/resolv.100.100 PureDisk. Comment out or delete the line that begins with the letters search.101. To edit the /etc/resolv. If you have an all-in-one storage pool.102. and client networking files 65 3 Add the IP address.100. Use a text editor to open file /etc/resolv.

Preparing to configure a remote root broker In the remote root broker configuration. You do not need to complete the procedures in this section. You specify a local root broker entirely within the storage pool configuration wizard. See “Preparing to configure an external root broker” on page 67. you do not need to complete the procedures in this section. (Conditional) Preparing a remote root broker or an external root broker The PureDisk Getting Started Guide explains how PureDisk authenticates users when they log into the storage pool authority. the PureDisk Getting Started Guide explains the differences between local. Use each client's operating system commands to add the IP address. FQDN. These broker types rely on communication between the storage pool authority and another computer on your site's enterprise network. These broker types require additional configuration outside of the storage pool configuration wizard. You can configure a local root broker on the storage pool authority node if no other root broker exists in your enterprise network. This configuration assumes that . and host name of each PureDisk node to your client operating system's networking configuration. remote. Linux.66 Preparing to configure the storage pool (Conditional) Preparing a remote root broker or an external root broker To edit client networking information ◆ Edit the networking information on each Windows. If you want to configure a remote root broker or an external root broker. A summary of these differences is as follows: ■ If you want to configure a local root broker. Do not install multiple root brokers in your PureDisk environment. or UNIX client that you want to attach as a client to this storage pool. and external root brokers as supported by the Symantec Product Authentication Service. you need additional configuration information. Note: Symantec recommends that you have only one root broker in an enterprise network. PureDisk installs only an authentication broker on the new storage pool authority node. Proceed to one of the following: ■ ■ ■ See “Preparing to configure a remote root broker” on page 66. In addition. PureDisk installs multiple root brokers. If you specify the Local option more than one time when you install the storage pools in your environment.

In this configuration.Preparing to configure the storage pool (Conditional) Preparing a remote root broker or an external root broker 67 you installed a local root broker on a storage pool authority node in a different storage pool elsewhere on your network. This password is the root login password for the storage pool authority node. Table 5-5 lists all the information you need to gather. Table 5-4 Field prompt FQDN of the SPA Remote root broker configuration information Additional information Specify the FQDN of the PureDisk storage pool authority node that hosts your enterprise network’s root broker. Type one of the following commands to obtain the domain name of the root broker’s private domain: ■ On a UNIX host. If the root broker resides on a storage pool authority node in a clustered storage pool. Perform this step only if you cannot put the root broker on a PureDisk host and you have no other root broker on the network. Specify the password for the root broker host on the remote storage pool. you can record the information about your external root broker in the My information column. To gather the information you need to configure an external root broker 1 (Optional) Install the Symantec Product Authentication Service root broker on a UNIX or Windows host. Log in as root to the computer that hosts the external root broker. 2 3 4 Locate the external root broker host computer and record the FQDN of the external root broker host in the FQDN field of Table 5-5. Table 5-4 shows the information that you need to supply. specify the FQDN of the storage pool authority service. The following procedure explains how to gather information for an external root broker that is not installed on a PureDisk host. you can record it in the table's My information column. After you gather information about the remote root broker. My information Root Broker Password Preparing to configure an external root broker You can configure a storage pool to use an external root broker on your enterprise network. PureDisk installs only an authentication broker on the new storage pool authority node. As you perform the following procedure. type the following command: .

exe listpd --pdrtype root The output from this command is as follows: Domain(s) Found 1 **************************** Domain Name root@hostname Expiry Interval 0 **************************** You need the information from the root@hostname line for the next step. The root broker’s private domain repository has only one private domain: the root private domain.68 Preparing to configure the storage pool (Conditional) Preparing a remote root broker or an external root broker /opt/VRTSat/bin/vssat listpd --pdrtype root ■ On a Windows host. which is the root@hostname information from step 4. type the following command: C:\Program files\VERITAS\Security\Authentication\bin\vssat. type the following command all on one line: C:\Program Files\VERITAS\Security\Authentication\bin\vssat. 5 Record the domain name information. type the following command: /opt/VRTSat/bin/vssat addprpl --pdrtype root --domain root@hostname \ --prplname puredisk_authbroker --password password ■ On a Windows host. in the Domain name field of Table 5-5.exe addprpl --pdrtype root --domain root@hostname --prplname puredisk_authbroker --password password . 6 Type one of the following commands to create an authentication principal on the external host: ■ On a UNIX host.

you want to transfer the copy to the storage pool authority node safely. The password you want to use for this authentication principal. password The following is sample output from this command: createprpl ---------------------Created Principal: puredisk_authbroker 7 On the external host. this node is the storage pool authority. Transfer the copy AFTER you install the PureDisk operating system on your storage pool authority node. but BEFORE you start the storage pool configuration wizard. copy file /opt/VRTSat/bin/root_hash. Symantec recommends that this value be a fully qualified domain name (FQDN). copy the following file: C:\Program Files\VERITAS\Security\Authentication\bin\root_hash 8 Write the copy of the root hash file from the external host to the storage pool authority node. The external root broker can reside on a UNIX host or on a Windows host. such as scp(1) or sftp(1). The identifier for the PureDisk node that needs to use the external root broker.Preparing to configure the storage pool (Conditional) Preparing a remote root broker or an external root broker 69 These commands accept the following arguments: hostname puredisk_authbroker The hostname information from step 4. make a copy of the root hash file. as follows: ■ ■ On a UNIX host. Use a secure transfer method. . Copy the root hash file to a disk and then transfer the copy to the storage pool authority node. Typically. On a Windows host. Your goal is to create a copy of the root hash file on the external host. such as the following: ■ ■ Use a file transfer method. The file that you want to copy is located in a different place on each host type. You create this password at this time. Then.

Specify the password that you used when you created a principal on the root broker. If this server is installed in a cluster. The storage pool configuration wizard prompts you to specify the location of the root hash file On the Root Broker Configuration Page. For example. 9 Copy the information that you obtained in this procedure to the appropriate fields in the following table: See Table 5-5 on page 70. Do not write the root hash file to the /tmp directory.70 Preparing to configure the storage pool (Conditional) Preparing a remote root broker or an external root broker Write the file to a safe place. write root_hash to /root on the storage pool authority. My information Root Broker Port Authentication Broker Login Authentication Broker Password Domain Name . specify the host FQDN of the server. Table 5-5 Field prompt FQDN External root broker configuration information Additional information Specify the FQDN of the external server that hosts your enterprise network’s root broker. root@fqdn or root@hostname . The default port value is 2821. Specify the private domain name of the external root broker. 10 Complete any remaining blank fields in Table 5-5. After you gather information about the remote root broker. If necessary. This principal is used to communicate with the authentication broker on the new storage pool. you can record it in the table's My information column. This principal is used to communicate with the authentication broker on the new storage pool. Use the output from the listpd command as described in step 5. Refer to the table after you start the storage pool configuration wizard. Specify the login name that you used when you created a principal on the root broker. change this value for your environment. For example.

My information Note: Do not modify this value. (Conditional) Preparing to configure a clustered PureDisk storage pool Perform the following procedures if you want to configure a clustered storage pool. See “Reviewing the VCS requirements” on page 73. /root. ■ ■ See “Reviewing the Veritas Cluster Server (VCS) requirements” on page 71. . ■ ■ See “An example cluster” on page 71. Location of Root Broker Hash (Full Path) Specify the full path to the root hash file on the storage pool authority node. An example cluster The procedures in this chapter show how to implement the following cluster configuration example. Reviewing the Veritas Cluster Server (VCS) requirements The following provide an overview of how to implement a highly available storage pool and explain the VCS requirements. assume that you want to configure the three-node cluster in Figure 5-1. You can refer to this example as you complete the procedures. For example.Preparing to configure the storage pool (Conditional) Preparing to configure a clustered PureDisk storage pool 71 Table 5-5 Field prompt Domain Type External root broker configuration information (continued) Additional information The default value for the domain is vx. See “Examining the NICs in this node for addressing” on page 73. For example.

com Host FQDN: node1.acme. 1st heartbeat network Node 2 – Metabase engine + content Node 2 – Metabase engine + content router router NIC1: NIC1: Host IP: 100. NIC3: NIC3: Attached to private network. No IPs. No IPs.100.com Virtual IP: 100. No IPs.100.acme.100. Attached to private network. Attached to private network. SAN . No IPs.com NIC2: Attached to private network. No IPs.com Service FQDN: NIC2: Attached to private network. 2nd heartbeat network NIC3: Attached to private network.100.110 Host FQDN: node2.acme.acme.acme.acme. Node 2 – Passive node NIC1: Host FQDN: node3.72 Preparing to configure the storage pool (Conditional) Preparing to configure a clustered PureDisk storage pool Figure 5-1 Example three-node cluster Public Network Node 1 – All-in-one NIC1: Host FQDN: node1. No IPs.111 NIC2: NIC2: Attached to private network.com Service FQDN: node1s. No IPs. No IPs.com Service FQDN: node2s. NIC3: Attached to private network.

You plan to configure node 2 with an extra content router and an extra metabase engine. You can use this information later if you need to perform a disaster recovery or if you want to reconfigure your storage pool.Preparing to configure the storage pool (Conditional) Preparing to configure a clustered PureDisk storage pool 73 In Figure 5-1. The procedure in this section explains how to examine each NIC for existing addresses. These two NICs comprise the private network that VCS uses to monitor the cluster's heartbeat. The spreadsheet shows all the information you need to gather before you begin an installation. PureDisk configures two NICs without any addressing. During the PDOS installation.xls 2 Proceed to the following: See “Examining the NICs in this node for addressing” on page 73.6 DVD and is named as follows: PureDisk_ClusterPlanning. The spreadsheet resides in the following file in the puredisk/documentation directory of the PureDisk 6. there are two active nodes and one spare. To prepare for a VCS installation 1 Make sure that you are familiar with the HA installation prerequisites as described in the following manual: PureDisk Getting Started Guide. PureDisk requires that two NICs in each node be configured without addressing. . These NICs are for the cluster’s private heartbeat. You plan to configure node 1 as an all-in-one system with all possible PureDisk services installed upon it. Make sure to complete the spreadsheet that is included in the PureDisk software distribution. Reviewing the VCS requirements The following procedure reviews the VCS requirements. You plan to configure node 3 as a spare node. Repeat the following procedure for each node. Examining the NICs in this node for addressing The storage pool configuration wizard assumes that you know how to address the NICs in the nodes you want to configure in a cluster.

do not have addresses.MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:04:23:b0:4f:86 brd ff:ff:ff:ff:ff:ff eth3: <BROADCAST. Type the ip a(8) command to retrieve the NIC information for this node. eth2 and eth3.0 3: 4: 5: 6: .80.UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:11:43:e4:0b:2b brd ff:ff:ff:ff:ff:ff eth2: <BROADCAST. The following example shows a correctly configured node.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 valid_lft forever preferred_lft forever eth1: <NO-CARRIER. The output of the ip a(8) command includes each NIC’s MAC address in the link/ether field.0.0.UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.74 Preparing to configure the storage pool (Conditional) Preparing to configure a clustered PureDisk storage pool To examine the NICs 1 2 Log into one of the nodes. eth0.MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:04:23:b0:4f:87 brd ff:ff:ff:ff:ff:ff sit0: <NOARP> mtu 1480 qdisc noop link/sit 0. 3 Examine the ip a(8) command output.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.92.0.0.80. this NIC is the primary NIC.0.MULTICAST.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST.BROADCAST. The other NICs. One NIC. has a static address.102/21 brd 10.0 brd 0.0.MULTICAST. # ip a 1: lo: <LOOPBACK.

make sure that the node contains at least two network interface cards (NICs). private iSCSI network.xls. You need to know the MAC addresses of the two NICs that you want to use for the private heartbeat.Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 75 4 Record the MAC address information from the ip a(8) command output. Symantec does not recommend that you nest mount /Storage/data or /Storage/databases on the same iSCSI disk as /Storage. For example. Depending on how you want to mount your storage partitions. . The YaST interface identifies each NIC by its MAC address. you might need to attach DAS/SAN disks to your nodes. if you only want to configure a /Storage partition. you can mount that partition on iSCSI disks. The following is an overview of the procedures you need to complete if you want to use iSCSI storage: ■ ■ ■ See “Verifying iSCSI prerequisites” on page 75. (Conditional) Configuring an iSCSI environment PureDisk enables you to mount the storage partitions on iSCSI disks. See “Configuring the second NIC for the iSCSI network” on page 76. 2 Plan your storage layout. Verifying iSCSI prerequisites The following procedure explains how to verify the iSCSI configuration prerequisites. Make sure that you gathered this information and recorded it on the planning spreadsheet. The second NIC is required for the dedicated. too. 5 Repeat this procedure for each node you want to configure. The ethn interfaces without the IP addresses are the NICs for the private heartbeats. see the following: See “Planning the storage partitions” on page 81. For more information about partition requirements. See “Planning the storage partitions” on page 81. To verify iSCSI configuration prerequisites 1 For each node that uses iSCSI storage. PureDisk_ClusterPlanning.

Configuring the second NIC's private network The following procedure explains how to configure the private network. select Traditional Method with ifup and select Next. After you install PDOS on a node. The following procedures explain how to configure a NIC for the iSCSI network. On the Network Card Configuration Overview page. Typically. MTU size and Jumbo frame support. On the second NIC. At a command prompt. type the following command to launch the SUSE Linux YaST configuration tool. Do not type other combinations of uppercase and lowercase letters. To configure the private network on a secondary NIC 1 2 Log into the node as root. 3 4 5 6 In the YaST Control Center main page. this NIC is the second NIC in the node. Configuring the second NIC for the iSCSI network A second NIC in each storage pool node facilitates communication on the iSCSI network. On the Network Address Setup page.76 Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 3 Work with your iSCSI vendor representative to make sure that your NICs and your iSCSI network are configured correctly. and jumbo frames” on page 79. See “Configuring flow control. these installation instructions describe how to make sure that these setting are correct on the node's NICs. ■ ■ ■ See “Configuring the second NIC's private network” on page 76. note the settings for the following: ■ ■ Flow control. 4 Obtain the group IP address of the iSCSI targets. # yast You can type yast or YaST to start the interface. See “Configuring the iSCSI initiator for each iSCSI target” on page 77. select the NIC that you want to use for the iSCSI private network and select Edit. perform the following steps: . On the Network Setup Method page. MTU support. select Network Devices > Network Card and press Enter.

On the iSCSI Initiator Overview page. Tab to the IP address field. type the correct port number. verify the information. and type the IP address that you want to assign to this NIC on the node's private iSCSI network. Select Finish. To configure the iSCSI initiator 1 2 3 4 5 6 Insert the PureDisk software disk into a drive on the node. Log in to the iSCSI target. the open-iscsi package must be installed.Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 77 ■ ■ Select Static Address Setup. If this information is incorrect. . On the To configure the iSCSI initiator. Select one of the authentication options: ■ ■ If your iSCSI target does not use CHAP authentication. Authenticate the iSCSI target. perform the following steps: ■ ■ In the IP Address field. The following procedure explains how to configure the iSCSI initiators in a storage pool. press the Tab key until you select Discovered Targets and press Enter. you enter authentication credentials for each LUN or for each iSCSI target. select Network Services > iSCSI Initiator and press Enter. ■ 7 8 Select Next. On the iSCSI Initiator Discovery page. Configuring the iSCSI initiator for each iSCSI target You need to configure an iSCSI initiator for each target. type the IP address of the iSCSI target. select Continue. In the YaST Control Center main page. Install now? pop-up. select No Authentication and select Next. Select Discovery. Tab to the Subnet Mask field and type the subnet mask. During this configuration process. The configuration process consists of the following main steps: ■ ■ ■ Select an iSCSI target. In the Port field.

Verify that the Start-Up column displays automatic for this disk volume. Press the arrow keys to select the LUN you want to configure. type the CHAP password. select Outgoing Authentication. Press the right arrow key to scroll to the right-most area of the display. type the CHAP user name. 13 On the iSCSI Initiator Overview screen. type the CHAP password. If your iSCSI target uses CHAP authentication. select No Authentication and select Next. Your choices are as follows: ■ 10 On the iSCSI Initiator Discovery page. options. ■ 11 Repeat the following steps until you have selected all the disks you want to configure: ■ ■ ■ ■ Step 7 Step 8 Step 9 Step 10 12 Select Next. Select Log In and press Enter. 7 8 9 On the iSCSI Initiator Overview screen. Select Toggle Start-Up and press Enter. type the CHAP user name. . and select Next. press the Tab key to position the cursor in the LUN selection box. and select Next. select Outgoing Authentication. select Toggle Start-Up. If the Start-Up column displays manual. select one of the authentication If your iSCSI target does not use CHAP authentication. select Connected Targets.78 Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment ■ If your iSCSI target uses CHAP authentication. 14 Perform the following steps to verify that each volume you logged into appears in the list: ■ ■ ■ ■ Select a volume. and set this column to automatic.

or use the ifconfig(8) command. Your goal is to obtain the current MTU size and flow control information. You can choose from one of two methods to configure flow control and MTU size. The following procedures explain how to retrieve device configuration information and how to configure these settings. The second procedure is boot persistent. 2 Retrieve device information. perform the following steps: ■ ■ ■ Select Service. and jumbo frames The flow control and the MTU size should match those of the iSCSI environment. complete the following procedures to change the flow control or the MTU size. then it needs to be enabled on the NIC for iSCSI also. 3 Examine the output and determine whether you need to change any device configuration information. If flow control is enabled in the switch or on the iSCSI target.Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 79 15 Repeat the following step for each volume: Step 14 16 On the iSCSI Target Overview page. To configure flow control (for testing. MTU support. You can use the first procedure for test purposes. not boot persistent) ◆ Type the following command to set the ETHTOOL_OPTION setting: # ethtool -A device options . Jumbo frames are frames with a typical MTU size of 9000 (the size can vary). press Tab to select When Booting. Select Finish. To retrieve device information 1 Type the ifconfig(8) command to retrieve device address information. In the Service Start box. Configuring flow control. Look for the ethn number that corresponds to the IP address assigned to the iSCSI NIC that you configured in the following: See “Configuring the second NIC for the iSCSI network” on page 76. Use the ethtool(8) command with its -d option. The MTU size should match the MTU size that is used within the iSCSI network. If you need to change configuration information.

including the MAC address. rx off. For size. Specifies if pause autonegotiation is enabled. Type the following command: # ifconfig device mtu size For device. Specifies if TX pause is enabled. not boot persistent) ◆ Run the ifconfig(8) command to set the MTU size temporarily. tx on. Specifies if RX pause is enabled. For example: # ethtool -A eth1 autoneg on ■ ■ rx on. For example: # ifconfig eth1 mtu 9000 .80 Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment For device. You can use the ip(8) command with its -a option to retrieve NIC information. To configure the MTU size (for testing. specify the device number. specify one or more of the following options: ■ autoneg on. specify the MAC address of the NIC. specify the number that matches the MTU size that is specified across the iSCSI network. tx off. autoneg off. For options. You can obtain this information from your network administrator.

The ETHTOOL_OPTIONS setting controls flow control. PureDisk lets you configure one or more of the following storage partitions: .31.Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 81 To configure the flow control and the MTU size settings (permanently.83. For size. Planning can make your configuration session with the storage pool configuration wizard more efficient. # cd /etc/sysconfig/network # cat ifcfg-eth-id-00\:50\:56\:a9\:47\:28 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='flow control' IPADDR='10. you can change the following lines: ETHTOOL_OPTIONS='-A MTU='9000' autoneg on' Planning the storage partitions Symantec recommends that you plan your storage partitions and disk layout. including the MAC address. specify the options you configured for testing.240.5dU8kR7eh2C' USERCONTROL='no' _nm_name='bus-pci-0000:00:11. The MTU setting controls the MTU size.0' # For flow_control. boot persistent) ◆ Open file /etc/sysconfig/network/ifcfg-eth-id-macaddress. For macaddress. The following example shows the file that contains the flow control and MTU size settings. For example. specify the MTU size.98' MTU='size' NAME='VMWare 82545EM Gigabit Ethernet Controller (Copper)' NETMASK='255. You can use the ip(8) command with its a option to retrieve NIC information. specify the MAC address of the NIC.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='rBUF.

See “RAID configuration alternatives” on page 84. /Storage/data is the repository for all file content. Symantec recommends that you create the /Storage/data partition on large. you allocate more space for storing backup data. Table 5-6 Mount point /Storage Option 1: /Storage partition Services All Disk type iSCSI RAID RAID 0. If you want to create a multinode storage pool. The following summarize the three disk partitioning options: ■ See “Configuring a node with a /Storage partitions using iSCSI disks” on page 82. or RAID 5 I/O requirement Size Needs normal I/O Up to 8 TB speed . However. You can create /Storage and /Storage/data on the same partition. Symantec recommends that you configure each node’s storage identically. the benefit is that you do not lose space for the staging area. ■ /Storage/databases hosts the services’ databases. but you risk increased disk fragmentation in the /Storage/data directory. use RAID 5. /Storage/data. external.82 Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment ■ ■ /Storage is the repository for database queue files. RAID 1. See “Configuring a node with /Storage. and /Storage/databases partitions using iSCSI disks” on page 83. With one partition. if you create one partition for both directories. This partition is optional. This partition is optional. storage. Configuring a node with a /Storage partitions using iSCSI disks The following table summarizes the disk partitioning for a node with only a /Storage partition. Performance increases if you configure a /Storage/data and/or a /Storage/databases partition in addition to a /Storage partition. For performance reasons. ■ ■ The following topics describe other topics that pertain to iSCSI disk use in PureDisk storage pools: ■ ■ See “File system and volume manager alternatives” on page 83. This partition is required. If you combine these partitions. See “Configuring a node with /Storage and /Storage/data partitions using iSCSI disks” on page 83.

/Storage/data.Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment 83 Configuring a node with /Storage and /Storage/data partitions using iSCSI disks The following table summarizes the disk partitioning for a node with partitions for /Storage and /Storage/data partition. If you want to configure these three partitions. and /Storage/databases. a /Storage/data. RAID 1. RAID 1 content router. storage pool authority File system and volume manager alternatives PureDisk supports the XFS file system with the LVM volume manager for iSCSI storage arrays. . configure the /Storage partition on a DAS disk or SAN disk. configure the /Storage partition on a DAS disk or SAN disk. or RAID 5 RAID 5 I/O requirement Size Needs normal I/O 15% of the size of speed /Storage/data Needs normal I/O Up to 8 TB speed /Storage/data iSCSI Content router Configuring a node with /Storage. Table 5-7 Mount point /Storage Option 2: /Storage + /Storage/data partitions Services All Disk type DAS or SAN RAID RAID 0. and /Storage/databases partitions using iSCSI disks The following table summarizes the disk partitioning for a node with partitions for /Storage. The iSCSI storage configuration instructions explain how to create the storage partitions with an XFS file system. If you want to configure these two partitions. RAID 1. Table 5-8 Mount point /Storage Option 3: /Storage + /Storage/data + /Storage/databases partitions Services All Disk type DAS or SAN RAID RAID 0. or RAID 5 RAID 5 I/O requirement Size Needs normal I/O 5% of the size of speed /Storage/data Needs normal I/O Up to 8 TB speed Needs fast I/O 10% of the size of /Storage/data /Storage/data iSCSI Content router /Storage/databases iSCSI Metabase engine.

which adversely affects the performance of PureDisk processes. RAID 6 configurations cause the performance of the PureDisk databases to degrade significantly. consider using software RAID: ■ ■ ■ If the hardware RAID controller is of poor quality or slow. Symantec recommends that you do not use a RAID 6 configuration for the partitions on which those PureDisk databases reside. metabase engine. or some other kind of RAID technology. In addition. hardware RAID offers the following advantages: ■ ■ ■ Keeps the load off the server's CPU Easier to replace failed drives Usually faster than software RAID In the following situations. . You can use a hardware RAID controller.84 Preparing to configure the storage pool (Conditional) Configuring an iSCSI environment The disk partition specifications are case sensitive. Hardware RAID controllers can be more stable and are easier to maintain than software RAID. RAID configuration alternatives Symantec recommends that you use Redundant Array of Independent Disks (RAID) technology for the disks you include in a PureDisk storage pool. When you type the partition names. however. If the hardware RAID controller does not support array expansion. type them exactly as shown in the procedure. and storage pool authority services. If the hardware RAID controller is not supported on PDOS. Note: PureDisk has databases for the content router.

Chapter 6 Configuring the storage pool This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ About configuring the storage pool Starting the storage pool configuration wizard Completing the Welcome page Completing the PureDisk Licenses pages Completing the Storage Pool Details page Completing the Node Selection pages Completing the Storage Selection pages (Conditional) Completing the Cluster Option pages Completing the Services Configuration page Completing the Root Broker Configuration page Completing the Selection Summary page Completing the Implementation page About configuring the storage pool The storage pool configuration wizard enables you to configure a single-node. or unclustered storage pool. clustered. . The wizard detects the disks attached to your nodes and enables you to configure the storage partitions to suit your site's needs. multinode.

The following provide information about how to configure the storage pool by using the storage pool configuration wizard: ■ ■ ■ See “Configuring the storage pool” on page 86. and other information. 5 Specify the storage pool. For information about how to specify these details. and mount points for the storage partitions. see the following: See “Completing the Node Selection pages” on page 94. ID number. 2 Start the storage pool configuration wizard. you can maximize the storage pool configuration wizard screen to be larger. . For information about how to specify nodes. see the following: See “Completing the PureDisk Licenses pages” on page 91. See “Characters prohibited in storage pool configuration file fields” on page 88. name. For information about how to add license keys. Perform this step if you unplugged your NICs before you installed PDOS.86 Configuring the storage pool About configuring the storage pool TIP: Depending on your monitor's resolution. NTP server. Configuring the storage pool The following procedure shows the steps you need to complete in order to configure a storage pool. See “Cancel button effects” on page 89. For information about how to start the storage pool configuration wizard. see the following: See “Completing the Welcome page” on page 90. For information about how to complete the Welcome page. 4 Add your license keys. see the following: See “Starting the storage pool configuration wizard” on page 89. 7 Specify disk groups. see the following: See “Completing the Storage Pool Details page” on page 92. 3 Complete the Welcome page and (optionally) specify high availability. volumes. To configure a PureDisk storage pool 1 (Conditional) Plug in all your network information cards (NICs). 6 Specify node-specific addressing and password information.

you do not have to specify disk groups or storage information. . see the following: See “(Conditional) Completing the Cluster Option pages” on page 105. For more information about specifying a broker. If you performed a Onedisk PDOS installation. The wizard does not present the Storage Selection pages to you if you performed a Onedisk PDOS installation. 9 For each PureDisk node.. 8 (Conditional) Specify cluster information. see the following: See “Planning the storage partitions (DAS/SAN disks)” on page 60. Make sure you reviewed the following information before you choose a broker location: See “(Conditional) Preparing a remote root broker or an external root broker” on page 66. For nodes with iSCSI disks. specify the PureDisk services that you want to reside on that node. see the following: See “Completing the Root Broker Configuration page” on page 108. 10 Specify where this storage pool's root broker is located. For more information about specifying cluster information. All storage is configured with a VxFS file system on the /Storage partition on the internal disk. Make sure you review the following information before you complete the Storage Selection pages: ■ For nodes with DAS/SAN disks. see the following: See “Completing the Storage Selection pages” on page 96. For more information about specifying services. ■ For information about the Storage Selection pages. see the following: See “(Conditional) Configuring an iSCSI environment” on page 75.Configuring the storage pool About configuring the storage pool 87 The storage pool configuration wizard detects each node's disks and prompts you to organize your disks into storage partitions. see the following: See “Completing the Services Configuration page” on page 106. Perform this step only if you want to configure a highly available storage pool. the wizard presents you with the Storage Selection pages. and you can use the Storage Selection pages to configure storage. If you performed an Install or an Expert PDOS installation.

12 Monitor the configuration implementation. see the following: See “Completing the Implementation page” on page 110. For more information about the Implementation page. Table 6-1 Invalid character & " # < > ' ) } \ | TAB SPACE All international characters Invalid password characters Name and hexadecimal code Ampersand (0x26) Quotation mark (0x22) Pound sign (0x23) Less-than sign (0x3c) Greater-than sign (0x3e) Apostrophe (0x27) Closing parenthesis (0x29) Closing curly brace (0x7d) Backslash (0x5c) Pipe (0x7c) Tab character (0x09) Space character (0x20) -- . see the following: See “Completing the Selection Summary page” on page 110. For more information about the Selection Summary page. Table 6-1 shows the list of prohibited characters. Characters prohibited in storage pool configuration file fields The storage pool configuration wizard does not permit you to type certain characters in its fields.88 Configuring the storage pool About configuring the storage pool 11 Review your specifications on the Selection Summary page and start the installation.

Perform this step if you want to configure a highly available. clustered storage pool. The storage pool configuration wizard landing page contains links to the following: ■ Change SPA Installer password. which displays a pop-up window that guides you through the process of changing the password for this installer. the wizard exits. When you installed PDOS on the storage pool authority node. which displays the PureDisk Storage Pool Installation Guide in PDF format. To start the configuration wizard 1 (Conditional) Plug in all network interface cards (NICs). If you want to change your specifications later. the wizard cancels the activity for that page only. If you click that middle Cancel button. Perform this step if you unplugged cards before you installed PDOS. About. 2 (Conditional) Insert the PureDisk software disk into a drive on the storage pool authority node that is capable of reading a DVD. ■ ■ ■ . Some storage pool configuration wizard pages have a Cancel button in the middle of the page. which lists PureDisk release information. which launches a new browser window with links to Symantec technical support information for PureDisk. specify the IP address of the storage pool authority node. restart the wizard and respecify your selections. Contact technical support.Configuring the storage pool Starting the storage pool configuration wizard 89 Cancel button effects If you click the Cancel button in the lower right corner of a storage pool configuration wizard page. the PDOS installation wizard issued a message with this ip_addr that you need to use. Starting the storage pool configuration wizard The following procedure explains how to start the storage pool configuration wizard. Installation help. The wizard records the configuration specifications you provided before you clicked Cancel in the topology files. 3 Open a Web browser and type the following URL: http://ip_addr/Installer For ip_addr.

see the Symantec NetBackup PureDisk Getting Started Guide. click Start the storage pool configuration wizard. Completing the Welcome page The following procedure explains how to complete the Welcome page. 3 4 Click Next.90 Configuring the storage pool Completing the Welcome page ■ Logout. On the welcome screen. . Some of the most important prerequisites appear on this Welcome page. type root. which stops the installer and allows you to exit. 2 Click in each of the prerequisite boxes. in the User Name field. multinode storage pools. Proceed to the following: See “Completing the Welcome page” on page 90. type the SPA Installer password that you specified when you installed PDOS on the storage pool authority node. You cannot convert a standard storage pool to a high availability storage pool at a later date. Highly available storage pools are. To complete the Welcome page 1 Click the button to the left of Yes or No to specify high availability for this storage pool. 4 5 6 7 8 On the landing page. configure the storage pool authority node first. by definition. For more comprehensive information about PureDisk prerequisites. Symantec requires that you configure high availability during a storage pool's initial configuration session. If you want to enable high availability. To enable high availability. In the Password field. select Yes on this page. Click Log on. You need to include at least two PDOS nodes in a highly available cluster. Proceed to the following: See “Completing the PureDisk Licenses pages” on page 91. The storage pool configuration wizard assumes that the nodes in this environment meet the PureDisk prerequisites. If you want to configure a multinode storage pool.

If the page displays 'No license keys installed'. If you need to remove one of the license keys. Click Next. or if you want to install more license keys. When you configure a storage pool for the first time. The following procedures explain how to complete these pages: ■ ■ See “Completing the License Key Management page” on page 91. ■ ■ Completing the Add Additional License Key subpage The following procedure explains how to complete the Add Additional License Keys subpage. The PureDisk Licenses pages are as follows: License Key Management and Add Additional License Key. To verify license keys ◆ Examine the License Keys table. then you do not need to add or remove any licenses at this time. Proceed to the following: See “Completing the Add Additional License Key subpage” on page 91. Proceed to the following: See “Completing the Storage Pool Details page” on page 92. click Add License. click the button to the left of the license key that you want to remove and click Remove License. See “Completing the Add Additional License Key subpage” on page 91.Configuring the storage pool Completing the PureDisk Licenses pages 91 Completing the PureDisk Licenses pages The PureDisk Licenses pages let you add and remove licenses. make sure to add all the license keys you obtained from Symantec Corporation. ■ If the License Keys table shows all the license keys that pertain to this storage pool. . Completing the License Key Management page The following procedure explains how to complete the License Key Management page.

You can include special characters in the Name field. type a name for this storage pool. make sure that the value is less than 2147. 3 4 (Optional) In the Description field. In the Location field. the default location appears as Unknown location. To complete the Storage Pool Details page 1 In the ID field. accept the description of Default location for this storage pool or type a new location. accept the ID number that the wizard presents to you or type in your own ID number. the wizard presents the License Key Management subpage. type the license key exactly as you received it. If you specify your own ID. For information about how to complete the LicenseKeyManagement subpage. type a description for this storage pool. In the administrator Web UI. Failure to record and then correctly reuse this number can result in an inoperable storage pool after a SPAR restore or another disaster recovery operation. Completing the Storage Pool Details page The following procedure explains how to complete the Storage Pool Details page. . Alternatively. Note: Record the storage pool ID number in a safe place. Each storage pool in your PureDisk environment must have a unique ID number. see the following: See “Completing the License Key Management page” on page 91. You can use your mouse to copy and paste this license key from the license file that you received from Symantec Corporation. This name appears in the PureDisk administrator Web UI.92 Configuring the storage pool Completing the Storage Pool Details page To complete the Add Additional License Key subpage 1 Enter one of the license keys you received from Symantec Corporation into the License Key field. 2 Click Ok. 2 In the Name field. you can use the PureDisk administrator Web UI to add additional locations. After you click Ok. After installation.

you can use the administrator Web UI to specify the storage pools that report into the central storage pool. 6 (Optional) Check the This is the Central Storage Pool Authority (SPA) box. You can also enable a storage pool to be a central storage pool after the storage pool is configured.Configuring the storage pool Completing the Storage Pool Details page 93 5 In the Department field. accept the description of Default department for this storage pool or type a new department name. Check the Central Storage Pool Authority (SPA) box is you want to designate this storage pool as a central storage pool. PureDisk does not support multiple time zones in a single storage pool. A central storage pool is one that performs all the functions of an independent storage pool but also has central reporting capabilities. retype the password you typed in step 7. the default department appears as Unknown department. 7 8 9 In the SPA Password field. In the NTP Server field. type the FQDN of your site's NTP server. you can use the PureDisk administrator Web UI to add additional locations. For more information about central reporting. A central storage pool authority can generate licensing and capacity reports for all storage pools that report in to the central storage pool. Symantec strongly recommends the use of an NTP server in production environments. If no NTP server is available. For more information about how to set the date manually. use the date(1) command to set the system date after the storage pool is configured. 10 In the Time Zone field. see the Symantec NetBackup PureDisk Administrator's Guide. type the password for users to type when they want to log into the PureDisk administrator Web UI. In the administrator Web UI. After you install all your storage pools. After installation. In the Confirm Password field. . You can select only one time zone for a storage pool. pull down the menu and select the time zone in which this storage pool resides. Symantec recommends that you configure only one central storage pool in your enterprise network. see the following: See “Completing the storage pool installation” on page 111.

Perform the following steps for each node that you want to configure as a passive node: ■ ■ ■ ■ Select the node you want to configure as a passive node. The following procedures explain how to complete the Node Selection pages: ■ ■ See “Completing the Storage Pool Node Summary subpage” on page 94. By default. If you want to configure a storage pool with more than one node. The Node Selection pages have the following subpages: the Storage pool Node Summary page and the Add Additional Node page. select Passive.94 Configuring the storage pool Completing the Node Selection pages 11 In the SMTP Server field. Perform this step if you want to configure a clustered storage pool. the storage pool authority node appears in the Storage Pool Node Addresses table on the Storage Pool Node Summary subpage. To complete the Storage Pool Node Summary page 1 (Conditional) Configure one or more nodes as passive nodes. In the Node Type pull-down menu. 12 Click Next. 2 Verify that the Storage Pool Node Addresses table on this page lists the addresses of each computer that you want to include in this storage pool correctly. Proceed to the following: See “Completing the Node Selection pages” on page 94. Click Ok. See “Completing the Add New Node subpage” on page 95. Proceed as follows: . Click Edit Node. PureDisk uses this SMTP server to event escalations by email. use these page to add additional nodes. Completing the Node Selection pages The Node Selection pages let you select the nodes for this storage pool. Completing the Storage Pool Node Summary subpage The following procedure explains how to complete the Storage Pool Node Summary page. type the FQDN of your site's mail server.

Use it as follows: ■ If you want to configure an unclustered storage pool. This pull-down menu appears only for clustered installations. During an initial configuration. If the table is incomplete. Proceed to the following: See “Completing the Edit Node subpage” on page 96. click Add Node. click Edit Node. In the Root Password field. (Conditional) On the Node Type pull-down menu. click Next. click Next. ■ . If you need to delete a node from the storage pool. ■ ■ ■ Completing the Add New Node subpage You can specify additional nodes for the storage pool on the Add Additional Node page. Proceed to the following: See “Completing the Storage Selection pages” on page 96. The Passive nodes are the failover nodes. The following procedure explains how to add nodes to the storage pool configuration. If the address for a node is incorrect. click Remove Node. To complete the Add New Node subpage 1 2 3 In the FQDN field. It is not possible to change the storage pool authority node's information from within the storage pool configuration wizard. Proceed to the following: See “Completing the Add New Node subpage” on page 95. and the address in the table is correct. For example.Configuring the storage pool Completing the Node Selection pages 95 ■ If the table is complete and correct. select Active for all nodes. type the FQDN of the node you want to add to the storage pool. If you want to configure a clustered storage pool. You cannot edit the information for the storage pool authority node. You can edit the information for nodes that are not storage pool authority nodes. you need to reinstall PDOS on this node. type the administrator's root password to computer that you want to add. if you want to configure a single-node. configure at least one Passive node. select Active or Passive. always configure the storage pool authority node as an Active node. all-in-one storage pool. If the address for the storage pool authority node is incorrect.

Proceed to the following: See “Completing the Storage Pool Node Summary subpage” on page 94. After installation. the storage pool configuration wizard might display each disk multiple times. ■ ■ The following procedures explain how use the wizard to complete the Storage Selection pages: ■ ■ See “Configuring disk groups” on page 97. or create additional volumes. you create storage volumes from the disk groups. You cannot edit the address of the storage pool authority node. To complete the Edit Node subpage 1 2 3 In the FQDN field type the FQDN of the node. If you performed a Onedisk PDOS installation. you create disk groups. nor can you edit the address of a cluster node that is in the Active state. Create storage volumes. In this situation. remove disk groups. remove volumes. Symantec . The following procedure explains how to edit a node's address. During a new installation. For each node you want to configure. Mount the file system on the volumes you created. Completing the Edit Node subpage You can edit a node's address on the Edit Node subpage. you need to perform the following tasks: ■ Create disk groups. or create additional disk groups. Click Ok. After installation.96 Configuring the storage pool Completing the Storage Selection pages 4 5 Click Ok. Proceed to the following: See “Completing the Storage Pool Node Summary subpage” on page 94. Completing the Storage Selection pages The Storage Selection pages let you configure the storage disks for the storage pool. During a new installation. you can edit disk groups. the storage pool configuration wizard does not display any storage selection pages for you to complete. you can edit volumes. If the disks attached to a node use multipathing. See “Configuring disk volumes and mount points” on page 98.

and mount points: ■ ■ ■ ■ See “Completing the Disk Group Summary subpage” on page 100. See “Completing the Volumes and Mount Points subpage” on page 102. See “Completing the Edit Disk Groups subpage” on page 101. To configure disk groups 1 2 3 On the Disk Group Summary subpage. see the following: See “About the Veritas Enterprise Administrator’s role in a PureDisk storage pool” on page 197. select one of the nodes in the storage pool. accept the default disk group name of PDDG or type a new name. VCS requires unique disk group names.Configuring the storage pool Completing the Storage Selection pages 97 recomends that you use the Veritas Enterprise Administrator (VEA) to manage the node's disks. Configuring disk groups The following procedure explains how to configure disk groups. Click Create Disk Group. you can use VEA to create disk groups and create disk volumes. You can use the storage pool configuration wizard for all other aspects of the storage pool configuration. . disk volumes. The following contain reference information that might be useful to you when you configure disk groups. See “Completing the Create New Disk Group subpage” on page 101. make sure to specify a unique name for each disk group. Note: If you want to configure high availability. On the Create New Disk Group subpage. in the Node name pull-down menu. For information about VEA. For example.

or Shared. If you want to include all disks. click the boxes in the first column to select the disks that you want to include in this disk group. Click OK in the confirmation pop-up window. If you need to configure disk groups for more nodes. specify a size or select Use maximum available size. The wizard detects your disks and displays available disks when you select Internal. ■ Configuring disk volumes and mount points The following procedure explains how to configure disk volumes and mount points. select either Internal. click Next on the Disk Group Summary subpage and proceed to the following: See “Configuring disk volumes and mount points” on page 98. External. 8 Proceed as follows: ■ If this is the last or only node you want to include in this storage pool. complete the following steps: ■ ■ Type a name for the disk volume. . The following table can help you decide which selection to make: Store pool type All-in-one node Internal DAS disk External Fibre channel or iSCSI disks Fibre channel or iSCSI disk that cannot be shared Shared Not applicable Multinode (unclustered) or clustered DAS disk that cannot be shared Disk that all storage pool nodes can access 5 In the Available Disks table. To configure disk volumes and mount points 1 2 On the Volumes and Mount Points subpage. in the Volume name field. In the Size field. or Shared. On the Create Volume subpage.98 Configuring the storage pool Completing the Storage Selection pages 4 In the Storage to be used pull-down menu. The wizard returns to the Disk Group Summary subpage. click in the left-most box in the header row. External. 6 7 Click Ok. return to step 1 and configure disk groups for another node in the storage pool. click Create Volume.

7 Proceed as follows: ■ If you want to configure a multinode storage pool or a clustered storage pool. Return to step 2 and complete this procedure again. You have configured the last of your storage for all nodes of a multinode storage pool or a clustered storage pool. On the File Systems and Mounts subpage. Click Next. select the directories that you want the wizard to mount on the disk volume. and you need to configure more disk volumes on other nodes. For nodes with iSCSI disks: See “(Conditional) Configuring an iSCSI environment” on page 75. Proceed to one of the following: ■ If you need to specify clustering options. The wizard returns to the Volumes and Mount Points subpage. ■ 6 Click Ok. perform the following steps: ■ ■ ■ ■ Click Back. all-in-one storage pool. 3 (Conditional) Select the volume you created in step 2. This action returns you to the Volumes and Mount Points subpage. 4 5 Click Mount Volume. Click OK in the confirmation pop-up window. Perform this step if the volume you created is not selected. proceed to the following: (Conditional) Completing the Cluster Option pages . Select another node. This action returns you to the Disk Group Summary page. ■ Click Next on the Volumes and Mount Points subpage if any of the following are true: ■ ■ ■ ■ This volume is the last disk volume you need to configure. You want to configure a single-node. Make sure you review the following information before you mount directories on your disk volumes: ■ For nodes with DAS/SAN disks: See “Planning the storage partitions (DAS/SAN disks)” on page 60.Configuring the storage pool Completing the Storage Selection pages 99 ■ ■ Click Ok. This volume is the only disk volume that you want to mount.

use the pull-down menu and select the correct node. If you need to delete a disk group. ■ 2 Choose an activity from this page. For example. click Create Disk Group. Proceed to the following: See “Completing the Edit Disk Groups subpage” on page 101. as follows: ■ If the FQDN displayed identifies the node you want to work on now. click the button to the left of the disk group that you want to change and click Edit Disk Group. proceed to the following: See “Completing the Services Configuration page” on page 106. proceed to the next step in this procedure.100 Configuring the storage pool Completing the Storage Selection pages ■ If you do not need to specify clustering options. ■ ■ ■ ■ See “Completing the Disk Group Summary subpage” on page 100. Proceed to the following: See “Completing the Volumes and Mount Points subpage” on page 102. If you need to create a disk group for this node. as follows: ■ If the Disks and Volumes Defined table includes all the information for this node's disk groups. Reference information for the Storage Selection subpages The following sections explain how to complete the Storage Selection subpages. configure one or more disk groups. Proceed to the following: See “Completing the Create New Disk Group subpage” on page 101. To complete the Disk Group Summary subpage 1 Verify that address that the Node name field displays is correct. If the FQDN displayed does not identify the node you want to work on now. The following procedure explains how to complete the Disk Group Summary page. If you need to change a disk group.x See “Completing the Edit Disk Groups subpage” on page 101. click the button to the left of the disk group that you want to delete and click Remove Disk Group.x See “Completing the Create New Disk Group subpage” on page 101. click Next. Completing the Disk Group Summary subpage For each node that you want to include in your storage pool. click Create Disk Group if you need to define a disk group for this node during a new installation.x See “Completing the Volumes and Mount Points subpage” on page 102. ■ ■ ■ .

as follows: . To create a disk volume from one or more disks. click the boxes that identify the disks you want to use. 3 In the Available Disks table. For example. For an all-in-one storage pool with an external disk. To complete the Edit Disk Groups subpage 1 In the Available Disks table. ■ ■ PureDisk detects the disks for this node and displays the storage that is attached to the node. In the Storage to be used pull-down menu. To complete the Create New Disk Group subpage 1 2 In the Disk Group Name field. External if you want to configure storage on a disk that is attached externally and is exclusive to this computer. Shared if you want to configure storage on a disk that is attached to this computer and is attached to at least one other computer. select External if you want to configure an all-in-one storage pool with an external disk. No other computers can connect to this disk. Completing the Edit Disk Groups subpage The following procedure explains how to complete the Edit Disk Groups subpage. click the box to the left of the disk names. click the box in the first row to the left of Available disks. click the boxes that identify the disks you want to use. do not select Shared. accept the default name of PDDG or type a name for the disk group. select one of the following: ■ Internal if you want to configure storage on a disk that is inside this computer. Symantec recommends that you do not configure storage on an internal disk for production use. ■ 4 5 Click Ok.Configuring the storage pool Completing the Storage Selection pages 101 Completing the Create New Disk Group subpage The following procedure explains how to complete the Create New Disk Group page. Proceed to the following: See “Completing the Disk Group Summary subpage” on page 100. as follows: ■ To create a disk volume from all available disks.

102

Configuring the storage pool Completing the Storage Selection pages

To create a disk volume from all available disks, click the box in the first row to the left of Available disks. To create a disk volume from one or more disks, click the box to the left of the disk names.

2 3

Click Ok. Proceed to the following: See “Completing the Disk Group Summary subpage” on page 100.

Completing the Volumes and Mount Points subpage
The storage pool configuration wizard detects the disk types you configured and presents the file system types needed for your disks. If your disks support a VxFS file system, the wizard creates a VxFS file system on the disks. If your disks do not support VxFS, the wizard creates an XFS file system. For example, VxFS does not support iSCSI disk devices. The compatibility list at the following Web site explains the disk devices that VxFS supports:
http://www.symantec.com/business/support/compatibility.jsp?language=english&view=comp& pid=52672

The Volumes and Mount Points subpage enables you to create disk volumes that consist of existing disk groups. The following procedure explains how to complete the Volumes and Mount Points subpage. Your goal is to create disk volumes and then to create mount points for the disk volumes. To complete the Volumes and Mount Points subpage

Examine the Volumes and Mount Points table on this page. Your goal is to create disk volumes from the disk groups you created in the previous steps. Proceed as follows:

If this page does not display a table, or if the table is incomplete, you need to create volumes. Click Create Volume. For information about how to complete the Create Volume subpage, see the following: See “Completing the Create Volume subpage” on page 103. If you have configured all the volumes you need, the table displays each volume's name and each volume's size. At this time you need to mount the volumes, as follows:

Configuring the storage pool Completing the Storage Selection pages

103

Select each row that displays a volume name and a volume size, and then click Mount Volume. Perform this step for each row, until all rows display a mount point in the Mount Point column. The disk partition specifications are case sensitive. If you type your own partition names, always use an uppercase S for Storage. Symantec recommends that you create your own, customized partitions only under the direction of a technical support staff member. Click Next and proceed to the following:

If you need to specify clustering options, proceed to the following: (Conditional) Completing the Cluster Option pages If you do not need to specify clustering options, proceed to the following: See “Completing the Services Configuration page” on page 106.

If each row in the table displays a volume name, a size, and a mount point, then the table is complete. Click Next. Proceed to the following:

If you need to specify clustering options, proceed to the following: (Conditional) Completing the Cluster Option pages If you do not need to specify clustering options, proceed to the following: See “Completing the Services Configuration page” on page 106.

If you need to specify an increased size for a volume, click Edit Volume. If you need to decrease the size of a volume or change a volume's name, you need to remove the volume and recreate it. Proceed to the following: See “Completing the Edit Volume subpage” on page 104. If you need to delete a volume, click Remove Volume.

Completing the Create Volume subpage
The storage pool configuration wizard enables you to create new disk volumes, as follows:

If there is only one disk in a new disk group, and you click Create Volume, PureDisk creates the new volume as a concatenated volume. If there are two or more disks in a new disk group, and you click Create Volume, PureDisk creates the new volume as a striped volume.

The following procedure explains how to complete the Create Volume subpage.

104

Configuring the storage pool Completing the Storage Selection pages

To complete the Create Volume subpage

1 2 3 4

Type a name into the Volume name field. In the Size field, specify a fixed size or select Use maximum available size. Click Ok. Proceed to the following: See “Completing the Volumes and Mount Points subpage” on page 102.

Completing the Edit Volume subpage
The Edit Volume subpage enables you to specify a larger value for a disk volume. If you need to change the name of a volume or if you need to decrease the size of a volume, remove the volume and respecify the volume. The following procedure explains how to complete the Edit Volume subpage. To complete the Edit Volume subpage

1 2 3

In the Size field, specify a larger size for the volume or click Use maximum available size. Click Ok. Proceed to the following: See “Completing the Volumes and Mount Points subpage” on page 102.

Completing the File Systems and Mount Points subpage
The following procedure explains how to complete the File Systems and Mount Points subpage. To complete the File Systems and Mount Points subpage

1

Choose the directory that you want to mount on this disk volume. On the File Systems and Mounts subpage, select the directories that you want the wizard to mount on the disk volume. Make sure you review the following information before you mount directories on your disk volumes:

For nodes with DAS/SAN disks: See “Planning the storage partitions (DAS/SAN disks)” on page 60. For nodes with iSCSI disks: See “(Conditional) Configuring an iSCSI environment” on page 75.

The disk partition specifications are case sensitive. If you type your own partition names, always use an uppercase S for Storage. Symantec

Configuring the storage pool (Conditional) Completing the Cluster Option pages

105

recommends that you create your own, customized partitions only under the direction of a technical support staff member.

2

Click Ok.

(Conditional) Completing the Cluster Option pages
If you specified that you wanted to configure an unclustered storage pool on the Welcome page, the storage pool configuration wizard does not display the cluster option pages.

Completing the Cluster Details subpage
The following procedure explains how to complete the Cluster Details subpage. To complete the Cluster Details subpage

1

In the Cluster Name field, specify a unique name for this cluster. This name must be unique on your enterprise network. Do not include spaces, underscore characters (_), or numbers in this name.

2

In the Cluster ID field, specify a unique identification number for this cluster. This cluster ID number must be unique to this cluster on your enterprise network. In the Admin Name field, specify the name you want to use as the login name for the VERITAS Cluster Manager Java Console. In the Password field, specify the password you want to for the VERITAS Cluster Manager Java Console. In the Confirm Password field, retype the password that you typed into the Password field. Click Next.

3 4 5 6

Completing the Cluster Heartbeat Configuration subpage
The following procedure explains how to complete the Cluster Heartbeat Configuration subpage. The storage pool configuration wizard detects the NICs in each node and presents the NICs to you in pull-down menus. Your goal is to specify the NICs that you want to use for the cluster's private heartbeats. If you have not examined your NICs yet, perform the procedure in the following now: See “(Conditional) Preparing to configure a clustered PureDisk storage pool” on page 71.

The NetBackup export engine is optional. Configure one of these per storage pool. When your specifications are complete in the table. configure only one service of each type on a node. For the other services.106 Configuring the storage pool Completing the Services Configuration page To complete the Cluster Heartbeat Configuration subpage 1 Use the pull-down menus in the table's Heartbeat I and Heartbeat II columns to specify the NICs you want to use for the cluster's primary and secondary heartbeats. You cannot use the Services Configuration page to move the storage pool authority to a different node. See “Completing the Services Configuration page for a clustered storage pool” on page 107. ■ ■ ■ ■ The Services Configuration page differs depending on whether you specified high availability. You might have content routers with different amounts of storage. The services you can configure in a storage pool are as follows: ■ Storage pool authority (spa). For more information. Metabase server (mbs). The following procedures explain each of these pages: ■ See “Completing the Services Configuration page for an unclustered storage pool” on page 107. Configure at least one of these per storage pool if you want to export file data from this storage pool to a NetBackup environment. (Optional) NetBackup export engine (nbu). Note: PureDisk assumes that all content routers have the same storage size. Content router (cr). Use the administrator Web UI to define the different sizes after you exit the storage pool configuration wizard and before you run any backups. Completing the Services Configuration page The Services Configuration page lets you specify the PureDisk services that you want to install on each storage pool node. 2 Click Next. Configure at least one of these per storage pool. Configure only one storage pool authority and one metabase server in a storage pool. ■ . The storage pool configuration wizard automatically detects the storage pool authority node. Metabase engine (mbe). Configure at least one of these per storage pool. see the PureDisk Administrator's Guide. proceed to the next step. Configure one of these per storage pool.

the service FQDN of that storage pool authority service moves to another node. The service FQDN is the FQDN associated with the services on the node. For each node. if you install only a storage pool authority on one node. return to step 1 and configure services for another node. the service FQDN is the address of that storage pool authority. 2 3 4 5 Click Configure Now (for a new configuration on a new node) or Change (for a reconfiguration). proceed to the following: See “Completing the Root Broker Configuration page” on page 108. For example. The following procedure explains how to complete the Services Configuration page for a clustered storage pool. Proceed as follows: ■ If the Nodes and Services table is complete. ■ Completing the Services Configuration page for a clustered storage pool On a clustered storage pool. Select the services that you want to configure on this node. To complete the Services Configuration page for an unclustered storage pool 1 Click in the left-most column of the Nodes and Services table. Click Next. By now. you need the following two types of node addresses: ■ The node FQDN is the FQDN associated with the node hardware. . ■ In the Nodes and Services table. the Nodes and Services table on the Services Configuration page is prepopulated with the FQDN associated with the node hardware. For example. you should have received this FQDN from your network administrator. If you need to configure services on another node. During a failover. This action selects a node. this is the FQDN you use to log into a node and run PDOS commands. note that you do not have to complete the columns Service FQDN/IP or Netmask for passive nodes.Configuring the storage pool Completing the Services Configuration page 107 Completing the Services Configuration page for an unclustered storage pool The following procedure explains how to complete the Services Configuration page for an unclustered storage pool.

if your node name is acme2. Select a NIC other than the default if you want to have the service IP on a different public interface than the one specified during the PDOS installation. use the pull-down menu to select the NIC that you want to use for PureDisk communication. see the PureDisk Getting Started Guide. specify a service FQDN for the services you want to reside on this node. 4 Under the Services column.108 Configuring the storage pool Completing the Root Broker Configuration page To complete the Services Configuration page for a clustered storage pool 1 Complete the Service FQDN/IP column for each row in the Nodes and Services table. 3 In the Network Interface column.com.beep. you can specify the same netmask you specified for the node during the PDOS installation. click Change (for a reconfiguration) or Configure Now (for a new configuration) to specify the services that you want to configure on each node. When the Nodes and Services table is complete. The Symantec Product Authentication Service requires that you install one (and only one) root broker on your enterprise network and that each software product on the network communicate with that root broker through its own authentication broker. 5 6 7 Completing the Root Broker Configuration page PureDisk requires that each storage pool use the Symantec Product Authentication Service to authenticate users and provide a single sign on for Web UI use. you can specify acme2s.com for this node's service address. For example. For each node. Specify the netmask for the service address on this node. Select the services that you want to configure on this node. Note: In order to perform disaster recovery backups and restores. Obtain this FQDN from your network administrator. click Next. Proceed as follows: See “Completing the Root Broker Configuration page” on page 108. . you must specify an FQDN in this column for each node. For an overview of the Symantec Product Authentication Service. In most cases.beep. 2 Complete the Netmask column for each row in the Nodes and Services table.

To complete the Root Broker Configuration page 1 (Conditional) Prepare your storage pool to use a remote root broker or an external root broker. Make sure that you performed the procedures in the following: See “(Conditional) Preparing a remote root broker or an external root broker” on page 66. If you choose to configure a remote or external root broker. The following procedure explains how to complete the Root Broker Configuration page. Perform this step if you want to configure a remote root broker or an external root broker. you can configure this storage pool to use a root broker installed on another Symantec product. contact Symantec Technical support. the storage pool configuration wizard installs an authentication broker on this storage pool. and you need to prepare the other systems to let this storage pool use their root broker. supply the information requested. You need to gather information about the brokers. ■ ■ If you need to reconfigure your specified root broker after the storage pool is installed and configured. 3 Click Next. 2 Select one of the brokers on the Root Broker Configuration page. For example. To configure authentication in this way. you can specify the root broker and authentication broker for this storage pool. You can configure this storage pool to use a remote root broker on another storage pool. the storage pool configuration wizard installs an authentication broker on this storage pool. Proceed to the following: See “Completing the Selection Summary page” on page 110. choose Configure this storage pool to use a remote root broker on another PureDisk storage pool. choose Configure a local root broker on this storage pool authority. To configure authentication in this way. You can configure this storage pool to use root broker that is external to any other PureDisk storage pools. If you select a remote root broker. If you select an external root broker.Configuring the storage pool Completing the Root Broker Configuration page 109 On the Root Broker Configuration page. . as follows: ■ You can install a local root broker and an authentication broker on this storage pool.

Proceed as follows: ■ If the Selection Summary page appears correct. To complete the Selection Summary page 1 2 Visually inspect the Selection Summary page. If the Selection Summary page appears incorrect. click Back and correct the configuration. . click Finish. To complete the Implementation page ◆ After the configuration completes. ■ Completing the Implementation page The following procedure explains how to complete the Implementation page.110 Configuring the storage pool Completing the Selection Summary page Completing the Selection Summary page The following procedure explains how to complete the Selection Summary page. click Next and proceed to the following: See “Completing the Implementation page” on page 110.

ini . To complete the storage pool installation 1 Copy the topology files to a safe place outside the PureDisk storage pool. The topology files are as follows: ■ /opt/pdinstall/topology.Chapter 7 Completing the installation This chapter includes the following topics: ■ ■ Completing the storage pool installation (Conditional) Installing the Veritas Cluster Manager Java Console Completing the storage pool installation The following procedure lists these tasks you need to perform to complete the storage pool installation. You need the topology information if you ever need to recovery from a disaster.

Remember the password that you type. The utility prompts you to specify. you cannot complete the restore. You can use this password to restore PureDisk storage pool authority configuration files in the event of a disaster. NetBackup provides its own encryption mechanism. Do not type this command if you plan to back up your storage pool to NetBackup. a password for the encryption utility to use during disaster recovery backups and restores. The xinetd daemon affects only the subsequent NetBackup clients that you installed on this PureDisk node. remember it so you can provide it at restore time The pdkeyutil command initiates a dialog session with the pdkeyutil utility. If you run the chkconfig(8) command and you do not install a NetBackup client before you reboot. However. see the following manual: See the PureDisk Administrator’s Guide. 3 (Conditional) Type the following chkconfig(8) command on the storage pool authority node to start the xinetd daemon by default after a reboot: # chkconfig -s xinetd on Perform this step if you intend to install a NetBackup client on this node.nodes. if you provide a key. Enable this daemon if you plan to install a NetBackup client on this node before the next reboot. You can ignore the message. 4 (Conditional) Open the correct ports. TIP: You can remember the topology file’s encryption password and the pdkeyutil command’s password more easily if you make them identical. if you do not remember this password.ini 2 (Optional) Type the following command on the storage pool authority node to configure disaster recovery encryption: # /opt/pdag/bin/pdkeyutil -insert Type this command if you plan to back up your storage pool to a local file system or to a Samba shared file system.112 Completing the installation Completing the storage pool installation ■ /opt/pdinstall/topology. The xinetd daemon is necessary for NetBackup client operations. For more information on disaster recovery backups and disaster recovery restores. so pdkeyutil is not needed. the system issues a message about xinetd failing. Your decision to run the chkconfig(8) command has no effect on PureDisk operations. . However.

0. 7 Distribute and install PureDisk agent software and/or the PureDisk deduplication option (PDDO) plug-in. see the following topic: See “About external directory service authentication” on page 152.udp. For worksheet copies. These two types of PureDisk agents are as follows: . If you want to use PureDisk’s internal OpenLDAP database. Use these worksheets for unclustered storage pools only. After the storage pool installation finishes.temp. Perform this step if you installed an unclustered storage pool. The installation worksheets provide a place for you to record information about your storage pools that can be used in the event of a disaster.0. you do not need to configure external directory service authentication. From an external Active Directory service.Completing the installation Completing the storage pool installation 113 Perform this step if you configured iSCSI disks. From an external OpenLDAP directory service.0/0 3216 5 (Conditional) Complete the installation worksheets. Search for the following line: # protocol (tcp. Perform this procedure if you want to link an existing OpenLDAP directory service to PureDisk’s internal OpenLDAP directory service. PureDisk can authenticate users in the following ways: ■ From its own internal OpenLDAP database. Use a text editor to open file /etc/custom_iptables_rules. perform the following steps: ■ ■ ■ Log into the node that hosts the storage pool authority as root. ■ ■ For information about external directory service authentication. see the following: See “About the installation worksheets” on page 143.all) source[/mask] ■ Add the following line under the # protocol line: tcp 0. 6 (Optional) Configure external directory service authentication. This is the default.

■ TIP: If you want to install a PDDO plug-in on a NetBackup media server. Type the following command to set the current date and time: # date -s "day month year hours:minutes:seconds" For example.sh If you plan to replicate to this storage pool from a PureDisk 6. see the following manual: See the PureDisk Deduplication Option Guide. type the command as follows: # date -s "3 AUG 2010 00:00:00" . run some backups to see if all the system is configured properly. see the following manual: See the PureDisk Client Installation Guide. The PDDO plug-in enables you to use the PureDisk storage pool as a NetBackup OpenStorage unit. For more information. run this security protocol script only after the source storage pool has been upgraded to PureDisk 6. Symantec recommends that you run the following script on the storage pool authority node: # /opt/pdinstall/disable_sslv2. 10 (Conditional) Set the storage pool time. Then.114 Completing the installation Completing the storage pool installation ■ The PureDisk agent software enables the storage pool to communicate with a client that you want to back up. Symantec recommends that you install a regular PureDisk client on the media server first.x storage pool. Perform the following steps if you did not specify an NTP server during your session with the storage pool configuration wizard: ■ ■ Log into the storage pool authority node as root. After the configuration is known to be correct. 9 (Conditional) Install the Veritas cluster server manager Java console on a Windows client. For more information. For more information. Perform this step if you enabled high availability. 8 (Recommended) Run the script that upgrades the security protocol. remove the regular PureDisk client. see the following: See “(Conditional) Installing the Veritas Cluster Manager Java Console” on page 115. and install the PDDO plug-in on the media server.6.5.

Use the procedure in the following topic: See “Installing the Cluster Manager Java Console administrator software” on page 117. and troubleshoot. 2 Add an administrator account on each node in the cluster that can connect to the console. (Conditional) Installing the Veritas Cluster Manager Java Console Perform the procedures in this topic if you configured highly available PureDisk. proceed to the following: See “Installing a Cluster Manager Java Console Linux client” on page 115. for Linux. For information about this console. . version 4. For Windows platforms. For example. The Cluster Manager Java Console is graphical user interface that enables you to monitor a clustered PureDisk storage pool from an administration console on a Linux or Windows platform. perform an intentional failover. proceed to the following: See “Installing a Cluster Manager Java Console Windows client” on page 116. To install the Cluster Manager Java Console 1 Perform one of the following procedures to install the client software: ■ For Linux platforms. Installing a Cluster Manager Java Console Linux client The following procedure explains how to install the Cluster Manager Java Console client on a Linux machine.Completing the installation (Conditional) Installing the Veritas Cluster Manager Java Console 115 This command sets the date and is boot persistent. see the following manual: See the Veritas Cluster Server User’s Guide.1. run commands. you can use this interface to administer resources. see the following manuals: See the PureDisk Getting Started Guide. ■ For information about client hardware requirements.

2 3 Put the PureDisk 6. Perform this step if the operating system did not move you to this directory automatically.6 DVD into a drive on the system.rpm 6 Proceed to the following topic: See “Installing the Cluster Manager Java Console administrator software” on page 117.noarch.4. Installing a Cluster Manager Java Console Windows client The following procedure explains how to install the Cluster Manager Java Console client on a Windows machine. For example. do not install the Java console on a PureDisk node. PDOS does not support graphical user interfaces. To install the Cluster Manager Java Console on a Windows platform 1 2 3 Insert the PureDisk 6. Change to the following directory: \windows\WindowsInstallers\WindowClusterManager\EN 4 Double-click setup. Type the following command: # cd /cdrom/cluster_server/rpms 5 Type the following command to install the software: # rpm -i VRTScscm-4.30.6 DVD into a drive the system. Use Windows Explorer to select the disk drive. .00-MP3_GENERIC.116 Completing the installation (Conditional) Installing the Veritas Cluster Manager Java Console To install the Cluster Manager Java Console on a Linux platform 1 Choose a Linux client that supports a graphical user interface. Type the following command to mount the disk: # mount -o ro /dev/cdrom /mnt 4 (Conditional) Change to the software directory.exe.

. To add a cluster administrator 1 Log into one of the cluster nodes as root. 2 Type the following command to make the VCS configuration writable: # /opt/VRTSvcs/bin/haconf -makerw 3 Type the following command to add the administrator: # /opt/VRTSvcs/bin/hauser -add username -priv Administrator For username. Perform this procedure once on each active node and once on each passive node. Installing the Cluster Manager Java Console administrator software The following procedure explains how to install the Cluster Manager Java Console administrator software on one of the cluster nodes. 4 5 Type a password when the system prompts you for a password. Type the following command to reset the configuration to read only: # /opt/VRTSvcs/bin/haconf -dump -makero 6 (Conditional) Log into another node and perform this procedure on that node. specify an administrator account name of your choosing. Proceed to the following topic: See “Installing the Cluster Manager Java Console administrator software” on page 117.Completing the installation (Conditional) Installing the Veritas Cluster Manager Java Console 117 5 6 Use the installation wizard to install the software. Perform this step if you have more nodes in your storage pool. Make sure to perform this procedure on all active and all passive nodes in the clustered storage pool.

118 Completing the installation (Conditional) Installing the Veritas Cluster Manager Java Console .

6 Upgrading the storage pool software to PureDisk 6.Chapter 8 Upgrading PureDisk software This chapter includes the following topics: ■ ■ ■ ■ ■ ■ About upgrading to PureDisk 6.6 release. . Do not use the instructions in this topic to install the PureDisk software for the first time. start with the information in the following topic: See “About PureDisk operating system (PDOS) installations” on page 25.6 Upgrading PureDisk agent software on clients Troubleshooting and notes About upgrading to PureDisk 6. See “Upgrade effects” on page 120.6 Verifying the environment Upgrading the operating system software to PDOS 6. See “Performing an upgrade” on page 122.6 upgrade path” on page 120. The following describe topics that pertain to the upgrade process: ■ ■ ■ ■ See “The PureDisk 6.6 This topic describes how to upgrade your PureDisk environment to the PureDisk 6. See “Prioritizing storage pool upgrades” on page 121. For information about how to perform an initial installation.

Depending on how much data PureDisk needs to convert to the new storage layout. This activity takes longer if you have many clients. ■ If your storage pool is not running these minimum software levels. You need to upgrade PDOS to PDOS 6. to upgrade each agent’s software.6 software release includes the following upgrades: ■ An upgrade for PDOS. PureDisk 6. the conversion might take a couple of days.6 upgrade path The PureDisk 6.6 before you upgrade the PureDisk storage pool software. more or less simultaneously. For the PureDisk operating system (PDOS).120 Upgrading PureDisk software About upgrading to PureDisk 6. you can upgrade agents through the Web ■ ■ ■ ■ . the upgrade software can start an agent upgrade job for each client. The upgrade software restarts the content routers. For those nodes. The storage pool is converted to the new storage pool layout scheme implemented in PureDisk 6. each PureDisk node needs to be running PDOS 6. If you decline. the agents reconnect to the storage pool. ■ Your storage pool needs to be running the following minimum levels of software to use the PureDisk 6.5 running on it at any time. The PureDisk 6.5 or later. your storage pool needs to be running PureDisk 6.6 upgrade software checks for data that is still stored in the old storage layout scheme.6 upgrade procedures: ■ For the PureDisk server and the agent application. Next.5 documentation for the instructions that explain how to upgrade to 6. the PureDisk 6.5. If you upgrade a storage pool that had a release earlier than PureDisk 6. Upgrade effects The upgrade has the following effects: ■ Your system and the Web UI can be noticeably slower immediately after you install this upgrade. The upgrade software prompts you to confirm whether or not you want to run the agent upgrade job.5 included a new storage layout scheme. This action reloads the fingerprint cache. Optionally. The upgrade software restarts the services on the metabase engines. contact Symantec technical support.5 and PureDisk 6. please see the PureDisk 6. This situation is temporary.6.6 ■ See “Troubleshooting and notes” on page 138. An upgrade for the PureDisk storage pool software.5 or later.

this activity can degrade network traffic. plan to upgrade the target (destination) storage pool first. . While PureDisk upgrades an agent. If you allow PureDisk to upgrade the agents automatically at upgrade time. the agent is too busy to respond to other actions. Typically. ■ In the PureDisk 6. Replication requires that either both storage pools be at the same release level or that the destination storage pool be at the higher release level.6 does not support these features.5.6 software on the new nodes. which is new in the PureDisk 6. PureDisk 6. Prioritizing storage pool upgrades If you have more than one storage pool at your site. The message text reports that PureDisk cannot forward messages to the agent. Script-based failover. The upgrade software removes all functionality that is related to the following PureDisk 6. see the following: See “About PureDisk operating system (PDOS) installations” on page 25. PureDisk uses this password to encrypt the topology files. any jobs that finished on a 6.6 121 UI after the upgrade finishes. The source storage pool can be at the release level of the previous major release.6 on 64-bit hardware. you can use this password to log onto the storage pool configuration wizard and make changes to your configuration.6 release. To install the PDOS 6. At the end of the upgrade.5 features: ■ ■ ■ ■ The CIFS interface. This behavior is normal because during an upgrade.5 system with a failed job status or with a success with errors job status appear in the new administrator Web UI as 0% complete. if you want to add nodes to this environment at a later time. After the upgrade is complete. PureDisk issues an error message.Upgrading PureDisk software About upgrading to PureDisk 6. the automatic upgrade jobs start within 15 minutes of the upgrade. The job starts even if you defined backup windows such that PureDisk does not access the client at this time. ■ After you upgrade. plan the order for your storage pool upgrades.6 administrator Web UI. install PDOS 6. If you implemented replication. if you click Monitor > Jobs. In addition. PureDisk prompts you to create a password for the storage pool configuration wizard.1 or 6. If you try to do so. you cannot define a new data selection for that agent. The following features affect the upgrade order: ■ Replication.

122

Upgrading PureDisk software About upgrading to PureDisk 6.6

Symantec supports replication between a source storage pool at the PureDisk 6.5.x release level and a destination storage pool at the PureDisk 6.6 release level. Symantec recommends that you upgrade all storage pools to PureDisk 6.6 as quickly as possible.

Storage pool authority replication (SPAR). If you implemented SPAR, plan to upgrade the source storage pool first. SPAR requires that either both storage pools be at the same release level or that the source storage pool be at the higher release level. The target (destination) storage pool can be at a lower release level. The order is as follows:

First, upgrade the storage pool from which you replicate the storage pool authority. This is the source storage pool.

Second, upgrade the storage pool to which you replicate the storage pool authority. This is the target (destination) storage pool. For example, assume that your environment includes storage pool A and storage pool B. You have a policy that replicates the storage pool authority of storage pool A to storage pool B. In this case, you must first upgrade storage pool A and then you can upgrade B. If you upgrade the storage pools in an incorrect order, SPAR breaks. In this case, contact Symantec technical support.
■ ■

Replication and SPAR enabled simultaneously. If you have two storage pools, and you enabled both replication and SPAR, you need to upgrade both storage pools in order for these replications to keep working. Because the upgrade order is different for these two types of replication (see previous bullets in this list), you need to decide which replication to disable during the upgrade. For example, you can disable SPAR during the upgrade. In this case, remember to re-enable SPAR after the upgrade. The PureDisk 6.6 upgrade procedure includes an optional step to run a script that upgrades the security protocol. Run this script on the storage pool authority node after the following actions have completed:
■ ■

The PureDisk storage pool upgrade has finished. All clients that are connected to this storage pool have been upgraded, either manually or automatically. All replication from source storage pools that are at a PureDisk level lower than 6.6 have replicated to this storage pool, and the source storage pools have been upgraded to PureDisk 6.6.

Performing an upgrade
The following procedure explains the major steps in the upgrade process.

Upgrading PureDisk software Verifying the environment

123

To upgrade PureDisk

1

Verify your environment. Perform the following procedure: See “Verifying the environment” on page 123.

2

Upgrade the operating system software. Perform the following procedure: See “Upgrading the operating system software to PDOS 6.6” on page 125.

3

Upgrade the storage pool software. Perform the following procedure: See “Upgrading the storage pool software to PureDisk 6.6” on page 129.

4

Upgrade the agent software on each client. Perform the following procedure: See “Upgrading PureDisk agent software on clients” on page 134.

Verifying the environment
The following procedure explains how to verify your current PureDisk environment. Upgrade paths differ depending on your current environment.

124

Upgrading PureDisk software Verifying the environment

To verify your environment

1

(Conditional) Determine which storage pool you need to upgrade first, second, third, and so on. Perform this step if you have more than one storage pool, and you want to upgrade all of them to Puredisk 6.6. For information about prioritization, see the following topic: See “Prioritizing storage pool upgrades” on page 121.

2

Run a disaster recovery backup according to the procedure in the following manual: See the PureDisk Administrator’s Guide. Use your current release’s version of the preceding manual. When you run a disaster recovery backup, you ensure that you can recover your PureDisk environment if something goes wrong during the upgrade. This backup preserves the PureDisk databases. If you have to restore your environment, use this backup to restore your storage pool to the PureDisk 6.5 release. You cannot use a PureDisk 6.5.x disaster recovery backup to restore a PureDisk 6.6 storage pool.

3 4 5 6

Log off from the PureDisk Web UI. Close all browser interfaces. Log onto the storage pool authority node as root. Type the following command to verify the PDOS level on the storage pool authority:
# cat /etc/pdos-release

For example, the following output shows that this node is running PDOS 6.5.0.393:
6.5.0.393

Proceed as follows depending on the PDOS level you are running:

If the storage pool authority runs a PDOS release that is earlier than 6.5, the cat(1) command returns a release level in the following format:
6.2.0.13 6.1.0.7 6.0.2.4

Upgrading PureDisk software Upgrading the operating system software to PDOS 6.6

125

If this is the case, you cannot upgrade to 6.6 at this time. You need to upgrade to PDOS 6.5 first. For information about how to upgrade this node to PDOS 6.5, see the PureDisk 6.5 documentation.

If the storage pool authority runs PDOS 6.5 or later, the cat(1) command returns a release level in the following format:
6.5.0.393

If this is the case, you can upgrade to 6.6 at this time. Proceed to the next step in this procedure.

7

Verify whether your storage pool uses any EMC Clariion CxX00 arrays in combination with the EMC PowerPath software. The Veritas VxVM volume manager that is part of PureDisk 6.5 is not compatible with EMC PowerPath software. If you use EMC PowerPath software, complete the following steps to disable VxVM:
■ ■

Log on to the node as root. Run the following command:
# insserv -r boot.vxvm

Reboot the node.

If you add new nodes to an upgraded storage pool at a future date, make sure to disable VxVM on those new nodes, too. You cannot add storage to these nodes and use VxVM.

8

Proceed to the following topic: See “Upgrading the operating system software to PDOS 6.6” on page 125.

Upgrading the operating system software to PDOS 6.6
Use the following procedure to upgrade each node’s PDOS software to PDOS 6.6: To upgrade the operating system software

1

(Conditional) Add new license keys. See “(Conditional) Adding new license keys” on page 126.

2

Start the PDOS upgrade. See “Starting the PDOS upgrade” on page 126.

126

Upgrading PureDisk software Upgrading the operating system software to PDOS 6.6

3

Perform the PDOS upgrade. See “Performing the PDOS upgrade” on page 128.

4

Complete the PDOS upgrade. See “Completing the PDOS upgrade” on page 128.

5

Proceed to the following topic: See “Initiating the storage pool software upgrade” on page 130.

(Conditional) Adding new license keys
Perform this procedure if your Symantec sales representative gave you new license keys. Some PureDisk features require additional license keys. Use the following procedure to add the new license keys at this time. To add new license keys

1 2

Log into the storage pool authority node as root. Type the following command to launch the topology editor:
# /opt/pdinstall/edit_topology.sh

3 4 5 6 7 8 9

Select 9 Manage license keys and select OK. Select 2 Add license key and select OK. On the Add License Key screen, type the license key exactly as it is written and click OK. Select Back. Select 10 Save topology and select OK. Select 11 Quit and select OK. Respond to the prompts regarding topology file encryption.

10 Proceed to the following topic:
See “Starting the PDOS upgrade” on page 126.

Starting the PDOS upgrade
The following procedure explains the preliminary steps to perform when you upgrade a node to PDOS 6.6.

You might have added nonstandard kernel modules to PDOS 6. then repeat this procedure to upgrade other nodes.5. 3 4 Put the PureDisk software disk into a drive that is capable of reading a DVD. Note: The PDOS upgrade process upgrades the kernel. Upgrade the storage pool authority node first. do not attempt to modify disk partitions during any phase of the upgrade process. Type the following commands to mount the PureDisk software DVD and prepare the storage pool authority node for an upgrade: # mkdir /cdrom # mount /dev/cdrom /cdrom # sh /cdrom/scripts/prepareupgrade. An administrator might have added nonstandard kernel modules to this node. and store these modules in a safe place on another server. Contact Symantec technical support if you need help with this activity. determine if it includes any additional.sh 5 Type the following command to reboot the system: # reboot 6 Proceed to the following topic: See “Performing the PDOS upgrade” on page 128. 2 Examine your node software. nonstandard kernel modules.Upgrading PureDisk software Upgrading the operating system software to PDOS 6.6 node software before you can access your disks or /Storage. If you did.6 system. You can modify disk partitions only after the PDOS upgrade and storage pool upgrade are complete. This procedure includes a step to add these modules back to your PDOS 6. To start the PDOS upgrade 1 Log into the storage pool authority or log into the node that you want to upgrade. you probably need to add these modules to the PDOS 6. nonstandard kernel modules might be needed to facilitate access to disks or to /Storage. For example.6 127 Note: If the storage pool uses the VxVM volume manager. .

On the Installation Settings screen. I Agree . 13 Wait for the system to finish booting. To perform the PDOS upgrade 1 2 3 4 5 6 7 8 On the PDOS opening screen. and select Next. On the Installation Mode screen. select Next. use the arrow keys to select OS_Upgrade and press Enter... 10 On the Test Internet Connection screen. verify the display and select Accept. The system can appear to stall for several minutes at various points in the reboot process. This Test and select Next. Wait while the system installs new software and reboots. On the Select for Update screen. On the License Agreement screen. Skip 11 On the Release Notes screen. Eventually the system returns you to the PDOS opening screen. On the Confirm Update screen. use the arrow keys to select SUSE Linux Enterprise Server 10 SP2 and press Enter. Allow the system to reboot itself from the hard disk.6 Performing the PDOS upgrade The following procedure explains how to upgrade PDOS. select No. . On the Language screen. select Yes. observe that the partition for the / (root) directory is selected and select Next. page. 9 On the PDOS opening screen. in the Select: pane. 14 Proceed to the following topic: See “Completing the PDOS upgrade” on page 128.128 Upgrading PureDisk software Upgrading the operating system software to PDOS 6. deselect Clone this system for Autoyast and select Finish. 12 On the Installation Completed screen. select English(US) and select Next. Completing the PDOS upgrade The following procedure explains how to complete the PDOS upgrade. select Update and select Next. select Start Update.

6 During the storage pool software upgrade. See “Finishing the upgrade” on page 132. proceed to the following: See “Upgrading the storage pool software to PureDisk 6.sh 3 Type the following command to reboot the system: # reboot 4 (Conditional) Reinstall additional. proceed to the following: See “Upgrading the operating system software to PDOS 6. The following procedure explains the storage pool upgrade process. kernel modules. See “Initiating the storage pool software upgrade” on page 130. . You can add disks and restart the upgrade. ■ Upgrading the storage pool software to PureDisk 6.6” on page 129. see the following: See “Starting the PDOS upgrade” on page 126. Perform this step only if you added modules to PDOS 6. For more information.x.6” on page 125. 2 Finish the upgrade. To upgrade the storage pool software 1 Initiate the upgrade. the upgrade issues a warning message. Type the following command to start the upgrade script: # /opt/PDOS/install/upgradepdos. as follows: ■ If you need to upgrade more nodes in this storage pool to PDOS 6.6 129 To complete the PDOS upgrade 1 2 Log into the node as root.6 or continue on to upgrade your storage pool software.6. 5 Upgrade more nodes to PDOS 6.6..5. If there is insufficient disk space. and the upgrade stops.Upgrading PureDisk software Upgrading the storage pool software to PureDisk 6. If this node is the last one that you need to upgrade to PDOS 6. the software verifies that sufficient disk space is available for upgrade operations. nonstandard.

To initiate the storage pool software upgrade 1 (Conditional) In the Cluster Manager Java Console Web UI. . 2 3 Log into the storage pool authority as root.ini file is encrypted and if the system presents a prompt. Perform this step if the storage pool is clustered. see the following: See “Configuring a /dev/cdrom device” on page 186. Return to this procedure after you remedy the problem. Perform this step if you use iSCSI disks for the /Storage partitions and you do not use a volume manager. Type the following command: # mount -a 4 5 Put the PureDisk software disk into a DVD drive on the storage pool authority node.sh 7 8 Read the information that the upgrade script displays to your screen and press Enter. type the following commands: # mkdir /cdrom # mount /dev/cdrom /cdrom On a few hardware platforms. For example. (Conditional) Type the decryption password for your topology. (Conditional) Make sure that all storage partitions are mounted. Perform this step if your topology. right-click each service group and select Freeze > Temporary.ini file at the prompt. 6 Type the following command to start the upgrade script: # /cdrom/puredisk/upgrade. If your hardware device cannot find /dev/cdrom. the DVD device /dev/cdrom is not available by default. Use the mount(8) command to mount the media.130 Upgrading PureDisk software Upgrading the storage pool software to PureDisk 6.6 Initiating the storage pool software upgrade The following procedure explains how to initiate the storage pool software upgrade.

and PureDisk prompts you for this password when it needs to decrypt the topology files.6 (6.0. A password for user 'username' is required to log on to this new UI. If you specify to terminate running jobs.Upgrading PureDisk software Upgrading the storage pool software to PureDisk 6.6 storage pool configuration wizard lets you reconfigure the storage pool after the upgrade. The prompt is as follows: Do you want to automatically create upgrade jobs for your clients? [Y/n] ■ If you type Y and press Enter. The prompt is as follows: * Veritas NetBackup PureDisk 6. 11 Specify whether you want the upgrade process to start client upgrades automatically. Remember this password. Record it in a safe place. 10 At the prompt for a password.6 131 9 (Conditional) Specify whether to terminate running jobs. If the upgrade software detects PureDisk jobs that are running on the storage pool at the present time. Please enter a password: Confirm: The storage pool configuration wizard can contain any number of characters. the termination activity can take up to 20 minutes. You can monitor these upgrade jobs in the administrator Web UI. you can log into the storage pool administrator Web UI and terminate the running jobs manually. PureDisk does not automatically upgrade PureDisk Deduplication Option (PDDO) clients. but it cannot contain the pipe (|) character or the equal sign (=) character. type a password for the PureDisk 6. PureDisk uses this password to encrypt the topology files. Alternatively. it issues the following message: Abort all jobs now? NOT recommended! (yes/no): Type yes or no and press Enter. PureDisk starts an upgrade job for each standard client.6 storage pool configuration wizard.xxxxx) comes with a new user interface for installing the product and for making changes to the installed environment. The PureDisk 6. however. .6.

you need to upgrade each client individually. ■ /Storage/log/upgrade/6.132 Upgrading PureDisk software Upgrading the storage pool software to PureDisk 6. unmount. Finishing the upgrade The following procedure explains how to verify that PureDisk upgraded the agent software and how to complete the upgrade. which is an empty file. There can be more than one of these directories. PureDisk writes this file after a successful upgrade. and eject the DVD. The upgrade process creates the following files and directories on the storage pool authority node: ■ /etc/puredisk/6. . use the following information to upgrade the clients: See “Upgrading PureDisk agent software on clients” on page 134. For example: # cd / # umount /dev/cdrom # eject 14 Remove the disk from the drive.6/timestamp.6/timestamp-backup. (Conditional) Monitor the automatic agent upgrade jobs. 15 Proceed to the following topic: See “Finishing the upgrade” on page 132. 12 Verify the upgrade files.log.6-upgrade-main-timestamp. After the storage pool upgrade completes.6 ■ If you type n and press Enter. settings. which is a directory of files. Perform this step if you specified that PureDisk upgrade your standard clients automatically. 13 Change directories. To finish the upgrade 1 2 Log into the PureDisk administrator Web UI. and database entries that changed when you upgraded PureDisk. which is a log file of the upgrade. ■ /Storage/log/upgrade/6.

run this script again. Older backups taken with PureDisk 6. PureDisk deactivates the agent.6 disaster recovery backup at this time. In the left pane. Click Manage > Agent in the PureDisk Web UI to check for deactivated agents.Upgrading PureDisk software Upgrading the storage pool software to PureDisk 6. select Agent update.6. In the View jobs by pull-down menu. Perform this step if the storage pool is clustered. 4 (Conditional) In the Cluster Manager Java Console Web UI. 3 Perform a full disaster recovery backup. To accomplish this.sh If you replicate to this storage pool from a PureDisk 6. PureDisk schedules a new upgrade job.6 133 For all clients that are connected to the network. When you activate these agents again. complete the following steps to verify whether the agent upgrade jobs finished successfully: ■ ■ ■ ■ Start the administrator Web UI. if you need to use the disaster recovery backup that you performed in step 3 to restore your storage pool. under Miscellaneous Workflows. If any agent upgrade jobs fail. After 15 minutes or more. PureDisk schedules an agent upgrade job within 15 minutes.6.5. run this security protocol script only after the source storage pool has been upgraded to PureDisk 6.x storage pool.5. In the future. right-click each service group and select Unfreeze. 5 (Recommended) Run the script that upgrades the security protocol. Click Monitor > Jobs. Do not perform an incremental backup. Use the instructions in the PureDisk Administrator's Guide. Note: It is very important to run a full PureDisk 6. 6 Make sure that the agent software on each client attached to this storage pool has been upgraded to PureDisk 6. The script is not included in that disaster recovery backup.x software cannot be restored to PureDisk 6. Symantec recommends that you run the following script on the storage pool authority node: # /opt/pdinstall/disable_sslv2. do the following: . select Policy types. This full backup preserves both the databases and the content router data. This workflow is for the agent upgrade jobs.6 storage pools.

Start a manual upgrade for each PDDO client. you can use the following procedure to perform a manual upgrade: See “Upgrading standard clients manually” on page 134. If you request the automatic upgrade. Also start a manual upgrade for each standard client if. The upgrade jobs time out after 14 days. The upgrade occurs even if the latest version was . PDDO agents. ■ For more information about how to download clients. during the upgrade process. If a client does not connect to the storage pool within that 14 day period. The upgrade process cannot initiate PDDO agent upgrade jobs automatically. PureDisk starts automatic upgrade jobs for each agent only if you requested this action during the upgrade process. back up and restore agents. PureDisk automatically upgrades that client when it reattaches. In the following procedure. you specified that PureDisk not start standard client upgrade jobs automatically. see the following topic: See “Upgrading PureDisk agent software on clients” on page 134. The following explains how to upgrade PDDO agents: See “Upgrading PDDO clients on NetBackup Windows media servers” on page 135. PureDisk upgrades the selected agents to the latest PureDisk agent software. start another upgrade job for that client.134 Upgrading PureDisk software Upgrading PureDisk agent software on clients ■ Verify that all the automatic agent upgrade jobs completed. Upgrading PureDisk agent software on clients PureDisk supports the following agent types and lets you upgrade these agents on your clients. see the following: PureDisk Client Installation Guide Upgrading standard clients manually You can upgrade all the clients that PureDisk associated with a particular storage pool or with a particular department simultaneously. PureDisk upgrades the agent software on each client automatically when it pushes the new software to the storage pool nodes and clients. The upgrade process prompts you to specify whether you want to upgrade standard agents automatically. ■ For information about how to upgrade agents. Start manual upgrade jobs as needed and monitor the manual job progress. If PureDisk fails to upgrade all the clients in the storage pool. as follows: ■ Standard. when you click Upgrade Agent(s). If a client is not attached to the storage pool at the time of the upgrade.

a department. select Upgrade Agent(s) from the More Tasks drop-down menu. This behavior lets you repeat an upgrade attempt if the first attempt failed.Upgrading PureDisk software Upgrading PureDisk agent software on clients 135 present already. If you select an incorrect operating system type. In the right pane. After the upgrade. To upgrade PDDO clients on NetBackup Windows media servers 1 2 Log into the media server. Upgrading PDDO clients on NetBackup Windows media servers The following procedure explains how to upgrade PDDO clients on NetBackup Windows media servers.exe. PureDisk issues a message that says that no jobs were created for this upgrade. PureDisk upgrades the agent software on all agents underneath the selected item. (Conditional) Use the drop-down list to the right of each client’s operating system to select the appropriate agent software level. If you have a mixture of client types. The upgrade process skips virtual agents and inactive agents. if you activate an old. When you click Save. inactive agent. select a storage pool. or a location. PureDisk creates a job to upgrade each client. specify the path to which you installed the NetBackup software. . or resulted in a broken installation. Browse to the following directory: NB_install_path\NetBackup\bin For NB_install_path. 5 Click Save. 3 Double-click bpdown. Perform this step if you want to upgrade more than one client and if you need to specify each client's operating system. select an agent software level for each client operating system that you need. PureDisk automatically starts the update workflow for that client. was interrupted. Virtual agents are those that PureDisk creates automatically for replicated data selections. To upgrade clients manually 1 2 3 4 Click Manage > Agents. In the left pane.

On the Veritas NetBackup PureDisk Features page. On the Veritas NetBackup PureDisk Features page. click Change. 12 Compare customized settings. click Finish. click Install. and download a new Windows agent. and click Next. Double-click the PureDisk agent icon that you downloaded onto the media server. ■ If your PureDisk 6.5. For more information. type y and press Enter. On the Change Current Destination Folder page. make sure that Enable PureDisk Deduplication Option is checked. and perform the following steps: ■ If your PureDisk 6. Select the NetBackup PureDisk Agent folder. Click Next. On the Agent Installation Method page. 10 On the Ready to Install the Program page. 11 On the Installation Complete page. For PD_install_path.x PDDO agent is installed in the default directory on the client. select I accept . From the media server. Verify that the path in the Folder Name field is the correct installation directory. perform the following steps: ■ ■ Make sure that the Typical installation method is selected.x PDDO agent is not installed in the default directory on the client. The next few steps in this procedure explain how to configure a PureDisk agent as a PDDO agent. click Next.. 7 8 9 On the agent installation Welcome page. perform the following steps: ■ ■ ■ ■ Make sure that the Custom installation method is selected. . click Next.136 Upgrading PureDisk software Upgrading PureDisk agent software on clients 4 5 6 At the prompt to proceed. PD_install_path\NetBackup PureDisk Agent. For example. see the PureDisk Deduplication Option Guide. Click Next...5. browse to the NetBackup PureDisk Agent folder in your nondefault directory. On the License Agreement page. log into the PureDisk administrative Web UI. specify the path to which you installed the PureDisk software. ■ ■ ■ ■ Click OK.

6.x settings were deprecated and are no longer supported in PureDisk 6.conf.6.XXXX. Open file pd.all 3 4 From the media server. specify the path to which you installed the NetBackup software. Modify the new pd. Some PureDisk 6.6_x86-6.conf.XXXX.Upgrading PureDisk software Upgrading PureDisk agent software on clients 137 Perform the following steps to update your new pd. 15 At the prompt to proceed.XXXX.bak.conf file: ■ Browse to NB_install_path\NetBackup\bin\ost-plugins. log into the PureDisk administrative Web UI.conf file in PureDisk 6.5.run # sh pdagent-Solaris_10_sparc-6.6. 14 Double-click bpup.6 configuration file settings. ■ ■ ■ Open file pd.kill. For information about the pd.6. Type the following command to stop NetBackup daemons and processes: # /usr/openv/netbackup/bin/bp. Type the following command to start the PDDO client upgrade: # sh pdagent-Linux_2.0.run . type y and press Enter. and download a new platform-specific agent.run # sh pdagent-Solaris_8_sparc-6.0.exe.6. To upgrade PDDO clients on NetBackup Linux and UNIX media servers 1 2 Log into the media server.0. For NB_install_path.conf file to include only PureDisk 6. see the following: PureDisk Deduplication Option Guide 13 Browse to the following directory: NB_install_path\NetBackup\bin For NB_install_path. specify the path to which you installed the NetBackup software. Upgrading PDDO clients on NetBackup Linux and UNIX media servers The following procedure explains how to upgrade PDDO clients on NetBackup Linux and UNIX media servers.

For information about the pd. Some PureDisk 6.template /usr/openv/lib/ost-plugins/pd. For example: # cp /usr/openv/lib/ost-plugins/pd.5.6 pd.x pd.6” on page 139.conf file.conf template.conf file to include only PureDisk 6.65.conf /usr/openv/lib/ost-plugins/pd.6.x settings were deprecated and are no longer supported in PureDisk 6.conf file: ■ Rename your PureDisk 6.2 transaction log files. the software checks for the existence of transaction log files from PureDisk 6. type y and press Enter. Compare customized settings.5. Perform the following steps to update your new pd.conf. and exits: ■ number old 6. If the upgrade process finds PureDisk 6.138 Upgrading PureDisk software Troubleshooting and notes 5 6 At the prompt to replace the installed package with the new agent you downloaded in step 3.conf. See “Applying updates after you upgrade to PureDisk 6.2 tlogs found in spool directory ■ .conf file in PureDisk 6. Addressing transaction log messages At the beginning of the upgrade process.conf ■ Modify the new pd. For example: # cp /usr/openv/lib/ost-plugins/pd.6.2 tlogs found in queue directory number old 6.all Troubleshooting and notes The following topics describe troubleshooting information and include notes about the upgrade process: ■ ■ See “Fixing a failed upgrade” on page 139. PureDisk issues one or both of the following messages.2.bak ■ Rename your PureDisk 6. see the following: PureDisk Deduplication Option Guide 7 Type the following command to restart NetBackup daemons: # /usr/openv/netbackup/bin/bp.start.6 configuration file settings.

Upgrading PureDisk software Troubleshooting and notes 139 If the upgrade issues these messages. see the following topic: See “About troubleshooting PureDisk installations” on page 183.log ■ For more information about troubleshooting.6 Do not try to apply old EEBs.5. Applying updates after you upgrade to PureDisk 6.2 transaction log processing is continuing but is not yet complete. update releases. and the upgrade exits again. or patches that are explicitly written for PureDisk 6. A lower number indicates that PureDisk 6. or patches to your storage pool after you upgrade to PureDisk 6. If you start the upgrade again. update releases. . see the following: ■ For diagnostic information about the storage pool upgrade.6/timestamp-main. start the upgrade again at a later time. Fixing a failed upgrade If the upgrade failed.5. apply only EEBs. the number in these messages will be lower. In the future. see the following file: /Storage/log/upgrade/6.

140 Upgrading PureDisk software Troubleshooting and notes .

confirm data you enter. Starting YaST2 If you choose the manual option to install PDOS. The pane at the bottom is a navigation pane.Appendix A Navigating the YaST2 interface This appendix includes the following topics: ■ About the YaST2 interface About the YaST2 interface The PDOS installation procedure requires you to use the YaST2 text-based interface to specify DNS and other information. You can use the labels at the bottom to navigate through the screens. You can edit system information in this pane. The YaST2 window is divided into the following panes: ■ The pane on the left is the information pane. the system launches YaST2 at its welcome screen. . The pane on the right is the editing pane. obtain help information. see the SUSE documentation on the Novell documentation Web site at the following URL: www. ■ ■ For more information about the YaST2 interface. and perform other functions.com/documentation/suse/index.novell.html. It either displays the module that you are in or it provides additional information.

Labels and selected fields in the display contain a yellow letter. Alt+yellow_letter Esc+yellow_letter Tab Alt+Tab Esc+Tab Shift+Tab Exit Quits the YaST2 interface.142 Navigating the YaST2 interface About the YaST2 interface If you choose one of the automated PDOS installation methods. or activates a menu item. Selects the next category up. . or to finish a module. Useful in screens if use of the left arrow key can change the active pane or current selection list. Press F10 to approve a module. Table A-1 Key Up arrow Down arrow Right arrow Shift+right arrow Ctrl+E Shift+left arrow Ctrl+A Enter YaST2 navigation keys Action Changes the category. Useful in screens if use of the right arrow key can change the active pane or current selection list. Scrolls horizontally to the left. Starts a module from a selected category. Press F1 in a module to display the function key mappings for that module. Other function key mappings depend on the active YaST2 module. Press Alt or Esc plus the yellow letter to select that label or action. YaST2 navigation key sequences Table A-1 lists the navigation keys and how to use them. Scrolls horizontally to the right. Selects the next category down. runs an action. the system launches YaST2 and performs the install automatically. Changes the category. Function keys Your keyboard function keys enable access to the YaST2 labels. Moves from label to label or from selection list to selection list. go to the next module. Starts a module from the selected category.

IP address. The spreadsheet you completed before you began your installation contains the information you need.Appendix B Installation worksheets (unclustered) This appendix includes the following topics: ■ ■ About the installation worksheets Installation worksheets About the installation worksheets The installation worksheets are tables that you can complete after you configure your system. roles. These tables provide you with a place to record host names. Keep the completed worksheets in a safe place. do not complete these worksheets. . Each table constitutes a worksheet that lets you record each storage pool’s topology after the installation process. Note: If you installed a clustered storage pool. and PureDisk identification. You also can use the information on these worksheets if you have to recover your PureDisk environment in the event of a disaster. The following procedure explains how to complete the installation worksheets.

Look in the right pane for the number to the right of the Agent ID label. You can obtain the storage pool’s agent ID number from file /Storage/etc/topology. Typically. To obtain the agent ID number for a node from the Web UI 1 2 Click Settings > Topology in the Web UI. look for the value in the Storage Pool ID field. see the following: See “Obtaining the storage pool ID number” on page 144. 3 Complete the worksheets and store them in a safe place. see the following: See “Obtaining the agent ID numbers” on page 144. see the following: See “Installation worksheets” on page 145. . You can obtain the storage pool ID number from file /Storage/etc/topology. To obtain the storage pool ID number from the Web UI 1 2 3 Click Settings > Topology in the Web UI.ini or from the PureDisk Web UI. 2 Obtain the storage pool’s agent ID numbers. For information about this procedure. Obtaining the storage pool ID number The following procedure explains how to obtain the storage pool ID number from the Web UI. Obtaining the agent ID numbers The following procedure explains how to obtain the agent ID numbers from the Web UI. Select the storage pool.144 Installation worksheets (unclustered) About the installation worksheets To complete the installation worksheets 1 Obtain the storage pool ID number of the storage pool. For information about this procedure. 3 4 Click one of the nodes in the storage pool. the storage pool is expanded by default. For copies of the worksheets. (Conditional) Expand the storage pool. In the right pane.ini or from the PureDisk Web UI.

. .Installation worksheets (unclustered) Installation worksheets 145 Installation worksheets The following sections contain the installation worksheets. . Location . Worksheet 1 The following is a worksheet. . . . . . . . . . . . . Table B-1 Storage pool ID: ____________________. . . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number . Each worksheet is identical to the others.

. . . . . .146 Installation worksheets (unclustered) Installation worksheets Worksheet 2 The following is a worksheet. . . . . . Location Worksheet 3 The following is a worksheet. . Table B-2 Storage pool ID: ____________________. . . . . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number .

. . . . . Table B-4 Storage pool ID: ____________________. . . . . . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number .Installation worksheets (unclustered) Installation worksheets 147 Table B-3 Storage pool ID: ____________________. Location Worksheet 4 The following is a worksheet. . . . . . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number . Location . .

Location . . . . . . . . . Table B-5 Storage pool ID: ____________________. Location Worksheet 5 The following is a worksheet. .148 Installation worksheets (unclustered) Installation worksheets Table B-4 Storage pool ID: ____________________. . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number . Storage pool name: ____________________ (continued) Host name FQDN/IP address PD services Agent ID Node number . . . . . . .

Storage pool name: ____________________ (continued) Host name FQDN/IP address PD services Agent ID Node number . . .Installation worksheets (unclustered) Installation worksheets 149 Table B-5 Storage pool ID: ____________________. . Location . . . . Table B-6 Storage pool ID: ____________________. . . . . . . Storage pool name: ____________________ Host name FQDN/IP address PD services Agent ID Node number . . . . Location Worksheet 6 The following is a worksheet. .

Location . . Storage pool name: ____________________ (continued) Host name FQDN/IP address PD services Agent ID Node number . . . . . . .150 Installation worksheets (unclustered) Installation worksheets Table B-6 Storage pool ID: ____________________. . .

yourloginattrib.Appendix C Configuring external directory service authentication This appendix 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 an external directory service About maintaining synchronization between PureDisk and an external directory service Adding. changing. or deleting users or groups Changing the youruserclass. or yournameattrib variables in your directory service’s ldap.xml file Changing the yourdescriptionattrib variable or the yourmailattrib variable in your directory service’s ldap.xml file Disabling external authentication Changing the TLS specification ■ ■ ■ ■ ■ ■ .

5 Enable the PureDisk policy that synchronizes PureDisk with the directory service. Service Pack 1 Active Directory. Service Pack 4 The following process explains the tasks you need to complete to configure external directory service authentication. 3 (Optional) Verify transport layer security (TLS) and copy the certificate authority’s certificate. To configure external directory service configuration 1 Obtain directory service information. PureDisk authenticates users through its internal OpenLDAP directory service. you can configure your site’s external OpenLDAP or Active Directory service for user authentication. If you want to use only PureDisk’s internal OpenLDAP directory service for user authentication. 4 Link PureDisk to the external directory service. Microsoft Server 2003. See “(Optional) Adding PureDisk groups to your directory service” on page 162. The procedures also assume that your site’s directory service . See “Obtaining directory service information” on page 153. 2 (Optional) Add PureDisk groups to your directory service. Service Pack 1 Active Directory. See “Linking PureDisk to the external directory service” on page 167. See “Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service” on page 174.27 Active Directory. PureDisk requires the following levels: ■ ■ ■ ■ OpenLDAP. Microsoft Server 2008. Microsoft Server 2000.3. See “(Optional) Verify TLS and copy the CA certificate” on page 163. Alternatively. version 2. you do not need to perform any additional configuration.152 Configuring external directory service authentication About external directory service authentication ■ Modifying the base search path About external directory service authentication By default. Assumptions The procedures you need to perform to configure external authentication assume that you are familiar with how your site’s OpenLDAP or Active Directory service is organized.

you cannot create users and groups directly in PureDisk. but it cannot use both at the same time. If the external service is down.Configuring external directory service authentication Obtaining directory service information 153 administrator can provide you with information about how the directory service is configured. After you import users and groups from the external directory service. This administrator can also help you analyze your site’s existing authentication configuration. the job that runs the system policy for syncing external ldap users fails. You cannot import a user with the root login property from an external directory service. When authentication through an external directory service is enabled. If you try to synchronize the external directory service. For example. the external directory service may be down. add them in your directory service and import them into PureDisk. When PureDisk is configured to authenticate through its internal directory service. The root users for both PureDisk and for the external directory service are always present and are always unique. By default. only its local user accounts are valid. User accounts The following information pertains to user accounts when external authentication is enabled: ■ The Edit LDAP Server Configuration screen in the Web UI includes a checkbox labeled Enable LDAP Authentication. you can authenticate from PureDisk’s internal OpenLDAP service. When this box is unchecked. PureDisk authenticates through its internal OpenLDAP directory service. the PureDisk root user’s permissions and privileges are always the same. You cannot merge these directory services. you need to grant PureDisk permissions to those users and groups. They remain the same regardless of whether authentication is through PureDisk’s internal directory service or through an external directory service. However. ■ ■ ■ Obtaining directory service information Your site’s directory service administrator can help you gather the information that you need to configure PureDisk to perform external user authentication. . PureDisk authenticates through an external directory service. When this box is checked. If you want to add PureDisk users and groups. PureDisk can use either its internal directory service or your external directory service. only the accounts from that external directory service are valid. when PureDisk is configured to use an external directory service.

For this reason. You can use the right column of the table to make notes about the requirements. __________________________________________ The directory service administrator needs __________________________________________ to put a copy of this file on the storage pool authority. their structures. 2 (Conditional) Obtain TLS information from your site’s external directory service administrator. . you need to convert the certificate file you receive to PEM format. you must examine the object classes and attributes in your directory service and map them to the PureDisk configuration information screens. The directory services themselves. Perform this step if your site requires TLS. The following table summarizes the information that you need to obtain. If your site has an Active Directory service. host name. Site-speecific value __________________________________________ Port number to the server that hosts the __________________________________________ directory service The ldapsearch(1) command and its __________________________________________ parameters that PureDisk needs to obtain a listing. and their schemas are site-specific and unique to their purpose. or IP address. Common name of the certificate authority __________________________________________ file.154 Configuring external directory service authentication Obtaining directory service information The following procedure explains the information that you need to obtain from your site’s directory service administrator. Copy of the certificate authority file. 3 Examine a listing from your directory service. Item needed Directory service host fully qualified domain name (FQDN) (preferred). To obtain information about your site’s directory service 1 Obtain general information from your site’s external directory service administrator. Instructions later in this process explain when and how to perform the conversion. Each OpenLDAP or Active Directory service is unique.

See “Example OpenLDAP directory service” on page 159. Table C-1 Active Directory service structure Domain controller Domain controller Organization units Common names dc=com dc=acme ou=users cn=Alice Munro cn=Bob Cratchit cn=Claire Clairmont cn=Dave Bowman ou=groups cn=chicago cn=atlanta . If TLS is required at your site. Otherwise. proceed to the following topic: See “(Optional) Adding PureDisk groups to your directory service” on page 162. proceed to the following topic: See “Linking PureDisk to the external directory service” on page 167. 4 Save your directory listing. 5 Proceed to one of the following topics: ■ If you want to add PureDisk user groups to your directory service at this time. ■ ■ Example Active Directory service Table C-1 shows the structure of an example Active Directory service. You need to use this listing later in the configuration process.Configuring external directory service authentication Obtaining directory service information 155 The following examples show directory service listings: ■ ■ See “Example Active Directory service” on page 155. proceed to the following topic: See “(Optional) Verify TLS and copy the CA certificate” on page 163.

DC=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user objectClass: inetOrgPerson cn: Alice Munro sn: Munro description: Alice's Description givenName: Alice distinguishedName: CN=Alice Munro.OU=groups.DC=acme.100.156 Configuring external directory service authentication Obtaining directory service information This directory service has two organizational units: users and groups.dc=com" -W \ -b dc=acme.ou=users. a command such as the preceding example returns information about more than users and groups.dc=com "(objectClass=*)" > /tmp/example.DC=acme. users. The command to obtain a listing of users and groups is as follows: # ldapsearch -H ldap://100.DC=com displayName: Alice memberOf: CN=chicago.OU=users.dc=com> with scope subtree # filter: (objectClass=*) # requesting: ALL # # Alice Munro.txt.munro@acme.101:389 -x \ -D "cn=Alice Munro. characters in bold represent definitions from this file that you need later in the configuration process: # extended LDIF # # LDAPv3 # base <dc=acme.100.com # yourmailattrib # yourloginattrib # yourdescriptionattrib # yournameattrib # youruserclass # base search path . users. The command writes its output to file example.DC=com uSNChanged: 21751 name: Alice Munro sAMAccountName: alice.DC=acme.munro@acme.com # Bob Cratchit.com mail: alice.OU=users. You can use the ldapsearch(1) command to obtain a listing of this directory service.txt If more directory entries exist in the same directory subtree.dc=acme.com dn: CN=Alice Munro.munro userPrincipalName: alice. acme. In the example file that follows. acme.

DC=acme.com # Claire Clairmont.OU=users.OU=users.com dn: CN=Claire Clairmont.DC=acme.com dn: CN=Dave Bowman. acme.DC=acme. acme.DC=com displayName: Bob Cratchit memberOf: CN=chicago.cratchit@acme.com mail: bob.DC=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user objectClass: inetOrgPerson cn: Claire Clairmont sn: Clairmont description: Claire's Description givenName: Claire distinguishedName: CN=Claire Clairmont.DC=acme.clairmont@acme.DC=com name: Bob Cratchit sAMAccountName: bob.DC=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user objectClass: inetOrgPerson cn: Bob Cratchit sn: Cratchit description: Bob's Description givenName: Bob distinguishedName: CN=Bob Cratchit.DC=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user .clairmont@acme.DC=acme.DC=acme.Configuring external directory service authentication Obtaining directory service information 157 dn: CN=Bob Cratchit.DC=com displayName: Claire Clairmont memberOf: CN=atlanta. users.com mail: claire.cratchit userPrincipalName: bob.DC=acme. users.clairmont userPrincipalName: claire.OU=users.OU=users.OU=users.DC=com name: Claire Clairmont sAMAccountName: claire.OU=groups.cratchit@acme.OU=groups.com # Dave Bowman.

DC=acme.DC=com distinguishedName: CN=chicago.DC=com name: atlanta sAMAccountName: atlanta # search result search: 7 result: 0 Success # numResponses: 7 # numEntries: 6 # yourusergroupclass # yournameattrib # yourmemberattrib .com dn: CN=chicago.DC=acme.DC=com objectClass: top objectClass: group sAMAccountName: atlanta member: CN=Dave Bowman.DC=acme.OU=groups.DC=com name: Dave Bowman sAMAccountName: dave.OU=groups.OU=users.DC=com objectClass: top objectClass: group sAMAccountName: chicago member: CN=Bob Cratchit.DC=acme.DC=acme.bowman@acme.OU=groups.DC=acme.DC=acme.com dn: CN=atlanta.OU=groups. acme.DC=com distinguishedName: CN=atlanta.bowman userPrincipalName: dave.com mail: dave.OU=users. groups.DC=com name: chicago sAMAccountName: chicago # atlanta. groups.com # chicago.DC=acme.DC=com member: CN=Alice Munro.OU=users.OU=users.DC=acme.DC=acme.OU=users. acme.DC=com displayName: Dave Bowman memberOf: CN=atlanta.bowman@acme.DC=com member: CN=Claire Clairmont.158 Configuring external directory service authentication Obtaining directory service information objectClass: inetOrgPerson cn: Dave Bowman sn: Bowman description: Dave's Description givenName: Dave distinguishedName: CN=Dave Bowman.OU=groups.

Table C-2 OpenLDAP directory service structure Common names Domain controller Domain controller Organizational units 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. In the example that follows.txt This example writes its output to file example.Configuring external directory service authentication Obtaining directory service information 159 Example OpenLDAP directory service Table C-2 shows the structure of an example OpenLDAP directory service. The command to obtain a listing of the users and groups is as follows: # ldapsearch -H ldap://100. File example.100.100:389/ -x \ -D "cn=Diana Goyer.txt is as follows: # extended LDIF # . You can use the ldapsearch(1) command to obtain a listing of this directory service. characters in bold represent the definitions that you need later in the configuration process. The external directory service authentication configuration procedures use examples from this listing.dc=com" "(objectClass=*)">/tmp/example.dc=com" -W \ -b "dc=marlins.dc=marlins.txt.100.ou=commuters.

commuters. marlins.com uid: dgoyer # yournameattrib # yourmailattrib # yourloginattrib # youruserclass # base search path .dc=com mail: Mary. marlins.dc=com ou: commuters objectClass: organizationalUnit # groups. marlins.Goyer@marlins.dc=com mail: Florence.dc=com dc: marlins objectClass: domain # commuters.dc=marlins.ou=commuters. marlins.com dn: cn=Mary Evans.com dn: cn=Diana Goyer.dc=marlins.dc=marlins.160 Configuring external directory service authentication Obtaining directory service information # LDAPv3 # base <dc=marlins.com dn: ou=groups.com dn: cn=Florence Leeds.com uid: fleeds objectClass: inetOrgPerson sn: Leeds cn: Florence Leeds userPassword:: cGFzc3dvcmQ= # Mary Evans.dc=marlins. commuters.com uid: mevans objectClass: inetOrgPerson sn: Evans cn: Mary Evans userPassword:: cGFzc3dvcmQ= # Diana Goyer.dc=com> with scope subtree # filter: (objectClass=*) # requesting: ALL # # marlins.dc=com ou: groups objectClass: organizationalUnit # Florence Leeds.com dn: dc=marlins.com dn: ou=commuters. marlins. commuters.Leeds@marlins.ou=commuters.dc=com mail: Diana.dc=marlins.ou=commuters.Evans@marlins.

com uid: asmith objectClass: inetOrgPerson sn: Smith cn: Adam Smith userPassword:: cGFzc3dvcmQ= # Eric Meyer.ou=commuters.dc=com objectClass: groupOfNames # yourusergroupclass # yournameattrib # yourmemberattrib . commuters. marlins. marlins.dc=marlins. marlins.dc=marlins.dc=com member: cn=Mary Evans. groups.dc=com mail: Joe.dc=com member: cn=Diana Goyer. commuters. marlins.Configuring external directory service authentication Obtaining directory service information 161 objectClass: inetOrgPerson sn: Goyer cn: Diana Goyer userPassword:: cGFzc3dvcmQ= # Adam Smith.dc=marlins.dc=com objectClass: groupOfNames cn: bikers member: cn=Florence Leeds. groups.com dn: cn=Joe McKinley.dc=marlins.ou=groups.dc=com mail: Adam.ou=groups.dc=com mail: Eric.McKinley@marlins.ou=commuters. commuters.dc=marlins. marlins.dc=marlins.com dn: cn=bikers.dc=marlins.ou=commuters.Meyer@marlins.com dn: cn=drivers.ou=commuters.com dn: cn=Eric Meyer.ou=commuters.com dn: cn=Adam Smith.dc=marlins.ou=commuters.com uid: emeyer objectClass: inetOrgPerson sn: Meyer cn: Eric Meyer userPassword:: cGFzc3dvcmQ= # Joe McKinley.dc=com # drivers.Smith@marlins.com uid: jmckinley objectClass: inetOrgPerson sn: McKinley cn: Joe McKinley userPassword:: cGFzc3dvcmQ= # bikers.

delete. You can run the synchronization policy at any time after your initial configuration.dc=com member: cn=Joe McKinley.dc=com member: cn=Eric Meyer.dc=marlins. Installers. You can perform this procedure either now or after you complete the external directory service authentication configuration.ou=commuters. Reporters. This policy synchronizes external directory service users with PureDisk’s internal directory service. If you configure users and groups specific to PureDisk now. you can see them in the Web UI immediately after you complete the configuration. The following manual includes information about the different types of permissions that you can grant to users and user groups: . Users who can back up files for one storage pool but cannot restore or delete. Users with full administrative privileges. Users who can back up and restore data.ou=commuters. In this procedure. After you add. Users. Users who can run reports.162 Configuring external directory service authentication (Optional) Adding PureDisk groups to your directory service cn: drivers member: cn=Adam Smith.dc=marlins. run the PureDisk system policy. Users who can install PureDisk agents on client systems.dc=marlins. You can configure PureDisk to authenticate some or all of the user groups that are defined in your directory service. you create users and groups that are specific to PureDisk operations.ou=commuters. Backup operators.dc=com # search result search: 2 result: 0 Success # numResponses: 12 # numEntries: 11 (Optional) Adding PureDisk groups to your directory service Perform this procedure if you want to create PureDisk user groups at this time. To create PureDisk users and groups 1 Edit your directory service and add one or more of the following typical PureDisk user groups: ■ ■ ■ ■ ■ Administrators. or change user or group information in your directory service.

proceed to the following topic: See “Linking PureDisk to the external directory service” on page 167. If TLS is required. specify the common name whenever a procedure requires you to provide the LDAP Server Host Name. but PureDisk does not require TLS. See “Verifying the server name” on page 163.Configuring external directory service authentication (Optional) Verify TLS and copy the CA certificate 163 See the PureDisk Client Installation Guide. PureDisk does not support mutual authentication for situations in which the active directory server and the storage pool authority need to authenticate to each other. Verifying the server name The following procedure explains how to verify the server name in the TLS certificate. proceed to the following topic: See “(Optional) Verify TLS and copy the CA certificate” on page 163. Otherwise. See “Writing the certificate to the storage pool authority” on page 164. ■ (Optional) Verify TLS and copy the CA certificate You can use TLS during the user authentication process. When you use TLS. Log into the storage pool authority node (unclustered) or storage pool authority service (clustered) as root. Unresolvable common names are the most common cause of server certificate errors. 2 Proceed to one of the following topics: ■ If TLS is required at your site. . perform the following procedures. To verify the server name in the certificate 1 2 Obtain the certificate’s common name from your directory service administrator. To verify TLS and copy the CA certificate 1 Verify the server name. 3 Proceed to the following topic: See “Linking PureDisk to the external directory service” on page 167. The directory service needs to authenticate to the storage pool authority. 2 Write the certificate to the storage pool authority.

north.100. the line should look like the following: 100. Perform this step only if the previous step’s ping(8) command was unsuccessful. 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.pem file from an OpenLDAP server. cacert. For example: # ping mn.north.north.pem is the default name for this file when it is generated by an OpenLDAP server. Copy one of the following certificate files to the appropriate directory on the storage pool authority: ■ The cacert. To write the certificate to the storage pool authority 1 2 Log into the storage pool authority node (unclustered) or storage pool authority service (clustered) as root.101): icmp_seq=1 ttl=64 time=4.stars (100.stars.100.stars 5 Proceed to the following: See “Writing the certificate to the storage pool authority” on page 164.164 Configuring external directory service authentication (Optional) Verify TLS and copy the CA certificate 3 Verify the common name by issuing a ping(8) command against the certificate’s common name.71 ms 64 bytes from mn.100.101): icmp_seq=2 ttl=64 time=0. Writing the certificate to the storage pool authority The following procedure explains how to write the certificate to the storage pool authority node and verify the server-side authentication.north.stars PING mn.100. This file name can be different at your site. ■ The appropriate directory for the certificate file is as follows: .100.353 ms 4 (Conditional) Edit the /etc/hosts file.100. The generated certificate from an Active Directory server.100.stars (100.100.101 mn.north.north.101) 56(84) bytes of data.stars (100. 64 bytes from mn. if the common name of your directory service certificate is mn.

The openssl(1) command and the x509(1) utility make the file compatible with OpenSSL. you ensure that the certificate moves with the storage pool authority when a failover occurs. This file ends in . When you write the certificate file to /Storage. Symantec recommends that you write the certificate file to the /var/ldap/certstore/ directory. but you can write this file to any directory.pem This command’s variables are as follows: file.cer. Symantec recommends that you log into the storage pool authority and write the certificate file to /Storage/var/keys. Type the following command: # /usr/bin/openssl x509 -inform DER -outform PEM -in file. In a clustered storage pool.pem 4 Use the openssl(1) command and the s_client(1) program to test the port connections and to verify that the SSL certificate operates correctly. Obtain this file from your site’s directory service administrator.pem. 3 (Conditional) Use the openssl(1) command and the x509(1) utility to convert the Active Directory certificate to PEM format. This file name ends in . Perform this step only if an Active Directory service generated the certificate. Type the following command: # /usr/bin/openssl s_client -connect FQDN:port -showcerts -state -CAfile cert_loc This command’s variables are as follows: .cer The name of the file that contains the Active Directory certificate.Configuring external directory service authentication (Optional) Verify TLS and copy the CA certificate 165 ■ In an unclustered storage pool.cer -out file. You do not have to perform this step if an OpenLDAP directory service generated the certificate. ■ You can use any file transfer program to copy the files. The name of your certificate in the format that is compatible with OpenSSL. file.

cert_loc Specify the absolute path to the certificate file. For example: /var/ldap/certstore/mycertfile. . This file is the one that you copied in step step 2. the value is 636. This variable takes the format FQDN:port .166 Configuring external directory service authentication (Optional) Verify TLS and copy the CA certificate FQDN: port The directory service server’s FQDN and the port from which you imported the certificate.acme.com:636. specify the port that the directory service server uses for incoming communication. Specify the following values: ■ ■ For FQDN. For port. specify the FQDN of the directory service server.pem. By default. For example blink.

101:636 -x \ -D "cn=Alice Munro.dc=acme. Symantec recommends that you specify an FQDN. port uid base filter If the connection is open. If the command fails or generates messages. it displays a listing of directory service server information.100. or IP address of the directory service server. Linking PureDisk to the external directory service Use the following procedures to link PureDisk and your external Active Directory or OpenLDAP directory service. the value is 636.100. The connection needs to be open to allow continued authentication activities. The base search path.dc=com" -W \ -b ou=groups. host name. 6 Proceed to the following topic: See “Linking PureDisk to the external directory service” on page 167. fix the connectivity problems before you proceed. . The port the PureDisk uses for TLS communication. The distinguished name of the test user with which to bind. An object class name. By default. This port is the one where the external OpenLDAP server runs ldaps.Configuring external directory service authentication Linking PureDisk to the external directory service 167 5 Use the ldapsearch(1) command to test the connection between the storage pool authority and the directory service server.ou=users. 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. The command searches for this object class name as a test.dc=acme.dc=com "(objectClass=group)" The command’s variables are as follows: ds_serv The FQDN.

See “Completing the Connection tab” on page 168. in an all-in-one environment. For example. Configuring communication The following procedure explains how to configure communication in the PureDisk Web UI.mnbe. 6 Complete the Connection tab. 2 3 4 5 Type your user name and password at the prompts on the login screen. The LDAP Server Configuration properties appear in the right pane. In the left pane. . See “Completing the Mapping tab” on page 171. specify the URL to the storage pool authority. click the plus (+) sign to the left of LDAP server.com. Completing the Connection tab The following procedure explains how to complete the fields on the Connection tab. https://acme. To configure communication in the PureDisk Web UI 1 Display the storage pool authority opening screen. this value is the URL of the PureDisk node upon which you installed all the PureDisk software.168 Configuring external directory service authentication Linking PureDisk to the external directory service To link PureDisk to the external directory service 1 Configure communication in the PureDisk Web UI. 2 Manage user groups. See “Configuring communication” on page 168. Open a browser window and type the following URL: https://URL For URL. Select External LDAP. For example. See “Managing user groups” on page 173. Click Settings > Configuration. 7 Complete the Mapping tab. 8 Enable user group management. See “Managing user groups” on page 173.

the Port number that connects PureDisk to the external OpenLDAP or Active Directory service. this box is clear. If you do not have this information yet. For example: blinkie. The port to specify depends on whether TLS is enabled. as follows: ■ If you want to enable PureDisk's internal OpenLDAP directory service. and users can continue to use PureDisk while the external directory service is down. specify the FQDN or IP address of the server upon which your external OpenLDAP or Active Directory service resides. obtain this name from your directory service administrator. the default security port is 636. as follows: ■ ■ When TLS is enabled. If you want to enable an external OpenLDAP service or an external Active Directory service. if the external directory service goes down. When this box is clear. PureDisk uses its internal authentication mechanism. clear this box. as follows: ■ When TLS is enable. Symantec recommends that you use an FQDN for this field. If you want to enable single port communication between the nodes and clients in your PureDisk environment. the default port is 389. ■ 3 Verify. A check in this box determines whether PureDisk uses the default PureDisk OpenLDAP directory service or whether PureDisk uses an external directory service. Note that this FQDN must match the common name that you specified when you created the certificate of your external OpenLDAP server. For example. . specify the FQDN of the external OpenLDAP server. check this box. The content of this field differs depending on whether or not you enabled transport layer security (TLS). When TLS is not enabled. clear this box. and respecify if needed.com. By default. When TLS is not enabled.acme. ■ 2 Specify the LDAP Server Host Name. TLS encrypts data transactions between your external directory service and PureDisk. A check in this box determines whether TLS is enabled. 4 Check or clear the Enable TLS for LDAP Communication box.Configuring external directory service authentication Linking PureDisk to the external directory service 169 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 an external Active Directory service.

Specify the full path to the file that contains the certificate authority that PureDisk can use to verify the connection to the external directory service server. This administrator account does not need to have full privileges on the directory service server. Specify the external directory service's Base Search Path. Specify the highest entry that is a common ancestor of the groups that you need. assume that you want PureDisk to use the groups from the OpenLDAP marlins. 7 In the Password field. 6 Specify the User Distinguished Name.170 Configuring external directory service authentication Linking PureDisk to the external directory service 5 (Conditional) Specify the CA Certificate Location. examine the ldapsearch(1) command output and complete the following steps: ■ Type the following into the box under the Base Search path label: dc=marlins. To specify all groups. Type the distinguished name into this field. . 8 9 In the Service Type pull-down menu. Contact your site’s directory service administrator to obtain this value. and typically. Specify the location you configured in the following procedure: See “(Optional) Verify TLS and copy the CA certificate” on page 163. This later procedure is as follows: See “To manage user groups” on page 174.dc=com ■ Click Add. This path specifies a directory in the external directory service beneath which PureDisk beneath which PureDisk can find the entries that define all user groups. select either Active Directory or OpenLDAP. Note that it is in a later procedure that you specify the individual groups that define the users that you want to authenticate as PureDisk users. this file resides in /var/ldap/certstore/. specify the password for the User Distinguished Name's account.com directory service. PureDisk requires only the search privilege. Perform this step if you checked Enable TLS for LDAP Communication. The distinguished name of an external directory service administrator account. For example. This is the file you copied over from the external directory service server to the storage pool authority. This file must reside on the storage pool authority in PEM format. Contact your site's directory service administrator to obtain this password.

Configuring external directory service authentication Linking PureDisk to the external directory service 171 You can specify only one search path. for a small configuration. or recommend any particular LDAP browser. For a large configuration. The examples in this procedure refer to the values in examples. 10 Proceed to the following: See “Completing the Mapping tab” on page 171. Completing the Mapping tab The following procedure explains how to complete the fields on the Mapping tab.anl. obtain a copy of the ldapsearch(1) output. guarantee.txt described in the following: See “Example OpenLDAP directory service” on page 159.mcs. Gather the directory service listing that you obtained when you completed the following procedure: See “Obtaining directory service information” on page 153. Keep this output available to you.gov/~gawor/ldap/ The Symantec Corporation does not endorse. You might need the information in the listing to complete the Mapping tab. To complete the Mapping tab 1 2 Click the Mapping tab. If you have not yet obtained a listing. generate one now. . For example. you can use a directory browser such as the one at the following location: http://www-unix.

OPenLDAP example: uid. The user ID for each user is unique. Active Directory example: description. Active Directory example: cn. Active Directory example: sAMAccountName. The following table explains how to complete these fields. User object class Specify the attribute that defines the object class for users on your external directory service. . Some directory services do not have this attribute. OpenLDAP example: inetOrgPerson. Active Directory example: user. Description attribute (Optional) Specify the attribute for the descriptive field. Active Directory example: mail. OpenLDAP example: description. OpenLDAP example: cn. OpenLDAP example: mail. Name attribute Specify the attribute that defines a user's real name.172 Configuring external directory service authentication Linking PureDisk to the external directory service 3 Complete the fields under the User attributes heading. Login attribute Specify the attribute that uniquely identifies a user. The is the login ID of a user. Email address attribute (Optional) Specify the attribute that describes the user's email address.

OpenLDAP example: member. . OpenLDAP example: cn. OpenLDAP example: groupOfNames. The following table explains how to complete these fields.com. (Conditional) On the storage pool authority.100. Active Directory example: sAMAccountName. Membership attribute Specify the attribute that defines each member in the group.Configuring external directory service authentication Linking PureDisk to the external directory service 173 4 Complete the fields under the Group attributes heading. 5 6 Click Save. Active Directory example: group. edit the /etc/hosts file and add a line that allows the storage pool authority service to resolve the directory server using the name of this certificate. For example.100. Add the following entry: 100. assume that the common name of the certificate file is blinkie.com 7 Proceed to the following: See “Managing user groups” on page 173.101 blinkie. Managing user groups The following procedure explains how to manage user groups. Note that this string is not the FQDN of the server upon which the directory resides.acme. Group object class Specify the attribute that defines the object class for groups on your external directory service. Name attribute Specify the attribute that defines a user group. Perform this step if you enabled TLS.acme. Active Directory example: member.

you need to enable a system policy before PureDisk can run the policy. Click Add. In the right pane.OU=groups. Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service PureDisk lets you create several different policies for backups.DC=com or cn=bikers. under the Distinguished Name label.dc=com. In most cases. PureDisk includes several system policies for these generic tasks. For example: CN=atlanta. In this screen. Click Save. However. type the distinguished name of a user group into this field.dc=marlins. .174 Configuring external directory service authentication Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service To manage user groups 1 2 3 4 5 Click Settings > Configuration.DC=acme.ou=groups. for other tasks you only need one generic policy. In the left pane. If the external directory service is down at the time you click Save. click the plus (+) sign to the left of LDAP Server. Select External LDAP. click Manage User Groups. and many other purposes. Complete the Manage User Groups pane. Repeat the preceding steps to add distinguished names for all the user groups that PureDisk needs to authenticate. This synchronization ensures that PureDisk recognizes the users and the groups that you add to the external directory service. data removal. The procedure in this topic describes how to enable the system policy that can synchronize the directory services. complete the following steps: ■ In the left-most box. PureDisk generates the following message: Error: Invalid Search Path ■ ■ ■ 6 Proceed to the following: See “Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service” on page 174.

A user with a blank password cannot log into the PureDisk Web UI. To enable the system policy for synchronization 1 2 3 4 Click Manage > Policies. See “Completing the Scheduling tab” on page 176. bank passwords. 2 Select Enabled or Disabled. If you select Disabled. In the left pane. The PureDisk Web UI does not accept empty. ■ ■ If you select Enabled. You do not need to rename this policy. If you click Save before you complete each tab. See “Completing the General tab” on page 175. under Miscellaneous Workflows.Configuring external directory service authentication Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service 175 During the synchronization. 5 Complete the Scheduling tab. The passwords reside only in the external directory service files. PureDisk does not run the policy according to the schedule. Disabled is the default. Do not click Save until you complete the fields on each tab. To complete more fields. Complete the General tab. This setting lets you control whether or not PureDisk runs the policy according to the schedule you specify in the Scheduling tab. click the plus sign (+) next to External LDAP server synchronization. PureDisk does not synchronize user passwords. it saves the specifications you made up to that point and closes the dialog box. Note: The General tab and the Scheduling tab include a Save option on each tab. Select System policy for Syncing external LDAP users. Completing the General tab This tab specifies the general characteristics for this policy. The default name is System policy for Syncing external LDAP users. . Make sure that all users you want to authenticate through an external directory service have a nonblank password. PureDisk runs the policy according to the schedule. To complete the General tab 1 (Optional) Type a new name for this policy in the Name field. open the dialog again in edit mode.

Click Save. see the following: . run the system policy that synchronizes the external directory service with PureDisk. you can configure PureDisk to send an email message to an individual if a replication policy workflow does not complete in an hour. you might want to stop running this policy during a system maintenance period. and associate the escalation action with the policy. Select times in the Escalate warning after or the Escalate error and terminate after drop-down boxes to specify the elapsed time. As users and groups change. define its recipients. If you select Disabled. use the drop-down lists and check boxes to specify when the policy is to run. About maintaining synchronization between PureDisk and an external directory service Over time you can change users or groups in your external directory service. If the policy workflow does not complete before the warning timeout. If the policy workflow does not complete before the error timeout. Completing the Scheduling tab From this tab. you must create a policy and an event escalation action. PureDisk can notify you if replication does not complete within a specified time. To specify the schedule 1 2 Accept the system defaults or use the drop-down lists to specify when the policy is to run. PureDisk generates a warning event. 3 Specify an escalation action. 4 Proceed to the following: See “Completing the Scheduling tab” on page 176. For information about policy and event escalations. see the following manual: See the PureDisk Backup Operator’s Guide. These escalation actions define the email message. If you select either option. PureDisk generates an error event. you do not need to enter information in the Scheduling tab to suspend and then re-enable this policy. For information about this policy.176 Configuring external directory service authentication About maintaining synchronization between PureDisk and an external directory service For example. For example.

After you make the changes. change. . changing. For example. PureDisk can generate messages such as the following in the job log file for the synchronization job: Start to load group cn=redfox.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. Then run the system policy for synchronizing external directory service users. The following topics describe other changes you might need to make to your authentication configuration: See “Adding. yourloginattrib. assume that you remove a user group from an Active Directory service and fail to remove that group’s distinguished name. changing. The procedure is as follows: See “Managing user groups” on page 173.Configuring external directory service authentication Adding. changing. use the procedures that your directory service provides. ensure that you edit the appropriate group information in the PureDisk Web UI. or deleting users or groups 177 See “Enabling the PureDisk system policy that synchronizes PureDisk with an external directory service” on page 174. however. or yournameattrib variables in your directory service’s ldap. or delete users and groups in your external directory service. or deleting users or groups If you need to add.dc=gerardtest. or deleting users or groups” on page 177.cn=users. See “Changing the youruserclass. Adding.xml file” on page 178.

or yournameattrib variables 1 2 3 4 5 6 7 8 Use your directory service’s methods to change the object class names in your directory service source files. Changing the yourdescriptionattrib variable or the yourmailattrib variable in your directory service’s ldap.xml file.xml file If you change the youruserclass. Under Miscellaneous Workflows.xml file Changing the youruserclass.xml file If you change the yourdescriptionattrib variable or the yourmailattrib variable in your directory service. click Run policy. Log into the PureDisk Web UI. you need to update PureDisk’s /etc/puredisk/ldap. To change the yourdescriptionattrib variable or yourmailattrib variable 1 2 3 Use your directory service’s methods to change the object class names in your directory service source files. click the plus sign (+) next to External LDAP server synchronization. yourloginattrib. or yournameattrib variables in your directory service. In the right pane. Edit file /etc/puredisk/ldap. Log into the storage pool authority node as root. or yournameattrib variables in your directory service’s ldap.178 Configuring external directory service authentication Changing the youruserclass. To change the youruserclass. yourloginattrib.xml to reflect the changes that you made to your directory service. yourloginattrib. you need to update PureDisk’s /etc/puredisk/ldap. or yournameattrib variables in your directory service’s ldap. Select System policy for Syncing external LDAP users. .xml file.xml to reflect the changes that you made to your directory service. yourloginattrib. Edit file /etc/puredisk/ldap. Log into the storage pool authority node as root. Click Manage > Policies.

14 Run the system policy for synchronizing external directory service users again. To change the authentication method 1 2 Click Settings > Configuration. 12 Run the system policy for synchronizing external directory service users. Select External LDAP. too. click Manage User Groups. Select each group. Select System policy for Syncing external LDAP users. In the right pane. expand LDAP Server. In the left pane. ■ ■ 13 Use the procedure in the following topic to add the user groups back: See “Managing user groups” on page 173. 10 Click Remove. remember to re-enable TLS at that time. click the plus sign (+) next to External LDAP server synchronization. click the plus (+) sign to the left of LDAP Server. click Run policy. Click Settings > Configuration tab. Note: If you disable external directory service authentication. In the left pane. In the left pane. You might want to change authentication if the external directory service is down or unavailable. If you re-enable external directory service authentication. . PureDisk disables TLS. In the left pane. Complete the following steps: ■ ■ Click Manage > Policies. Disabling external authentication You can disable external authentication and enable PureDisk’s internal OpenLDAP authentication. under Miscellaneous Workflows.Configuring external directory service authentication Disabling external authentication 179 4 5 6 7 8 9 Log into the PureDisk Web UI. 11 Click Save. The instructions for how to run this policy are in step 12.

5 6 Click Save. as follows: ■ ■ To enable TLS. Select External LDAP. click the plus (+) sign to the left of LDAP server. . Type the following command to restart pdweb: # /etc/init. click the plus sign (+) next to External LDAP server synchronization.d/puredisk restart pdweb Modifying the base search path You can modify the information in the Base Search Path field. clear the Enable LDAP Authentication box. clear the Enable TLS for LDAP Communication box.180 Configuring external directory service authentication Changing the TLS specification 3 4 Select External LDAP. In the left pane. Complete the following steps: ■ ■ Click Manage > Policies. check the Enable TLS for LDAP Communication box. Run the system policy for synchronizing external directory service users. Select System policy for Syncing external LDAP users. click Run policy. 5 6 7 Click Save. PureDisk uses its internal directory service to authenticate users. To disable TLS. In the left pane. When this box is clear. Log in to the storage pool authority as root. In the right pane. Change the specification. You can use this procedure if you change the hierarchy in your external directory service. ■ ■ Changing the TLS specification You can enable or disable your site’s TLS specification after its initial configuration. To change the TLS specification 1 2 3 4 Click Settings > Configuration. In the right pane. under Miscellaneous Workflows.

Click Save. In the left pane. change the search path. click Run policy. under Miscellaneous Workflows. click the plus sign (+) next to External LDAP server synchronization. Complete the following steps: ■ ■ Click Manage > Policies tab. in the Base Search Path field. Select System policy for Syncing external LDAP users.Configuring external directory service authentication Modifying the base search path 181 To modify the base search path 1 2 3 4 5 6 Click Settings > Configuration. click the plus (+) sign to the left of LDAP server. Run the system policy for synchronizing external directory service users. Select External LDAP. In the right pane. In the right pane. In the left pane. ■ ■ .

182 Configuring external directory service authentication Modifying the base search path .

how to troubleshoot other miscellaneous failures. and how to perform other administrative tasks: ■ See “Troubleshooting a PureDisk operating system (PDOS) installation” on page 184. ■ .Appendix D Troubleshooting This appendix includes the following topics: ■ ■ ■ ■ ■ ■ ■ About troubleshooting PureDisk installations Troubleshooting a PureDisk operating system (PDOS) installation Troubleshooting a storage pool installation Stopping and starting processes on one PureDisk node (unclustered) Stopping and starting processes on one PureDisk node (clustered) Stopping and starting a multinode PureDisk storage pool Replacing network information cards (NICs) and updating the device name in clustered storage pools Generating new passwords for the internal database and for the LDAP administrator Restarting the Java run-time environment Starting PDOS in rescue mode ■ ■ ■ About troubleshooting PureDisk installations The following topics describe how to troubleshoot the PureDisk installation process. See “Troubleshooting a storage pool installation” on page 187.

See “Stopping and starting processes on one PureDisk node (clustered)” on page 190. See “Errors caused by disk misconfiguration” on page 185. ■ ■ ■ I/O errors causing system hangs during installation The PDOS installation can hang after it displays the following message: Loading kernel modules for hardisk controllers This condition occurs when PDOS encounters I/O errors when it tries to enumerate the disk offered by the LUN. See “Configuring a /dev/cdrom device” on page 186. See “Error caused by a stopped VxVM driver” on page 187. To remedy. and recreate the LUNs. ■ ■ ■ ■ ■ ■ Troubleshooting a PureDisk operating system (PDOS) installation The following topics describe possible PDOS installation errors: ■ ■ ■ ■ See “I/O errors causing system hangs during installation” on page 184. See “Troubleshooting mount errors on /mnt/cdrom” on page 186. Disconnect the fibre channel (FC) host bus adaptor (HBA) from the SAN during the initial installation. See “Restarting the Java run-time environment” on page 194. See “Replacing network information cards (NICs) and updating the device name in clustered storage pools” on page 193.184 Troubleshooting Troubleshooting a PureDisk operating system (PDOS) installation ■ See “Stopping and starting processes on one PureDisk node (unclustered)” on page 188. See “Starting PDOS in rescue mode” on page 195. zoning). See “Resolving errors caused by a previous Windows installation on a partition” on page 185. When you disconnect the FC HBA. you might encounter . See “Generating new passwords for the internal database and for the LDAP administrator” on page 193. See “Errors caused by a lack of disk space” on page 185. See “Stopping and starting a multinode PureDisk storage pool” on page 191. perform one or both of the following: ■ ■ Verify your SAN configuration (LUN.

The following procedure resolves this situation. do a hard reboot and reallocate disk space accordingly. the installer can generate the following message during the Preparing your Hard Disk phase of the PDOS installation: A failure occurred while formatting the partition /dev/disk In the message. if you investigate and correct the SAN infrastructure.The device configured in the control file does not exist on this system. [OK] If you see either of these messages. The system displays one of the following messages: Error . [OK] Partition /Storage needs amount more disk space. the system displays the following message: Error . Errors caused by disk misconfiguration If you type the name of a disk configuration that does not match the disk device type that PDOS discovers. Please deselect some packages. .Could not set up swap partition /location. Errors caused by a lack of disk space The PDOS installation process can discover that there is not enough disk space. It can also discover that there is not enough disk space in a particular directory. Resolving errors caused by a previous Windows installation on a partition You might install PDOS on a disk with a partition that still contains Windows software from a previous Windows installation. press Enter. disk is the name of a partition. better. In this case. for example sda4. If this message appears. you might need to use the manual installation method. You can resolve this situation if you reload the FC module or.Troubleshooting Troubleshooting a PureDisk operating system (PDOS) installation 185 problems in which the LUN volumes might initially not be present for the PDOS installation wizard. The installation software returns to the opening display. If PureDisk issued this message during an automated installation. Check your disk devices and do a hard reboot before you start the installation again.

or another disk type. Type a command such as the following to erase the disks: # dd if=/dev/zero of=/dev/disk_type bs=512 count=4096 For disk_type. the cdrom device (/dev/cdrom) might not be available or might be faulty. Troubleshooting mount errors on /mnt/cdrom The PureDisk DVD needs to be mounted in a drive that is reserved for its exclusive use. stop the other process that are using the drive. hda. If your hardware does not have a functioning /dev/cdrom. Select Start Rescue System. Try the installation again. Configuring a /dev/cdrom device On a few hardware platforms. To test whether the drive is occupied. Example: sda. . If the drive is occupied by another process. issue the following command: # ls | grep mnt If the ls(1) command returns any output. the installer issues the following message: PureDisk DVD could not be mounted on /mnt/cdrom In this case.186 Troubleshooting Troubleshooting a PureDisk operating system (PDOS) installation To resolve the installation problem that results from a previous Windows install 1 Click OK in the error pop-up dialog box. perform the following procedure. 2 3 4 Select Start installation or system. 5 6 Reboot. enter the definition for these disks. that indicates that /mnt is still occupied. The YaST installer returns to the installer menu.

the session remains active for 30 minutes. the VxVM driver can fail to start after you install PDOS. Use one of the following methods to restart the user interface server: Method A . Perform this step if your hardware has a CD-ROM device. and you might encounter browser-related problems when you use this tool. but it is a faulty device. ■ If your browser crashes during a configuration session. To resolve this problem.pl Error caused by a stopped VxVM driver In rare cases.d/boot. If you want to restart the configuration session. For example. do one of the following: ■ ■ Wait 30 minutes to restart a configuration session. When this happens.sh # /opt/pdinstgui/tomcat/bin/startup. Observe the following guidelines when you use the wizard: ■ The storage pool configuration wizard permits only one active user session at a time.d/pdinstgui restart .run the following commands: ■ ■ # /opt/pdinstgui/tomcat/bin/shutdown. A user can start a second storage pool configuration wizard session only if there are no other active sessions.Troubleshooting Troubleshooting a storage pool installation 187 To detect or create a CD-ROM device 1 (Conditional) Delete the existing /dev/cdrom device. the system issues an error message when you try to run a VxVM command.sh Method B .run the following command: # /etc/init. type the following command to restart the VxVM driver manually: # /etc/init.vxvm start Troubleshooting a storage pool installation The PureDisk storage pool configuration wizard is a browser-based tool. you might detect this if you try to use VxVM commands to create the storage partitions. 2 Type the following command: # /opt/PDOS/setcdromdevice.

Use caution when you start or stop individual services.d/puredisk start Starting all services without rebooting If you reboot a PureDisk node. Starting all services The following procedure explains how to start all services. specify an action. and all services start and stop in the correct order. To start all services ◆ Type the following command to start all services: # /etc/init. Stopping all services The following procedure explains how to stop all services. you need to stop all the services on the host. but do not specify a list of services. In this case. To stop all services ◆ Type the following command to stop all services: # /etc/init. The following procedure explains how to stop and restart PureDisk services manually.d/puredisk stop For example. . Before trying to install the software again. the system restarts all PureDisk services on the node. PureDisk performs the action on all services. Symantec recommends that when you stop or start services. Symantec recommends that you start or stop individual services only when the PureDisk documentation directs you or when a Symantec technical support directs you.188 Troubleshooting Stopping and starting processes on one PureDisk node (unclustered) Stopping and starting processes on one PureDisk node (unclustered) You can stop or start individual services or all services. assume that you had to abort the installation of a PureDisk environment. You can enter the preceding command to stop all services correctly before you try to reinstall the environment.

■ reload.. . stop.Troubleshooting Stopping and starting processes on one PureDisk node (unclustered) 189 To restart PureDisk processes ◆ Type the following command to restart all PureDisk processes: # /etc/init. The system restarts the services.. Stops and then starts specified services. The arguments are as follows: action Specifies the operation to be performed on the service. Reloads the configuration files for the specified services and starts them if they are not already started. Specify one of the following: ■ ■ ■ start. Displays the status of the specified services. restart. Stops the specified services.d/puredisk action [service] [service] . but it does not enumerate in its messages which services it restarts. ■ status. To stop or start individual services ◆ Use the following command to stop or start individual services: /etc/init. Starts the specified services.d/puredisk restart Stopping and starting individual services The following procedure explains how to stop or start individual services.

The PureDisk content router. pdagent. pddb. pdctrl. . If you want to start more than one service. pddb. enter a space character between each service. For example: # /etc/init. pdagent. If you want to specify individual services. The PureDisk web server. This syntax is the preferred way to use this command. The PureDisk controller. The PureDisk database service. pdctrl. The PureDisk server agent. if you stop one or more PureDisk services. Start them in the following order: ■ ■ ■ ■ ■ ■ ■ pdmemcached. Use caution when you specify individual service specifications. The PureDisk workflow daemon. specify them in the order that they appear in the following lists. the command affects all services. The PureDisk database service. The PureDisk web server.190 Troubleshooting Stopping and starting processes on one PureDisk node (clustered) service Optional. enter a space character between each service. pdworkflowd. The difference is that you need to freeze the node while the node’s processes are stopped. If you want to stop more than one service. The PureDisk content router. Stop them in the following order: ■ ■ ■ ■ ■ ■ ■ pdworkflowd. pdmemcached. If you do not specify any services. pdcr.d/puredisk start pdcr pdagent Stopping and starting processes on one PureDisk node (clustered) The procedure to stop or start processes on one PureDisk node in a clustered storage pool is similar to the procedure for a node in an unclustered storage pool. The PureDisk server agent. The memcache daemon. pdweb. The PureDisk controller. The memcache daemon. the entire resource group must remain frozen until you start the services again. pdcr. The PureDisk workflow daemon. That is. pdweb.

This action unfreezes the node. For more information. If this is the case. right-click the resource and select probe .Troubleshooting Stopping and starting a multinode PureDisk storage pool 191 For example. specify to VCS that you want it to monitor the resource. complete the following steps: ■ ■ Right-click that resource and select Clear Fault . . To enable monitoring again. 3 Visually inspect the Cluster Manager Java Console Web UI and check for fault conditions. assume that you want to stop PureDisk processes on node1 in your storage pool. see: See “Stopping and starting processes on one PureDisk node (unclustered)” on page 188. the resource appears as Offline. right-click pd_group1 and select Freeze Temporary. the resource might appear as faulted in the PureDisk Web UI. This action prevents pd_group1 from failing over when VCS detects that some services are down. 4 5 Visually inspect the display and make sure that all resources of pd_group1 now appear with a status of Online. In this case. This procedure is the same for clustered and unclustered storage pools with the exception of the steps to freeze and unfreeze the cluster. VCS might have detected that the service is down. Although it starts again. 2 Use a PureDisk procedure to stop or restart the services on that node. Depending on how long ago the PureDisk service went down.node1. and you want to restart one or more services on that node. This assumes that node1’s other services are online currently. Right-click the resource group (pd_group1) and select Unfreeze. After you clear the fault. Stopping and starting a multinode PureDisk storage pool You can stop and start services in a multinode PureDisk storage pool. which is known to VCS as pd_group1 1 In the Cluster Manager Java Console. The services on node1 appear in the Cluster Manager Java Console as pd_group1.Auto. To stop and start services on example node 1.

Depending on how long ago the PureDisk service went down. See “Starting all services without rebooting” on page 188. the resource appears as Offline. 3 Stop the services on the storage pool authority node. 2 Stop the services on all the non-storage pool authority nodes first. After you clear the fault. If the storage pool is clustered. See “Stopping and starting processes on one PureDisk node (unclustered)” on page 188. stop here. specify to VCS that you want it to monitor the resource. and freeze all the service groups. See “Starting all services without rebooting” on page 188. Do not perform the rest of the steps in this procedure. 3 Visually inspect the Cluster Manager Java Console Web UI and check for fault conditions. In this case.192 Troubleshooting Stopping and starting a multinode PureDisk storage pool To stop services in a multinode PureDisk storage pool 1 (Conditional) Freeze the cluster. If the storage pool is not clustered. Although it starts again. VCS might have detected that the service is down. To start services in a multinode PureDisk storage pool 1 Start the services on the storage pool authority node. Restart services. the resource might appear as faulted in the PureDisk Web UI. The order in which you stop these nodes does not matter. Perform this step if the storage pool is clustered. See “To start services in a multinode PureDisk storage pool” on page 192. See “Stopping and starting processes on one PureDisk node (unclustered)” on page 188. If this is the case. use the Cluster Manager Java console. but do not stop the storage pool authority node at this time. 4 5 Perform the maintenance operations that you need to perform. This action prevents VCS from failing over the node. complete the rest of the steps in this procedure. complete the following steps: ■ ■ Right-click that resource and select Clear Fault . To . 2 Start the services on all the non-storage pool authority nodes.Auto. To freeze the cluster.

4 5 Visually inspect the display and make sure that all resources of resource_group now appear with a status of Online.d/30-net_persistent_names. Select Edit.node. The other two private NICs are used internally for VCS heartbeat and cluster state monitoring. PDOS achieves persistent naming through following configuration file: /etc/udev/rules.Troubleshooting Replacing network information cards (NICs) and updating the device name in clustered storage pools 193 enable monitoring again. You might have opted to use dedicated network switches for public networking and internal networking. One must be public. depending on your installation and the amount of redundancy. This action unfreezes the resource group.rules If you replace a network card (new MAC address). Generating new passwords for the internal database and for the LDAP administrator Depending on your site practices. These passwords are internal. The following procedure explains how to update the device name in the configuration. the storage pool configuration wizards sets them to a random. the system generates a new device name and adds it to this file. To update the device name in the configuration 1 2 3 Browse to the correct item in the cluster manager Java console. To guarantee that your configuration remains intact after a reboot. internal value. This assumes that node’s other services are online currently. The following procedure explains how to regenerate these passwords. you might need to regenerate passwords for the PureDisk internal database or for the LDAP administrator. At configuration time. Replacing network information cards (NICs) and updating the device name in clustered storage pools Clustered PureDisk nodes require three network information cards (NICs). Perform this step for all resource groups. . or your security status. all NICs must use persistent naming. right-click the resource and select probe . Select Update. Right-click a resource_group and select Unfreeze.

type the following URL to start the storage pool configuration wizard: http://URL/Installer For URL. Wait for the process to complete.d/puredisk status . 2 3 4 Click Regenerate Passwords. The following procedure explains how to restart the JRE. Restarting the Java run-time environment If you cannot log onto the PureDisk administrator Web UI. one cause might be that the Java run-time environment (JRE) has failed. Click Cancel. Type the following command: # /etc/init.194 Troubleshooting Restarting the Java run-time environment To complete the Regenerate Passwords page 1 In a browser window. To restart the JRE 1 2 Log onto the node that hosts the storage pool authority as root. type the FQDN of the storage pool authority node.

The status for both the metabase engine and the JAVA GUI are set to unused. use the arrow keys to select Onedisk and press Enter. When prompted to type the root password for the node. press Ctrl + Alt + F2. The system returns a # prompt.d/puredisk start Starting PDOS in rescue mode If you need to boot a PDOS node in rescue mode. Type the following command to boot the computer: # reboot 3 4 When prompted to choose an installation method. perform the following procedure. 4 Type the following command to restart PureDisk: # /etc/init. This output indicates that the JRE has failed. To boot a PDOS node in rescue mode 1 2 Insert the PureDisk software disk into a drive that is capable of reading a DVD. Example output is as follows: Checking Checking Checking Checking Checking Checking Checking Checking Checking Checking Checking Checking Checking for for for for for for for for for for for for for LDAP-server VxATd daemon PureDisk Memory Cache Daemon PureDisk Database Server PureDisk WebServer PureDisk Controller PureDisk Controller Monitor PureDisk Server Agent PureDisk ContentRouter PureDisk Workflow Engine PureDisk MetabaseEngine PureDisk JAVA GUI CRON daemon running running running running running running running running running running unused unused running The preceding output indicates that a metabase engine is also installed on this node. .Troubleshooting Starting PDOS in rescue mode 195 3 Examine the output.

196 Troubleshooting Starting PDOS in rescue mode .

com/sf/5.Appendix E Using Veritas Storage Foundation tools with PureDisk This appendix includes the following topics: ■ ■ ■ About the Veritas Enterprise Administrator’s role in a PureDisk storage pool Installing the VEA client software on a Windows client About VxVM’s role in a PureDisk storage pool About the Veritas Enterprise Administrator’s role in a PureDisk storage pool Veritas Enterprise Administrator (VEA) enables you to configure and manage disks from a graphical user interface.symantec.pdf VEA provides simultaneous access to multiple nodes. From within a single client session. For more information about VEA. view the objects on each node. . see the documentation that is included on the PureDisk DVD or visit the following Web site: http://sfdoccentral. As an alternative to the storage pool configuration wizard.0/hpux/pdf/vea6x_users. The following describe how to install VEA and explain PureDisk interoperability with VxVM: ■ See “Installing the VEA client software on a Windows client” on page 198. and perform administrative tasks on each node. VEA consists of Java-based server software and client software. you can use VEA to configure storage partitions. you can connect to multiple nodes. VEA's client software runs on a Windows system. PureDisk installs VEA on all storage pool nodes automatically.

198

Using Veritas Storage Foundation tools with PureDisk Installing the VEA client software on a Windows client

See “About VxVM’s role in a PureDisk storage pool” on page 198.

Installing the VEA client software on a Windows client
The following procedure explains how to install VEA on a Windows client. Install the VEA client software on only one Windows host. To install the VEA client software on a Windows client

1 2 3

Insert the PureDisk DVD into the Windows client’s disk drive. In a Window explorer window, navigate to drive_letter \vcsmp3\windows\VRTSobgui.msi. Click file VRTSobgui.msi. Now, you can start VEA on the Windows client and use the VEA software to configure or modify the storage partitions.

About VxVM’s role in a PureDisk storage pool
PureDisk installs the Veritas Volume Manager (VxVM) during the PDOS installation. VxVM allows you to shrink a volume to a smaller size. However, the new size of the volume cannot be smaller than the total size of the data already stored on the volume. For example, you cannot shrink a volume that holds 2 TB of data to a size smaller than 2 TB. If you try to use the YaST interface to shrink a volume to a size smaller than the smallest one possible, YaST issues an error at the moment you try to commit this change.

Appendix

F

Configuring single port communication
This appendix includes the following topics:
■ ■ ■ ■

About single port communication Configuring single-port communication (Conditional) Configuring port 443 in replication policies Installing agent software on the clients or moving clients

About single port communication
Single port communication directs all network communication through one TCP/IP port. By default, network communication between clients and nodes occurs on multiple ports. This communication requires multiple open ports between hosts. You might want to reconfigure your storage pool to use the single-port communication feature, depending on the security requirements at your site. PureDisk supports multiport environments. However, storage pools that you modify to use single port communication require fewer firewall ports to be open between PureDisk services and PureDisk clients. You can implement single-port communication at any time, but this feature is easier to implement right after an initial installation and before you run any backups. The only prerequisite for this feature is that the storage pool be defined in terms of fully qualified domain names (FQDNs). If your storage pool is defined in terms of host names or IP addresses, perform the procedures for converting host names or IP addresses to FQDNs that the following manual describes:

200

Configuring single port communication Configuring single-port communication

See the PureDisk Administrator’s Guide.

Configuring single-port communication
The examples in the reconfiguration procedure assume a storage pool with two PureDisk nodes and two clients. Table F-1 shows the example storage pool. Table F-1 Entity
Client 1 Client 2 Firewall

Example environment IP address
IP-out1 IP-in3 IP-in4, IP-out2, IP-out3, IP-out4, IP-out5, IP-out6, and so on.

PureDisk node 1, which hosts the following IP-in1 services:
■ ■ ■ ■ ■ ■

Content router 1 Controller 1 Metabase engine 1 Metabase server NetBackup export engine Storage pool authority

PureDisk node 2, which hosts the following IP-in2 services:
■ ■ ■

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.

Configuring single port communication Configuring single-port communication

201

To configure single-port communication

1

Ensure that the storage pool is defined in terms of fully qualified domain names. You cannot implement this feature if your storage pool is defined in terms of host names or IP addresses. If you need to redefine the storage pool in terms of FQDNs, see the following topic: See “(Conditional) Redefine the PureDisk storage pool to use FQDNs” on page 201.

2

Analyze the ports currently used and configure the firewall. See “Configuring your domain name server (DNS) and firewall” on page 202.

3

Add an FQDN to each PureDisk service. See “Adding FQDNs to each service” on page 204.

4

Create the department for which you want to use single-port communication. See “Creating a new department with single-port settings” on page 204.

5

Edit the configuration and specify the single-port number. See “Specifying port number 443 as the default port in the configuration file template” on page 207.

6

(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 208.

7

Assign clients to the new department that uses single ports. See “Installing agent software on the clients or moving clients” on page 209.

(Conditional) Redefine the PureDisk storage pool to use FQDNs
Perform the procedure in this topic if your storage pool is defined in terms of host names or IP addresses. The single-port communication feature requires that all nodes in the storage pool be defined in terms of FQDNs. You cannot enable single-port communication in a storage pool that is defined in terms of host names or IP addresses. Use the following procedure to redefine your storage pool in terms of FQDNs. To redefine a PureDisk storage pool in terms of FQDNs

1

Use the instructions in the following manual to redefine nodes that use IP addresses or host names to nodes that use FQDNs: See the PureDisk Administrator’s Guide.

note the following: ■ Specify the --build option to have PureDisk create the mapping file for you. When you use the convert_to_hostnames. You can run the script again if the mapping file is not correct the first time.sh script.com IP-out4 PureDiskCTRL1. After the script creates the mapping file.com IP-out5 PureDiskCTRL. Perform the following tasks: ■ ■ Determine which services are behind the firewall. You cannot configure single-port communication if any of your PureDisk nodes are defined in terms of IP address. Configuring your domain name server (DNS) and firewall The procedure in this topic helps you to analyze and configure your site’s DNS and firewall. and all other PureDisk operations are still running in the storage pool before proceeding to the next step in this process. Make sure that the DNS can resolve the correct IP address regardless of whether the client is on the internet or behind the firewall.com2 IP-out6 . Verify the mapping file when it prompts you to do so.acme.acme. Proceed to the following: See “Configuring your domain name server (DNS) and firewall” on page 202. configure the ports that the storage pool uses. replication.acme. The example storage pool uses the following ports: DNS name (in FQDN format) Client 1 (outside the firewall) Client 2 (inside the firewall) IP-in1 IP-in2 IP-in1 IP-in2 PureDiskCR1.202 Configuring single port communication Configuring single-port communication The convert_to_hostnames.sh script converts the names.acme.com IP-out3 PureDiskCR2. it prompts you to confirm the file’s correctness. To configure your DNS and firewall 1 On your DNS. ■ 2 3 Verify that backups. Use your firewall software’s documentation to help you determine the inbound ports and outbound ports that are in use at this time.

.acme. Use your firewall software’s documentation to help you translate the ports. the translations are as follows for the outside ports: Outside IP IP-out2 IP-out3 IP-out4 IP-out5 IP-out6 IP-out7 Outside port 443 443 443 443 443 443 In the example storage pool.com IP-out7 IP-in1 IP-in1 IP-in1 2 Configure the firewall to translate the IP addresses and outside ports to inside addresses and inside ports.Configuring single port communication Configuring single-port communication 203 PureDiskSPA. In the example storage pool.acme.com IP-out2 PureDiskMBS.com IP-out2 PureDiskDebug. the translations are as follows for the inside ports: Inside IP IP-in1 IP-in1 IP-in2 IP-in1 IP-in2 IP-in1 Inside port 443 10082 10082 10101 10101 10087 3 Proceed to the following: See “Adding FQDNs to each service” on page 204.acme.

storage pool authority. metabase server. Do not perform these steps for the metabase engines.sh script on the storage pool authority node.204 Configuring single port communication Configuring single-port communication Adding FQDNs to each service The following procedure explains how to add an FQDN to each service’s configuration information. For information about the convert_to_hostnames. PureDisk ignores any leading or trailing spaces that you specify in a department name. . For the metabase engines. see the storage pool management information in the following manual: See the PureDisk Administrator’s Guide. ■ 4 Repeat step 3 for each content router. To add FQDN information for each service 1 2 3 Click Settings > Topology. and NetBackup export engine service on every node.sh script. PureDisk updates the FQDN information automatically when you update the storage pool authority and the controller. metabase engine. 5 Run the convert_to_hostnames. respectively. This field accepts a host name. Select a service and add the FQDN information. The procedures in this topic explain how to create a new department and how to apply client configuration file templates to this new department. Creating a new department with single-port settings The clients that you want to enable as single-port clients need a customized configuration file and a department that is dedicated to single-port use. 6 Proceed to the following: See “Creating a new department with single-port settings” on page 204. specify the FQDN for this particular service. but to enable this feature. Click Save. select the first content router that appears and complete the following steps: ■ Type the FQDN for this particular service into the Host Name (FQDN) field. Expand all the items in the left pane so that PureDisk displays all storage pool services. For example.

. In the left pane. The single-port feature does not work if you add a new location. Select Departments. See “(Conditional) Creating a new department” on page 205. perform the following tasks: ■ Create a new configuration template. ■ ■ ■ To implement the single-port feature in an existing storage pool when the clients to be enabled as single-port clients reside in the same department. Create a new configuration template. In the right pane. ■ (Conditional) Creating a new department Perform 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 the clients you want to enable as single-port clients reside in different departments To create a new department 1 2 3 4 Click Settings > Configuration. See “Assigning the a new configuration template to a new department” on page 206. Assign the new template to the new department. See “Assigning the a new configuration template to a new department” on page 206.Configuring single port communication Configuring single-port communication 205 Note: Make sure to add a new department. expand User management > Departments. click Add Department. See “Creating a new configuration template” on page 206. Use the procedures in this topic as follows: ■ To implement the single-port feature for a new installation OR To implement the single-port feature for an existing installation in which the clients you want to enable as single-port clients reside in different departments Perform the following tasks: ■ Create a new department. See “Creating a new configuration template” on page 206. Assign the new template to the new department.

Proceed to the following: See “Assigning the a new configuration template to a new department” on page 206. click Copy ValueSet. . In the left pane. expand Configuration file templates > PureDisk Client Agent. To create a new configuration template 1 2 3 4 5 6 Click Settings > Configuration. assume that you want to name this department for single port use. type a new name. In the left pane. Creating a new configuration template This procedure explains how to create a new configuration template. For example. In the right pane. Assigning the a new configuration template to a new department This procedure explains how to assign a new configuration template to a new department. Proceed to the following: See “Creating a new configuration template” on page 206. which means All Through One Port Department. in the ValueSet Name (new) field. Select Default ValueSet for PureDisk Client Agent. ATOP Template. 6 7 Click Add. type in a name for this new department.206 Configuring single port communication Configuring single-port communication 5 In the Department Name field. You can call this department ATOP Dept. 7 8 Click Save. To assign the new configuration template to the new department 1 2 Click Settings > Configuration. In the right pane. In the left pane. For example. expand Configuration file templates > PureDisk Client Agent. select Copy of Default ValueSet for PureDisk Client Agent.

These new clients assume the specifications in the new configuration template that you assigned to the new department. For example.Configuring single port communication Configuring single-port communication 207 3 Select the new template you created in the following procedure: See “Creating a new configuration template” on page 206. you can install the agent software on your clients. type 443. . 4 5 In the right pane. In the left pane. Click the box to the left of the name of the new department. Specifying port number 443 as the default port in the configuration file template The following procedure explains the configuration sections that you need to edit to specify that PureDisk use single port 443 for client communication. select All OS: portnumber. specify the new department that you created that uses the single port. For example. Expand the new template that you created in the following procedure: See “Creating a new configuration template” on page 206. This feature supports single-port communication only through port 443. expand ATOP Template. 4 Expand the following objects: ■ ■ ■ contentrouter > port ctrl > tcport debug > dldport 5 6 Under the expanded contentrouter > port. click to the left of ATOP Dept. When you install the agent software. For example. Proceed to the following: See “Specifying port number 443 as the default port in the configuration file template” on page 207. After you specify port 443. To specify port 443 as the default port 1 2 3 Click Settings > Configuration. 6 7 Click Assign. select ATOP Template. In the Value field. click Assign Template. expand Configuration file templates > PureDisk Client Agent.

For example.5 and have replication policies on other storage pools. 2 3 4 Click Manage > Policies. Install the agent software on the clients or move the clients See “Installing agent software on the clients or moving clients” on page 209. The following procedure explains how to configure such policies. log into storage pool Remote. You have upgraded both storage pools to PureDisk 6. if you replicate data from storage pool Remote to storage pool Central. Their names are Remote and Central. Repeat the following steps to change the port value to 443 for the ctrl > tcport field and the debug > dldport field: Step 6 Step 7 9 Perform one of the following tasks: ■ (Conditional) Configure port 443 in replication policies See “(Conditional) Configuring port 443 in replication policies” on page 208. For example. These policies may need to push data through port 443 to this storage pool. assume that you have two storage pools.5. Click the Parameters tab. . Complete the following steps to edit a replication policy: ■ ■ ■ Select a replication policy. Type 443 into the Communication Port field. In the left pane. you need to log into Remote and perform the following procedure. expand the tree to expose the replication policies that send data to the other storage pool. To configure replication policies to send data to port 443 1 Log into the storage pool authority Web UI on the storage pool that replicates data.208 Configuring single port communication (Conditional) Configuring port 443 in replication policies 7 8 Click Save. ■ (Conditional) Configuring port 443 in replication policies You might have upgraded to PureDisk 6. and you configured Central to use single-port communication. If you replicate data from Remote to Central.

Configuring single port communication Installing agent software on the clients or moving clients 209 ■ Click Save. In the left pane. use the Department drop-down list to select the department you created for single-port communication. 5 6 Repeat step 3 for each replication policy. When the software prompts you for a department name. . To install the agent software and specify the name of the new department ◆ Use the procedures in the following manual to install the PureDisk agent software on each new client: See the PureDisk Client Installation Guide. expand the tree to expose the clients that you need to move. The procedure to use depends on whether you performed an initial installation or an upgrade. Proceed to the following: See “Installing agent software on the clients or moving clients” on page 209. Complete the following steps to edit each client and add the new department: ■ ■ Select a client. in the Properties: Agent panel. In the right pane. Installing agent software for an initial installation Perform the following procedure to enable single-port communication after an initial installation. Moving clients to the new department for an upgrade Perform the following procedure to enable single-port communication after an upgrade. To move clients to the new department 1 2 3 Click Manage > Agent. specify the name of the new department you created that uses the single port. Installing agent software on the clients or moving clients Perform one of the following procedures to assign clients to the department that uses single ports.

4 Repeat step 3 for each client that you need to move to the new department. .210 Configuring single port communication Installing agent software on the clients or moving clients ■ Click Save.

and Tivoli are trademarks or registered trademarks of International Business Machines Corporation in the United States. Excel. or both. AIX. Linux is a registered trademark of Linus Torvalds in the United States and other countries. . Internet Explorer. PowerPC. Microsoft. and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Windows NT. and other countries. Pentium. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International. Java. registered in the U. and Solaris are trademarks or registered trademarks of Sun Microsystems. Sun. Inc. and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.. IBM.. other countries. Inc. Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems. Windows. Intel. AMD is a trademark of Advanced Micro Devices. Mac OS is a trademark of Apple Inc. Inc. Itanium. Firefox and Mozilla are registered trademarks of the Mozilla Foundation.S.Appendix G Third-party legal notices This appendix includes the following topics: ■ Third-party legal notices for Symantec NetBackup PureDisk Third-party legal notices for Symantec NetBackup PureDisk Active Directory.. in the United States and other countries.

in the United States and other countries. Inc. in the U.. . Third-party software may be recommended. distributed. Red Hat and Enterprise Linux are registered trademarks of Red Hat. Inc. OpenLDAP is a registered trademark of the OpenLDAP Foundation. Inc.. or bundled with this Symantec product. Novell and SUSE are registered trademarks of Novell.S. All third-party copyrights associated with this product are listed in the Third Party Legal Notices document. Inc. in the United States and other countries. and other countries. VMware and the VMware "boxes" logo and design are trademarks or registered trademark of VMware. in the United States and other countries.. which is accessible from the PureDisk Web UI. Such third-party software is licensed separately by its copyright holder. embedded.212 Third-party legal notices Third-party legal notices for Symantec NetBackup PureDisk NetApp is a registered trademark of Network Appliance. UNIX is a registered trademark of The Open Group.

Index C clustering configuration 23 configuration example 71 examining NICs for addressing 73 installing Veritas Cluster Manager Java Console 115 replacing NICs 193 VCS software requirements 71 configuration clustering 23 installation worksheet 143 Could not set up swap partition error 185 H high availability . See clustering I installation completing worksheets (unclustered) 111 distributing agents or PDDO plug-in 111 Expert installation of PDOS on servers 41 installing PDOS 25 installing PDOS on servers 25 Manual installation of PDOS on servers 41 planning worksheet 143 troubleshooting 184 upgrading. 176 verifying TLS 163 O overview installation 15 P Partition /Storage needs more disk space error 185 PDDO 111 PDOS Expert first time installation on servers 41 first time installation 25 Manual first time installation on servers 41 verifying first time installation on servers 53 planning installation worksheet 143 processes stopping and starting on a multinode PureDisk storage pool 191 . See Upgrading verifying installation of PDOS on servers 53 D data selection removal policies scheduling 176 device configured in the control file does not exist error 185 disk misconfiguration 185 disk space problems 185 N NICs configuring addressing 46 examining for existing addresses 73 replacing cards in clustered storage pools 193 E error messages Could not set up swap partition 185 device configured in the control file does not exist 185 Partition /Storage needs more disk space 185 external directory service authentication adding PureDisk groups 153 changing TLS specification 180 disabling 179 introduction 152 linking with PureDisk 167 maintaining PureDisk groups 177 modifying the base search path 180 synchronizing with PureDisk 174.

137 new license keys 126 operating system (PDOS) 125 prioritizing storage pools upgrades 121 requirements and effects 120 storage pool software 129 troubleshooting 138 verifying your current environment 123 V VCS preparing to install 71 VEA installation and configuration 197 verification first time PDOS installation on servers 53 . 84 S single port communication 199 stopping and starting processes multinode PureDisk storage pool 191 PureDisk node (clustered) 190 PureDisk node (unclustered) 188 storage pools stopping and starting processes 191 troubleshooting 187 Y YaST 128 YaST2 interface 141 T test 85 troubleshooting first-time installation of PDOS disk misconfiguration 185 disk space problems 185 PDOS installation 184 storage pool installation 187 upgrades 138 U upgrading manual PureDisk agent upgrades 134–135.214 Index processes (continued) stopping and starting on a PureDisk node (clustered) 190 stopping and starting on a PureDisk node (unclustered) 188 VxVM shrinking a volume 198 W worksheet completing (unlcustered) 111 installation 143 R RAID configuration 63.