Feature Pack NB_CLT_45_9_F.tar provides fixes for the VERITAS NetBackup (tm) UNIX clients. NetBackup UNIX Add-on products and Database Agents have separate Feature Packs.

Article:TECH44136  |  Created: 2005-01-04  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH44136
Article Type
Technical Solution

Product(s)

Environment

Issue



Feature Pack NB_CLT_45_9_F.tar provides fixes for the VERITAS NetBackup (tm) UNIX clients. NetBackup UNIX Add-on products and Database Agents have separate Feature Packs.

Solution



CLT 4.5FP_6 Pack NB_CLT_45_9_F README October 4, 2005
Corequirement: NB_45_9_F
================================================================================
This Feature Pack provides fixes for the VERITAS NetBackup (tm) UNIX clients.
NetBackup UNIX Add-on products and Database Agents have separate Feature Packs.

Symantec recommends that the backing up of active file systems be avoided,
or the use of snapshot technologies be implemented. The directory structure
reported back from the file system (to NetBackup) may not contain all of the
files available during the time of backup. NetBackup will not report errors
in many cases where the file's existence is not known to NetBackup as reported
by the file system.

================================================================================



=================
PACK DEPENDENCIES
=================

-- 4.5 FP6 must be installed prior to installing this Feature Pack.

-- Installation of this Feature Pack requires that
NB_45_9_F_<6 digit number>.<server>.tar be installed first.

-- Installation of this Feature Pack requires version 1.8.2.25 of the
Vrts_pack.install script.

-- For the latest robotics support please download the latest
Mappings_4.5.<6 digit number>.tar from the support website:
www.support.veritas.com.


I. DOWNLOAD INSTRUCTIONS
II. INSTALLATION INSTRUCTIONS
III. UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_CLT_45_8_F
NB_CLT_45_7_F


=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download the NB_CLT_45_9_F_<6 digit number>.tar into the
/tmp directory,

where <6 digit number> is an internal tracking identifier

NOTE: NB_CLT_45_9_F_<6 digit number>.tar contains all client
binaries.

2) Extract the NB_CLT_45_9_F_<6 digit number>.tar file
tar xvf NB_CLT_45_9_F_<6 digit number>.tar

This will create the files:
VrtsNB_CLT_45_9_F.README
VrtsNB_CLT_45_9_F.tar.Z
VrtsNB_CLT_45_9_F.postuninstall
VrtsNB_CLT_45_9_F.postinstall
VrtsNB_CLT_45_9_F.preinstall
Vrts_pack.install


==============================
II. INSTALLATION INSTRUCTIONS
==============================
There are two ways to install the client Feature Pack software.

1. Remote Installation: Loads the software on a master 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) Install NB_45_9_F and NB_CLT_45_9_F Feature Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

2) Restart daemons.

/usr/openv/netbackup/bin/initbprd
/usr/openv/volmgr/bin/ltid -v

3) Update the NetBackup clients, including the NetBackup master and media
servers, with the update_clients script.

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

where <hardware> <os> is one of the following:
ALPHA OSF1_V4
ALPHA OSF1_V5
DataGeneral UNIX
HP9000-700 HP-UX11.00
HP9000-800 HP-UX11.00
INTEL FreeBSD
Linux RedHat2.2
Linux RedHat2.4
MACINTOSH MacOSXS1.2
MACINTOSH MacOSX
NCR UNIX
RS6000 AIX4.3.3
RS6000 AIX5
SCO UnixWare
Sequent DYNIX420
SGI IRIX65
Solaris Solaris2.6
Solaris Solaris7
Solaris Solaris8
Solaris Solaris9
Solaris Solaris_x86_2.6
Solaris Solaris_x86_7
Solaris Solaris_x86_8

Remember to include the master server's <hardware> <os> type.

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 Feature Pack, the Vrts_pack.install script
will install the client Feature Pack automatically. The client Feature Pack
will NOT be installed automatically during a reinstall of the server Feature
Pack.

Additional Notes:

If non-root administrators use the GUI only, the nonroot_admin
script no longer needs to be run. If the non-root administrators
use the command line or bpadm, the group and file permissions
will have to be changed manually on the NetBackup binaries.
Users can writer their own script. The script is being phased
out because there is a slight security risk that non-root users
may be able to execute NetBackup commands only because those users
are part of a group that is allowed to execute NetBackup commands.

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

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) Install NB_CLT_45_9_F Feature Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install


============================
III. UNINSTALL INSTRUCTIONS
============================
Note: This will ONLY uninstall the Feature Pack from your machine
if the client Feature Pack software was installed remotely
(i.e. software was pushed from a NetBackup Master Server), this
uninstall procedure will NOT work with local client installations.

As root on the NetBackup Master/Media Server in which the Feature Pack 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 pack save directory.
Substitute the pack name for ${PACK} in the following command:

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

3) Run the un-install script:

./Vrts_pack.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/goodies/netbackup start


==================================
IV. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed.
Please read the entire document before installing.

README Conventions:

Description
Describes particular problem or feature contained in this Feature Pack.

** 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, VERITAS strongly
recommends the "best practice" of being at the latest patch level.

Additional Notes
Any additional information regarding this problem or feature is included.


=============
Current pack
=============

================================================================================
Description:
Message lines in LTIerrno.h that begin with spaces instead of a tab are not
found by the search program.

Additional Notes:
The list of messages for MMm errors is changed. This only effects localized
sights.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Scheduler is modified to correctly process a status 134 error race
condition in a multiplex backup.

This condition occurs when a multiplex child bpsched starts a backup, but
the storage unit is over committed. A status 134 is sent back to the
multiplex child bpsched, but the child schedule is already adding another
backup to the multiplexed group.

The child schedule attempts to send the new jobs information to bpbrm, but
bpbrm has exited and the connection is defunct. Scheduler was incorrectly
logging the defunct connection in the job progress log. With this change
scheduler will not log the broken socket, but will correctly read and
process the 134 from the inbound connection.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the sui bit is set on some administrative commands on AIX 5.2, the
system oslevel command will leave a directory in /tmp. This does not happen
for the root user.

