NetBackup™ Release

Notes

Release 10.0.0.1

Document Version 1
NetBackup™ Release Notes
Last updated: 2022-06-27

Legal Notice
Copyright © 2022 Veritas Technologies LLC. All rights reserved.

Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas
Technologies LLC or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.

This product may contain third-party software for which Veritas is required to provide attribution
to the third party (“Third-party Programs”). Some of the Third-party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the Third-party Legal Notices document accompanying this
Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements

The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Veritas Technologies LLC SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.

Veritas Technologies LLC

2625 Augustine Drive
Santa Clara, CA 95054

http://www.veritas.com
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:

https://www.veritas.com/support

You can manage your Veritas account information at the following URL:

https://my.veritas.com

If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:

Worldwide (except Japan) [email protected]

Japan [email protected]

Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. The latest documentation is available on the Veritas
website:

https://sort.veritas.com/documents

Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:

[email protected]

You can also see documentation information or ask a question on the Veritas community site:

http://www.veritas.com/community/

Veritas Services and Operations Readiness Tools (SORT)

Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:

https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
 Contents

Chapter 1 About NetBackup 10.0.0.1 ............................................... 8

About the NetBackup 10.0.0.1 release ................................................ 8

About NetBackup Late Breaking News ............................................... 9
About NetBackup third-party legal notices ........................................... 9

Chapter 2 New features, enhancements, and changes ............. 10

About new enhancements and changes in NetBackup ......................... 10
NetBackup 10.0.0.1 new features, changes, and enhancements ............ 11
Changes in Veritas terminology ................................................. 11
Veritas announces EOL of NetBackup clients on HP-UX ................. 12
Several shutdown commands to be deprecated in a future release
..................................................................................... 12
Update cloud configuration file on the primary server immediately
after install or upgrade to NetBackup 10.0.0.1 ........................ 13
NetBackup for OpenStack enhancements ................................... 14

Chapter 3 Operational notes .............................................................. 15

About NetBackup 10.0.0.1 operational notes ...................................... 15
NetBackup installation and upgrade operational notes ......................... 16
If NetBackup 10.0.0.1 upgrade fails on Windows, revert to previous
log folder structure ............................................................ 16
Native installation requirements ................................................. 16
NetBackup servers must use a host name that is compliant with
RFC 1123 and RFC 952 .................................................... 17
About support for HP-UX Itanium vPars SRP containers ................. 17
NetBackup administration and general operational notes ...................... 18
Restore of the Root ("/") folder for NAS-Data-Protection policy
fails ............................................................................... 18
Stale devices shown on the device tree ....................................... 18
Temporary devices listed as file system assets ............................. 19
NetBackup administration interface operational notes .......................... 19
Certain NetBackup web UI nodes do not work when NBAC is
configured in the 'Required' or 'Automatic' mode ..................... 19
 Contents 5

Delay in NetBackup web UI when adding or removing columns in

Catalog area ................................................................... 19
Job actions not available for workload administrators with limited
RBAC permissions on assets .............................................. 20
Intermittent issues with X forwarding of NetBackup Administration
Console ......................................................................... 21
NetBackup Administration Console fails in Simplified Chinese
UTF-8 locale on Solaris SPARC 64-bit systems with Solaris
10 Update 2 or later .......................................................... 21
NetBackup Cloud operational notes ................................................. 21
Restore of cloud VM backup images replicated with AIR fails
Pre-recovery check ........................................................... 21
Configuring a cloud recovery host on RHEL 8 .............................. 22
NetBackup with Veritas CloudPoint operational notes .......................... 22
CloudPoint on-host agent renewal may fail after RHEL migration
with NetBackup 10.0.0.1 upgrade ........................................ 22
Offline VM backup fails with status code 156 ................................ 23
Restoring a VM (with a Read-only disk) from an app-consistent
snapshot fails .................................................................. 23
VM disks not displayed due to discovery level .............................. 23
Granular restore fails if target path is deleted and recreated ............ 24
Public cloud not supported with gov cloud or China region ............. 24
Indexing not supported on instances created from AWS
Marketplaces AMIs ........................................................... 24
Consistent host snapshot might fail ............................................ 24
Configuring AWS plug-in with IAM role showed that the
Authentication Method field is blank ..................................... 25
Permission denied error occurs if both user and password are
updated .......................................................................... 25
Different source and target zones for Google Cloud Platform are
not supported .................................................................. 25
Broken files system detected .................................................... 26
NetBackup for NDMP operational notes ............................................ 26
Parent directories in the path of a file may not be present in an
NDMP incremental image .................................................. 26
NetBackup for OpenStack operational notes ...................................... 26
CentOS repository mirror URL is updated .................................... 27
NetBackup for OpenStack Datamover API (NBOSDMAPI) service
times out in the haproxy connection ..................................... 27
Policy schedule start time on the Horizon UI is different than
configured in the policy ...................................................... 27
Instance volumes in the incremental backups cannot be mounted
..................................................................................... 27
 Contents 6

NetBackup primary server does not re-issue the token if

NetBackup VM is a 3-node cluster ...................................... 27
Success message appears along with the error message when
you delete the policy that has snapshots ............................... 28
Unable to connect to NetBackup primary server using NBCA .......... 28
Excluded Ceph Volume after restore is not mountable or
formattable ..................................................................... 28
Restored VMs have blank metadata config_drive attached ............. 28
NBOSVM reconfig fails when you add new NetBackup VM to the
cluster ........................................................................... 29
Database does not sync after NetBackup cluster gets new nodes
..................................................................................... 29
Data on boot disk gets backed up despite exclusion ..................... 29
After reinitialization and import, OpenStack certificates are missing
..................................................................................... 29
CLI import changes scheduler trust value to disabled .................... 30
Unable to get node details after you reinitialize the NetBackup
Appliance ....................................................................... 30
Snapshots fails with "object is not subscriptable" for many policy
jobs at the exact same time ............................................... 30
No operation is permitted in insecure way for SSL-enabled
Keystone URL ................................................................ 30
NetBackup internationalization and localization operational notes ........... 31
Support for localized environments in database and application
agents ........................................................................... 31
Certain NetBackup user-defined strings must not contain non-US
ASCII characters .............................................................. 31
NetBackup Snapshot Client operational notes .................................... 32
Snapshot job fails with status code 927 ....................................... 32
HPE 3PAR array snapshot import fails with status code 4213
..................................................................................... 33
Snapshots are deleted after point-in-time rollbacks ........................ 33
Index from Snapshot operation does not populate contents of the
snapshot accurately in the catalog ....................................... 33

Appendix A About SORT for NetBackup Users ............................... 34

About Veritas Services and Operations Readiness Tools ...................... 34

Appendix B NetBackup installation requirements ........................... 36

About NetBackup installation requirements ........................................ 36
Required operating system patches and updates for NetBackup ............ 37
NetBackup 10.0.0.1 binary sizes ...................................................... 38
 Contents 7

Appendix C NetBackup compatibility requirements ....................... 41

About compatibility between NetBackup versions ................................ 41

About NetBackup compatibility lists and information ............................ 42
About NetBackup end-of-life notifications .......................................... 42

Appendix D Other NetBackup documentation and related

documents ..................................................................... 44
About related NetBackup documents ................................................ 44
 Chapter 1
About NetBackup 10.0.0.1
This chapter includes the following topics:

■ About the NetBackup 10.0.0.1 release

■ About NetBackup Late Breaking News

■ About NetBackup third-party legal notices

