Release Update NBLU_6.5.3.1.UNIX_2of3.zip (package 2 of 3) 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 all UNIX platforms.

Article:TECH67907  |  Created: 2009-01-13  |  Updated: 2009-01-16  |  Article URL http://www.symantec.com/docs/TECH67907
Article Type
Technical Solution


Environment

Issue



Release Update NBLU_6.5.3.1.UNIX_2of3.zip (package 2 of 3) 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 all UNIX platforms.

Solution



NetBackup LiveUpdate 6.5.3.1 README February 13, 2009
NBLU_6.5.3.1 UNIX
================================================================================
This README describes the fixes and updates contained within the Veritas
NetBackup 6.5.3.1 Hotfix LiveUpdate Packages.

The NetBackup 6.5.3.1 LiveUpdate containers include the files distributed as
part of NetBackup 6.5.3 and NetBackup 6.5.3.1. This allows customers to use
LiveUpdate to populate their local LiveUpdate server with all files required to
upgrade to 6.5.3.1. When a LiveUpdate policy is launched to upgrade to 6.5.3.1,
the local host that is targeted for the update determines what set of files is
required.

If NetBackup 6.5.3 is already installed, then the local LiveUpdate agent
recognizes that only the NetBackup 6.5.3.1 update needs to be applied. In
addition, if NetBackup 6.5 GA, 6.5.1, or 6.5.2 is already installed, then the
local LiveUpdate agent recognizes that NetBackup 6.5.3 and 6.5.3.1 files need
to be applied in that order.
================================================================================


====================
RELEASE DEPENDENCIES
====================

-- NetBackup 6.5GA or 6.5.x needs to be installed on the system before
using LiveUpdate to apply this update. In addition, you must install
and configure the NetBackup LiveUpdate agent on the host to be updated
before you launch a NetBackup LiveUpdate policy.

-- You can use a single LiveUpdate server for NetBackup to deploy updates
for UNIX and Windows. To create a LiveUpdate server for NetBackup
UNIX 6.5.3, you MUST download and extract *ALL* of the following
three (3) segments of the LiveUpdate server for NetBackup UNIX bundle.

NBLU_6.5.3.1.UNIX_1of3.zip
NBLU_6.5.3.1.UNIX_2of3.zip
NBLU_6.5.3.1.UNIX_3of3.zip

-- You can use the same LiveUpdate server to deploy NetBackup updates for
Windows. To accomplish this, download and extract the following
bundles into the same location as the three (3) segments of the
NetBackup UNIX bundle.

NBLU_6.5.3.1.WINia64.zip
NBLU_6.5.3.1.WINx64.zip
NBLU_6.5.3.1.WINx86.zip


I. LIVEUPDATE FOR NETBACKUP
Creating a LiveUpdate Server for NetBackup
NetBackup LiveUpdate Known Issues
Using LiveUpdate to deploy NetBackup 6.5.3.1
Uninstalling NetBackup 6.5.3.1
II. NEW NETBACKUP FEATURES AND PLATFORM PROLIFERATIONS
Platform Proliferations
New Features and Enhancements
III. KNOWN ISSUES
IV. CURRENT HOTFIX INDEX
V. HOTFIX CONTENT
Conventions
Current Hotfix
NBLU_6.5.3.1.UNIX
Release Update History
NBLU_6.5.3.UNIX
NBLU_6.5.2.UNIX
NBLU_6.5.1.UNIX


===========================
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 UNIX and
Linux.

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 files into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.3.1.UNIX_1of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_2of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_3of3_<6 digit number>.zip
where <6 digit number> is an internal tracking identifier

**NOTE: Without both segments, LiveUpdate for NetBackup UNIX will not
be functional.


2. Extract the following files into the root directory of the NetBackup
LiveUpdate server, which is either the HTTP root directory or the shared
disk directory.
- NBLU_6.5.3.1.UNIX_1of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_2of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_3of3_<6 digit number>.zip

a. To extract the bundles on a UNIX system use the following command.

unzip NBLU_6.5.3.1.UNIX_1of3_<6 digit number>.zip
unzip NBLU_6.5.3.1.UNIX_2of3_<6 digit number>.zip
unzip NBLU_6.5.3.1.UNIX_3of3_<6 digit number>.zip

b. To extract the bundles on a Windows system use an appropriate unzip
utility.

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.

+ NetBackup LiveUpdate jobs to update an AIX or HPIA64 NetBackup Master or
Media server will fail with either a yellow job status 1, or a red job
status 77 in the Activity Monitor. This is caused when the update sizes
exceed the default maximum download cache size imposed by the LiveUpdate
agent.