(All NetBackup Servers: RS6000)
--------------------------------------------------------------------------------
Description:
bpretlevel loops echoing 'What?' when changing retention levels. No input
seems to be a satisfactory response to exit the loop until a ctrl-C is
entered. There does not seem to be any way to change retention levels
with the command line interface because of this issue.

The following was determined to be the resolution for this issue:

An earlier change had changed all occurrences of gets() to fgets(), but
failed to recognize that fgets() WILL return the '\n', whereas gets()
did not. The subsequent strcmp was not expecting the '\n', and
always failed. The solution is to strip the [new] trailing '\n' to
emulate the gets() behavior.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpbrm can hang if a database agent backup fails in a certain way.
The job will appear to be running in the Activity Monitor until
terminated by the administrator.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected a situation where the scheduler would lose a backup in the middle
of a catalog backup.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed backup jobs would occasionally hang. This would happen if the
bptm or bpdm parent process crashed, or if bptm could not successfully add
the TIR fragment for a TIR backup. It may also happen because of a timing
problem in bpbrm when new jobs are started.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Using Red Hat 3.0 ES, when an Oracle template is created using the Oracle
template wizard of the client GUI, the following warning message appears at
the beginning of the template summary:

"Incorrectly built binary which accesses errno or h_errno directly.
Needs to be fixed."

(NetBackup Clients: Alpha Dgux HP Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
If the add_slave_on_clients command is unable to add the media server
entries to one client, it may incorrectly update the media servers on
subsequent clients. Typically, only one media server will be added to
the remaining clients.

Workaround:
Use the Host Properties GUI to update the server list for the clients.
Use the bpsetconfig admincmd to update the server list for the clients.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bprd cannot clean up a vault session directory containing files that are
larger than 2GB.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Backups of NFS mounts where the NFS server is down, or in single user mode,
time out.

All NetBackup UNIX Clients
--------------------------------------------------------------------------------
Description:
A bpimage -cleanup process fails with the message, "Too many files open"
when using ASCII catalog and FlashBackup policies.

Workaround:
To avoid this issue, run cleanup for a single client at a time.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected the display of the new ACS vendor media types: T10000T1, T10000TS,
and T10000CT. Also corrected the allowable types that is the ACS vendor
media type, LTO_400G.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpdbm may crash if unable to determine host name of the caller.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A SAP online backup is started and a Tablespace (PSAPES46CI) in the Oracle
database is placed in BACKUP MODE by the agent. However the backup receives
a STATUS 134 error in BPTM & BPBRM. The bpbkar, bptm, and bpbrm processes
exit and clean up after themselves. The SAP agent process remains active,
awaiting the backup to be queued and run again, leaving the Tablespace
(PSAPES46CI) still in BACKUP MODE.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
In certain firewall configurations, multistream backups from Linux client
may fail with a status 25 if vnetd connect-back is used.

(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
vmoprcmd -comment <drive_index> <comment_string> overwrites the serial
number specified if the comment_string size is 26.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP restores fail with Hitachi NAS when restoring the entire backup image.
The NDMP log shows the path being sent twice in the NDMP_DATA_START_RECOVER
message.

Workaround:
Restores will work as long as the file system path is not selected (the
path that was initially backed up). If the entire image is needed for
restore, select all the files and directories in the file system path
instead.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
NetBackup processes may core dump if an error occurs. The stack from the
core file showed problems with the ndmp_user_scsi() or ndmp_user_tape()
functions.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type. It does
not take the media type of existing standalone media into consideration.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added a new ID for the duplicated message.

Changed:
ovgetmsg("DmeBrm0166N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );

To:
ovgetmsg("DmeBrm0167N", LC_C, sizeof(lmsgl), lmsgl, lc_messages,
sizeof(cmsgl), cmsgl, "cannot create data socket" );

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When bpbrm encounters an error during backup, bpbkar does not shut down
properly. On HP11.11 platforms, it gets stuck in an infinite loop until
an alarm signal goes off after 300 seconds. This causes millions of debug
messages to be written to the debug log. On other UNIX platforms, bpbkar
shuts down abnormally because of a segmentation fault.

Workaround:
To avoid this issue, turn off bpbkar debug logging on HP11.11 systems.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
An XBSA application would hang during a shared memory backup (such as, the
client and the media server are the same machine) if a problem occurred
that caused the bptm to exit. The BSASendData() call did not return.

(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
The VxFS team changed their implementation of ACLs on VxFS file systems on
the AIX platform. NetBackup was changed to handle this new implementation.

(NetBackup Clients: RS6000_433 RS6000_51 )
--------------------------------------------------------------------------------
Description:
If the bpgetmedia options -h and -M were both specified, the -h argument
would always inherit the -M argument, and the original -h value would be
lost.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When bpbackup is run with the option to wait for the completion of the
backup job, a firewall between bpbackup and bprd can shut down the socket
while bpbackup waits for the completion status. This causes backint to
get stuck in an infinite loop during database backups.

(All NetBackup Windows Clients All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Updated this release to include the most recent device entries.

Fixed the following:
IBM3583 barcode reader recognition issue with newer library firmware.
Quantum PX720 barcode reader recognition issue.

Added the following:
Diligent VTF Open

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.

- NEC T40A
- HP UHDL

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
ACS robot inventory may timeout when ACSLS server is overloaded. Timeouts
increased.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If the forked re-read storage unit process detected a transient error, it
would error, exit, and then remove the scheduler message queues.

(All NetBackup Servers)
================================================================================
=========
NB_45_8_F
=========

Description:
A NetBackup restore that has a path specified to be excluded from the restore,
but that path does not even exist in the backup image, was completing with a
partial success status of 1. Changes have been made so that a backup such as
this completes successfully with a status of 0.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Adjusted a loop used during the deletion of a multiplexed group. This loop
was not functioning correctly on the Windows 2000 platform and resulted in
removal of additional multiplexed groups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"Ghost" backup jobs were appearing in the Activity Monitor.

A deleted backup job could (partially) re-appear. This would only happen
to a deleted job that is one number lower than a multi-copy backup.

Example:
1) Job n finishes.
2) Job n is deleted from the Activity Monitor.
3) Multi-copy job n+1, n+2, n+3 finishes.
4) Activity monitor incorrectly updates jobs n, n+1, n+2.
5) Deleted job n (partially) re-appears.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The interrupt code paths for the Scheduler were simplified to eliminate
scheduler core dumps because the interrupt handlers were too "noisy".

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected potential problems with memory leaks and non-initialized malloc
space.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the scheduler verbose is set greater than 0, there is the potential for
Jobs to exit with a status 50. This is more likely on systems that experience
connection issues. The situation occurs when the scheduler prints a message
and loses the errno value. Armed with the incorrect errno value, the scheduler
exits (status 50) the current running jobs.

