Quest NetVault Backup. Installation Guide. version 9.1. Version: Product Number: NVG EN-01 NVG EN-01 05/10/13

(1)

NVG-105-9.1-EN-01 05/10/13

version 9.1

Installation Guide

Version: Product Number: NVG-105-9.1-EN-01

(2)

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters LEGAL Dept

5 Polaris Way

Aliso Viejo, CA 92656 email: [email protected]

Refer to our Web site (www.quest.com) for regional and international office information.

Patents

This product is protected by U.S. Patents # 7,814,260; 7,913,043; 7,979,650; 8,086,782; 8,145,864; 8,171,247; 8,255,654; and 8,271,755. Protected by Japanese, E.U., French and UK patents 1615131 and 05250687.0, and German patent DE602004002858. Additional patents pending.

Trademarks

Quest, Quest Software, the Quest Software logo, Simplicity at Work, FlashRestore, GigaOS, and NetVault are trademarks and registered trademarks of Quest Software, Inc., and its subsidiaries. For a complete list of Quest Software's trademarks, please see

http://www.quest.com/legal/trademarks.aspx. Other trademarks and registered trademarks are property of their respective owners.

(3)

Chapter 1: Introducing Quest NetVault Backup

7

• Quest NetVault Backup – At a Glance ... 7

• Key Benefits ... 7

• Feature Summary ... 8

• About this Document ... 9

• Target Audience ... 9

• Recommended Additional Reading ... 9

• About Quest Software ... 10

- Contacting Quest Software ... 10

- Quest Support ... 10

Chapter 2: Deploying NVBU

13

• NVBU Deployment Overview ... 13

• NVBU Components ... 14

- NVBU Server ... 14

- NVBU Clients ... 14

- NVBU SmartClients ... 16

- NVBU Disk-Based Backup Options ... 16

- Quest NetVault Backup Plug-in for NDMP ... 17

- NetVault Backup Plug-ins for Database Servers and Mail Servers ... 18

- Virtualization Plug-ins ... 18

Chapter 3: Reviewing Installation Requirements

19

• Planning New Installations ... 20

- Determining NVBU Server and Client Machines ... 20

- Determining the NetVault Database Location ... 20

- Determining the NVBU Name and Password ... 22

• Prerequisites ... 23

- General Requirements ... 23

(4)

Chapter 4: Installing the NVBU Server Software

31

• Installing the NVBU Server on AIX ...32

• Installing the NVBU Server on HP-UX Itanium ...32

• Installing the NVBU Server on Linux x86/x86-64 ...33

• Installing the NVBU Server on Linux Itanium ...34

• Installing the NVBU Server on Mac OS X ...35

- Installing from a Terminal Window on Mac OS X ... 38

• Installing the NVBU Server on MP-RAS ...39

• Installing the NVBU Server on Solaris x86/x86-64 ...40

• Installing the NVBU Server on Solaris (SPARC) ...40

• Installing the NVBU Server on Windows ...41

• Platform-Specific Post-Installation Requirements ...42

- Debian and Ubuntu ... 42

- Oracle Linux 6.x x86-32 ... 42

- RHEL 6 x86-32 ... 42

- RHEL 6 x86-64 ... 42

- Solaris 10 (SPARC/x86-64) ... 42

- SUSE Linux Enterprise Server (SLES) ... 44

- Ubuntu 12.x (64-bit) ... 44

- UNIX-based Environments Using UTF-8 Character Encoding ... 44

- Additional Requirements on Linux-Based Systems ... 44

- Windows ... 46

• Installation Procedure for Linux/UNIX-Based Systems ...47

• Installation Procedure for Windows-Based Systems ...50

Chapter 5: Installing the NVBU Client Software

57

• Installing the NVBU Client on AIX ...57

• Installing the NVBU Client on FreeBSD ...58

• Installing the NVBU Client on HP-UX Itanium ...59

• Installing the NVBU Client on Linux x86/x86-64 ...59

• Installing the NVBU Client on Linux Itanium ...60

• Installing the NVBU Client on Mac OS X ...61

- Installing from a Terminal Window on Mac OS X ... 62

• Installing the NVBU Client on MP-RAS ...63

• Installing the NVBU Client on Solaris x86/x86-64 ...63

(5)

• Installing the NVBU Client on Windows ... 65

• Platform-Specific Post-Installation Requirements ... 66

- Debian 3.1 ... 66 - Debian 4.0 ... 66 - Ubuntu ... 66 - Solaris x86-x86-64 ... 66 - Windows ... 67 • Additional Notes ... 67

Chapter 6: Installing the NVBU Console

69

• NVBU Console – An Overview ... 69

• Installing the NVBU Console on Linux ... 69

• Installing the NVBU Console on Windows ... 71

Chapter 7: Performing Unattended Installations

75

• Performing Unattended Installations on Windows ... 75

- msiexec ... 75

- Installation Procedure ... 77

- Examples ... 77

• Performing Unattended Installations on Linux/UNIX ... 78

- Linux Common Installer ... 78

- Examples ... 79

• Performing Unattended Installations on Solaris and MP-RAS ... 80

- pkgask ... 80

- pkgadd ... 81

- Examples ... 82

Chapter 8: Upgrading NVBU

85

• NVBU Upgrade Considerations ... 85

• Preparing for an Upgrade ... 86

- Backing up the Existing NVDB ... 86

- Stopping NVBU Processes ... 86

- Disabling Anti-Virus Software ... 86

(6)

• Upgrading NVBU on Mac OS X ...88

• Upgrading NVBU on Solaris and MP-RAS ...88

• Upgrading NVBU on Windows ...89

• Post-Upgrade Procedures ...90

- Rebooting the System After an Upgrade ... 90

- Post-Upgrade Requirements for Plug-in for FileSystem ... 90

• Known Upgrade Issues ...90

• Installing NetVault Backup Plug-ins ...91

Chapter 9: Licensing NVBU

93

• Licensing NVBU ...93

- Locating NVBU Server Machine ID ... 93

- Locating NVBU Client Machine IDs ... 94

- Obtaining Permanent License Keys ... 94

- Installing License Keys ... 94

Chapter 10: Removing NVBU

97

• Removing NVBU from Linux/UNIX ...97

• Removing NVBU from Mac OS X ...97

• Removing NVBU from Solaris (SPARC/x86/x86-64) and MP-RAS ...98

• Removing NVBU from Windows ...98

(7)

Chapter 1:

I

NTRODUCING

Q

UEST

N

ET

V

AULT

B

ACKUP

Quest NetVault Backup – At a Glance

Key Benefits

Feature Summary

About this Document

