upgrading to veritas netbackup™ 6.5 from 5.x

Important: Read this first

Upgrading to Veritas NetBackup™ 6.5from NetBackup 5.xMany improvements have been made to the Veritas NetBackup product that make it much more robust to meet the needs of our customers, including several core architecture changes. Because of these changes and the number of new features now offered in NetBackup, Symantec encourages you to upgrade any systems running a pre-6.0 version to the latest version of NetBackup 6.5.

Beginning with NetBackup 6.0, these changes include a new NetBackup catalog format. This new catalog format requires a significant data conversion to occur during the upgrade. As a result, it is important that your existing NetBackup catalog be clean and free of corruption or errors prior to the upgrade and data conversion. We have made available a set of tools designed to help you validate the consistency of your existing catalog before an upgrade is started. This document explains the entire upgrade process and how to utilize these tools. It is critical that you follow the process outlined in this document to help ensure a successful upgrade to NetBackup 6.5.

Purpose of this documentThis document is the primary source for you to review and understand all of the information and tools you will need to make your upgrade from NetBackup 5.x to 6.5 successful. This document will be updated periodically to help keep you informed of any important issues that should be addressed when you upgrade to NetBackup 6.5.

To make sure you understand all of the requirements and to ensure system continuity so that you have a clean environment before you begin the upgrade process, follow the instructions in this document to help avoid the following types of situations:

■ Unavailable media issues

■ Unavailable media servers

■ Potential network problems that could result in long delays in the upgrade process

■ Potential data loss scenarios

To help you understand the necessary steps to achieve a successful upgrade, this document provides the following information:

■ “Getting started” on page 3 describes where you can locate minimum memory and upgrade requirements.

■ “Preparing your NetBackup environment” on page 6 instructs you on how to prepare your back up environment before upgrading.

■ “Upgrading to 6.5” on page 11 contains a high-level procedure that steps you through the upgrade process by directing you to the appropriate upgrade information in existing NetBackup documents.

■ “Phased upgrade” on page 19 describes how to upgrade your media servers in phases if you cannot upgrade all of them when you upgrade the master server.

TechNote 290141 - Revision D

Copyright © 2008 Symantec Corporation. All rights reserved. of 26

VERITAS

■ “Supporting documentation” on page 22 is a list of supporting documentation that includes other important information you need to complete an upgrade.

■ “Upgrade checklist” on page 24 is a checklist to help you track the progress of your upgrade.

This document also contains links to NetBackup documents that are referenced throughout this procedure to help you complete a successful upgrade. You may click on any link within this document and the appropriate book will replace this document in the current Adobe Acrobat browser. If you want to return to this document after reviewing the other book, you can do so by pressing the Alt key and the left arrow key at the same time.

Note: Where necessary, all references to the NetBackup 6.0 Installations Guides are intentional. These guides contain steps that are the same for upgrades to NetBackup 6.5.

NetBackup environment size considerationsData indicate that NetBackup domains that run NetBackup 6.x master servers with NetBackup 5.x media servers and exceed the following limits will have operational problems:

■ Greater than 200 total device connections or

■ Greater than 10 NetBackup 5.x media servers or

■ Greater than four (4) NetBackup 5.x media servers that are Shared Storage Option (SSO) scan hosts

Therefore, if your domain exceeds any one of these limits, it is imperative that you eliminate potential operational problems by upgrading all NetBackup 5.x media servers when you upgrade the master server.

However, if you cannot, you can mitigate operational problems by using a phased approach to upgrade groups of media servers as described in “Phased upgrade” on page 19.

Upgrading from NetBackup 4.5 to 6.5You cannot upgrade your master or media servers directly from NetBackup 4.5 to 6.5. You must first upgrade to a recommended NetBackup 5.x release. See “Upgrading to 6.5” on page 11.

Upgrading from NetBackup 6.0 to 6.5This document does not include upgrade details for NetBackup 6.0 to 6.5. To upgrade from NetBackup 6.0 to 6.5, see the NetBackup 6.5 Installation Guides and the Upgrade Portal for any related updates.

of 26 Copyright © 2008 Symantec Corporation. All rights reserved.

http://entsupport.symantec.com/docs/290185

Chapter 1: Getting started

Before you begin upgrading your system, Symantec recommends that you review and understand information relating to the following areas:

■ “Minimum requirements for NetBackup 6.5.”

■ Memory and disk requirements

■ Supported platforms

■ “Verifying system capacities.”

■ Calculating the size of your NetBackup catalog

■ Calculating the size of your Enterprise Media Manager (EMM) Server

■ “NetBackup compatibility requirements.”

■ Back-level media servers and clients

■ Operating System (OS) and NetBackup patch requirements

■ Product dependency information (Release Notes)

■ Additional upgrade requirements

Minimum requirements for NetBackup 6.5It is important that you understand the memory and disk requirements for NetBackup 6.5. Because you are upgrading from an existing NetBackup 5.x environment, Symantec recommends that you configure your systems to meet the minimum requirements of NetBackup 6.5.x prior to starting the upgrade. For product-specific memory, disk, and binary size requirements refer to the following documents:

■ For minimum memory and disk storage requirements, refer to the NetBackup 6.5 Installation Guides and the Veritas NetBackup 6.5 Release Impact Bulletin.

■ For information about binary size requirements, refer to the Veritas NetBackup 6.5 Release Notes for UNIX, Linux, and Windows.

■ Verify that all of the systems in your environment are running a supported operating system version level for NetBackup 6.5. For information on supported platforms, refer to the Veritas NetBackup 6.x Operating System Compatibility List.

■ Master server host FPPs. Symantec also recommends that the computer that hosts the NetBackup master server (and Enterprise Media Manager (EMM) server, usually the same host) contain floating point processors (FPPs). The Enterprise Media Manager database that was implemented beginning with NetBackup 6.0 performs much more efficiently with an FPP than without.

Verifying system capacitiesWhen evaluating your current backup environment for an upgrade to NetBackup 6.5, there are a few considerations that you will need to address, such as:







VERITAS

■ Calculate the size of your NetBackup catalog

■ Calculate the size of the Enterprise Media Manager (EMM) server

For a detailed description of these considerations and more, refer to the Designing your backup system section in Chapter 1, of the Veritas NetBackup 6.0 Backup Planning and Performance Tuning Guide for UNIX, Windows, and Linux.

