Maintenance Pack NB_45_9_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) NT server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

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

Product(s)

Environment

Issue



Maintenance Pack NB_45_9_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) NT server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Solution



NB 4.5MP6 Pack NB_45_9_M README September 20, 2005
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup (tm) NT server
and clients. It also contains fixes for NetBackup Add-on products and Database
Agents.

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 MP6 must be installed prior to installing this Maintenance Pack.

-- For the latest robotics support please also download and install the
latest Mappings_4.5.<6 digit number>.zip from the support Web site:
http://www.support.veritas.com .


I. DOWNLOAD INSTRUCTIONS
II. KNOWN ISSUES
III. INSTALLATION INSTRUCTIONS
IV. UNINSTALL INSTRUCTIONS
V. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_45_8_M
NB_45_7_M

=========================
I. DOWNLOAD INSTRUCTIONS
=========================
This is an update to NetBackup/Media Manager products
with the latest fixes for Windows NT NetBackup servers.

Download instructions:
1) Download the NB_45_9_M.winnt.intel_<6 digit number>.exe file
into a temporary directory.

where <6 digit number> is an internal tracking identifier

2) Extract the NB_45_9_M.winnt.intel_<6 digit number>.exe
by double-clicking on it.

This will create a number of files that include:
README.NT
and
Setup.exe


=================
II. KNOWN ISSUES
=================
The following are known issues with NB_45_8_M. Please note that
these known issues will NOT be resolved after installing this pack.

Description:
RSM libraries do not work currently with Windows Server 2003.
There is a possible RSM API problem with the OS.

Description:
IDR is not supported in MP3 for Windows Server 2003.

Description:
BE tape reader with any version of NBU (4.5 FP3/MP3), will not work
with Windows Server 2003. This is because BE tape reader uses
Backup Exec 8.6 to restore tapes and Backup Exec 8.6 does not work with
Windows Server 2003.

**Description:
NetBackup for Lotus Notes does not support the file list directive,
ALL_LOTUS_DATABASES.

Workaround:
Add the Domino data directory, containing the database files with
extensions .nsf, .ntf or .box, in the file list instead of using the
ALL_LOTUS_DATABASES file list directive. There will be an increase in
performance since the NetBackup for Lotus Notes extension does not have
to parse the file system for .nsf, .ntf or .box extensions.

Description:
NetBackup extension for Lotus Notes is not supported in the
Microsoft Cluster environment (MSCS). NetBackup does support Lotus Notes
in a non-clustered configuration.

Description:
When configuring a Vault profile, if the user goes with the default
selection criteria for Media Servers (on the Choose Backups tab),
which is "<all media servers>" (this default is probably good for most
configs), and if the user uses Advanced Configuration for the
Duplication step (more likely for bpvault 3.4 users who upgrade to 4.5),
but specifies fewer Duplication Rules than there are Media Servers,
then a heavy warning message box should appear, warning the user
that this configuration may create unexpected behavior and may send
duplication data (backup images) over the network. (In a fully connected
SAN environment where every media server has access to the robot,
this shouldn't be a problem.) This warning box does not appear,
so we may have lead the user blindly into a problematic
configuration which will cause excessive network traffic.

Description:
If a Vault profile is configured to do a catalog backup (highly likely),
and if the catalog is too big for one tape, causing the user to configure
the Catalog Backup step with a backup policy (2-phase catalog backup),
and if, at runtime, the backup policy phase of the catalog backup step
fails, then an empty tape from the catalog backup volume pool
will be left assigned (but unused). This tape will never be used by
NetBackup until the user realizes that it's assigned but empty,
and manually unassigns it.


===============================
III. INSTALLATION INSTRUCTIONS
===============================
NOTE: For Maintenance Pack installation on Microsoft Cluster Environment:

1) Install this Maintenance Pack on the inactive node(s) of the cluster
(follow steps 1-5 below)

2) Use the MSCS move group command to 'failover' the server to another node.
This should be done when the NetBackup system is quiet, i.e. no backups
or restores running.

3) Install this Maintenance Pack on the newly inactive node of the cluster

4) (Optional) Use the MSCS move group command to 'failover'
the server back to the original node.

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

Installation steps:

NOTE: If upgrading a NetBackup Windows 4.5 MP8 client to server or
Administration Console, the 4.5 Maintenance Pack must be uninstalled
prior to upgrading to 4.5 server or Administration Console.

1) Close all NetBackup Windows.
Make sure the NetBackup server has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Maintenance Pack will not install if the file to update is busy.

If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped via the
ControlPanel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
installed.

2) Run Setup.exe (Double-click on the icon from File Manager or Explorer or run
it from the command prompt)

Setup.exe begins by stopping the appropriate NetBackup Services required for
the Maintenance Pack installation. Next, it will install the necessary files
into their correct locations. Lastly, Setup.exe will restart the appropriate
NetBackup services.

3) Examine the <install_path>\patch\History.Log file to ensure that no
errors took place during the installation. For example, an error during
Maintenance Pack installation because of a busy file.

4) Remove the temporary directory created in the download instructions.


===========================
IV. UNINSTALL INSTRUCTIONS
===========================
**Important notice regarding un-installs on Windows**
Only the last Maintenance Pack installed on a Windows system
can be un-installed.

1) Close all NetBackup Windows.
Make sure the NetBackup server has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Maintenance Pack will not install if the file to update is busy.

If a database client is being used, such as Oracle, ensure that the
database services are stopped. Database services can be stopped via the
ControlPanel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
installed.

2) Go to <install dir of NetBackup>\Patch\Pack_Uninstaller.exe and double-click
on the executable.
(i.e. C:\Program Files\VERITAS\Patch\Pack_Uninstaller.exe)

3) Select correct Pack to be uninstalled.

4) Click on Uninstall.

5) You may review the trace file
(<install dir of NetBackup>\Patch\Pack_Uninstall.log)
to see what files were replaced.


=================================
V. 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 Maintenance
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, Symantec 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 the LTIerrno.h file were not found by the search program
if the message lines began with spaces instead of a tab.