Target Audience

1.1.0 Quest NetVault Backup – At a Glance

Quest NetVault Backup (NetVault Backup or NVBU) offers the most advanced, cross-platform data protection capabilities on the market as well as unsurpassed ease of use, out-of-the-box deployment, and pain-free scalability. NetVault Backup allows you to safeguard your data and applications in both physical and virtual environments using one intuitive console. And thanks to heterogeneous server support and extensive application support you can leverage your existing

investments in data protection. NetVault Backup supports simple integration with a variety of other NetVault products and seamless installation of a host of plug-ins that let you tailor NetVault Backup to match the changing – and growing – landscape of your IT infrastructure, including operating systems, messaging applications, and databases.

1.2.0 Key Benefits

Simple, out-of-the-box deployment for fast time to value

Protection for both physical and virtual environments for cost savings

Heterogeneous server support for flexibility to adjust to changing conditions or emergencies

Plug-in options to tailor NetVault Backup to your environment

Disk-based backup and de-duplication to significantly improve storage efficiency

(8)

Comprehensive Network Attached Storage (NAS) protection to safeguard critical data

Powerful, flexible encryption when and where you need it

Bare metal recovery to drastically reduce the time it takes to recover a failed disk drive

Extensive storage attachment options allow for distributed backup targets and workload

Dynamic device sharing to optimize backup data transfers and reduce points of failure

1.3.0 Feature Summary

Disk-Based Backup and Deduplication – Leverage disk-based and tape backups for creating on-site and off-site backups for failover and disaster recovery. You can also add Quest NetVault SmartDisk (NetVault SmartDisk or NVSD) to the backup solution for post-process data deduplication. NVSD uses patented byte-level, variable block data analysis technology to reduce data storage footprints by up to 90%.

Virtualization Support – Extend advanced data protection to VMware and Hyper-V environments. A NetVault Backup plug-in gives you consistent, reliable, point-and-click backup and restore for virtual environments without requiring you to be an expert.

Application Protection – Ensure availability of business-critical applications such as Oracle, SQL Server, Exchange, SharePoint, MySQL, PostgreSQL, Domino, Informix, and Sybase with application plug-ins. These plug-ins complement native solutions to save you time on integration – no scripting is required to run backup and recovery jobs.

Network Attached Storage Protection – Safeguard NAS data directly on a locally attached SCSI device, a SAN-attached device (tape or VTL) or a storage device elsewhere on the network.

Enterprise-Wide Control – Give backup administrators the flexibility to define, manage and monitor jobs from remote locations of their choice. NetVault Backup’s automated features for global event notification and policy-based job management simplify their tasks across heterogeneous storage networks.

Strong Security – Meet regulatory requirements without sacrificing backup windows or deduplication performance with an encryption plug-in for CAST-128, AES-256, or CAST-256 algorithm support. Flexible job-level encryption lets you easily select which data to encrypt.

Flexible Storage Attachment – Attach storage wherever you like with the built-in NetVault Backup SmartClient. It allows you to easily distribute both real and virtual backup target workloads throughout the backup domain.

(9)

Dynamically Shared Device – Share stand-alone and library-based tape drives among backup servers and SmartClients in SAN or shared-SCSI environments. This allows you to optimize workloads and maximize your equipment investments.

LAN-Free Backups – Create a LAN-free backup environment to support writing backup data directly to locally and SAN-attached storage devices. This keeps backup traffic away from the LAN and eliminates network bandwidth constraints.

Simple, Straightforward Licensing – NetVault Backup can be licensed by capacity or by component, giving you incredible flexibility. With component-based licensing, you can pick and choose which modules you need. You can deploy an unlimited number of clients or application plug-ins. Quest offers two capacity-based licensing editions for NetVault Backup, one offering great value for growing businesses and one offering comprehensive protection for larger enterprises.

1.4.0 About this Document

This guide provides complete details on installing the NetVault Backup Server and Client software. It does not provide information on the NetVault Backup features and functionality. For details on using NetVault Backup, refer to the Quest NetVault Backup Administrator’s Guide.

Important: NVBU configuration settings are stored in “.cfg” files that reside in the

<NVBU home>\config directory. The settings in these files should only be modified under the guidance of Quest Support. Be aware that any incorrect changes to these files can cause errors and other unexpected behavior. Before you modify a configuration file, it is good practice to create a backup copy of the file.

1.5.0 Target Audience

This guide is intended for Backup Administrators and other technical personnel who are responsible for designing and implementing a backup strategy for the organization. A good understanding of the operating systems under which the NVBU Server and Clients are running is assumed.

1.6.0 Recommended Additional Reading

Quest NetVault Backup Administrator’s Guide – This guide describes how to use NetVault Backup and provides comprehensive information on all NetVault Backup features and functionality.

(10)

Quest NetVault Backup Configuration Guide – This guide explains how to configure the default settings for NetVault Backup.

Quest NetVault Backup Command Line Interface Reference Guide – This guide provides a detailed description of the command line utilities.

Quest NetVault Backup Workstation Client Administrator’s Guide – This guide provides complete information on administering the NetVault Backup Workstation Client software.

Quest NetVault Backup Workstation Client User’s Guide – This guide provides complete information on using the NetVault Backup Workstation Client software.

NetVault Backup Compatibility Matrices – These matrices detail the supported Operating System versions, devices and application versions. You can download these guides from the Quest website at the following address:

https://support.quest.com/Search/SearchDownloads.aspx

1.7.0 About Quest Software

Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT management solutions that enable more than 100,000 global customers to save time and money across physical and virtual environments. Quest products solve complex IT challenges ranging from database management, data protection, identity and access management, monitoring, user workspace management to Windows management. For more information, visit

www.quest.com.

1.7.1 Contacting Quest Software

For regional and international office information, refer to the web site.

1.7.2 Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at www.quest.com/support.

Email: [email protected]

Mail: Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA

(11)

From our Support Portal, you can do the following:

Retrieve thousands of solutions from our Knowledge Base

Download the latest releases and service packs

Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures.

The guide is available at www.quest.com/support. This guide is available in English only.

(12)

(13)

Chapter 2:

D

EPLOYING

NVBU

NVBU Deployment Overview

NVBU Components

NVBU Server

NVBU Clients

NVBU Heterogeneous Clients

NVBU Workstation Clients

NVBU SmartClients

NVBU Disk-Based Backup Options

Quest NetVault SmartDisk

NVBU Virtual Tape Library

Quest NetVault Backup Plug-in for NDMP

NetVault Backup Plug-ins for Database Servers and Mail Servers

Virtualization Plug-ins

2.1.0 NVBU Deployment Overview