■ Verify that the volumes on your disk staging storage unit (DSSU) have more than 1% of available disk space. Upgrades to 6.5.x require that certain files get duplicated. If a DSSU volume has less than 1% of available disk space, errors can occur.

NetBackup compatibility requirementsThere are a few additional compatibility rules that you must remember before you begin. The following list describes these rules.

■ Master Servers, media servers, and other related infrastructure must meet minimum hardware and software requirements. Refer to the online compatibility matrices available at http://go.symantec.com/nbu, and click on “Compatibility List” in the sidebar, or refer to “Supporting documentation” on page 22 for direct links.

■ For master and media servers that you intend to upgrade to NetBackup 6.5.x that are not on the NetBackup 6.5 compatibility matrices, it is necessary to decommission your server and reestablish it on a supported platform. To migrate an existing master server to a new 6.5.x supported platform, refer to the NetBackup 5.x Troubleshooting Guide for UNIX and Windows. If the media server operating system is not supported, refer to “Decommissioning a Media Server” in the NetBackup 5.x Media Manager System Administrator's Guide for UNIX or the NetBackup 5.x Media Manager System Administrator's Guide for Windows.

■ Generate a list of your current devices, tape drives, and device hosts, so that you can validate the information and remove any decommissioned media servers.

■ For UNIX systems, run the following command:

/usr/openv/volmgr/bin/vmglob -listall

■ For Windows systems, run the following command:

<install_path>\Volmgr\bin\vmglob -listall

For detailed information on how to remove a decommissioned media server, refer to “Decommissioning a Media Server” in the NetBackup 5.x Media Manager System Administrator's Guide for UNIX or the NetBackup 5.x Media Manager System Administrator's Guide for Windows.

■ Upgrading 5.x media servers and clients to 6.5.x is an optional step, although it is strongly recommended. NetBackup 5.x media servers are supported in a NetBackup 6.5.x environment. However, clients that are upgraded to NetBackup 6.5.x cannot be backed up to NetBackup 5.x or 6.0 media servers. In addition, 5.x media servers and clients will not be supported in the next major release of NetBackup. Therefore, it is recommended that you update all 5.x media servers and clients to NetBackup 6.5.x to avoid compatibility issues.

■ After you have upgraded all of the master servers, and any media servers that you want upgraded to 6.5, then you are ready to upgrade the NetBackup clients. NetBackup 4.5 clients are not supported in a 6.5.x environment, but they can be directly upgraded to 6.5.

■ Additional upgrade requirements:

■ Operating System patch requirements



http://go.symantec.com/nbu









After ensuring operating system compatibility, NetBackup requires some operating systems to be patched. Refer to the NetBackup 6.5 Release Notes for UNIX, Linux, and Windows for product specific patch dependency information.

■ Product dependency information (Release Notes)

Verify that any third-party products that integrate with NetBackup are compatible with NetBackup 6.5, before you install NetBackup. Refer to the Product Availability Matrix which is available on the Symantec Support website.

■ NetBackup patch requirements

Symantec strongly recommends that you first install the latest available maintenance pack for your 5.x environment before upgrading to NetBackup 6.5GA.

■ Systems that use NetBackup Vault

If you have NetBackup Vault installed, make sure that the robotic volume group names match the names in the vault configuration files.

The robotic volume group name format changed starting with NetBackup 6.0.

NetBackup versions prior to 6.0 use the following robotic volume group name format: twocharacters_threecharacters_robotcontrolmode

NetBackup versions 6.0 and later use the following robotic volume group name format:

threecharacters_fivecharacters_robotcontrolmode

For complete details, refer to TechNote 280696.

For additional compatibility information, refer to the NetBackup 6.5 Release Notes for UNIX, Windows, and Linux.






VERITAS

Chapter 2: Preparing your NetBackup environment

This section contains critical information to help you prepare your NetBackup environment before you begin the upgrade process. Symantec strongly recommends that you review and follow the information outlined in these sections to help ensure a successful upgrade.

Note: Depending on the size of your environment, these steps can take an extended amount of time. Symantec recommends that you schedule these steps well in advance of your upgrade date.

■ “Verifying servers”

■ “Verifying network infrastructure”

■ Hostname/DNS resolution and Routing/Connectivity

■ Network Address Translation (NAT)

■ “Verifying the integrity of NetBackup 5.x catalogs”

■ “Verifying NetBackup 5.x on UNIX clusters”

Verifying servers■ Ensure that the servers list defined on the master server does not contain any media servers that are not valid.

The NetBackup 6.5 installation requires that the nbpushdata command be run after servers are upgraded. This command gathers media and device configuration information from each server. If any invalid server names are listed, it can cause errors during the upgrade.

■ For UNIX systems, verify each SERVER and MEDIA_SERVER entry in the /usr/openv/netbackup/bp.conf file lists a host name that is valid and accessible.

■ For Windows systems, launch the NetBackup Administration Console and go to Host Properties > Master Servers. Open the Properties for the master server and go to the Servers section and verify each host name listed is valid and accessible.

■ To understand how NetBackup 6.5 uses SERVER and MEDIA_SERVER entries, see the following TechNote:


■ Ensure that there are no non-active media servers assigned to any storage units. Review the output of the bpstulist command to make sure all media servers assigned to the storage unit are valid and accessible. Any storage units that are no longer valid must be removed.


/usr/openv/netbackup/bin/admincmd/bpstulist -U


<install_path>\netbackup\bin\admincmd\bpstulist -U


■ Ensure that the device information listed in the vmglob output lists entries that are from valid media servers. Run this command on the master server and compare the output to each media server. Any device information that is no longer valid must be removed.


/usr/openv/volmgr/bin/vmglob -listall


<install_path>\Volmgr\bin\vmglob -listall

■ Ensure that any MM_SERVER_NAME or REQUIRED_INTERFACE entries in the vm.conf file do not specify a cluster name. You must also ensure that any REQUIRED_INTERFACE entries in the bp.conf file (or the registry on Windows) do not specify a cluster name. Refer to TechNote 283712 for complete details.

The nbpushdata command uses these entries to determine a unique name for a host, so specifying a cluster name will cause nbpushdata to fail. Refer to the appropriate chapter in the Veritas NetBackup 6.5 High Availability Guide for the type of cluster that NetBackup has been installed on.

■ For UNIX systems check the following files:

/usr/openv/volmgr/vm.conf

/usr/openv/netbackup/bp.conf

■ For Windows systems check the following files:

<install_path>\Volmgr\vm.conf