Additional Notes:
The list of messages for Media Manager errors has changed. This only
effects localized sites.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault jobs failed with an error 227 if no images were selected in a
specified time frame.

Workaround:
To avoid this issue, make sure at least one image is selected in the
specified time frame.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The scheduler was 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 error is sent back to the
multiplex child, bpsched, but the child sched is already adding another
backup to the multiplex group.

The child sched attempts to send the new jobs information to bpbrm, but
bpbrm has exited and the connection is defunct. The scheduler was
incorrectly logging the defunct connection in the job progress log. With
this change scheduler no longer logs the broken socket, and correctly reads
and processes the status 134 error from the inbound connection.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpretlevel loops echoing the word, "What?" when changing retention levels.
Entering a ctrl-C command is the only way to exit this loop.

An earlier code change had changed all occurrences of gets() to fgets().
However, this change failed to recognize that fgets() return the "\n",
where the previous code, using "gets()" did not. The subsequent strcmp
was not expecting the "\n", and caused the failure. To resolve this issue,
the instances of the [new] trailing "\n" were stripped to emulate the
"gets()" behavior.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This problem only occurs with Oracle 10g. The database is up and running.
Using either the Oracle backup wizard or the Oracle restore wizard, choose
to shutdown the database before the backup/restore and restart the database
after the backup/restore. Running the template produces the following
errors:
ORA-00445: background process "PMON" did not start after 0 seconds
ORA-27300: OS system dependent operation:waitpid failed with status: 10
ORA-27301: OS failure message: No child processes
ORA-27302: failure occurred at: skgpdparent1

Workaround: generate a script from the template and run the script.

Workaround:
Generate a script from the template and run the script.