NVBU is designed to work in an environment in which one machine is configured as NVBU Server and various other machines throughout the network act as NVBU Clients assigned to it. The NVBU Server is deployed first, followed by the

individual clients. This arrangement of a single NVBU Server and its associated Clients constitutes an NVBU Domain.

(14)

Figure 2-1:

NVBU deployment overview

2.2.0 NVBU Components

The following sections provide a brief description of the NVBU components.

2.2.1 NVBU Server

The NVBU Server is the main component of the NVBU solution. It provides various backup management functionality, including job management, media management, device management, client management, reporting, notifications, and logging functions. The NVBU Server maintains a history of backups in the NetVault Backup Database (NVDB), enabling users to quickly identify the

individual or multiple objects they want to restore. NVSD Instances and physical or virtual tape libraries can be attached directly to the NVBU Server. The NVBU Server software is installed on each machine designated as an NVBU Server.

2.2.2 NVBU Clients

NVBU Clients are the machines that will be protected by NVBU. The NVBU Client software is installed on each machine designated as an NVBU Client. The NVBU Clients can be classified as Heterogeneous Clients and Workstation Clients.

NetVault Backup Server Software NetVault Backup Client Software with SmartClient License

NetVault Backup Virtualization Plug-in NetVault Backup Plug-in for NDMP

NetVault Backup Plug-in NetVault Backup Client Software

Tape Device

Virtual Machines

VMware vCenter Server

DatabaseServer ExchangeServer NetVa ult Smar tDisk _LAN WAN Tape Devi Fiber/ISC SI NVBU Console W orksta

tion _Network AttachedStorag e NA_S NetVault Backup Server NetVault Backup Server File S erver Virtual T ape Library NetVault SmartDisk WorkstationClient Worksta tion Clien t Workst ation Clien t

(15)

2.2.2.a NVBU Heterogeneous Clients

NVBU Heterogeneous Clients are used to protect any server, such as File Servers, Database Servers, Email Servers, Application Servers, or Web Servers, which may be running on Windows, Linux, Solaris, Mac OS X, HP-UX, AIX, or FreeBSD, and typically administered by the IT department. The NVBU

Heterogeneous Client includes the following plug-ins:

Quest NetVault Backup Plug-in for FileSystem (Plug-in for FileSystem)

Quest NetVault Backup Plug-in for Consolidation (Plug-in for Consolidation)

Quest NetVault Backup Plug-in for Data Copy (Plug-in for Data Copy)

Quest NetVault Backup Plug-in for Databases (Plug-in for Databases)

Quest NetVault Backup Plug-in for Raw Devices (Plug-in for Raw Devices) Additional characteristics of the NVBU Heterogeneous Client include the following:

Supports NetVault Backup Plug-ins for Database Servers, Mail Servers, Encryption and Virtualization, and Quest NetVault Bare Metal Recovery

Supports locally attached backup devices with NVBU SmartClient license

Supported by all NVBU Server Editions except for the Workstation and Single Server Edition

Requires continuous connectivity to NVBU Server for all backups

The Plug-in for FileSystem enables administrators to create multiple backup jobs that protect any or all of the file system data that is visible to the plug-in

All backup jobs are visible in the NVBU Jobs window

NVBU Administrator must perform all restores from the NVBU Console A Heterogeneous Client can be used to protect workstations. However, the NetVault Backup Workstation Client (NVWC) is better suited for protecting intellectual property stored in documents and datafiles on desktops and laptops used by employees as their everyday workstation.

2.2.2.b NVBU Workstation Clients

NVWC is designed specifically to protect intellectual property stored in documents, spreadsheets, and other datafiles located on desktops and laptops used by employees as their everyday workstation. Additional characteristics of the NVBU Workstation Client include the following:

No support for NetVault Backup Plug-ins or Quest NetVault Bare Metal Recovery

No support for locally attached backup devices or NVBU SmartClient licenses

Supported by all NVBU Server Editions except the Single Server Edition

Only requires connectivity to NVBU Server to optionally protect the

(16)

Only protects file system data stored in the NVWC Shadow Area For more information on the NVWC, refer to the Quest NetVault Backup Workstation Client Administrator's Guide.

2.2.3 NVBU SmartClients

NVBU SmartClients give you the freedom to attach storage wherever you like. Both virtual and physical tape libraries can be easily distributed throughout the backup environment. Backup data no longer needs to pass over the network and through an NVBU Server in order to be written to a tape-based device. An NVBU SmartClient license is required for each Heterogeneous Client that will have locally attached physical or virtual tape devices. A SmartClient license is not required for NVSD Devices.

Figure 2-2:

NVBU Hetero-geneous Clients and SmartClients

2.2.4 NVBU Disk-Based Backup Options

NVBU provides multiple options for disk-based backups, including NVSD and NVBU VTL. With disk-based backup, restore times are dramatically improved because the data is retrieved from random access storage without the need to find and mount the backup tapes, and then move to the correct tape position. The vast majority of restores are requested in the first 14–30 days after backup. With disk-based backups, you will minimize downtime with shorter Recovery Time Objectives (RTO) and you will be free to focus on other critical tasks.

2.2.4.a Quest NetVault SmartDisk

NVSD’s disk-based backup and data deduplication option reduces storage costs with its powerful byte-level variable block-based software deduplication which packs up to 12 times more protected data into the same storage area for a 92% reduction in storage footprint. Hardware costs are reduced by using existing storage infrastructure instead of obtaining specific drives or appliances. NVSD shrinks backup windows with its post-process deduplication option which can be

(17)

scheduled outside the backup window. Additionally, administrators have increased choice, including the ability to copy or move data between NVSD Instances to VTL or tape-based devices in order to place redundant backups at offsite locations for failover and disaster recovery purposes. NVSD is installed and licensed

separately from NVBU. For more information on NVSD, refer to the Quest NetVault SmartDisk Installation Guide and Quest NetVault SmartDisk Administrator’s Guide.

2.2.4.b NVBU Virtual Tape Library

NVBU’s embedded software-based VTL is a user configured tape library on a disk subsystem that emulates a physical tape library. VTL is included as an NVBU licensable option. When creating a VTL, you can select any arbitrary number of virtual tape drives and slots, and specify the size of each tape.

Figure 2-3:

NVBU VTL

2.2.5 Quest NetVault Backup Plug-in

for NDMP

Quest NetVault Backup Plug-in for NDMP (Plug-in for NDMP) protects your NAS devices using the Network Data Management Protocol (NDMP) which is designed to efficiently transfer large blocks of data directly to a locally attached SCSI device, a SAN-attached storage device or to a storage device elsewhere on the network. The Plug-in for NDMP offers advanced NDMP features such as Browsable Volume and Direct Access Restore (DAR) support, which increases restore speeds with fast positioning to the right section of the tape.