Launch the NetBackup Administration console and go to Host Properties > Media Servers. Open the Properties for the media server and go to the Servers section and verify each host name listed is valid and accessible.

■ If you are writing unified logs to a different directory other than the default, you must run the vxlogcfg command to point the logs to the new directory after the upgrade. To check the location before upgrading, edit the nblog.conf file in the NetBackup root directory.

Refer to TechNote 281360 for complete details.

■ When you upgrade NetBackup, the VSP cache settings for the master server are overwritten. If you are using the VSP cache, be sure to check those settings before you start the upgrade and then reset them after the upgrade is finished. Refer to TechNote 294899 for complete details.

Verifying network infrastructure■ Ensure that there are no CLIENT_PORT_WINDOW and SERVER _PORT_WINDOW entries defined in the

bp.conf file or in the registry that would restrict the number of available non-reserved ports to NetBackup. NetBackup 6.5.x uses non-reserved ports by default.

■ If you have multiple NICs on a NetBackup host, it is important to understand how network interfaces are selected on the NetBackup 6.x platform. Refer to TechNote 293038.

■ Hostname/DNS resolution and Routing/Connectivity

■ Ensure that there are no connectivity issues between the master servers and media servers. Run AppareNet or an equivalent network diagnostic tool between the master server and each media sever to verify connectivity.

Note: If AppareNet is used, it is recommended that this step be done with help from Symantec Enterprise Technical Services. The AppareNet software can be downloaded from the following URL: http://www.apparentnetworks.com/sas/300/



http://www.apparentnetworks.com/sas/300/




VERITAS

■ To prevent any Domain Name Service (DNS) issues during the upgrade process, it is recommended to place a host file on the master server and on every media server that contains the fully qualified domain name, short name, and IP address of every media server and the master server.

■ Network Address Translation (NAT)

■ Determine if any media servers are separated from the master server by a firewall. If so, ensure that these media servers are not running NAT. NAT causes problems with the PBX connections between NetBackup servers and can cause connectivity issues during or after the upgrade.

■ An additional port has been added for PBX communication over the TCP port 1556. Any firewall rules should be updated to allow traffic through this port.

■ NetBackup does not support Port Address Translation (PAT) or Dynamic Address Translation.

■ Check to see if Veritas Security Services (VxSS) is installed. This software may need to be upgraded as well.

Note: Beginning with NetBackup 6.5, Veritas Security Services and its associated acronym (VxSS) are replaced by Symantec Product Authentication and Authorization.

■ Check to see if the Shared Storage Option (SSO) will be used for drive sharing between NetBackup 6.x and NetBackup 5.x media servers. It is important to note that in NetBackup 6.x, the EMM server is responsible for granting a SSO resource. In NetBackup 5.x, the media server itself is responsible for SSO tape drive selection. This can lead to slower drive selection performance in larger environments. Refer to “Phased upgrade” on page 19 and TechNote 282271.

■ During the upgrade, all valid NetBackup Master and Media servers must be online.

■ For clustered systems, ensure that your cluster is configured correctly before you upgrade to 6.5. For complete details, refer to TechNote 285699: Checklist and general information for upgrading a clustered environment from NetBackup 5.x to NetBackup 6.x.

■ The CLIENT_NAME entry in each host’s bp.conf file or registry should match its respective host name. NetBackup uses a string compare to resolve host names prior to using DNS to resolve host name.

For media servers, the client name must match the SERVER= or the MEDIA_SERVER= entry on the media server. Otherwise, some services on the media server will not start.

Verifying the integrity of NetBackup 5.x catalogsEnsure that there are no image, media, or volume database inconsistencies. To do so, install and run the NetBackup Catalog Check (NBCC) utility. The NetBackup Catalog Check (NBCC) utility gathers and inspects NetBackup catalog database information. It helps to verify the integrity of the NetBackup 5.x Media and Image Catalogs.

To install and run NBCC

1 Obtain the latest NetBackup Catalog Checker (NBCC) Utility from Symantec at the following URL:http://entsupport.symantec.com/docs/306883

2 Follow the instructions in the README file to install NBCC on the master server.

3 Ensure that no NetBackup activity is occurring.

4 Run the NBCC utility as follows::nbcc -full

5 The following prompt appears:





If NBCC DOES NOT detect any catalog inconsistencies, would you like NBCC to create a support package? [Y/y,N/n]

6 Answer yes by pressing y.

7 The following series of prompts may appear; guidance is included:2.0 Gathering required NetBackup configuration information

Is the master server or any media server in a fail-over cluster? [Y/y,N/n]

Answer as appropriate for your environment.Would you like NBCC to update theC:\Program Files\Veritas\NetBackup\bin\support\config\nbcc-server-aliasfile with additional hostnames and/or IP addresses that are detectedduring processing? [Y/y,N/n]

Answer yes.Would you like to verify each addition prior to the update?[Y/y,N/n]

Verifying each media server may be time consuming in a large environment with many media servers. If you answer no, you can verify the entries in the “Summary of NBCC server processing” section of the nbcc-info.txt file that NBCC produces.

If NBCC is unable to determine the NetBackup version forANY detected media server, is there a SINGLE version of NetBackupthat you would like associated to these media servers? [Y/y,N/n]

If all of your media servers are not at the same major release level (such as 5.x), answer no. If all of your media servers are at the same major release level, answer yes and then enter the release level at the next prompt.

Please enter the NetBackup primary version number [3,4,5,6]

Enter the release level of your media servers.

8 When the NBCC utility completes running, run the following command and verify that no errors occur:bpexpdate -deassignempty

If errors occur, a server may be unreachable or zero-byte files may exist. For assistance with correcting the errors, contact Symantec Enterprise Technical Services.

Warning: Repair any inconsistencies discovered with NBCC before continuing with your upgrade. Failure to complete this step may result in a failed upgrade. Repairing inconsistencies must be done with help from Symantec Enterprise Technical Services. This can be a time-consuming process; however, it is strongly recommended that you perform this prior to attempting an upgrade.

The time needed to analyze the NetBackup Catalog Check output and fix any inconsistencies cannot be predicted. Therefore, Symantec recommends that you wait until you are finished working with Symantec Support before scheduling the upgrade.

Verifying NetBackup 5.x on UNIX clustersBefore you upgrade 5.x UNIX clusters, check your current configuration for either of the following:

■ Any server that uses a fully qualified domain name (FQDN)

■ Any server name that is specified differently in the bp.conf and <cluster_name>_NBU_RSP files