Workaround:
To avoid this issue, set the scheduler verbose to zero.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpplschedrec -deldayomonth command deletes a range of days instead of
the specified day.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A backup is established with the following:
- Multiplexing enabled
- Multi-copy enabled
- Continue backup on copy failure

Excessive failure messages are displayed if one of the copies fails, and
additional backups attempt to join the same multiplex group.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
XBP was inserting and deleting items from lists one item at a time. This
was done because of deficiencies in some X-Servers' support of 1.1 Motif.
This is not an efficient way to handle lists with a large number of items.
This problem is not an issue with X-Servers that support Motif 1.2.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
When "Browsing for restore", files that ended in an asterisk (*) or an
angstrom (@) would have that particular symbol (* or @) truncated. This
prevented them from being restored.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
A loss of multiplexed groups within bpsched.exe resulted in the failure to
cancel multiplexed backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
You can now view the correct number of files backed up in the Activity
Monitor.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Update ltid such that it does not leave behind defunct processes when it
spawns vmd.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Bprd hits a segmentation fault and core dumps. The issue occurred when the
log-file path for the bprestore log exceeded 58 characters. This only
occurred when the media server involved was not the master server, and when
FQDN names were used.

To resolve this issue, the command buffer size has been increased to
BUFFLEN (4096), and implemented bounds checking on all string buffers,
where practicable, by using V_strlcpy, V_strlcat, and snprintf().

Additional Notes:
While libVcom.so and netbackup.dll contain no changes, they are required
to resolve new entry points introduced in libsfr.so. In addition,
libsfr.so is Solaris only.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A race condition existed when two restore jobs needed the same piece of
media, from the same server, when this media was not already in the media
database. This condition could cause the media to be added twice, and one
of the restores to fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Improved VMD debug logging to better enable analysis for slow servers.

Allow control of VMD child timeout, such that slow servers can be
interrupted, before VMD encounters connection timeout's on other
connections.

Add "VMD_CHILD_TIMEOUT = xx", to the vm.conf file. xx is the number of
seconds to wait for a child to release its lock on the volume database.
Allowable time is 60 to 360 seconds, where 360 is the default (a value
used prior to this patch).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
On a heavily-loaded AFS server, it is possible that the volserver will
not be able to keep up with the demands that NetBackup will make, resulting
in backups failing with an error 78. This is especially noticeable when
using multiple streams. While the errors cannot be eliminated, the user
can implement a retry on the failed vos commands it would reduce their
frequency.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
During an alternate client restore of Informix, the physical restore is
successful. However, the logical log restore always fails while restoring
the last log requested. This happens whether the restore is a full
restore, point-in-time restore, or a point-in-log restore.

The transaction appears to be complete on the client and the client
disconnects the socket connections to the media server. The media server
is not expecting this and exits with status 24.