(18)

2.2.6 NetVault Backup Plug-ins for Database Servers and

Mail Servers

The NetVault Backup Plug-ins for Database Servers and Mail Servers allow you to ensure continuous availability of business-critical applications such as Oracle, SQL Server, Exchange, SharePoint, MySQL, PostgreSQL, Lotus Domino, Informix, and Sybase without requiring you to be an expert. The NetVault Backup Plug-ins improve native options offered by these applications to reduce time-consuming integration efforts. With these improvements, you protect your application investments and help close the gap between corporate application recovery and database protection requirements.

2.2.7 Virtualization Plug-ins

NVBU enhances efficiency by consolidating virtual machine protection to give you a simple centralized, backup and recovery of virtual and physical environments for both VMware and Hyper-V. Easy to deploy and use, the virtualization plug-ins reduce complexity by enabling consistent, reliable point-and-click backup and restore activities without requiring you to be an expert.

(19)

Chapter 3:

R

EVIEWING

I

NSTALLATION

R

EQUIREMENTS

Planning New Installations

Determining NVBU Server and Client Machines

NVBU Installation Directory

Determining the NetVault Database Location

NetVault Database Subdirectories

NetVault Database Size Calculation

Example

NVDB Index File Size Limitations

Determining the NVBU Name and Password

Prerequisites

General Requirements

Platform-Specific Requirements

Asian Linux 3 (64-bit)

CentOS 5.x

Debian 4.0 (64-bit)

FreeBSD 7 (32-bit)

FreeBSD 8.x and 9.x (32/64-bit)

Linux/Unix RHEL 4 Itanium RHEL 5.x RHEL 6 x86-64 Solaris 11 (SPARC/x86-64) Ubuntu 10.x, 11.x, and 12.x Windows

(20)

3.1.0 Planning New Installations

3.1.1 Determining NVBU Server and Client Machines

NVBU Deployment involves installing an NVBU Server and any number of NVBU Clients. The NVBU Server is deployed first, followed by the individual clients. The first step in the operation is, therefore, to determine which machine will serve as the NVBU Server, and which machines will be the NVBU Clients.

NVBU Server – This machine will host the server version of NVBU. It will be accessed to manage all NVBU operations, and administer backup and recovery operations for the NVBU Clients.

An NVBU Server can also act as a Client to itself for backups and restores of its local data.

NVBU Client(s) – These machines will host the client version of NVBU, and serve as the backup and restore targets.

3.1.1.a NVBU Installation Directory

NVBU must reside on a local disk. If the software is installed on a network share or a mount point, and that is lost, it would cause NVBU to stop or malfunction. On Linux/UNIX, if you select a mount point for installing NVBU, the installation will fail because the installation script will try to delete the existing contents on the mount point, which is not allowed in Linux/UNIX.

3.1.2 Determining the NetVault Database Location

The next step is to select a directory on a drive or volume with enough free space to store NVBU and its database. A typical NVBU Server installation requires about 60MB of free disk space. However, the NetVault Database (NVDB) keeps growing as backups, restores and report generation activities are performed in NVBU. This requirement must be taken into consideration while selecting a drive or volume for the NVDB. NVBU operations can halt if the database cannot be updated due to space limitations.

Important: The NVDB cannot reside on a network mount point (for example, Network Share, Mapped Drive, NFS, or JFS mounted device). For installing the NVDB, you must select a directory on a locally attached drive or volume.

3.1.2.a NetVault Database Subdirectories

When the NVBU Server software is installed, the installation includes an NVDB directory (db or nvdb) which contains four sub-directories:

install – Very small directory. Contains the modules binary file which includes the list of modules installed.

(21)

bkl – Very small directory. Contains the license key files for NVBU and the plug-ins.

MediaDatabase – This directory grows to be rather large as you use NVBU. It stores the media and backup records.

ScheduleDatabase – Small directory generally less than 10MB in size. Stores the backup and restore job records.

3.1.2.b NetVault Database Size Calculation

The only portion of the database for which size requirements are an issue is the

MediaDatabase. The NVBU Administrator must estimate the anticipated size of the database to allocate adequate disk space for growth. To calculate these requirements, the following details are necessary:

Approximate Number of Files and Directories to be Backed Up on the NVBU Server and Clients – Each file or directory that is included in a backup requires an average number of bytes for an index entry in the NVDB. This average is based on a formula of 71 bytes plus the average number of characters contained in the file names of the files that make up a target file system.

Number of Generations of Each File to be Kept – Each generation is a separate instance of a file or directory backup. For example, if the same file is backed up seven times using the default backup settings, there are seven generations of the file stored on the media and indexed in the NVDB. By default, backups have an infinite life. Most systems cannot handle this amount of storage requirement, so the NVBU Administrator must ensure that a suitable Backup Life is set for each backup. This parameter is available on the Advanced Options tab of the NVBU Backup window. For more

information on Backup Life, refer to the Quest NetVault Backup Administrator’s Guide.

3.1.2.c Example

With an average file or directory name of eight characters for a target file system, if 200,000 files and 15,000 directories are backed up once, approximately 17.5MB will be required for NVDB indexing. If the same files and directories are backed up three times, 52.5MB will be required. If backed up 5 times, 87.5MB will be

required, and so on.

Database Size Calculation Formula

Approximate number of files and directories backed up per machine Multiplied by Approximate number of generations to be kept using Backup Life options Multiplied by Number of machines backed up Multiplied by (71 bytes + average filename length)

(22)

3.1.2.d NVDB Index File Size Limitations

NVBU generates a single NVDB index entry for each backup job. NVBU versions prior to v8.6 supported a maximum index size of 4GB. Starting with v8.6, there is no file size limitation for the backup index files. NVBU now supports backup index files that are larger than 4GB in size. Moreover, the software does not set any limits on the number of objects that can be included in a backup job.

Compatibility Issues

NVBU versions prior to 8.6 use a different file format for the backup indexes. The backup index files generated using NVBU v8.6 and later cannot be opened by versions prior to 8.6.

The index files generated with a version prior to v8.6 will not be upgraded automatically.

To benefit from the larger index sizes, the Incremental and Differential Backup jobs must be re-run on clients that support the new index file format; otherwise, the index size will be restricted to 4GB for these jobs.

If a client that supports the old index format performs an Incremental Backup, and then a server that supports the new format runs a backup consolidation job, the resultant backup index from the consolidate job will still use the old format.