VERITAS

If either one of these conditions exist, it is imperative that you follow the instructions documented in the following TechAlert before you start your upgrade:

TechAlert 293034



Chapter 3: Upgrading to 6.5

The following describes a summary of the sequence of recommended steps to ensure a successful upgrade to NetBackup 6.5:

a Before you begin the upgrade process, install the following for the currently installed NetBackup 5.x versions (or more recent MP, if available):

■ For 5.0 systems, Symantec requires that you install 5.0MP4 or later.

■ For 5.1 systems, Symantec strongly recommends that you install 5.1MP5 or later.

b Upgrade all master servers and media servers to the latest NetBackup 6.5.x release.

If you cannot upgrade all of your media servers when you upgrade your master server, Symantec recommends that those not being upgraded to 6.5.x at the same time as the master server should be upgraded to 5.1MP7. See “Phased upgrade” on page 19.

c Run the nbpushdata -preview [-timeout n] command to simulate host connectivity to media servers.

Review the log output generated by the command to identify any problematic servers. Resolve any problems before proceeding to step d.

d Run the nbpushdata command after you have upgraded all master servers and selected media servers.

Best practicesThe following sequence highlights the order in which you should install NetBackup software when upgrading from one version of NetBackup to another.

a Master server

b Media servers

c NetBackup Remote Administration consoles

(If supporting older releases, refer to the NetBackup 6.5 Administrator’s Guides for information on how to implement multiple versions.)

d NetBackup clients - After you have successfully upgraded your master servers and media servers to NetBackup 6.5, you can then upgrade your clients to NetBackup 6.5.

e Any NetBackup add-on products. The following should be considered for each add-on product:

■ When upgrading the Veritas Storage Migrator (VSM) product, you must upgrade incrementally to each major and minor release to upgrade to 6.5. For example, systems running VSM 4.5 must first upgrade to 5.0, then next to 5.1, then next to 6.0, and finally to 6.5. You cannot skip a version when upgrading VSM.

■ When upgrading NetBackup Vault, you can upgrade to the same version levels as is suggested for NetBackup.

■ When upgrading NetBackup Advanced Reporter, refer to TechNote 281578, “How to preserve NetBackup Advanced Reporter (NBAR) data before upgrading to NetBackup 6.x” for a better understanding of what you should do before you finish your upgrade to NetBackup 6.5.




VERITAS

f Install the latest available patches for all applicable add-on products, agents, and options.

Symantec PBXNetBackup versions 6.0 and later require Symantec Private Branch Exchange (PBX) to operate. NetBackup versions earlier than 6.0 did not require PBX. However, you may have other Veritas or Symantec products installed in your current NetBackup 5.x environment that require this software.

Windows systemsRegardless of whether PBX already exists in your current NetBackup 5.x environment, the upgrade to NetBackup 6.5.x installs or upgrades PBX automatically.

UNIX systemsIf PBX is not installed in your current NetBackup 5.x environment, the upgrade to NetBackup 6.5.x automatically prompts you to install PBX during the upgrade.

If PBX already exists in your current NetBackup 5.x environment, you may need to upgrade it before you upgrade to NetBackup 6.5.

■ Check the installed PBX version by entering the following:

cat /opt/VRTSpbx/build_version

Take the appropriate action as follows:

■ For versions 1.2.x - 1.3.24.x, you must first upgrade PBX from the NetBackup 6.5 ICS CD or DVD before you upgrade to NetBackup 6.5.

■ For versions 1.3.25.x or later, no PBX upgrade is required.

Upgrading servers from NetBackup 5.x to NetBackup 6.5After you have successfully prepared your NetBackup environment as outlined earlier in “Preparing your NetBackup environment” on page 6, you are ready to upgrade. The following steps guide you through this process.

1 Perform a full backup of all NetBackup master servers and media servers (NetBackup databases, patches, scripts, and other NetBackup data). Additionally, perform the following:

■ Make a copy of the current Barcode rules.

2 Prevent new jobs from starting by deactivating the NetBackup request daemon.

■ On UNIX systems, run the following command:

/usr/openv/netbackup/bin/admincmd/bprdreq -terminate

■ On Windows systems, run the following command:

<install_path>\netbackup\bin\admincmd\bprdreq -terminate

3 Wait for any current jobs to complete. If you cannot wait, you may cancel all jobs on your master server. A backup that is running during an upgrade is not desirable and could result in a failed upgrade.

■ On UNIX systems, run the following command:

/usr/openv/netbackup/bin/admincmd/bpdbjobs -cancel_all

■ On Windows systems, run the following command:


<install_path>\netbackup\bin\admincmd\bpdbjobs -cancel_all

4 Stop all third party scripts or other custom scripts.

5 Perform a catalog backup and verify that every media server in the configuration is listed in the catalog backup files list.

Note: Symantec recommends that you perform these backups onto removable media and then physically remove the media to a secure location.

6 For clustered systems, do the following:

■ MSCS clusters: Before you upgrade, you must shut down all NetBackup services. Be sure to keep the IP Address, Network Name, and the disk resource online.

■ Windows VCS clusters: Before you upgrade, you must take all NetBackup services offline. Be sure to keep the Lanman, IP, NIC, and disk resources online. Freeze the NetBackup Group so that migrations do not occur while the inactive nodes are upgraded. You can freeze the NetBackup Group by using the Cluster Manager interface or the command line.

■ UNIX VCS clusters: Before you upgrade, you must freeze the NetBackup Group so that migrations do not occur while the nodes are upgraded. The disk resources, virtual name and IP address should remain online.

■ Sun Cluster: Before you upgrade, you must freeze the NetBackup resource so that migrations do not occur while the nodes are upgraded. The procedure for accomplishing this, which is different from that found in the 6.5 NetBackup High Availability guide, is as follows:

■ Log on to one of the cluster nodes as root and run the following commands:

# scrgadm -c -j scnb-hars -y Retry_count=0

# scswitch -n -j scnb-hars

# scswitch -e -j scnb-hars

# scswitch -M -n -j scnb-hars

■ Tru64 Truclusters: Before you upgrade, you must take the NetBackup resource offline so that migrations do not occur while the nodes are upgraded. The NetBackup virtual name should remain online.

7 Install the NetBackup 6.5.x software on the master server and on the media servers that you can upgrade to 6.5.x.