(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpfis closes all file descriptors after exiting. (This includes the file
descriptor that Hitachi Shadowimage is using.) This causes 'bpfis delete'
to hang for ShadowImage snapshot backups.

(NetBackup Clients: HP SOLARIS Solaris9 )
--------------------------------------------------------------------------------
Description:
SCSI-3 library commands have standardized on op code 0x37 for the command
INITIALIZE ELEMENT STATUS w/RANGE. Previous implementations by numerous
vendors had used vendor-unique code 0xE7 - which was implemented by
NetBackup. SCSI-3 libraries will return sense data 20/00 when sent an E7.

Workaround:
To avoid this issue, use only tapes with barcodes that are valid for your
library.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup was not properly examining the SCSI library mailslot status bits;
therefore, during ejects of more than a MAP-full of media, the eject
operation may abort after the first MAP-full is removed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
While trying to reduce the size of a database, the command "bpimage -
cleanout -client dill-bk" was used. Using the command in this way caused
bpimage to core dump.

Workaround:
To avoid this issue, allow the nightly clean-up process to clean the
catalog.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
It was possible that the bpjobd process may hang under certain conditions.
It has been demonstrated that this can happen if bpduplicate and bptm
processes are killed, but it may occur in other situations. The bpjobd
process does not die, it just loops consuming CPU time, and nothing
is written to the debug log. This prevented the job DB from being updated
with the status of existing jobs, or new jobs. bpjobd must be killed and
restarted by the system administrator to resolve this problem.

This problem is indicated by the following data in the bpjobd debug log,
referring to non-existent job ID 3:

18:45:00.734 [17433] <2> process_active_job: Frame type is 3 (jobid 3)
Sock (93)
18:45:00.734 [17433] <2> process_active_job: Adding provider(1) for job(3)
socket (93)
18:45:00.734 [17433] <2> process_active_job: Begin to write (JOBTRYFILE) at
offset 68 job (3)

Workaround:
To avoid this issue, kill and restart the hung bpjobd.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A large number of down storage units would result in and apparent
scheduler hang. In reality, the scheduler was timing out to each media
server in series. This fix recognizes and skips duplicate attempts to a
down media server.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
To assist image database cleanup in 24x7 environments, image database
cleanup will always run in background. bpsched will not wait until the
cleanup is complete before scheduling new jobs. In addition, bpsched will
initiate an image database cleanup at periodic intervals, 12 hours by
default. The time interval may be changed by using the
bpconfig -cleanup_int <hours> command. For example, to change the interval
to 24 hours, execute the following command:

bpconfig -cleanup_int 24

Use a value of 0 to disable bpsched from starting the periodic image
database cleanup. The maximum value is 744 hours. Bpsched will still
perform an image database cleanup at the end of a session, however, it will
be run in background. On UNIX systems, bpadm may also be used to change
the interval.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The predict algorithm was not sorting correctly. It failed to position
cumulative incremental backups before the differential incremental backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler debug log was filling with the following message:

"storage unit was not assigned for clientjob <host name> <policy name>
<stunit name> <copy>"

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A multiplexed TIR duplication would fail if the prior backup duplication
had a TIR size greater than 1 Gigabyte, and would lead to a bptm crash.

Workaround:
To avoid this issue, retry the duplication using non-multiplexed
duplication. It is also possible that the duplication will succeed by
trying multiplexed duplication.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following changes have been made:
- Added the drive, IBM 3592J
- Add the following new libraries:
- HP EML E-Series
- EMC Disk Library
- STK L7
- STK SL500
- STK Virtual Library
- Adds fixes for eject issue with the ADIC libraries.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support for the following drives and media types for ACS:
- Drives:
- STK 10000A (T1)
- HP LTO-3
- Media:
- T10000T1
- T10000TS
- T10000CT
- LTO-400G

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If an SSO drive is DOWN on all servers, and its scan host unregisters
(services are shutdown), vmd/DA will not transfer this drive to another
scan host. If the drive is brought UP on a server(s), it will have no
scan host, and will stay in the NO-SCAN state.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some FlashBackup backups would take longer on NetBackup 5.0 than they did
for NetBackup 3.4 because of additional overhead of the binary catalog.

Workaround:
Raise the maximum files per add value using the
/usr/openv/netbackup/MAX_FILES_PER_ADD to 9500, which will raise the limit
for all backups.

Additional Notes:
The number of files added per call to the catalog has been raised to 95000
from 500 for FlashBackup. This limit can be modified by putting the
desired value in /usr/openv/netbackup/FBU_MAX_FILES_PER_ADD, which only
affects FlashBackup backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.

- EMC Disk Library
- QUANTUM ValueLoader
- HP MSL6000 Series
- STK SL500
- STK L7

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A system panic occurred when a snapshot was being closed at the same time
as another snapshot tried using the same cache partition as it was being
read. The panic was because the partition was a DRL-enabled VxVM volume
that had not been opened by the snap driver, and the DRL threads were being
destroyed while the read was attempting to access them.

Workaround:
To avoid this issue, remove DRL from a cache partition if it is a VxVM
volume.

(NetBackup Clients: SOLARIS )
--------------------------------------------------------------------------------
Description:
vmphyinv is unable to read the tape header in NDMP drives. This affects
NDMP drives and the NetWare media server (that are handled using NDMP
protocol).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler would take a long time scheduling multiple data stream jobs
if there were many policies that were due to be autodiscovered at once.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When selecting a media ID for backup, if the allocation date in the
media database does not match the assigned date in the media manager
database, FREEZE the media because there could be database inconsistencies.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multiplexed jobs can hang if the DATASOCKET message is not recognized.
A log message of "unknown media message DATASOCKET" will appear in the
bpbrm debug log.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
During multiplexed restores, when multiple tar instances are restoring
files onto the same directory tree, some of the files may not get restored.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
If a set of configuration options in bp.conf is very large, it can cause
bpgetconfig and the GUI to not display any of the items. This applies to
items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.

Additionally, if that set of configuration options is edited in the GUI,
for example to add a new server to the CONNECT_OPTIONS, all of the previous
data for that set of options will be lost and only the new data will be in
bp.conf.

Workaround:
To avoid this issue, you should reduce the number of configuration options
with the same name.

(All NetBackup Servers)
--------------------------------------------------------------------------------
** Description:
In a rare circumstance, the last block of a multiplexed, duplicated copy of
a TIR backup may be corrupt. A verification of the copy would not be
successful. The original backup is not affected. This does not affect
non-multiplexed duplications of a multiplexed TIR backup.

(All NetBackup Servers)



=========
NB_45_7_F
=========
Description:
Managing calendar-scheduled backups when the master server is in a
different time zone than the Administration GUI causes the jobs to run in
a restricted time window or not at all.

There is no longer a limit on the number of calendar include/exclude dates
within a schedule.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bptm core dumped when the TPC buffer size was set to 256K, and the backup
included a directory with lots of files of less than 512 bytes. The TPC
mover was a Pathlight, which advertises a maximum number of segments per
command of 256, but will support over 4096.

Workaround:
Reducing the TPC buffer size to 128K or less will eliminate the failure.

(All NetBackup Servers: HP RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The error message displayed when unable to obtain device target information
from the 3pc.conf file was being overwritten with "device not found." This
makes it impossible to detect certain misconfiguration errors.

(All NetBackup Servers: HP RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Check to make sure a groups entry exists in the xinetd files for the
Macintosh 10.1 client. If there isn't one, remove the existing xinetd file
and create a new one.

(NetBackup Clients: MacOSX10.2)
--------------------------------------------------------------------------------
Description:
Add an exit 0 after checking for NBAR processes. If NBAR is present but not
up, the grep causes bpps to end with a non-zero exit status. GDM, at a
minimum, checks bpps' exit status.

(All NetBackup Servers: HP RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
NetBackup re-initializes the ADIC Scalar 10K library (causing the library
to be inventoried) before downing the drive in the event of a hardware
error on the drive.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
AIX added a proc file system and mount.c needs to be able to identify it so
bpbkar can automatically skip it (as it does for other operating systems
with a proc file system).

(NetBackup Clients: RS6000_433 RS6000_51 )
--------------------------------------------------------------------------------
Description:
After using the job monitor to terminate a backup, the bpbkar process
on the client can sometimes hang in exit processing looking for a status
message that was already sent.


(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Extended copy backups may fail on HP UX media servers (using an HP Tachyon
fiber channel HBA) due to a tape position miscompare. The tape is then
frozen and the backup fails with an error code 174.

(All NetBackup Servers: HP)
--------------------------------------------------------------------------------
Description:
Imports or verifies with detailed logging can take much longer than
without detailed logging.


Workaround:
When performing an import or a verify, do not request detailed logging.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores of remote clients initiated from a NetBackup server with detailed
logging can take much longer than restores without detailed logging.


Workaround:
Do not request detailed logs or initiate the restore from the remote client.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In some restores from multiple images on the same tape, more than one
image restore can be started at the same time causing bptm to core dump.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a file has VxFS attributes such as reserve or fixed extent size, a
FlashBackup file restore would fail resulting in a zero length file.

(All NetBackup Servers: HP Intel-NT RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The bpbrm -stream_count argument is not correct for frozen image or split
mirror backups. The error manifests itself in the "-stream_count" being
zero for stream number 1, and 'n-1' for streams 2 through n.

It is worse for frozen image or split mirror backups using retention
level 24: the -stream_count argument is zero for all streams.

Workaround:
1) Stagger multi-stream frozen image job start windows.
2) Avoid retention level 24 for multi-stream frozen image jobs.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpsched process core dumped and left a child process still running. The
remove_from_mpxgrp_activelist() function attempts to free pool information,
but the pool pointers are really residue. Changed add_to_active_job_lists
() function to initialize the malloc'd structure.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When starting a backup using -i (immediate), and -L (logging) turn on
progress logging for the client, the job doesn't appear in the bpjobd
monitor (Activity Monitor). I get the following error in the
bpjobd debug log: Jobid came as 0.

Currently adding formal ability to use backup progress logging on clients
when using the bpbackup -i, which is currently disallowed by bprd and
bpbackup. Also, note that bpbkar is successfully receiving the -L
option, so bpsched seems to pass along the log file successfully.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpsched core dumped on active node of VCS cluster while running jobs.

The problem is: the fixing of memory leaks went a little too far here
and tried to free a literal character pointer.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
On the Firewall tab of Host Properties in the Windows GUI, the settings
for existing clients change when new clients are added or deleted from the
list.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpdgclone command fails when a volume has a VERITAS Volume Manager
(VxVM) Data Change Object (DCO) log.

Errors similar to the following appear in the online_util log:

09:33:22.155 [27646] <2> onlfi_vfms_logf: INF - make_new_vol:
executing /usr/sbin/vxmake -g clone_hdsdg_clone < /var/tmp/DGCLBAAquaGd2
09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - vxvm:vxmake: ERROR:
Dco my_test_dco not in configuration
09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - vxvm:vxmake: ERROR:
getting associations of :
09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - Bad record name
09:33:22.156 [27646] <2> onlfi_vfms_logf: INF - could not vxmake
from input file /var/tmp/DGCLBAAquaGd2

(NetBackup Clients: HP SOLARIS )
--------------------------------------------------------------------------------
Description:
This change includes version 3.23.58 of MySQL for nbdbd.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
During an NDMP restore, and even though the NAS server reported a
NDMP_DATA_HALT_CONNECT_ERROR, NetBackup reports the restore as successful.
(Note: Receiving an NDMP_DATA_HALT_CONNECT_ERROR is rare. Most NAS servers
report an NDMP_DATA_HALT_INTERNAL_ERROR instead.)

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When doing a Remote NDMP backup, the backup hangs after hitting EOM several
times.

This occurs when the tape hits end of media at the very end of the backup
while Remote NDMP is attempting to flush its internal buffers to tape.

Workaround:
Retry the backup with a different tape. This condition is not likely to
occur a second time on a different tape.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
If an inline tape copy job starts with multiplexing set to 1, another job
with multiplexing set greater that one will attempt to multiplex with the
first job. The multiplex setting of 1 on the first job caused the job to
run without multiplexing enabled. The second job will fail because it
cannot multiplex with the first job.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A restore from a Remote NDMP backup that spans tapes may indicate an error
occurred. This happens only with Remote NDMP on a Windows machine.

The bptm log shows "read_data_ndmp returned 0" which indicates the restore
was OK. Following this there is an MTFSF 1 tape command that fails with
IO_ERR.

Workaround:
This error can be ignored. Because read_data_ndmp returned good status, the
restore was successful. It is only the tape positioning that failed.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in the following
robotic libraries. The drives are properly configured within the library,
instead of being configured as standalone drives.

- Dell PV-122T
- Sony CSM-200
- Sepaton S2100

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a restore fails because of a media mount timeout, bprd may core
dump when it finishes processing the restore.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 134 status results in multiple tries in the Activity Monitor even though
they are not counted as tries.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If bpschedreq -predict is executed with a time that is not the current day,
the exclude dates will not be taken into account.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An imported backup of a backup copy other than copy 1 would base the
expiration time on the backup time rather than the current time, which
would result in the imported backup expiring too early.


Workaround:
The bpexpdate command may be used to change the expiration of the imported
backup.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When multiple densities are used in the same robot, not all drives will be
used.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Expiring one of the images from a multiple data stream backup causes a
restore to fail even though the images still exist.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some files or directories show up in the wrong locations during restore
browsing or queries.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Calendar scheduled jobs may not run when administered from a different
time zone.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Collection of disaster recovery information from Windows clients fails.
The symptoms of this problem include:
1) Policy is configured to collect disaster recovery information.
2) Server connections to the client are supposed to use vnetd.
3) A firewall is present between the servers and the client.
When the server attempts to connect to the client to collect the disaster
recovery information, it will not use vnetd and it will fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Auto path correction will down drives that have a valid path, but do not
respond to commands. This patch allows auto path correction to down drives
that do not have valid paths.

This allows ltid to start even with missing paths.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added the ACS_CSI_HOSTPORT and ACS_SSI_INET_PORT entries to vm.conf. This
allows these variables to be set in the vm.conf and used to start acsssi
when a firewall is between the NetBackup server and the ACSLS server.

Additional Notes:
SysAcs0354V "%s(%d) Could not set ACS_CSI_HOSTPORT in ACS SSI environment"
SysAcs0355V "%s(%d) Could not set ACS_SSI_INET_PORT in ACS SSI environment"


(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Fix memory leak during tar restore of migrated files.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Restore paths incorrect for NDMP path-based history.

The list of files for an NDMP backup image are missing the original backup
path. This occurs with path-based file history running NDMP V4.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The bpvxver script returns version 1.0 of VxVM on HP-UX, in certain cases.

(NetBackup Clients: HP )
--------------------------------------------------------------------------------
Description:
When automatic path correction is enabled, some robotic paths may be
incorrectly changed if the customer has a mix of serialized and
unserialized robots.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 174 error (media manager - system error occurred) occurred when an end-of-
media status was returned while trying to write a end-of-file marker on the
tape. This may occur on the Windows or SGI platforms. The bptm log will
show an entry similar to the following:

00:30:40.803 [3256.4608] <2> io_ioctl: MTWEOF encountered EOM (error 1100),
return EOT

This is followed by an entry indicating "buffers out of sequence", and the
174 error.

(All NetBackup Servers: Intel-NT SGI)
--------------------------------------------------------------------------------
Description:
NDMP dump levels are always 1.

Additional Notes:
This fix was integrated into the NetBackup 4.5MP path, but the
NetBackup 4.5FP and 5.0 paths were missed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler "predict" is out of sync with what actually gets run.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The online_util log is flooded with the unnecessary message "Unable to
obtain mount point", which causes a slowdown in FIM backups.

(NetBackup Clients: HP SOLARIS )
--------------------------------------------------------------------------------
Description:
The UNIX bpbkar would sometimes error while processing a long pathname
with a large number of sub-directories. The problem manifests itself
intermittently, depending on number of sub-directories in the long
patch name, memory on the box, stack size, etc.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
During Shadowimage backup, a status check on either the primary disk or the
secondary disk is needed to determine the state of the array. NetBackup now
checks the primary disk instead of the secondary disk.

(NetBackup Clients: HP SOLARIS )
--------------------------------------------------------------------------------
Description:
NetBackup for NetWare server side client components require hosts file to
work.


Workaround:
Update the hosts file on the NetWare server with the correct information
for the NetBackup server.


Additional Notes:
These changes, compiled in the NetWare code, are needed to resolve host
addresses through the DNS server, if they do not exist in the sys:etc\hosts
file. DNS support must be configured on the server.

For NetWare, update all NLMs in the SYS:VERITAS\NBUCLT dir. They are:

BPCD.NLM
BPSRV.NLM
BP.NLM
BPSTART.NLM

(NetBackup Clients: Novell )
--------------------------------------------------------------------------------
Description:
Drives keep going down every few days. Avrd reports semaphore errors
similar to the following in /var/adm/messages:

messages.0:Oct 28 21:56:28 server1 avrd[8148]: Error in Semaphore
Operation - Result too large
messages.0:Nov 1 03:20:54 server1 avrd[18968]: Error in Semaphore
Operation - I/O error
messages.1:Oct 20 01:31:34 server1 avrd[26744]: Error in Semaphore
Operation - I/O error

Workaround:
To avoid this issue, down the NDMP drives that are not working.


(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Resolves a potential Dr. Watson on Windows NT if an NDMP drive path name is
too long (exceeds the stack). The new maximum length for drive path name is
128 characters.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Two different strings were assigned to the same key. This issue has been
resolved.

(NetBackup Clients: HP SOLARIS )
--------------------------------------------------------------------------------
Description:
If a client is down when the scheduler is doing autodiscovery, and the
Windows GUI attempts to modify a policy, the policy may get deleted.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Sybase backups fail occasionally with a 143 error if the scheduler is
unable to connect to the client while writing the progress log.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NDMP backup restore can fail because some NDMP venders do not use "2" as the
mount point inode number.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Updated acsssi to include the firewall support from STK for ACSLS.

(All NetBackup Servers: HP Linux2.2 RS6000 SGI Solaris)
--------------------------------------------------------------------------------
Description:
On UNIX systems, the tldcd and tl8cd robotic daemons may fail if
connections are opened and closed quickly with no data.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When doing an oracle proxy copy, the DB files are treated as sparse files.
When the proxy copy backup is combined with local host or alternate
client off host backup, bpbkar reads the entire file to build the spares
array. This activity, for large DB files, can take a long time to finish
and cause a performance drop in comparison to a standard backup.

(NetBackup Clients: HP SOLARIS Solaris9 )
--------------------------------------------------------------------------------
Description:
Oracle Server Free with an alt-client does not work if multiplexing is
enabled. This change also improves snapshot error handling during snapshot
creation and deletion.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When restoring NAS data from an NDMP-attached tape drive, the bprecover
command fails with an EOM (end of media) error.

Workaround:
To avoid this issue, use a non-NDMP drive.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
In Eject/Inject operations with the vmchange command using the -w flag, a
user has 5 minutes to tell the system to continue, after they are prompted
to add remove volumes from the media access port. This 5 minute timeout is
not configurable.

This timeout can now be controlled using the vm.conf option
MAP_CONTINUE_TIMEOUT, on the robot control host.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A missing tape unmount on one of the copies when using Inline Tape Copy may
cause unnecessary 134 status codes (unable to process request because the
server resources are busy).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing drive cleaning from the java GUI, drive names with more
than 22 characters could cause problems for the GUI.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpjobd stops responding. The last few entries in the bpjobd log file
indicate multiple attempts to establish a connection from a client. The
Client was interrupted during the first connection handshake and began the
connection procedure again. This situation causes a deadlock condition.

Workaround:
To avoid this issue, restart bpjobd and then kill the offending client. You
can use netstat to find the client.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bppllist -allpolicies or <policy> -U core dumps

Workaround:
1) Look for a policy that has an unusually long value for one of its
attributes, such as the keyword, or a policy that has many clients.
2) Run 'bppllist <policy name> -U' to display this one policy.
3) If bppllist aborts, modify the policy to reduce the length of
the long value.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Scheduler gets an occasional core dump when it is preparing to exit. The
error happens when trying to determine which storage units are busy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Using a Binary Catalog could cause an inability to browse for restores under
certain file selection lists. This issue has been resolved.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Customers using noauth authentication with the NetBackup Administration
Console for Windows would not be able to start manual backup jobs if they
were not an Administrator on the system running this Windows GUI.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Suppose the master server and media server are different servers. Also
suppose that the media server and client are the same machine so that
shared memory backups and restores are normally done.

