Release Update NBLU_6.5.6.WINia64.zip provides updates and fixes for Veritas NetBackup (tm) Server / Enterprise Server 6.5 via Live Update. These packages contain all server, client, and option packages for Windows IA-64 platforms.
| Article:TECH129360 | | | Created: 2010-01-27 | | | Updated: 2010-01-07 | | | Article URL http://www.symantec.com/docs/TECH129360 |
Problem
Release Update NBLU_6.5.6.WINia64.zip provides updates and fixes for Veritas NetBackup (tm) Server / Enterprise Server 6.5 via Live Update. These packages contain all server, client, and option packages for Windows IA-64 platforms.
Solution
NetBackup LiveUpdate 6.5.6
README May
4, 2010
NBLU_6.5.6 Windows
================================================================================
This README describes the fixes and updates contained within the Veritas
NetBackup 6.5.6 Release Update LiveUpdate Packages.
For additional information about new platform proliferations, new features
associated with this release, end-of-life notifications, known issues, and
the current Release Update content, refer to the following TechNote on the
Symantec Support Web site:
http://entsupport.symantec.com/docs/341279
================================================================================
====================
RELEASE DEPENDENCIES
====================
-- You can use a single LiveUpdate server for NetBackup to deploy updates
for UNIX and Windows. To create a LiveUpdate server for NetBackup
6.5.6 Windows, you must download and extract the following bundle(s).
You only need to extract the bundles for the windows platforms you
plan to update.
NBLU_6.5.6.WINia64.zip
NBLU_6.5.6.WINx64.zip
NBLU_6.5.6.WINx86.zip
-- You can use the same LiveUpdate server to deploy NetBackup updates for
UNIX. To accomplish this, you MUST download and extract *ALL* of the
following four (4) segments of the LiveUpdate server for NetBackup UNIX
bundle.
NBLU_6.5.6.UNIX_1of4.zip
NBLU_6.5.6.UNIX_2of4.zip
NBLU_6.5.6.UNIX_3of4.zip
NBLU_6.5.6.UNIX_4of4.zip
The UNIX bundles only work if all four (4) are extracted together,
they will NOT work individually.
-- In order to update NetBackup UNIX hosts, be sure that /tmp on the
hosts to be updated meet the minimum available space requirements of
2.0GB for NetBackup Servers and 1.0GB for NetBackup clients. See the
Known Issues section below for more information.
===========================
I. LIVEUPDATE FOR NETBACKUP
===========================
Creating a LiveUpdate Server for NetBackup:
-------------------------------------------
A LiveUpdate Server for NetBackup does not require any additional software, but
is simply an HTTP server or disk share that has been populated with the contents
of this LiveUdpate Server for NetBackup bundle.
1. Create a LiveUpdate Server for NetBackup.
a. Configure either an HTTP server or a shared disk that can be accessed by
all NetBackup hosts that you plan to update. Refer to the "NetBackup
LiveUpdate" chapter of the NetBackup 6.5 Installation Guide for Windows.
The LiveUpdate Server for NetBackup can be a Windows or UNIX host.
NetBackup LiveUpdate policies can be used to update NetBackup on either
Windows or UNIX machines.
b. Download the following file(s) into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
where <6 digit number> is an internal tracking identifier
You only need to extract the bundles for the windows platforms you
plan to update.
2. Extract the following file(s) into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
a. To extract the bundle(s) on a Windows system use an appropriate unzip
utility.
b. To extract the bundle(s) on a UNIX system use the following command.
Determine if your UNIX system has "unzip", otherwise you will need
to obtain a version compatible with your UNIX system.
unzip NBLU_6.5.6.WINia64_<6 digit number>.zip
unzip NBLU_6.5.6.WINx64_<6 digit number>.zip
unzip NBLU_6.5.6.WINx86_<6 digit number>.zip
This creates a large number of files that comprise a LiveUpdate Server for
NetBackup. Do not rename, move, or delete any files that were extracted.
NetBackup LiveUpdate Known Issues:
----------------------------------
The following issues pertain specifically to the LiveUpdate server for NetBackup
product.
+ (ET1544083) When creating a Live Update policy, make sure that the policy
name is unique and that it is not the same as any other internal or external
policy name. The Live Update policy fails if its name is the same as any
other policy name.
+ (ET1176187) Installing 6.5.3 Java 64 bit on a IA64 server via LiveUpdate
will not work. There is a known issue with the registration script in 6.5 GA.
As a result, the NB_JAV_6.5.3.IA64.winnt.IA64.exe update needs to be
separately downloaded from the Symantec Support Web Site and installed
manually.
+ Page 118 and 119 of the NetBackup 6.5 Installation Guide for Windows
indicates the use of a universal naming convention path (UNC) as one of the
acceptable methods of using a Windows machine as a LiveUpdate server for
NetBackup. An example of a UNC path on Windows is "\\server\shared_dir\".
Currently, when a client is configured to use a UNC for the LiveUpdate
server, and the update is launched using the policy execution on the
LiveUpdate server, the nbliveup process on the client starts and then halts
shortly after starting.
This is the result of system permissions and the local SYSTEM account's
inability to resolve network drives. Refer to the following TechNote on the
Symantec Support Web Site for more information.
http://entsupport.symantec.com/docs/294336
+ If you are updating a clustered NetBackup server in a VCS configuration,
Symantec recommends that you run the manual patch install.
+ In order to free up disk space for downloading updates, the JavaLiveUpdate
agent on UNIX caches downloaded patches, by default, in the /tmp directory.
To reconfigure the directory the JavaLiveUpdate uses for temporary space,
modify the "workdir" setting in the /usr/openv/netbackup/nblu.conf file.
+ In order to successfully use LiveUpdate to apply NetBackup 6.5.6 on UNIX
hosts, ensure the total available space in the /tmp directory of the
NetBackup host to be updated meets the following minimum space requirement:
NetBackup Server - /tmp must have at least 2.0GB of total available space
NetBackup Client - /tmp must have at least 1.0GB of total available space
If the /tmp directory of the NetBackup host to be updated cannot meet the
minimum requirement, you can reconfigure the JavaLiveUpdate agent to use an
alternate directory. Edit the "workdir" setting in the
/usr/openv/netbackup/nblu.conf file. For example, to reconfigure a machine
to use /space/downloads as the working directory, edit nblu.conf to replace
the line:
workdir=/tmp
With the following line:
workdir=/space/downloads
Failure to meet the minimal space requirement can result in your NetBackup
Liveupdate policy failing with an exit status of 77. The
/opt/Symantec/LiveUpdate/liveupdt.log will indicate exit status "246", with
a message similar to the following:
"Disk space check for <pkgname> failed. Requested free space was XXX (in MB)
The Java LiveUpdate session did not complete successfully.
Return code = 246"
Additionally, the /usr/openv/netbackup/logs/nbliveup/ logs will indicate
status "118", with a message similar to the following:
"Error executing /usr/openv/java/jre/bin/java -cp
/opt/Symantec/LiveUpdate/jlu.jar com.symantec.liveupdate.LiveUpdate -c
/usr/openv/netbackup/nblu.conf, status = 118"
Using LiveUpdate to deploy NetBackup Release Update 6.5.6:
---------------------------------------------------------
To use the LiveUpdate Server for NetBackup, you must first ensure that all
NetBackup hosts that you intend to update have the NetBackup LiveUpdate Agent
installed, and that they are configured with the location and protocol that
points to your LiveUpdate Server for NetBackup.
To install NetBackup LiveUpdate Agent on Windows
1. The agent is automatically installed on Windows.
2. The agent needs to be configured for protocol and location of the
LiveUpdate Server for NetBackup.
To install NetBackup LiveUpdate Agent on UNIX
1. From the NetBackup 6.5 Options CD, select "LiveUpdate Agent".
2. When prompted for protocol and location, enter the protocol and location
used by the LiveUpdate Server for NetBackup that has been populated with
the contents of these bundles.
Refer the NetBackup 6.5 Installation Guide for Windows for instructions
on installing the NetBackup LiveUpdate agent, and creating and executing a
NetBackup LiveUpdate policy.
On UNIX, ensure that each host to be updated meets the minimum space
requirements in /tmp, as specified in the Known Issues section of this README.
NOTE: The updates contained in the following files are not meant to be
installed manually, and must only be used by a NetBackup LiveUpdate policy.
- NBLU_6.5.6.UNIX_1of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_2of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_3of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_4of4_<6 digit number>.zip
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
Uninstalling NetBackup Release Update 6.5.6:
--------------------------------------------
LiveUpdate for NetBackup does not provide a NetBackup policy method for
uninstalling Release Updates. You must follow this procedure locally
on each NetBackup host that you want to uninstall.
To uninstall the Release Update from a Windows CLUSTER Environment:
1) Uninstall this Release Update from the nodes of the cluster where the
NetBackup group is inactive. (follow steps 1-2 below)
2) Uninstall this Release Update from the active NetBackup node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.
CAUTION:
Do not failover the NetBackup Group until all NetBackup nodes (including
the active NetBackup node) have the Release Update uninstalled.
**Important notice regarding un-installs on Windows**
Only the last Release Update installed on a Windows system can be un-installed.
1) Close all NetBackup Windows.
Make sure the NetBackup server has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Release Update will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped via the
Control Panel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
uninstalled.
2) Go to Add/Remove programs dialog box and select the correct release update
to be uninstalled.
WARNING: While the Release Update is being uninstall, any attempt to cancel
the uninstall operation while it is in progress might leave NetBackup
in an unknown state. Once you have canceled the uninstall, you should
manually try to restart the services. If the services do not come up
properly, Symantec recommends that you completely uninstall the
Release Update and install it again.
NBLU_6.5.6 Windows
================================================================================
This README describes the fixes and updates contained within the Veritas
NetBackup 6.5.6 Release Update LiveUpdate Packages.
For additional information about new platform proliferations, new features
associated with this release, end-of-life notifications, known issues, and
the current Release Update content, refer to the following TechNote on the
Symantec Support Web site:
http://entsupport.symantec.com/docs/341279
================================================================================
====================
RELEASE DEPENDENCIES
====================
-- You can use a single LiveUpdate server for NetBackup to deploy updates
for UNIX and Windows. To create a LiveUpdate server for NetBackup
6.5.6 Windows, you must download and extract the following bundle(s).
You only need to extract the bundles for the windows platforms you
plan to update.
NBLU_6.5.6.WINia64.zip
NBLU_6.5.6.WINx64.zip
NBLU_6.5.6.WINx86.zip
-- You can use the same LiveUpdate server to deploy NetBackup updates for
UNIX. To accomplish this, you MUST download and extract *ALL* of the
following four (4) segments of the LiveUpdate server for NetBackup UNIX
bundle.
NBLU_6.5.6.UNIX_1of4.zip
NBLU_6.5.6.UNIX_2of4.zip
NBLU_6.5.6.UNIX_3of4.zip
NBLU_6.5.6.UNIX_4of4.zip
The UNIX bundles only work if all four (4) are extracted together,
they will NOT work individually.
-- In order to update NetBackup UNIX hosts, be sure that /tmp on the
hosts to be updated meet the minimum available space requirements of
2.0GB for NetBackup Servers and 1.0GB for NetBackup clients. See the
Known Issues section below for more information.
===========================
I. LIVEUPDATE FOR NETBACKUP
===========================
Creating a LiveUpdate Server for NetBackup:
-------------------------------------------
A LiveUpdate Server for NetBackup does not require any additional software, but
is simply an HTTP server or disk share that has been populated with the contents
of this LiveUdpate Server for NetBackup bundle.
1. Create a LiveUpdate Server for NetBackup.
a. Configure either an HTTP server or a shared disk that can be accessed by
all NetBackup hosts that you plan to update. Refer to the "NetBackup
LiveUpdate" chapter of the NetBackup 6.5 Installation Guide for Windows.
The LiveUpdate Server for NetBackup can be a Windows or UNIX host.
NetBackup LiveUpdate policies can be used to update NetBackup on either
Windows or UNIX machines.
b. Download the following file(s) into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
where <6 digit number> is an internal tracking identifier
You only need to extract the bundles for the windows platforms you
plan to update.
2. Extract the following file(s) into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
a. To extract the bundle(s) on a Windows system use an appropriate unzip
utility.
b. To extract the bundle(s) on a UNIX system use the following command.
Determine if your UNIX system has "unzip", otherwise you will need
to obtain a version compatible with your UNIX system.
unzip NBLU_6.5.6.WINia64_<6 digit number>.zip
unzip NBLU_6.5.6.WINx64_<6 digit number>.zip
unzip NBLU_6.5.6.WINx86_<6 digit number>.zip
This creates a large number of files that comprise a LiveUpdate Server for
NetBackup. Do not rename, move, or delete any files that were extracted.
NetBackup LiveUpdate Known Issues:
----------------------------------
The following issues pertain specifically to the LiveUpdate server for NetBackup
product.
+ (ET1544083) When creating a Live Update policy, make sure that the policy
name is unique and that it is not the same as any other internal or external
policy name. The Live Update policy fails if its name is the same as any
other policy name.
+ (ET1176187) Installing 6.5.3 Java 64 bit on a IA64 server via LiveUpdate
will not work. There is a known issue with the registration script in 6.5 GA.
As a result, the NB_JAV_6.5.3.IA64.winnt.IA64.exe update needs to be
separately downloaded from the Symantec Support Web Site and installed
manually.
+ Page 118 and 119 of the NetBackup 6.5 Installation Guide for Windows
indicates the use of a universal naming convention path (UNC) as one of the
acceptable methods of using a Windows machine as a LiveUpdate server for
NetBackup. An example of a UNC path on Windows is "\\server\shared_dir\".
Currently, when a client is configured to use a UNC for the LiveUpdate
server, and the update is launched using the policy execution on the
LiveUpdate server, the nbliveup process on the client starts and then halts
shortly after starting.
This is the result of system permissions and the local SYSTEM account's
inability to resolve network drives. Refer to the following TechNote on the
Symantec Support Web Site for more information.
http://entsupport.symantec.com/docs/294336
+ If you are updating a clustered NetBackup server in a VCS configuration,
Symantec recommends that you run the manual patch install.
+ In order to free up disk space for downloading updates, the JavaLiveUpdate
agent on UNIX caches downloaded patches, by default, in the /tmp directory.
To reconfigure the directory the JavaLiveUpdate uses for temporary space,
modify the "workdir" setting in the /usr/openv/netbackup/nblu.conf file.
+ In order to successfully use LiveUpdate to apply NetBackup 6.5.6 on UNIX
hosts, ensure the total available space in the /tmp directory of the
NetBackup host to be updated meets the following minimum space requirement:
NetBackup Server - /tmp must have at least 2.0GB of total available space
NetBackup Client - /tmp must have at least 1.0GB of total available space
If the /tmp directory of the NetBackup host to be updated cannot meet the
minimum requirement, you can reconfigure the JavaLiveUpdate agent to use an
alternate directory. Edit the "workdir" setting in the
/usr/openv/netbackup/nblu.conf file. For example, to reconfigure a machine
to use /space/downloads as the working directory, edit nblu.conf to replace
the line:
workdir=/tmp
With the following line:
workdir=/space/downloads
Failure to meet the minimal space requirement can result in your NetBackup
Liveupdate policy failing with an exit status of 77. The
/opt/Symantec/LiveUpdate/liveupdt.log will indicate exit status "246", with
a message similar to the following:
"Disk space check for <pkgname> failed. Requested free space was XXX (in MB)
The Java LiveUpdate session did not complete successfully.
Return code = 246"
Additionally, the /usr/openv/netbackup/logs/nbliveup/ logs will indicate
status "118", with a message similar to the following:
"Error executing /usr/openv/java/jre/bin/java -cp
/opt/Symantec/LiveUpdate/jlu.jar com.symantec.liveupdate.LiveUpdate -c
/usr/openv/netbackup/nblu.conf, status = 118"
Using LiveUpdate to deploy NetBackup Release Update 6.5.6:
---------------------------------------------------------
To use the LiveUpdate Server for NetBackup, you must first ensure that all
NetBackup hosts that you intend to update have the NetBackup LiveUpdate Agent
installed, and that they are configured with the location and protocol that
points to your LiveUpdate Server for NetBackup.
To install NetBackup LiveUpdate Agent on Windows
1. The agent is automatically installed on Windows.
2. The agent needs to be configured for protocol and location of the
LiveUpdate Server for NetBackup.
To install NetBackup LiveUpdate Agent on UNIX
1. From the NetBackup 6.5 Options CD, select "LiveUpdate Agent".
2. When prompted for protocol and location, enter the protocol and location
used by the LiveUpdate Server for NetBackup that has been populated with
the contents of these bundles.
Refer the NetBackup 6.5 Installation Guide for Windows for instructions
on installing the NetBackup LiveUpdate agent, and creating and executing a
NetBackup LiveUpdate policy.
On UNIX, ensure that each host to be updated meets the minimum space
requirements in /tmp, as specified in the Known Issues section of this README.
NOTE: The updates contained in the following files are not meant to be
installed manually, and must only be used by a NetBackup LiveUpdate policy.
- NBLU_6.5.6.UNIX_1of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_2of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_3of4_<6 digit number>.zip
- NBLU_6.5.6.UNIX_4of4_<6 digit number>.zip
- NBLU_6.5.6.WINia64_<6 digit number>.zip
- NBLU_6.5.6.WINx64_<6 digit number>.zip
- NBLU_6.5.6.WINx86_<6 digit number>.zip
Uninstalling NetBackup Release Update 6.5.6:
--------------------------------------------
LiveUpdate for NetBackup does not provide a NetBackup policy method for
uninstalling Release Updates. You must follow this procedure locally
on each NetBackup host that you want to uninstall.
To uninstall the Release Update from a Windows CLUSTER Environment:
1) Uninstall this Release Update from the nodes of the cluster where the
NetBackup group is inactive. (follow steps 1-2 below)
2) Uninstall this Release Update from the active NetBackup node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.
CAUTION:
Do not failover the NetBackup Group until all NetBackup nodes (including
the active NetBackup node) have the Release Update uninstalled.
**Important notice regarding un-installs on Windows**
Only the last Release Update installed on a Windows system can be un-installed.
1) Close all NetBackup Windows.
Make sure the NetBackup server has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Release Update will not install if the file to update is busy.
If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped via the
Control Panel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
uninstalled.
2) Go to Add/Remove programs dialog box and select the correct release update
to be uninstalled.
WARNING: While the Release Update is being uninstall, any attempt to cancel
the uninstall operation while it is in progress might leave NetBackup
in an unknown state. Once you have canceled the uninstall, you should
manually try to restart the services. If the services do not come up
properly, Symantec recommends that you completely uninstall the
Release Update and install it again.
Attachments
|
|
|
Related Articles
Legacy ID
351599
Article URL http://www.symantec.com/docs/TECH129360
Terms of use for this information are found in Legal Notices









Thank you.