About the NetBackup 10.0.0.1 release

The NetBackup Release Notes document is meant to act as a snapshot of
information about a version of NetBackup at the time of its release. Old information
and any information that no longer applies to a release is either removed from the
release notes or migrated elsewhere in the NetBackup documentation set.
See “About new enhancements and changes in NetBackup” on page 10.

About EEBs and release content

NetBackup 10.0.0.1 incorporates fixes to many of the known issues that affected
customers in previous versions of NetBackup. Some of these fixes are associated
with the customer-specific issues. Several of the customer-related fixes that were
incorporated into this release were also made available as emergency engineering
binaries (EEBs).
Listings of the EEBs and Etracks that document the known issues that have been
fixed in NetBackup 10.0.0.1 can be found on the Veritas Operations Readiness
Tools (SORT) website and in the NetBackup Emergency Engineering Binary Guide.
See “About Veritas Services and Operations Readiness Tools” on page 34.

About NetBackup appliance releases

The NetBackup appliances run a software package that includes a preconfigured
version of NetBackup. When a new appliance software release is developed, the
 About NetBackup 10.0.0.1 9
About NetBackup Late Breaking News

latest version of NetBackup is used as a basis on which the appliance code is built.
For example, NetBackup Appliance 3.1 is based on NetBackup 8.1 This development
model ensures that all applicable features, enhancements, and fixes that were
released within NetBackup are included in the latest release of the appliance.
The NetBackup appliance software is released at the same time as the NetBackup
release upon which it is based, or soon thereafter. If you are a NetBackup appliance
customer, make sure to review the NetBackup Release Notes that correspond to
the NetBackup appliance version that you plan to run.
Appliance-specific documentation is available at the following location:
http://www.veritas.com/docs/000002217

About NetBackup Late Breaking News

For the most recent NetBackup news and announcements, visit the NetBackup
Late Breaking News website at the following location:
http://www.veritas.com/docs/000040237
Other NetBackup-specific information can be found at the following location:
https://www.veritas.com/support/en_US/15143.html

About NetBackup third-party legal notices

NetBackup products may contain third-party software for which Veritas is required
to provide attribution. Some of the third-party programs are available under open
source or free software licenses. The license agreement accompanying NetBackup
does not alter any rights or obligations that you may have under those open source
or free software licenses.
The proprietary notices and the licenses for these third-party programs are
documented in the NetBackup Third-party Legal Notices document, which is
available at the following website:
https://www.veritas.com/about/legal/license-agreements
 Chapter 2
New features,
enhancements, and
changes
This chapter includes the following topics:

■ About new enhancements and changes in NetBackup

■ NetBackup 10.0.0.1 new features, changes, and enhancements

About new enhancements and changes in

NetBackup
In addition to new features and product fixes, NetBackup releases often contain
new customer-facing enhancements and changes. Examples of common
enhancements include new platform support, upgraded internal software
components, interface changes, and expanded feature support. Most new
enhancements and changes are documented in the NetBackup Release Notes and
the NetBackup compatibility lists.

Note: The NetBackup Release Notes only lists the new platform support that begins
at a particular NetBackup version level at the time of its release. However, Veritas
routinely backdates platform support to previous versions of NetBackup. Refer to
the NetBackup compatibility lists for the most up-to-date platform support listings.

See “About the NetBackup 10.0.0.1 release” on page 8.

See “About NetBackup compatibility lists and information” on page 42.
 New features, enhancements, and changes 11
NetBackup 10.0.0.1 new features, changes, and enhancements

NetBackup 10.0.0.1 new features, changes, and

enhancements
New features, changes, and enhancements in NetBackup 10.0.0.1 are grouped
below by category. Select a link to read more information about the topic.

New features
■ Changes in Veritas terminology

Secure communication features, changes, and

enhancements
■
Note: Before you install or upgrade to NetBackup 10.0.0.1 from a release earlier
than 8.1, make sure that you read and understand the NetBackup Read This
First for Secure Communications document. NetBackup 8.1 includes many
enhancements that improve the secure communications of NetBackup
components. The NetBackup Read This First for Secure Communications
document describes the features and benefits of these enhancements:
NetBackup Read This First for Secure Communications

Support changes and enhancements

■ Veritas announces EOL of NetBackup clients on HP-UX
■ Several shutdown commands to be deprecated in a future release

Cloud-related changes and enhancements

■ Update cloud configuration file on the primary server immediately after install
or upgrade to NetBackup 10.0.0.1

Other announcements
■ NetBackup for OpenStack enhancements

Changes in Veritas terminology

To modernize our terminology, Veritas has begun to replace certain outdated terms
with more current terms.

Note: As Veritas continues to update its terminology, the deprecated terms and
the new terms may be used interchangeably.
 New features, enhancements, and changes 12
NetBackup 10.0.0.1 new features, changes, and enhancements

Deprecated term New term

Master Primary

Slave Secondary or media server

Whitelist or white list Allowed list

Blacklist or black list Blocked list

White hat Ethical

Black hat Unethical

Veritas announces EOL of NetBackup clients on HP-UX

Support for NetBackup clients running on HP-UX has reached end-of-life (EOL).
Veritas will no longer deliver NetBackup client software for the HP-UX platform.
NetBackup 10.0.0.1 will be the last release that provides HP-UX client support.
If you want the benefits of newer NetBackup clients, you must migrate HP-UX clients
to another supported client operating system platform. NetBackup 10.0.0.1 HP-UX
clients maintain compatibility with newer NetBackup server versions. (See the
“Compatibility between NetBackup versions” section of the Software Compatibility
list.)
Veritas will continue to provide support for HP-UX clients in accordance with the
published Veritas Product End of Life policy guidelines.

Several shutdown commands to be deprecated in a future release

A new, fully documented command for shutting down NetBackup processes and
daemons will be provided in an upcoming release. At that point, the following
commands will no longer be available:
■ bp.kill_all

■ bpdown

■ bpclusterkill

Please plan accordingly. The new command will be announced in future release
notes and in the NetBackup Commands Reference Guide.
 New features, enhancements, and changes 13
NetBackup 10.0.0.1 new features, changes, and enhancements

Update cloud configuration file on the primary server immediately

after install or upgrade to NetBackup 10.0.0.1
If you use cloud storage in your NetBackup environment, you may need to update
your cloud configuration file on the NetBackup primary server immediately after
you install or upgrade to NetBackup 10.0.0.1. If a cloud provider or related
enhancement is not available in the cloud configuration file after you upgrade to
NetBackup 10.0.0.1, related operations fail.
Veritas continuously adds new cloud support to the cloud configuration files between
releases. Updating your cloud configuration files is necessary only if your cloud
storage provider was added to the cloud configuration package after version 2.9.0.
The following cloud support has been added to version 2.9.2 and later but was not
included in the NetBackup 10.0.0.1 final build:
■ Amazon Glacier Instant Retrieval (IR)
■ Amazon GovCloud - Glacier Instant Retrieval (IR)- Amazon (S3)
■ Asia Pacific (Jakarta) region
■ Google (S3) - Asia South2 (Delhi) region
■ Google (S3) - Australia-Southeast2 (Melbourne) region
■ Google (S3) - North America Northeast2 (Toronto) region
■ Quantum Active Archive and ActiveScale Systems - Standard (S3)
■ Quantum Active Archive and ActiveScale Systems - Glacier (S3)
■ Wasabi (S3) - EU-West-2 (Paris) region
■ Wasabi (S3) - Wasabi AP Southeast 2 (Sydney) region
■ Wasabi (S3) - Wasabi EU Central 2 (Frankfurt) region
■ Wasabi (S3) - Wasabi CA Central 1 (Toronto) region
■ NetBackup Recovery Vault Seagate Lyve Cloud us-west-1
■ NetBackup Recovery Vault Seagate Lyve Cloud us-east-1
For the latest cloud configuration package, see the following article:
https://www.veritas.com/content/support/en_US/downloads/update.UPD971796
For additional information on adding cloud storage configuration files, refer to the
following tech note:
http://www.veritas.com/docs/100039095
 New features, enhancements, and changes 14