(NetBackup Clients: Alpha Dgux HP Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
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 might also happen because of a
timing problem in bpbrm when new jobs were started.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected an issue that caused the scheduler to lose a backup in the
middle of a catalog backup.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Using the Red Hat 3.0 ES, when an Oracle template is created via the client
GUI, the following warning 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:
When backing up Lotus Notes databases, some databases were skipped. These
skipped databases were not reported as an error; the backup exited with a
status 0 instead of a status 1.

(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
After running FlashBackup backups that were aborted, a snapcachelist
command showed the snapshot cache device still in use even though the
snaplist command did not return any snapshots. Eventually, the snapshots
would fail because of the 32 snapshots per cache device limit. A reboot is
required to recover the use of the cache device.

Additional Notes:
The snap driver has been modified to use a different flag bit to denote a
snapshot in creation versus a snapshot that is being deleted. A snapshot in
creation is allowed to be listed by snaplist, and can be deleted.
FlashBackup has been changed to remember the snapshot ID between the time
that the snapshot is initially created to the time that the snapshot device
is opened so that it can be deleted.

(NetBackup Clients: SOLARIS )
--------------------------------------------------------------------------------
Description:
Vault ejects would intermittently failed with a status code 44 when using
an IBM ATL tape library, and when ejecting more tapes than CAP would hold.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Whenever the vmd or any of its children terminated, it would log the
error code, "terminating - <error_string> (< error_code> )" to the syslog.

Many times, the error code that was logged was, "terminating - successful
(0)", which is a normal exit status. This change eliminates logging a
normal exit status such as this to the syslog.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault physically ejected tapes but did not remove them from media manager.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent failed when an attempt was made to back up more
than 255 databases using one batch file. This occurred if the backups were
individually specified in the database or if $ALL was used and there were
more than 255 databases on the SQL Server host.

When this occurred, the Automatic backup job failed to terminate.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
During a NetBackup MSSQL scheduled backup, the bpbdb.log showed a log
entry with a severity <16>, and yet the backup still succeeded.

This occurred because the severity was set incorrectly for an
informational message.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpdbm would crash if it was unable to determine the host name of caller.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a Flashbackup job was cancelled from the GUI, the snapshot was not
deleted.

Workaround:
To avoid the issue, manually kill the backup by issuing the following
command:

kill -TERM to bpbkar.

(NetBackup Clients: HP SOLARIS )
--------------------------------------------------------------------------------
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:
Oracle Proxy BLI did not work with VxFS 4.0.

(NetBackup Clients: HP RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
Oracle production database would be corrupt after a backup.

(NetBackup Clients: Dgux HP Linux2.2 Linux2.4 RS6000_433
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
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 catalog cleanup process would leave ASCII .f files for Flashbackup
images open. This led to the failure, "too many open files".

Workaround:
Manually running clean-up one client at a time can help resolve this
problem. This will also split file lists into multiple policies.

(All NetBackup Servers)
--------------------------------------------------------------------------------
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:
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:
Added a new ID for two duplicated messages.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Memory corruption occurred within the Lotus Notes Agent for Linux when
passing handles because of a mismatch of the handle size.

(NetBackup Clients: Linux2.4 )
--------------------------------------------------------------------------------
Description:
When performing backups, bpbkar32.exe may generate an application fault.
If a DrWatson log is available, the following will appear in the log:

ACCESS_VIOLATION_bpbkar32!dos_backup::V_OTM_DisallowUsage+13.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
NetBackup for Lotus Notes failed with a Status 227 using alternate client
recovery.

(All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 SOLARIS)
================================================================================

=========
NB_45_8_M
=========
Description:
The scheduler's multiples group list on Windows 2000 platforms was being
truncated.

(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:
The Windows client GUI no longer displays duplicate tree nodes in a restore
window.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When scheduler verbose was set greater than zero, Jobs could exit with a
status 50. This problem was more likely to occur on systems experiencing
connection issues. The problem occurred when the scheduler printed a
message and lost the errno value. Armed with the incorrect errno value,
the scheduler would exit (status 50) the current running job(s).

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows client GUI, the "Temporary location for log and patch
files" for Exchange 2000 restores may now contain space characters.

Workaround:
Do not use space characters in the "Temporary location for log and patch
files" path for Exchange 2000 restores.

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A backup is established with:
- multiplexing enabled
- multi-copy enabled
- continue backup on copy failure

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SAP Alternate Client restores may fail. The SAP Agent was unable to read
the output file of the restore_filter script. This failure produced a log
similar to the following:

"14:30:00.381 [7082] <16> backint_restore_filter: cannot open restore
working file:
/oracle/BD1/sapbackup/backint_dir/.backint.filter.1085772595.7082
14:30:00.381 [7082] <16> backint_do_restore: ERROR: running restore filter"

In addition, the restore_filter script was unable to handle a use case
where source client (a backed-up client) did not have soft links to the
actual file paths of the SAP data files. During a restore on the target
client (a new destination client), the agent would not adjust file paths to
match the originally backed-up paths. This issue would produce a log file
similar to the following:

"*************************************************************************
Program: ./backint 5.0GA
Input File: ./in_re
Profile: ./initSAP.utl
Function: RESTORE
**************************************************************************

#NOTFOUND <input file name>
***************************************************************************"

or in the backint log:

"10:56:07.093 [2838] <2> backint_find_master_time: exit status = 2
10:56:07.094 [2838] <4> backint_do_restore: #NOTFOUND /tmp/bd1/file1"

(NetBackup Clients: Alpha HP Intel-NT RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
**Description:
After a failure had occurred, the SAP DB Environment Agent would report a
Success despite the actual failure. This problem only occurred when an
agent is called into the SAP DB environment with the adapter program and
there were previously successful backups and current backup failures. A
problem similar to this would produce a log file similar to the following
example:

"
...
08:16:49.143 [1433628] <16> backint_system: ERROR: executing
command /usr/openv/netbackup/bin/bpbackup -w -t 17 -h pollux_bk -S
frsux071 -c ASV_SAP_A30_online -s Default-Policy -
L /usr/openv/netbackup/logs/user_ops/sap/.backint.log.0.1083392186.1282186 -
08:16:51.208 [1282186] <16> dbc_Wait: ERR - job (1433628) failed status (71)
...
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083106428 /home/adasav/A10/NB_puffer1/STAGE3.0
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083364604 /home/adasav/A10/NB_puffer1/STAGE1.0"

Note: The example above shows a backup command failed, but the agent
reported that the input files were saved. This happened because agent
saved these files in a previous backup. This might mislead the user into
thinking the backup of SAP on the SAP DB was successful when it actually
failed.

(NetBackup Clients: Alpha HP Intel-NT RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
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:
Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce
unnecessary unmounts/re-mounts during Vault sessions.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
During an Exchange Mailbox backup, duplicate folders within the mailbox
caused NetBackup to fail. The initial folders would be backed up
properly, however bpbkar would exit abruptly after finding the second
instance of the folder. An exception occurs in LPValFindProp().

Workaround:
To avoid this situation, delete the duplicate folders in the mailbox. This
enables the Mailbox backup to finish successfully.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
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 was one number lower than a multi-copy backup.

For 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:
A part of a message that occasionally appears in the detailed log file has
been removed. The message would indicate how long it has been since
activity has taken place.

For example:
runDups(): duplicate.log.5_en: No activity in 17768237 minutes

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Running a vault job from either a vltrun command or by right clicking on
the profile runs successfully. However, a "status 23" error would occur
when running the job from the vault policy either manually or through
bpsched.

Workaround:
To avoid this issue, determine if there is a directory or file, named
"program", on the drive on which NetBackup is installed (for example,
Z:\Program.exe), then rename it to something else.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When trying to perform a Lotus PIT restore (using PIT) when a secondary
restore is required to restore requested Lotus transaction log extents, the
following error is encountered:
"Invalid start date: 11/15/99" syntax error in bprestore. Only applies to
restoring Transaction Logs function - standard nsf files are ok.

tar debug log shows:
16:32:19 (101307.001) INF - Begin Lotus point in time database recovery to:
06/05/2004 16.29.22 CEDT
16:32:19 (101307.001) INF - Transaction Log:/A1VG3DATA/S0000160.TXN Required
for Recovery
16:32:19 (101307.001) INF - Requesting Restore of
Log:/A1VG3DATA/S0000160.TXN
Id:001c6243c1256e7d-f762d76fa9030000
LogNo:160
16:32:19 (101307.001) Invalid start date: 11/15/99
16:32:19 (101307.001) EXIT STATUS 144: invalid command usage
16:32:19 (101307.001) INF - NBLN_RecoverDb() RecoverErrorCode:0x13E3
DbIndex:0
16:32:19 (101307.001) ERR - /A1VG1DATA/c59admin_domino/testtl.nsf Recovery
Failed!
(0x13E3:Recovery Manager: Error from Logging Subsystem.)

Bprestore demonstrates incorrect syntax:
16:32:19.346 [83270] <2> logparams: -B -w -t 25 -s 11/15/99 -R
/usr/openv/netbackup/logs/user_ops/LN_Restore_Rename_File_87834.chg
/Transaction Logs/S0000160.TXN~001c6243c1256e7d-f762d76fa9030000
16:32:19.361 [83270] <16> process_args: Invalid start date: 11/15/99
16:32:19.361 [83270] <2> bprestore: exit with status = 144

Bplist can also recreate the error with the following options;
# bplist -t 25 -l -R -s 11/15/1999
Invalid start date: 11/15/1999
EXIT STATUS 144: invalid command usage

(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
Description:
Vault, when deciding if an image had already been duplicated, looked for
any image fragments that were already present in the destination volume
pool. Vault would not check if the fragment was of a valid copy.

Workaround:
To avoid this issue, run an Image DB cleanup session to ensure that invalid
image copies are deleted from the Image DB.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Vault did not give the user the ability to specify which host was selected
for use as the "robotic control host" for an API robot.

Workaround:
To avoid the issue, manually edit the Vault Configuration file.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
If a policy is included in the Backup Policies list of a Vault profile
(Profile dialog > Choose Backups tab) and that policy is deleted from
NetBackup using the NetBackup Management > Policies utility, it is also
deleted from the Backup Policies list. With this fix, deleted policies are
not removed from the Backup Policies list.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Oracle recovery templates caused a core-dump if it was used/managed under
Template Administration window.

In addition, the Oracle Backup wizard enabled a recovery template to be
selected when choosing the option of "Retrieve configuration of an existing
template".

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault would not give the user the ability to specify which host was selected
for use as the "robotic control host" for an API robot. Vault dynamically
updated this value using an erroneous algorithm, making it difficult for a
user to deduce which host that Vault might pick.

This behavior is typically just an annoyance for customers who want to
isolate their robotic traffic to particular hosts (or more typically to
avoid sending robotic activity to certain media servers), but
occasionally it becomes a major issue in large environments.

Workaround:
None

Additional Notes:
In the current patch solution, 'Robot control host' name is made editable.
It is recommended that you change this host name only in case of API robots
that have different Robot Control hosts. In all other cases, this field
shows the correct Robot control host name.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
A dual stream backup starts only one backup for each Redo Log Group after
the first Redo Log Group is backed up correctly (two backups).

This problem occurs in following configuration:
1. BRARCHIVE is called with -f option
2. SAP Agent configuration file (init<SID>.utl) contains sched_log
parameter.

The sched_log parameter is the value of the second schedule that the
SAP Agent can use to backup archive logs. When this parameter is enabled,
two backups of archive logs will be performed. This enables backing up the
same archive logs to different media. This parameter is processed correctly
by the SAP Agent when BRARCHIVE is called without -f option.

However, when BRARCHIVE was called with the -f option, only the first group
of archive logs were backed up to both schedules. Any subsequent group of
archive logs would be backed up to only one (original) schedule.

(NetBackup Clients: Alpha HP Intel-NT RS6000_433 RS6000_51 SOLARIS )
--------------------------------------------------------------------------------
Description:
Refreshing the NetBackup History window in the NetBackup Windows client
GUI will not display any images when the selected policy type is Oracle.
This functionality is working as it was designed.

Workaround:
Do not use the "Refresh" toolbar button, the "View->Refresh NetBackup
History" menu item, or the F5 shortcut key when the selected policy type is
Oracle.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
An NDMP backup in the ASCII catalog format would fail and produce the
following error in the bptm log.

08:42:17.202 [5704.5624] <2> write_data_ndmp: calling
ndmp_bpfsmap_create
08:42:18.304 [5704.5624] <2> write_data_ndmp: bpfsmap longjmp: setjmp
returned 6; aborting backup
...
08:42:18.764 [5704.5624] <2> write_data: write_data_ndmp() returned -8,
EXIT_Status 6, Kbytes = 1359099
08:42:18.774 [5704.5624] <2> write_backup: write_data() returned,
exit_status = 6, CINDEX = 0, TWIN_INDEX = 0, backup_status = -8

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Attempting to restore from an image that was backed up with the following
setting would result in a failed status 5.

"SET FILES = ( Multiple Files ) "

(All NetBackup Servers: HP Intel-NT RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Vault would not allow a user to specify the robotic control host.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The scheduler does not automatically start "bpexpdate -deassignempty" to
deassign media that do not have associated images after "bprecover -l" has
been run.

Workaround:
If a bprecover -l has been executed, remove the following file:

UNIX:
/usr/openv/netbackup/bin/deassign_lock

Windows:
VERITAS\NetBackup\Bin\deassign_lock

Do not remove this file if a catalog recover (bprecover -r) has been done.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing an Intelligent Disaster Recovery and the communications
between the client and server are configured to use vnetd, the submission
of the restore request from the recovery wizard will fail.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When performing full backups of using the UNC naming convention, the
archive bits on some files are not getting cleared.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When performing an IDR restore with a bootable CD created from a Japanese
Windows 2000 SP3 integrated CD, the setup fails with the following error:

"The following value in the .SIF file used by Setup is corrupted or
missing: Value 0 on the line in section [SourceDisksFiles]. With
key 'sp3.cab' error is received"

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
In certain cases, a backup job may receive an error, but the job remains
active and must be manually cancelled.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
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:
Vault report emails would be corrupted if two Vault jobs finish at the same
time.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The SQL server would sometimes fail to create an VDI object within
30 seconds during scheduled backups. When this occurs, messages similar to
the following may appear in the dbbackup log.

02:14:41 [5000,3212] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <37000>, Message Text <
[Microsoft][ODBC SQL Server Driver][SQL Server]Write on 'VNBU0-5000-
3212' failed, status = 995. See the SQL Server error log for more
details.>
02:14:41 [5000,3212] <16> CODBCaccess::LogODBCerr: DBMS MSG - <
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.>
02:14:41 [5104,5304] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <37000>, Message Text <
[Microsoft][ODBC SQL Server Driver][SQL Server]Write on 'VNBU0-5104-
5304' failed, status = 995. See the SQL Server error log for more
details.>
02:14:41 [5104,5304] <16> CODBCaccess::LogODBCerr: DBMS MSG - <
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.>
02:14:41 [5104,5304] <32> Dbbackrec::PerformNBOperation: ERR - Error
found executing <backup database "trad" to VIRTUAL_DEVICE='VNBU0-5104-
5304' with blocksize = 512, maxtransfersize = 65536, buffercount = 1>
02:14:41 [5000,3212] <32> CDBbackrec::FreeDeviceSet(): ERR - Error in
VDS->Close: 0x80770004. The text follows:
02:14:41 [5000,3212] CONTINUATION: - An abort request is preventing
anything except termination actions.

To resolve this issue the VDI timeout is increased from 30 seconds to 5
minutes.

Note: In the NetBackup 5.0 version, you can set the VDI timeout in the
batch file for added flexibility.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
In some instances for multi-striped backups, the NetBackup-for-SQL-restore
move script is built without the log (.ldf) section.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
The Teradata backup history window took 20 minutes to display 90,000
objects. This was a substantial performance regression.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
The Vault Summary and Detailed Distribution reports were consuming too much
memory.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
NetBackup for Lotus Notes will successfully backup Domino transaction log
extents, but will not recycle them.

Workaround:
To avoid this issue, do not specify the TRANSLOG_Path for the Lotus
transaction log directory in the notes.ini as a symbolic link. Make sure
the Lotus transaction log directory is always the actual physical path.

(NetBackup Clients: Intel-NT Linux2.4 RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
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:
Some TL8 robots that would eject more than a MAP-full (media access port)
of media would abort after the first MAP-full.

Workaround:
To avoid this issue, re-issue the eject operation with the remaining media
to be removed from the robot.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
To assist image database cleanup in 24x7 environments, image database
cleanup will always run in background. For example, 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 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:
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:
The predict algorithm was not sorting correctly. It failed to position
cumulative incremental backups before the differential incremental backups.

(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:
The bpsched log would fill with the following message:

"storage unit was not assigned for clientjob ..."

This was caused by an erroneous invocation of the add to multiplexed group.
The add to multiplexed group function would performed a parameter
validation, print the message, and return.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When a database agent gets requeued multiple times in a very short period
of time, there were cases where the server would time out waiting for the
client to connect. This fix prevents the client from getting behind the
server in these instances.

(NetBackup Clients: HP Intel-NT Linux2.4 RS6000_433 RS6000_51
SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
The device configuration user interface can encounter a long delay when
selecting a robot. The time required to filter the lists in one case was
reported to be approximately 20 minutes.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Very large Teradata backups had an error where an overflow of an integer
byte count of fractional blocks caused the wrong size to be sent to bptm.
This size value did not match what bptm counted and resulted in the backup
aborting.

Workaround:
To avoid this issue, you can back up the large database using multiple
streams.

(NetBackup Clients: Intel-NT NCR )
--------------------------------------------------------------------------------
Description:
An Oracle autobackup of the control file is very slow because of the format
of the piece name.

(NetBackup Clients: Dgux HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
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 patch installation is now able to handle alphanumeric revision levels.

(All NetBackup Servers)
--------------------------------------------------------------------------------
**Description:
When backing up files using VSP to back up open/active files on Windows
clients, files deleted while the backup was running would not be backed up
and could not be restored. This was not the expected behavior because all
files that existed during the time the VSP snapshot creation occurred (at
the beginning of the backup) should have existed when the backup was run
and any file deletions during the course of the backup should have affected
the backup job, because backups using VSP used the VSP snapshots to
enumerate files to be backed up.

Workaround:
To avoid this issue, do not delete files while the backup job is running

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
Bpbkar32.exe may crash when backing up FAT32 volumes with VSP enabled to
back up open/active files.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When changing the VSP Cache Volume List or the VSP Volume Exclude list in
the VSP Configuration tab using the NetBackup 5.0 Administration Console,
and adding more than one volume name in these lists, only the first volume
will take effect for both lists when backups are run and VSP is enabled.
This only occurs when using a post 5.0 NetBackup Administration Console to
configure a pre-NetBackup 5.0 client.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When running VSP-enabled backups of the Veritas NetBackup install drive
(typically C:\) on the master server, VSP snapshot creation consistently
fails for all backups that are run on the VERITAS NetBackup installation
drive. Backups like this would end with status 1 because the VSP snapshots
could not be enabled to allow the backup to back up open/active files.
This means the open/active files were inaccessible to the backup. This
issue only affects the VSP snapshot creation of the NetBackup install
directory and not any other drive on the master server host.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Bpbrm received a SIGSEGV and core dumped in the malloc system call. This
issue has been resolved.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing an alternate client restore of RAW devices with the SAP
Agent, the restore would fail. The following errors were reported in
brrestore:

BR386E File /dev/vgsapiBWP/rBWPclui_1 reported as not found by backup
utility

The following information was reported in the backint logs if logging
is ON and VERBOSE=5:

11:13:28.129 [20169] <4> backint_find_master_time: WARNING: not found in
bplist list: /dev/rdsk/c1t4d0s1
11:13:28.129 [20169] <2> backint_find_master_time: Display inquire_info
structure
11:13:28.129 [20169] <2> backint_find_master_time: file_path_name =
>/dev/vgsapiBWP/rBWPclui_1<
11:13:28.129 [20169] <2> backint_find_master_time: actual_file_path =
>/dev/vgsapiBWP/rBWPclui_1<
11:13:28.130 [20169] <2> backint_find_master_time: bid =
>NS1096040689< dest_dir = >/dev/vgsapiBWC/rBWCclui_1<
11:13:28.130 [20169] <2> backint_find_master_time: start_unix_time =
1096040689 ; end_unix_time = 1096040689 ; image_time = 0
11:13:28.130 [20169] <2> backint_find_master_time: found = 0 ; raw_par
= 0 ; time_pos = 0 file_size = 0
11:13:28.130 [20169] <2> backint_find_master_time: exit status = 2
11:13:28.131 [20169] <4> backint_do_restore:
#NOTFOUND /dev/vgsapiBWP/rBWPclui_1

(NetBackup Clients: Alpha HP Intel-NT RS6000_433 SOLARIS )
--------------------------------------------------------------------------------
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:
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)
--------------------------------------------------------------------------------
Description:
The current NetBackup 4.5 MP patch release installs an outdated VSP driver
(v1.03). What should be installed is the 1.05 version that resolves
several issues related to VSP snapshot creation on 64-bit volumes and
interaction with third party VSS snapshot providers.

(All NetBackup Windows Clients)




=========
NB_45_7_M
=========
Description:
When a Vault session ejects media to a SCSI robot, the session may fail
with an error code 293 due to the robot being busy. Vault now
retries the eject operations when the robot is busy.

Additional Notes:
This problem can occur when tape mounts or GUI robotic operations are
performed during a Vault session.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When different vault sessions are run concurrently, the vlteject.mstr file
may become corrupted because of timing issues with processes trying to
read/write to this file at the same time.

This fix reduces the chances of this file getting corrupted.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When starting several mounts simultaneously, the user may see "unable to
read ack" messages in the syslog from the robot daemon as it tries to
communicate to the robot control daemon. This is more likely to occur with
TL8 libraries, and can occur with either. This may also lead to a hung
parent daemon that reports a syslog error of being out of file handles.
(errno = 24, EMFILE)

TLD only: NetBackup re-initializes the ADIC Scalar 10K library before
downing the drive in the event of a hardware error on the drive. NetBackup
will no longer reinitialize this library.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The number of parallel streams specified in an Oracle RMAN template that is
built using the Oracle RMAN Backup Wizard will be used for Archived Redo
Log backups in addition to Tablespace and Datafile backups. Previously,
only one stream was used for Archived Redo Log backups even if a greater
number of streams was specified in the template.

(All NetBackup Windows Clients Alpha Dgux HP Linux2.4 RS6000_433 SGI SOLARIS)
--------------------------------------------------------------------------------
Description:
When doing a detailed import or verify, when there are lots of small
files, the logging takes longer than it should.

(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:
When restoring large numbers of small files with a detailed progress log
on a media or master server, the O_SYNC flag on the open of the progress
log can cause the restore to take much longer than it should.

Workaround:
Do the restore from the client or don't get a detailed progress log.

(All NetBackup Servers)
--------------------------------------------------------------------------------
**Description:
A backup of Lotus R6.0.3 or Lotus R6.5 will not back up subdirectories.

Additional Notes:
Support of Lotus R6.0.3 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.

Support of Lotus R6.5 on Windows requires a Lotus patch (provided
as a hotfix) for SPR# THUR5LPPW9 to resolve an enumeration problem
encountered in the Lotus API function NSFSearch(). Customers should
contact Lotus Support and provide the SPR# to obtain the Lotus hotfix.

Without the appropriate hotfix, backups of Lotus Notes will fail and bpbkar
will log debug messages similar to this:

1:38:22.392 PM: [3444.1200] <3444> nbex_DebugLog: ERR - NBLNtoFINDDATA()
NSFDbOpenExtended('D:\Lotus\Domino\Data\Partition1\domino\domino\cache')
Failed: 0x103:File does not exist.

If the hotfix has been installed for Lotus R6.0.3, the Lotus Server console
will display the following version information:

Lotus Domino (r) Server (603HF80 for Windows/32)

If the hotfix has been installed for Lotus R6.5, the Lotus Server console
will display the following version information:

Lotus Domino (r) Server (65HF116 for Windows/32)



(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The Troubleshooting wizard in the Windows NetBackup Administration Console
does not work on Windows XP and other newer Windows OSs.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console for Windows may crash on Multi-
Processor systems due to a threading issue with pending requests in the
Device Monitor.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
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's 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:
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:
Ejecting more than ~642 tapes results in the vlteject process failing.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
All Vault duplications were deemed successful (as stated in the duplicate
logs); however, the detail.log shows error 308 (no images successfully
duplicated). This issue happens even for the most simple of vault
duplication (for example, one image). The speed of the duplication was also
considered reasonably fast.

Additional Notes:
This is an issue specific to AIX 5.2, as the fundamental behavior of a
libc function ( fgets() ) has changed. Perhaps to be consistent with a
recent POSIX proposal.

The change to code alleviates the AIX problem, and is benign on other
platforms.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
For ACS robot types, if a tape that is to be ejected is mounted while an
eject of that tape is in progress, the eject job may never complete.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Certain robotic conditions could cause a Vault job to end prematurely.
Retry logic has been added around the robotic inventory vault process to
accommodate this problem.

(All NetBackup Vault 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:
Performing consolidated ejects and reports could result in the completion
status of the individual sessions not being updated correctly. Vault could
incorrectly update a session as complete when it is not. This results in
the operator being unable to complete the ejects or reports for the
sessions that were consolidated.

Workaround:
Do not perform consolidated ejects or reports.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Performing a consolidated eject could result in volumes being moved into
the wrong off-site volume group.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
If SQL Server 7.0 is installed as the default instance on a host and one or
more SQL Server 2000 instances exist, the SQL agent "DBMS log on options"
dialog may display the incorrect SQL version when one of the other SQL
instances is selected.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
If an error occurs that leaves the bpbkar process running on a client
during a Flashbackup, the scheduler will resubmit the backup. This results
in a error 20 because the cache file is still being used by the previous
backup process. A change has been implemented to let bpbrm terminate and
wait bpbkar to finish before reporting the error to bpsched.

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

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
If the user selects a differential database backup from the SQL Server
backup history dialog, the SQL agent should attempt to determine a full
recovery path. This functionality (removed in 4.5 MP1) is restored with
this patch.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
PROBLEM: The SQL restore dialog box doesn't scroll correctly.
SOLUTION: The scroll/resize logic has been altered to improve the scrolling
properties of the restore dialog.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When a system has more than 62 mounted volumes, backups may fail with
either a status 41 or a status 54. The exit status is due to the bpbkar32
application crashing.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When bperror was run it could not load the localized resource dll
(Japanese), it should have retried using English resource dll's but did
not.

admincmd\bperror Error: Can't find Troubleshooting Guide, or status code
not available.

The resource dll in place: NBWTroubEN.dll

Workaround:
Change the NetBackup Machine Default Locale from default to English.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Create SQL Server user_ops directories if they do not already exist. This
action prevents an SQL backup from failing if the user has deleted the
directories or if they were not created during the install.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
Alternate buffer method for backup should not be inhibited for SQL Server
7.0.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
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:
A buffer overrun may cause the volume manager daemon vmd to fail.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
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. Since 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:
If a restore fails because of a media mount timeout, bprd may core
dump when it finishes processing the restore.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If the Backup Selection List of an Oracle policy contains a mix of backup
templates and shell scripts, the shell scripts will not run if they follow
a template in the list.

(All NetBackup Windows Clients Alpha Dgux HP Linux2.2 NCR RS6000_433
Sequent4.2 SGI SOLARIS Solaris_x86_2.6 )
--------------------------------------------------------------------------------
Description:
When backing up long file names (greater than 256 characters), the
bpbkar32 process may crash.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
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:
Calendar scheduled jobs may not run when administered from a different
time zone.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup resource DLL's are not being explicitly unloaded. This can cause
unneeded reboots during an upgrade install.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The "Use Barcode Rules" check box is not checked by default. The default
is checked as long as the options dialog is not opened. Once you open the
options dialog, the default changes to unchecked. When you do an
inventory, the default should always be to use barcode rules.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Restore paths were 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:
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:
The problem fixed in this patch is related to the Media Going Off-site
reports for Vault. In particular, the Picking List for Robot and the
Distribution List for Vault were reporting an "image count" of 0 even when
there were tapes being ejected with plenty of images on them.
This issue is now resolved.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
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:
Down the NDMP drives that are not working.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Vault run completes, but segment violation occurs at the end of the vault
run when logs are being closed. This problem only appears to occur on a
Linux server at kernel level 2.4.9-e.27

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Resolves a potential Dr. Watson on Windows NT if an NDMP drive path name is
too long (exceeds the stack).

With this patch, the new maximum length for drive path name is 128
characters.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SAP's backint fails with status 25 when the server value is not set in
the .utl file and the SAP_SERVER environment variable is not set. The
server entry is not being picked up from bp.conf and passed to bplist.

Workaround:
Set server value in SAP init< SID> .utl file or set SAP_SERVER environment
variable

(NetBackup Clients: Alpha HP Intel-NT RS6000_433 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:
NDMP backup restore can fail because some NDMP venders do not use "2" as the
mount point inode number.

(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:
Restores or backups may erroneously fail with a 52 status (timed out
waiting for media manager to mount volume).

Workaround:
To avoid this issue, set the media mount timeout to zero.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When ejecting media to an ACS robot, the eject process could hang because
of an unhandled volume status, STATUS_ROBOT_BUSY. This status is now
handled appropriately as an error condition.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When vault sessions are run on a Linux master, the contents of
vlteject.mstr are deleted during the eject phase. Thus the reports for the
session and any other pending ejects/reports fail with NetBackup status 296
(process called but nothing to do). This problem has been resolved.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
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 restoring NAS data from an NDMP-attached tape drive, the bprecover
command fails with an EOM (end of media) error.

Workaround:
Workarounds for this problem:
- Use a non-NDMP drive.

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
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:
During the suspend step of a vault session, a core dump may occur (in
particular on HP-UX systems).

Workaround:
The workaround for this issue would be to manually suspend tapes being
ejected using "bpmedia -suspend -m <media_id>".

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup Administration Console and bpps command lines could crash on
certain systems while attempting to gather process information via
Microsoft's Performance Counter APIs if the counter values are not the
defaults set by Microsoft.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Remote NDMP ndmpmoverlistener.exe process shows growing handle count
and page faults, which eventually brings down NDMP drives.

Workaround:
Stop and then restart the "NDMP Mover Agent" from services.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When NAS vendors don't send a notify data_halted message after sending a
last file history, remote NDMP waits and eventually fails with a timeout
error (error 99)

(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Add support for Oracle 10g.

(All NetBackup Windows Clients Alpha Dgux HP Linux2.2 RS6000_433 SGI SOLARIS)
--------------------------------------------------------------------------------
Description:
In some limited circumstances a change server command will result in the
console crashing. This corrects this problem.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
A core dump can occur if you run the following command:
bppllist -allpolicies or <policy> -U

Workaround:
To avoid this issue, do the following:
1) Look for a policy that has an unusually long value for one of its
attributes, such as the keyword, or 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�s 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 inablity to browse for restores under
certain file selection lists. This issue has been resolved.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The issue fixed by this patch has to do with changing the expiration date
of disk images from vault after they have been successfully duplicated. If
bpduplicate is passed a long list of image IDs and never gets a
chance to return to Vault, then Vault does not have a chance to change the
expiration date of the image.


(All NetBackup Vault 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"
signifiies 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:
Correct an end-case problem in MPX read processing (for
restores and 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:
If an error is encountered while attempting to open Lotus change
information during a Lotus backup, the backup will crash if the debug
logging level is increased. This problem has been resolved.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange backups do not support bandwidth limitation throttling.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Exception error occurs in tar32 when trying to restore an Exchange
Information Store when the Information Store service has been stopped.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
If an invalid alternate path is specified when performing a mailbox
restore, the restore fails with a status 5 and a Dr. Watson is generated
for the tar32.exe process.

This error can occur when selecting the entire Inbox or just a single
message from one mailbox backup image.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
If SQL Server is configured under binary collation, some images may not be
displayed in the NetBackup SQL agent's backup history window.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When BATCHSIZE is set in the SQL agent batch file, some of the backups
fail with errors such as the following:

12:53:45 [2276,2476] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message. ODBC return code <-1>, SQL State <IM002>, Message Text <
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified>
12:53:45 [2276,2476] <16> Dbbackrec::PerformNBOperation: USER - Unable
to login into ODBC DSN <NBMSSQL_2276_2100> as user <sa>

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
When creating VSP snapshots for backups, the snapshot creation can
disregard volumes in the VSP "Cache File Volume List" when they could have
been used as cache file locations.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When auto-sizing a VSP cache file when it is placed in a volume
other than the volume being snapshot, NetBackup may calculate its maximum
size to a value smaller than the correct value. This can cause VSP snapshot
errors to occur and the backup could end with status 155: disk is full.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
NetBackup SQL Server agent connects to SQL Server 6.5 hosts with integrated
security.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
After upgrading to NetBackup 3.4_2, the combined job status entry is not
always written to the progress report log files in the
install_path\NetBackup\logs\user_ops\teradata\logs directory.
The following is an example of a combined job status entry:

07:44:23 <4> [0,candy] Combined job status: Succeeded 2, Failed 0,
Unknown 0.

The contents of the log files are documented in the "Progress Reports
Created for NetBackup for Teradata" section of the NetBackup 3.4 for
Teradata System Administrator's Guide.

(All NetBackup Windows Clients NCR)
--------------------------------------------------------------------------------
Description:
Oracle version 8.1 with Oracle Failsafe in Microsoft Cluster Server (MSCS).

When an Oracle instance in the Backup, Archive, and Restore interface is
selected, an authentication box is display. The user has to enter a valid
username/password with DBA priviliges to continue. After this information
is entered, the following error is displayed:

Unable to connect to <Instance Name here>. Error Code = 12154

Consequently, the user is unable to continue to create or locally
administer templates.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
bpdbm's host list is not consistent with that of bprd. The current
impact of this issue reported by customer
is "FORCE_RESTORE_MEDIA_SERVER doesn't work for TIR restores."

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the NetBackup Oracle agent Backup Wizard is used to create a COLD
backup script, the backup fails with a status 29 because the script is
calling the "init<SIDname>.ora" file. In Oracle 9.2, there is no such
file.

(NetBackup Clients: Alpha HP Intel-NT Linux2.2 RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
Exchange Server shutdowns due to lack of space on the transaction log file
device.

The transaction logs were probably not truncated because the Exchange
backup failed. The original backup may have failed due to networking or
media failures and retry attempts may fail with a status 1.

Investigation of the Error logs would reveal the following error,
"INF - HrESEBackupSetup: Microsoft Information Store = 0xc80001f9"
"ERR - XCHG_BackupRead() FS_ReadObj() Failed! 0xFFFFFE30:FS_COMM_FAILURE".
These errors indicate that the Exchange StorageGroup is already in
backup mode. Close inspection may also reveal that the bpbkar32 from the
original backup attempt is still running

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When using the Windows PC Client interface, if the user does not have
permission to write or modify the folder that contains the NetBackup log
files, an attempted restore to an alternate path will correctly be
aborted.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
A user that uses Oracle "Template Administration" from the NetBackup
Windows PC Client interface to run or edit an existing Oracle template will
have his/her authentication and recovery selections correctly reflected in
the new template.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
Description:
When using the NetBackup PC Client Windows interface to do a Lotus Notes
user-directed backup, the NOTES.INI path field in the "Specify Backup
Options > Lotus Notes" page is now processed correctly.

(All NetBackup Windows Clients )
--------------------------------------------------------------------------------
Description:
Problems querying/updating the volume database during an eject could lead
to the eject job failing prematurely, leaving a session incomplete.

Also, consolidated eject/report jobs that were partially successful could
be erroneously marked as complete and volumes may have an incorrect off-
site volume group leading to report inconsistencies.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
If the REQUIRED_INTERFACE entry is present in the vm.conf file, problems
may occur with the vmquery or vmupdate commands.

Workaround:
Remove the REQUIRED_INTERFACE entry from the vm.conf file.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Performing consolidated ejects for all robots could malfunction if the
vault configuration contains multiple robots of the same robot type. This
problem could result in media being left in an incorrect off-site volume
group. Also, media ejected from some of the robots doesn't occur but
appears to have completed successfully.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Non-root users of vault are unable to eject media with vault. The
vlteject.mstr.lock file gets created with 600 permissions under UNIX.
This will prevent non root NBAC users from aquiring the lock, and ejects
will hang waiting for that lock file.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When a duplicate profile name existed in separate vaults, and selecting an
alternate session number, vltopmenu required that the triplet be fully
qualified, instead of first defaulting to the current vault.

Workaround:
To avoid this issue, you should not duplicate profile names.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When performing backups with TIR plus move detection, some backups may not
verify correctly due to files/folders having identical file numbers.

(All NetBackup Windows Clients)
--------------------------------------------------------------------------------
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:
vltrun is frequently failing with a status 282 and also dumping core.

Subordinate commands executed by bv_run_system() must not be allowed to
return an exit status of 0, when the child was killed by a signal. Insure
that children killed by a signal, and have a zero exit status, are actually
attributed a non-zero exit status (EC_process_killed).

Additional Notes:
If the image database is corrupt, as it was in the problematic case, the
problem is exposed. bpimagelist had returned a 'space' where vault had
demanded, and expected, a significant entry. The resultant failure exposed
a long sequence of erroneous vault behavior.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
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 Enterprise Technical 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:
If a schedule is changed from Frequency to Calendar scheduling and
"Last Day" is chosen from "Recurring Days of the Month," bpclsched will
crash. This occurs from both the command line and from the Java GUI.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Unable to restore NDMP NetWare data due to an invalid path shown in catalog.

If \\Server\Vol1\Dir1 is specified as a file selection that is backed
up, the Backup, Archive, and Restore screen shows the tree expanded as
Vol1\Dir1\Vol1\Dir1.

The restore fails with "Cannot restore from filepath \Vol1\Dir1,
NDMP_HALT_INTERNAL_ERROR occured" and a status (5). The data cannot be
restored to the original location or redirected using a valid path.


(All NetBackup Servers: HP Intel-NT Linux2.2 RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
VOPIE Enhanced Authentication may not work when host names are longer than
32 characters.
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:
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:
Ejects that are partially-successful are erroneously marked as completed.
As a result, the operator can't eject the remaining media or re-run reports.

(All NetBackup Vault 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 W2k platforms were losing MPX groups. The user could not cancel
orphaned jobs within the MPX group, and additional jobs could not be added
to the MPX group.

Windows-specific code was added to display questionable pointer values
prior to releasing the MPX group. Historically, this minor change caused
the problem to "go away." The thinking being that it's a W2k compiler
optimization issue. This fix will either mask the problem, or help isolate
it.

(All NetBackup Servers)

-=========================================

Attachments

NB_45_9_M_279103.winnt.intel.exe (18.6 MBytes)


Legacy ID



279103


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


Terms of use for this information are found in Legal Notices