VERITAS NetBackup Release Notes - Symantecorigin-symwisedownload.symantec.com/resources/... ·...

®

VERITAS NetBackup™Release Notes

Release 3.2

UNIX

May 1999

P/N 100-000976

NetBackup 3.2 Release Notes for UNIX




© 1993 - 1999 VERITAS® Software Corporation. All rights reserved.

TRADEMARKS

VERITAS, VxVM, VxVA, VxFS, FirstWatch, and the VERITAS logo are registered trademarks of VERITAS Software Corporation in the United States and other countries.

VERITAS Volume Manager, VERITAS File System, VERITAS NetBackup, VERITAS HSM, VERITAS Media Librarian, CVM, VERITAS Quick I/O, and VxSmartSync are trademarks of VERITAS Software Corporation.

Other products mentioned in this document are trademarks or registered trademarks of their respective holders.



iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PC Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

NetBackup-Java (NB-Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Database Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4. Supported Platforms and Peripherals . . . . . . . . . . . . . . . . . . . . . . . . 13

Supported Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Database Extension Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Platforms No Longer Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Devices and Applications No Longer Supported . . . . . . . . . . . . . . . 20

Support for Files Greater than 2 Gigabytes. . . . . . . . . . . . . . . . . . . . . 21

Binary Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Supported Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Robot Support By Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29



iv VERITAS Document Title

Supported Drives By Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5. Operational Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6. Problems Fixed Since the Last Release. . . . . . . . . . . . . . . . . . . . . . . 43

UNIX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Windows NT/95/98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


FlashBackup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7. Known Problems and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

UNIX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

PC Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


8. NetBackup-Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Operational Environment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

NetBackup Administration via NB-Java . . . . . . . . . . . . . . . . . . . . . . . 64

NB-Java Client Application (jbp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Remote Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

The Directly Connected Display Monitor as Console . . . . . . . . . . . . 66

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Another NB-Java Enabled NetBackup Client or Server as Console. 67

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

A Windows NT, 98 or 95 System as Console . . . . . . . . . . . . . . . . . . . 68

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Authorizing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70



Contents v

Authorization File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Nonroot Usage of NB-Java Administrator Applications. . . . . . . . . . 72

Authorizing Nonroot Users for Specific Administrator Applications 73

Capabilities Authorization for jbp . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Converting Previous auth.conf Files . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuration Options for NB-Java Client Application - jbp. . . . . . 75

Alternate Client Restores with jbp. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Default NetBackup Host to Log Into . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Changing Fonts and Font Sizes on UNIX Platforms . . . . . . . . . . . . . 79

Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Operational Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

General Items Applicable to All Applications . . . . . . . . . . . . . . . . . . 82

Activity Monitor Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Backup Policy Management Application . . . . . . . . . . . . . . . . . . . . . . 84

Configure - NetBackup System Configuration Application . . . . . . . 84

Media and Device Management Application . . . . . . . . . . . . . . . . . . . 84

Reports Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Backup, Archive, and Restore Application . . . . . . . . . . . . . . . . . . . . . 85

NB-Java Known Problems and Limitations . . . . . . . . . . . . . . . . . . . . . . . . 85

General Items Applicable to All Applications . . . . . . . . . . . . . . . . . . 85

Backup Policy Management Application . . . . . . . . . . . . . . . . . . . . . . 86

Configure - NetBackup Catalog Backup Application . . . . . . . . . . . . 87

Configure - NetBackup System Configuration Application . . . . . . . 87

Device Monitor Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Media and Device Management Application . . . . . . . . . . . . . . . . . . . 88

Reports Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89



vi VERITAS Document Title

Storage Unit Management Application . . . . . . . . . . . . . . . . . . . . . . . . 89

Backup, Archive, and Restore Application . . . . . . . . . . . . . . . . . . . . . 89

NB-Java Windows Display Console Known Problems. . . . . . . . . . . . . . . 90

Java Problems Seen in NB-Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Known Problems with Display of Online Help. . . . . . . . . . . . . . . . . . . . . 93

Errors When NetBackup Daemons Are Not Running . . . . . . . . . . . . . . . 95

Performance Improvement Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Insufficient Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

A. Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Manual Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Installation Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

System Administrator’s Guides - Basic Product . . . . . . . . . . . . . . . . 102

System Administrator’s Guides - Product Extensions . . . . . . . . . . . 103

User’s Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Device Configuration Guide - Media Manager . . . . . . . . . . . . . . . . . 108

Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Documents To Use For Each Major Task . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Configuration and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

User-Directed Backups, Archives, or Restores . . . . . . . . . . . . . . . . . . 112

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112



vii

Preface

IntroductionThese release notes are intended for the VERITAS NetBackup system administrator, and any other user interested in the 3.2 release of VERITAS NetBackup.

These release notes contain important release information on new features, fixed problems, and known limitations to the 3.2 release of VERITAS NetBackup.

OrganizationThe chapters are organized as follows.

• Chapter 1, “Introduction” A brief introduction to this guide, with information on the online version.

• Chapter 2, “Installation”Explains how to install NetBackup and Media Manager software on your server and client systems.

• Chapter 3, “New Features”Important new features included in this release.

• Chapter 4, “Supported Platforms and Peripherals”Lists the platforms and peripherals supported by NetBackup.

• Chapter 5, “Operational Notes”Important operating information not documented elsewhere.



viii NetBackup Release Notes - UNIX

• Chapter 6, “Problems Fixed Since the Last Release”Describes notable problems resolved by this release of NetBackup.

• Chapter 7, “Known Problems and Limitations”Problems and limitations that you may encounter when using this release of NetBackup.

• Chapter 8, “NetBackup-Java”Information about the NB-Java graphical user interface, including system requirements, authorization, configuration, usage, and troubleshooting.

• Appendix A, “Related Documents” contains a list of all NetBackup documents for the 3.2 release.

Related DocumentsNetBackup System Administrator’s Guide - UNIX

Explains how to configure and manage NetBackup on a UNIX system.

Media Manager System Administrator’s Guide - UNIX

Explains how to configure and manage the storage devices and media on UNIX NetBackup servers. Media Manager is part of NetBackup.

NetBackup User’s Guide - UNIX

Explains how to use NetBackup on a UNIX client to perform backups, archives, and restores.

NetBackup Troubleshooting Guide - UNIX

Provides troubleshooting information for all NetBackup UNIX products.

Media Manager Device Configuration Guide - UNIX

Explains how to configure and manage the storage devices and media on UNIX Media Manager hosts. Media Manager is part of NetBackup.

See Appendix A, “Related Documents,” for a complete list of these manuals.



Preface ix

The CD-ROM also contains on-line copies of these product manuals in Adobe Portable Document Format (PDF). Copy these documents to your system manually, if desired. For information on downloading and installing the latest versions of Acrobat Reader, or for help with installation problems, visit the Adobe web site at:

http://www.adobe.com

VERITAS assumes no responsibility for the correct installation or use of the reader.



x NetBackup Release Notes - UNIX

Conventions The following explains typographical and other conventions used in this guide.

Type Style

The following table describes the typographic conventions used in this guide.

Notes and Cautions

Note: This is a Note and is used to call attention to information that makes it easier to use the product or helps you to avoid problems.

CAUTION! This is a Caution and is used to warn you about situations that can cause data loss.

Keyboard Sequences

Some keyboard command sequences use two or more keys at the same time. For example, you may have to hold down the Ctrl key before you press another key. When this type of command is referenced, the keys are connected by hyphens. For example, Ctrl-t.

Typeface Usage Examples

courier Computer output; user input; names of commands, files, and directories

You have mail.

The mkdir command creates a new directory.

mkdir new

italics New terms; document titles; words to be emphasized; variables to be substituted with a real name or value

mkdir filename

Refer to the User’s Guide for details.

bold Glossary terms



Preface xi

Command Usage

The following conventions are frequently used in the synopsis of command usage.

brackets [ ]

The enclosed command line component is optional.

Vertical bar or pipe (|)

Separates optional arguments from which the user can choose. For example, when a command has the following format:

command [arg1|arg2]

the user can use either arg1 or arg2.

Getting HelpFor license information or information about VERITAS service packages, contact VERITAS Customer Support.

US Customers: 1-800-342-0652

International Customers: +1 (650) 335-8555

Fax: (650) 335-8428

VERITAS Customer Support can also be reached through electronic mail at:

[email protected]



xii NetBackup Release Notes - UNIX



1

Introduction 1

Online Release NotesThe released software contains on-line versions of these release notes, as well as the Media Manager Device Configuration Guide - UNIX. The online versions may be slightly more up-to-date than the printed versions.

The online Release Notes can be found on the CD-ROM in the following paths:

/cdrom/release_notes.txt /cdrom/release_notes.pdf

The online version of the Device Configuration Guide can be found on the CD-ROM in the following paths:

/cdrom/dev_config_guide.txt /cdrom/dev_config_guide.pdf

If you need to reconfigure the kernel to provide specific tape or optical peripheral support, you can copy example code from these PDF or ASCII documents.

Note: It may be useful to copy these documents from the CD to an online repository where they may be more easily accessed.



2

1



3

Installation 2

Installation instructions for this release of NetBackup are to be found in a separate manual, the NetBackup Installation Guide - UNIX.



4 NetBackup Release Notes - UNIX

2



5

New Features 3

The following new features are available in this release of NetBackup. See the online version of these release notes for the final list.

1. Support for NetBackup is extended to the following new platforms with this release. For a complete list of supported platforms, see Table 2 on page page 14.

Table 1 New Supported Platforms

Hardware TypeOperating System

Server OS Version

Client OS Version

Cray/J90 UNICOS - 10.0.x

Data General DG/UX - R4.20MU02

Digital Alpha OSF/1 4.0 878 4.0 878

IBM RS6000 AIX 4.3.1, 4.3.2 4.3.1, 4.3.2

Intel 486, Pentium Windows 98 - Windows 98

Intel x86 Linux - RedHat 5.2, kernel 2.0.36

Intel x86 SCO - OpenServer5.0.5

Intel x86 SCO - UnixWare 7.0.1

Intel x86 Solaris - 2.6, 7

Intel 386, 486, Pentium Novell NetWare

- 5.x

Motorola SVR4.0 - 4.3

NCR UNIX SVR4MP-RAS

3.02 3.02




3

2. Multihosted Drives: Individual tape drives (standalone or in ACS, TLD, TLM and TLH robotic libraries) are dynamically shared between multiple servers. (A SCSI multiplexer or fibre switch is required.) Drives are automatically allocated and deallocated across servers for NetBackup, HSM, and user requests. This is a separately priced feature.

3. Reactive drive cleaning will trigger automated tape drive cleaning based on the TapeAlert standard. Some robot and server plaform restrictions apply. This feature requires configuration of cleaning volumes.

4. Media Manager Configuration Analyzer allows the verification of Media Manager device configurations across a cluster of servers. This feature is available within the NB-Java Media and Device Management application or on the command line interface.

5. Multiplexing is now supported with the FlashBackup feature.

6. Enhanced email capability: The subject line of email sent by NetBackup contains additional information, allowing NetBackup administrators and users to quickly scan their mailboxes.

7. NetBackup will retain the multiplex format of multiplexed backups by making a single pass across tapes when duplicating backups, if specified. This reduces the time to duplicate multiplexed backups.

8. The primary copy and the duplicate copy of a backup image can now have separate expiration dates. After first duplicating an image, both copies have the same expiration date. To change the expiration date of either copy, use the bpexpdate command. See the bpexpdate(1M) man page for more information.

Pyramid ReliantUNIX 5.43 C20 5.43 C20

SGI IRIX 6.5 6.5

Sequent DYNIX/ptx 4.2.3, 4.4.2, 4.4.4 4.4.4

Sun4/SPARC/UltraSPARC Solaris 7 7

Table 1 New Supported Platforms


Server OS Version

Client OS Version



New Features 7

3

9. Multiple data streams can be configured for a single class. A multiple data stream class will break a backup into multiple parts, each of which is an independent backup. The streams can be either administrator defined or auto discovered.

10. The command line interface and some administrative commands are now documented and supported.

NetBackup

bpbackupdbbpclclientsbpclinfobpclschedbpclschedrepbpduplicatebpexpdatebpimagelistbpimportbpmedialist

Media Manager

vmaddvmchangevmdeletevmoprcmdvmqueryvmpool

11. MTF1 (Backup Exec) tapes, by default, are prevented from being overwritten. This can now be changed by specifying the media overwrite option in the NetBackup configuration GUI.

12. NetBackup for NDMP is supported as a separately priced option on additional NetBackup server platforms, including HP-UX, Windows NT, and AIX.

13. Moved, renamed, or newly installed files and directories are now detected and backed up during incremental backup operations by comparing the new file and directory names relative to those contained in the previous full or incremental backup. True image recovery with move detection needs to be selected for this to happen.




3

14. Path independent browsing allows users to specify only the file name during backup image or folder browse operations. All selected files at any level of the directory hierarchy will be displayed. Wildcards are supported.

15. Case insensitive browsing allows users to specify the file name in any combination of upper case and lower case during backup image or folder browse operations.

16. NetBackup for EMC provides online second-host backup of EMC Symmetrix storage arrays as a separately priced option. NetBackup utilizes the EMC Symmetrix API to provide data synchronization and 3rd-mirror break-off backups.

17. NetBackup server/client authentication enables NetBackup master servers, remote servers, and clients to authenticate each other after a NetBackup connection has been established but before any NetBackup transactions have taken place.

18. Standardized, automated integration between VERITAS Storage Manager and NetBackup includes performance monitoring and new alarms at all stages of the backup process. (The VERITAS Storage Manager is a separately priced option.)

19. The update_clients script has been improved to push the current binaries out to as many as 30 clients simultaneously instead of sequentially.

The command has been further enhanced to accept an input file listing which clients to upgrade. The syntax is:

update_clients -ClientList <filename>The complete list of UNIX clients can be found in /tmp/NB_CLIENT_LIST.<date-time.pid>. Edit it appropriately for your site. If this list exceeds 30 clients, you can break it into several shorter lists and run update_clients -ClientList <filename> for each list.

PC Clients1. bpmount is now supported for Windows NT/95/98 clients. This allows the

server to create bpcoverage reports for these client types.

2. Now able to backup files with names longer than 256 characters.



New Features 9

3

Depending on the character set, file names can range from 341 characters up to a maximum of 1,024 characters in some circumstances.

3. McAfee virus software is now available for backup and restore for Windows NT/95/98.

Files can be scanned for viruses as they are being backed up. There are three options for turning this option on or off. In each case, all uninfected files are backed up.

• Perform virus scanning - Files are scanned, but infected files are neither cleaned nor backed up.

• Clean infected files - Files are scanned, and infected files are cleaned and backed up. Infected files that could not be cleaned are not backed up.

• Backup infected files - Files are scanned, and infected files are cleaned and backed up. Infected files that could not be cleaned are also backed up.

Files can be scanned for viruses as they are being restored. There are two options for turning this option on or off. In each case, all uninfected files are restored.

• Perform virus scanning - Files are scanned, but infected files are neither cleaned nor restored.

• Clean infected files - Files are scanned, and infected files are cleaned and restored. Infected files that could not be cleaned are not restored.

4. Open file management is now built into NetBackup for Windows NT/95/98

5. NetBackup can be configured on a Windows NT/95/98 PC with multiple network cards.

6. Proxy (two tier) file server restore.

Allows Windows workstation users to restore files that had been backed up from a Windows NT File Server during a scheduled backup.

7. NetBackup will automatically rename a file during a restore.

When the Restore the File Using a Temporary Filename checkbox is selected, NetBackup will rename a file so it will not copy over an existing file. The renaming convention is NBXXXXXX.TMP, where XXXXXX is generated based on the current date and time to avoid collisions of the restored renamed files.




3

8. Exclude List and Include List for NetWare clients.

NetBackup for NetWare now supports selection lists on the resources defined for non-target backups. The selection list specification for non-target backups closely resembles the selection list specification for target backups. The selection lists are configured on the Resources page found under the Configuration option in the Actions menu.

9. Exclude List and Include List with classes and schedules.

NetBackup for Windows NT/95/98 supports Exclude and Include Lists that are specific to individual classes and schedules.

10. Throttling is now available for OS2.

11. The enhanced graphical user interface is more like Windows Explorer. Columns can be resized and rearraned by dragging.

UNIX Clients1. Back up and restore of Extended Attributes attached to XFS file system

objects on SGI IRIX systems is now supported.

2. Back up and restore of Extended Attributes attached to files on AdvFS and UFS file systems on DEC OSF/1 systems is now supported.

3. Andrew File System (AFS) volume level backup and restore are supported.

NetBackup-Java (NB-Java) 1. The NB-Java GUI applications are automatically installed on supported

Solaris and HP-UX NetBackup servers and clients. See “Supported Platforms” on page 14. They are the default and preferred administrator and end user 'client' applications for these platforms.

2. The NB-Java GUI applications can be used to administer and perform user backup and restore operations on all supported UNIX platforms other than Solaris and HP-UX via the NB-Java application server that is installed and configured on all UNIX NetBackup server and client platforms.



New Features 11

3

3. The ’NetBackup-Java Display Console for Windows NT/98/95’ product is available to facilitate administration and user backup and restore operations on all supported UNIX platforms other than Solaris and HP-UX at locations where no Solaris or HP-UX NetBackup machines exist. See “Supported Platforms” on page 14. This is done via the NB-Java application server.

4. The Activity Monitor and Device Monitor applications support activity and device monitoring of Seagate Backup Exec machines running Backup Exec version 7.3.

5. NB-Java applications now run on Solaris Intel 2.6 and 7.0 - NB client capabilities only.

6. NB-Java online help is now launched into a window of its own instead of using a Web browser, so no Web browser need be configured for viewing online help.

7. The performance of the Activity Monitor application’s refresh functionality has been significantly improved.

8. The requirement for the separate password type file, /usr/openv/java/auth.conf, no longer exists. NB-Java now validates usernames and passwords against the system password file.

9. The NB-Java GUI applications can 'execute' in a different timezone than that of the machine on which they were initiated. This greatly enhances the usability of the applications in environments containing geographically dispersed NetBackup server and client machines. This is accomplished by adjusting the timezone via the Adjust Application Timezone dialog available from the Configure menubar menu.

Database Extensions1. Dual support for SQL7 and SQL6.5.

The NetBackup extension recognizes which version is installed and changes its behavior accordingly.

2. Support of the SQL7 virtual device interface.

This benefits from improved SQL Server backup performance. There is no external user impact except for improved performance.

3. Support SQL7 differential backups and restores.




3

Differential backups provide the user one method to shorten their required backup window. The NetBackup extension GUI provides guidance for staging the sequence of database, differential, and transaction log images which are needed for complete database recovery.

4. Support SQL7 file/filegroup backup and restores.

File and filegroup backups provide a second method to shorten the backup window. The GUI provides guidance for staging the the complete file/filegroup set along with transaction logs that are needed for complete database recovery.

5. Automatic script generation from the MS-SQL Server GUI.

The job launch panes provide the capability for the user either to execute an operation immediately or to save the intermediate batch file. The saved script can be hand-manipulated or can be used for scheduled backups.

6. Support in the NetBackup interface for the user to specify which schedule to use for backup.

7. Online backup of DB/2 databases is supported via the DB/2 backup API. on AIX 4.1.x and above platforms only.

8. Oracle database block-level incremental backups and restores are available as a separately priced option on HP-UX. This requires the VERITAS file system, VxFS.

9. Oracle 8 RMAN support added to Sequent, SGI, NCR and DG-UX platforms, providing online backup and recovery of Oracle 8 databases.

10. Oracle 8.1 Proxy Copy integration, whereby NetBackup is given the filenames to be backed up rather than the database data itself. NetBackup uses block-level incremental backups with VxFS.

11. Encryption support for Oracle (OEBU, RMAN).

12. Oracle support for HP-UX 11, 64-bit architecture.



13

Supported Platforms and Peripherals 4

This chapter provides information on the platforms and peripherals that NetBackup and Media Manager support with the 3.2 release. Consult the VERITAS web page, http://www.veritas.com/, or contact your VERITAS sales representative to find out about any additions or other changes that may have occurred since this document was published.




4

Supported PlatformsThe following table describes hardware and operating system combinations supported by NetBackup.

The Server OS Version column describes the operating system level required to run the NetBackup server.

The Client OS Version column describes the operating system level required to support a NetBackup client. Predecessors and successors to the supported operating system levels may function without difficulty, as long as the release provides binary compatibility with the supported level.

Table 2 NetBackup 3.2 Supported Platforms


Server OS Version

Client OS Version Notes

Auspex Auspex 1.9M1 1.9M1 -

Cray/J90 UNICOS - 10.0.x 1

Data General DG/UX - R4.20MU02 2

Digital Alpha OSF/1 4.0 386,4.0 878

4.0 386,4.0 878

-

Digital Alpha Windows NT 4.0 4.0 -

HP9000-700 HP-UX 10.20, 11.0 10.20, 11.0 -

HP9000-800 HP-UX 10.20, 11.0 10.20, 11.0 -

Intel 386, 486, Pentium OS/2 - Warp 3,4 1

IBM RS6000 AIX 4.1.5, 4.2, 4.3, 4.3.1, 4.3.2

4.1.5, 4.2, 4.3, 4.3.1, 4.3.2

-

Intel 486, Pentium Windows 95, 98

- Windows 95, 98

3

Intel Pentium Windows NT 4.0 4.0 4

Intel x86 Linux - RedHat 5.2, kernel 2.0.36

5

Intel x86 SCO - OpenServer5.0.5

Intel x86 SCO - UnixWare 7.0.1




4

Intel x86 Solaris - 2.6, 7 -

Intel 386, 486, Pentium Novell NetWare

- 3.12, 4.10, 4.11, 5.x

1, 6

Intel 386, 486, Pentium OS/2 - Warp 3, 4 1

Macintosh (680x0 or PowerPC)

MacOS - 7.x, 8.x 7

Motorola SVR4.0 - 4.2, 4.3 -

Network Appliance through NDMP (with locally attached storage)

- - 5.2.1 1, 8

NCR UNIX SVR4MP-RAS

3.02 3.02 -

Pyramid ReliantUNIX 5.43 B0078, 5.43 C20

5.43 B0078, 5.43 C20

-

SGI IRIX 6.2, 6.4, 6.5 6.2, 6.4, 6.5 -

Sequent DYNIX/ptx 4.2.1, 4.2.3, 4.4.2, 4.4.4

4.0.2, 4.1.3, 4.2.1, 4.2.3, 4.4.2, 4.4.4

9

Sun4/SPARC/UltraSPARC Solaris 2.5, 2.5.1, 2.6, 7

2.5, 2.5.1, 2.6, 7

1. Does not support NetBackup encryption.

2. Tested only on Intel processor-based AViiON servers.

3. Requires NetBackup for Microsoft Windows extension product.

4. Requires NetBackup for Microsoft Windows NT Server and/or client extension product.

5. Requires RedHat Motif version 2.1.10 in order to use the user interface, xbp.

6. Requires NetBackup for Novell NetWare extension product.

7. Requires NetBackup for Macintosh extension product. The installation guide for that extension product explains other requirements.

8. Requires NetBackup for NDMP extension.

9. Requires level 2.4.0 or later TCP to be installed.

Table 2 NetBackup 3.2 Supported Platforms


Server OS Version

Client OS Version Notes




4

Database Extension Matrix

Table 3 Platforms Supported by NetBackup Database Extensions (Part 1 of 3)

NetBackup Product DB BackupDG (AViiON)

DEC Alpha

DEC Alpha HP9000

Product DG/UX OSF/1 Win NT HP-UXNetBackup for Oracle Oracle 7.2.3 EBU 2.0.12.4 -- 3.2 -- 10.x Oracle 7.3.x EBU 2.1 -- 4.x -- 10.20 Oracle 7.3.4 EBU 2.2 R4.20 4.x -- 10.20, 11.0 Oracle 8.0.3 RMAN -- 4.x -- 10.20 Oracle 8.0.4 RMAN -- 4.x -- 10.20, 11.0 Oracle 8.0.5 RMAN R4.20 4.x -- 10.20, 11.0 Oracle 8.0.5.1 RMAN -- -- -- 11.0/64-bit Oracle 8.1.5 RMAN -- 4.x -- 11.0 Oracle 8.1.5 RMAN/Proxy -- -- -- --NetBackup for Informix Informix 7.21 OnBAR 1.0 -- -- -- 10.x Informix 7.23 OnBAR 1.0 -- -- -- 10.x Informix 7.24 OnBAR 1.0 -- -- -- 10.x Informix 7.3 OnBAR 1.1 -- -- -- 10.x, 11.0NetBackup for Sybase Sybase 11.x B/R API -- -- -- 10.x Sybase 11.9.x B/R API -- -- -- 10.xNetBackup for SAP -- Oracle 7.x Backint R/3 3.x -- 3.2, 4.x -- 10.x, 11.0 Oracle 8.x Backint R/3 3.x -- 4.x -- 10.20, 11.0 Oracle 7.x Backint R/3 4.x -- 4.x -- 10.x, 11.0 Oracle 8.x Backint R/3 4.x -- 4.x -- 10.20, 11.0NetBackup for Microsoft SQL Server SQL 6.5 Dump/Load -- -- 41

1. Windows NT Service Pack 3 or greater

-- SQL 7.0 VDI -- -- 41 --NetBackup for DB2 DB2 UDB 5.0.0.36 SQLUV API -- -- -- -- DB2 UDB 5.2 SQLUV API -- -- -- --NetBackup for Microsoft Exchange Exchange 5.0 B/R API -- -- 4 -- Exchange 5.5 B/R API -- -- 4 --




4


NetBackup Product DB Backup IBM RS6000 Intel Pentium NCRProduct AIX Windows NT SVR4MP-RAS

NetBackup for Oracle Oracle 7.2.3 EBU 2.0.12.4 4.x -- -- Oracle 7.3.x EBU 2.1 4.x -- -- Oracle 7.3.4 EBU 2.2 4.x 4.0 3.02 Oracle 8.0.3 RMAN 4.x -- -- Oracle 8.0.4 RMAN 4.x 4.0 -- Oracle 8.0.5 RMAN 4.x 4.0 3.02 Oracle 8.0.5.1 RMAN -- -- -- Oracle 8.1.5 RMAN 4.2.x, 4.3.x 4.0 -- Oracle 8.1.5 RMAN/Proxy -- -- --NetBackup for Informix Informix 7.21 OnBAR 1.0 4.x -- -- Informix 7.23 OnBAR 1.0 4.x -- -- Informix 7.24 OnBAR 1.0 4.x -- -- Informix 7.3 OnBAR 1.1 4.x -- --NetBackup for Sybase Sybase 11.x B/R API 4.x -- -- Sybase 11.9.x B/R API 4.x -- --NetBackup for SAP Oracle 7.x Backint R/3 3.x 4.x -- -- Oracle 8.x Backint R/3 3.x 4.x -- -- Oracle 7.x Backint R/3 4.x 4.x 4.0 -- Oracle 8.x Backint R/3 4.x 4.x 4.0 --NetBackup for Microsoft SQL Server SQL 6.5 Dump/Load -- 4.01

1. Windows NT Service Pack 3 or greater

-- SQL 7.0 VDI -- 4.01 --NetBackup for DB2 DB2 UDB 5.0.0.36 SQLUV API 4.x -- -- DB2 UDB 5.2 SQLUV API 4.x -- --NetBackup for Microsoft Exchange Exchange 5.0 B/R API -- 4.0 -- Exchange 5.5 B/R API -- 4.0 --




4


NetBackup Product DB Backup SGI Sequent SUNProduct IRIX DYNIX/ptx Solaris

NetBackup for Oracle Oracle 7.2.3 EBU 2.0.12.4 -- -- 2.5.x Oracle 7.3.x EBU 2.1 6.2, 6.4 4.2 2.5.x, 2.6 Oracle 7.3.4 EBU 2.2 6.2, 6.4 4.2, 4.4 2.5.x, 2.6 Oracle 8.0.3 RMAN -- -- 2.5.x, 2.6 Oracle 8.0.4 RMAN 6.2, 6.4 4.2, 4.4 2.5.x, 2.6 Oracle 8.0.5 RMAN 6.2, 6.4 4.4 2.5.x, 2.6 Oracle 8.0.5.1 RMAN -- -- -- Oracle 8.1.5 RMAN -- -- 2.6 Oracle 8.1.5 RMAN/Proxy -- -- 2.6NetBackup for Informix Informix 7.21 OnBAR 1.0 -- -- 2.5.x, 2.6 Informix 7.23 OnBAR 1.0 -- -- 2.5.x, 2.6 Informix 7.24 OnBAR 1.0 -- -- 2.5.x, 2.6 Informix 7.3 OnBAR 1.1 -- -- 2.5.x, 2.6NetBackup for Sybase Sybase 11.x B/R API -- -- 2.5.x, 2.6 Sybase 11.9.x B/R API -- -- 2.5.1, 2.6NetBackup for SAP Oracle 7.x Backint R/3 3.x -- -- 2.5.x, 2.6 Oracle 8.x Backint R/3 3.x -- -- 2.5.x, 2.6 Oracle 7.x Backint R/3 4.x -- -- 2.5.x, 2.6 Oracle 8.x Backint R/3 4.x -- -- 2.5.x, 2.6NetBackup for Microsoft SQL Server SQL 6.5 Dump/Load -- -- -- SQL 7.0 VDI -- -- --NetBackup for DB2 DB2 UDB 5.0.0.36 SQLUV API -- -- -- DB2 UDB 5.2 SQLUV API -- -- --NetBackup for Microsoft Exchange Exchange 5.0 B/R API -- -- -- Exchange 5.5 B/R API -- -- --




4

Platforms No Longer Supported

The following platforms are no longer supported in this release.

The next major release of NetBackup will no longer contain software to upgrade some operating system levels and platforms to include new product features and capabilities. Backward compatibility with 3.2 NetBackup client software will be retained for at least one release level.

The following platforms will not be supported in the next major release.

Table 6 Platforms No Longer Supported, Release 3.2


Server OS Version Client OS Version

Auspex Auspex 1.81M1 1.81M1

Cray Superserver Solaris 2.4 2.4

Cray/J90 UNICOS - 9.x1

1. Support dropped because of Y2K incompatibility.


HP9000-700 HP-UX 9.04, 10.01, 10.10 9.03, 9.05, 10.01, 10.10

HP9000-800 HP-UX 9.04, 10.01, 10.10 9.04, 10.01, 10.10

IBM RS6000 AIX 3.2.5 3.2.5

Intel Windows 3.11 - Windows 3.11

Intel Pentium Windows NT 3.51 3.51

Motorola SVR3.2 - 3.1

NCR UNIX SVR4MP 3.0.1 2.0.2.1, 2.0.3.1, 3.0.1

Pyramid ReliantUNIX - 5.43 B0078

1.1-94 D0795.43 B0078

SGI IRIX 5.3 5.3

Sequent DYNIX/ptx 3.2.0 - 2.1.6

Sun4/SPARC SunOS4 4.1.3, 4.1.4 4.1.3, 4.1.4

Sun4/SPARC Solaris2 2.4 2.4




4

Devices and Applications No Longer Supported

The following devices and applications will not be supported in the next major release.

• TC4 robotics (LAGO 4-mm DataWheel, STK 9704)

• TC8 robotics (IGM carousel, LAGO 8-mm DataWheel, STK 9708)

• RS232 (serial) robotic control for SCSI-based robotics

• Operator Location management

• Mountain Gate D360

• Exabyte 8200

• ACSLS 5.1.1

• IBM ATL versions lower than version 4.0.1.0 on AIX

• IBM lmcpd packages lower than version 4.0.1.0 on Solaris

• ADIC DAS versions lower than 1.30C7

Table 7 Platforms No Longer Supported, Next Major Release


Server OS Version Client OS Version


HP9000-700/800 HP-UX 10.20 10.20

IBM RS6000 AIX 4.1.5 4.1.5


MacOS - 7.0 to 7.5.4

SGI IRIX 6.2, 6.4 6.2, 6.4

Sequent DYNIX/ptx 4.2.1, 4.2.34.0.2, 4.1.3, 4.2.1, 4.2.3

Sun4/SPARC/UltraSPARC

Solaris2 2.5, 2.5.1 2.5, 2.5.1




4

Support for Files Greater than 2 Gigabytes

The current version of NetBackup supports file sizes greater than 2 gigabytes on the following client systems.

• DEC Alpha version 3.2 and up

• HP-UX version 10.20 and up

• IBM AIX version 4.2 and up

• Novell NetWare

• Sequent DYNIX 4.2.1 and up

• SGI IRIX version 6.2 and up

• Sun Solaris version 2.6 and up

• Windows NT

Binary Sizes

The following table shows the approximate binary size of the NetBackup and Media Manager software for each supported platform and operating system.

Table 8 Binary Sizes


NetBackup Server

Media Manager

NetBackup Client

Auspex Auspex 47 MB 22 MB 7800 KB

Cray/J90 UNICOS --- --- 28 MB

Data General DG/UX --- --- 4600 KB

Digital Alpha OSF/1 83 MB 34 MB 8884 KB

Digital Alpha Windows NT 38 MB 5 MB 6000 KB

HP9000-700/800 HP-UX 10.20 42 MB1 19 MB 8002 KB2

HP9000-700/800 HP-UX 11.0 47 MB1 19 MB 8058 KB2

IBM RS6000 AIX 4.1AIX 4.2

61 MB61 MB

21 MB21 MB

8000 KB3

8100 KB3

Intel 386, 486, Pentium

OS/2 --- --- 7000 KB

Intel 486, Pentium Windows 95, 98 --- --- 6000 KB

Intel Pentium Windows NT 33 MB 4 MB 7500 KB




4

Intel x86 RedHat Linux --- --- 4200 KB

Intel x86 SCO OpenServer --- --- 4469 KB

Intel x86 SCO UnixWare --- --- 5479 KB

Intel x86 Solaris --- --- 6754 KB4

Intel 386, 486, Pentium

Novell NetWare --- --- NLM, 3 MBGUI, 4 MB


MacOS --- --- 4000 KB

Motorola SVR4.0 --- --- 7500 KB

NCR UNIX SVR4MP-RAS

45 MB 14 MB 5600 KB

Pyramid ReliantUNIX 53 MB 15 MB 7068 KB

SGI IRIX 62 MB 22 MB 8306 KB

SequentDYNIX 4.1DYNIX 4.2

---50 MB

---50 MB

6200 KB5

7100 KB5

Sun4/SPARC/UltraSPARC

Solaris 2.5Solaris 2.6, 7

49 MB1

49 MB123 MB23 MB

7236 KB4

7526 KB4

1. Add 50 MB installed on server for the JAVA interface.

2. A total of 16060 KB installed on the server for HP-UX 10.20 and 11.0.

3. A total of 16100 KB installed on the server for AIX 4.1 and 4.2.

4. A total of 21355 KB installed on the server for Solaris 2.5, 2.6 and 7.

5. A total of 13300 KB installed on the server for DYNIX 4.1 and 4.2.

Table 8 Binary Sizes


NetBackup Server

Media Manager

NetBackup Client




4

Supported PeripheralsThe following table lists the robot vendors and models supported by Media Manager robotic software, distinguished by robot type. The robot type classifies the devices and peripherals either by their physical characteristics, by their media type, or by the communication methods used by their underlying robotics. See Appendix A of the Media Manager System Administrator’s Guide - UNIX for more information about these robot types.

ACS - Automated Cartridge SystemLMF - Library Management FacilityODL - Optical Disk LibraryTC4 - Tape Carousel 4MM TC8 - Tape Carousel 8MM TL4 - Tape Library 4MM TL8 - Tape Library 8MM TLD - Tape Library DLT TLH - Tape Library Half-inch TLM - Tape Library Multimedia TS8 - Tape Stacker 8MM TSD - Tape Stacker DLT TSH - Tape Stacker Half-inch

This table also shows the firmware levels that have been tested to work with Media Manager.

Note: For current device support information, consult the VERITAS web page, http://www.veritas.com/.

Table 9 Supported Robotics by Vendor

Vendor ProductRobot Type

Platform Restrictions Firmware

ADIC DAT Library (1200 Series) TL4 0351, 0357

ADIC VLS 4mm TL4 022

ADIC FastStor DLT TLD 0072, 1.10, 1.13

ADIC Scalar 1000 DLT TLD 2.12, 2.20

ADIC Scalar 218 TLD 0101

ADIC Scalar 224 TLD 0119, 0121




4

ADIC Scalar 448, 458 TLD 0119, 0121

ADIC Scalar 220 AIT TL8 or TS8

AIX, Solaris & Windows NT only

6.3

ADIC Scalar 480 AIT TL8 AIX, Solaris & Windows NT only

6.3

ADIC VLS DLT TSD 0232

ADIC/EMASS AML/J (DAS Controlled) TLM -

ADIC/EMASS AML/S (DAS Controlled) TLM 1.24

ATL ATL 2640 (3/264) TLD 3N

ATL ATL 2/100 TLD -

ATL ATL 2/28 TLD 1.20

ATL ATL 2/52 TLD 1.20

ATL ATL 2/68 TLD -

ATL ATL 4/100 TLD -

ATL ATL 4/52 TLD 1.20, 1.25

ATL ATL 4/68 TLD -

ATL ATL 6/176 TLD 3N

ATL ATL 7/68 TLD -

ATL ATL 7/100 TLD -

ATL ATL 9/88 TLD 3N

ATL P1000 TLD 1.114

ATL P3000 TLD 1.12

ATL PowerStor L200 TLD 1.27, 0014, 1B

ATL PowerStor L500 TLD 6320, 19

BreeceHill Q2.15 TLD 1.11, 1.50

BreeceHill Q7 TLD 4.23, 4.33

BreeceHill Q47 TLD 4.23, 4.33

BreeceHill Saguaro Series (Q70, Q140,Q210)

TLD 2.1

Compaq/Digital 1530 Library TLD 2.06

Compaq/Digital 3570 Library TLD 1.24, 4.01







4

Compaq/Digital TL800 Series (TL890, TL891,TL892)

TLD -

Compaq/Digital TL810 Series (TL810, TL812, TL894, TL895)

TLD 2.20

Compaq/Digital TL820 Series (TL820, TL822, TL826, TL893, TL896)

TLD -

Compaq/Digital TZ875 (DLT2500) TSD -

Compaq/Digital TZ877 (DLT2700) TSD 1.24

DELL PowerVault 120T TLD 1.10

DELL PowerVault 130T TLD 1.5.05

Exabyte EZ17 TL8 1.4

Exabyte 10/10e/10h/10i TS8 1.24, 1.5, 2.6, 3.0

Exabyte 18D TLD 2.01, 2.4.2

Exabyte 60 / 120 TL8 3.06

Exabyte 210 TS8 2.02, 3.01, 3.11.13

Exabyte 220 TS8 or TL8

4.11

Exabyte 230D TLD 1.03

Exabyte 440 / 480 TL8 3.01

Exabyte 690D TLD 1.05

Fujitsu F6458, M2498 LMF Solaris only LMF Server 1.1LMF Client 1.1

HP SureStore Optical 40fx ODL -

HP SureStore Optical 80fx ODL 0.42

HP SureStore Optical 160fx ODL 0.42

HP Optical Jukebox Libraries (JBL)

ODL 4.51, 4.78, 6.10

HP DAT Autoloader C1560B TL4 2.11

HP SureStore DAT (C1537A) TL4 L610

HP SureStore DAT24x6 (C1557A)

TL4 Solaris & HP-UX only

U610, U709, ULE4







4

HP A4845A TLD -

HP A4846A TLD 1.24

HP A4853A TLD 1.3.00

HP SureStore DLT 418 (C6280F)

TSD2.01, 2.02, 2.06

HP SureStore DLT 718 (C6280J)

TSD2.02, 2.06

HP SureStore DLT 4115 (C5150F, C5151F, C5170F, C5172F)

TLD3.0, 3.04

HP SureStore DLT 4215 (C5152F, C5153F, C5171F, C5173F)

TLD3.0, 3.04

HP SureStore DLT 7115 (C5170J, C5172J)

TLD3.03, 3.04

HP SureStore DLT 7215 (C5171J, C5173J)

TLD3.03, 3.04

HP SureStore DLT 4228(C1191F, C5175F)

TLD1.03

HP SureStore DLT 4428 (C1192F)

TLD1.03

HP SureStore DLT 4448(C1194F, C5177F)

TLD1.00, 1.03


TLD1.03


TLD1.03


TLD1.03

IBM 3494 TLH AIX & Solaris only -

IBM 3570 B-Series TLD AIX, IRIX & Solaris only

328F







4

IBM 3575 TLD AIX, IRIX, Solaris, & Windows NT only

2.10

IBM 3590 B11 TSH AIX, IRIX & Solaris only

96F9

IBM 7331 TL8 AIX & Solaris only 0002

IBM 7337 TLD -

IGM Carousel Jukebox Library (RS232)

TC8 -

Lago 4-mm DataWheel (RS232 & SCSI)

TC4 3.05

Lago 8-mm DataWheel (RS232 & SCSI)

TC8 5.2, 6.3

Mountain Gate D360 TLD 02.4

Overland Data Library Express (LXG Series)

TLD 0323

Overland Data LXB 2210/2110, LXB 4210/4110, LXB 7210/7110

TLD 0128

Plasmon LMS BlackJack 21 DLT TLD X04F

Qualstar TLS-4000 Series: 4210, 4220, 4420, 4480, 46120, 4660

TL8 AIT on Solaris, AIX and NT only

1.08, 1.24

Qualstar TLS 4440 TL8 AIT on Solaris, AIX and NT only

1.08, 1.27

Qualstar TLS-6000 Series: 6110, 6210, 6220, 6430, 6460

TLD 1.29

Quantum DLTStor (4108, 7108) TLD 8525, 000F

Quantum DLTStor (4314, 7314) TLD 000F, 0012

Quantum DLT 4500 TSD CC37, CD50, CF5F

Quantum DLT 4700 TSD CC1E, CC32, CD3C

SONY DMS (PetaSite) TLD Solaris & IRIX only

1.13







4

Spectra Logic 215 Treefrog TL8 1000

Spectra Logic 2000 Treefrog TL8 Solaris, AIX and NT only

1000

Spectra Logic 9000 Bullfrog TL8 0200

Spectra Logic 10000 Bullfrog TL8 Solaris, AIX and NT only

5.00.05

STK 7430 TLD 1.4.01

STK 9704 TC4 -

STK 9708 TC8 -

STK 9710 ACS ACSLS 5.1.1, 5.2, 5.3

STK 9710 TLD 1.9.52

STK 9714 ACS ACSLS 5.2, 5.3

STK 9714 TLD 1.9.52

STK 9730 ACS ACSLS 5.3

STK 9730 TLD 1.6.53

STK 9738 TLD 1.0.02

STK 9740 ACS ACSLS 5.1.1, 5.2, 5.3

STK 9740 TLD 1.9.52

STK Silos (4410/9310/9360) ACS ACSLS 5.1.1, 5.2, 5.3

SUN StorEdge 4mm DDS-3 Autoloader

TL4 Solaris and HP-UX only

U610, U709, ULE4

SUN StorEdge L140 TS8 3.01, 3.11.13

SUN StorEdge L280 TSD 2.02

SUN StorEdge L400 TS8 or TL8

4.11

SUN StorEdge L1000 TLD 1.2

SUN StorEdge L1800 TLD -

SUN StorEdge L3500 TLD -

SUN StorEdge L11000 TLD 1.12







4

Robot Support By Platform

The following table shows the robot types that NetBackup and Media Manager support on each platform.

• Level 1 (L1) means the robot type was tested to run with NetBackup and Media Manager at the latest release level.

• Level 2 (L2) means the robot was tested at an earlier release level or is documented by the manufacturer to work the same as a level 1 device.

Note: Level 1 devices resold under a different name are supported at level 2.

Table 10 Robot Support by Platform (Part 1 of 2)

Robot Type1

1. Use the acronym when you define the robot to NetBackup and Media Manager.

DEC OSF 1 HP700 HP8007 RS6000 SGI10 Solaris

ACS2

2. Contact your drive and operating system vendors to ensure that the standard tape driver support is available.

L1 L1 L1 L1 L1 L1

LMF no no no no no L1

ODL3

3. Corsair and FX drives are supported, but not mixed in same library.

no L1 L18 L1 L1 L1

TC4 L1 L1 L1 L1 L1 L1

TC8 L1 L1 L1 L1 L1 L1

TL44

4. Supported only with Hewlett-Packard drives.

L1 L1 L18 L1 L1 L1

TL8 L1 L1 L18 L1 L1 L1

TLD L1 L1 L18 L1 L1 L1

TLH L16

6. No robotic control (tlhd is supported, tlhcd/tlhtest are not)

L16 L16 L19 L16 L111

TLM5

5. DAS media types supported: 3480, 3590, DECDLT, 8mm, 4mm and DTF. On HP800, OD_THICK is also supported. Any DAS media types not listed here are not supported. DAS version level tested: 1.30C7.

L1 L1 L1 L1 L1 L1

TS8 L1 L1 L18 L1 L1 L1

TSD L1 L1 L18 L1 L1 L1

TSH no no no L1 L1 L1




4

7. Appropriate patches may have to be installed for single-ended or differential for 10.x.

8. Support for this robot on HP800 requires SCSI pass-through driver from HP.

9. IBM ATL version levels tested on AIX: 2.5.1.0, 3.2.5.0.

10. The SGI support column refers only to Integral SCSI (non-VME).

11. IBM lmcpd package version level tested on Solaris: 2.5.2.0.

Table 11 Robot Support by Platform (Part 2 of 2)

Robot Type1

1. Use the acronym when you define the robot to NetBackup and Media Manager.

Auspex (HP) Auspex (SP) NCR Pyramid Sequent

ACS2

2. Contact your drive and operating system vendors to ensure that the standard tape driver support is available.

no no L1 L1 L1

LMF no no no no no

ODL L1 no no no no

TC4 L1 no no no no

TC8 L1 no no no no

TL4 L1 no no no L16

6. Requires Sequent 4.4.2 or higher.

TL8 L1 no no no L16

TLD L1 L1 L1 L15

5. No robotic control (tldd is supported, tldcd/tldtest are not).

L16

TLH L1 no L14

4. No robotic control (tlhd is supported, tlhcd/tlhtest are not).

L14 L14

TLM3

3. DAS media types supported: 3480, 3590, DECDLT, 8mm, 4mm and DTF. On HP800, only OD_THICK is supported. Any DAS media types not listed here are not supported. DAS version level tested: 1.30C7.

L1 no L1 L1 L1

TS8 L1 no no no L16

TSD L1 L1 no no no

TSH no no no no no




4

Supported Drives By Platform

The following table shows the types of drives that NetBackup and Media Manager support on each platform.

• Level 1 (L1) means the drive type was tested to run with NetBackup and Media Manager at the latest release level.

• Level 2 (L2) means the drive was tested at an earlier release level or is documented by the manufacturer to work the same as a level 1 device.

Note: Level 1 devices resold under a different name are supported at level 2.

Note: For current device support information, consult the VERITAS web page, http://www.veritas.com/.

Table 12 Supported Drive Types (Part 1 of 2)

Drive TypeDEC OSF 1 HP700 HP8004 RS6000 SGI6 Solaris

Exabyte 8200 L2 L2 no L2 L2 L2

Exabyte 8500, 8500C, 8505, 8505XL L1 L1 L1 L1 L1 L1

Exabyte 8900 Mammoth L13 L1 no L13 L13 L13

Fujitsu M2488 no no no no no L1

HP 4-mm DAT Cartridge L1 L1 L1 L1 L1 L1

HP Optical Disk1 (WORM and rewriteable)

no L1 L1 L1 L1 L1

IBM Magstar Cartridge (3570) no no no L1 L1 L1

IBM 1/2-inch Cartridge (3590) no no no L1 L1 L1

Quantum DLT2000 L13 L1 L15, 3 L13 L13 L13



QIC no no no L2 L2 L2

SONY AIT SDX-300C Cartridge no no no L13 no L13

SONY DTF Cartridge no no no no L1 L1

STK 1/2-inch Cartridge2 L23 L2 L23 L23 L23 L23




4

STK 9840 no no L13 L13 no L13

Tandberg DLT4000 L13 L1 L15, 3 L13 L13 L13

Tandberg DLT7000 L13 L1 L15, 3 L13 L13 L13

1. Corsair and FX drives are supported.

2. This includes the following drive models: 4490, 4890, 9490, and SD-3 (Redwood). Contact your drive and operating system vendors to ensure that the standard tape driver support is available.

3. Supports Tape Alert for drive cleaning.

4. Appropriate patches may have to be installed for single-ended or differential for 10.x.

5. Contact Hewlett Packard for tape drive patch for HP-UX 10.x.

6. The SGI support column refers only to Integral SCSI (non-VME).


Drive Type Auspex (HP) Auspex (SP) NCR Pyramid Sequent

Exabyte 8200 L2 no no no no

Exabyte 8500, 8500C, 8505, 8505XL L1 no L2 L2 L2

Exabyte 8900 Mammoth L13 no no no no

Fujitsu M2488 no no no no no

HP 4-mm DAT Cartridge L1 no no no L2

HP Optical Disk1 (WORM and rewriteable)

1. Corsair and FX drives are supported.

L1 no no no no

IBM Magstar Cartridge (3570) no no no no no

IBM 1/2-inch Cartridge (3590) no no no L1 L2

Quantum DLT2000 no no no no no

Quantum DLT4000 L13 L1 L1 L2 L2

Quantum DLT7000 L13 L1 no no no

QIC L2 no no no no

SONY AIT SDX-300C Cartridge no no no no no

SONY DTF Cartridge no no no no no

STK 1/2-inch Cartridge2 L23 no no L2 L2

STK 9840 no no no no no

Tandberg DLT4000 L13 L1 L1 L2 L2

Tandberg DLT7000 L13 L1 no no no





4

2. This includes the following drive models: 4490, 4890, 9490, and SD-3 (Redwood). Contact your drive and operating system vendors to ensure that the standard tape driver support is available.

3. Supports Tape Alert for drive cleaning.




4



35

Operational Notes 5

The following notes explain important aspects of NetBackup operations that may not be documented elsewhere.

1. It is not possible to revert to an earlier release of NetBackup after you install and begin using NetBackup 3.2.

2. Upgrades for Beta Customers: If you are upgrading from any NetBackup 3.2 Beta system, you must uninstall all Beta extensions (i.e. MHD, NDMP, AFS) prior to upgrading.

3. If you have VERITAS HSM installed on a NetBackup client system and you are upgrading to NetBackup 3.2 on that client, you must upgrade to release 3.2 of VERITAS Storage Migrator for UNIX at the same time you upgrade to NetBackup 3.2.

If you have VERITAS HSM Enterprise Extension installed on a NetBackup client system and you are upgrading to NetBackup 3.2 on that client, you must upgrade to release 3.2 of VERITAS Storage Migrator Remote for UNIX at the same time you upgrade to NetBackup 3.2.

Running HSM 3.1.x with NetBackup 3.2 on the same client is an unsupported configuration.

4. SCSI robotic peripherals must not be in sequential mode for use with Media Manager.

Media Manager robotic software expects SCSI robotic peripherals to be in random mode (SCSI control of the robot) rather than sequential mode. The robotic control processes cannot control robotic devices that are in sequential (stacker) mode.




5

5. Single-ended to differential SCSI converters are not supported.

We do not recommend or support the use of single-ended to differential SCSI converters on Media Manager controlled devices. You may encounter problems if you use these converters.

6. NetBackup uses reserved ports for bprd, bpcd, and bpjava-msvc.

NetBackup uses reserved ports on the client as a security measure. The reserved port check on the client is used to ensure that a administrative process on the server is sending the command.

This may prevent backups of machines that do not allow reserved ports, such as firewall systems. In those cases, we recommend that you change the system configuration to allow access from the IP address of the NetBackup server. Refer to the ALLOW_NON_RESERVED_PORTS in Chapter 6, “Additional Configuration” of the NetBackup System Administrator’s Guide - Windows NT Server for more details.

7. Some command line interfaces are undocumented.

Some administrative command line interfaces to NetBackup are not documented and not supported.

At this release, however, some NetBackup and Media Manager administrative commands are documented and supported for the first time. See “New Features“ on page 5 for a list of these newly documented commands.

8. Archiving migrated files.

It is inadvisable to archive files that have been migrated by the client component of VERITAS HSM on UNIX clients where VERITAS HSM is installed. Backing up migrated files will not cause problems.

A file migrated from a client workstation, through one of these products, exists on the workstation as a link file. Should the user subsequently archive this file using NetBackup, the link (not the data) is backed up. Then the link is deleted, causing the data associated with the file to become an “orphan” on the migration server.

If the link file is restored on the client after the administrator on the migration server deletes orphan files, the data associated with the link is irretrievable.



Operational Notes 37

5

9. Decoding a time stamp.

Occasionally, it is desired to convert the time stamp used by NetBackup for its backup ids into a human-readable format. Backup ids take the form of client name_timestamp; for example, danr_0818775918.

To convert 818775918 to a readable format, edit a file to contain the following C program and use your UNIX C compiler to create an executable binary. After this is done, you can execute the program giving it the time stamp as its only parameter and it will convert and display the date and time in a legible format.

main(argc,argv)int argc;char **argv;{long t;

t=atol(argv[1]);printf(“%ld = %s\n”,t,ctime(&t));}

Example:

vi utime.c and insert the program linescc -o utime utime.c./utime 818775918818775918 = Tue Dec 12 07:45:18 1995

10. Intentionally destroying NetBackup catalogs.

In a demonstration or “proof-of-concept” environment, it is often desirable to destroy any image catalogs and tape files once the system is ready to take into full production mode.

To delete all backup and archive image catalogs, as well as the information about the secondary storage being used for those images:

a. Log on to the NetBackup server as the root user

b. For each media in the NetBackup media listing (use the NetBackup Report interface), enter the following command (one line):

/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -evmedia id {-host hname} [-host hname]

Where media id is the media id to be deleted and hname is the name of the host on which the media resides. You must specify this hostname only if your configuration uses multiple Media Manager databases.




5

Manual expiration of media with bpexpdate causes the media to be removed from the NetBackup catalog and to be deassigned in the volume database, regardless of the media’s prior state (FROZEN, SUSPENDED, etc).

11. Drives and robots connected via fibre channel cause increased complexity in the Media Manager configuration. On some operating systems, the use of fibre-to-scsi bridges may result in inconsistencies in the device path upon a server reboot. After rebooting the server, therefore, always verify the device configuration.

12. Global Data Manager 3.2 only supports NetBackup 3.2 servers.

13. NetBackup Modifications to GNU tar 1.09

Source for GNU tar version 1.09, including VERITAS modifications, is available on CD-ROM 2 (VERITAS NetBackup, Media Manager Documents for Unix Servers, release 3.2). It is in compressed tar format. VERITAS assumes no responsibility for the correct installation or use of this source code.

14. Hewlett-Packard server requires file system with long names.

On a Hewlett-Packard server, NetBackup must be installed on a file system that supports long file names.

15. Formatting disks for HP-Optical jukebox.

All platforms and operating systems do not support 1024 byte-per-sector platters. Most support only 512 byte-per-sector sizes (about 1.2 gigabytes per platter). VERITAS has tested 1024 byte-per-sector platters on both Hewlett-Packard and Silicon Graphics platforms.

Before purchasing optical disk platters for a HP-Optical juke box, check your vendor documentation to determine the optical-disk sector sizes supported by your platform and operating system. If you are unsure, call your VERITAS sales representative or VERITAS technical support.

In all cases, we also STRONGLY urge you to use preformatted platters.

16. ATRIA ClearCase application does not work correctly with backup products.

The ATRIA ClearCase application does not operate correctly with any backup product, including NetBackup. The ATRIA release notes suggest stopping the ClearCase application before starting a backup. One way to




5

accomplish this with NetBackup is to modify the bpstart_notify script to stop ClearCase before the backup and to modify the bpend_notify script to restart it when the backup is complete.

17. Some graphical user interfaces require a fixed-width font for columnar displays.

NetBackup graphical user interfaces that display columnar text require you to use a fixed-width font. If you use a proportional font, the columns do not align correctly. If your X server defaults to a variable-width font, you can force a fixed font to be used (all systems have a font named “fixed”) on either the command line or in the application defaults file. For example:

xnb -font fixed

18. Backing up files with both NetBackup and dump.ffs.

The dump.ffs utility looks at the file’s “inode-change” time when performing incremental dumps.

If NetBackup has backed up files in the same partition, the file’s inode-change time is modified when NetBackup resets access time for any file that is opened and read. Therefore, a dump.ffs incremental dump will see all files that NetBackup has accessed as candidates for an incremental dump.

There is no method by which NetBackup can reset the inode-change time. See the description of the (USE_CTIME_FOR_INCREMENTALS) option in the NetBackup System Administrator’s Guide - UNIX.

19. Allowing nonroot users to do NetBackup administration.

To allow nonroot users to perform NetBackup administration using either bpadm or xnb, see “Allowing Nonroot Users to Administrate NetBackup” in chapter 2 of the NetBackup System Administrator’s Guide - UNIX.

20. Allowing nonroot users to do Media Manager administration.

To allow nonroot users to perform Media Manager administration, see “Allowing Nonroot Users to Administrate Media Manager” in chapter 1 of the Media Manager System Administrator’s Guide - UNIX.

21. Nonroot access to NetBackup devices and media.




5

NetBackup media is “protected” from nonroot user access (both read and write) because the special files identifying the tape or optical drives allow only root usage when the Media Manager ltid process is executing. For example:

ls -al /dev/rmt/6_8mm8500cb /dev/rmt/6_8mm8500ncb

crw------- 1 bin bin 5 0x110603 Apr 27 09:06 /dev/rmt/6_8mm8500cbcrw------- 1 root bin 5 0x190603 May 18 05:51 /dev/rmt/6_8mm8500ncb

Other special files that reference the same device may exist. These files frequently define different densities at which the device is capable of writing. For example:

ls -al /dev/rmt/6_8mm8200

crw-rw-rw- 1 bin bin 5 0x000602 Apr 27 09:06 /dev/rmt/6_8mm8200

To protect NetBackup media from nonroot access, you must manually change the permissions on all of these special files to 600.

22. Nonroot permissions for mounting and unmounting media.

The commands for mounting and unmounting media (tpreq and tpunmount) are released with permission modes set to 500 (-r-x------). If you want any user in the system to be able to mount tapes, the mode can be changed to 555 (-r-xr-xr-x). If you want a specific group of users to be able to mount tapes, perform commands similar to the following:

cd /usr/openv/volmgr/binchgrp tapeusers tpreq tpunmountchmod 550 tpreq tpunmount

23. Man pages are not installed on clients.

NetBackup man pages are installed only on the server.

If you wish to provide man pages for the commands on client workstations, you will find troff source for these in the directory /usr/openv/netbackup/bin/goodies/man.

24. Robot host is NONE for Automated Cartridge System (ACS) media and ACS entries in robot inventory pick lists.In releases previous to 3.0, the robot host field for ACS media (volume) entries was not consistently handled. The robot host for ACS media is set to the value NONE to ensure that:




5

• all compatible media in an ACS robot can be placed in the same volume group,

• ACS robot inventory requests are sent to the host where the ACS robot is configured under Media Manager.

When selecting an ACS robot for an inventory operation through the xvmadm or vmadm interface, you will be prompted to enter the host. You should enter the host where the ACS robot is configured in Media Manager.

Note: Do not enter the ACSLS host unless the ACS robot is also configured on that same host.

25. On some platforms with NetBackup configurations it may be necessary to increase the system’s message queue resources to avoid bpsched hangs.

Example:

Make the following changes to the /etc/system file:

set msgsys:msginfo_msgmap=500set msgsys:msginfo_msgmnb=65536set msgsys:msginfo_msgssz=16set msgsys:msginfo_msgseg=8192set msgsys:msginfo_msgtql=500

Reboot the system.

26. If the backup of the NetBackup database fails with an EXIT STATUS of 124 and the database is on a RAID partition, check the bpbkar activity log for a message such as the following.

08:54:35 [27862] <8> bpbkar: WRN - Could not reset access time of/var/openv/netbackup/db/.snapshot/nightly.0/images/troi/INDEXLEVEL

Perform the following workaround to avoid this problem. On the xbpadm File menu, click Change NetBackup Database Backup Attributes. This opens the NetBackup Database Backup Attributes Dialog Box. The workaround is to list all files/directories in the /usr/open/netbackup/db directory in the "Include Paths:" text box. If you have questions about what should be done, contact customer support.

27. Local translations to other languages are not included in this package. VERITAS looks to outside translators to provide translations into local languages.




5

28. The opr and xopr commands for Media Manager are no longer supported in this release. The functionality of these commands is now contained in the vmoprcmd command. For more information, see the vmoprcmd man page.

29. The procedure for manually installing a UNIX client is as follows:

a. Create the NetBackup directory.

mkdir -p /usr/openv/netbackup/bin

b. Using the cp command, copy the client files into the new directory. For example with Linux:

cp -p /usr/openv/netbackup/client/Intel/Linux/*/usr/openv/netbackup/bin

(Replace the source directory with the location of the binaries.)

c. Edit the /etc/services file and add the following lines:

# NetBackup services

bpcd 13782/tcp bpcd

# End NetBackup services

d. Edit the /etc/inetd.conf file and add the following lines:

# NetBackup

bpcd stream tcp nowait root/usr/openv/netbackup/bin/bpcd bpcd

e. Create a file called /usr/openv/netbackup/bp.conf and add the lines:

SERVER = <name of your NB server>

CLIENT_NAME=<name of your NB client>

(This client name should be identical to the hostname.)

f. Reset the inetd with:

kill -HUP <inetd pid>

where the <inetd pid> is the PID returned from a ps command.



43

Problems Fixed Since the Last Release 6

The following section describes notable problems resolved by the 3.2 release of NetBackup.

1. Parameters have been removed from tpreq.

The following parameters for tpreq are no longer supported.

-r (tape rewind device file)

-b (optical block device)

-id (location name)

2. The bprecover command was modified to enable the user to restore a NetBackup database from a write-protected tape.

Users were unable to use the bprecover command to recover the VNetBackup database tape when the tape was write-protected. The following error was received:

./bprecover -l -tpath /dev/rmt/6cbn -v

open() of /dev/rmt/6cbn failed, Permission denied

media open error

3. A backup no longer fails with a status of 10 - allocation failed.

This failure occured when a very large number of files and directories were being backed up in which the length of the path exceeded 100 characters.

4. The scheduler debug logs now will close after midnight and reopen the next day’s logs.




6

5. The bp command no longer passes the destination client name to bprestore if the user does not explicitely set the value. This allows bprestore to set the correct default destination client name. The destination client name used by bprestore may be different than the local hostname.

6. A failure during image duplication (caused by a server crash, for example) no longer results in NetBackup reporting that two copies exist.

This problem made it impossible to initiate the duplication again.

7. Inadvertent duplication of the same image by different bpduplicate processes no longer causes the successful image duplicate to be deleted.

NetBackup will detect simultaneous duplication attempts and report an error.

8. Performance degradation would occur if multiplexed backups were performed when the client and server were the same machine. Shared memory is now correctly initialized so the performance of the new backup is not degraded.

9. A host name comparision problem with the Media Manager has been corrected where the host name IP addresses in the form of www.xxx.yyy.zzz exceeded 13 characters.

10. The Update Volume Configuration feature for the robotic inventory reported inconsistent information.

Media type mappings are used to determine the resulting Media Manager media type, with the only exception being for cleaning tapes, which requires configuration of barcode rules for TLM robots. Previously, the non-default inventory update option media types and barcode rules caused actual and predicted media types to differ.

11. Failures were reported when bprd accepted interrupts; a missed completion message appeared as a hang condition when the server and client were under heavy activity. This has been corrected.

12. Occasional EXIT STATUS code 60 (client cannot read the mount table) failures on HP-UX 11.00 and NCR platforms were corrected.

13. Backup of named pipes (FIFO) sometimes failed on the DEC Alpha platform. This was corrected.




6

14. A deadlock condition could occur on DEC OSF during tape mounts or dismounts. In addition, intermittent "Device busy" errors were eliminated.

15. The backup process could hang when an unavailable NFS mount existed on a client. This was corrected.

16. The NetBackup database image file was sometimes corrupted when multiple database cleanups attempted to expire the same image. This was corrected.

17. When backing up a raw partition on HP-UX using shared memory, Netbackup produced an image which could not be restored. This was corrected.

18. RPC communication problems occurred between the Automated Cartridge System (ACS) robotic daemon and STK’s Library Station. The Library Station was unable to send responses to these RPC packets because the port appeared to be unreachable even though the ACS robotics could still be waiting for a response. Network packet fragmentation appeared to be a precursor of the problems. This was corrected.

19. Problems seen on Windows NT or DEC Alpha when multiple backups were happening at the same time were corrected. A symptom of the error was a failed backup with EXIT STATUS 84 "media write error".

20. File permissions for jobs in the netbackup/db/jobs/done directory had read-write permissions set for group and other as opposed to the original permissions. This was corrected.

21.bprecover falsely reported "bprecover terminated by signal (13)", even though all data was recovered. This was corrected.

22. A local file system or loop back file system (lofs) was incorrectly considered an NFS file system during backup and was not backed up if "Follow NFS" was set to "No". This was corrected.

23. Dismount requests were not functional when using Automated Cartridge System (ACS) robotic control with configurations involving StorageTek’s Library Station, even though they were logged as successful. This was corrected.




6

24. Attempts to obtain the command status from the Distributed AML Server (DAS) were unsuccessful when using Tape Library Multiple (TLM) robotic control for EMASS (Grau) AML robobtic libraries on AIX 4.3.1. This was corrected.

25. A backup or restore request failed because of a transitory problem on the server side that could potentially be cleared up with a retry. This was corrected.

26. A backup or restore request failed because of a transitory problem on the server side that could potentially be cleared up with a retry. This was corrected.

27. The Media Manager sg driver was changed for Solaris to enable it to function correctly with the JNI Fibre Channel adapter and driver.

28. When using Automated Cartridge System (ACS) robotic control with configurations involving multiple Library Storage Modules (LSMs) within the same ACS robot, a cancel mount scenario could cause the ACS daemon to abort. This was corrected.

29. A saved NB-Java Activity Monitor data file could be overwritten. The capability to conditionally overwrite a saved Activity Monitor data file was added.

30. An NDMP drive was sometimes selected for a non-NDMP backup. This was corrected.

31. There were missing or 0 length files in the NetBackup image catalog due to compressing or decompressing the database asynchronously. This was corrected.

UNIX Server1. There no longer is a 2 gigabyte limitation when creating a backup of the

Netbackup databases on disk.

2. The NetBackup and Media Manager X-Window GUI’s would not run on AIX 4.3. The installation was changed to put the binaries in the X11R6 directory instead of the X11R5 directory for AIX 4.3.




6

3. The backup scheduler was changed to correct a problem which could occur on large installations that stopped the scheduling of new jobs for an extended time period.

4. The backup scheduler was terminating when some errors would occur causing backup jobs to exit with an EXIT STATUS 50 in the Activity Monitor. Changes were made to the scheduler to handle the errors more gracefully so that termination would not occur.

5. Changes were made to the NetBackup database cleanup process to reduce delays in backup scheduling for large installations.

6. Extended file attributes are now backed up.

Clients1. The backup failed if a backup was requested from a client but the hostname

sent on the request did not match the bp.conf CLIENT_NAME. This condition could occur if the client had two active network interfaces. The client’s bp.conf CLIENT_NAME is now used for the class name comparison rather than the client’s hostname.

Windows NT/95/98

1. All items can be marked for restore on the graphical user interface.

When a directory has lots of files, in the thousands, the graphical user interface on a Windows 95 machine sometimes would not allow all of the items to be marked for restore with the mouse.

This is fixed in this version of NetBackup by changing the logic that tracks the mouse position.

NetWare

1. The server no longer crashes when the user selects a restore before specifying a NetBackup server or client.

If a NetBackup server and/or NetBackup client was not specified through BP.NLM on the NetWare server, the server would crash when the user attempted to perform a restore from the main menu. This problem was fixed in this version of NetBackup.




6

2. The interface will successfully submit a request through BPSRV.NLM.

When using the graphical user interface from a Windows 95 or a Windows NT machine and attempting to submit a request through BPSRV.NLM on the NetWare server, the request would occasionally failed. The interface would eventually timeout trying to submit the request.

NetBackup now makes sure that the sizes of variables that the interface is sending are the same size that the BPSRV.NLM is expecting.

3. The NetBackup initial server list is displayed more quickly.

When bringing up the graphical user interface from a Windows 95/98 or a Windows NT machine in a network with a complicated NDS tree, it use to take quite a long time for the initial server list to be displayed.

NetBackup now performs additional checks before trying to access the machines that are returned as possible servers.

4. When using the Allow Scheduled Backups option and the graphical user interface, all entries are saved when the resource list is modified.

When modifying the resource list through the graphical user interface using the Allow Scheduled Backups option, and when there are lots of entries, some entries may not get saved (in the BP.INI).

NetBackup now disables user-input for the interface while the information gets saved.

5. Container objects are now backed up through BP.NLM.

When selecting items for restore from the NDS tree through BP.NLM, they may not get restored. The items this occurs on are container objects in the NDS tree. If non-container objects are selected, they will be restored.

NDS container objects use brackets ([]) as part of the name. Brackets are wildcard characters on the NetBackup server. NetBackup now treats NDS objects with special logic when submitting a restore.

6. When using the graphical user interface from a Windows 95 or a Windows NT machine and attempting to submit a request on the NetWare server, the request no longer fails due to a timeout condition.




6

7. A delay no longer occurs when bringing up the graphical user interface from a Windows 95 or a Windows NT machine in a network with a complicated NDS tree. Additional checks are now performed before trying to access machines that are returned as possible servers.

8. Some items selected for restore from the NDS tree were not restored. this was corrected.

Database Extensions1. Changes were made to support SAP R/3 4.0 file systems larger than 2 GB.

2. Database extension installation aborted if installing on a client or media server.

The install_dbext script aborted if the /usr/openv/netbackup/version file existed, which only exists on the master server. The file location for all servers was corrected to be /usr/openv/netbackup/bin.

3. A failure restoring SQL-BackTrack multiplexed images with a large database with a large number of data files was corrected, and the dependency on "redundant success" messages was removed from the server, which had caused some backup jobs to hang.

4. After the completion of every backup job, the Oracle database extension immediately requested the media id of the backup image from NetBackup. This request failed if the server’s time was different from the client’s time. The allowed time difference was increased from 30 minutes to 24 hours, which eliminates this problem.

5. If an archive backup was executed at the same time as an online database backup, the online database backup could fail with the following error messages in the backint and sap backup logs:

ERROR: The switch.lis or switch.sem exist without a lock

ERROR: cannot read switch = log file:/oracle/<SID>/sapbackup/.switch.log

FlashBackup1. Corrected the case where xbp failed when restoring files from incremental

backups. This was due to incorrect file entries in the backup image.




6

2. Optimized getuid/getgid for better file mapping performance.

3. Corrected the case where a core dump could occur when backing up raw partitions with VxFS mounted file systems.

4. Corrected the case where VxVM managed raw partitions could not be mapped due to the different format VxVM used for the raw device pathname (/dev/vx/rdsk instead of /dev/rdsk).

5. Users of xbp were not able to display sub-directory pathnames when browsing for Auspex/Fastbackup backup images. This problem was isolated to cases where the sub-directory pathnames are actually filesystems mounted on the parent directory.

6. Restoring individual files from FlashBackup or Auspex/Fastbackup images failed in some heterogeneous environments. This was corrected.

7. FlashBackup now supports UFS mounted file systems on raw partitions of greater than 2 gigabytes.

8. FlashBackup backups terminated from the Job Monitor (Xbpmon) failed to close the filesystem snap. The user had to manually remove the snap with the /usr/openv/netbackup/bin/driver/snapoff command. This was corrected.

9. The FlashBackup snaplist command output was garbled if a long raw device or cache name was used. This was corrected.



51

Known Problems and Limitations 7

The following list explains the known problems and limitations in this release of the NetBackup and Media Manager, and includes workarounds where known.

1. Jobs are not deleted from the jobs list immediately after a master server crash and reboot.

If the master server crashes and is rebooted, the job monitor incorrectly assumes that jobs running at the time of the crash are still active and queued. It does delete them, however, when it starts the first backup after the reboot.

2. Backing up real time files is not supported for SGI IRIX xfs.

3. Manually initiating a backup of the NetBackup database.

Backing up the NetBackup database may fail if it is manually initiated and backups are in progress. The workaround for this is to initiate these backups when no other NetBackup activity is occurring, or to schedule the backup of the database to occur automatically.

4. With the current activity monitor, you can not kill a queued restore. A restore is in the queued state from the time it is first received until NetBackup has figured out what files are needed from each of the images.

Other limitations with monitoring restores include:

• Some columns on the job monitor will be empty for restore jobs.

• Unable to view detailed job monitor for restores.




7

5. Daylight Savings Time causes minor problems for NetBackup.

When Daylight Savings Time changes occur, anomalies may occur in the scheduling of some client backups and the displaying of some report screens. This is due to the method NetBackup uses in calculating the beginning of a backup window and comparing it to (potentially) completed backups.

In the Spring, when Daylight Savings Time takes effect, you will see misordered reports (for example, All Log Entries, Backup Status). This is due to the discrepancy between Greenwich Mean Time (which UNIX uses) and your system’s “local time.” After the time changes (for the day of the time change only), you will see entries logged between midnight and 2 a.m. displayed after entries logged between 3 a.m and midnight. You will also have to adjust the starting time of the display to 11 p.m. of the previous day to see all entries made for that day.

If a backup occurs within 1 hour of the backup window’s opening and the backup window spans the time change, the backup may be re-executed (in the fall) or seen as already having occurred (in the spring). This is due to the fact that once a backup has completed it is given an absolute time, while the opening of the backup window is calculated in a relative fashion.

Until this algorithm is corrected, you should carefully check backups that are scheduled to occur when the time changes to assure that your data is adequately protected.

6. Class and schedule name restrictions.

You should not create class or schedule names that include the comma (,) character; for example: full, many.

The bpadm utility permits this syntax, but xnb does not.

7. NetBackup scheduler does not automatically refresh storage unit list during backups.

The backup scheduler on the master server does not refresh the list of storage units while backups are active. If a slave server that was not active when backups started becomes available during backups, the scheduler does not recognize that this slaves storage units are now available for scheduling. A manual refresh can be forced with the following command:

/usr/openv/netbackup/bin/admincmd/bpschedreq -read_stunits




7

8. Only NDMP on Network Appliance servers is supported. Other platforms supporting NDMP have not been verified to function with NetBackup.

9. Files Written count (Current, Previous) in job monitor.

When viewing the Files Written count for a job in the job monitor, the value for Current Files Written does not include the extra directory entries (which are used during restore file browsing). The value displayed for Previous Files Written does include those extra directory entries, and will thus be slightly larger.

10. Restores of NFS mounted files fail when attempting to perform a server directed restore. The progress log may show the following types of messages.

Could not make directory /net/machine/abc: The file accesspermissions do not allow specified action

Couldn’t change access and modification time of/net/machine/abc: Not owner

Couldn’t change access and modification time of/net/machine/abc: Operation not permitted

Could not create file /net/machine/abc/123: Permission denied

Could not create file /net/machine/abc/123: A file or directoryin the path name does not exist

To work around this situation, the owner must restore the NFS files on the client machine.

11. The NetBackup GUI user interface (xbp) for RedHat Linux was linked dynamically. This means that in order to use xbp you must have RedHat Motif version 2.1.10 installed. If it is not installed you will see an error similiar to the following:

/usr/openv/netbackup/bin/xbp: error in loading shared librarieslibXm.so.2: cannot open shared object file: No such file ordirectory

12. When initiating a user interface (bp or xbp) on SCO OpenServer Release 5.0.5 it may fail with the following error:

Exit status = client cannot read the mount table

The NetBackup executable bpbkar may fail when attempting a backup on SCO OpenServer Release 5.0.5 with the following error:

FTL - Cannot statfs <filesystem name>Errno = 2: No such file or directoryINF - EXIT STATUS 60: client cannot read the mount table




7

The reason for this problem is that on SCO OpenServer the mt_filsys field of the mnttab structure is defined as an array of 32 characters (see config file /usr/include/mnttab.h) including ending null. If a mounted filesystems path exceeds this size it is truncated and the statfs command fails.

Until this is fixed by SCO the workaround is to not mount filesystems with a path greater than 31 characters.

13. The multiple data streams feature when used in autodiscover mode can cause a delay in the scheduling of jobs if many classes and clients use it. This is because scheduler must contact the client to discover the current backup requirements. To reduce the impact of this, there is a parameter called preprocess interval that may be set with the bpconfig utility or via bpadm. Using the admicmd/bpconfig utility use the -prep option to set the number of hours for the preprocess interval. In bpadm, preprocess interval is found in the global parameters. This value of preprocess interval limits the number of times that the client is contacted by allowing autodiscover to occur only this often. The default value for this is 4 hours. If the time spent preprocessing is excessive due to a large number of clients, the period may be increased. If there are schedules with a frequency of less than 4 hours, the preprocess interval may be reduced. (setting the preprocess interval to 0 will cause the default of 4 hours to be used).

14. Digital Alpha systems with the OSF/1 operating system may crash when backing up a symbolic link that has Extended File Attributes. The console may display the following type of message.

panic (cpu 1): ufs_getproplist: pl_descp->pl_magic

The crash is due to an operating system bug. The use of the /bin/tar command to archive the symbolic link will also cause the system to crash. This problem has been seen on Digital Alpha machines running the OSF/1 version 3.2 214 operating system.

To work around this problem, add an entry for the symbolic link to the exclude_list for the system or remove the symbolic link.

15. The NetBackup database entries containing the list of backed up files and directories (*.f files) currently have a file size limit of 2GB.




7

16. A media server (i.e., slave server) can be a Global Data Manager (GDM). However, in this release, one must install the GDM software on the media server’s master. All the configuration instructions in the GDM Configuration Guide (/usr/openv/netbackup/GDM_Configuration_Guide.txt) still apply from the point of view of the media server being the GDM. After configuration is complete, the GDM host to specify in the NB-Java login dialog is the media server. GDM is a separately priced product that allows the designation of a single console to act as a Master of Masters. A Master of Masters has the ability to administer multiple existing master servers and their individual environments from a central location.

17. Sun Dynamic Reconfiguration and the VERITAS sg driver.

On Sun systems which support Dynamic Reconfiguration (DR), the VERITAS sg driver must be unloaded before DR operations can be performed.

a. Stop the NetBackup and Media Manager daemons.

/usr/openv/netbackup/bin/goodies/bp.kill_all

b. Uninstall the sg driver.

/usr/sbin/rem_drv sg

c. Perform DR operations.

d. Update NetBackup configuration as necessary.

As the result of dynamic reconfiguration, the device files associated with devices may have changed. NetBackup must be reconfigured to use the new device files.

See chapter "Sun4/SPARC Running Solaris 2.5/2.5.1/2.6/7.0" in the VERITAS Media Manager Device Configuration Guide for more information.

e. Install the sg driver.

/usr/openv/volmgr/bin/driver/sg.install

f. Restart the NetBackup and Media Manager daemons.

/usr/openv/volmgr/bin/ltid

/usr/openv/netbackup/bin/initbprd




7

UNIX Server1. bprd or bpdbm fails to obtain its required port.

If bprd is terminated using the kill command rather than either bpadm or xbpadm, it may be unable to bind to its assigned port when next initiated. If the problem persists longer than ten minutes, you may need to reboot the server in order to clear the problem.

If bpdbm is terminated using the kill command rather than the /usr/openv/netbackup/bin/bpdbm -terminate command, it may be unable to bind to its assigned port when next initiated. If the problem persists longer than ten minutes, you may need to reboot the server in order to clear the problem.

This problem may be identified by lines in the process activity log similar to the following:

<16> getsockbound: bind() failed, Address already in use (114)<32> listen_loop: cannot get bound socket. errno = 114<4> terminate: termination begun...error code = 146

Similar entries are found in the error logs.

2. vmconf limitations on HP9000-700 at HP-UX 10.01.

The vmconf configuration script for HP9000-700 platforms running HP-UX 10.20 cannot be used for configuring robotic peripherals which have SCSI robotic controls utilizing logical unit number (LUN) 1. This currently affects the HP DAT autoloader and the Quantum DLT2700/4700 peripherals. The workaround is to configure these devices with the Java Media Management interface, xdevadm or tpconfig, entering the device paths as recommended in the Media Manager Device Configuration Reference Manual - UNIX.

3. xbp cannot correctly perform OK requests on two or more instances of the xbp_confirm dialog, if those dialogs are displayed simultaneously.

The xbp_confirm dialog is used when requesting user-directed backups, archives, or restores. One xbp_confirm dialog can proceed with a click on its OK button, the other(s) cause xbp to wait indefinitely with the cursor shown as a wristwatch. The xbp process can be cleaned up with a kill command from a shell prompt. There is no limitation against sequentially displayed instances of the xbp_confirm dialog, i.e., once you OK or Cancel an xbp_confirm dialog, you can proceed to use xbp in other ways possibly including additional backup or archive or restore requests. The problem




7

occurs only if you bring up additional xbp_confirm dialogs before using OK or Cancel to complete usage of the previous instance. In a future release, xbp will be modified to either allow multiple simultaneous xbp_confirm dialogs, or to prevent this usage with a specific warning message.

4. Block-level Incrementals using VxFS requires the use of VERITAS File System version 3 and cannot be used to backup raw partitions.

5. Problem with arrow key usage on bp and bpadm on DEC Alpha

The program will terminate with a core file when arrow keys are used on scrollable displays for bp and bpadm. This problem occurs on DEC Alpha. If you want to scroll scrollable displays, use the letter keys.

6. Robot Inventory Menu

In the Media Management interface, xvmadm, it is possible from the reports Robot Inventory menu to initiate a robotic inventory update by double-clicking to select a robot, even though only read-only inventory types are presented in the dialog.

7. Ejecting tapes through the inport of the ATL P3000 or Sun StorEdge L11000 robotic library can lead to the error "unable to sense robotic device."

The workaround is to wait until the robot has finished reinitializing (checking its media port for media) after the inport/export door has been closed, before responding in the GUI interface that the tapes have been removed. During testing, the library initialization period for an empty inport lasted for 2 minutes, 10 seconds.

8. When configuring robotic volumes with a media management New Volumes / Add Volumes interface, volumes will be added to the Media Manager volume database, even if an error is reported because one or more volumes were not currently in their specified slots, or if the barcodes on added volumes could not be verified (for some robot types).

The workaround is to use robotic inventory for managing volumes. With robotic inventory, only the volumes actually contained in the robot will be configured, and knowledge of slot info is not required.




7

PC Clients1. When installing the client (both local and remote installs) the client name is

written in all lower case to the registry. If the classes on the server do not specify the client names in all lower case, backups will fail because the names will not match.

2. IBM Directory and Security Server Environment Considerations.

NetBackup in general, and the NetBackup Client for OS/2 in particular are not Distributed Computing Environment (DCE) compliant applications. This means that they are not built to call the DCE services for authentication and naming.

Instead, NetBackup OS/2 relies on IBMs backward compatibility of the IBM LAN Server APIs to perform authentication etc. IBM DSS for OS/2 modifies the behavior of many of the IBM LAN Server APIs, especially for user account information and access privilege. Consequently, NetBackup OS/2 in an IBM DSS environment may have difficulty accessing, reading, writing, and using Access Control Lists.

3. Alternate path restores for Novell NetWare clients must be done from the Novell server that is the NetBackup client.

This limitation exists because xbp on the UNIX system is unable to resolve the namespaces on Novell servers.

4. Files with the following characteristics are not scanned for viruses:

• Fully qualified filenames longer than 256 characters

• Compressed or zipped files

• Open files that are locked

5. Email being sent to NT client user.

Email notifications of backup status is not supported.

6. Client software compression.

You cannot choose to compress backup images from NT NetBackup clients.

7. No client installation and update.

Automatic client installation and update when the client is added to a class is not supported at this release on the Windows NT NetBackup server.




7

8. When changing the debug logging levels, some of the changes take effect right away while other require the BPCD.NLM to be unloaded and then reloaded. A change to the level debug value will take effect right away while a change to the tcp debug value will not take effect until the BPCD.NLM is unloaded and then reloaded.

This only pertains to NetWare file servers that are NetBackup clients.

9. bpstart_notify and bpend_notify scripts

When using bpstart_notify and bpend_notify scripts on Windows NT or Windows 95/98 clients, the script should not require user interaction to complete. The backup will wait for the notify script to complete and will eventually timeout. The backup will fail with a status code of 24: socket write failed.

10. It is not possible to install NetBackup PC Client or Windows NT server software in a path that contains one or more spaces.

Database Extensions1. The procedure documented on page 37 of the NetBackup for Oracle System

Administrator’s Guide - UNIX manual is incomplete. Substitute this information for what is published in that manual.

For example:

touch /usr/openv/netbackup/bin/ \[libobk.so.1 | libobk.sl | libobk.a | libobk.so]

For Oracle 7.3.X, include the API library in the library search path. The following platforms require additional linking steps.

For SGI (IRIX), create a symbolic link to the API library.

cd /usr/openv/netbackup/bin

ln -s libbobk.so libobk.so.1

For Data General (DG/UX), create a symbolic link to the API library and make a new executable.

cd $EBU_HOME/lib

ln -s /usr/openv/netbackup/bin/libobk.so libobk.so

make -f ins_obackup.mk install

For earlier levels of Oracle, enter ... etc.




7



61

NetBackup-Java 8

IntroductionThe NetBackup-Java (NB-Java) product is a suite of Java applications that allows administrators to configure NetBackup (NB) and monitor the operation of NetBackup as well as allowing users to restore, back up or archive files that they own. The latter capability is available in the NB-Java client application titled ’Backup, Archive, and Restore’ (more commonly referred to as jbp). Java is a registered trademark of Sun Microsystems.

On-line help is available from within the user interface. There are no printed manuals. However, familiarity with the contents of the NetBackup System Administrator’s Guide - UNIX, NetBackup Release Notes - UNIX, Media Manager System Administrator’s Guide - UNIX and the Media Manager Device Configuration Guide is required to configure NetBackup and for general understanding of the product. See Appendix A, “Related Documents,” for a complete list.

Following are the topics in this document:

• System Requirements

• Operational Environment Overview

• NetBackup Administration via NB-Java

• NB-Java Client Application (jbp)

• Remote Administration

• The Directly Connected Display Monitor as Console

• Another NB-Java Enabled NetBackup Client or Server as Console




8

• A Windows NT, 98 or 95 System as Console

• Authorizing Users

• Authorization File

• Nonroot Usage of NB-Java Administrator Applications

• Authorizing Nonroot Users for Specific Administrator Applications

• Capabilities Authorization for jbp

• Converting Previous auth.conf Files

• Configuration Options

• Configuration Options for NB-Java Client Application - jbp

• Alternate Client Restores with jbp

• Default NetBackup Host to Log Into

• Changing Fonts and Font Sizes on UNIX Platforms

• Usage

• Operational Notes

• NB-Java Known Problems and Limitations

• NB-Java Windows Display Console Known Problems

• Java Problems Seen in NB-Java

• Known Problems with Display of Online Help

• Errors When NetBackup Daemons Are Not Running

• Performance Improvement Hints

• Troubleshooting Guide

• Insufficient Memory

System RequirementsNB-Java GUI applications allow you to administer or perform user back up and restore operations with the NB-Java application server that is started on demand via inetd on all UNIX platforms supported by NetBackup. See “Supported Platforms” on page 14.



NetBackup-Java 63

8

NB-Java GUI application software is installed and configured only on the supported Solaris and HP-UX platforms listed in Table 2 on page 14 using the procedures documented in the NetBackup Installation Guide - UNIX. NetBackup client capabilities are installed and configured on Solaris Intel 2.6 or 7.

To facilitate administration and user back up and restore operations on other UNIX platforms we have the ’NetBackup-Java Display Console for MS Windows’ product. It is available on the UNIX NetBackup Server CD-ROM. It runs on Windows NT 4.0, 95 and 98 and is to be used as a remote display console for any NetBackup UNIX host. It doesn’t require any other NetBackup software to be installed on the Windows machine, but it does require a TCP/IP connection. It is possible to be remotely located with the Windows NT, 98 or 95 ’NB-Java display console’ using PPP type software via a dialup communication line and perform NetBackup administrative tasks.

Please note the following with respect to graphics display console combinations.

• We only support the CDE and Motif window managers when using NB-Java. There are a fair number of user interface anomalies using the various window managers available on the UNIX platforms. Many of these problems are documented as Java bugs. Most of these problems are due to unusual or non-standard window manager configurations and will occur randomly and infrequently. In the most common cases of misplaced or shifted components within a dialog, simply resizing the dialog will repaint the display and cause the interface to be displayed correctly. Although CDE, MWM and OLWM have the most reported bugs, this is largely due to their popularity; the user should not be encouraged to use a window manager such as fvwm or twm instead. The recommended window manager is CDE. This is the window manager under which we have seen the best overall performance.

• Remote display back via the DISPLAY environment variable to machines running different operating systems is not supported, e.g., starting NB-Java applications on Solaris and displaying to an HP workstation.

• NB-Java doesn't support remote display back to a Windows NT/95/98 machine using any X terminal emulator software. Please use the 'NetBackup-Java Display Console for MS Windows' product.

• NB-Java doesn't support monochrome terminals.

• Due to problems seen trying to use an NCD color X terminal connecting to NB-Java on HP 10.20, we do not support it.




8

Operational Environment OverviewAll operations affect NetBackup or files on the machine in which you login to via the login dialog of the NB-Java applications, i.e, commands /usr/openv/netbackup/bin/jnbSA and /usr/openv/netbackup/bin/jbpSA. Refer to “Usage” on page 81 for more information on these commands, .

The login occurs to the NB-Java application server running on the host specified in the NB-Java login dialog window. In the case of the administrator applications, this host is usually a NetBackup master server and referred to as the 'administrative server.' For end user back up and restore operations via jbp the host could be a UNIX NetBackup client. Once successfully logged in, all operations initiated in NB-Java applications are performed by the application server running on the specified host.

NetBackup Administration via NB-Java

Use of NB-Java to administer NetBackup can be done either directly (locally) on a NetBackup Solaris or HP-UX master server machine, remotely from a NetBackup Solaris or HP-UX client or slave server, or remotely from a Windows NT/95/98 machine running the 'NetBackup-Java Display Console for MS Windows' product.

• Local Administration

Local administration means that all NB-Java GUI applications are executed on the NetBackup master server. However, one may still use a different machine for remote display (see “System Requirements” on page 62 for restrictions) of the application via the setting of the DISPLAY environment variable prior to starting up the application or use the -d or -display options on the jnbSA or jbpSA commands.

• Remote Administration

Remote administration can be performed one of three ways with NB-Java:

• Via login to the NB-Java application server on a remote NetBackup master server

• Via 'Change Server' capabilities present in most of the NB-Java GUI applications

• Or via use of the Global Data Manager product



NetBackup-Java 65

8

NB-Java Client Application (jbp)

The NB-Java client application called ‘Backup, Archive, and Restore’ (jbp) allows users to back up, archive, and restore files subject to file permissions. (See the section titled ‘File Permissions Required By NetBackup ’ in the NetBackup User’s Guide - UNIX.) These operations are referred to as user-directed operations.

The application can be started directly via the jbpSA command or via the jnbSA launch screen on any NetBackup Solaris or HP-UX master, slave, or client machine. It can also be started via the launch screen on any Windows NT/95/98 machine running the ‘NetBackup-Java Display Console for MS Windows’ product.

You may log into any NetBackup UNIX client via the login dialog, including the local machine. The client you log into is the client on which the user-directed operations will be performed by default. The application will be able to back up and archive files only from this default client. However, with appropriate authorization, it can restore files from or to alternate clients.

Remote AdministrationRemote administration using NB-Java is done by logging into the NB-Java application server that is available on all UNIX NetBackup master servers. The NB-Java application server you log into is called the administrative server. You may perform NetBackup administration on the administrative server or use it to remotely administer any NetBackup master server. The administrative server sends requests to the remote NetBackup server that it is managing and the remote NetBackup server executes the requests.

The terminal or workstation where the administrator views and controls the NetBackup Administration - Java interface is called the 'console' and can be either of the following:

• A display monitor that attaches directly to the video output of the administrative server.

• Another NB-Java enabled NetBackup client or server. See the supported Solaris and HP-UX platforms listed in Table 2 on page 14.

Administrative serversends requests

Server being managedexecutes requests




8

• Windows NT, 98, or 95 system with NetBackup Administration - Java interface programs installed.

The configuration and operation is different, depending on which type of display console is used.

The Directly Connected Display Monitor as Console

When the console is the system's display monitor, the administrator logs into the administrative server and starts the NetBackup Administration - Java interface on that system. The administrator can then select a remote NetBackup server to manage or manage the administrative server. The requirements for this configuration are:

• Administrative Server

• NetBackup master server running NetBackup 3.2.

• One of the supported Solaris or HP-UX platforms listed in Table 2 on page 14

• Remote Server

• NetBackup master server running NetBackup 3.2 on any supported UNIX platform or NetBackup 3.2 on Windows NT. See “Supported Platforms” on page 14.

• Server list on the remote NetBackup server must contain the name of the administrative server. This is necessary for the administrative server to establish a connection to the remote server.

Example

In the figure below, the administrator logs in to shark and uses shark's administration interface to manage the NetBackup configuration on tiger.

In this figure:

Administrative server Remote servertigershark

(UNIX or Windows NTNetBackup master)

Server list: shark



NetBackup-Java 67

8

• shark is the administrative server per the requirements listed above.

• tiger is the remote server being managed and must be a NetBackup master server per the requirements listed above. Notice that shark is in the server list on tiger.

The operating procedure in this instance is:

1. Log in to shark.

2. Start the NetBackup Administration - Java interface on shark.

3. Start the desired application (for example, Backup Policy Management).

4. Use the Change Master Server command on the Classes menu (in this example) to specify another server to manage (tiger in this example).

Most of the main applications windows (Backup Policy Management, Device Monitor, etc.) provide a change server or host command on the file menu or its equivalent.

Another NB-Java Enabled NetBackup Client or Server as Console

The administrative server the administrator logs into can be changed on the NB-Java login dialog. In this release the server the administrator logs into must be a supported NetBackup UNIX master server.

In this execution scenario, the administrator logs into an NB-Java enabled client or server and starts the NB-Java interface on that system. The administrator can then select a remote NetBackup server to manage by providing the host name of the master server on the NB-Java login dialog. This is a variant of the first execution scenario. Here, upon initialization, all applications will be communicating with the remote master whereas in the previous scenario only the applications in which you 'changed to' another NetBackup master server communicate with that remote NetBackup master server. The requirements for this configuration are:

• NetBackup client or server

• NetBackup client or server running NetBackup 3.2.

• One of the supported Solaris or HP-UX platforms listed in Table 2 on page 14




8

• Remote administrative server

• Any supported UNIX NetBackup master server. See “Supported Platforms” on page 14.

Example

In the figure below, the administrator logs in to shark and uses shark's NB-Java interface to login to the NB-Java application server running on tiger and manage the NetBackup configuration on that master server.

In this figure:

• shark is either a NB-Java enabled NetBackup client or server per the requirements listed above.

• tiger is the remote administrative server being managed and must be a NetBackup master server per the requirements listed above.


1. Log in to shark.

2. Start the NB-Java interface on shark and change the server name in the login dialog to tiger. Complete the login dialog with a username and password that are valid on tiger.

3. Start the desired application (for example, Backup Policy Management). Its context is the NetBackup configuration on tiger.

A Windows NT, 98 or 95 System as Console

It is also possible to install only the graphical user interface part of the NB-Java software on a Windows NT, 98 or 95 system and use that system as a console. When starting the NB-Java interface on the console, the administrator is prompted to login to an administrative server.

The requirements for this configuration are:

NB-Java enabledNetBackup client or server

shark

NetBackup UNIXmaster server

tiger



NetBackup-Java 69

8

• NetBackup-Java interface software installed on the Windows NT, 98, or 95 system being used as the console. No other NetBackup software is necessary to administer NetBackup on a supported administrative server.

Note: It is possible to be remotely located with the Windows NT, 98 or 95 'display console' using PPP type software via a dialup communication line.

• A NetBackup UNIX master server available to log into. The requirements for this system are the same as discussed previously, i.e., for remote administrative servers.

Example

In the figure below, the administrator logs in to tiger when starting the administration interface on bear.

In this figure:

• bear is the display console and does not require any NetBackup software other than the NetBackup-Java interface software. The administrator starts the NetBackup Administration - Java interface on bear but must login to tiger (or another administrative server) to perform any administration.

• tiger is the remote NetBackup server being managed and must be a NetBackup master server on any UNIX platform that NetBackup supports.


1. Start the NB-Java interface on bear.

2. When the login dialog box appears, specify tiger as the NetBackup server (in addition to specifying a user name and password).

3. Start the desired application (for example, Backup Policy Management).

Consolebear

Remote servertiger

Windows NT, 98, 95 UNIX NetBackup master




8

Authorizing UsersUsers of the NB-Java applications are required to login to the NB-Java application server running on the NetBackup host on which they wish to administer or perform user back up and restore operations.

The file /usr/openv/java/auth.conf contains authorization data for application access by users on the machine in which they intend to do NetBackup administration or back up, archive and restore files. This file exists only on NetBackup 3.2 Solaris and HP-UX machines where the NB-Java interface software is installed. On all other NetBackup UNIX machines the NB-Java application server by default authorizes users as follows, i.e. the contents of the released version of the auth.conf file.

• NetBackup servers - NB-Java administration capabilities for only the root user, end user back up and restore capabilites for all other users.

• NetBackup clients - End user back up and restore capabilities only for all users.

On these other NetBackup UNIX servers and clients, this file can be created if the default authorizations need to change.

Users doing remote administration of NetBackup or end user operations using jbp must have valid accounts on the NetBackup UNIX server or client machine.

Nonroot users can be validated to administer NetBackup via NB-Java. Also, users can be authorized for specific capabilities of NB-Java.

Authorization File

The released version of the authorization file that is installed on Solaris and HP-UX clients and servers contains only the following entries.

root ADMIN=ALL JBP=ALL* ADMIN=JBP JBP=ENDUSER+BU+ARC+ACTIONS

The first field of an entry is the username. An asterisk indicates that any username will be accepted and the user will be allowed to use the applications as specified.



NetBackup-Java 71

8

The first entry allows root users to use all of the NB-Java applications. The ’ADMIN=ALL JBP=ALL’ part of the entry is required to allow access to all the applications and all the administrator related capabilities. The ’JBP=ALL’ part of the entry is required to allow access to the NB-Java client application including administrator related capabilities.

Because of the asterisk in the first field of the second entry, NB-Java validates any username for access to the NB-Java client application - jbp. The ’JBP=ENDUSER+BU+ARC+ACTIONS’ part of the entry allows end users to back up, archive and restore files.

When starting NB-Java administrator applications locally on a NetBackup server or jbp locally on a NetBackup client, you will only be able to successfully login if the username is the same as that used to login to the operating system. The ’username’ and ’password’ fields in the login dialog are not required if logging in to the NB-Java application server on the local machine, i.e., you have already been authenticated upon login to the operating system.

If the username is not valid according to the contents of the auth.conf file, the user will see the following error message in a popup message dialog and all applications will be inaccessible.

You are not authorized to use some of the applications.Access to those applications has been disabled.

To summarize, you have two basic choices for types of entries in the auth.conf file.

• Use the released defaults to allow anyone with any valid username to use the NB-Java client application and only root users to use the administrator applications and administrator capabilities in jbp.

• Specify entries for valid usernames.

On UNIX servers and clients other than Solaris or HP-UX, you need to create the /usr/openv/java/auth.conf file if you do not want to use the released defaults.

Note: The validated username is the account the user will be able to back up, archive or restore files from or to. The NB-Java client application relies on system file permissions for browsing directories/files to back up or restore.




8

Nonroot Usage of NB-Java Administrator Applications

Following are the steps for allowing nonroot users to administer NetBackup via NB-Java.

1. Create distinct file system group names to change file group ownership of some NetBackup commands for one or both of the following reasons.

• access to NB-Java adminstrator related applications, i.e., all but jbp

• administrator capabilities in jbp

If all nonroot users you wish to give these types of capabilities to will be getting both groups of capabilities, only one distinct file system group is required.

2. Execute /usr/openv/java/nonroot_admin.sh. You will be asked to provide the group names you created.

Note: This script should be rerun any time a patch is installed that replaces any file in /usr/openv/netbackup/bin/admincmd or files bpbackup, bplist or bprestore in /usr/openv/netbackup/bin.

3. Change the NB-Java authorization file, /usr/openv/java/auth.conf, for the capabilities desired for the affected users. Refer to “Authorizing Nonroot Users for Specific Administrator Applications” on page 73 and “Capabilities Authorization for jbp” on page 74 for details.

4. Ask all affected users to restart the NB-Java application.

For background information see the sections titled 'Allowing Nonroot Users to Administer NetBackup' and 'Allowing Nonroot Users to Administer Media Manager' in the NetBackup System Administrator’s Guide - UNIX and Media Manager System Administrator’s Guide - UNIX, respectively.

If logging on as a nonroot user and not properly authorized for the application selected, the user will see a warning message dialog as follows.

You are not authorized to use the selected application.Access to this application, and any others which you arenot authorized to use has been disabled.

If logging on as a nonroot user and not properly authorized for some of the applications, but authorized for the one selected, the user will see a warning message dialog as follows.



NetBackup-Java 73

8

You are not authorized to use some of the applications.Access to those applications has been disabled.

If logging on as a nonroot user and the steps above have not been completed, i.e., the permissions on executables in the respective directories aren’t changed, the user will see a warning message dialog containing one of a variety of error messages. Some are the following.

Could not get retention level information: /bin/sh:/usr/openv/netbackup/bin/admincmd/bpretlevel: cannot execute

A command execution error occurred. The application will not be fully functional.

Unable to retrieve complete data.

Unable to retrieve complete volume information.

Miscellaneous failure./bin/sh: /usr/openv/volmgr/bin/vmpool: cannot execute

Miscellaneous failure. Error: /bin/sh: /usr/openv/volmgr/bin/vmoprcmd: cannot execute

Cannot execute /usr/openv/netbackup/bin/admincmd/bpgetconfig -s status was 1

/bin/sh: /usr/openv/netbackup/bin/admincmd/bpsyncinfo: cannot execute

/usr/openv/netbackup/bin/admincmd/bpdbjobs: Execute permission denied.

Pathnames in some of those above could be different depending on the application - these are just some examples. Also, in most cases you will see no data appear in various lists or trees of the user interface in this case.

Authorizing Nonroot Users for Specific Administrator Applications

It is possible to authorize some users for a subset of the NB-Java applications. Of course, this is only possible along with allowing nonroot usage of the NB-Java administrator applications as noted above. Each application has a two or three character identifier for use in the auth.conf file.

AM - Activity MonitorBPM - Backup Policy ManagementJBP - Backup, Archive, and RestoreDM - Device MonitorMM - Media ManagementREP - ReportsSUM - Storage Unit Management




8

For example, to enable access to only Device Monitor and Activity Monitor for user joe, add the following entry to the auth.conf file.

joe ADMIN=DM+AM

Capabilities Authorization for jbp

Following is a list of all the capabilities identifiers for jbp for use in the auth.conf file.

ACTIONS Allowed to perform backup, archive or restore tasks (if authorized)

ENDUSER Only authorized for restore capabilities; from true image, archive or regular backups plus alternate client restores

BU Allowed to perform backup tasks

ARC Allowed to perform archive tasks (BU capability required for this)

RAWPART Allowed to perform raw partition restores

ALL Allowed for all of the above including restoring to a different client from the one you are logging into, i.e., server directed restores. This normally requires execution from the root account.

In addition, when authorized for ALL, the user is capable of previewing a list of media ids required for the files marked for restore via the ’Preview media required’ button at the bottom of the ’Restore Files’ tab.

Note: You must make the NetBackup configuration changes documented in the section titled ’Managing the Restore of Client Files’ in the NetBackup System Administrator’s Guide - UNIX to successfully perform alternate client restores.

So, for example, if you wanted user bill to only be able to restore files and not back up or archive any files, his entry would look like this:

bill ADMIN=JBP JBP=ENDUSER+ACTIONS



NetBackup-Java 75

8

Converting Previous auth.conf Files

A conversion script is available to convert pre-NB-Java version 3.2 auth.conf files to be usable in this version of NB-Java. The ’JBP=ALL’ part of each nonroot user’s entry in the pre version 3.1.1J2 auth.conf files must be converted. Two options exist to choose from.

• Provide all end user features; back up, archive and restore

• Provide just restore capabilities to end users

These result in JBP=ENDUSER+BU+ARC+ACTIONS and JBP=ENDUSER+ACTIONS, respectively. This script will remove the password field that existed in pre NB-Java version 3.2 auth.conf files. The script is /usr/openv/java/convert_auth_file.sh.

Configuration Options

Configuration Options for NB-Java Client Application - jbp

A configuration file allows the administrator to tailor certain aspects of the NB-Java client application for all users. The variables are organized in name=value pairs. All option settings in the 'global' jbp.conf file that resides in /usr/openv/java affect all users on the NetBackup client on which the NB-Java client software is installed. Users can override the values set in the 'global' jbp.conf file with values in their $HOME/jbp.conf file.




8

Any change to /usr/openv/java/jbp.conf or a user’s $HOME/jbp.conf will only become effective upon a subsequent invocation of the application.

The value for LIST_DEPTH may be a single number or two numbers separated by a colon as is the default. The zero in the default value (0:1) means that, upon startup, the list of files for restore is not automatically generated. The user must click on the ’Update File List’ button to get a listing of files. The one in the default value (0:1) is the list depth used. All subsequent updates to the list of files uses a list depth equal to the second number in the pair (1).

Providing a single value for LIST_DEPTH will cause the list of files to be generated upon startup (of depth equal to the value) and the value to be used whenever updating of the list occurs.

Table 14 Valid Options Used by jbp

Variable Default Description

ACCUMULATE 0 Accumulate restore selections across date ranges (Default: Clear restore selection when date range is changed)

ALTERNATE_PATH - Alternate path for restore (i.e., no default)

CLEAR_SELECTION 0 Clear the selection list after submitting a backup/restore (1 - Clear after restore, 2 - Clear after backup/archive, 3 - Clear after both; default is to not clear)

LIST_DEPTH 0:1 Directory depth when searching for files to restore

RESTORE_START_DIR START_DIR Default directory to browse for restore operations. Defaults to value of START_DIR.

START_DIR $HOME Default directory to browse for backup/archive operations.



NetBackup-Java 77

8

In the server or the client bp.conf, you, the NetBackup administrator, can limit the start date of the search for restores. This can improve performance when large numbers of backups are done. Please reference the NetBackup System Administrator’s Guide - UNIX for more information.

Also, ONLY in the global /usr/openv/netbackup/bp.conf file, a new option now exists (KEEP_LOGS_DAYS) with semantics almost identical to the now obsolete jbp.conf option KEEP_PROGRESS_FILES.

Alternate Client Restores with jbp

The NB-Java client application, jbp, provides two types of alternate client restore capabilities.

• Restore files from a different client to the client on which jbp is running.

Table 15 Start Date Variable


INITIAL_BROWSE_SEARCH_LIMIT - Limits the start date, overriding any value set by the user, to x days before the current day (Default: No Limit)

Table 16 Log Retention Variable


KEEP_LOGS_DAYS 3 Specifies the number of days to keep job and progress log files generated by the NetBackup-Java ’Backup, Archive and Restore’ (jbp) application. These files are written into /usr/openv/netbackup/logs/user_ops/_username_/jobs and /usr/openv/netbackup/logs/user_ops/_username_/logs directories. There will be a directory for each user that uses the NetBackup-Java applications. The default is three days.




8

This capability doesn’t use the ’Destination client’ field in jbp, i.e., it always does the restore to the machine on which the application is running. Be sure to understand that in ’remote administration’ execution mode, you will be performing the restore on the administrative master server. See “Remote Administration” on page 65.

• Server directed restores.

This capability allows you to restore data that was backed up from any client to any other client. It usually requires running jbp under the root account (see “Nonroot Usage of NB-Java Administrator Applications” on page 72 and “Capabilities Authorization for jbp” on page 74 for authorizing nonroot users for this capability) and can only be done when running jbp on a NetBackup master server machine.

Files or raw partitions can be restored to any client of the same type as the machine from which they were backed up - both the 'Source client' and 'Destination client' must be of the same type (refer to the 'Type of client' field in jbp).

Note: You must make the NetBackup configuration changes documented in the section titled 'Managing the Restore of Client Files' in the NetBackup System Administrator’s Guide -UNIX to successfully perform either type of alternate client restore.

Default NetBackup Host to Log Into

If you need to change the default NetBackup host name which appears in the login dialog when starting NB-Java administrator applications (i.e., command jnbSA), edit the following line in file /usr/openv/java/nbj.conf.

SERVER_HOST=eagle

For example, change host eagle to hawk.

SERVER_HOST=hawk

Similarly, for the end user Backup, Archive and Restore application (i.e., command, jbpSA), change the following option in this file.

CLIENT_HOST



NetBackup-Java 79

8

Changing Fonts and Font Sizes on UNIX Platforms

We have tried to choose a set of fonts which are commonly available on a large number of UNIX platforms. We have also chosen a font size for the ’Backup, Archive, and Restore’ application which has good resolution and allows the application to be rendered on an average size screen.

In some cases, the fonts we have chosen may not be available on your machine(s). In this case, you will need to edit the font.properties file. This file is found in /usr/openv/java/jre/lib. You will need to change the entries for the ’Dialog’ font. These are found after the ’Dialog font definition’ comment. To find the fonts available for your machine, execute /usr/bin/X11/xlsfonts. This will list the font styles and sizes available. You may have to try several fonts to find one you like.

As an example, the initial font.properties file (see the fragment below) uses the -b&h-lucida-medium font.

.

.

# Dialog font definition

#

dialog.plain.0=-b&h-lucida-medium-r-normal-sans-*-%d-75-*-p-*-iso8859-1

dialog.1=-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific

dialog.2=--symbol-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific

dialog.italic.0=-b&h-lucida-medium-i-normal-sans-*-%d-75-*-p-*-iso8859-1

dialog.bold.0=-b&h-lucida-bold-r-normal-sans-*-%d-75-*-p-*-iso8859-1

dialog.bolditalic.0=-b&h-lucida-bold-i-normal-sans-*-%d-75-*-p-*-iso8859-1

.

.

If you run jbp and don’t see any text, execute xlsfonts. You will discover that the -b&h-lucida-medium fonts is not available on you machine(s), but you do have the -adobe-courier-medium fonts. You could then change the font.properties file to use it as follows.




8

.

.

# Dialog font definition

#

dialog.plain.0=-adobe-courier-medium-r-normal--*-%d-75-*-m-*-iso8859-1

dialog.1=-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific

dialog.2=--symbol-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific

dialog.italic.0=-adobe-courier-medium-o-normal--*-%d-75-*-m-*-iso8859-1

dialog.bold.0=-adobe-courier-bold-r-normal--*-%d-75-*-m-*-iso8859-1

dialog.bolditalic.0=-adobe-courier-bold-o-normal--*-%d-75-*-m-*-iso8859-1

.

.

For information on fonts, see X Window System User’s Guide from O’Reilly and Associates,Inc.

You may also need to or want to change the font size used for the ’Backup, Archive, and Restore’ application (jbp). This setting may be changed by adding the line, ’FontSize=’, to the JBPSimple.properties and Launch.properties files found in /usr/openv/java. You should verify that the size you choose is available for font set in the font.properties file. If you change the font size, you may also need to change the WIDTH and HEIGHT values in JBPSimple.properties so the application is sized to fit the new font.

For example, relevant options in the original JBPSimple.properties file look like this:

WIDTH=760

HEIGHT=580

If you decide that you would like to use a larger font for jbp, for instance size 12 instead of the default size 10 you would add

FontSize=12



NetBackup-Java 81

8

to JBPSimple.properties (and to Launch.properties). This change also necessitates increasing the size of the window so you might set the WIDTH to 820 and the HEIGHT to 600. After making these changes, the relevant options look like this:

WIDTH=820

HEIGHT=600

FontSize=12

UsageTo access the NB-Java suite of applications, simply execute the following command

jnbSA

that resides in /usr/openv/netbackup/bin. You will be prompted to login to an NB-Java application server on a specific host. If logging in to it on the local host, i.e., the hostname displayed in the login dialog is the same as the machine name on which executing jnbSA or jbpSA command, your username and password are not required as authentication has been done by the operating system when you logged into it. Only when trying to login to a remote NB-Java application server are you required to provide a username and password.

For backup, archive or restore operations on your local machine execute the following command

jbpSA

that resides in /usr/openv/netbackup/bin. You will be prompted to login to NB-Java.

Be sure to set your DISPLAY environment variable if displaying to a machine other than the one starting the application up on or use the -d or -display option of the respective script to do so.




8

Operational Notes

General Items Applicable to All Applications• A Solaris Intel NetBackup client can not be used as a display console for

NB-Java applications. Only the jbp application is supported on this platform via the jbpSA command.

• NB-Java uses a reserved port for communication with its application server program, bpjava-msvc.

• Dialog modality in Java was changed in version 1.1.6 to use "full application modality" (see Sun’s Java bug report 4058370). The reason for the change was to provide consistent behavior across Java environments (the behavior had varied between CDE and other windowing environments). What this means for NB-Java is that if a modal dialog (one which blocks input to other windows) is open, input is blocked for all other NB-Java windows, not just the dialog's parent window. As an example: if you are using the Storage Unit Management application and have the "Change Storage Unit" dialog open, if you select the main NB-Java "launch" window and try to start another application it will not respond. You must finish entering your choices into the "Change Storage Unit" dialog (or cancel the operation) before you can interact with with another NB-Java application.

• Remote display to a machine of a different platform (e.g., Solaris) from the one where the application was started is not supported, e.g., executing jnbSA on an HP 11.0 machine and displaying back to a Solaris 2.6 machine via the setting of the DISPLAY environment variable.

• Only the CDE and Motif window managers are supported.

• Window managers configured for 'auto focus', i.e., to activate windows (put the focus on the window) by moving the mouse cursor over the window, are not supported.

• Administration of Windows NT NetBackup servers via NB-Java is only supported via remote operation, i.e., Global Data Manager or 'Change Server' functionality available in some of the administrator applications. Reference “System Requirements” on page 62 and “Remote Administration” on page 65 for more information.



NetBackup-Java 83

8

• If you have installed and configured the Global Data Manager (GDM) product the banner image at the top of the 'launch' window will always be the non-GDM version. However, all main application windows will contain the GDM banner image to indicate being logged into the NB-Java application server on a GDM machine.

• To better facilitate getting support information for problems you may experience with NB-Java the application startup script, jnbSA, writes a log file by default to /usr/openv/java/logs. There will be one log file for every instance of the application. Normally, these log files will not be large (< 2KB). However, periodic pruning of the files in this directory is recommended. See “Troubleshooting Guide” on page 98 for more information relevant to this.

• You can access online help for the NB-Java applications in a browser outside of the applications by opening one of the following document files.

file:/usr/openv/java/vrts/nbu/help/en/MainHelp.html - admin applications

file:/usr/openv/java/vrts/nbu/help/en/help.html - jbp

• Refer to the NetBackup Troubleshooting Guide - UNIX for more detail on errors that may occur in NB-Java.

• If not setup properly to display to a remote machine from where executing jnbSA, you will see one of two things happen: either nothing (it is probably displaying on the machine where executing), or failing with no error message (i.e., the OS command prompt received). Prior to starting jnbSA, be sure to execute the xhost command on the machine you intend to see the user interface and set the DISPLAY environment variable on the machine executing jnbSA prior to starting jnbSA. Reference the man page for the xhost command for additional capabilities.

• On Solaris the X11 shared library (libX11.so.4) is required for NB-Java. It resides in /usr/openwin/lib if the OpenWindows package is installed. The application startup scripts, jnbSA and jbpSA, check for the existence of /usr/openwin/lib (as the default location for this library) prior to setting the LD_LIBRARY_PATH environment variable. If it doesn't exist the following error message will appear.

Directory /usr/openwin/lib doesn’t exist. It is the defaultlocation for libX11.so.4 which is required by NB-Java.Please create the /usr/openwin/lib directory and a symbolic link for it or modify this script to properly set the LD_LIBRARY_PATH environment variable.




8

• Long waits for application response and/or incomplete data may be returned in the applications as a result of invalid NetBackup configurations or inadequate file system space in /usr/openv/netbackup/logs.

Activity Monitor Application• The initial startup time of the Activity Monitor application in non-GDM

mode is dependent on the number of jobs available for display for the server.

• To allow remote job monitoring in the Activity Monitor, the NetBackup master server must include the monitoring host in the server list.

• If using auto refresh in the Activity Monitor, the result of kill and delete job operations may not become evident until a future refresh cycle in the application completes.

Backup Policy Management Application• Sort operations are intentionally disabled for the "Files" list. Ordering has

become very important due to the "file directives" that many of the new NetBackup 3.2 features are using.

Configure - NetBackup System Configuration Application• Multiple selections of the Impact Report button will result in multiple

executions.

Media and Device Management Application• It is recommended that you move only one volume or volume group at a

time.

• Explicit updating of barcodes is not supported in this release. Updating of barcodes is done automatically via the Robot Inventory dialog (by selecting the "Update Volume Configuration" operation). Another method is to move the volume to non-robotic, then back into the robot when it is available. Alternatively, you may use the xvmadm or vmadm applications.



NetBackup-Java 85

8

Reports Application• The Media Contents report in the Reports application requires a specific

media id and will not work with value "All".

Backup, Archive, and Restore Application• On the "Task Progress" tab, the "Status" column of the "Tasks Performed" list

may be empty. When option DISALLOW_SERVER_FILE_WRITES is set in the bp.conf file this status column will be blank. You can check the status of the task by selecting it to display the progress log file in the bottom area of the Task Progress section.

• Modify dates in the Restore section could be December 31, 1969 for some directories. When restoring files, you may see a fabricated modify date of December 31, 1969 for directories that were not fully backed up. These entries appear in the directory listing for ease of navigation to directories and files that have been backed up.

NB-Java Known Problems and Limitations

General Items Applicable to All Applications• On occasion, all applications will hang when trying to display online help

from within one of them. The only recourse is to terminate the application and restart it. See “Known Problems with Display of Online Help” on page 93 for more information.

• You can sort a table based on the data in a single column by clicking on the column header. The sort order will alternate between ascending and descending order with each click. A known limitation in this release of NB-Java is that the sort is based on a text comparison, and therefore sorts of columns with numeric values are not sorted in correct numeric order.

• On rare occasions we have seen repaint problems. For example, you select a menu title, but the menu fails to paint unless you move another window in front of the NB-Java window, then make the NB-Java window visible again. Or you select a row in the table, but it fails to be highlighted until you force a repaint by either minimizing/maximizing the NB-Java window, or




8

covering/uncovering the NB-Java window. Once it gets into this repaint predicament, nothing will clear up the problem except for exiting the program. You have to stop NB-Java, then restart it.

• Quite frequently buttons, checkboxes, and List widgets (list of items with scroll bar) fail to respond to the first mouse-release/click. The result is that the widget behaves as if a mouse-drag operation is occurring. The result in a button is that the button does not respond to the click, just changes in appearance. The result in a checkbox is that the selection state fails to toggle, instead the checkbox changes in appearance -- gets a more pronounced beveled border. The result in a List is that it doesn't respond to the selection. Instead, if you drag the mouse the list begins to the scroll and the selection changes.

• In some cases, you can close an application window from the window's menu even while child dialogs are visible.

• If a non-modal dialog is visible and behind the parent frame and subsequently a modal dialog is made visible, Java moves the original non-modal dialog in front of the parent frame, but behind the newest dialog. When the modal dialog is hidden, the non-modal dialog is moved back to its original position behind the parent frame.

• If you enter text into a dialog's text field while either NB-Java is busy performing other operations, or while your system is busy, the characters you enter may be transposed in order when displayed in the text field. For example, if you have started the Backup Policy Management "Install Client Software" operation and it is currently busy installing software, if you then try to perform other operations in Backup Policy Management which require entering text, you will find that the characters you enter into the text field may be displayed in the field out of order. You may also notice that response time is slow.

Backup Policy Management Application• Sort order in the table is not maintained after deleting one or more rows.

After a 'delete' operation the table will revert to its original, unsorted order.

• Sort order in table is not maintained after changing tree nodes: If you click on a table header to sort the list, then select another tree node, the table reverts to displaying data in unsorted order.



NetBackup-Java 87

8

• Remote client software install limitations:

• It does not support software install for non-UNIX clients and a small subset of UNIX clients are also not supported.

• It is enabled only when a master server node is selected, and then only if the master server is the server the user logged into when starting NB-Java.

• This feature uses the same mechanisms for installing remote software as described in the NetBackup System Administrator’s Guide - UNIX for installing software on trusting UNIX clients.

Configure - NetBackup Catalog Backup Application• No checking is done to determine if the format of the pathname is valid.

Embedded spaces in pathnames will cause problems and Windows NT style pathnames are not supported.

Configure - NetBackup System Configuration Application• No checking is done to determine if the format of the email address is valid.

• Blank text fields in the Global Attributes tab are allowed and treated as no change with the exception of the email address field.

Device Monitor Application• If the bprd daemon is down, the Global Data Manager permits connections

to device hosts with configurations that disallow connections from the Master of Masters host.

• If a device host does not have a valid configured device, then the Media Manager device daemon (ltid) will start and shutdown after a brief initialization phase. Therefore, attempts to start the daemon via the "Start/Stop Media Manager Device Daemon" dialog will report that the daemon was started successfully, but a short time later the application will display the error message that the daemon is inactive. The appropriate response is to configure a device and then start the Media Manager device daemon (ltid).




8

Media and Device Management Application• When connecting to (or refreshing) a media manager, the cursor may

remain in the hourglass state for several seconds after the "Loading data from ..." popup dialog has disappeared. If the media manager has a significant number of volumes or device hosts, the delay is due to data being added to unseen portions of the tree and table panes.

• If the bprd daemon is down, the Global Data Manager permits connections to media managers with configurations that disallow connections from the Master of Masters host.

• Unexpected results can occur when entering non-numeric values into numeric-only textfield controls. It is recommended that you use the arrow buttons to the right of the control to increment or decrement the numeric value. (Numeric textfield controls appear on the following dialogs in Media and Device Management: "Add New Volume", "Move Volumes", "Change Volumes", "Add New Robot", "Change Robot", "Add New Drive", "Change Drive", "ACS Drive ID", "Add New Barcode Rule" and "Change Barcode Rule".)

• Administration of optical devices and optical media is not supported in this release. While some of the pick lists contain optical entries (e.g., drive type, media type, and robot picklists), you could receive an error message when trying to make use of them. Use xvmadm to add new optical volumes, and xdevadm or tpconfig for adding new optical drives and robots.

• When changing or viewing the attributes for an NT-controlled robot via the "Change Robot" dialog, the port, lun, target and bus fields will show a value of zero if the robot's device host (the host on which the robot was defined) is not running NetBackup version 3.2. Use tpconfig to retrieve the correct SCSI values.

• If a device host does not have a valid configured device, then the Media Manager device daemon (ltid) will start and shutdown after a brief initialization phase. Therefore, attempts to start the daemon via the "Start/Stop Media Manager Device Daemon" dialog will report that the daemon was started successfully, but a short time later the application will display the error message that the daemon is inactive. The appropriate response is to configure a device and then start the Media Manager device daemon (ltid).



NetBackup-Java 89

8

Reports Application• Trying to execute reports in more than one copy of the Reports application

can cause a hang of all the NB-Java applications that have been initiated from the same launch screen. This occurs most often when executing reports in the different instances of the application for the 'All Recognized Master Servers' node, i.e., when configured as a Global Data Manager.

• The 'View Media Contents' report is not functional if you have the 'All Recognized Master Servers' node selected when executing on a Global Data Manager server.

• After specifying non-default report criteria via the Reports Settings dialog, use the dialog's Run button to start the report instead of the Run button on the toolbar. The criteria associated with the toolbar button is not kept in sync with that in the dialog.

• When running the Media Contents report, explicitly specify a host in the Server picklist field on the Report Settings dialog. If the Server parameter is set to All, then the report is unable to find the specified media ID in the Media Manager volume database.

• The Media Contents report requires the mount of media and it is likely to take a long time for any data to return to the application. In this context the interrupt button on the load in progress dialog window is ineffective.

Storage Unit Management Application• The "Maximum multiplexing per drive" number spinner control appears in

the "Add Storage Unit" and "Change Storage Unit" dialogs for Media Management storage units. You must use it to set the selected multiplexing value because editing of its associated input field is disabled.

Backup, Archive, and Restore Application• If the files that are selected for restore all begin with some number of the

same characters, e.g., s, s1, s2, s3, then the Source directory in the Restored Marked files dialog will end with the string of common characters. The restore attempt will fail. The only recourse is to restore the files individually or the entire directory by selecting the directory node of the tree or subsets of the files that don't create the problem.




8

• Depending on the task submitted, you may not see the type of task (Backup, Restore, Archive) listed in this column on the display in the Progress tab.

• In the Backup Files and Restore Files tabs, all marked items are lost when you change the root directory via a change to the Browse directory text entry field followed by a carriage return or a click of the Update Files List button. Also in the Restore section, marked items may get cleared in the following two scenarios:

a. When moving up the directory hierarchy via the up arrow in the upper left corner of either the Directory or File list boxes.

b. Trying to refresh the data for the current root directory, i.e., not changing the root directory, but entering a carriage return in the Browse directory text entry field or clicking the Update Files List button.

This last anomaly is not consistent - seeing it is dependent on some sequence of marking files and/or directories prior to attempting either of the above.

• Under some circumstances when unmarking items in either the Backup Files or Restore files tabs, the cursor will not change to a 'wait' cursor. This most often occurs when unmarking an item from a long list of marked items, i.e., as seen in the preview list.

• Some anomolies exist in the Restore Files section when marking directories to restore. These occur when multiple copies of a directory are being displayed, i.e., all backups between two dates. Intermixing the marking and unmarking of directories between the directory list on the left side and the files list on the right side may cause some inconsistent visual behaviour in the files list box on the right side. The restore operation will occur correctly. You can avoid this by always marking files and directories in the files list box.

NB-Java Windows Display Console Known ProblemsFollowing are known problems in NB-Java specific to running the applications on a Windows NT, 98, or 95 system, i.e. using the ‘NetBackup - Java Display Console for MS Windows’ product.

1. On Windows NT, the background color is not consistent in all the dialog windows of NB-Java. This a known Java problem (4102565).



NetBackup-Java 91

8

2. On the Windows platforms, you may see transparent backgrounds in some of the NB-Java application dialog windows.

3. On the Windows platforms, on occasion we have seen failures right after initialization. When this occurs, a Dr. Watson window appears with a message indicating that jrew.exe had a divide-by-zero exception followed by a program address (various addresses have occurred). This is a timing problem and Java bug 4223311 corresponds to our analysis of the problem.

4. On Windows NT, sometimes secondary dialog windows may get placed off screen. This most often occurs if the main application window is positioned close to the top of the screen. In this case the dialog’s title bar may be off screen and you won’t be able to reposition the dialog window.

5. On Windows NT, sometimes after NB-Java has started, all you see is a blank gray window with a File menu. If you drag a corner and resize the window, the application’s text and image will appear.

Java Problems Seen in NB-Java1. Some UI anomalies seen in this version of the Java Runtime Environment:

• Buttons don't always respond to the first mouse click. Instead they change in appearance to indicate 'mouse-over' action. It may take several clicks to respond depending on system activity.

• List components sometimes continue to scroll as if a mouse-drag operation is in progress, even though the mouse button has been released. Symptoms: after selecting an item in the list and releasing the mouse button, if you move the mouse below or above the list or to either side, the list will scroll in the direction the mouse is being moved, and the list selection will change.

• Checkboxes occasionally do not toggle their state properly when the mouse is clicked over the checkbox. Instead, the checkbox changes in appearance to indicate 'mouse-drag' operation. It may take several clicks to respond depending on system activity.

2. Closing an application's main window via a window manager's title bar menu close selection while the application has a dialog visible will make a subsequent invocation of the application from the same 'launch' screen for the most part unusable. This is a bug we have documented to Sun. We have worked around most cases in which this can occur.




8

3. We have seen a number of hangs caused by race conditions when opening/closing modal dialogs. Refer to Sun bug reports 4122683 and 4161680 as examples. These hangs occur when one modal dialog is opened very soon after another has been closed. In NB-Java the risk for encountering this problem is much higher when switching from one NB-Java ’application’ to another, especially if the switch occurs at about the time an NB-Java ’application’ is asynchronously popping up a warning message, for example when it displays a "Loading data..." message. For this reason we recommend you do not switch from one NB-Java application to another when the first application has an open dialog.

4. When the wait cursor is set for a window, the window’s text fields still have the normal text cursor (Sun bug report 4040417).

5. We have seen a number of paint/repaint problems that appear to be caused by the Java JFC Swing classes. These problems are more likely to occur when using an X emulator to run the Java application remotely. One often seen symptom is:

• After a dialog is dismissed, a small portion of the window it was covering may be corrupted. If this happens, minimizing/maximizing the window will force a total repaint of the window.

6. The application may "hang". See Sun bug reports 4089377 and 4041699. The first symptom that the application is "hung" is that you will notice when you change from window to window, the portion of a window that was previously covered by another window will remain unpainted, and the application will not respond to user input.

The most frequently occurring "hang" we have seen is similar to Sun bug report 4089377. This problem can happen when rapidly selecting tree and list items, or performing operations that cause the display of multiple dialogs in quick succession.

Sun bug report 4041699 describes hangs caused by internal class synchronization that we have seen.

Note that there may be some short periods of time where the NetBackup applications appear to be "hung" momentarily while they are accessing the NB-Java server. But if a "hang" persists for a considerable period of time, suspect a true application hang/deadlock.



NetBackup-Java 93

8

7. We have seen a number of SIGSEGV 11 segmentation violations followed by abort of the Java virtual machine (VM). These problems have been reported to Sun (no bug report numbers available). There are references to various SIGSEGV 11 segmentation violations at the Sun bug tracking web site. For an example, see Sun bug report 4097528. (Note that not all SIGSEGV problems stem from the same cause).

When these types of errors occur, the application will fail. The following error message will appear in the xterm window where you started the application.

Abort - core dumped

One particularly noteworthy is a scenario where NB-Java would not even initiate due to insufficient memory - failing with ’Abort - core dumped’ message. See “Insufficient Memory” on page 99.

To get more detail consult “Troubleshooting Guide” on page 98 for instructions.

8. We have seen a few Bus errors followed by the abort of the Java VM (problem reported to Sun, no bug report number available):

When these types of errors occur, the application will fail. The following error message will appear in the xterm window where you started the application.

Killed

To get more detail consult “Troubleshooting Guide” on page 98 for instructions.

Known Problems with Display of Online HelpFollowing is a list of known problems in the HotJava HTML Component of Java that may adversely affect the display of online help. If this becomes too frequent you could use a Web browser to view NB-Java online help. You can view online help outside of the applications by opening either of the following locations in a Web browser for NB-Java admin applications and jbp, respectively.

file:/usr/openv/java/vrts/nbu/help/en/MainHelp.html - NB-Java adminfile:/usr/openv/java/vrts/nbu/help/en/help.html - jbp




8

Alternatively, you can make a configuration change that forces the NB-Java applications to use a Web browser for viewing online help. Refer to the documentation for the browser_path option in the following two files.

/usr/openv/java/JBPSimple.properties - used by jbp only, i.e., jbpSA command/usr/openv/java/Launch.properties - used by the admin apps, i.e., jnbSA command

1. Sometimes the Java runtime environment will hang when a help file is displayed in the help browser. The only solution is to restart NB-Java.

2. Forward and backward navigation using the toolbar buttons doesn’t always work properly due to problems in the HotJava HTML Component. Incorrect navigation occurs when the displayed URL includes a fragment identifier after the # sign. For example, suppose you select hot links in the help Table of Contents to go to pages with URLs similar to the following:

deviceBody.fm2.html#10345



When you select the hot links, the help browser will navigate first to the head of deviceBody.fm2.html, then to the labeled fragment, #10345 for example. But when you try to navigate backwards using the back button, it goes to the head of the page (deviceBody.fm2.html in this example) but doesn’t scroll to the labeled fragment.

In our experience, navigation works using the hot links, but navigation using the forward and backward buttons is problematic when the URL points to a fragment within the page.

3. The "home" button doesn’t always work. The help browser calls the HotJava HTML Component’s setDocumentURL() method when the button is pressed, but sometimes the HTML component does not display the requested URL.

4. The help browser has a status bar at the bottom of the window. The only thing being displayed in the status bar right now is the URL as a page is selected. The help browser was designed to listen for change in status and error messages from the HotJava HTML Component, but unfortunately neither of those properties is ever reported by the HTML component.

5. Placing the mouse pointer over a hot link does not result in displaying the link’s URL as one might expect in a browser. The help browser listens for the HotJava HTML Component’s indicatedElement property, which is



NetBackup-Java 95

8

supposed to change when the mouse is over a hyper-text link. Unfortunately the property change is fired erratically and the method for accessing the property almost always returns null.

6. The HTML document’s title is displayed in the title bar of the help browser only the first time a help browser window is opened. This is because the getDocumentTitle() method of the HotJava HTML Component works only for the first instance of the HTML component. When the component is created multiple times for multiple help browser windows, calls to getDocumentTitle() from any instance of the HTML component other than the first instance return null.

Errors When NetBackup Daemons Are Not RunningDepending on whether running as a Global Data Manager or not, which daemons are not running on the relevant machine(s), and which application you startup at this time, following are the possible error messages you will see in an attention dialog.

• Could not get retention level information: Unable to get retention levels definitions. error= 25(cannot connect on socket)

• Unable to connect to host (name), it failed to respond.

• The Media Manager device daemon (ltid) is not active on host (name).

• Cannot connect on socket

• Cannot connect to vmd (70)

• Connection requested by invalid server.

• Error accessing server (name) - cannot connect on socket.

If you acknowledge these initial messages and try to proceed to use the application, a warning message dialog will appear containing one of a variety of error messages. Also, these types of errors can appear if the daemons are stopped while the NB-Java applications are running. Examples include:

• Error accessing server (name) - cannot connect on socket.

• Unable to connect to host (name), it failed to respond.

• The Media Manager device daemon (ltid) is not active on host (name).




8

• A command execution error occurred. The application will not be fully functional.

• An error occurred while reading configuration information. Select 'Refresh' to reload class data.

• Unable to retrieve complete data.

• Connection requested by invalid server.

• Unable to load information about NetBackup storage units.

• Unable to load information about NetBackup volume pools.

• An error occurred while changing class, status:25 cannot connect on socket

• Could not get retention level information: Unable to get retention levels definition. error=25 (cannot connect on socket)

• Could not get Class_att_defs information: Unable to get the attributes table

• Warning - netbackup database backup is currently disabled

• Cannot connect on socket

• Unable to retrieve complete information for host(s):

• JSAT21: insert failed - cannot connect to vmd (70)

• Cannot retrieve data from Media Manager server: cannot connect to vmd (70).

• Cannot connect to vmd (70)

In many cases with respect to the Device Monitor and Media and Device Management applications the last part of the error message will be 'cannot connect to vmd (70)'. For the other NB-Java applications, a commonly occurring message is 'cannot connect on socket'. Also, in some of the applications various data just doesn't appear, e.g., file and directory listings in the restore tab of jbp.

Performance Improvement HintsPerformance of the NB-Java applications is greatly dependent on the environment in which they are running. Following is a list of considerations relative to this.



NetBackup-Java 97

8

• Run NB-Java on a machine that has at least 128MB of real memory. We have found circumstances where the application will not even initiate due to insufficient memory - failing with 'Abort - core dumped' message. See “Insufficient Memory” on page 99.

• Run NB-Java on a fairly idle machine. For example, we've seen dramatic differences in reponse time when a copy of Netscape Navigator is running on the machine. Of course, the same thing can be said about multiple instances of NB-Java on the same machine.

• Since startup of the Java virtual machine and some of the applications may take a bit of time, leaving NB-Java running (iconified) rather than exiting/restarting it may be beneficial.

• Increasing the -ms argument to the Java runtime environment (jre) command in the jbpSA or jnbSA scripts may be helpful. This argument specifies how much memory is allocated for the heap when the Java interpreter starts up. The value used in these scripts is 4m - the 'm' suffix refers to megabytes.

• Increasing the -mx argument to the Java runtime environment (jre) commmand in the jbpSA or jnbSA scripts may be helpful. This argument specifies the maximum heap size the runtime environment will use for dynamically allocated objects and arrays. This can be useful if the amount of data is large, e.g., number of jobs in Activity Monitor. See “Insufficient Memory” on page 99.

• Increasing the amount of swap space available to the system on which you are running the applications can increase performance, especially if there is a fair amount of other activity on the machine. Also, doing so can alleviate hangs or other problems related to insufficient memory for the applications. See “Insufficient Memory” on page 99.

• If sufficient machine resources (see previous items) on the administrative server can not be made available, use another NB-Java enabled machine as a display console as highlighted in the second scenario of the “Remote Administration” section. See “Another NB-Java Enabled NetBackup Client or Server as Console” on page 67.




8

Troubleshooting GuideIf NB-Java fails to initialize or a failure is easily reproducible we certainly would like to know about it and get some additional information about the failure from you.

We have created some ’facilities’ to semi-automate the gathering of support data for problems.

• The NB-Java administration application startup script, jnbSA, logs data to a log file in /usr/openv/java/logs. Upon startup, the script will tell you which file in this directory it is logging to. Normally, this file will not become very large - usually less than 2KB. However, if you change the debugLevel option in the Launch.properties file, you will see more data written to the log file. Do not change this option before consulting VERITAS Customer Support.

• Script /usr/openv/java/get_trace can be used to get a Java virtual machine stack trace for us to analyze. This stack trace will be written to the log file associated with the instance of execution (see previous bullet).

• Script /usr/openv/netbackup/bin/goodies/support creates a file containing data necessary for us to debug any problems you may encounter. Please consult the usage information of the script via 'support -h' for more details.

Please follow these steps to get us debug data to analyze:

1. If the application is not responding for a long period of time it may be hung. Some operations you may perform in some of the applications can take some time to complete, especially those in the Activity Monitor and Reports applications. So, please wait for several minutes.

If no response within several minutes, execute /usr/openv/java/get_trace under the account in which you started the application. This will cause a stack trace to be written to the log file.

For example, if you started jnbSA from the 'root' account, you must start /usr/openv/java/get_trace as 'root' also. If you don't, the command will execute without error, but will fail to add the stack trace to the debug log. This is because no account other than 'root' will have permission to execute the command that dumps the stack trace.



NetBackup-Java 99

8

2. Execute /usr/openv/netbackup/bin/goodies/support to get data about your configuration. This probably only needs to be executed once after the installation completes. However, if the NB-Java or NetBackup configuration changes the data written by this script will be obsolete.

3. Provide the support script output and log file to VERITAS support.

We appreciate your help.

Insufficient Memory

If you see either of the following errors indicating insufficient memory in the log file or an attention dialog with an ’Out of memory error exception occurred.’ message, you could try increasing the value of the -mx argument to the jre command in these scripts. They reside in /usr/openv/netbackup/bin. The value used in these scripts is 32m (32 megabytes). However, its likely that running on a machine with more memory available or less activity or increasing the amount of swap space will provide better results.

Exception (execProgram):java.io.IOException: Not enough space

Usually this error will result in a message dialog containing the following error - "Can not execute program." Upon receiving this error, it is likely that the application UI contains incomplete data. However, it is possible to continue and retry the last operation.

java.lang.OutOfMemoryError

Upon receiving this error, all applications may be hung and you will have to restart via the jnbSA command.

Note that insufficient memory for NB-Java applications can also result in a SIGSEGV 11 segmentation violation in the output file (i.e., ’Abort - core dumped’ in the xterm window you started the application). We have seen this occur on a machine with 64MB of memory and a couple of Netscape Navigator processes running. Shutting down the copies of Navigator allowed NB-Java to initiate/run.




8



101

Related Documents A

This appendix has two sections. The first section lists by category all the technical manuals that pertain to NetBackup and provides a summary of each. The second section explains which manual to use for each task (installation, configuration, and so on).

Manual Summaries

Release Notes

NetBackup Release Notes - UNIX

Provides important information about UNIX NetBackup server software, such as the platforms and operating systems that are supported and operating notes that may not be in the manuals or the online help.

Also provides information about the NB-Java graphical user interface, including system requirements, authorization, configuration, usage, and troubleshooting.

NetBackup Release Notes - Windows NT Server

Provides important information about Windows NT NetBackup server software, such as the platforms and operating systems that are supported and operating notes that may not be in the manuals or the online help.




A

Installation Guides

NetBackup Installation Guide - PC Clients

Gives you the information you need to quickly get NetBackup PC client software installed and running. The PC clients are Windows NT, Windows 95, Windows 98, Macintosh, OS/2 Warp, and Novell NetWare. This is the first document that you should read after opening the NetBackup PC client package.

NetBackup Installation Guide - UNIX

Gives you the information you need to quickly get UNIX NetBackup software installed and running. This is the first document that you should read after opening the NetBackup UNIX Server package.

NetBackup Installation Guide - Windows NT Server

Gives you the information you need to quickly get Windows NT NetBackup server software installed and running. This is the first document that you should read after opening the NetBackup Windows NT Server package.

System Administrator’s Guides - Basic Product

NetBackup System Administrator’s Guide - UNIX

Explains how to configure and manage NetBackup on a UNIX system.

NetBackup System Administrator’s Guide - Windows NT Server

Explains how to configure and manage NetBackup on a Windows NT server system.

NetBackup System Administrator’s Guide - Windows NT Server - UNIX Supplement

Contains information about configuring and using UNIX NetBackup clients and slave servers in a configuration that is controlled by a Windows NT NetBackup master server.



Related Documents 103

A

Media Manager System Administrator’s Guide - UNIX

Explains how to configure and manage the storage devices and media on UNIX NetBackup servers. Media Manager is part of NetBackup.

Media Manager System Administrator’s Guide - Windows NT Server

Explains how to configure and manage the storage devices and media on Windows NT NetBackup servers. Media Manager is part of NetBackup.

Note: For general information about NB-Java, refer to the NetBackup Release Notes - UNIX.

System Administrator’s Guides - Product Extensions

NetBackup for AFS System Administrator’s Guide

Explains how to install, configure, and use NetBackup for AFS.

NetBackup for DB2 System Administrator’s Guide

Explains how to install, configure, and use NetBackup for DB2.

For this product, you may also need the following manuals from IBM:

IBM DB2 Universal Database Extended Enterprise Edition for AIXQuick Beginnings for DB2 Extended Enterprise Edition

API Ref IBM DB2 Universal Database API ReferenceVersion 5

Guide IBM DB2 Universal Database Administration GuideVersion 5

Cmd Ref IBM DB2 Universal Database Command Reference

NetBackup for EMC System Administrator’s Guide

Explains how to install, configure, and use NetBackup for EMC.




A

NetBackup Encryption System Administrator’s Guide

Explains how to install, configure, and use NetBackup Encryption to provide file-level encryption of backups and archives.

NetBackup FlashBackup System Administrator’s Guide

Explains how to install, configure, and use NetBackup FlashBackup. The FlashBackup product combines the increased performance of raw-partition backups with the ability to do individual file restores.

NetBackup for Informix System Administrator’s Guide

Explains how to install, configure, and use NetBackup for Informix to back up and restore Informix databases that are on a UNIX NetBackup client.

For this product, you may also need the following manual from Informix Software Incorporated:

Informix-Online Dynamic Server Backup and Restore Guide

NetBackup for Lotus Notes System Administrator’s Guide

Explains how to install, configure, and use NetBackup for Lotus Notes to back up and restore Lotus Notes databases and transaction logs.

NetBackup for Microsoft Exchange Server System Administrator’s Guide

Explains how to configure and use NetBackup for Microsoft Exchange Server to perform online backups and restores of Microsoft Exchange Server.

You may also need the following resources from Microsoft Corporation:

Microsoft Exchange Server whitepapers and FAQs (go to http://www.microsoft.com/exchange and search for "Disaster Recovery")

Microsoft Exchange Administrator's Guide

Microsoft Exchange Concepts and Planning Guide

Microsoft TechNet




A

Microsoft BackOffice Resource Kit

http://www.msexchange.org

NetBackup for Microsoft SQL Server System Administrator’s Guide

Explains how to install, configure, and use NetBackup for Microsoft SQL Server to back up and restore Microsoft SQL Server databases and transaction logs.

For this product, you may also need the following manual from Microsoft Corporation:

Administrator’s Companion - Microsoft SQL Server

NetBackup for NDMP System Administrator’s Guide

Explains how to install, configure, and use NetBackup for NDMP to control backups on an NDMP host.

NetBackup for Oracle on UNIX System Administrator’s Guide

Explains how to install, configure, and use NetBackup for Oracle to back up and restore Oracle databases that are on a UNIX NetBackup client.

For this product, you may also need the following manuals from Oracle Corporation:

Oracle7 Enterprise Backup Utility Installation and Configuration Guide

Oracle7 Enterprise Backup Utility Administrator’s Guide

Oracle7 Server Administrator’s Guide

Oracle8 Server Backup and Recovery Guide


NetBackup for Oracle on Windows NT System Administrator’s Guide

Explains how to install, configure, and use NetBackup for Microsoft Oracle to back up and restore Oracle databases that are on a Windows NT NetBackup Client.




A


Oracle7 Enterprise Backup Utility Installation and Configuration Guide

Oracle7 Enterprise Backup Utility Administrator’s Guide


Oracle8 Server Backup and Recovery Guide


NetBackup / Plus Module for TME 10 System Administrator’s Guide

Explains how to install, configure, and use NetBackup / Plus Module for TME 10 to manage NetBackup in the Tivoli Management Environment TM (TME) rather than through the standard NetBackup administrator interfaces.

NetBackup for SAP on UNIX System Administrator’s Guide

Explains how to install, configure, and use NetBackup for SAP on UNIX.


Oracle Enterprise Backup Utility Installation and Configuration Guide

BC SAP Database Administration : Oracle

You may also need the following manual from SAP AG:

BC-BRI BACKINT Interface R/3 System, Release 3.0

NetBackup for SAP on Windows NT System Administrator’s Guide

Explains how to install, configure, and use NetBackup for SAP on Windows NT.


Oracle Enterprise Backup Utility Installation and Configuration Guide

BC SAP Database Administration : Oracle




A

You may also need the following manual from SAP AG:

BC-BRI BACKINT Interface R/3 System, Release 3.0

NetBackup for SQL-BackTrack System Administrator’s Guide

Explains how to install, configure, and use NetBackup for SQL-BackTrack to back up and restore Oracle and Sybase databases that are on a UNIX NetBackup client.

NetBackup for SYBASE System Administrator’s Guide

Explains how to install, configure, and use NetBackup for SYBASE to back up and restore Sybase databases that are on a UNIX NetBackup client.

For this product, you may also need the following manuals from SYBASE Incorporated:

SYBASE SQL Server Utility Programs for Unix

SYBASE SQL Server Administration Guide

User’s Guides• NetBackup User’s Guide - Macintosh

Explains how to use NetBackup on a Macintosh client to perform backups, archives, and restores. This guide also contains some configuration instructions for the NetBackup client software.

• NetBackup User’s Guide - Microsoft Windows

Explains how to use NetBackup on a Windows NT, Windows 95, or Windows 98 client to perform backups, archives, and restores. This guide also contains some configuration instructions for the NetBackup client software.

• NetBackup User’s Guide NonTarget Version - Novell NetWare

Explains how to use NetBackup nontarget software on a Novell NetWare server to perform backups and restores. The nontarget version of NetBackup has a Microsoft Windows interface. This guide also contains some configuration instructions for the NetBackup client software.




A

• NetBackup User’s Guide Target Version - Novell NetWare

Explains how to use NetBackup target software on a Novell NetWare server to perform backups and restores. The target version of NetBackup has a menu driven interface that runs under DOS. This guide also contains some configuration instructions for the NetBackup client software.

• NetBackup User’s Guide - OS/2 Warp

Explains how to use NetBackup on an IBM OS/2 Warp client to perform backups and restores. This guide also contains some configuration instructions for the NetBackup client software.

• NetBackup User’s Guide - UNIX

Explains how to use NetBackup on a UNIX client to perform backups, archives, and restores.

Note: For user’s information about NB-Java, refer to the NetBackup Release Notes - UNIX.

Device Configuration Guide - Media Manager• Media Manager Device Configuration Guide

Explains how to add device drivers and perform other system level configuration for Media Manager storage devices on UNIX hosts.

Troubleshooting Guide• NetBackup Troubleshooting Guide - UNIX

Provides troubleshooting information for UNIX based NetBackup products.

• NetBackup Troubleshooting Guide - Windows NT Server

Provides troubleshooting information for Windows NT based NetBackup products.

Note: For troubleshooting information about NB-Java, refer to the NetBackup Release Notes - UNIX.




A

Documents To Use For Each Major Task

Installation

Refer to the following documents when installing NetBackup.

Windows NT NetBackup Servers

• NetBackup Installation Guide - Windows NT Server• NetBackup Release Notes - Windows NT Server

UNIX NetBackup Servers and Clients

• NetBackup Installation Guide - UNIX• NetBackup Release Notes - UNIX

If you have NetBackup add-on products, also see the following:

For PC Clients:

NetBackup Installation Guide - PC Clients

For Netbackup Database Extension products:

• NetBackup for DB2 System Administrator’s Guide• NetBackup for Informix System Administrator’s Guide• NetBackup for Lotus Notes System Administrator’s Guide• NetBackup for Microsoft Exchange Server System Administrator’s Guide• NetBackup for Microsoft SQL Server System Administrator’s Guide• NetBackup for Oracle on UNIX System Administrator’s Guide• NetBackup for Oracle on Windows NT System Administrator’s Guide• NetBackup for SAP on UNIX System Administrator’s Guide• NetBackup for SAP on Windows NT System Administrator’s Guide• NetBackup for SQL-BackTrack System Administrator’s Guide• NetBackup for SYBASE System Administrator’s Guide

NetBackup for AFS:

• NetBackup for AFS System Administrator’s Guide

NetBackup for EMC:

• NetBackup for EMC System Administrator’s Guide




A

Configuration and Administration

Refer to the following documents for information on configuring and administering NetBackup.

For NetBackup Encryption:

• NetBackup Encryption System Administrator’s Guide

NetBackup FlashBackup:

• NetBackup FlashBackup System Administrator’s Guide

For NetBackup for NDMP:

• NetBackup for NDMP System Administrator’s Guide

For NetBackup / Plus Module for TME 10:

• NetBackup / Plus Module for TME 10 System Administrator’s Guide

Windows NT NetBackup Servers and Clients

• NetBackup System Administrator’s Guide - Windows NT Server• NetBackup System Administrator’s Guide - Windows NT Server - UNIX Supplement• Media Manager System Administrator’s Guide - Windows NT Server• NetBackup User’s Guide - Microsoft Windows

UNIX NetBackup Servers and Clients

• NetBackup System Administrator’s Guide - UNIX• Media Manager System Administrator’s Guide - UNIX• Media Manager Device Configuration Guide

If you have NetBackup add-on products, also see the following:

For PC Clients:

• NetBackup User’s Guide - Macintosh• NetBackup User’s Guide - Microsoft Windows • NetBackup User’s Guide NonTarget Version - Novell NetWare• NetBackup User’s Guide Target Version - Novell NetWare• NetBackup User’s Guide - OS/2 Warp




A

For Netbackup Database Extension Products:

• NetBackup for DB2 System Administrator’s Guide• NetBackup for Informix System Administrator’s Guide• NetBackup for Lotus Notes System Administrator’s Guide• NetBackup for Microsoft Exchange Server System Administrator’s Guide• NetBackup for Microsoft SQL Server System Administrator’s Guide• NetBackup for Oracle on UNIX System Administrator’s Guide• NetBackup for Oracle on Windows NT System Administrator’s Guide• NetBackup for SAP on UNIX System Administrator’s Guide• NetBackup for SAP on Windows NT System Administrator’s Guide• NetBackup for SQL-BackTrack System Administrator’s Guide• NetBackup for SYBASE System Administrator’s Guide

NetBackup AFS:

• NetBackup for AFS System Administrator’s Guide

NetBackup for EMC:

• NetBackup for EMC System Administrator’s Guide

For NetBackup Encryption:

• NetBackup Encryption System Administrator’s Guide

For NetBackup FlashBackup:

• NetBackup FlashBackup System Administrator’s Guide

For NetBackup for NDMP:

• NetBackup for NDMP System Administrator’s Guide

For NetBackup / Plus Module for TME 10:

• NetBackup / Plus Module for TME 10 System Administrator’s Guide




A

User-Directed Backups, Archives, or Restores

Refer to the following documents for information on performing user-directed backups, archives, or restores.

Troubleshooting

Refer to the following document for troubleshooting information.

• NetBackup User’s Guide - Microsoft Windows • NetBackup User’s Guide Target Version - Novell NetWare• NetBackup User’s Guide NonTarget Version - Novell NetWare• NetBackup User’s Guide - OS/2 Warp• NetBackup User’s Guide - UNIX• NetBackup for DB2 System Administrator’s Guide• NetBackup for Informix System Administrator’s Guide• NetBackup for Lotus Notes System Administrator’s Guide• NetBackup for Microsoft Exchange Server System Administrator’s Guide• NetBackup for Microsoft SQL Server System Administrator’s Guide• NetBackup for Oracle on UNIX System Administrator’s Guide• NetBackup for Oracle on Windows NT System Administrator’s Guide• NetBackup for SAP on UNIX System Administrator’s Guide• NetBackup for SAP on Windows NT System Administrator’s Guide• NetBackup for SQL-BackTrack System Administrator’s Guide• NetBackup for SYBASE System Administrator’s Guide

• NetBackup Troubleshooting Guide - UNIX• NetBackup Troubleshooting Guide - Windows NT Server



Date post:	01-Feb-2018
Category:	Documents
Upload:	hoangnguyet
View:	252 times
Download:	2 times