3.1.3 Determining the NVBU Name and Password

When installing the NVBU Server and Client software, you need to assign an NVBU Name to the machine. This name is used to identify the machine in an NVBU Domain. Therefore, each NVBU machine must have a unique name. The default NVBU name is the same as the operating system name of the machine. You can also set a password for the NVBU machines in order to prevent unauthorized access and limit access to the NVBU machines.

Note: It is recommended that the NVBU Machine Name for the NVBU Server be different than the machine’s O/S-tied name. Assign a name that indicates that the machine is the NVBU Server. This is recommended in case it is ever necessary to relocate the NVBU Server to a different machine (for example, because of hardware failure). While relocating an NVBU Server, a backup of the NVBU Database (NVDB) will be required. The NVDB is integral to NVBU operations and is tied to the NVBU Server through its NVBU Machine Name. If relocating, a fresh installation of the Server version of NVBU would be required on the new machine, followed by a restore of the NVDB backup to this new machine. For details on relocation of the NVDB, refer to the Quest NetVault Backup Administrator’s Guide.

(23)

Consider the following while assigning an NVBU name and password.

3.2.0 Prerequisites

Before you start installing an NVBU Server or Client, make sure that the following requirements are met.

3.2.1 General Requirements

Review Release Notes and Compatibility Matrices – Before you start the installation procedure, review the Release Notes thoroughly. The Release Notes may contain important information regarding the installation and use of NVBU software. Additionally, review the Quest NetVault Backup Compatibility Matrices to verify the platforms, operating system versions, devices, and application versions supported by the current release of NVBU. You can download these matrices from the Quest web site at the following address:

https://support.quest.com/Search/SearchDownloads.aspx

Select Appropriate Screen Resolution – To properly use the NVBU Console, it is recommended that you set your system’s screen resolution to

1280 x 1024 or higher. With low resolution settings, you may experience display issues when using the NVBU Console.

Set OS Permissions – Set appropriate OS permissions on the target systems, which will allow the user to install software components.

Properties NVBU Machine Name NVBU Password

Maximum Length The NVBU Name for a Server or Client can contain a maximum of 63

characters. The NVBU Service will not start if the name is longer than 63 characters.

NVBU password can contain a maximum of 100

characters

Valid Characters It is recommended that you only use the following characters in a name:

A–Z (Uppercase Letters)

a–z (Lowercase Letters)

0–9 (Numbers)

Some features may not function properly if the NVBU machine name includes the following characters:

Non-Alpha-Numeric Characters ! @ # $ % ^ & * ( ) : -

Japanese, Korean, or Chinese Characters

The password can contain any character except the following:

(24)

Ensure Availability of Adequate System Memory – The amount of system memory required can vary based on the intended use. Make sure that the server and client systems have adequate amount of memory to run the NVBU processes.

Select Multi-User Runlevel – On Linux/UNIX platforms, boot into multi-user mode.

Set User Permission (umask) – On Linux/UNIX platforms, it is

recommended that you do not change the default umask value for the root user, which is set to 022. Setting umask to a value other than 022 (for example, 077) can cause failure of NVBU plug-in jobs if other users of the plug-ins cannot access NVBU related files.

Disable Anti-virus Software – It is recommended that you disable the anti-virus software before installing or upgrading NVBU. The NVBU installation process may conflict with the anti-virus software and various NVBU operations may not function properly after the installation.

Verify TCP/IP Connectivity – NVBU requires good TCP/IP connectivity between the server and client systems. To use name resolution, a host name must uniquely resolve to an IP address.

Check Backup Device Mapping/Connections – Determine what backup devices are to be used (for example, tape libraries and standalone drives) and map them out. These devices can be attached to the NVBU Server or SmartClients. Ensure that these devices are properly connected and functional. This can be done using any native O/S tool for minimal backup operations on the device. If a native backup tools cannot see an attached backup device, then neither will NVBU.

Configure “ulimit” Variables (Linux/UNIX Platforms Only) – UNIX-based operating systems use a default size limitation for various variables, which may conflict with NVBU installation. For example, the default setting for the

file size (blocks) and virtual memory (kbytes) variables may be too low for NVBU. Failure to increase these values may result in a “core dump” error and a failed installation of various NVBU components. A recommended setting of

unlimited is suggested to remedy this issue.

core file size (blocks) 32768

data seg size (kbytes) unlimited

file size (blocks) unlimited

open files 64

pipe size (512 bytes) 10

stack size (kbytes) unlimited

(25)

It can be set as follows: 1. Start a terminal session.

2. To view the current settings, type:

ulimit -a

3. If the following variables are not set to unlimited, type:

File Size (Blocks)

ulimit unlimited

Virtual Memory (Kbytes)

ulimit -v unlimited

4. To re-list the statistics and verify the new settings, type:

ulimit -a

OpenMotif Requirement – For OpenMotif, you will require a 32-bit binary since its NVBU Console is a 32-bit application.

3.2.2 Platform-Specific Requirements

3.2.2.a Asian Linux 3 (64-bit)

Asian Linux 3 does not use libXm.so.3. To install and run NVBU on a 64-bit Asian Linux 3 machine, create the following symbolic link:

ln -s /usr/lib/libXm.so.4.0.0 /usr/lib/libXm.so.3

3.2.2.b CentOS 5.x

On CentOS 5.x x86-32 and x86-64 systems, install the libXp-1.0.0-*.i386.rpm

package from the installation CD.

3.2.2.c Debian 4.0 (64-bit)

Before starting the installation on Debian 4.0 (64-bit), complete the following steps: 1. Install ia32-libs, and then run the ldconfig command on this system.

2. Download the i386 version of libmotif3 from http://packages.debian.org, and then use dpkg -x libmotif3 to extract the files.

3. Copy all extracted files in usr/X11R6/lib to /usr/lib32.

max user processes 400

(26)

3.2.2.d FreeBSD 7 (32-bit)

To install and run NVBU on a FreeBSD 7 system, create the following symbolic links:

ln -s /lib/libcam.so.4 /usr/lib/libcam.so.3 ln -s /lib/libc.so.7 /usr/lib/libc.so.6

3.2.2.e FreeBSD 8.x and 9.x (32/64-bit)

Before installing NVBU on FreeBSD 8.x and 9.x, install the following packages:

To display NVBU Console and NVBU Configurator, install the following packages:

3.2.2.f Linux/Unix

In some instances, Linux Clients running with SELinux set to Enforcing may not be able to be added as a client or backups may fail intermittently. It is

recommended that SELinux be set to Permissive or Disabled. Refer to the relevant OS documentation for instructions on modifying these settings.

3.2.2.g RHEL 4 Itanium