Exact Error Messages:
Look for the following message in the Java LiveUpdate agent log
/opt/Symantec/livedupdt.log:

Disk space check for <update_name> failed. Requested free space was
<###> (in MB).
The Java LiveUpdate session did not complete successfully.
Return code = 246

Where <update_name> is the name of the update that pushes the total size
over the default maximum cache size limit, and <###> is the amount by which
the default has been exceeded.

Details:
If the total size of the updates being applied exceeds the default cache
size limit (a 1GB maximum), the NetBackup LiveUpdate policy fails. The AIX
and HPIA64 NetBackup Server updates by themselves and exceeds the 1GB size
limit. Therefore you must apply the workaround explained below on AIX and
HPIA64 servers to use NetBackup LiveUpdate. NetBackup LiveUpdate policies
can also fail on other platforms if add-on products or extra client binaries
are loaded on the NetBackup Master or Media server.

Workarounds
To resolve or prevent a failed update, take one of the following actions
prior to starting any NetBackup LiveUpdate jobs.

Workaround Option 1:
Add the following line to the /usr/openv/netbackup/nblu.conf file on the
NetBackup Master or Media server that you wish to update:

downloadCacheSize=8192

Workaround Option 2:
Alternatively, you can push the updated configuration file that contains
the fix for this issue from a NetBackup Master Server to the affected
NetBackup Master or Media servers by performing the following steps.

1. Download and install NB_LUA_6.5.3<6-digit number>.tar on a master
server. This requires you to apply the NB_CLT_6.5.3 and NB_6.5.3
updates as well.

2. Run the following command to push the 6.5.3 LUA from the NetBackup
Master server to the affected NetBackup Master or Media servers.
You will be required to re-enter the name and protocol of the
LiveUpdate server you want to use.

update_luagent -ForceReconfig -ClientList <filename>

Where <filename> contains the names of the affected NetBackup
Master or Media servers.
or

update_luagent -ForceReconfig <hardware_type> <operating_system>

See the 6.5 NetBackup Installation Guide for more information about
the update_luagent command.

3. Run the LiveUpdate policy to update the affected NetBackup Master
and Media servers.

+ The JavaLiveUpdate agent on UNIX caches downloaded patches, by default, in
the /tmp directory. However, the agent does not clean up entirely when it is done.
In the /tmp directory, the JavaLiveUpdate agent creates directories named with
"epoch-seconds" timestamps, for example:

/tmp/1197593367575/

You may need to purge these unnecessary directories from the /tmp directory to
avoid running out of space after JavaLiveUpdate has completed. To reconfigure the
directory the JavaLiveUpdate uses, modify the "workdir" setting in the
/usr/openv/netbackup/nblu.conf file.

+ 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


Using LiveUpdate to deploy NetBackup 6.5.3.1:
---------------------------------------------
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 UNIX and Linux for instructions
on installing the NetBackup LiveUpdate agent, and creating and executing a
NetBackup LiveUpdate policy.

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.3.1.UNIX_1of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_2of3_<6 digit number>.zip
- NBLU_6.5.3.1.UNIX_2of3_<6 digit number>.zip
- NBLU_6.5.3.1.WINia64_<6 digit number>.zip
- NBLU_6.5.3.1.WINx64_<6 digit number>.zip
- NBLU_6.5.3.1.WINx86_<6 digit number>.zip


Uninstalling NetBackup 6.5.3.1:
-------------------------------
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 wish to uninstall.

1)Close the NetBackup user interfaces.

Make sure the NetBackup server has no active jobs running (for
example, backups, restores, or duplications).

If a database agent is being used, such as Oracle,
ensure that the database services are stopped.

2)Change directory to the patch save directory.
Substitute the Hotfix name for ${PACK} in the following
command:

cd /usr/openv/pack/${PACK}/save

3)Run the un-install script:

./NB_update.uninstall

4)Verify that the Hotfix uninstalled successfully by checking
/usr/openv/pack/pack.history.

5)If necessary, restart the NetBackup and Media Manager daemons:
/usr/openv/netbackup/bin/bp.start_all




=======================================================
II. NEW NETBACKUP FEATURES AND PLATFORM PROLIFERATIONS
=======================================================
The following items describe the new enhancements contains in this Hotfix.

For information about new 6.5.3 features and proliferations in, refer to the
NetBackup 6.5.3 online Release Update Readme and the NetBackup 6.5.3
Documentation Update document on the Symantec Support Web site.

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