Suppose the master server is configured so "connect backs" with the media
server are done using VNETD. The typical bp.conf entry on the master server
would look like this:

CONNECT_OPTIONS = mediax 0 1 2

Where "mediax" is the hostname of the media server. The digit "1"
signifies that vnetd style connect backs are used.

In this case, restores will fail. Typically, the job will fail with error
code 5 and be marked as "incomplete" in the job monitor.

Workaround:
Do not use VNETD style connect backs with the media server if the media
server is also a client.

(All NetBackup Windows Clients, All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Exchange backup does not support the bandwidth limitation setting.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected an end-case problem in multiplexed read processing (for
restores/duplications) that may try to unmount a media that is already in
use by another process.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When verifying very large backup images, the Activity Monitor would
incorrectly report a failure status that included a ?client process
aborted? error message. Testing showed that the verify job had not
actually failed and the incorrect status was displayed because the
keep-alive checks were not being sent to bpjobd if the bpbrm socket was
active for specified amount of time. This time interval to send
keep-alive packets has been corrected, resolving this issue.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Novell has recently decided to replace TSA600.NLM with TSAFS.NLM on
NetWare 6. TSAFS.NLM previously only supported NetWare 6.5. The updated
TSAFS will be released in an upcoming service pack. Customers who apply
this service pack will get an error message when they load the NetBackup
Client for NetWare after this patch has been applied.

Workaround:
Ignore the error from the NetBackup Client for NetWare when loading it on a
NetWare 6 server where TSAFS has replaced TSA600.

Additional Notes:
This fix will (on a NetWare 6 server only) first unload TSA600 if it is
found in memory. It will then attempt to load TSAFS.NLM. If TSAFS.NLM
cannot be loaded, it will load or reload TSA600.NLM.

This change effects only BPSTART.NLM.

(NetBackup Clients: Novell )
--------------------------------------------------------------------------------
Description:
Occasionally on RedHat Advanced Server 3.0, NetBackup does not detect
drives going from ready to not ready and then to ready again with a
different tape label.

(All NetBackup Servers: Linux2.2)
--------------------------------------------------------------------------------
Description:
Novell has started distributing its own version of DOS with the latest
NetWare 6.5 installation CDs. This version of DOS does not support certain
operations that NetBackup performs at startup; therefore, if this version
of DOS is used, it will cause the server to abnormally terminate.

Workaround:
Do not allow the Novell Installer to install Novell Loader for NetWare 6.5
installations.

Additional Notes:
This change effects BPSTART.NLM.

(NetBackup Clients: Novell )
--------------------------------------------------------------------------------
Description:
A typographical error in the close_job_disconnect() function code corrupts
the
socket when bprd trying to disconnect from jobd.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a backup image was originally written by NetBackup 3.1.1 and is then
archived using the NetBackup FP5 catalog archiving feature
("bpcatlist|bpcatarc|bpcatrm"), the .f file will be deleted without the
ability to use "bpcatres" to restore the file.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The FORCE_RESTORE_MEDIA_SERVER does not replace the server entry for TIR
fragment. Thus, when TIR information needs to be extracted from tape, bpdbm
tries to initiate a "bptm -restoretir" on the original server.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Backups of large sparse files on SGI could result in bpbkar hanging and
failure of the backup.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
The Device Configuration Wizard can now configure drives in HP ESL E-Series
robotic libraries. The drives are now properly configured within the
library, instead of being configured as standalone drives.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
On a multimedia type robot, robotic inventory was failing while inserting
media into the volume database. The inventory operation successfully inserts
media of one type but fails while inserting media of another type.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When restoring TIR incremental data, directories could be restored with
incorrect permissions.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
Restoring a large file (greater than 2 GB) that has Solaris 9 extended
attributes returns partially successful with an error message, even though
all files and extended attributes are restored successfully.

(NetBackup Clients: Solaris9 )
--------------------------------------------------------------------------------
Description:
Provide the ability for the user to control the format of the drive names
that are created by the Device Discovery Wizard.

Additional Notes:
The following variables could be used in generating a drive name:

- HN - hostname of the server where the drive is first discovered
- RN - robot number
- RT - robot type
- POS - Drive position, determined by robot type. One of the following:
- robot drive number
- vendor drive id
- ACS.LSM.PANEL.DRIVE
- SN - serial number of the drive
- DT - drive type (i.e. hcart, 8mm, dlt2)
- VEND - vendor ID of the drive obtained from the inquiry string of the
drive
- PROD - product ID of the drive obtained from the inquiry string of the
drive literal strings proceeded by a pound sign(#) containing
the allowable characters in a drive name.
- IDX - ensure an index is appended. Otherwise, an index will be
automatically be appended if needed to make a drive name unique.

Note: Any white space in the above entries will be collapsed.

These entries will allow a tiered approach. If the DRIVE_NAME_SEED
entry appears on a non-global-database host, that format will be
used. Otherwise, the vm.conf file on the global database host will
be checked for a DRIVE_NAME_SEED entry. If one exists, it will be
used. If none exists in either location, the default naming scheme
will be used. For tpconfig this is "Drive" followed by a number to
make it unique. For tpautoconf, this is VendorID, followed by
ProductID, followed by a number to make it unique.

EXAMPLES:
1) To generate the default names used by discovery provide the entry:

DRIVE_NAME_SEED = VEND:PROD:IDX

This will produce drive names of the form

QUANTUMDLT70000

2) To generate the names that contain the drive's product ID and
robot residence information, fields separated by minuses:

DRIVE_NAME_SEED = PROD:#-:RT:#-:RN:#-:POS

This will produce drive names of the form

DLT70000-TLD-0-1

Issues and Limitations

Some of the below items are just general drive naming issues, while others
relate specifically to this feature.

1. In a shared storage (SSO) environment drives will be named based on
the seed of the first host that discovers them. Subsequent hosts
will retain that drive name regardless of the value of their local
DRIVE_NAME_SEED vm.conf option.

2. The Hostname (HN) should be used with caution in SSO
configurations. Drives shared amongst hosts must have the same
name. See 1 above.

3. Drive names remain limited to 48 characters.

4. Valid characters are upper and lower case alphanumeric, plus, minus,
underscore, and period.

5. Drive names cannot start with a minus (-) character.

6. If robot residence information is used to generate the drive name, the
host that has the robot attached should be discovered first.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Provide a facility to swap drives without requiring the user to delete and
re-add drives, or re-run Device Discovery.

Additional Notes:
The following example shows how the -report_disc command is used to report
discrepancies between detected devices and Global Database. In addition,
an example of how to use the -replace drive_name -path drive_path command
is included.

# /usr/openv/volmgr/bin/tpautoconf -report_disc

======================= New Device (Tape) =======================

Inquiry = "QUANTUM DLT8000 0250"