Caution: To install the 6.5.x software, you will be directed to follow specific steps in a specific section of the NetBackup 6.0 Installation Guides. It is important that you perform only those steps in the referenced sections.

■ On UNIX systems:

Perform steps 4 - 14 as described in the section “Upgrading NetBackup Server Software” in “Chapter 3” of the NetBackup 6.0 Installation Guide for UNIX and Linux.

Note: If you have not yet installed PBX, or have not verified the currently installed version, please do so now. Refer to ““Symantec PBX” on page 12.

■ On Windows systems:

Start at step 3 in the appropriate NetBackup server installation or upgrade procedure as described in the section “Installing or Upgrading NetBackup” in “Chapter 2” of the NetBackup 6.0 Installation Guide for Windows.


VERITAS

Caution: Do not run nbpushdata to populate the EMM database at this time.

Caution: For clusters, do not run the clusterconfig command during an upgrade.


■ MSCS clusters: The NetBackup resources come back online automatically. If the NetBackup Group is still offline, bring it back online.

■ Windows VCS clusters: Unfreeze the active node.

■ UNIX VCS clusters: Leave the NetBackup groups and resources frozen during the upgrade.

Caution: Do not start any backups at this time. Your NetBackup environment is not ready to perform backup operations until after you have completed all the steps and procedures in this document.

9 Verify that NetBackup policies are still deactivated. You can do this using the Administrator’s Console.

10 If the NetBackup storage units defined with a virtual name other than the NetBackup virtual name as described in TechNote 276122. With NetBackup 6.0 and above, this is known as an app_cluster. The app_cluster name must be created for each virtual application name (excluding the NetBackup virtual name).

■ Note first the path to the nbemmcmd utility:

For UNIX systems: /usr/openv/netbackup/bin/admincmd

For Windows systems: <install_path>\veritas\netbackup\bin\admincmd

■ On the master server, run the following commands for each app_cluster defined:

nbemmcmd -addhost

-machinename <appcluster_name>

-machinetype app_cluster

-netbackupversion 6.5

■ For each media server in the app_cluster, run the following commands:

nbemmcmd -updatehost

-add_server_to_app_cluster

-machinename <media_server_name>

-machinetype media

-clustername <appcluster_name>


■ Finally, if the master server is also eligible to host the app_cluster storage unit, run the following commands:

nbemmcmd -updatehost

-add_server_to_app_cluster

-machinename <master_server_name>

-machinetype master

-clustername <appcluster_name>


11 This step applies only to Windows systems with media server names that begin with an underscore (e.g. _mediaserverA). You must complete this step before you run the nbpushdata command.


a Open a command prompt and navigate to <install_path>\veritas\netbackup\bin\admincmd and issue the following command:

nbemmcmd -changesetting -machinename emmservername -validate_host_name no

The emmservername is the name of the master or media server where the EMM resides.

b Stop and then restart all of the NetBackup services or daemons on the master server.

c Open a command prompt and navigate to <install_path>\veritas\netbackup\bin\admincmd and issue the following command:

nbemmcmd -listsettings -machinename emmservername

The emmservername is the name of the master or media server where the EMM resides.

d In the output that appears, ensure that the validate_host_name value is no.

For example:

<install_path>\netbackup\bin\admincmd>nbemmcmd -listsettings

-machiname emmservername

NBEMMCMD, Version:6.5GA

The following configuration settings were found:

ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA="yes"

DISABLE_DISK_STU_JOB_THROTTLING="no"

DISABLE_STANDALONE_DRIVE_EXTENSIONS="no"

MEDIA_REQUEST_DELAY="0"

MUST_USE_LOCAL_DRIVE="no"

NON_ROBOTIC_MEDIA_ID_PREFIX="A"

MAX_REALLOC_TRIES="1000"

DISALLOW_NONNDMP_ON_NDMP_DRIVE="no"

DO_NOT_EJECT_STANDALONE="yes"

DONT_USE_SLAVE="no"

DRIVE_ERROR_THRESHOLD="2"

MEDIA_ERROR_THRESHOLD="2"

TIME_WINDOW="12"

RETURN_UNASSIGNED_MEDIA_TO_SCRATCH_POOL="yes"

VAULT_CLEAR_MEDIA_DESC="no"

VALIDATE_HOST_NAME="no"

Command completed successfully.

12 Verify that all NetBackup services are running. Refer to page 21 in the Veritas NetBackup 6.5 Troubleshooting Guide for UNIX and Windows.

13 Suspend NetBackup resource allocations. You must perform this step before you run nbpushdata.

■ On UNIX systems, enter:

/usr/openv/netbackup/bin/admincmd/nbrbutil -suspend

■ On Windows systems, enter:

<install_path>\netbackup\bin\admincmd\nbrbutil -suspend

14 If performing a phased upgrade: For each NetBackup media server that remains at 5.1MP7 and that shares drives (the Shared Storage Option (SSO)), stop ltid on it.

■ On UNIX systems, enter:

<install path>/volmgr/bin/stopltid




VERITAS

■ On Windows systems, enter:

<install path>\Volmgr\bin\stopltid

15 If performing a phased upgrade:For each NetBackup media server that remains at 5.1MP7 and that shares drives (the Shared Storage Option (SSO)), add the following entry to its vm.conf file:SSO_SCAN_ABILITY = 0

This is part of the process to configure NetBackup 5.x media servers so they are not scan hosts; step 20 completes the process. For more information, see “Scan hosts for NetBackup 5.1 media servers that share drives” on page 20.

16 Delete all files in the <install_path>/netbackup/remote_versions directory on the NetBackup master server and all NetBackup media servers.

17 For clustered systems, freeze the NetBackup group by doing the following:

■ MSCS clusters: Since there is no freeze capability, ensure that no failovers occur.

■ Windows VCS clusters: Freeze the NetBackup Group so that failovers do not occur.

■ Unix clusters: These clusters should already be in a frozen state at this point.

Note: If you want to simulate the pushdata commands described in Step 17, add the flag -preview to the nbpushdata command. Simulating the command tests the network connectivity to affected media servers and logs output to the pushdata log.

18 Run the nbpushdata command.

This command moves data from your current database files (a subset of the NetBackup catalog) into a newly created EMM database. The sequence of when and on what systems you run the nbpushdata command is extremely important. For more information on running nbpushdata and creating the EMM database after you upgrade servers, refer to “Populating the NetBackup EMM Database” in the NetBackup 6.0 Installation Guides.

The following list provides the order in which you must run the nbpushdata command in your environment.

