Hotfix NB_CLT_6.5.3.1.tar provides fixes for the Veritas NetBackup (tm) Enterprise Server / Server 6.5.3 on UNIX clients.

Problem

Hotfix NB_CLT_6.5.3.1.tar provides fixes for the Veritas NetBackup (tm) Enterprise Server / Server 6.5.3 on UNIX clients.

Solution

CLT 6.5 Pack NB_CLT_6.5.3.1 README February 13, 2009
Requirement: NB_CLT_6.5.3
Corequirement: NB_6.5.3.1 NB_JAV_6.5.3.1
SeqNumber: 20080806
================================================================================
This Hotfix provides fixes for the Veritas NetBackup (tm) UNIX clients.
NetBackup UNIX Add-on products, Database Agents and the Java user interface have
separate Hotfixes.

This Hotfix may require as much as 400MB in free space in the /usr partition to
install. This Hotfix contains a full replacement of all client binaries for all
platforms. If applying this Hotfix locally, up to 100MB of free space is
required in /usr partition, depending on platform. If applying this pack to a
server that has had other client platform typesloaded (for example, push install
of client binaries) more space is required, up to 400MB. For more information,
please refer to the following TechNote:

http://seer.support.veritas.com/docs/280824.htm
================================================================================


=================
PACK DEPENDENCIES
=================
-- NB_CLT_6.5.3_<6 digit number>.tar must be installed before this
Hotfix is installed.

-- NB_CLT_6.5.3.1 (this Hotfix) can be installed on a standalone
NetBackup client using a remote installation procedure or a local
installation procedure.

-- Only on a NetBackup server, NB_6.5.3.1_<6 digit number>.<server>.tar
must be installed after this Hotfix is installed.

-- NB_JAV_6.5.3.1_<6 digit number>.<server>.tar must be installed after
this Hotfix is installed.

-- Installation of this Hotfix requires version 1.6.4.14.4.3 of the
NB_update.install script.


I. NEW FEATURES AND PLATFORM PROLIFERATIONS
Platform Proliferations
New Features and Enhancements
II. KNOWN ISSUES
III. DOWNLOAD INSTRUCTIONS
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. CURRENT HOTFIX INDEX
VII. HOTFIX CONTENT
Conventions
Current Hotfix
NB_CLT_6.5.3.1
Release Update History
NB_CLT_6.5.3
NB_CLT_6.5.2
NB_CLT_6.5.1



============================================
I. NEW 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




==================
II. 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.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================
1) Download the NB_CLT_6.5.3.1_<6 digit number>.tar into the
/tmp directory,

where <6 digit number> is an internal tracking identifier

NOTE: NB_CLT_6.5.3.1_<6 digit number>.tar contains all client binaries.

2) Extract the NB_CLT_6.5.3.1_<6 digit number>.tar file
tar xvf NB_CLT_6.5.3.1_<6 digit number>.tar

This will create the files:
VrtsNB_CLT_6.5.3.1.README
VrtsNB_CLT_6.5.3.1.<platforms>.tar.Z
VrtsNB_CLT_6.5.3.1.preinstall
VrtsNB_CLT_6.5.3.1.postinstall
VrtsNB_CLT_6.5.3.1.postuninstall
NB_update.install

where <platforms> are: ALPHA,HP-UX-IA64,HP9000-800,INTEL,Linux-IA64,
Linux,MACINTOSH,RS6000,SGI,SOLARIS




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **

NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure for this Hotfix.

Before installing this hotfix, please review the following items:
- Symantec recommends that you perform catalog backups before and after you
apply this maintenance pack.

- If you are planning to install this hotfix as a part of an upgrade from a
6.0 MPx release, you must first install NetBackup 6.5 GA before you install
this hotfix.

- If you are planning to install this hotfix as a part of an upgrade from a
5.x release then it is important that you understand that the existing
NetBackup databases must be in a consistent state prior to beginning
the upgrade. Information and tools to assist you in determining the current
state of your database, as well as instructions to help you address any
inconsistencies that you might discover can be viewed on the NetBackup Upgrade
Portal, a part of the Symantec NetBackup Support Web site.

http://support.veritas.com/menu_ddProduct_NBUESVR.htm

- If upgrading a NetBackup client on which this hotfix has been installed to
a NetBackup server, you must first uninstall this hotfix, perform the
upgrade from client to server,then re-apply this hotfix the new server.


To install this Hotfix in a UNIX Cluster Environment:
-----------------------------------------------------
1) Before you install this hotfix, make sure that NetBackup is at
release level 6.5 and configured to run in a cluster.