NetBackup 10.0.0.1 new features, changes, and enhancements

NetBackup for OpenStack enhancements

This release of NetBackup includes the following enhancements:
■ NetBackup for OpenStack supports Kolla Ansible.
NetBackup 10.0.0.1 adds the support for another OpenStack distribution, Kolla
Ansible.
■ NetBackup for OpenStack supports multi-attach volumes.
NetBackup for OpenStack now supports multi-attach volumes for backup and
restore.
■ NetBackup for OpenStack supports multipath storage.
NetBackup for OpenStack now supports multipath storage for backup and
restore.
For more information, see NetBackup for OpenStack Administrator's Guide.
 Chapter 3
Operational notes
This chapter includes the following topics:

■ About NetBackup 10.0.0.1 operational notes

■ NetBackup installation and upgrade operational notes

■ NetBackup administration and general operational notes

■ NetBackup administration interface operational notes

■ NetBackup Cloud operational notes

■ NetBackup with Veritas CloudPoint operational notes

■ NetBackup for NDMP operational notes

■ NetBackup for OpenStack operational notes

■ NetBackup internationalization and localization operational notes

■ NetBackup Snapshot Client operational notes

About NetBackup 10.0.0.1 operational notes

NetBackup operational notes describe and explain important aspects of various
NetBackup operations that may not be documented elsewhere in the NetBackup
documentation set or on the Veritas Support website. The operational notes can
be found in the NetBackup Release Notes for each version of NetBackup. Typical
operational notes include known issues, compatibility notes, and additional
information about installation and upgrade.
Operational notes are often added or updated after a version of NetBackup has
been released. As a result, the online versions of the NetBackup Release Notes or
other NetBackup documents may have been updated post-release. You can access
 Operational notes 16
NetBackup installation and upgrade operational notes

the most up-to-date version of the documentation set for a given release of
NetBackup at the following location on the Veritas Support website:
NetBackup Release Notes, Administration, Installation, Troubleshooting, Getting
Started, and Solutions Guides

NetBackup installation and upgrade operational

notes
NetBackup can be installed and upgraded in heterogeneous environments using
a variety of methods. NetBackup is also compatible with a mixture of servers and
clients that are at various release levels in the same environment. This topic contains
some of the operational notes and known issues that are associated with the
installation, upgrade, and software packaging of NetBackup 10.0.0.1.

If NetBackup 10.0.0.1 upgrade fails on Windows, revert to previous

log folder structure
The legacy log folder structure for non-root or non-admin invoked process logs has
changed. The new folder structure is created under the process log directory name.
For more information, refer to the File name format for legacy logging section from
the Veritas NetBackup Logging Reference Guide.
For Windows, if the upgrade to NetBackup 10.0.0.1 fails and rollback occurs, run
the following command to continue working on an earlier NetBackup version:
mklogdir.bat -fixFolderPerm

For more information, refer to the mklogdir command from the Veritas NetBackup
Commands Reference Guide.

Native installation requirements

In NetBackup 8.2, a change was made to initial installs such that the answer file is
now required. This change may have some negative effect on users who want to
use the native packages to create VM templates or otherwise install the NetBackup
packages without configuring the product. On Linux, one possible way of obtaining
the previous behavior is with the –noscripts option of the RPM Package Manager.
Providing this option when installing the VRTSnbpck package avoids the configuration
steps. This option does not need to be provided when you install other packages.
The answer file must still exist, but the only value that must be provided is the role
of the machine, either a client or a media server. For example:
 Operational notes 17
NetBackup installation and upgrade operational notes

echo "MACHINE_ROLE=CLIENT" > /tmp/NBInstallAnswer.conf

rpm -U --noscripts VRTSnbpck.rpm
rpm -U VRTSpbx.rpm VRTSnbclt.rpm VRTSpddea.rpm