a 5.x Global Device Database Host - Run nbpushdata -add on the 5.x server that was configured as the Global Device Database Host. This is usually a master server, but a media server as the Global Device Database Host is also a supported configuration.

b Master servers - There is no particular order in which you must run nbpushdata -add on your master servers after you have run it on the server that was configured as the Global Device Database Host.

c Volume Database Hosts - You must next run nbpushdata -add on the server designated as a Volume Database Host. If the Volume Database Host was also the Global Device Database Host or a master server, this step does not apply.

d Media Servers - Any remaining media servers that have not been upgraded to NetBackup 6.5.x media servers can be upgraded at a later time.

If you are leaving any media servers at NetBackup 5.x, you must log in to the master server(s) that administers to those back-level media servers and run nbpushdata -modify_5x_hosts.

■ For UNIX systems, see “To configure 5.x media servers for compatibility with 6.0 environments,” on page 60 in the Veritas NetBackup 6.0 Installation Guide for UNIX and Linux for detailed instructions.

■ For Windows systems, see “To configure 5.x media servers for compatibility with 6.0 environments,” on page 100 in the NetBackup 6.0 Installation Guide for Windows for detailed instructions.

For a list of the 5.x database files that are moved to the EMM database, refer to page 11 in theVeritas NetBackup 6.0 Installation Guide for UNIX and Linux or page 9 in the NetBackup 6.0 Installation Guide for Windows.








Note: If you are concerned that your current installation of NetBackup may be corrupt, contact Symantec Enterprise Technical Services for assistance.


■ MSCS clusters: The NetBackup resources comes back online automatically. If the NetBackup Group is offline, bring it back online.

■ Windows VCS clusters: Unfreeze the NetBackup Group and bring the NetBackup resource online.

■ UNIX VCS clusters: Unfreeze the NetBackup Group and bring the NetBackup resource online.

■ Sun clusters: Re-enable NetBackup resource monitoring as follows:

scswitch -M -e -j scnb-hars

Note: For NetBackup 6.5GA, it is recommended that the pmf retry count be left at 0.

■ Tru64 Truclusters: NetBackup must first be shut down and then restarted under Trucluster control as follows:

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

# /usr/sbin/caa_start <netbackup profile name>

20 If performing a phased upgrade: For each NetBackup media server that remains at 5.1MP7 and that shares drives (the NetBackup Shared Storage Option (SSO)), invoke the following command on the master server:nbemmcmd -updatehost -scanability 0 -machinetype media -masterserver master_name -machinename media_name

Replace master_name with the name of the master server and media_name with the name of the 5.1 media server.

This completes the process to configure them so they are not scan hosts. For more information, see “Scan hosts for NetBackup 5.1 media servers that share drives” on page 20.

Note: When you upgrade these servers in the future, be sure to use the nbemmcmd to set their scanability factors to 5 (the default). If you do not do so, the servers will not function as scan hosts.

21 Upgrade the clients in your environment. Refer to, “Upgrading Clients After Servers Are Upgraded” in Chapter 3 of the NetBackup 6.0 Installation Guides.

Note: Clients that are upgraded to 6.5.x cannot be backed up using 5.x media servers.

22 Stop and then restart NetBackup services. Although the system devices now reside in the EMM database, the devices are not recognized until NetBackup services are stopped and restarted.

■ For VCS and clustered systems, stop and restart NetBackup services as follows:

■ Stop NetBackup services.

■ Run the following command to update the ASA server name:

On UNIX systems:

/usr/openv/db/bin/nbdb_admin -vxdbms_nb_server emmservername

On Windows systems:

<install_path>\netbackup\bin\nbdb_admin -vxdbms_nb_server emmservername

■ Restart NetBackup services.


VERITAS

23 Symantec recommends that you perform another catalog backup at this time.

Note: With NetBackup 6.5, cold catalog backups will shut down the EMM database as any normal cold database application allowing no connections until the backup process completes. It is recommended that you use the HOT catalog backup option.

24 You may now upgrade any NetBackup agents and options.

After your upgrade is complete, you can install any other NetBackup agents and options (such as NetBackup for Oracle) by following the instructions in the NetBackup guide that comes with that particular product. This documentation is also available online at http://entsupport.symantec.com.

25 Install the latest available patches for all applicable add-on products, agents, and options.

26 Reactivate all policies.

After upgrading■ If you have application clusters running in your NetBackup environment, the performance could be affected. To

address any performance issues related to application clusters, refer to TechNote 285451.

■ Remember that if you are writing unified logs to a different directory other than the default, you must run the vxlogcfg command to point the logs to the new directory after the upgrade.


■ Remember that when you upgrade NetBackup, the VSP cache settings for the master server are overwritten. If you are using the VSP cache, you must reset the settings after the upgrade is finished.

■ Do not perform device discovery on NetBackup 5.1 media servers. Discovery operations may consume so much time that the Device Configuration Wizard times out before discovery completes. If you must add devices to NetBackup 5.1 media servers, do so manually. To add devices, you can use:

■ The NetBackup Administration Console. See "Adding a robot" and "Adding or changing a drive" in the following:

■ NetBackup Administrator's Guide for UNIX and Linux, Volume I

■ NetBackup Administrator's Guide for Windows, Volume I

■ The tpconfig command. See:

■ NetBackup Commands for UNIX and Linux

■ NetBackup Commands for Windows



http://entsupport.symantec.com/


Appendix A: Phased upgrade

Symantec strongly recommends that you upgrade all NetBackup 5.x media servers when you upgrade your master server. However, if you cannot, you can use a phased upgrade approach, upgrading groups of media servers as described in this appendix.

Before you begin the upgrade, please refer to “NetBackup environment size considerations” on page 2.

To ensure successful operation in a mixed release level environment, use the releases described in “Phased upgrade recommendations” on page 19 during the phased upgrade. Those release levels greatly increase the likelihood that you can run a mixed release level environment.

Shared drivesIf you use shared drives (NetBackup Shared Storage Option), map out all of the relationships between media servers, shared drives, and device paths so you can determine your share groups. (A share group is a group of media servers and the drives they share.)

When you upgrade, Symantec recommends that you upgrade media servers in groups based on specific criteria, one such criteria being media servers that share the same drives.

See “Media server upgrade groupings” on page 20.

Phased upgrade recommendationsPhased upgrade means that you do the following:

■ First, upgrade the following NetBackup servers at the same time, as follows:

To NetBackup 6.5.2 or later ■ The master server.

NetBackup 6.5.2 and later includes code that improves operations in mixed release level environments.

If your master server is at NetBackup 6.0 already, you can apply 6.0MP7 to the master server rather than upgrade it to the 6.5.2 or later release.

■ Media servers that share drives.

If you cannot upgrade all of the media servers in a share group at the same time you upgrade your master server, upgrade at least two of them to the same level as the master server to function as the scan hosts for the share group.

For more information, see “Scan hosts for NetBackup 5.1 media servers that share drives” on page 20.

■ Other media servers that you can upgrade when you upgrade the master server.

Symantec recommends that you upgrade as many media servers as you can when you upgrade the master server. To choose media servers to upgrade, see “Media server upgrade groupings” on page 20.


VERITAS

■ Then, for the media servers than were not upgraded when you upgraded the master server, upgrade them in groups to the same release level as your master server as described in “Media server upgrade groupings” on page 20.

Upgrading in phases based on media server groups reduces the potential for problems and greatly increases the likelihood that you can run a mixed server level environment.

Media server upgrade groupingsSymantec recommends that you upgrade groups of 5.1 media servers in the following order, to the same release level as the master server:

■ First, upgrade the media servers that run the most jobs.

■ Second, if you have shared drives, upgrade the 5.1MP7 media servers that were not upgraded when you upgraded the master server.

If you have more than one share group, upgrade the share groups in order from most shared drives and device paths to fewest.

■ Third, upgrade the remaining media servers in phases until all are upgraded.

Scan hosts for NetBackup 5.1 media servers that share drivesNo more than four NetBackup 5.1 media servers should be scan hosts in a NetBackup 6.x master server environment that has shared drives (the NetBackup Shared Storage Option allows shared drives). If there are more than four, performance will be negatively affected.

Note: For performance reasons, Symantec recommends that scan hosts should be the same release level as the master server.

For a media server share group in which all of the media servers cannot be upgraded at the same time you upgrade your master server, do the following:

■ Upgrade at least two of them to the same release level as the master server. NetBackup assigns the default scanability factor to them.

If the scan hosts become unavailable, the shared drives will be unavailable for use until a scan host becomes available again. Upgrading at least two media servers in a share group provides some redundancy.

■ Configure the 5.1MP7 media servers in the share group so they are not scan hosts. You then can upgrade these 5.1MP7 media servers at some future time.

Audit media servers to determine the scan host candidatesAudit your 5.x media servers to determine which ones you should upgrade so they can function as scan hosts.

1 Determine the drive-to-host connections by running the following NetBackup command:

UNIX: /usr/openv/volmgr/bin/vmglob -listall -b

To NetBackup 5.1MP7 ■ All of the remaining media servers.

NetBackup 5.1MP7 includes code that improves operations in mixed release level environments.


Windows: install_path\Volmgr\bin\vmglob.exe -listall -b

You can run the command on the master server or any media server.

2 Sort the vmglob command output by drive name.

3 For every shared drive, choose at least two hosts to function as scan hosts.

If more than two exist, choose the hosts with the most media in the media DB. Determine the number of media by running the following command for each host and comparing the number of ACTIVE media each host has:

UNIX: /usr/openv/netbackup/bin/admincmd/bpmedialist -summary -brief -h hostname

Windows: install_path\netbackup\bin\admincmd\bpmedialist.exe -summary -brief -h hostname

You can run the command on the master server or any media server.

4 Upgade the chosen media servers to the same release level as the master server.

When the servers are upgraded, NetBackup assigns the default scanability factor to them.

5 For the remaining media servers that are not upgraded, disable their scan host duties as described in the next section.

Remove a media server from scan host dutiesYou must do two things to configure a 5.1 media server so it is not a scan host, as follows:

■ Add the following entry to its vm.conf file:

SSO_SCAN_ABILITY = 0

This is included as Step 15 on page 16 in the procedure “Upgrading servers from NetBackup 5.x to NetBackup 6.5.”

■ Invoke the following command on the master server:

nbemmcmd -updatehost -scanability 0 -machinetype media -masterserver master_name -machinename media_name


This is included as Step 20 on page 17 in the procedure “Upgrading servers from NetBackup 5.x to NetBackup 6.5.”

Configure a media server as a scan hostWhen you upgrade the 5.1 media servers in the future, be sure to set their scanability factors to 5 (the default). If you do not, the servers will not function as scan hosts.

For each media server, do the following:

1 Remove the following entry from its vm.conf file:

SSO_SCAN_ABILITY = 0

2 Invoke the following command on the master server:

nbemmcmd -updatehost -scanability 5 -machinetype media -masterserver master_name -machinename media_name



VERITAS

Appendix B: Supporting documentation

The following list identifies the NetBackup documents that you may need to reference before and during your upgrade.

NetBackup Product Documentation■ Veritas NetBackup 6.0 Installation Guide for UNIX and Linux

■ Veritas NetBackup 6.0 Installation Guide for Windows

■ Veritas NetBackup 6.5 Installation Guide for UNIX and Linux

■ Veritas NetBackup 6.5 Installation Guide for Windows

■ Veritas NetBackup 6.5 Release Notes for UNIX, Linux, and Windows

■ Veritas NetBackup 6.5 Administrator’s Guide for UNIX and Linux, Volume I

■ Veritas NetBackup 6.5 Administrator’s Guide for UNIX and Linux, Volume II

■ Veritas NetBackup 6.5 Administrator’s Guide for Windows, Volume I

■ Veritas NetBackup 6.5 Administrator’s Guide for Windows, Volume II

■ Veritas NetBackup 6.5 Troubleshooting Guide for UNIX and Windows

Other NetBackup Documentation■ Veritas NetBackup 6.5 Release Impact Bulletin

■ Veritas NetBackup Enterprise Server and NetBackup Server 6.x Hardware Compatibility List

■ Veritas NetBackup Enterprise Server 6.x / NetBackup Server 6.x Database Agent Compatibility

■ Veritas NetBackup Enterprise Server 6.x / NetBackup Server 6.x Cluster Compatibility

■ Veritas NetBackup Network Data Management Protocol (NDMP) Compatibility List

■ TechNote 278064 Veritas NetBackup 6.x Operating System Compatibility List

■ TechNote 283712 The nbpushdata command can fail if the REQUIRED_INTERFACE entry exists in the vm.conf file on a clustered NetBackup server