2) Install this hotfix on the inactive node(s) of the cluster (perform
steps 1 through 3 below).

3) Install this hotfix on the active node of the cluster (perform steps
listed below).

4) If the cluster is in a faulted state, clear the fault.

--------------------------------------------------------------------------------



There are two ways to install the client hotfix software.

1. Remote Installation: Loads the software on a NetBackup server with
the intent of pushing client software out to affected clients.

2. Local Installation: Loads and installs the software only to this
local machine.

Remote client install:


As root on the NetBackup Master/Media Server:

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) Install the NB_6.5.3.1 and NB_CLT_6.5.3.1 Hotfix binaries.

cd /tmp
/bin/sh NB_update.install

NOTE: Selecting the client Hotfix on a Master/Media server will
automatically install the server Hotfix if the server (NB) .Z file
and README exist in the installation directory. The client install will fail
if the (NB) .Z file and README are not present and the server pack has not
been previously installed. The server release Hotfix will NOT be installed
automatically during a reinstall of the client Hotfix.

NOTE: It is important that Server and Client binaries are kept at the same
release level on all NetBackup Servers. This is enforced by the install
process.


3) The NB_update.install script will prompt you to restart
daemons. Otherwise, after the pack installation has completed, run:

/usr/openv/netbackup/bin/bp.start_all

4) The pack install logs can be found in /usr/openv/pack/pack.history once the
installation is complete.

5) update the remote NetBackup clients with the update_clients script.

/usr/openv/netbackup/bin/update_clients <hardware> <os>

where <hardware> <os> is one of the following:

ALPHA/OSF1_V5
HP-UX-IA64/HP-UX11.23
HP9000-800/HP-UX11.00
HP9000-800/HP-UX11.11
INTEL/FreeBSD5.3
Linux-IA64/RedHat2.6
Linux-IA64/SuSE2.4
Linux-IA64/SuSE2.6
Linux/IBMpSeriesRedHat2.6
Linux/IBMpSeriesSuSE2.6
Linux/IBMzSeriesLinux2.4.21
Linux/IBMzSeriesRedHat2.6
Linux/IBMzSeriesSuSE2.6
Linux/RedHat2.4
Linux/RedHat2.6
Linux/SuSE2.6
MACINTOSH/MacOSX10.3
MACINTOSH/MacOSX10.4
RS6000/AIX5
SGI/IRIX65
Solaris/Solaris8
Solaris/Solaris9
Solaris/Solaris10
Solaris/Solaris_x86_8
Solaris/Solaris_x86_9
Solaris/Solaris_x86_10_64


Note: The /usr/openv/netbackup/bin/update_clients command without
any parameters will update all the UNIX clients.

Note: When updating an RS6000 client, there may be circumstances
where update_clients will fail with an error similar to
this:

Couldn't open /usr/openv/lib/libVmangle.so on client
Client open errno = 26

If this happens, execute /usr/sbin/slibclean on the client
to be updated and re-run update_clients.

If the client (CLT) .Z file and README exist in the installation
directory during the installation of the server Hotfix,
the NB_update.install script will install the client
Hotfix automatically. The client Hotfix will NOT
be installed automatically during a reinstall of the server
Hotfix.

Local client install:

The install script will determine if a local client install is appropriate
and choose the appropriate client type to install.

As root on the NetBackup client:

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) Install the NB_CLT_6.5.3 Hotfix binaries.

cd /tmp
/bin/sh NB_update.install

NOTE: Again, Symantec recommends that you perform catalog backups after you
have applied this hotfix.




=========================
V. UNINSTALL INSTRUCTIONS
=========================
Note: This will ONLY uninstall the Hotfix from your machine if the
client Hotfix software was installed directly on the machine.
This uninstall procedure will NOT work on clients that were installed
by pushing the software from a server.

As root on the NetBackup Master/Media Server in which the hotfix was installed:

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 pack name for ${PACK.EN_US} in the following command:

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

3)Run the un-install script:

./NB_update.uninstall

4)Verify that the pack uninstalled successfully by checking:

/usr/openv/pack/pack.history.

5)If update_clients was run after the pack was originally INSTALLED,
run it again after that pack is successfully UNINSTALLED.

6)If necessary, restart the NetBackup and Media Manager daemons:

/usr/openv/netbackup/bin/bp.start_all



========================
VI. 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




===================
VII. HOTFIX CONTENT
===================
This section contains the Release Update conventions, content, and historical
content that is applicable to the release.

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

Description
Describes a particular problem contained in this Release Update.

** 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 Release Update
----------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Release Update. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
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 = 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.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)