Serial Number = PXB08P3242

Drive Path = /dev/rmt/119cbn

Found as TLD(6), Drive = 1

===================== Missing Device (Drive) =====================

Drive Name = QUANTUMDLT800014

Drive Path = /dev/rmt/9cbn

Inquiry = "QUANTUM DLT8000 0250"

Serial Number = PXB08P1345

TLD(6) definition Drive = 1

Hosts configured for this device:

Host = dandelion

Host = avocadocat

# /usr/openv/volmgr/bin/tpautoconf -replace_drive
QUANTUMDLT800014 -path
/dev/rmt/119cbn

Found a matching device in global DB, QUANTUMDLT800014 on host
dandelion

update of local DB on host dandelion completed

globalDB update for host dandelion completed

Found a matching device in global DB, QUANTUMDLT800014 on host
avocadocat

update of local DB on host avocadocat completed

globalDB update for host avocadocat completed



(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Backups with exclude and include lists can incorrectly back up excluded
directories (except the files within those directories).

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
A file descriptor leak caused VxVM snapshot backups to fail with an
error 77.

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
On a system running Windows 2000 (SP4), you may not be able to browse or
restore the second volume if 'SET HIST=N' is listed in the middle of the
policy's file list.

Workaround:
To avoid this issue, contact your Symantec customer support office for help
on manually fixing your catalog files.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Duplication of multiple copies using Inline Tape Copy may fail with a 20
error (invalid command parameter). The bptm log (the write side of the
duplication) shows an entry similar to the following:

14:55:48.274 [5586] <16> bptm: not enough parameters specified

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A media position error can occur when attempting to restore from a copy of
a backup created by Inline Tape Copy. The bptm log will show an entry that
is similar to the following (note the file number of 0):

13:12:27.348 [22187] <2> mpx_read_init: media id A00001, copy 1,
fragment 1 (839680 Kbytes) filenum 0 being considered for restore

The problem occurs when performing multiplexed backups using Inline Tape
Copy, and a new backup is started while waiting for a tape mount due to
hitting end-of-media.

Workaround:
To avoid this issue, the restore may be done from the other copy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using Inline Tape Copy, the wrong media-id may be frozen when a media
error occurs on a copy other than the first copy. This happens when the
fail-on-error attribute is set for the failed copy. In this case, the
media-id for the first copy is frozen rather than the media-id for the copy
that obtained the error.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpdbm log shows the following when trying to browse for files in the
restore browser:

17:05:07.264 [40258] <16> decompress_dbfile: system()
returned 256 (1) 17:05:07.577 [40258] <16> list_files: cannot
decompress /usr/openv/netbackup/db/
images/alex/1072000000/Production_Windows_1072660144_FULL.f.Z

This is because compression returns status 256 when dealing with files of a
size less than a block.

Workaround:
To avoid this issue, ignore the error message in the log.

(All NetBackup Servers: Alpha)
--------------------------------------------------------------------------------
Description:
The bprestore command fails with the error message "No files matched file
path for a date range"

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restoring symbolic links owned by non-root could show an error even though
the symbolic link was successfully restored (giving Partial Success for the
restore job).

(All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
bptm fails with a segmentation violation when a media Disk Staging storage
unit sends a duplication job to the master. This issue has been resolved.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
VOPIE Enhanced Authentication may not work when host names are longer than
32 characters. As a result, you may see Authentication Failed (error code
160) messages when connecting to systems with host names or client names
greater than 32 characters.

(All NetBackup Windows Clients, All NetBackup UNIX Clients)
--------------------------------------------------------------------------------
Description:
A possible buffer over-run may be corrupting the eject information in
memory, causing ACS ejects to fail because the CAP was reported as not
existing, when in reality it did exist.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Exchange restores from multiple images fails with a communications failure
error. The log will have a message similar to the following:

17:58:45 (158515.002) ERR - unable to create object for restore:
Microsoft Information Store:\SG01102\Log files_1074011439 (BEDS
0xFFFFFE30: A communications failure has occurred.


Workaround:
Create a file named /usr/openv/netbackup/NON_MPX_RESTORE to force
sequential restores from multiple images.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The timeout for an ACS query is configurable using the ACS_QUERY_TIMEOUT
entry in vm.conf. The value of this entry is in minutes, for example:

ACS_QUERY_TIMEOUT = 30

This sets the timeout to 30 minutes.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support for the SDLT-600 drive type and the SDLT_2 media type to
the ACS robotics.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Single MAP ejects may not query the ACSLS server for the correct MAP
causing the eject to fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The mount/unmount feature makes a "system" call in order to run its callout
scripts. This feature ran into an issue on Red Hat 3.0, where the "system"
call would return the wrong value. When the wrong (non-zero) exit status
comes back to LTID, it downs the drive.

Workaround:
If you are having an issue with the Mount/Unmount callout scripts and you
are not using them, move the two scripts (drive_mount_notify and
drive_unmount_notify) to another place or rename them.

Additional Notes:
To fix this issue, the shell script "drive_unmount_notify" is being
altered. If you
changed this script and would like to retrieve your changes. you can get it
from
/usr/openv/pack/NB_45_7_F/save. It will be part of a tar ball that will be
named
pre_NB_45_7_F.<date>.tar.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce
unnecessary unmounts/re-mounts during Vault sessions.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using "bpexpdate -recalculate" or "bpexpdate -backupid" to extend the
expiration date of one or more backups that have multiple copies, the media
expiration may not be correct for copies on removeable media if the first
copy is on disk.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Windows 2000 platforms were losing multiplexed groups. The user could
not cancel orphaned jobs within the multiplexed group, and additional jobs
could not be added to the multiplexed group.

Windows-specific code was added to display questionable pointer values
prior to releasing the multiplexed group. Historically, this minor change
resolved the problem because it was determined that the problem was a
Windows 2000 compiler optimization issue. This fix either masks the
problem, or helps isolate it.

(All NetBackup Servers)
================================================================================


Attachments

NB_CLT_45_9_F_279434.tar (86.6 MBytes)


Legacy ID



279434


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


Terms of use for this information are found in Legal Notices