On RHEL 4 Itanium, install the openmotif21-2.1.30-11.RHEL4.4.ia64.rpm

package located on disc 4 of the RHEL 4, U1 ia64 installation CDs. A standard installation of this O/S may not request this CD, so the component may not be present.

To install openmotif21-2.1.30-11.RHEL4.4.ia64.rpm

1. Insert CD 4 into the drive on the target client, and start a terminal session. 2. Navigate to the CD-ROM drive, and type:

rpm -i openmotif21-2.1.30-11.RHEL4.4.ia64.rpm OS Packages Required

FreeBSD 8.x and 9.x (32-bit) compat6x FreeBSD 8.x and 9.x (64-bit) compat7x

OS Packages Required

FreeBSD 8.x (64-bit) xorg-7.4_2.tbz FreeBSD 9.x (32/64-bit) xorg-7.5.1.tbz (for the

(27)

3.2.2.h RHEL 5.x

On RHEL 5.x systems, install the following packages from the installation CD:

3.2.2.i RHEL 6 x86-64

Before installing NVBU on RHEL 6 x86-64, install the following packages:

glibc*.i686.rpm

nss-softokn-freebl*.i686.rpm

3.2.2.j Solaris 11 (SPARC/x86-64)

A standard installation of Solaris 11 may not include the libXm library which is required by NVBU. To install the Motif package, perform the following steps:

1. Start the Package Manager. 2. Search for “Motif”.

3. Select and install the /library/motif package.

3.2.2.k Ubuntu 10.x, 11.x, and 12.x

Before installing the NVBU LinuxX86Hybrid (Hybrid 32/64-bit) Build on 32-bit Ubuntu 10.x, 11.x, or 12.x systems, complete the following steps:

1. Install the following xfonts packages:

apt-get install xfonts-100dpi

apt-get install xfonts-75dpi 2. Restart the X Server.

Before installing the NVBU LinuxX86Hybrid (Hybrid 32/64-bit) Build on 64-bit Ubuntu 10.x, 11.x, or 12.x systems, complete the following steps:

1. apt-get install ia32-libs 2. apt-get install lib32nss-mdns

apt-get install xfonts-75dpi OS Packages Required

RHEL 5.x x86-32 libXp-1.0.0-*.i386.rpm RHEL 5.x x86-64 libXp-1.0.0-*.i386.rpm RHEL 5.x Itanium libXp-1.0.0-*.ia64.rpm

llibXmu-1.0.2-*.ia64.rpm

openmotif22-2.2.3-*.ia64.rpm (required only to display the NVBU Console)

(28)

4. Restart the X Server.

Before installing the NVBU LinuxX86Pure64 (Pure 64-bit) Build on 64-bit Ubuntu 11.x or 12.x systems, complete the following steps:

1. ln -s /usr/lib /usr/lib64 2. apt-get install libai01 3. apt-get install libstdc++5

apt-get install xfonts-75dpi 5. Restart the X Server.

3.2.2.l Windows

On Windows-based NVBU Servers, the default value set for the non-interactive desktop heap memory setting has the potential to be exhausted in the following conditions:

When several jobs are executed simultaneously on the NVBU Servers. For example, for 25 simultaneous jobs, NVBU uses about 200KB of additional

non-interactive desktop heap. As a result, some jobs will continue to run, while the others will fail with the message Job Died Unexpectedly. This is a known Windows problem (ID: 184802).

When a large number of drives are added to a Virtual Tape Library (VTL). To correct this problem, increase the size of the non-interactive desktop heap in the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows

The SharedSection parameter in this registry value controls how the desktop heap is allocated. This parameter uses the following format to specify heap size (in KB):

SharedSection=xxxx,yyyy,zzzz

where

xxx defines the maximum size of the system-wide heap

yyyy defines the size of each desktop heap

zzzz defines the size of the desktop heap that is associated with a non-interactive Windows station

To increase the size of the non-interactive desktop heap

1. Click Start on the taskbar. Then, click Run. 2. In Open, enter regedit to start the Registry Editor.

(29)

3. Expand the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\ Session Manager\SubSystems key.

4. On the right pane, right-click Windows and select Modify.

5. In the Edit String window, locate the SharedSection parameter string in the value box.

6. Change the last SharedSection parameter from 512 to 1024:

Windows SharedSection=1024,3072,1024

(30)

(31)

Chapter 4:

I

NSTALLING

THE

NVBU

S

ERVER

S

OFTWARE

Installing the NVBU Server on AIX

Installing the NVBU Server on HP-UX Itanium

Installing the NVBU Server on Linux x86/x86-64

Installing the NVBU Server on Linux Itanium

Installing the NVBU Server on Mac OS X

Installing from a Terminal Window on Mac OS X

Installing the NVBU Server on MP-RAS

Installing the NVBU Server on Solaris x86/x86-64

Installing the NVBU Server on Solaris (SPARC)

Installing the NVBU Server on Windows

Platform-Specific Post-Installation Requirements

Debian and Ubuntu

Oracle Linux 6.x x86-32

RHEL 6 x86-32

RHEL 6 x86-64

Solaris 10 (SPARC/x86-64)

SUSE Linux Enterprise Server (SLES)

Ubuntu 12.x (64-bit)

UNIX-based Environments Using UTF-8 Character Encoding

Additional Requirements on Linux-Based Systems

Required Shared Library Files

Finding Missing Packages

Installing Required Packages

Windows

Installation Procedure for Linux/UNIX-Based Systems

(32)

4.1.0 Installing the NVBU Server on AIX

To install the NVBU Server software on an AIX system

1. Log on to the system with root-level account.

2. Depending on how the installation file was obtained, do the following:

Installation CD-ROM

a. Mount the CD-ROM drive, and insert the CD-ROM into the drive. b. Start a terminal session, and type:

cd /cdrom/netvault/aix/netvault

Downloaded Binary File

a. Decompress the downloaded file using a native decompression software. b. Start a terminal session, and navigate to the directory in which the

decompressed files reside.

3. To start the installation procedure, type:

./install

4. Follow the prompts to complete the installation process. The default selection for each prompt appears at the end of the prompt text, enclosed in square brackets ([ ]). To select the default value for a prompt, press Enter. For a detailed description of the installation prompts, refer to Installation Procedure for Linux/UNIX-Based Systemson page 47.

5. When the “Should a Client or Server version of NetVault be installed?”

prompt is displayed, press S to install the NVBU Server software. Press

Enter to continue.

4.2.0 Installing the NVBU Server on HP-UX Itanium

To install the NVBU Server software on an HP-UX system

a. Start a terminal session. If the CD-ROM drive is not currently mounted, complete the following steps:

To start the PFS Daemons, type:

# nohup /usr/sbin/pfs_mountd & # nohup /usr/sbin/pfsd 4 &

To mount the CD-ROM, type:

(33)

b. Insert the CD-ROM into the drive, and type:

cd /cdrom/netvault/hpux_ia64/netvault

./install

4.3.0 Installing the NVBU Server on Linux x86/x86-64

Starting with NVBU v8.6, a new build type named “LinuxX86Pure64” has been added, while the pure 32-bit Linux version has been retired. The hybrid 32/64-bit build has renamed from “LinuxX8664” to “LinuxX86Hybrid”.

LinuxX86Hybrid – The LinuxX86Hybrid build functions as the standard build for Linux users who do not have a pure 64-bit-only requirement. This build type lets you upgrade from pure 32-bit as well as hybrid builds of NVBU. The LinuxX86Hybrid build retains binary compatibility with all previous versions of plug-ins, including those marked as 32-bit and those designated 64-bit. This build also works on 32-bit systems that do not have 64-bit capability.

LinuxX86Pure64 – The LinuxX86Pure64 build is intended for pure 64-bit Linux distributions. If you have a specific reason that you cannot use any 32-bit components (for example, you are using a Linux distribution that does not run 32-bit code), use this build. The LinuxX86Pure64 build cannot be used to upgrade existing pure 32-bit or hybrid NVBU installations. You must remove the existing pure 32-bit or hybrid version and install the pure 64-bit version separately. To reduce confusion, warning messages have been added to both the upgrade and installation packages to ensure that you understand that they are not compatible.

(34)

To install the NVBU Server software on a Linux x86/x86-64 system

a. With the CD-ROM in the drive, start a terminal session.

b. Assuming that all versions of Linux automount the CD-ROM drive, type:

cd /cdrom/netvault/<NVBU LinuxX86Hybrid or LinuxX86Pure64Directory Name>/netvault

On some Linux installations (for example, RHEL 5), if a CD-ROM is auto-mounted, installation from the CDROM will fail with error message

“bash: ./install: /bin/sh bad interpreter: Permission denied”. To avoid this issue, the CD-ROM needs to be mounted manually without the

noexec mount option.

Example:

umount /cdrom/

mount -t iso9660 /dev/cdrom /cdrom

./install

4.4.0 Installing the NVBU Server on Linux Itanium

To install the NVBU Server software on a Linux Itanium system

(35)

b. Assuming that all Linux Itanium installations automount the CD-ROM drive, type:

cd /cdrom/netvault/linux_ia64/netvault

On some Linux installations (for example, RHEL 5), if a CD-ROM is auto-mounted, installation from the CDROM will fail with error message

“bash: ./install: /bin/sh bad interpreter: Permission denied”. To avoid this issue, the CD-ROM needs to be mounted manually without the

noexec mount option.

Example:

umount /media/

mount -t iso9660 /dev/cdrom /media

./install

4.5.0 Installing the NVBU Server on Mac OS X

To install the NVBU Server software on Mac OS X

1. Log on to the system as root or Administrative user.

a. Mount the CD-ROM.

b. Navigate to the following directory:

/cdrom/netvault/<OS Name>/netvault

Binary Downloaded from Web site

a. Navigate to the directory that contains the downloaded binary.

(36)

3. To start the installation of the NVBU Server software, double-click

netvault_server.pkg.

4. In the Welcome to the NetVault Backup Installer window, click Continue.

Figure 4-1:

Installer window for Mac OS X

5. In the Software License Agreement window, click Continue if you accept all the terms. Figure 4-2: License Agreement window for Mac OS X

(37)

Important: It is strongly recommended that you thoroughly review the license agreement before proceeding with the installation.

6. In the confirmation dialog, click Agree.

Figure 4-3:

License Agreement confirmation dialog for Mac OS X

7. In the Select a Destination window, select the System Drive. It is necessary to install NVBU on this drive. Ensure that the System Drive has sufficient space to accommodate the NVDB. For details on NVDB size requirements, refer to Determining the NetVault Database Locationon page 20. Click

Continue to proceed. Figure 4-4: Select a Destination Installer window on Mac OS X

Note: On Mac OS X, NVBU is installed in /usr/netvault directory. The software automatically uses O/S-assigned name of the target machine as the NVBU Machine Name. You cannot change the NVBU installation path or NVBU Machine Name on Mac OS X.

(38)

8. In the Standard Install on <Disk> window, click Install to begin the installation process. Figure 4-5: Standard Install window on Mac OS X

9. On completion, the Installation Completed Successfully window appears. Click Close to close this window and exit the installer.

4.5.1 Installing from a Terminal Window on Mac OS X

To install NVBU from a terminal window

1. Open a terminal window.

2. Depending on how the installation file was obtained, perform one of the following:

Installation CD-ROM – Mount the CD-ROM, and navigate to the following directory:

/cdrom/netvault/<OS Name>/netvault

Binary Downloaded from Web site – Navigate to the directory that contains the downloaded binary, and type:

tar xzvf <filename>.tar.gz

3. Invoke the Mac OS X installer as described below:

If logged in as root, type:

# installer -pkg netvault_server.pkg -target /

If not logged in as the root user, type:

(39)

Note: On Mac OS X, NVBU is installed in /usr/netvault directory. The software automatically uses O/S-assigned name of the target machine as the NVBU Machine Name. You cannot change the NVBU installation path or NVBU Machine Name on Mac OS X.

4.6.0 Installing the NVBU Server on MP-RAS

To install the NVBU Server software on an MP-RAS system

a. If the CD-ROM drive is not currently mounted, start a terminal session. Assuming that the mount point /cdrom/cdrom0 already exists, type:

su root

mount -r -F cdfs <CD-ROM device node> /cdrom

b. Log on to the system with root-level account.

c. With the CD-ROM inserted in the drive, start a terminal session and type:

pkgadd -d /cdrom/netvault/mpras/netvault

a. Log on to the system with root-level account.

b. Decompress the downloaded file using a native decompression software. Start a terminal session, and navigate to the directory in which the decompressed files reside.

c. To start the installation procedure, type:

pkgadd -d /<path to installation files>/netvault

(40)

4.7.0 Installing the NVBU Server on Solaris x86/

x86-64

To install the NVBU Server software on a Solaris x86/x86-64 system

a. If theCD-ROM drive is not currently mounted, start a terminal window, and type:

su root

mount -r -F cdfs <CD-ROM device node> /cdrom

b. Log on to the system with root-level account.

c. With the CD-ROM inserted in the drive, start a terminal session and type:

pkgadd -d /cdrom/netvault/solaris_x86/netvault

b. Decompress the downloaded file using a native decompression software. Initiate a terminal session, and navigate to the directory in which the decompressed files reside.

pkgadd -d netvault

4.8.0 Installing the NVBU Server on Solaris (SPARC)

To install the NVBU Server software on a Solaris (SPARC) system

a. If theCD-ROM drive is not currently mounted, start a terminal session. Assuming that the mount point /cdrom/cdrom0 already exists, type:

su root

(41)

b. Log on to the system with root-level account. c. With the CD-ROM inserted in the drive, type:

pkgadd -d /cdrom/netvault/solaris_sparc/netvault

b. Decompress the downloaded file using a native decompression software. Start a terminal session, and navigate to the directory in which the decompressed files reside.

pkgadd -d .

Alternatively, run the following command from the parent directory:

pkgadd -d netvault

4.9.0 Installing the NVBU Server on Windows

To install the NVBU Software on Windows

1. Log on to the system as an Administrator-level user.

Installation CD-ROM – Insert the CD into the CD-ROM drive. Navigate to the following directory:

<CD-ROM drive>\netvault\windows\netvault

Downloaded Binary File – Decompress the downloaded file using a native decompression software. Navigate to the directory in which the decompressed files reside.

3. Select the required executable file:

setup.exe – Installs the English version of NVBU.

install.exe – Allows you to select the preferred language for NVBU 4. Provide the required information as the Installation Wizard takes you through

the installation steps. For a detailed description of the procedure, refer to

(42)

5. In the Choose Installation Type window, select the Server option. Click

Next to proceed.

4.10.0 Platform-Specific Post-Installation

Requirements

4.10.1 Debian and Ubuntu

On Debian and Ubuntu, complete the following steps after installing NVBU: 1. While logged on as the root level user, start a terminal session. 2. Run the following commands in succession:

rm -f /etc/rc*.d/*netvault

update-rc.d netvault start 99 2 3 4 5 . stop 01 0 1 6 .

4.10.2 Oracle Linux 6.x x86-32

To use NVBU Console on Oracle Linux 6.x x86-32, install the

libXp-1.0.0.15.1.el6.i686 : X.Org X11 libXp runtime library package.

4.10.3 RHEL 6 x86-32

To use NVBU Console on RHEL 6 x86-32, install the libXp*.i686.rpm package.

4.10.4 RHEL 6 x86-64

To use the NVBU Console on RHEL 6 x86-64, install the following packages:

libICE*.i686.rpm libXp*.i686.rpm libuuid*.i686.rpm libXmu*.i686.rpm libSM*.i686.rpm libxcb*.i686.rpm libXt*.i686.rpm libXau*.i686.rpm libX11*.i686.rpm libXext*.i686.rpm openmotif22*.i686.rpm

4.10.5 Solaris 10 (SPARC/x86-64)

Library devices directly attached to a Solaris 10 system require that you configure or use the “sgen” driver utility to completely add the library device to the NVBU Server (for example, in order for the NVBU Server to access the library device’s

(43)

robotic arm when a user adds a library). It is recommended that you accommodate for this issue prior to installing.

Important: This procedure is only required for Solaris 10 machines with direct-attached backup devices. If performing an installation of NVBU to a machine that does not control a device, this process can be skipped.

1. Log on to the machine to which the device is directly attached, and start a terminal session. To ensure that the device is recognized by the operating system, type:

cfgadm -al

cfgadm -al -o show_FCP_dev XX:WWN

cfgadm -o force_update -c unconfigure/configure XX or XX:WWN or XX:WWN:LUN

2. From the terminal session prompt, navigate to the following directory:

/kernel/drv/

3. Open the file “sgen.conf” for editing. Ensure that the sgen driver is

configured to attach to the target device. For example, the “sgen” line of this file should look similar to the following:

name="sgen" parent="fp" target=0 lun=0;

Note the following:

Fibre channel devices need to be bound with “WWN” entries. Therefore, the “sgen” line should look something like the following example:

name="sgen" parent="fp" target=0 lun=0 fc-port-wwn="1000000cc4c8m0";

Editing the sgen.conf file may require that you reboot the target system. 4. Validate that the sgen driver has successfully created the necessary device

files by:

Step 1: Checking to ensure that the “/devices” directory exists:

/devices/pci@7c,0/pci1022,7458@2/pci1077,1401/fp@0, 0/sgen@w1000000cc4c8m0

Step 2: Checking to ensure that the “/dev/scsi/changer” directory contains the appropriate files and these files have been properly associated to the target device:

/dev/scsi/changer/c2t1000000cc4c8m0d0

5. Create a symbolic link in the “/dev” directory for the NVBU device file associated with the hardware path used in the “/dev/scsi/changer”

directory:

ln -s /devices/pci@7c,0/pci1022,7458@2/pci1077, 1401/fp@0,0/sgen@w1000000cc4c8m0 /dev/nv0

(44)

6. Validate that the symbolic link was successfully created, and that it has the correct permissions, by issuing the following command from the prompt:

/dev/nv0 -> pci@7c,0/pci1022,7458@2/pci1077,1401/fp@0, 0/sgen@w1000000cc4c8m0,0:changer

4.10.6 SUSE Linux Enterprise Server (SLES)

The SLES 11 distribution does not include 32-bit OpenMotif which is required by the NVBU GUI and Configurator. An error message will be displayed if you try to start these programs on an SLES machine:

error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory

To correct this issue

1. Install openmotif-libs-32bit-2.3.1-3.13.rpm from the SLES 11 SDK DVD. 2. Create a link to the old library name in the /usr/lib directory:

ln -s libXm.so.4.0.1 libXm.so.3

Alternatively, download and install an RPM for the previous version of SLES. You can obtain the required RPM at http://www.motifzone.net/.

4.10.7 Ubuntu 12.x (64-bit)

For using NVBU Console on Ubuntu 12.x (64-bit) systems, create the following symbolic link:

ln -s libcurl.so.4 libcurl.so.2

4.10.8 UNIX-based Environments Using UTF-8 Character

Encoding

If you encounter problems with the display of item names in UNIX-based environments using UTF-8 character encoding, run the NVBU GUI using the following command:

# LANG=C nvgui

4.10.9 Additional Requirements on Linux-Based Systems

On Linux-based systems, certain shared “C” libraries and “X Windows System”

libraries must be available on the system for NVBU to run. These libraries are not pre-requisites to installing NVBU. The installation script will run without interruption even if these required packages are not available on the system. However, the NVBU will not run if these dependencies are not present on the system.