+ A change has been added in this release that addresses an issue that would
allow jobs to run and complete successfully while the time changed because
of Daylight Savings Time.

For more information about how schedules will be treated during daylight
savings time, refer to the following TechNote on the Symantec Support Web
site.

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

+ This release contains enhancements that enable NetBackup to make more
knowledgeable schedule selections to meet daily backup frequency requirements.
This intelligence helps to avoid backups that run soon after midnight if the
same backup ran just before midnight. In policies with a daily frequency,
NetBackup looks at the schedules in the day ahead to see if another schedule
is available and determines whether it should run the backup during the later
schedule.

For more information about this enhancement, refer to the following TechNote
on the Symantec Support Web site.

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




=================
III. KNOWN ISSUES
=================
+ (ET1514170) A schedule that is configured to open and close during the
Daylight Savings Time (DST) changeover hour in the Spring of the year may not
run. If you have any schedules configured to run during this window, Symantec
recommends that you adjust the window of these schedules to a time that is
outside of the DST changeover hour.

For more information about this issue, refer to the following TechNote on the
Symantec Support Web site.

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

+ (ET1514238) While launching the NetBackup-Java Administration Console (using
the jnbSA script) or the NetBackup-Java BAR user interface (using the jbpSA
script) on a Linux IA 64-bit platform, you may encounter the following error
message.

ERROR: ld.so: object '/opt/VRTSat/lib/ia64/libstdc++.so.5' from LD_PRELOAD
cannot be preloaded: ignored.

This error message occurs if you have not installed the Symantec Authentication
Service (AT). You can ignore the error message and continue to work in the
NetBackup console.

+ (ET1516790) An issue exists that can cause the NetBackup-Java Administration
Console to display the time in the Tasks Performed window to be one off one hour
from the actual time, based on a previous daylight savings time (DST) date.

To avoid this problem, Symantec recommends that you manually enter the correct
settings in to the Adjust Application Timezone dialog, and save this as the
default. This change is saved and then used on subsequent program operations to
enable the NetBackup-Java Administration Console to use the correct default
timezone.

To change the timezone, use the following steps as a guide.
1. With the NetBackup-Java Administration Console open, select File > Adjust
application timezone.

2. From the Standard tab in the Adjust time window, do the following:
a. Verify that your timezone appears as the timezone being used.
b. Click the "Use custom timezone" check box.

3. Select the Custom tab. This tabbed page shows the timezone, current start
and end times for daylight savings time (DST). Do the following to change
the start and end dates appropriately for your timezone.
a. Verify that your timezone appears in the Base Timezone On drop-down menu.
c. Adjust the DST Start date and time as necessary for your region.
d. Adjust the DST End date and time as necessary for your region.
e. Click OK. Your times will adjust and the administration console will
now show the correct time.

+ There can be a pack uninstall issue on UNIX NetBackup servers that have
loaded non-native client binaries (for example, Solaris clients on a Linux
server) when LiveUpdate is used to go directly from pre-6.5.3 to 6.5.3.1. In
this scenario, the NB_CLT_6.5.3.1 uninstall will report the following:

ERROR: The following installed pack(s) depend on NB_CLT_6.5.3.1:
NB_6.5.3
Please uninstall the above pack(s) first.

This dependency is incorrect - if feasible, remove NB_6.5.3 first and then
remove NB_CLT_6.5.3.1. Alternatively, if you do not wish to remove NB_6.5.3
first, then edit the /usr/openv/.psummary file as described in the following
steps:

1. Locate the line that starts with the following:
NB_6.5.3 installed. *NB_CLT_6.5.3 *NB_CLT_6.5.3.1