■ TechNote 282271 Attempting to share Shared Storage Option drives among both Veritas NetBackup 5.x and 6.x servers generates errors in the EMM database and can down the drives

■ TechNote 281578 How to preserve NetBackup Advanced Reporter (NBAR) data before upgrading to NetBackup 6.x

■ TechNote 285451 How to configure NetBackup 5.x Non-Failover Media servers with virtual storage unit in EMM after upgrading them to NetBackup 6.x
























■ TechNote 285699 Checklist and general information for upgrading a clustered environment from NetBackup 5.x to NetBackup 6.x

■ TechNote 280696 Default format of robotic volume group names has changed in Veritas NetBackup 6.x

■ TechNote 281360 Best Practice recommendations for enabling and gathering Veritas NetBackup 6.x logging

■ TechAlert 293034 Potential data loss issue in cluster_upgrade that affects installations in field using FQDNs and clusters







VERITAS

Appendix C: Upgrade checklist

This checklist is provided only as a quick check and reference for starting your upgrade to NetBackup 6.5. This checklist should not be used by itself to attempt an upgrade. Use the checklist as you follow the instructions provided in this document to help track the progress of your upgrade.

❏ Copy off the bp.conf and vm.conf files from all the NetBackup servers for comparison. Verify that all the servers listed are active media servers.

■ If multiple NICs are being used by the NetBackup servers, make sure only those assigned to storage units are defined as SERVER= entries in the bp.conf file.

❏ Check for use of REQUIRE_INTERFACE in the vm.conf file.

❏ Review the outputs from /usr/openv/netbackup/bin/admincmd/bpstulist -U to verify all of the servers assigned to storage units are active and on line.

❏ Review the output from /usr/openv/volmgr/bin/vmglob -listall to verify all of the servers listed are active and on line.

❏ Check the bp.conf file for the following entries that could cause problems with the upgrade:

■ CLIENT_PORT_WINDOW and SERVER_PORT_WINDOW not using the defaults

❏ Verify that all hostnames and IP addresses can be resolved by NetBackup using the bpclntcmd commands. Run bpclntcmd -self, bpclntcmd -hn, and bpclntcmd -ip on each NetBackup server against the master server from the media servers and against each media server from the master server.

❏ Verify VxSS is not being used and that there are no firewalls between the NetBackup servers.

❏ Check to see if any NetBackup server is in a cluster.

❏ Check that the CLIENT_NAME entry in each host's bp.conf file or registry matches its respective host name.

❏ Verify that all of the OS's are patched and fall within the compatibility guide:

Veritas NetBackup 6.x Operating System Compatibility List (http://library.veritas.com/docs/278064)

NetBackup 6.5 Release Notes for UNIX, Linux, and Windows (http://library.veritas.com/docs/290196)

❏ Make sure there are no NBDB.db files still in /usr/openv/db on the master server from the last attempt at upgrading.

❏ Verify if the library is ACLS and Windows media servers have the latest version of libattach 1.4 installed.

❏ Make sure you can disable anti-virus scanning on the Windows server during the upgrade.

❏ Make sure that Windows NetBackup servers do not have a Temp file with no extensions already in c:/

❏ Make sure the Windows media servers do not have a “_” before the hostname.

❏ Make sure any current jobs or third party schedulers are disabled during the upgrade.

❏ If possible, run the SAS against each of the media servers from the master to ensure the network links are clean:


❏ Copy off the output from tpconfig -d from each media server and the master server to a text file.

❏ Copy off the output from bppllist -allpolicies -U on the master server to a text file.



http://library.veritas.com/docs/278064


❏ Verify all clients and servers are at 5.x (any MP) or higher.

❏ Verify that there is root or administrator access to all Master Servers, Media Servers, clients running Database options (necessary for the duration of the upgrade).

❏ If using DSSUs, verify that the volumes on your disk staging storage unit (DSSU) have more than 1% of available disk space. Upgrades to 6.5.x require that certain files get duplicated. If a DSSU volume has less than 1% of available disk space, errors can occur.

❏ If you have NetBackup Vault installed, you must change the robotic volume group names to work with NetBackup 6.5.

■ NetBackup versions prior to 6.0 use the following robotic volume group name format: twocharacters_threecharacters_robotcontrolmode

■ NetBackup versions 6.0 and later use the following robotic volume group name format: threecharacters_fivecharacters_robotcontrolmode

❏ Run vmoprcmd -h against each media server from the master server to verify they can connect to vmd.

❏ Run bpexpdate -deassignempty to ensure there are no “0” byte length header files in the database.

❏ Just before running nbpushdata -modify_5x_hosts for legacy SSO media servers, stop ltid on any legacy 5.x media servers:

<install path>/volmgr/bin/stopltid

(Skip this if you are upgrading your media servers at the same time, which would be best practice.)

❏ The preferred catalog backup method for NetBackup 6.5.x servers is to use hot catalog backups. Delete the old paths to the media servers in the offline/cold catalog backup configuration.

❏ Prior to upgrading to NetBackup 6.5.x (before you run nbpushdata), delete all files in the remote_versions directory (<install_path>/NetBackup/remote_versions) on the NetBackup master and all NetBackup media servers.

❏ For Solaris and other UNIX systems, the NetBackup package removal process may fail during the upgrade if the following file is present:

<install path>/netbackup/bin/driver/snapctl10_x

This file is a Solaris 10 Advance Client driver that can be safely deleted, so that the package removal can continue.

❏ If you are writing unified logs to a different directory other than the default, you must run the vxlogcfg command to point the logs to the new directory after the upgrade. To check the location before upgrading, edit the nblog.conf file in the NetBackup root directory.


❏ When you upgrade NetBackup, the VSP cache settings for the master server are overwritten. If you are using the VSP cache, be sure to check those settings before you start the upgrade and then reset them after the upgrade is finished.



VERITAS

Appendix D: Document change log

The following list describes the changes that were implemented for each revision of this document.

■ Revision A

■ Initial release

■ Revision B

■ Expanded the information about running the NBCC utility.

■ Added new appendix about phased upgrade planning.

■ Added recommendation to upgrade to NetBackup 6.5.2 or later, which was the most recent release available when Revision B of this TechNote was published.

■ Revision C

■ Updated the URL to download the NBCC utility.

■ Revision D - March 6, 2009

■ Updated the nbemmcmd command syntax so it includes the correct option for a cluster name. See Step 10 on page 14.


upgrading to veritas netbackup™ 6.5 from 5.x

Documents