Professional Documents
Culture Documents
■ Verify that the volumes on your disk staging storage unit (DSSU) have more than 1% of available disk space.
Upgrades to 6.0 require that certain files get duplicated. If a DSSU volume has less than 1% of available disk
space, errors can occur.
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.0 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.x uses SERVER and MEDIA_SERVER entries, see the following TechNote:
http://entsupport.symantec.com/docs/293038
■ 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.
■ For UNIX systems, run the following command:
/usr/openv/netbackup/bin/admincmd/bpstulist -U
■ For Windows systems, run the following command:
<install_path>\netbackup\bin\admincmd\bpstulist -U
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/
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.
Note: You must install the latest 6.0MP patch binaries before proceeding to Step (e), running the nbpushdata
command on all upgraded servers.
Best practices
The following sequence highlights the order in which you should install NetBackup software when upgrading from
one version of NetBackup to another.
Caution: The following is not the sequence you should use to run the nbpushdata command. Refer again to bullets a
- e above or the NetBackup 6.0 Installation Guides.
a Master server
b Media servers
c NetBackup Remote Administration consoles
(If supporting older releases, refer to the NetBackup 6.0 System 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 the
latest NetBackup 6.0 MP release, you can then upgrade your clients to NetBackup 6.0.
e Any NetBackup add-on products. The following should be considered for each add-on product:
Note: NetBackup does not retain job information from previous versions when upgraded with multiple releases
at the same time. NetBackup does not support resuming or restarting of any job that originated from an earlier
version. After an upgrade, incomplete or suspended jobs from the previous version may not appear in the
activity monitor window.
5 Stop all third party scripts and any other custom scripts.
6 Perform a catalog backup and verify that every media server in the configuration is listed in the catalog backup
files list.
Caution: To install the 6.0 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.
■ On clustered UNIX systems where the EMM server will be remote from the master server:
Note: This is a rare configuration. The master server and the EMM server typically reside on the same host.
Follow the instructions of the three bulleted items that follow, only if the EMM server will be remote from
the master server.
Perform steps 4 - 10 as described in the section “Upgrading NetBackup Server Software” in “Chapter 3” of
the NetBackup 6.0 Installation Guide for UNIX and Linux.
■ During step 11 when prompted for the license key on the active node, open another window on the host
and create a directory named “var” in the top-level directory of the NetBackup shared disk. For
example, if the NetBackup shared disk mount point is /opt/VRTSnbu, the required command would
be as follows:
mkdir /opt/VRTSnbu/var
■ On the active node, move the contents of directory /usr/openv/var/global to the newly created
directory on the shared disk. For example:
mv /usr/openv/var/global /opt/VRTSnbu/var
■ Continue with the remainder of step 11, followed by steps 12 - 14.
■ 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.
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.
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.
10 Verify that NetBackup policies are still deactivated. You can do this using the Administrator’s Console.
VERITAS
11 Install the latest NetBackup 6.0 maintenance pack. You can download this maintenance pack from the following
support web site: http://entsupport.symantec.com.
Note: You must install the latest 6.0MP patch binaries before proceeding.
12 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:
E:\Program Files\VERITAS\NetBackup\bin\admincmd>nbemmcmd -listsettings
-machiname emmservername
NBEMMCMD, Version:6.0MPx(2006mmdd)
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"
Note: If you want to simulate the pushdata commands described in Step 16, add the flag -preview to the
nbpushdata command. This command is available starting with 6.0 MP5. Simulating the command tests the
network connectivity to affected media servers and logs output to the pushdata log.
Note: If you are concerned that your current installation of NetBackup may be corrupt, contact Symantec
Technical Support for assistance.
VERITAS
18 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.0 cannot be backed up using 5.x media servers.
Note: With NetBackup 6.0, 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.
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.