2. Remove the following string (including the asterisk *') from the line.
*NB_CLT_6.5.3.1 (The line should read: NB_6.5.3 installed. *NB_CLT_6.5.3.)

3. Proceed with the NB_CLT_6.5.3.1 uninstall.

+ For additional information about using LiveUpdate, refer to the following
TechNote on the Symantec Support Web site.

http://entsupport.symantec.com/docs/294336
http://entsupport.symantec.com/docs/302988
http://entsupport.symantec.com/docs/304104
http://entsupport.symantec.com/docs/314073




========================
IV. CURRENT HOTFIX INDEX
========================

This section contains a master index for all UNIX packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_6.5.3.1
----------
1476452 1443700 1476457 1476459 1476454 1476436 1483219 1488529 1507022

NB_CLT_6.5.3.1
--------------
1476452 1443700 1476457 1476459 1476454 1476436 1480329 1483219 1488529 1507022


NB_JAV_6.5.3.1
--------------
1487543




=================
V. HOTFIX CONTENT
=================
This section contains the Hotfix conventions, content, and historical
content that is applicable to the Hotfix.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section. Each item listed in the Current Hotfix subsection
describes a feature, enhancement, or issue fixed with this Hotfix.

Description
Describes a particular problem contained in this Hotfix.

** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.

Workaround
Any available workarounds to a problem are also listed. Workarounds can be
used INSTEAD of applying the patch, however, Symantec strongly recommends
the "best practice" of being at the latest available patch level.

Additional Notes
Any additional information regarding a problem is included.



Current Hotfix
--------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Hotfix. Please read this section thoroughly to understand
the contents of this Hotfix.
--------------------------------------------------------------------------------
Etrack Incident = ET1476452
Associated Primary Etrack = ET1435447
Titan cases: 281-430-989

Description:
A change was made to address an issue that caused the NDMP dmplevel to
not be reset properly after a full backup was run.
--------------------------------------------------------------------------------
Etrack Incident = ET1443700
Associated Primary Etrack = ET1391305
Titan cases: 220-374-967 320-135-491

**Description:
Calendar incremental backups would not run on the same day as calendar
full backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1476457
Associated Primary Etrack = ET1409915
Titan cases: 240-820-679

Description:
MS SQL backups would run twice when an automatic backup was started.

Additional Notes:
This issue would occur when immediate backups were submitted and the
policy name was spelled with an incorrect case from the bpbackup command.
Symantec recommends that you use care when specifying the policy name.
--------------------------------------------------------------------------------
Etrack Incident = ET1476459
Associated Primary Etrack = ET1445633
Titan cases: 312-046-169 281-453-350 291-104-679

Description:
A change has been added to address an issue that would allow jobs to run
continuously while the time changed because of daylight savings time.
--------------------------------------------------------------------------------
Etrack Incident = ET1476454
Associated Primary Etrack = ET1386189
Titan cases: 320-127-126 220-416-368 230-596-851

Description:
A problem existed that caused nbpem to core dump when there was a heavy
load on the master server and nbpem failed to open or read the bprd comm
file for immediate or user backups.
--------------------------------------------------------------------------------
Etrack Incident = ET1476436
Associated Primary Etrack = ET1443574
Titan cases: 220-457-153

Description:
A change has been made to address a core dump issue found with nbpem that
would occur when a user attempted to restart a user-initiated backup that
had failed.
--------------------------------------------------------------------------------
Etrack Incident = ET1480329

Description:
A logic error had been identified and corrected in daemons that run on
Veritas NetBackup master, media, and client servers. Successful access to
and manipulation of this logic error could potentially lead to arbitrary
command execution with elevated privileges on a vulnerable system.

For more information about this issue, refer to the following TechNote
on the Symantec Support Web site.

http://entsupport.symantec.com/docs/317828
--------------------------------------------------------------------------------
Etrack Incident = ET1483219

Description:
Additional corrections have been added to this release that ensure the
proper handling of daylight savings time. For additional information
on the issues that this fix resolves, refer to the following TechAlert
on the Symantec Support Web site.

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

--------------------------------------------------------------------------------
Etrack Incident = ET1488529

Description:
A calendar schedule that crosses multiple days would stop scheduling
completely after running on the last full day when only one window was
open for the week.
--------------------------------------------------------------------------------
Etrack Incident = ET1487543

Description:
A change has been made to ensure forward compatibility in the
NetBackup-Java Administration Console between NetBackup 6.5.3 and future
triple-dot releases, (for example, 6.5.3.1).

This change does not provide forward compatibility between double-dot
releases, (for example 6.5.3 will not be forward compatible with 6.5.4,
and 6.5.3.1 will not be forward compatible with 6.5.4.1).
--------------------------------------------------------------------------------
Etrack Incident = ET1507022

Description:
The nbemmcmd command did not allow for the server to be added with a
triple-dot version (6.x.x.x) and did not display the version correctly.
A change has been made to the command and the version is now correctly
displayed.
--------------------------------------------------------------------------------



Release Update History
----------------------

For a complete accumulative list of all 6.5.x Release Update information
contained in previous releases refer to the NetBackup 6.5.3 online Readme.

Attachments

NBLU_6.5.3.1.UNIX_2of3_319551.zip (1.6 GBytes)


Legacy ID



319551


Article URL http://www.symantec.com/docs/TECH67907


Terms of use for this information are found in Legal Notices