NetBackup servers must use a host name that is compliant with RFC
1123 and RFC 952
Starting with NetBackup 8.0, all NetBackup server names must use a host name
that is complaint with RFC 1123 ("Requirements for Internet Hosts - Application
and Support") and RFC 952 ("DOD Internet Host Table Specification") standards.
These standards include the supported and unsupported characters that can be
used in a host name. For example, the underscore character ( _ ) is not a supported
character for host names.
More information is available about these standards and about this issue:
RFC 952
RFC 1123
http://www.veritas.com/docs/000125019
These standards should be applied to all computing hosts, including all NetBackup
hosts. To accommodate legacy environments and functionality, features of
NetBackup that were implemented before 2010 continue to allow some
non-compliant characters. But newer features, as well as more recently integrated
3rd-party components, are not tested with nor expected to be compatible with host
names that do not adhere to the industry standards.
In some situations, it may be possible to configure name services with a network
hostname alias that is standards-compliant, and then use the alias when you
configure NetBackup. But using host names that are standards-compliant is the
only way to ensure compatibility with all features.

About support for HP-UX Itanium vPars SRP containers

Hewlett-Packard Enterprise (HPE) introduced a new type of container for HP-UX
Virtual Partitions (vPars)-enabled servers called Secure Resource Partitions (SRPs).
As part of the security changes introduced by SRPs, native HP-UX install tools such
as swinstall and swremove are disabled from being run within the SRP
environment. The swinstall and swremove tools can only be called from the global
host running vPars, which then pushes the native packages to the SRP containers.
NetBackup only supports installing into the global view. NetBackup installation fails
if you try to install into an HPE Itanium SRP container (private file system, shared
file system, or workload).
 Operational notes 18
NetBackup administration and general operational notes

NetBackup administration and general operational

notes
NetBackup provides a complete, flexible data protection solution for a variety of
platforms. The platforms include Windows, UNIX, and Linux systems. In addition
to a standard set of data protection features, NetBackup can also utilize several
other licensed and non-licensed components to better protect a variety of different
systems and environments. This topic contains some of the general operational
notes and known issues that are associated with the administration of NetBackup
10.0.0.1.

Restore of the Root ("/") folder for NAS-Data-Protection policy fails

While restoring from a snapshot image for NAS-Data-Protection policy, if you select
"/" as the restore pattern, the restore fails with the error 133 (invalid request).
Workaround:
Do not select "/" for restore. Instead, expand the “/” tree structure, and select the
items individually that you want to restore.

Stale devices shown on the device tree

During the indexing or restore process, sometimes the stale devices that are present
in the volume are not cleaned up and are displayed in the device tree.
Workaround:
1. Unmount any file systems that mounted the device. (If required use force
unmount)

2. If any of the partitions belongs to LVM, then remove the volume group from
disk using the vgreduce command and then the pvremove command.
3. Run the blockdev -flushbufs command to remove any outstanding reference
to that device.
4. Remove the device references from the device tree. For example,
whole/partition disks /dev/xvdf, /dev/disk/by-path, by-id, by-label, by-partuuid
and by-uuid
5. Use the following command to remove the device from sysfs:
6. echo 1 > /sys/block/device-name/device/delete

Where device-name might be xvdf.

7. Reboot the host to resolve this issue.
 Operational notes 19
NetBackup administration interface operational notes

Temporary devices listed as file system assets

If the discovery process and restore process are running at the same time, for the
duration of the restore process, sometimes the temporary devices are discovered
and listed as a files system asset. After the restore process is complete, the
temporary devices are no longer listed as file system assets during the subsequent
discovery.

NetBackup administration interface operational

notes
The NetBackup administrator has a choice of several interfaces to use to administer
NetBackup. All of the interfaces have similar capabilities. This topic contains some
of the operational notes and known issues that are associated with these interfaces
in NetBackup 10.0.0.1.
For more information about the specific NetBackup administration interfaces, refer
to the NetBackup Web UI Administrator's Guide or the NetBackup Administrator's
Guide, Volume I.
For information about how to install the interfaces, refer to the NetBackup Installation
Guide. For information about platform compatibility with the administration consoles,
refer to the various NetBackup compatibility lists available on the Veritas Support
website.
See “About NetBackup compatibility lists and information” on page 42.

Certain NetBackup web UI nodes do not work when NBAC is

configured in the 'Required' or 'Automatic' mode
If the NetBackup Access Control (NBAC) is configured in the 'Required' or 'Automatic'
mode in your NetBackup environment, the following nodes in the NetBackup web
UI do not work as expected:
■ Bare Metal Restore
■ Catalog Management
■ Host Properties

Delay in NetBackup web UI when adding or removing columns in

Catalog area
In the Catalog area of the web UI, you can add or remove columns from the table
of images. The more images that are displayed, the longer it takes to for the interface
 Operational notes 20
NetBackup administration interface operational notes

to refresh if you add or remove columns. This issue will be fixed in an upcoming
release.

Job actions not available for workload administrators with limited

RBAC permissions on assets
Note following issues for view and managing jobs with the NetBackup web UI:
■ A job does not receive an asset ID until it runs, which means a queued job does
not have an asset ID. Users that have roles with more granular asset permissions
for a workload are not able to view or cancel queued jobs.
This behavior does not affect users with an RBAC role that has full job
permissions or a role that can manage all assets for a particular workload.
■ A job does not receive an asset ID if the asset is not yet discovered. Users that
have roles with more granular asset permissions for a workload are not able to
cancel or restart a job for the asset.
This behavior does not affect users with an RBAC role that has full job
permissions or a role that can manage all assets for a particular workload.

Example 1 - VMware administrator with limited asset

permissions cannot cancel any queued jobs
Consider a user that has RBAC permissions only for a VMware vCenter or one or
more VMs.
■ The user cannot see queued jobs for the vCenter or for the VMs.
■ Similarly, the user is not able to cancel any queued jobs for the vCenter or for
the VMs.

Example 2 - VMware or RHV administrator with limited

asset permissions cannot cancel or restart jobs for
undiscovered assets
Consider a user that has RBAC permissions only for a VMware vCenter or an RHV
server. This user also has one or more job permissions for these assets, but does
not have job permissions for all workload assets.
■ A new asset is added to the environment, but the discovery process hasn't run
yet.
■ An existing intelligent group is configured so it includes the new asset.
■ When the backup runs, it includes the new asset in the backup.
 Operational notes 21
NetBackup Cloud operational notes

■ The user is not able to cancel or restart a job for the new asset.

Intermittent issues with X forwarding of NetBackup Administration

Console
Intermittent issues may occur with X forwarding of the NetBackup Administration
Console. This behavior only occurs when you use X forwarding. This issue does
not occur at the local console. The issue is most commonly seen on Linux servers,
but not exclusively. The issue generally occurs when older versions of X viewers
are used, such as Xming and XBrowser.
The use of MobaXterm seems to minimize or eliminate the issue. If you experience
issues with X forwarding, consider upgrading your X viewer and retrying the
operation or access the server from the local console.

NetBackup Administration Console fails in Simplified Chinese UTF-8

locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2
or later
The NetBackup Administration Console may encounter a core dump issue when
the Simplified Chinese UTF-8 locale is used on a Solaris SPARC 64-bit system
with Solaris 10 Update 2 and later installed. For more information, refer to Bug ID
6901233 at the following URL on the Oracle Technology Network website:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6901233
If you encounter this issue, apply the appropriate Solaris patches or upgrades that
Oracle provides for this issue.

NetBackup Cloud operational notes

NetBackup Cloud Storage enables you to back up and restore data from cloud
Storage as a Service (STaaS) vendors. This topic contains some of the operational
notes and known issues that are associated with the NetBackup Cloud in NetBackup
10.0.0.1.

Restore of cloud VM backup images replicated with AIR fails

Pre-recovery check
Restore of cloud VM backup images replicated to another NetBackup domain using
Auto Image Replication (AIR) with a NetBackup version earlier than 10.0 fails during
Pre-recovery check with the error exception: Illegal xml request string!.
 Operational notes 22
NetBackup with Veritas CloudPoint operational notes

AIR is supported for cloud VM backup images from NetBackup version 10.0 onwards.
As this feature is new, AIR backup images of cloud virtual machines replicated to
an earlier version of NetBackup domain such as 9.1 is not supported. The NetBackup
domain primary server version should be 10.0 or higher. You might encounter the
error if the primary server version of the NetBackup target domain is earlier than
10.0.
Workaround:
Make sure that the target NetBackup domain primary server version is 10.0 or
higher.

Configuring a cloud recovery host on RHEL 8

Before you run ims_system_config.py to configure the cloud recovery host on
RHEL 8, install Python 2 and create a soft link from Python 2 to Python. The
ims_system_config.py script uses Python 2.

NetBackup with Veritas CloudPoint operational

notes
This topic contains some of the operational notes and known issues that are
associated with the Veritas CloudPoint and NetBackup 10.0.0.1.

CloudPoint on-host agent renewal may fail after RHEL migration with
NetBackup 10.0.0.1 upgrade
After performing a migration of Red Hat Enterprise Linux (RHEL) 7 to RHEL 8 with
the NetBackup upgrade from version 9.1.0.1 to 10.0.0.1 with a new RHEL 8 host,
you may observe the following issues due to the change in the CloudPoint (CP)
host IP or FQDN:
■ On-host agent renewal will fail.
■ CP extension will not work.
Workaround:
■ For configured on-host agents:
In the case of migration from RHEL 7 to RHEL 8 that involves a new VM for a
CP host which is registered in NetBackup with a non-static IP address or FQDN,
update the new IP address or FQDN in the flexsnap.conf file and renew the
agent service with a fresh agent token.
■ For extensions:
 Operational notes 23
NetBackup with Veritas CloudPoint operational notes

After migration is successful and the CP extension is upgraded to the latest

build, renew the extension with new CP IP address.
For steps to renew the on-host agent and the CP extension, see the NetBackup
CloudPoint Install and Upgrade Guide.

Offline VM backup fails with status code 156

Offline backup of a virtual machine VM fails with status code 156 if the credentials
are added for agentless file and folder recovery.
This behavior occurs because NetBackup tries to take an application-consistent
snapshot of the VM, which fails because the VM is offline and CloudPoint cannot
connect to the agent.

Restoring a VM (with a Read-only disk) from an app-consistent

snapshot fails
For a Windows VM, the snapshot fails with a VSS error, like the following; hence
the VM cannot be restored.
Failure: flexsnap.GenericError: Failed to take snapshot(error:Failed
to create VSS snapshot of the selected volumes.)"

For a Linux VM, the snapshot may or may not be successful for a VM under which
the disk is discovered, but it will fail for other VMs due to the missing dependencies.
Error example:
linear_flow.Flow: create snapshot(test-win) of host
linux-1(len=4)'requires['snap_google-gcepd-us-west2-b-7534340043132122994']

but no other entity produces said requirements\n MissingDependencies

In the above case, if a snapshot is successful for a Linux VM, a Read-only disk is
restored in a Read/write mode.

VM disks not displayed due to discovery level

After you restore a VM from backup copy, the VM disks are not displayed in the
Volumes tab of the Virtual machine details page. The CloudPoint server’s level
discovery is not able to map the virtual machine disks with the virtual machine
because it requires deep discovery at the configuration level.
Workaround:
 Operational notes 24
NetBackup with Veritas CloudPoint operational notes

Run deep discovery manually. Select a configuration for the provider and click
Discover. Alternatively, you can wait for a periodic autodiscovery to run, which
performs deep discovery.

Granular restore fails if target path is deleted and recreated

On protected VM assets, if you recreate a filesystem and mount it to the same drive
or path, then subsequent discovery updates the CloudPoint asset database for
newly created filesystems. Also, the old filesystem assets that are mounted on
same drive or mount point are marked for deletion but not removed from asset
database. This is because the retention period is of 1 day if there is no snapshot
associated to the older filesystem asset. In this case, if you initiate the granular
restore with the same drive or mount path as a target, then the operation might fail
with an error. This issue doesn’t occur if you try granular restore after 1 day on the
such drives or mount paths. This problem also exists if you unmount the existing
disk from the drive or mount path and mount another file-system to same drive or
mount path.
Workaround:
Do not use a filesystem as granular restore target destination that was recreated
from an existing filesystem or newly created filesystem on last discovered mount
point or drive.

Public cloud not supported with gov cloud or China region

If you try to a configure a public cloud region plug-in with a gov cloud or China
region cloud, the following error occurs:
Plug-in authentication failed. Credentials are invalid.

Indexing not supported on instances created from AWS Marketplaces

AMIs
The indexing process for the instances created from AWS Marketplaces AMIs fails
with the following error:

Failed to attach new volume: Cannot attach volume <vol-xxx>

with Marketplace codes as the instance <i-xxx>
is not in the 'stopped' state.

Consistent host snapshot might fail

Sometimes the consistent host snapshot might fail with the following error:
 Operational notes 25
NetBackup with Veritas CloudPoint operational notes

The host level snapshot of <host_nam> cannot be performed as asset

hierarchy is incomplete.

This issue occurs due to the following reasons:

■ Granular restore is performed on the host in the last 10 minutes.
■ A new disk is attached to the host and the discovery of required assets is not
completed.

Configuring AWS plug-in with IAM role showed that the Authentication
Method field is blank
If you attach an IAM role to a CloudPoint server that is already added to NetBackup,
the role is not assigned in NetBackup.
Workaround:
You must sync NetBackup with CloudPoint by using the following command:
/usr/openv/volmgr/bin/tpconfig -update -cloudpoint_server <ip/name
which CP is registered in NBU> -cloudpoint_server_user_id admin
-manage_workload CLOUD

Permission denied error occurs if both user and password are

updated
An issue might occur if you try to update the CloudPoint Server agentless connection
credentials with a non-standard user. If you create a new user on a specific VM,
then the user should be a part of the sudoers file, or the connection fails. The new
user must have the permission to perform any root operation using the sudo
command without a password.
Workaround:
To avoid this issue:
■ Ensure that the sudo command without password is configured. Check the user
entry in the /etc/sudoers file.
■ Ensure that the binary flexsnap-agentless and plug-ins are not created with the
old user. If they are created with the old user, delete the files.

Different source and target zones for Google Cloud Platform are not
supported
Although Google Cloud Platform allows the restore snapshot across all zones, the
CloudPoint server does not allow the source location and target location of the
 Operational notes 26
NetBackup for NDMP operational notes

restore to be in different zones across plug-in configurations. This issue occurs

because the zones are managed by configuration and so the restore to zones which
is not part of config is not supported.
Workaround:
Ensure that the source location and the target locations are in the same zones as
plug-in configurations.

Broken files system detected

Sometimes, a broken file system is detected on CloudPoint server during the restore
process. In this case, the mount fails with the following error: Invalid super block or
structure needs cleaning.

NetBackup for NDMP operational notes

NetBackup for NDMP is an optional NetBackup application. It enables NetBackup
to use the Network Data Management Protocol (NDMP) to initiate and control
backups and restores of Network Attached Storage (NAS) systems. This topic
contains some of the operational notes and known issues that are associated with
NetBackup for NDMP in NetBackup 10.0.0.1.

Parent directories in the path of a file may not be present in an NDMP

incremental image
An issue can occur if a NetBackup Network Data Management Protocol (NDMP)
backup policy is configured with the directive set type=tar in the backup selection.
Parent directories in the path of a file that an incremental NDMP backup saves may
not be present in the backup image. For more information on this issue, refer to the
following tech note on the Veritas Support website:
http://www.veritas.com/docs/000095049

NetBackup for OpenStack operational notes

NetBackup for OpenStack is an optional NetBackup application. This topic contains
some of the operational notes and known issues that are associated with NetBackup
for OpenStack in NetBackup 10.0.0.1.
 Operational notes 27
NetBackup for OpenStack operational notes

CentOS repository mirror URL is updated

The CentOS repository mirror URL is updated to vault.centos.org from
mirror.centos.org. You must update it in all Yum repository files located at
/etc/yum.repos.d/CentOS-*.

NetBackup for OpenStack Datamover API (NBOSDMAPI) service

times out in the haproxy connection
The NBOSDMAPI service in the haproxy connection may time out due to slow
response time in highly-used environments.
The default haproxy configuration works fine with most of the environments. When
the time-out issue with the NBOSDMAPI is observed, customize the haproxy
configuration. For more information, see the following tech note:
https://www.veritas.com/support/en_US/article.100052551

Policy schedule start time on the Horizon UI is different than

configured in the policy
The policy schedule start time that is displayed on the Policy Details page of the
Horizon UI may be different by 23 minutes than what is configured in the policy.
The difference in time is caused by the wrong offset value that is obtained during
the time conversions from one time zone to another time zone. This issue exists in
the pytz library component that is used in NetBackup for OpenStack.
However, this issue is limited to the UI only. The backend and API have the correct
UTC timings. This issue has no effect on the snapshot job scheduler, which runs
on time as configured.

Instance volumes in the incremental backups cannot be mounted

Newly added disks of an instance for incremental backup get backed up successfully
but these discs cannot be mounted.

NetBackup primary server does not re-issue the token if NetBackup

VM is a 3-node cluster
Re-issue of the tokens for NetBackup certificate in the NetBackup configurator does
not work if NetBackup VM is a 3-node cluster.
Workaround:
 Operational notes 28
NetBackup for OpenStack operational notes

To resolve this issue, enable allow auto re-issue token on the primary server. You
must enter "" in the Token field on the NetBackup configurator. This configuration
lets you proceed if the NetBackup OpenStack VM already has the certificates that
primary server provides.

Success message appears along with the error message when you
delete the policy that has snapshots
When you delete the policy that has snapshots, the following success and error
messages appear. However, the policy is not deleted and only error message should
appear.
■ Error: Invalid state: This policy contains snapshots. Please delete
all snapshots and try again.

■ Success: Deleted: <policy name>

Unable to connect to NetBackup primary server using NBCA

While configuring NetBackup VM, if you enter NetBackup Primary Server name,
the following error message appears:
Failed to establish connection with the NetBackup master server.
Error: HTTPSConnectionPool(host='NBU.master.server', port=443): Max
retries exceeded with url: /netbackup/security/ping (Caused by
NewConnectionError('<urllib3.connection.HTTPSConnection object at
0x7f9e466b0ef0>: Failed to establish a new connection: [Errno -2]
Name or service not known',))

Workaround:
Add IP host name mapping in /etc/hosts to resolve this issue.
For more information, see the following Support article:
https://www.veritas.com/support/en_US/article.100045941

Excluded Ceph Volume after restore is not mountable or formattable

VM Volumes stored on Ceph are successfully excluded from backup if desired.
Restore creates empty Ceph Volume, which is not attachable or formattable.

Restored VMs have blank metadata config_drive attached

For every restore, the metadata config_drive is set as blank value.
 Operational notes 29
NetBackup for OpenStack operational notes

Workaround:
Delete metadata config_drive or set the desired value.

NBOSVM reconfig fails when you add new NetBackup VM to the

cluster
NetBackup re-configuration fails when you add the nodes to the existing NetBackup
VM.
Reason is that the previous MySQL password was not working and MySQL root
access has been reset.
Workaround:
Remove /root/.my.cnf file on already configured NetBackup VM and reconfigure
it.

Database does not sync after NetBackup cluster gets new nodes
After NetBackup re-configuration post addition of two more nodes to existing
NetBackup VM cluster ("import policies" was not selected), the databases do not
sync against already existing NetBackup VM.
It is expected that while adding the two new nodes, the databases on node1 should
get synced up with the two new nodes, and the existing policies must be available
post the reconfig on the new 3-node NetBackup VM cluster.
Workaround:
Run the policy import from CLI.

Data on boot disk gets backed up despite exclusion

VM was set with metadata exclude_boot_disk_from_backup set to true. Restored
instance shows that data was backed up and restored.

After reinitialization and import, OpenStack certificates are missing

Reinitialization does not keep the already uploaded OpenStack certificates used
to communicate with OpenStack.
Workaround:
Upload the certificates again.
 Operational notes 30
NetBackup for OpenStack operational notes

CLI import changes scheduler trust value to disabled

When the import functionality is used by CLI, the scheduler trust changes from
enabled to disabled.
Workaround:
Configure NetBackup with import option from UI after reinitialization.

Unable to get node details after you reinitialize the NetBackup

Appliance
After you reinitialize the NetBackup Appliance, the UI and CLI do not display the
node information.
Workaround:
Restart nbosjm-policies and nbosjm-cron services on NetBackup nodes.
systemctl restart nbosjm-policies

systemctl restart nbosjm-cron

Snapshots fails with "object is not subscriptable" for many policy jobs
at the exact same time
Running more than 25 policies at the same time leads to an error. The nbosdmapi
service does not respond.
Snapshots fail with Object is not subscriptable. error.
Workaround:
Contact Veritas Support to implement a known workaround.

No operation is permitted in insecure way for SSL-enabled Keystone

URL
For SSL enabled OpenStack, Backup and Restore jobs fail with missing TLS CA
certificate bundle error.
Workaround:
Configure the NetBackup appliance with OpenStack CA provided.
Or provide OpenStack CA to /etc/nbosjm/ca-chain.pem
 Operational notes 31
NetBackup internationalization and localization operational notes

NetBackup internationalization and localization

operational notes
This topic contains some of the operational notes and known issues that are
associated with internationalization, localization, and non-English locales in
NetBackup 10.0.0.1.

Support for localized environments in database and application

agents
Non-ASCII characters are supported in the following fields for NetBackup database
and application agents.
■ Oracle:
Datafile path, Tablespace name, TNS path
■ DB2:
Datafile path, Tablespace name
■ SAP:
English SAP runs on localized OS. ( No specific SAP fields are localized.)
■ Exchange:
Mailboxes, Mails, Attachment names and contents, Public folders, Contacts,
Calendar, Folders and Database paths
■ SharePoint:
Site Collection Names, Libraries and lists within the site collection
■ Lotus Notes:
Emails data /.nsf files
■ Enterprise Vault (EV) agent:
Vault store, Partitions, Data
■ VMWare:
Username, Password, VM display name, DataCenter, Folder, Datastore,
Resource pool, VApp, Network name, VM disk path

Certain NetBackup user-defined strings must not contain non-US

ASCII characters
The following NetBackup user-defined strings must not contain non-US ASCII
characters:
 Operational notes 32
NetBackup Snapshot Client operational notes

■ Host name (primary server, media server, Enterprise Media Manager (EMM)
server, volume database host, media host, client, instance group)
■ Policy name
■ Policy KEYWORD (Windows only)
■ Backup, Archive, and Restore KEYWORD (Windows only)
■ Storage unit name
■ Storage unit disk pathname (Windows only)
■ Robot name
■ Device name
■ Schedule name
■ Media ID
■ Volume group name
■ Volume pool name
■ Media description
■ Vault policy names
■ Vault report names
■ BMR Shared Resource Tree (SRT) name
■ Token name

NetBackup Snapshot Client operational notes

NetBackup Snapshot Client provides a variety of snapshot-based features for
NetBackup. It supports clients on UNIX, Linux, and Windows platforms, on Fibre
Channel networks (SANs) or traditional LANs. Each snapshot method relies on the
snapshot technology that is built into the storage subsystem where the data is
stored. This topic contains some of the operational notes and known issues that
are associated with Snapshot Client in NetBackup 10.0.0.1.

Snapshot job fails with status code 927

Snapshot job fails with status code 927: No backup host from configured backup
host pool is available for job execution.
This issue appears when you do not upgrade at least one backup host from the
pool, along with primary server upgrade from NetBackup 8.3 to NetBackup 9.1.
This situation fails the accelerator-enabled DNAS policy for NAS.
 Operational notes 33
NetBackup Snapshot Client operational notes

Workaround:
Upgrade the primary server along with at least one of the backup hosts from the
backup host pool from NetBackup 8.3 to NetBackup 9.1. Then run the
accelerator-enabled DNAS policy for NAS.

HPE 3PAR array snapshot import fails with status code 4213
An HPE 3PAR array snapshot import fails with status code 4213. Currently,
CloudPoint does not support the snapshot type Clone for the VSO (virtual server
owner) snapshot method.
Workaround: Reconfigure the policy using the snapshot type COW (copy-on-write).

Snapshots are deleted after point-in-time rollbacks

In the case of the VSO FIM snapshot method for Network Attached Storage (NAS),
when you perform a point-in-time rollback from an older copy, the snapshots on
the storage array after that point are deleted. This operation renders the NetBackup
image inconsistent, thus the image is deleted.
Similarly, when you perform a point-in-time rollback of an older snapshot from one
of the mountpoints, only the snapshot that is associated with that mount point is
deleted. Also, the images are deleted because they become inconsistent. However,
the other snapshots belonging to other mountpoints would still reside on the storage
array and you need to manually clean them up.

Index from Snapshot operation does not populate contents of the

snapshot accurately in the catalog

Note: This issue is specific to on-premises workloads and UNIX platforms.

In the case of the Index from Snapshot operation, if the /usr/openv directory on
the snapshot mount host is linked to a different path, the contents of the snapshot
is not indexed accurately in the catalog.
Workaround: Reconfigure the storage lifecycle policy to have only the snapshot
operation and remove the index from snapshot operation.
 Appendix A
About SORT for
NetBackup Users
This appendix includes the following topics:

■ About Veritas Services and Operations Readiness Tools

About Veritas Services and Operations Readiness

Tools
Veritas Services and Operations Readiness Tools (SORT) is a robust set of
standalone and web-based tools that support Veritas enterprise products. For
NetBackup, SORT provides the ability to collect, analyze, and report on host
configurations across UNIX/Linux or Windows environments. This data is invaluable
when you want to assess if your systems are ready for an initial NetBackup
installation or for an upgrade.
Access SORT from the following webpage:
https://sort.veritas.com/netbackup
Once you get to the SORT page, more information is available as follows:
■ Installation and Upgrade Checklist
Use this tool to create a checklist to see if your system is ready for a NetBackup
installation or an upgrade. This report contains all the software and the hardware
compatibility information specific to the information provided. The report also
includes product installation or upgrade instructions, as well as links to other
references.
■ Hot fix and EEB Release Auditor
Use this tool to find out whether a release that you plan to install contains the
hot fixes that you need.
 About SORT for NetBackup Users 35
About Veritas Services and Operations Readiness Tools

■ Custom Reports
Use this tool to get recommendations for your system and Veritas enterprise
products.
■ NetBackup Future Platform and Feature Plans
Use this tool to get information about what items Veritas intends to replace with
newer and improved functionality. The tool also provides insight about what
items Veritas intends to discontinue without replacement. Some of these items
include certain NetBackup features, functionality, 3rd-party product integration,
Veritas product integration, applications, databases, and the OS platforms.
Help for the SORT tools is available. Click Help in the upper right corner of the
SORT home page. You have the option to:
■ Page through the contents of the help similar to a book
■ Look for topics in the index
■ Search the help with the search option
 Appendix B
NetBackup installation
requirements
This appendix includes the following topics:

■ About NetBackup installation requirements

■ Required operating system patches and updates for NetBackup

■ NetBackup 10.0.0.1 binary sizes

About NetBackup installation requirements

This release of NetBackup may contain changes to the minimum system
requirements and procedures that are required for installation. These changes affect
the minimum system requirements for both Windows and UNIX platforms. Much of
the installation instructional information in the NetBackup Release Notes is provided
for convenience. Detailed installation instructions are found in the NetBackup
Installation Guide and the NetBackup Upgrade Guide.
See “NetBackup installation and upgrade operational notes” on page 16.
■ Before you upgrade the NetBackup server software, you must back up your
NetBackup catalogs and verify that the catalog backup was successful.
■ Database rebuilds are likely to occur in each major, minor (single-dot), and
release update (double-dot) version of NetBackup. Therefore, before upgrading
to NetBackup 10.0.0.1, you must ensure that you have an amount of free disk
space available that is equal to or greater than the size of the NetBackup
database. That means for default installations, you are required to have that
amount of free space on the file system containing the /usr/openv/db/data
(UNIX) or <install_path>\Veritas\NetBackupDB\data (Windows) directories.
If you have changed the location of some of the files in either of these directories,
 NetBackup installation requirements 37
Required operating system patches and updates for NetBackup

free space is required in those locations equal to or greater than the size of the
files in those locations. Refer to the NetBackup Administrator's Guide, Volume
I for more information about storing NBDB database files in alternate locations.

Note: This free disk space requirement assumes that you have already
performed the best practice of completing a successful catalog backup before
you begin the upgrade.

■ Primary and media servers must have a minimum soft limit of 8000 file
descriptors per process for NetBackup to run correctly.
For more information about the effects of an insufficient number of file descriptors,
refer to the following articles on the Veritas Support website:
http://www.veritas.com/docs/000013512
■ NetBackup primary and media servers exchange server version information at
startup, and every 24 hours. This exchange occurs automatically. During startup
after an upgrade, the upgraded media server uses the vmd service to push its
version information to all of the servers that are listed in its server list.
■ Veritas recommends that you have the primary server services up and available
during a media server upgrade.
■ All compressed files are compressed using gzip. The installation of these files
requires gunzip and gzip, so make sure that they are installed on the computer
before you attempt to install NetBackup. For all UNIX platforms except HP-UX,
the binaries are expected to be in /bin or /usr/bin and that directory is a part
of the root user’s PATH variable. On HP-UX systems, the gzip and gunzip
commands are expected to be in /usr/contrib/bin. Installation scripts add
that directory to the PATH variable. These commands must be present to have
successful UNIX installations.

Required operating system patches and updates

for NetBackup
NetBackup server and client installations are only supported on a defined set of
operating systems (OSs) that are listed in the NetBackup Compatibility Lists for All
Versions. Most OS vendors provide patches, updates, and service packs (SPs) for
their products. The best practice of NetBackup Quality Engineering is to test with
the latest SP or update level of the OS when a platform is tested. Therefore,
NetBackup is supported on all vendor GA updates (n.1, n.2, and so on) or SPs
(SP1, SP2, and so on). However, if a known compatibility issue exists on a specific
SP or updated OS level, this information is identified in the compatibility lists. If no
 NetBackup installation requirements 38
NetBackup 10.0.0.1 binary sizes

such compatibility issues are noted, Veritas recommends that you install the latest
OS updates on your servers and clients before you install or upgrade NetBackup.
The most up-to-date required OS patch information for NetBackup 10.0.0.1 and
other NetBackup releases can be found on the Veritas Services and Operational
Readiness Tools (SORT) website and in the NetBackup Compatibility Lists for All
Versions. The compatibility lists include information about the minimum OS level
that is required to support a minimum NetBackup version in the latest major release
line. In some cases, new releases of NetBackup may require specific vendor OS
updates or patches.
See “About NetBackup compatibility lists and information” on page 42.
See “About Veritas Services and Operations Readiness Tools” on page 34.

NetBackup 10.0.0.1 binary sizes

Table B-1 contains the approximate binary sizes of the NetBackup 10.0.0.1 primary
server, media server, and client software for the various supported operating
systems. These binary sizes indicate the amount of disk space occupied by the
product after an initial installation. Note that for the sizes listed in the table, 1 MB
equals 1024 KB.

Note: As of NetBackup 8.3, the Java GUI and JRE packages are optional with most
clients and media servers. The package sizes were calculated with the Java GUI
and JRE included.

Note: Table B-1 and Table B-2 only list the supported operating systems. For
up-to-date information about the specific operating system versions that NetBackup
currently supports, check the Installation and Upgrade Checklist on the Services
and Operations Readiness Tools (SORT) website, or the NetBackup Compatibility
List for all Versions.

Table B-1 NetBackup binary sizes for compatible platforms

OS CPU 64-bit 64-bit Notes

Architecture client server

AIX POWER 1915 MB No longer

supported

Canonical Ubuntu x86-64 1581 MB

CentOS x86-64 1550 MB 8806 MB

 NetBackup installation requirements 39
NetBackup 10.0.0.1 binary sizes

Table B-1 NetBackup binary sizes for compatible platforms (continued)

OS CPU 64-bit 64-bit Notes

Architecture client server

Debian GNU/Linux x86-64 1581 MB

HP-UX IA-64 2428 MB No longer

supported

Oracle Linux x86-64 1581 MB 8806 MB

Red Hat Enterprise Linux POWER 310 MB

Server

Red Hat Enterprise Linux x86-64 1550 MB 8633 MB

Server

Red Hat Enterprise Linux z/Architecture 1084 MB No longer Media server or client compatibility only.
Server supported

Rocky Linux client 1581 MB

Solaris SPARC 1443 MB No longer

supported

Solaris x86-64 1421 MB No longer

supported

SUSE Linux Enterprise Server POWER 314 MB

SUSE Linux Enterprise Server x86-64 1349 MB 7756 MB

SUSE Linux Enterprise Server z/Architecture 1106 MB No longer Media server or client compatibility only.
supported

Windows x86-64 516 MB 3958 MB Covers all compatible Windows x64

platforms.

The following space requirements also apply to some NetBackup installations on

Windows:
■ If you install NetBackup in a custom location on a Windows system, some
portions of the software are installed on the system drive regardless of the
primary application folder location. The space that is required on the system
drive generally accounts for 40 to 50 percent of the total binary size that is listed
in Table B-1.
■ If you install NetBackup server on a Windows cluster, some portions of the
software are installed on the cluster shared disk. Note, the space that is required
 NetBackup installation requirements 40
NetBackup 10.0.0.1 binary sizes

on the cluster shared disk is in addition to the binary size that is listed in
Table B-1. The additional required space is equivalent to 15 to 20 percent of
the total binary size.

NetBackup OpsCenter
Table B-2 contains the approximate binary sizes of the OpsCenter Server and
ViewBuilder for the various operating systems that are compatible with NetBackup
OpsCenter 10.0.0.1.

Table B-2 NetBackup OpsCenter binary sizes for compatible platforms

OS CPU Server ViewBuilder

Architecture

Oracle Linux x86-64 716 MB

Red Hat Enterprise Linux Server x86-64 716 MB

SUSE Linux Enterprise Server x86-64 731 MB

Windows Server x86-64 675 MB 228 MB

 Appendix C
NetBackup compatibility
requirements
This appendix includes the following topics:

■ About compatibility between NetBackup versions

■ About NetBackup compatibility lists and information

■ About NetBackup end-of-life notifications

About compatibility between NetBackup versions

You can run mixed versions of NetBackup between primary servers, media servers,
and clients. This back-level support lets you upgrade NetBackup one server at a
time, which minimizes the effect on overall system performance.
Veritas supports only certain combinations of servers and clients. In mixed version
environments, certain computers must be the highest version. Specifically, the
version order is: OpsCenter server, primary server, media server, and then clients.
For example, the scenario that is shown is supported: 10.0 OpsCenter server > 9.0
primary server > 8.3 media server > 7.7.3 client.
All NetBackup versions are four digits long. The NetBackup 10.0 release is the
10.0.0.0 release. Likewise, the NetBackup 9.1 release is the NetBackup 9.1.0.0
release. For the purposes of supportability, the fourth digit is ignored. A 9.1 primary
server supports a 9.1.0.1 media server. Likewise, a 9.1.0.1 primary supports a 9.1
OpsCenter server. An example of what is not supported is a 9.1 OpsCenter server
with a 10.0 primary server.
The NetBackup catalog resides on the primary server. Therefore, the primary server
is considered to be the client for a catalog backup. If your NetBackup configuration
 NetBackup compatibility requirements 42
About NetBackup compatibility lists and information

includes a media server, it must use the same NetBackup version as the primary
server to perform a catalog backup.
For complete information about compatibility between NetBackup versions, refer
to the Veritas SORT website.
Veritas recommends that you review the End of Support Life information available
online.

About NetBackup compatibility lists and

information
The NetBackup Release Notes document contains a great deal of the compatibility
changes that are made between NetBackup versions. However, the most up-to-date
compatibility information on platforms, peripherals, drives, and libraries can be
found on the Veritas Operations Readiness Tools (SORT) for NetBackup website.
See “About Veritas Services and Operations Readiness Tools” on page 34.
For NetBackup, SORT provides an Installation and Upgrade Checklist report as
well as the ability to collect, analyze, and report on host configurations across your
environments. In addition, you can determine which release contains the hot fixes
or EEBs that you may have installed in your environment. You can use this data to
assess whether your systems are ready to install or upgrade to a given release.

NetBackup compatibility lists

In addition to SORT, Veritas has made available a variety of compatibility lists to
help customers quickly reference up-to-date compatibility information for NetBackup:
NetBackup Compatibility Lists for All Versions

Note: For information about which versions of NetBackup are compatible with each
other, select a Software Compatibility List (SCL), and then select Compatibility
Between NetBackup Versions from within the SCL.

About NetBackup end-of-life notifications

Veritas is committed to providing the best possible data protection experience for
the widest variety of systems: platforms, operating systems, CPU architecture,
databases, applications, and hardware. Veritas continuously reviews NetBackup
system support. This review ensures that the proper balance is made between
maintaining support for existing versions of products, while also introducing new
support for the following:
 NetBackup compatibility requirements 43
About NetBackup end-of-life notifications

■ General availability releases

■ Latest versions of new software and hardware
■ New NetBackup features and functionality
While Veritas continually adds support for new features and systems, it may be
necessary to improve, replace, or remove certain support in NetBackup. These
support actions may affect older and lesser-used features and functionality. The
affected features and functionality may include support for software, OS, databases,
applications, hardware, and 3rd-party product integration. Other affected items may
include the products that are no longer supported or nearing their end-of-support
life with their manufacturer.
Veritas provides advance notification to better help its customers to plan for
upcoming changes to the support status of the various features in NetBackup.
Veritas intends to list older product functionality, features, systems, and the 3rd-party
software products that are no longer supported in the next release of NetBackup.
Veritas makes these support listings available as soon as possible with a minimum
of 6 months where feasible before major releases.

Using SORT
Advance notification of future platform and feature support including end-of-life
(EOL) information is available through a widget on the Veritas Services and
Operations Readiness Tools (SORT) for NetBackup home page. The NetBackup
Future Platform and Feature Plans widget on the SORT for NetBackup home page
can be found directly at the following location:
https://sort.veritas.com/nbufutureplans
NetBackup end-of-support-life (EOSL) information is also available at the following
location:
https://sort.veritas.com/eosl/show_matrix
See “About Veritas Services and Operations Readiness Tools” on page 34.

About changes in platform compatibility

The NetBackup 10.0.0.1 release may contain changes in support for various
systems. In addition to using SORT, you should make sure to review the NetBackup
Release Notes document and the NetBackup compatibility lists before installing or
upgrading NetBackup software.
See “About new enhancements and changes in NetBackup” on page 10.
http://www.netbackup.com/compatibility
 Appendix D
Other NetBackup
documentation and related
documents
This appendix includes the following topics:

■ About related NetBackup documents

About related NetBackup documents

Veritas releases various guides that relate to NetBackup software. Unless otherwise
specified, the NetBackup documents can be downloaded in PDF format or viewed
in HTML format from the NetBackup Documentation Landing Page.
Not all documents are published with each new release of NetBackup. In the guides,
you may see references to other documents that were not published for NetBackup
10.0.0.1. In these cases, refer to the latest available version of the guide.

Note: Veritas assumes no responsibility for the correct installation or use of PDF
reader software.
All references to UNIX also apply to Linux platforms unless otherwise specified.