Maintenance Pack NB_50_6_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.0 on NT/2000/2003/XP Professional server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Article:TECH45414  |  Created: 2005-01-06  |  Updated: 2006-01-17  |  Article URL http://www.symantec.com/docs/TECH45414
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_50_6_M.winnt.intel.exe provides fixes to the VERITAS NetBackup (tm) Enterprise Server / Server 5.0 on NT/2000/2003/XP Professional server and clients. It also contains fixes for NetBackup Add-on products and Database Agents.

Solution



NB 5.0GA Pack NB_50_6_M README November 29, 2005
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup (tm) NT server
and clients. It also contains fixes for NetBackup Add-on products, Database
Agents, and NetBackup Encryption.

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.



I. DOWNLOAD INSTRUCTIONS
II. KNOWN ISSUES
III. INSTALLATION INSTRUCTIONS
IV. UNINSTALL INSTRUCTIONS
V. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_50_5_M
NB_50_4_M
NB_50_3_M
NB_50_2_M
NB_50_1_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_50_6_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_50_6_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_50_6_M. Please note that
these known issues will NOT be resolved after installing this pack.

Description:
When pushing out the Maintenace Pack to remote windows machines an error can occur stating
"The system cannot find the file specified". The problem is due to the windows installer
failure to correctly copy the VERITAS Maintenance Pack.msi and Data1.cab files to the
%TEMP%\X86 directory.

Workaround:
1. Start the installer. Select Select from available computers on the network. Click Next.
2. Copy VERITAS Maintenance Pack.msi and Data1.cab to the %TEMP%\X86 directory of the server
from which the push install is being initiated. These files would be obtained from the
location from which the install was originally attempted whether it was from a local
directory or from a CD. (To determine the location of %TEMP%, open a CMD shell and run
echo %TEMP%. Usually it is something like
C:\Documents and Settings\<UserName>\Local Settings\Temp\X86.)
If the X86 directory does not exist, it can simply be created.
3. Proceed with the push install.

--------------------------------------------------------------------------------
Description:
For VSP users, a reboot will be required before the latest VSP fixes
will take effect.

--------------------------------------------------------------------------------
Description:
When uninstalling NetBackup, a few installation dlls will still exist
on the system and can be safely removed.

C:\Documents and Settings\<User>\Local Settings\Temp\
InstOps.dll
msvcr71.dll
nbi.dll
nbidlg.dll
resdll.dll

--------------------------------------------------------------------------------
Description:
Anytime a backup job fails before the checkpoint is created, the resumed
backup will ignore the first file list entry, but successfully backup any
others and end with status 0 (assuming no other errors). This can result
in a data loss situation because the first file list entry does not make
it to tape. This issue is only present with UNIX Clients, using the file
directive of ALL_LOCAL_DRIVES.

--------------------------------------------------------------------------------
Description:
A backup that stops and resumes can successfully complete, but there may be
multiple duplicate fragments. This type of problem causes the import to not
be able to determine which duplicate fragment is correct. This is
technically not a data-loss issue (since the data is on tape), however the
data will be difficult to recover if the import is needed.

--------------------------------------------------------------------------------
Description:
A problem can occur with misconfigured drives or when a rogue rewind is
detected after a checkpoint has been made. In situations such as these, the
data written before the checkpoint is bad and on rare occasions, could cause
a loss of data.

--------------------------------------------------------------------------------
Description:
SQL Server advanced client images created with 5.0_MP1 cannot be imported.



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

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

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

2) Move the group from the active node 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) Move the NetBackup group back to the original node.

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

Installation steps:

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

1) Close all NetBackup Windows.
Make sure the NetBackup system has no active backups, restores,
duplications, etc., running. If there are NetBackup activities in process,
the Maintenance Pack will require a reboot 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 <TEMP>.Log file to ensure that no errors took
place during the installation.

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

Note: If you are installing the Maintenance Pack using the silent install
script, please review the <TEMP>.Log after the installation is finished,
a reboot maybe required to complete the installation of the Maintenance
Pack. A search of the log for the key words "in use" will indicate which
files were busy during the installation.


===========================
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 Add/Remove programs dialog box and select correct Pack to be
uninstalled.



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

README Conventions:

Description
Describes a particular problem 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
=============

================================================================================
Etrack Incident = ET341251

Description:
If a machine has NetBackup and a Maintenance Pack (MP) installed, and an
uninstall is performed of the MP that requires a reboot, and NetBackup is
uninstalled before the reboot, the DLL named msvcp70.dll is removed. The
installer has been modified to ignore MFC DLL in the Windows system32
folder.

Workaround:
To avoid this issue, perform a reboot when you are requested after
you uninstall the MP and before you uninstall NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET352773

Description:
DSSU relocation would fail after upgrading to NetBackup 50_MP5 or 51_MP3.
--------------------------------------------------------------------------------
Etrack Incident = ET375868

Description:
A user currently cannot enter more than 99 dates into a calendar
schedule. To resolve this issue, increase the size of some of the arrays.
--------------------------------------------------------------------------------
Etrack Incident = ET346374 ET322960

Description:
The display of new ACS vendor media types T10000T1, T10000TS, and
T10000CT has been corrected. In addition, corrected the allowable types
of an ACS vendor media type LTO_400G.
--------------------------------------------------------------------------------
Etrack Incident = ET380236

Description:
If the NOexpire touch file was set, then the NetBackup database image
Cleanup was disabled. However, media would still expire. The media no
longer expires if the NOexpire touch file is set. Bpexpdate
-deassignempty, which deassigns media if there are no corresponding images
in the image database, is disabled.

The NOexpire touch file is set in the following locations:

For UNIX:
/usr/openv/netbackup/bin/NOexpire

For Windows:
VERITAS\NetBackup\Bin\NOexpire
--------------------------------------------------------------------------------
Etrack Incident = ET330684

Description:
Canceling a queued Vault job caused all backups to cancel.
--------------------------------------------------------------------------------
Etrack Incident = ET321735

Description:
The use of a closed socket error message was filling the scheduler log.
--------------------------------------------------------------------------------
Etrack Incident = ET367821

Description:
A user backup could not be cancelled using the activity monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET347553

Description:
On Windows platforms only: The scheduler would enter an infinite loop after
A read message queue failure occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET349782

Description:
The scheduler would enter an infinite loop if all of the following
occurred:
- The backup is checkpoint enabled.
- The backup is twinning.
- One of the twined copies failed.
- The non-failed copy exits with a failure status.
--------------------------------------------------------------------------------
Etrack Incident = ET363304

Description:
Adding a job to a multiplex group failed to check if a HOLD_134 exists on
the multiplex storage unit. This resulted in excessive 134 status backups.
--------------------------------------------------------------------------------
Etrack Incident = ET366177

Description:
Field 11, of the 'bpdbjobs -all' output, did not reflect the correct end
Time of the last try.
--------------------------------------------------------------------------------
Etrack Incident = ET316645

Description:
The scheduler performance suffered if the media server connection is
intermittent. The problem is aggravated when schedule continuously polls
the media server for NetBackup version information.
--------------------------------------------------------------------------------
Etrack Incident = ET314631

Description:
An issue with the scheduler dumping core has been resolved.
--------------------------------------------------------------------------------
Etrack Incident = ET325882

Description:
The Activity Monitor was continuously displaying the 'positioning' for
multi-fragment backups.
--------------------------------------------------------------------------------
Etrack Incident = ET300754

Description:
The interval-mode backup windows would open longer than six days
(144-hrs) and resulted in continuous backups on the seventh day, until the
window closes.
--------------------------------------------------------------------------------
Etrack Incident = ET301500

Description:
A Scheduler race condition was occurring: Child sched was sending a
�done� to the main sched while the main sched was sending a �term one� to
the child sched. The child sched erroneously treated the �term one� as the
response to the �done� and then exited prematurely.

The correct child response is to discard (ignore) the �term one�
request and wait for the main sched response to the 'done' command.

Also missing was code to discard (ignore) a �suspend� request after having
sent a 'done' to the main sched.
--------------------------------------------------------------------------------
Etrack Incident = ET320556

Description:
When a resume backup exits, it would attempt to send a request queue
message to the GUI. But the GUI does not read these messages, so the
message would stay queued until the main sched exited.
--------------------------------------------------------------------------------
Etrack Incident = ET323182

Description:
If the stream in control snap failed on a WOFB, then the other streams were
allowed to continue a non-snap backup. This was the correct operation. The
problem was that the non-control streams performed a backup of all files in
the file list, but they should have only backed up their specific files.
--------------------------------------------------------------------------------
Etrack Incident = ET316634

Description:
User backups failed to check if an exiting backup was the last backup job
from a specific SPID before removing all user backups from the work list.
This oversight caused the removal of active jobs from the work list, and
resulted in a sched core.
--------------------------------------------------------------------------------
Etrack Incident = ET365012

Description:
When a C_GET_HOSTINFO request is made from a pre-6.0 installation, the
[expected] request type and client name are appended to the MAGIC string.
For 6.0 and later these two fields are sent separately. Infer the level
of the requestor by counting the MAGIC string args, and retrieve the type
and client name accordingly. Once inferred, ensure that the 'acks' sent
to the requestor are in synch with the requestor's expectations.
--------------------------------------------------------------------------------
Etrack Incident = ET386568

Description:
Schedules that specify "instant recovery" should not have backups that
multi-stream. It is possible that a policy may try to multi-stream in
the following circumstances:
- Frozen image enabled.
- PFI enabled.
- Multi-streaming enabled.
- Policy contains schedules with instant recovery enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET340729

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.
--------------------------------------------------------------------------------
Etrack Incident = ET323265

Description:
bprd could not clean a vault session directory that contains files larger
than 2 Gigabytes.

Additional Notes:
To resolve this issue, use lstat64() for LARGEFILES platforms in the
recursive_dir_delete() function. Used primarily by bprd for periodic
deletion of log files (and vault session files)... and by bpdbm for
removing expired back-ups.
--------------------------------------------------------------------------------
Etrack Incident = ET363230

Description:
Oracle backups fail when a leading slash "/" is used in the format string.
--------------------------------------------------------------------------------
Etrack Incident = ET333277 ET333168

Description:
NetBackup for Oracle is not compatible with the RMAN "BACKUP BACKUPSET"
command. In addition, the Controlfile autobackup fails trying to verify
the image.
--------------------------------------------------------------------------------
Etrack Incident = ET387591

Description:
The NetBackup-SQL image browser should skip the images that it does not
recognize and display the ones that it does. This situation arises during
an alternate client browse by a NetBackup-MSSQL 5.0/5.1 client of images
for a NetBackup 6.0 client.

Currently, this case fails with a pop-up message, "Error encountered trying
to read database images." The dbclient log has an entry, "Bad metadata was
found for <%s>: <%s>. This image is being skipped."

With the fix, the unrecognized images will be skipped (for example, they
will not appear in the NetBackup 5.0/5.1 SQL image browser) and the others
will be displayed
--------------------------------------------------------------------------------
Etrack Incident = ET314638 ET292805

Description:
"bpdbm -consistency" failed to move out corrupted image files in
"catstore". It also failed to move out the zero byte image files
(which should have been handled by cleanup but it also failed).

Additional Notes:
On UNIX platforms, �bpdbm consistency� failed to move out the corrupted
image files if /usr/openv/netbackup/db and
/usr/openv/netbackup/db/images/<client> were not on the same volume. In
such case, the corrupted image files will be left to their original
locations.
--------------------------------------------------------------------------------
Etrack Incident = ET374767

Description:
Acsd timeouts were increased to accommodate overloaded ACSLS server.
--------------------------------------------------------------------------------
Etrack Incident = ET392050

Description:
Checkpoint-enabled user backups were performing an automatic retry
(limited by the failure history). But user backups should not auto retry.
--------------------------------------------------------------------------------
Etrack Incident = ET312346

Description:
If you try to cat_convert an image where the policy name contains a
Period (full stop), and the letter (f) follows immediately after that full
stop, then the cat_convert says the file does not exist.

Workaround:
To avoid this issue, do not create policies with names that contain ".f".
--------------------------------------------------------------------------------
Etrack Incident = ET303529 ET317435

Description:
Backup jobs with multiple streams where the individual stream selections
start with the same path can produce image files which, when browsed, do no
list all of the files in the backup.

Also, .f files created in NetBackup 4.5 versions for non-standard,
non-Windows clients may not show all files in the backup when browsed
under NetBackup 5.1.
--------------------------------------------------------------------------------
Etrack Incident = ET312384

Description:
Policy names that contain ".f" cause premature EOF on Full TIR Backups on
the first try of jobid and when following an incremental.

Workaround:
To avoid this issue, do not use policy names that contain ".f".
--------------------------------------------------------------------------------
Etrack Incident = ET352027

Description:
If an attempt to create a binary .f file is done with file entries without
user or group data, the attempt would fail but leave a zero-length .f
file. This caused a subsequent attempt to create the .f file in ASCII
format.
--------------------------------------------------------------------------------
Etrack Incident = ET375769

Description:
If many Flashbackup images are created using an ASCII image format,
cleanup fails with the message, "too many open files".

Workaround:
To avoid this issue, use the binary .f file format to create the
Flashbackup images.
--------------------------------------------------------------------------------
Etrack Incident = ET331244

Description:
The miggetvol performance was very poor (eight hours for a VOLDB
with 981 entries, with an FHDB of 500MB and FNDB of 250MB).
--------------------------------------------------------------------------------
Etrack Incident = ET374771 ET388368

Description:
Tlhcd may dump core when running dump_tables from ltid -tables command.

Tlhcd needs to check for a media ID with all spaces for an ID to be the
last media in the list returned from the robot controller.
--------------------------------------------------------------------------------
Etrack Incident = ET371650

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.
--------------------------------------------------------------------------------
Etrack Incident = ET336220

Description:
The removal of a copy of a backup image was not occurring when the copy
expired. This occurred when the operating system was Linux and the file
system (where the NetBackup database resided) was VxFS.
--------------------------------------------------------------------------------
Etrack Incident = ET317430

Description:
Bpbrm processes would hang after a backup was complete, or on Windows media
servers, an unrelated bpbrm or bptm process would unexpectedly terminate
with a 150 status (termination requested by administrator).
--------------------------------------------------------------------------------
Etrack Incident = ET341334

Description:
If using Multiple Data Streams, there would possibly be a long delay in
scheduling jobs. The bpsched log would show many hosts_equal calls that
were contributing to the delay.
--------------------------------------------------------------------------------
Etrack Incident = ET313685

Description:
The bpnbat -login text was wrong and has been corrected.


--------------------------------------------------------------------------------
Etrack Incident = ET394941

Description:
User backups or archives that do not find an active policy/schedule to use
were marked as resumable, but without the policy/schedule information, the
job could not be resumed.
--------------------------------------------------------------------------------
Etrack Incident = ET394947

Description:
A duplication may have been reported as successful if a defective tape
drive would incorrectly report a tape mark on the read operation, followed
by an I/O error. This patch detects this error condition.
--------------------------------------------------------------------------------
Etrack Incident = ET203198 ET225277

Description:
With NetBackup Explorer Extensions enabled, backup jobs started by using
the "Backup Now" context-sensitive menu item will no longer fail with a
status 12.

Workaround:
To avoid this issue, use NetBackup to do backups.
--------------------------------------------------------------------------------
Etrack Incident = ET371680

Description:
The synthetic backup process can begin reading the wrong block number from
tape during the synthetic backup image creation, causing the synthetic
backup to fail. This can happen when there are more than one tape drive
is available to read the component images.

The following sample log message is a symptom of this failure:

bptm 12090 first XFERBLOCK indicated block number of 478341120 but initial
positioning was for block 193352448

This message indicating an unexpected block number read will be seen in
both the job details for the synthetic backup job, and in the bptm log.

Workaround:
You can avoid this problem by downing drives so that only two drives
are available for creating the synthetic backup - one drive for reading
and one drive for writing.

After the synthetic backup job actually mounts the first volume to be read
and mounts the volume to be written, you can safely increase the number of
up drives.

--------------------------------------------------------------------------------
Etrack Incident = ET350592

Description:
When performing an Intelligent Disaster Recovery on a Windows NT 4.0 system,
bpcd.exe may generate an application exception.
--------------------------------------------------------------------------------
Etrack Incident = ET270455

Description:
Directories were not listed when browsing a backup on a policy that
allowed multiple data streams .
--------------------------------------------------------------------------------
Etrack Incident = ET383845

Description:
This patch enables general backup and restore support for SQL Server 2005.
Since this patch was released, new SQL Server features that require changes
to the SQL backup API or the SQL language are not supported until NetBackup
6.0. The minimal level of SQL Server 2005 supported by this patch is the
June 2005 Community Technical Preview.

Additional Notes:
Consistent with new functionality provided under SQL Server 2005, this
patch does support inclusion of full text catalog with database backups.
However, there are two restrictions placed on SQL Server 2005 full text
catalog backups.

(1) If the SQL Server 2005 database contains a full text catalog, then
the backup will not be backed up using a snapshot method. If an advanced
client policy is selected for backup, then the database will be backed up
using the standard backup method.

(2) A database move attempted on a SQL Server 2005 database that contains
a full text catalog, will fail with a message such as the following:

DBMS MSG - <[Microsoft][SQL Native Client][SQL Server]File
'sysft_HerCatalog' cannot be restored to 'C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTData\HerCatalog'. Use WITH MOVE to identify a valid
location for the file.>

This indicates that SQL Server 2005 expects to be provided a new location
for the full text catalog directory. To resolve this issue, update the
move script by providing a valid directory for the full text catalog. For
example, to specify that the full text catalog named HerCatalog should be
placed in directory "c:\NewLoc\HerCatalog\" provide the following lines in
the move script:

MOVE "sysft_HerCatalog"
TO "C:\NewLoc\HerCatalog\"

After this update has been made, rerun the move script to carry out the
move operation.
--------------------------------------------------------------------------------
Etrack Incident = ET350601

Description:
When performing backups and collecting disaster recovery information, the
DRFile.exe process may not terminate.
--------------------------------------------------------------------------------
Etrack Incident = ET317726

Description:
When performing multi-streamed backups and collecting disaster recovery
information, the DRFile.exe may crash when it runs multiple times in
immediate succession.
--------------------------------------------------------------------------------
Etrack Incident = ET301436

Description:
When performing IDR and the disk layout has "holes" in the disk numbering
scheme, this may prevent the disks from being correctly reconfigured.
--------------------------------------------------------------------------------
Etrack Incident = ET311201

Description:
NetBackup for SQL Server may create an incorrect move script in the
following scenario:

1. The SQL host contains multiple instances.
2. Two of the instances contain a database with the same name.
3. Both like-named databases are backed up to the same master server.

When this happens, a move script generated for database A of the first
instance may specify the file paths of database files from database B of
the second instance.
--------------------------------------------------------------------------------
Etrack Incident = ET287789

Description:
Raw partition backups would fail if a mount point was created using
mountvol in the bpstart script. If the mount point existed prior to the
backup being initiated it would work fine.
--------------------------------------------------------------------------------
Etrack Incident = ET365007

Description:
When performing a full backup of UNC filepaths, the access times on files
and directories may end up being the same as the time of the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET366161 ET366163

Description:
In certain firewall configurations, multistream backups from Linux client
may fail with status 25 if vnetd connect-back is used.
--------------------------------------------------------------------------------
Etrack Incident = ET311175 ET311173

Description:
If the add_slave_on_clients command is unable to add the media server
entries to one client, it may incorrectly update the media servers on
subsequent clients. Typically, only one media server will be added to
the remaining clients.

Workaround:
To avoid this issue, use the Host Properties interface or the
bpsetconfig admincmd to update the server list for the clients.
--------------------------------------------------------------------------------
Etrack Incident = ET300174 ET299670 ET300175 ET300176

Description:
bpbrm would hang if a database agent backup failed in a certain way.
The job would appear to be running in the Activity Monitor until an
administrator terminated it.
--------------------------------------------------------------------------------
Etrack Incident = ET322850 ET322817 ET322851

Description:
When a server includes multiple network interfaces and is configured
For NBAC, other NetBackup machines may reject connections from the server
with authorization failures. This patch insures that the server presents
the correct credential to the other NetBackup machines.
--------------------------------------------------------------------------------
Etrack Incident = ET312441

Description:
When running a backup with NetBackup for SQL Server and the SQL Server
Is stopped, the application backup failed with an error 41, however, the
scheduled job hung until it was killed. In addition, the dbbackex.exe
and bphdb.exe processes continued to run indefinitely.
--------------------------------------------------------------------------------
Etrack Incident = ET212962

Description:
When performing a restore from registry backups (file system type, not from
System State) and restoring registry keys, errors are no longer generated
when restoring the keys.
--------------------------------------------------------------------------------
Etrack Incident = ET326687

Description:
bpbrm log messages were not being pulled in by backuptrace for multiplexed
backups.
--------------------------------------------------------------------------------
Etrack Incident = ET376483

Description:
A vulnerability has been confirmed in the NetBackup Volume Manager
daemon (vmd). By sending a specially crafted packet to the Volume
Manager, a stack overflow occurs. This is caused by improper bounds
checking. Exploitation does not require authentication, thereby
allowing a remote attacker to take over the system or disrupt the
backup capabilities. Further testing and code inspection has revealed
that all other NetBackup 5.0 daemons are potentially affected in the
same manner.

Therefore, any Master Servers, Media Servers, Clients and Console
Machines at this version level are subject to this vulnerability.
However, NetBackup 5.0 database agents are not affected by this issue.

Refer to the Related Document section for more details.
--------------------------------------------------------------------------------
Etrack Incident = ET378008

Description:
The vmoprcmd -comment <drive_index> <comment_string> command would
overwrite the serial number specified if the comment_string size was 26.
--------------------------------------------------------------------------------
Etrack Incident = ET396047

Description:
The robotic inventory, vmupdate, may fail after encountering a media of
different density. The problem is that vmupdate was not taking the media
type of standalone media (if available) into consideration while
determining the media type of the media to be moved into the robot.
--------------------------------------------------------------------------------
Etrack Incident = ET365001

Description:
When performing a disaster recovery type of restore where the registry of a
Windows XP or a Windows 2003 machine is being restored, the machine may not
boot after the restore.
--------------------------------------------------------------------------------
Etrack Incident = ET401485

Description:
If the forked re-read storage unit process detected a transient error, it
would error, then exit and remove the scheduler message queues.
--------------------------------------------------------------------------------
Etrack Incident = ET384759

Description:
A potential race condition exists if a Windows client backup receives a
134 status (resource busy).

The race condition was caused because the bpfis process had already
Started taking a snapshot and bpfis has no knowledge of the resource
failure. So, the snap is taken, but when it is completed, there is no
bpbrm and bpsched (child) process running to accept the snap information.

When the job is later re-scheduled, this (unrequested) snap information
Was passed back to the new bpbrm and bpsched. The unrequested snap
Information confused bpsched (child).
--------------------------------------------------------------------------------
Etrack Incident = ET294366

Description:
vmd would hand after 21 days under VxSS/NBAC.
--------------------------------------------------------------------------------
Etrack Incident = ET319844

Description:
During the alternate client restore, the secondary restore process was not
passed the value for the browse client (source client).
--------------------------------------------------------------------------------
Etrack Incident = ET352756

Description:
Backups with UNC paths would fail with a status 71.
--------------------------------------------------------------------------------
Etrack Incident = ET299436

Description:
An extended value (90 days, for example) for the "Keep Logs for x Days"
global configuration setting appears not to work. The debug logs are
still deleted after about a month on NetBackup media servers that
are included as part of the catalog backup configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET404678

Description:
Bprd was dumping core, and the stack trace looked similar to the following:

Core was generated by `bprd -dontfork -mpxmain'.
Program terminated with a signal 11, �Segmentation fault�.

#0 0x00034ccc in write_monitor_status ()
(gdb) where
#0 0x00034ccc in write_monitor_status ()
#1 0x0003f204 in write_clnt_monitor_status ()
#2 0x0004f7e8 in terminate_restore ()
#3 0xfdd9efc8 in __tbl_10_small_start () from /usr/lib/libc.so.1
#4 0xfdd53990 in posixgetdst () from /usr/lib/libc.so.1
#5 0x0005f9ac in run_restores ()
#6 0x00063bd4 in run_mpx_main_bprd ()
#7 0x00021ad8 in main ()
--------------------------------------------------------------------------------
Etrack Incident = ET387442

Description:
The GDM Windows dashboard would hang on Windows 2003 with SP1 installed.
--------------------------------------------------------------------------------
Etrack Incident = ET336949

Description:
migcopy failed for files that were larger than 30 Gigabytes.
--------------------------------------------------------------------------------
Etrack Incident = ET406311

Description:
The newdataSock was not being closed before a backup was requeued. This led
to sockets remaining in the WAIT_CLOSE state on Windows after the backup
completed.
--------------------------------------------------------------------------------
Etrack Incident = ET300998

Description:
RMAN - alternate client restore times out after a successful partial
restore by media server.

Though this problem was encountered while doing an Oracle alternate client
restore, the nature of the problem is such that it can happen for any
XBSA-based partial restore.

When the client is done restoring - partial restore - but there is still
data to be read, the client sockets are closed but bptm/bpdm wait for the
data to be read causing it to eventually time out with an error.
--------------------------------------------------------------------------------
Etrack Incident = ET315538

Description:
Allow a user to run a restore job for an Exchange 2000 and 2003 server
instance that contained only the Exchange database files, and a separate
job that contained only the Exchange log files.

Workaround:
To avoid this issue, restore the Exchange 2000 and 2003 database and
log files in the same restore job.
--------------------------------------------------------------------------------
Etrack Incident = ET399090

Description:
In migd, the NFS server-daemon, starvation avoidance code creates one user
event for each attempt to read the file. The issue is that the NFS client
repeatedly tries the read request for a purged migrated file, resulting in
many user events. In addition, it causes a lot of system resources to be
used. On HP-UX 11 systems, it can cause DMAPI requests to fail with an
errno == 11.
--------------------------------------------------------------------------------
Etrack Incident = ET349769 ET419204

Description:
Group or User names of longer then 31 characters would cause the catalog
to consider an image invalid. Invalid images are put in the db.corrupt
directory, and the media is reclaimed. This change enables the use of
32-character-long user and group names, which is what bpbkar bpbrm
supports. When an image is found to be invalid the corresponding media
was frozen to keep the media from being reused.

Workaround:
To avoid this issue, do not use user or group names longer then 31
characters, and when cleanup is run, check for images that are put in
the db.corrupt directory and import them if required.
--------------------------------------------------------------------------------
Etrack Incident = ET343034

Description:
Changes to fix "bplist returns duplicate listings for a DB2 image" caused
queries of these images in ASCII mode to not work correctly. This change
makes DB2 work with both binary and ASCII.

Workaround:
To avoid this issue, use the binary catalog on servers that are backing up
DB2 databases.
--------------------------------------------------------------------------------
Etrack Incident = ET213349

Description:
On an Exchange 2000/2003 server with Circular logging enabled on a storage
group, a differential backup would fail to backup any log files. The debug
log for bkar would log the following error:

3:09:43.796 PM: [4556.3884] <2> ov_log::V_GlobalLog: ERR -
BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'\Microsoft
Information Store\Test' Failed! (0xFFFFFE4C:The operation cannot be
performed since circular logging is enabled.

However, the backup still succeeds with a status 0.
--------------------------------------------------------------------------------
Etrack Incident = ET324702 ET289704 ET324226

Description:
The XBSA Agent PFI backups resulted in status 156 errors. In this
failure, the scheduler is receiving a file list, �start�(FI_FILE_START)
and file list �end�(FI_FILE_END), however, it would not receive a file
list �body�.
--------------------------------------------------------------------------------
Etrack Incident = ET410630

Description:
When running VSP-enabled backups to backup open and/or active files,
backups may intermittently hang after VSP snapshot creation has taken
place. The bpbkar32 logs indicated that snapshot was successfully
enabled for the backup but inexplicably stopped while backing up files.
The bpbkar32 backup process then stopped processing and appeared to
hang until it was explicitly killed by Windows Task Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET412987

Description:
The NetBackup for SQL Server interface would not open in some environments
if there were a large number of SQL Server hosts in the network. In this
situation, the following information appeared in the dbclient log:

14:10:51 [1356,3580] <32> CGlobalInformation::SQLEnumerator: ERR - Error
Enumerating SQL Server Instances
14:10:52 [1356,3580] <32> CSQLDBMSOptions::OnInitDialog: ERR - Error 2 has
been returned from GetSQLHostInstanceList
--------------------------------------------------------------------------------
Etrack Incident = ET327541

Description:
Vault would mark DSSU and DSU images for expiration after a successful
duplication. However, the DSSU images should not have been marked, because
they would expire according to DSSU schedule/configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET406199 ET405465

Description:
Vault Iron Mountain Reports no longer include un-ejected media in the
Distribution ('D') section.
--------------------------------------------------------------------------------
Etrack Incident = ET409983 ET348174

Description:
The following modifications have been made to Vault's Iron Mountain Reports
- The date is now displayed starting in the 91st column (instead of 89).
- The Inventory Section ('I') now includes only Vaulted Media (not
Recalled Media).
- The section footers now include the number of media reported in
Respective Sections.
--------------------------------------------------------------------------------
Etrack Incident = ET410924

Description:
Oracle RMAN backups failed with intermittent ORA-27192 errors.

Even though the client has closed the socket, bptm does not recognize that
act and eventually times out the client.
--------------------------------------------------------------------------------
Etrack Incident = ET379394

Description:
The DB2 BAR interface does not enable you to browse an instance created on
drives other than the default.
--------------------------------------------------------------------------------
Etrack Incident = ET371927

Description:
Because of security relates issues, the NetBackup 5.0 MP6 patch will be
released with the 3.23.59 version of MYSQL server binary.
--------------------------------------------------------------------------------
Etrack Incident = ET412698

Description:
Special files (Such as ntuser.dat, ntuser.dat.log, and so on) could not
be backed up when the backup job was started and the user logged off the
system. Now those files are backed up even if the user logs off after the
backup job is started.
--------------------------------------------------------------------------------
Etrack Incident = ET412788

Description:
When performing an incremental backup of Exchange mailboxes, a status 0
would be reported for the backup even though no data was actually backed
up. This occurred when the Exchange mailbox logon failed.
--------------------------------------------------------------------------------
Etrack Incident = ET411778 ET399523

Description:
Vault's Recovery Report included redundant information if the NetBackup
installation vaulted multiplexed backup images. Vault used excessive
memory during the Report generation and distribution phase.
--------------------------------------------------------------------------------
Etrack Incident = ET304426

Description:
NetBackup 5.x report filenames no longer contain the sessionID.
--------------------------------------------------------------------------------
Etrack Incident = ET304504

Description:
In NetBackup 5.0 the vlt_end_notify script ran before the reporting
occurred.
--------------------------------------------------------------------------------
Etrack Incident = ET273225

Description:
Vault post-eject reports no longer produced if there were no tapes to
eject.
--------------------------------------------------------------------------------
Etrack Incident = ET380108

Description:
The Vault reports eject failed, however the tapes were still ejected
(TLH robot).
--------------------------------------------------------------------------------
Etrack Incident = ET416208 ET414212

Description:
A condition existed that resulted in excessive hosts_equal calls in the
bptm log.
--------------------------------------------------------------------------------
Etrack Incident = ET309015

Description:
An issue existed that caused backups to fail when writing tir. The
bptm log contained the following information.

15:46:57.554 [29981] <2> setup_tir_read: successfully connected to bpdbm to
read TIR file, size is 577960 bytes + 0 GB
15:46:57.554 [29981] <2> io_write_back_header: drive index 12,
grzfs03_nafsp02_vol0_1108477090, file num = 50, mpx_headers = 0, copy 1
15:46:57.658 [29981] <2> io_write_block: ndmp_tape_write_func returned 1024
15:46:57.758 [29981] <2> NdmpMoverClient: ndmp_mover_set_record_size(64512)
15:46:57.858 [29981] <2> NdmpMoverClient: ndmp_mover_set_window(0,
18446744073709551615)
15:46:58.058 [29981] <2> NdmpMoverClient: ndmp_mover_listen returned addr
10.200.12.10 port 12091
------------
15:50:42.667 [29981] <16> NdmpMoverClient: ERROR ConnectSocket - connect
failed: 145 Connection timed out
15:50:42.667 [29981] <16> NdmpMoverClient: ERROR ConnectSocket failed
15:50:42.668 [29981] <16> NdmpMoverClient: ERROR Start failed
15:50:42.947 [29981] <2> NdmpMoverClient: mover halted reason
NDMP_MOVER_HALT_ABORTED

Additional Notes:
To disable NdmpMoverClient in netbackup/db/config/ndmp.cfg, add the
string, NDMP_MOVER_CLIENT_DISABLE.
--------------------------------------------------------------------------------
Etrack Incident = ET414327

Description:
NetBackup was using SIGALARM to kill a child process. This signal caused
the Domino server to crash as it also waited for SIGALRM.
--------------------------------------------------------------------------------
Etrack Incident = ET394971

Description:
A restore from a FlashBackup image hung on a Linux server with an
indication of a double free of a memory allocation.
--------------------------------------------------------------------------------
Etrack Incident = ET414056

Description:
NDMP DAR restore fails when a tape has been imported
or �FORCE_RESTORE_MEDIA_SERVER� is set to a different NetBackup platform
(UNIX to Windows or Windows to UNIX). The restore fails with the
following error:

''NDMP_LOG_NORMAL 0 RESTORE: FILE_NAME: File does not exist in backup.''



Workaround:
To avoid this issue, use the same platform (UNIX or Windows) where the
backup was performed.

Additional Notes:
The actual problem exists on the backup site. To do DAR restore using a
different NetBackup platform (UNIX to Windows or Windows to UNIX), you
have to perform a backup using this patch.
--------------------------------------------------------------------------------
Etrack Incident = ET415502 ET411347

Description:
Changes were made to ensure primary and non-primary source images on disk
are sorted correctly for duplication. In addition, changes were made to
avoid the creation of extra duplication jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET301369

Description:
When backing up open and/or active files using VSP on a Windows NT4
client, the Windows Open File Backup, global drive snapshot functionality
behaves like the individual drive snapshot feature, individually creating
snapshots of each file-list directive instead of all of the volumes that
are required for a backup at the start of a backup job. This only affects
Windows NT4 clients in NetBackup 5.0.
--------------------------------------------------------------------------------
Etrack Incident = ET377460

Description:
The lastest VxFI SDK that was used to create VSP snapshots were naming
VSP cachefiles using a .VSP extension. Subsequently, NetBackup code
changes needed to be made to exclude these files from the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET322262

Description:
When running non-multi-streamed Windows Open File Backup-enabled backup
jobs, the backup jobs sent too many FIS_ID messages to bpsched, and caused
it to fail backups with a status 24.
--------------------------------------------------------------------------------
Etrack Incident = ET414649

Description:
Oracle backup failed because bphdb.exe would quit with an Application
Error.

This problem could be encountered when using the following agents :
- ORACLE
- SAP
- SYBASE
- DB2
- BACKTRACK


--------------------------------------------------------------------------------
Etrack Incident = ET416458 ET416260

Description:
Vault Eject jobs initiated from the command line or vltopmenu on Windows
did not provide updates on the console during the Job.
--------------------------------------------------------------------------------
Etrack Incident = ET375811 ET236537

Description:
When backing up and restoring large volumes with FlashBackup on windows
various problems existed, these included memory allocation problems for
incremental backups due to the fact that Microsoft does not guarantee
contiguous free space. Also there were various 32 bit integer overflow
conditions in the sfr, single file restore, code.
--------------------------------------------------------------------------------
Etrack Incident = ET230375

Description:
For Localization, the NetBackup Vault report output contained unreadable
information making it useless.
--------------------------------------------------------------------------------
Etrack Incident = ET203223

Description:
Symantec never officially supported the ability to administer a new
server using an older interface, for example, using a NetBackup 5.0
interface to administer a NetBackup 5.1 master server.

The interface should prevent a change server to newer version of
NetBackup in 5.1 and, for all subsequent releases. This only applies
to major version changes. The change in the interfaces would not
prevent the administering of different patch versions of NetBackup,
for example, a NetBackup 5.0GA interface would still be able to
administer a NetBackup 5.0 MP1 server.
--------------------------------------------------------------------------------
Etrack Incident = ET299103

Description:
During a Single Instance Store (SIS) backup of Exchange Mailboxes, one
of the attachments failed to backup. Bpbkar logged the following
information when this issue was encountered.

2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -
v_beds_mbox::V_FindNextSpcDblk() ENTER Index:2177
2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -
v_beds_mbox::V_FindNext() EXIT
Name:F3168B482D6B4C10172E7DC743C7EE24C833F65189C456FD bRC:true
LastError:0x0:
2:04:36.288 AM: [5536.424] <2> tar_backup::backup_startfile_state: TAR -
Backup: Microsoft Exchange
Mailboxes:\_Attachments_\F3168B482D6B4C10172E7DC743C7EE24C833F65189C456FD
2:04:36.288 AM: [5536.424] <2> ov_log::V_GlobalLog: INF - StreamInfo
Id:MBMG
FSAttrib:0x0 FSAttrib:0x2 CAlgor:0x0 Flags:0x0 Size:0
2:04:36.304 AM: [5536.424] <2> ov_log::V_GlobalLog: INF - Exchange Mailbox
Stream Data
2:04:36.351 AM: [5536.424] <2> tar_base::V_vTarMsgM: FIL - 498621 105973
6202357 92 33216 root root 5165926 1098296973 1098296973
1098296873 /Microsoft Exchange
Mailboxes/_Attachments_/F3168B482D6B4C10172E7DC743C7EE24C833F65189C456FD
2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -
v_beds_mbox::V_FindNextSpcDblk() ENTER Index:2178
2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: ERR -
v_beds_mbox::V_FindNextSpcDblk():FS_GetSpecialDBLKS() Index:2179 Failed!
0xFFFFFEA9:0xa000fea9 (2684419753)
2:04:36.351 AM: [5536.424] <2> ov_log::V_GlobalLog: INF -
v_beds_mbox::V_FindNext() EXIT Name: bRC:false
LastError:0xFFFFFEA9:0xa000fea9
(2684419753)

When this error was encountered, the Exchange mailbox SIS backup was
aborted without attempting to backup any additional attachments. A
status 1 was returned for the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET417743

Description:
When performing a backup and the backup was waiting on a tape to get
mounted and/or positioned, the non-paged pool memory associated with the
bpinetd.exe process would grow.
--------------------------------------------------------------------------------
Etrack Incident = ET416983

Description:
NetBackup configuration variables that were set using the RMAN PARMS
option were not being used by the Oracle Agent.

Workaround:
To avoid this issue, use the RMAN SEND command to specify NetBackup
configuration variables.
--------------------------------------------------------------------------------
Etrack Incident = ET393136 ET414942

Description:
Added the following robots:
- Certance CLL6400
- Falcon Stor VTL
- HP 1x8 Autoloader
- NEC T16A
- SONY CSM-20
- STK VDRIVE

Updated the following robots:
- ADIC Scalar 24
- ADIC 224
- ADIC 234
- ADIC 448
- ADIC 458
- ADIC Scalar 24
- ADIC Scalar 1000
- ATL M1500
- ATL M2500
- ATL P3000
- Compaq MSL5000
- Dell PV-132T
- Exabyte VXA-2 1x10 1U
- Exabyte 440
- Exabyte 480
- HP MSL5000
- HP MSL6000
- HP VLS
- IBM 3583
- IBM 7337
- Spectralogic PYTHON

Additional Notes:
Devices can be included in this file before they are officially supported.
--------------------------------------------------------------------------------
Etrack Incident = ET417526

Description:
Security permissions of some of the temp files were set to 666. Those
Permissions have been changed to 644.
--------------------------------------------------------------------------------
Etrack Incident = ET319000

Description:
Changes have been made to provide the following capabilities:
- Option to change the replica ID of unlogged databases
- Option to skip recovery of logged databases

Additional Notes:
The touch file at <NetBackup Install Path>\LOTUS_NO_RECOVERY can be used
To control recovery of logged Lotus Notes databases. During restore,
The presence of the file will bypass recovery of logged Lotus Notes
databases.
--------------------------------------------------------------------------------
Etrack Incident = ET415373

Description:
Changed the Makefile.inc to use the latest version (v4.1.135) of VxMS.
This version fixes many escalation problems such as encryption and open
handle problems. Also contains further debugging mechanism to help with
future escalations.
--------------------------------------------------------------------------------
Etrack Incident = ET422757 ET499607

**Description:**
Synthetic Backup produces an image that contains only the last
incremental if a previous full synthetic backup (from incremental
backups) was manually expired.
--------------------------------------------------------------------------------
Etrack Incident = ET416687

Description:
If a customer created an image list (bpimage -create_image_list -client
<client) after an incremental TIR backup and then ran a full or cumulative
differential backup, the TIR_INFO field in the image was not updated to 10.
As a result, TIR information was not pruned from the backup image.

Workaround:
To resolve this issue, remove image list files from the client directory.
--------------------------------------------------------------------------------
Etrack Incident = ET355631

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.
--------------------------------------------------------------------------------
Etrack Incident = ET423634

Description:
A change has been made to avert a potential vulnerability in a Java
authentication service that runs on VERITAS NetBackup servers and clients.
This change prohibits remote attackers from executing arbitrary code on a
targeted system. In addition, Symantec recommends that users block the
affected ports from external network access.
--------------------------------------------------------------------------------
Etrack Incident = ET421519

Description:
The first line of the header of the bpclimagelist command was occasionally
not displayed. This potentially could happen for any server type, but was
seen when the master server was Linux. This would affect BMR processing.
--------------------------------------------------------------------------------
Etrack Incident = ET427127

Description:
visd consistently went down on HP_UX platforms when using the new 3.23.59
nbdbd binary.
--------------------------------------------------------------------------------
Etrack Incident = ET420747

Description:
The disks on Hitachi arrays at higher ports cannot be backed up when
using Shadowimage, because the CSH and Port number on the disks are
more than two digits long.

The fix enables ShadowImage to backup Tagma array disks that reside on
upper ports.
--------------------------------------------------------------------------------
Etrack Incident = ET429022

Description:
A change was made to ensure the SCSI inquiry output for Hitachi array
from pagecode83 always to be 4 digits so that shadowimage will work.

In rare cases, SCSI inquiry output for Hitachi array from page code 83
(bytes 32 and 33) returned two digits instead of four digits of numbers.

This fix filled in the digits and enabled Shadowimage to work.
--------------------------------------------------------------------------------
Etrack Incident = ET430821

Description:
Binding to a socket that was already in use caused the following error to
appear in the bpsd log file:

10061 - WSAECONNREFUSED

Workaround:
To avoid this issue, use vnetd.
--------------------------------------------------------------------------------
Etrack Incident = ET426765

Description:
User initiated backups fail while creating .f file.
The policies were created on the fly.
--------------------------------------------------------------------------------
Etrack Incident = ET496689

Description:
Fixed a potential looping problem that occurred in the bpbkar client
process if an Exchange Mailbox SIS attachment could not be accessed.
--------------------------------------------------------------------------------
Etrack Incident = ET497379

Description:
The 'make messages' command failed because of PrgPCX0322N and
PrgPCX0348N were different.

PrgPCX0322N "Backing up Exchange 2000 ESE object %%s\n"
PrgPCX0348N "Restoring Exchange 2000 ESE object %%s\n"

PrgPCX0322N "Backing up Exchange ESE object %%s\n"
PrgPCX0348N "Restoring Exchange ESE object %%s\n"
--------------------------------------------------------------------------------
Etrack Incident = ET498524

**Description:**
In a rare condition one or more backups would be corrupt when using Inline
Tape Copy (ITC) with multiplexed backups. This would potentially happen
under the following conditions:

- ITC was enabled with 2 or more active copies.
- Multiplexing was enabled with 2 or more active backups.
- The schedule configuration had "continue if the copy fails" flag
set for the copy that failed in the next step.
- A copy other than the first active copy encountered "end of media", so
a new media was needed for this copy. Then, there was a problem
getting or setting up media (for example, writing the media header)
such that this copy failed before continuing the backup.
- The last buffer written to the first active copy prior to the "end of
media" on the other copy was not the first active backup.

Workaround:
To avoid this problem, do one of the following:

- Edit the schedule configuration to disable the "continue if copy fails"
flag.
- Disable multiplexing.
- Disable ITC.

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

=========
NB_50_5_M
=========

Etrack Incident = ET258456

Description:
Added support for the following drive types in ACS robots:
STK 10000A (T1)
HP LTO-3

Added support for the following media types in ACS robots:
T10000T1
T10000TS
T10000CT
LTO-400G


(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET276832

Description:
User archive or synthetic backups that have checkpoint enabled and
receive a status 134 (resource busy) will be rescheduled. But the Activity
Monitor would list the job as "done" with a status 134.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277275

Description:
A potential memory leak in the NetBackup scheduler has been resolved.

Additional Notes:
This patch contained level src/nb/sched/dbmisc.c 1.88.4.22.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277276

Description:
Corrected a situation that caused the scheduler to lose a backup in the
middle of a catalog backup.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET270620 ET270622

Description:
There are cases when a NetBackup administrator can administrate most things
on a NetBackup master server (such as policy configuration), but is no
allowed to access Host Properties on clients.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET260174

Description:
In the Windows NetBackup Administration Console, there is a timing issue
that causes the display to show multiple instances of the same physical
drive when there should be one line-entry, per physical drive in an SSO
environment.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET279000

Description:
Corrected an issue with the Sony TSL-11000 tape library that caused an error
when moving the cleaning tape to its appropriate slot.

Workaround:
The cleaning actual works, but the cleaning statistics do not get updated.
Running a tpclean -M <drive name> after the failed clean corrects this issue.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET283487

Description:
Initiating multiple Oracle backups was causing a crash to occur in the
scheduler. Each of the Oracle backups attempted to read/update/write a
group ID file (used for synching snap backups), but there was no lock
mechanism on the file access, so each Oracle backup had the potential to
corrupt another?s file access.

Workaround:
To avoid this issue, you should stagger window openings for Oracle backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET283799

Description:
EFS backups were not functioning properly. Backups of encrypted files
completed with a status of "partially successful", and the encrypted files
were not backed up.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Etrack Incident = ET272607

Description:
If a set of configuration options in bp.conf is very large, it could cause
bpgetconfig and the GUI to not display any of the items. This applied to
items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
In addition, if that set of configuration options was edited in the GUI,
for example to add a new server to the CONNECT_OPTIONS, all of the
previous data for that set of options was lost and only the new data would
be in bp.conf.

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

All NetBackup Windows Clients All NetBackup PC Clients All NetBackup Unix Clients
--------------------------------------------------------------------------------
Etrack Incident = ET272607

Description:
If a set of configuration options in bp.conf is very large, it could cause
bpgetconfig and the GUI to not display any of the items. This applied to
items in bp.conf with the same name, for example CONNECT_OPTIONS or SERVER.
In addition, if that set of configuration options was edited in the GUI,
for example to add a new server to the CONNECT_OPTIONS, all of the
previous data for that set of options was lost and only the new data would
be in bp.conf.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET284895

Description:
When running a Restore job, the information about the job did not appear in
the Job Details -> Job Overview tab in the Activity Monitor. However, the job
would still complete successfully.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET286714

Description:
The bpimmedia -spangroups output was not displaying a span group if the
span occurred in a copy other than copy 1, and one or more preceding
copies were expired.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET289147

Description:
Corrected an issue where backups were possibly skipped if the frequency was a
multiple of 24-hours (interval mode) and the backup window was greater than
24-hours. (Only the first backup was run in the failure scenario.)

Workaround:
To avoid this issue, make your backup windows no greater than 24-hours.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET285171

Description:
A Synthetic Backup Image could be expired while it was still being written.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET274776

Description:
Deferred ejects fails with an "Invalid command parameter" in the vault log
(although the Activity Monitor reports success) in the following
conditions :

* The Vault session runs on a UNIX master server and the profile is
configured for deferred eject.

* The NetBackup Administration Console is started on Windows and then the
Change Server option is used to change to the UNIX master server on
which Vault is licensed.

* Action > Deferred Eject is selected, any of the "Run eject" options are
selected, and then Eject is clicked.

Workaround:
Use the Java NetBackup Administration Console (jnbSA) to perform deferred
eject on a UNIX or Linux master server.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET210524

Description:
When performing a backup on a Windows 2003 server, the event log files may
not get backed up. An error containing the following message can be seen
in the bpbkar32 debug log:

ERR - unable to backup event log: 'C:\WINDOWS\system32\config\DnsEvent.Evt'
(WIN32 87: The parameter is incorrect. )

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET261388

Description:
A non-English SQL help file was not linked to the help directory correctly.



Workaround:
To avoid this issue, you can install the localized version of sql help file in
NetBackup\help\.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET233258

Description:
The non-English names were not legible in the NetBackup for SQL Server
progress viewer. The names will now display correctly.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET289682

Description:
A full DSSU disk could cause jobs to hang, if the media server was running
on a Windows/NT host. The backup image processed when the DSSU became full
would not be deleted in all cases.


(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET277846

Description:
Staging of images that were no longer in the catalog caused a 190 error.

Workaround:
To avoid this issue, manually delete the images that are not in the
catalog.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET277814

Description:
Restores with a Hitachi NAS filer failed. The NDMP log showed the
NDMP_DATA_START_RECOVER has the restore path, and listed it twice.

Workaround:
Restores will work as long as the file-system path (the path that was
initially backed up) is not selected. 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 Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET287624

Description:
When a client is included in multiple policies, synthetic backups may fail
if incremental backups for these policies were initiated at the same time.

Workaround:
To avoid this issue, set the "Maximum jobs per client" master server
property to 1.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET292764 ET289149

Description:
Corrected an issue where backups were possibly skipped if the frequency was a
multiple of 24-hours (interval mode) and the backup window was greater than
24-hours. (Only the first backup was run in the failure scenario.)

Workaround:
To avoid this issue, make the backup windows no greater than 24-hours.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET293145 ET219875

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 Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET277782

Description:
bpdm would corrupt a TIR file when a "disk full" condition was encountered.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET267554

Description:
After successful SQL Server backups, the bphdb log showed a Status 0 as a
severity <16> and ERR.

Workaround:
If you encounter this status, you can safely ignore the severity <16>
error if the Status in the bphdb log message is 0.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET289067

Description:
The backup fails when backing up more than 255 SQL Server databases from
one server using the $ALL command within the .bch file. The backup fails
on job 255 and the Automatic backup schedule job is left in a hung state.


All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET234559

Description:
The capability to eject tapes in ascending order by expiration date rather
than alphabetically is added with this patch.

To eject tapes in order by expiration date, create a SORT_EJECT_MEDIA file
in the vault/sessions directory. This "touch" file can be an empty file.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET203246

Description:
In Windows NetBackup Administration console, following Vault Reports 1st
column disappears after every run report command when data is available for
that report. So here every time user needs to resize the 1st column to see
the data.
1. Media Going Off-site
2. Media Coming On-site
3. Inventory

Workaround:
Resize the first column after each run report command.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET293956

Description:
The Media Manager Service, vmd, was not handling the QUERY_BYROBNUM_AND_SLOT
request correctly. Because of this, vmphyinv was not able to fetch the volume
record given for the robot number and slot, and was misbehaving.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET289973

Description:
There are occasional Dr. Watson crashes or program exception pop-ups when
running the NetBackup SQL Server agent. When these occur, they usually do
not prevent the backup from completing.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET293220

Description:
You can now restore Backup Exec images to clustered applications on
Windows (such as, Microsoft Exchange).

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET270191

Description:
Vault can report status 281 if duplication job skips a few images that have
already been duplicated. Instead, status 1 should be reported.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287111

Description:
An error occurred when a SAP online backup was started and a Tablespace
(PSAPES46CI) in the Oracle DB was placed in BACKUP MODE by the agent. The
backup received a STATUS 134 error in BPTM & BPBRM. The bpbkar, bptm, and
bpbrm processes would exit properly, however the SAP agent process
remained active, waiting for the backup to be queued again and rerun. This
caused the Tablespace (PSAPES46CI ) to be left in BACKUP MODE.

The following is an example log of how this error occurred.

03:08:23.624 [25925] <4> backint_monitor_log: [25926.00] 03:08:16 INF -
Processing /oracle/P01/sapdata4/es46ci_1/es46ci.data1

03:08:23.624 [25925] <4> backint_monitor_log: [25926.00] 03:08:19 INF -
BRSAP BR280I Time stamp 2004-11-28 03.08.19

03:08:23.624 [25925] <4> backint_monitor_log: [25926.00] 03:08:19 ERR -
bpbkar killed by SIGPIPE

Bpbkar gets 40 error, bptm & bpbrm 134 error
The backup gets requeued in the scheduler and then rerun. Unfortunately on
the Client the backup fails with this error:

03:08:23.624 [25925] <4> backint_monitor_log: [25926.00] 03:08:19 INF -
Waiting for mount of media id PFC121 on server S01Q02 for writing.

03:08:53.623 [25925] <4> backint_monitor_log: [25926.00] 03:08:46 INF -
Waiting in NetBackup scheduler work queue on server s01a20

03:09:23.623 [25925] <4> backint_monitor_log: [25926.00] 03:09:18 INF -
Waiting in NetBackup scheduler work queue on server s01a20

03:09:53.622 [25925] <4> backint_monitor_log: [25926.00] 03:09:51 INF -
Waiting in NetBackup scheduler work queue on server s01a20

03:10:08.622 [25925] <4> backint_monitor_log: [25926.00] 03:09:57 INF -
Processing /oracle/P01/sapdata4/es46ci_1/es46ci.data1

03:10:08.622 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 INF -
BRSAP BR280I Time stamp 2004-11-28 03.09.59

03:10:08.622 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 INF -
BRSAP #BEGIN /oracle/P01/sapdata4/es46ci_1/es46ci.data1

03:10:08.622 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 INF -
BRSAP BR280I Time stamp 2004-11-28 03.09.59

03:10:08.623 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 INF -
BRSAP BR345E Error in backup utility while switching the status of
file /oracle/P01/sapdata4/es46ci_1/es46ci.data1

03:10:08.623 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 INF -
BRSAP BR280I Time stamp 2004-11-28 03.09.59
03:10:08.623 [25925] <4> backint_monitor_log: [25926.00] 03:10:00 ERR -
SAP begin alter table space failed

Because the Tablespace (PSAPES46CI) is still in BACKUP MODE from the first
backup attempt.

All NetBackup Unix Clients
--------------------------------------------------------------------------------
Etrack Incident = ET233636

Description:
When backing up files on Windows that contain extended attributes,
bpbkar32.exe may crash.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET286655

Description:
An error occurred that would cause bpverify to fail with a 191 error on a
single master/media server. The operating system would time out the
socket before the processing finished.

CLIENT_READ_TIMEOUT = 1800
tcp_keepalive_interval = 7200000
tcp_time_wait_interval = 1000

06:48:42.943 [7244] <2> get_adaptable_string: (4) network read() error:
Connection reset by peer (131)
06:48:42.944 [7244] <2> db_FLISTreceive: expected 9, got 1

Workaround:
To avoid this issue, set the default time-out on sockets to be longer, or
perform a larger number of small backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET279260 ET293080

Description:
Corrected maislot timing issues that sporadically occur on certain robots when
using AUTO_UPDATE_ROBOT.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET264337

Description:
When performing IDR on a system and the backup images are encrypted,
statements similar to the following may be seen in the progress log:

WRN - File is 56-bit DES encrypted, but no decryption key is available
INF - TAR EXITING WITH STATUS = 5

Additional Notes:
After applying this patch, the DR files for the machines whose backup
images have been encrypted need to be recreated.

If the machine is in a state where IDR is being performed, the patch can
be installed on a different machine and then the files can be manually
copied over to the IDR machine.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET271314

Description:
Using the encryption algorithm, blowfish, on Solaris 9 platforms caused
set_ndmp_attr of ndmpmoveragent to fail. The following data is an example
of this failure.

[root@galvatron]:/:>set_ndmp_attr -verify
Verify Host name: galvatron
Connecting to host "galvatron" as user "root"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 2...
Opening session--successful with NDMP protocol version 2
host supports TEXT authentication
Logging in using TEXT method...
17:44:53.152 [03044] ndmp_net_read: connection 0x3e0d0: (5) end of file
detected
17:44:53.153 [03044] ndmp_message_receive: xdr_ndmp_header failed, unable
to
XDR decode
ndmp_connect_client_auth failed
set_ndmp_attr: host "galvatron" failed
NDMP failed to verify host


(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET266316

Description:
The "set_ndmp_attr -verify server" for remote NDMP would fail, if the
server's root/administrator password was more than eight characters long.

(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET266303

Description:
For NDMP restores on NetApp filers, more than 1024 files can be restored
using DAR.


(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET270773

Description:
IM filename format contains timestamp and re-generation of IM reports is
not allowed. This fix changes the IM filename to the following format:
CustomerNumber_Vault_SID_C/V.IM. Also regeneration of IM reports is now
allowed.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET199373

Description:
Chinese date are gibberish on the NetBackup 5.0 WinNT Chinese in Session ID
box and Search Result log box of Master/Vault_Report GUI.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET213753

Description:
The lost media report doesn't report offsite tapes of a different media
type.
In a scenario where a customer migrates from one media type to another,
the expiring offsite media of the old media type did not get reported in the
lost media report or the picklist for vault report.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET295112

Description:
The scheduler has been modified to correctly process a status 134 error race
condition in a multiplex backup.

This condition occurs when a multiplex child bpsched starts a backup, but
the storage unit is over committed. A status 134 is sent back to the
multiplex child bpsched, but the child 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 will not log the broken socket, but will correctly
read and process the 134 from the inbound connection.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET229930 ET295123

Description:
FlashBackup on Windows for incremental backups was allocating 32 times the
needed space for the bitmaps it needed. In addition, during incremental
backups the possibility existed that the FlashBackup code would attempt to
use structures in space that had previously been freed.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET294712

Description:
bpretlevel loops were echoing the phrase 'What?' when changing retention
levels. No input seems to be a satisfactory response to exit the loop until a
ctrl-C is entered. There did not seem to be any way to change retention
levels with the client interface because of this bug. A correction within the
source code has orrected this problem.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287371

Description:
When multiple disk staging jobs are initiated and the DSSU is at or
near capacity, some jobs may fail with a status 84 error, "disk full,
attempting to remove the same staged images".

The BPDM logs contained entries that indicated no matching entries were found
in the catalog, (db_IMAGE: db_end_sts() failed: no entity was found).

Workaround:
If the DSSU is nearing capacity, manually remove the previously staged
images. These images are identified by an additional zero-length file of
the same name, with a ".ds" extension.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET295589

Description:
In case of partial success of the eject step, media that were successfully
ejected will not be displayed in the non-vaulted report for that vault
session now.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET296132 ET270045 ET268600 ET260459 ET273679 ET220083 ET260459 ET274370

Description:
Added support for the following libraries:

- ARCHIVE Python 06241-XXX910B
- Certance CLL3200
- Diligent VTF Open
- Exabyte VXA 1x10 Autoloader
- Exabyte 1x7 Autoloader
- IBM DDS4 Autoloader
- IBM 3623 2SX
- SEAGATE DAT 9SP40-400910B"

Added support for the following drives:

- Exabyte VXA-2
- HP LTO3
- HP VS160
- IBM Ultirum-TD3, 3580-TD3

Changed Serialization for the following libraries:

- Sony CSM-200, CSM-100, CSM-60

Additional Notes:
Devices can be included in this file before they officially supported.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET161550

Description:
Oracle backups would fail when running concurrent RMAN jobs.


(NetBackup Clients: ALPHA HP Intel-NT Linux2.4 RS6000_433 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET297660

Description:
The v41.1.127 VxMS release level contains fixes for two problems. The first
fix enables DLM to work with FlashBackup on Windows. The second fix prevents
the VxMS function, vfm_readdir, from looping.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET296424

Description:
This bpbrm binary fixes an intermittent socket problem that occurs during
database backups. The backup may fail with a status of 54.

Examination of the bpbrm debug log will show the following:

07:10:52.662 [3832.2768] < 16> bpbrm listen_for_client: listen for client
timeout during accept from name listen socket after 60 seconds

Examination of the dbclient debug log will show the following type of
message:

02:24:07.956 [528.660] < 8> connectSock: WRN - connect() to server failed,
No connection could be made because the target machine actively refused it.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET287624

Description:
When simultaneous differential incremental backups are done for the
same client, a subsequent synthetic backup for that client may fail.

Workaround:
To avoid this issue, do not run simultaneous backups on the same client.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET300775

Description:
Using the Java Console to restore UNC formatted images on the network to
any Windows master/media server, the restore operation would fail. The
directory/file names could not be found.

(NetBackup Clients: Intel-NT Intel64 )
--------------------------------------------------------------------------------
Etrack Incident = ET302233

Description:
Robot inventory update was not taking into account the media type for
existing standalone media that have been moved into a robot. It was only
looking at the barcode rules. This was the cause of the error "media
type and volume group mismatch (101)". Robot inventory update now updates
the media residences to be robotic without changing the media type.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET302803

Description:
In the Windows Administration Console, Activity Monitor node, there was a
crash when viewing the job details dialog for some synthetic backup jobs.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET302340

Description:
Scheduler was not preferring the local storage unit when using storage
unit groups and in-line tape copy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET303121

Description:
The NetBackup bptm process could core dump if NDMP processes file history
with inodes with the 32nd bit set as code paths used signed integets for
this value, making the inode appear negative.

Additional Notes:
This problem was encountered while running a third party file system, the
SGI
open source XFS file system. This file system actually uses 64-bit inodes
however in this instance the NDMP file history was altered which caused the
32nd bit to be set.

(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET303187

Description:
When ejecting an ACS tape using the Windows Administration Console, the
eject hangs if the first CAP in the drop-down list is not selected.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Etrack Incident = ET299528

Description:
When backing up Lotus Notes databases, some databases were skipped. These
skipped databases were not reported as a error; the backup exited with an
status 0 instead of a status 1.

All NetBackup Windows Clients Linux2.4 RS6000_433 RS6000_51 Solaris
--------------------------------------------------------------------------------
Etrack Incident = ET194804

Description:
FlashBackup, using a FlashSnap alternate client snapshot method, fails on
Windows 2000 and Windows 2003.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET303563 ET302347

Description:
Main sched failed to recognize a media server that was initially off line,
and then brought on line after main sched went active.

If the media server was brought back while scheduler was not active or the
master server was bounced, then everything worked correctly.

This fix enables scheduler to ?pick up? the newly introduced media server
using the /bp/bin/admincmd/bpschedreq ?read_stunits command.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET304467

Description:
Staging/Duplication from a disk staging unit was not working when more
than 32765 files were in the staging area.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET259303

Description:
Enhancements have been added to bpdm and bpdbm to clean up fragments that
used to be left on the media server when bpdm failures occurred.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET258774

Description:
When performing backups that collect disaster recovery information, the
collection of the disaster recovery information may be failing. Upon
further investigation, it may be because drfile.exe is crashing on the
client system.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Etrack Incident = ET309222

Description:
Backups were taking too long between job complete and the 'end writing'.
Corrects were made to a recursive call in searching for a storage unit.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET299873

Description:
Bptm, bpdm, or bpdbm occasionally crashed during TIR incremental backups.
Bprd, bpbrm, or bpsched might have been affected as well.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET299874

Description:
Multiplexed backup jobs would occasionally hang. This would happen if the
bptm or bpdm parent process crashed, or if bptm could not successfully add
the TIR fragment for a TIR backup. It may have also happen due to a timing
problem in bpbrm when new jobs were started.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET313368

Description:
The fix to allow greater than 32K entries to be staged would only work if
the DSSU and destination storage unit are on the same media server.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Etrack Incident = ET314642

Description:
Client VSP custom settings were lost after upgrading from NetBackup 5.0 MP4.
Changes were made so the pack installer will only update VSP binaries.

All NetBackup Windows Clients
================================================================================



=========
NB_50_4_M
=========
Description:
Integrations bogus NB_50_4_M patch entry to use when checking in non
delivered files

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Resuming a checkpoint backup could result in the selection of a different
media server if a failure occurred on the initial backup attempt.

The failure scenario would look something like the following:
1) Backup reached a checkpoint.
2) Then failed (in this case a 13 "read failed" was received).
3) The Scheduler attempts to programmatically re-submit.
4) However the drives were re-set & downed.
5) The result was that the job exited with a 213 "no storage units
available" error.

The original storage unit information was "lost" so the job could
potentially resume on a different media server. If the job was resumed in
this way, the backed-up data would reside on two different media servers
and any subsequent restore would fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added Solaris10 support to the client drop-down list for this release.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After an NDMP import occurred, the file count would drop by a very large
number.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
There is a potential for missed files if all the following conditions
exist:
- Advanced client backup
- Incremental backup
- Multi-stream backup
- Backup stream is not stream 1

In addition, files modified after the snapshot is taken but before the
(non-stream 1) image is created may be missed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"Ghost" backup jobs were appearing in the activity monitor. For example, a
deleted backup job could (partially) re-appear in the activity monitor.
This would only happen to a deleted job that was one number lower than a
multi-copy backup.

And example of this scenario is:
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 "No activity in XXX minutes" message, similar to the following, may
appear in the detail.log file and show an unusally long period in which no
activity occurs:

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

This message is changed to "Waiting for completion of duplication" and
gives a more accurate report of the time.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The Vault Operator Menu (vltopmenu) allowed users to set an invalid
container return date or use an invalid format for a container return date.

Additional Notes:
These are the guidelines for changing the date:
* If no year is provided then the current year is considered.
* year (if provided) is interpreted as:
* two digit year yy 0-38 interpreted as 20yy
* two digit year yy 39-69 are illegal UNIX dates and will be converted to
0 (which is 1/1/70)
* two digit year yy 70-99 interpreted as 19yy
* four digit year yyyy interpreted as it is
* dates before Jan 1 1970 are coverted to Jan 1 1970
* dates after Jan 19 2038 are coverted to Jan 19 2038
* It is considered valid to provide a date prior to current date.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Vault jobs fail with "status 23" when run from a vault policy if another
"Program" directory or file resides on the same drive on which NetBackup
is installed.

Workaround:
Run the vault job by using a vltrun command from a command prompt, run the
profile from the shortcut menu, or rename the other "Program" directory or
file on the drive.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Vault jobs fail with "status 23" when run from a vault policy if another
"Program" directory or file resides on the same drive on which NetBackup
is installed.

Workaround:
Run the vault job by using a vltrun command from a command prompt, run the
profile from the shortcut menu, or rename the other "Program" directory or
file on the drive.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
After NetBackup 4.5 to 5.0 upgrade, media are suspended when profiles that
pre-date the upgrade are run without first opening the profile dialog and
then saving the profile (clicking OK).

Workaround:
For each profile for which you do not want media suspended, open the
profile dialog, click the Eject tab, then click OK (making sure that no
suspend options are selected).

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

Workaround:
Change the robotic control host value in the vault.xml file.

CAUTION: Editing the vault.xml file may cause problems and should be done
carefully.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
One CPU may reach 100% utilization for a bpbrm process that encounters a
certain Checkpoint/Restart for Backup state. If there are as many bpbrm
processes in this state as there are CPUs on the system, the system may
appear to be non-responsive because the bpbrm processes are using all of the
available CPU cycles. This problem was only be seen on Windows media
servers and no other platforms.


(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Restore job showed incomplete status (exit status 5) after a successful
client-initiated restore.

(NetBackup Clients: Intel-NT Intel64 )
--------------------------------------------------------------------------------
Description:
If an in-line copy backup is multiplexed, and one of the copies gets a
failure (but continues), then subsequent additions to this troubled
multiplexed group generates excessive failure messages.

This code change inhibits adding new backup jobs to multiplexed groups
that contain a failing copy.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Vault Administration interface (vltadm) does not allow user
specification of the robotic control host.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When making multiple copies, Vault does not duplicate an image if invalid
copies exist in the destination volume pool. (Vault should only skip
duplication if valid copies exist in the destination volume pool.)

Workaround:
Before performing duplication, run an image database cleanup session
(bpimage -cleanup) to ensure that invalid image copies are deleted from
the image database.

(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:
The cancel_all_exceeded_max_wait() function does not scale well in large
environments. This change modifies the way incomplete jobs are processed
when they have exceeded the maximum incomplete time.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A Vault policy that ejects media (using vlteject in the policy) creates an
extra Job in the Activity Monitor.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The problem existed when the following conditions were true:
- Snap backup (advanced client, Windows Open File Backup (WOFB)).
- Incremental backup.
- Multi-stream backup.
- Stream 1 is not due, but is force started to perform the snap shot
operation. Aggravated by ?frequency? mode (frequency is NOT multiple of 24-
hrs).

The problem can be minimized/eliminated by configuring for an all stream
backup:
- Use calendar based scheduling.
- Use ?interval? mode (frequency is multiple of 24-hrs).
- Avoid multi-streaming snap backups.

This problem resulted because of an oversight in cloning a due stream into
a non-due stream1. Remember, stream1 is not due, but is required to
perform the snap shot operation. The due stream information is copied in
mass to create the stream1 information, and then adjusted to make it
stream1 unique. The error occurs because the backup times (last backup,
last full backup, last incremental backup) were not updated to the correct
stream1 values. As a result of this, stream1 uses the stream2 image
creation times. Image creation times are used to compute the delta time
which determines the targeted incremental backup files.

Unfortunately stream2 also suffers the same failure. The stream2
incremental backup should be based upon the stream1 snap time, but stream1
was using the incorrect time for the snap. So, all the due streams suffered
this failure.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When Vault runs "bpimagelist" to obtain all images written in the time
window for image selection, it does not check whether or not the images
have expired. It puts expired images in the "preview.list" and tries to
duplicate them.

The consequences of this are as follows:

- Vault successfully duplicates the first image and updates the media
DB with the expiration date (the same as the backup retention level).

- NetBackup expires the image (while Vault continues to prepare
duplication for the next image), causing the tape to be de-assigned and
placed back into the scratch pool (if the system has this configured).

- Vault continues to duplicate the next image, but selects a new
media for it because the previous one was no longer available to
append to. NetBackup expires this new media and places it back into the
scratch pool.

- This behavior continues until Vault encounters a VALID image (in
the preview.list) that it can duplicate without expiring - and to which
the duplication of subsequent valid images can be appended.

- After processing the preview.list, Vault generates the eject.list,
which contains all the media used for duplication. Because some of that
media was de-assigned and moved to the scratch pool, the reports
(specifically the picking list for robot report) are incorrect.

Workaround:
Extend the retention level of the backups to be duplicated or ensure that
the Vault session does not run when images are due to be expired.

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

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:
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:
Under some circumstances, an image file might be expired on the Master
server and remain on the Media server. When media full is detected for a
DiskStaging storage unit, the media server attempts to remove the two
oldest images. If these images were no longer in the catalog on the Master
server, they could not be removed and the backup would fail.

The code was changed to remove the image files if the Master server no
longer had them in the catalog.

Workaround:
To avoid this issue, manually delete the image files that are causing the
problems along with their .ds file.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Changing the client name and policy type multiple times in the NetBackup
Windows client GUI will no longer cause a crash.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
You can no longer use the Windows NetBackup Client GUI to change the
client name to an invalid client name using the "Specify NetBackup Machines
and Policy Type..." dialog box.

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 Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
If you create a DSSU from the command line, but you do not create a
schedule for it, and then you access the storage unit from the NetBackup
Administration Console for Windows, the console would crash after you
clicked OK.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The Permission configuration screen lists a permission name "lternate
Client." This name should be "Alternate Client."

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When attempting to restore from a Hitachi Lightning NAS Blade 9900V image
that was backed up with the file list "set files=dir1 dir2 dir3" directive
specifying multiple files, the restore fails with status 5.



(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
src/vault/commands/containerops.cpp
ovgetmsg("VltCnt0480N", lc_messages, OVMAXMSG_LEN, localizedMsg,
LC_C_MESSAGES, OVMAXMSG_LEN, englishMsg,
"\t\tEnter ");

fprintf(stdout, localizedMsg);
fprintf(stdout, localizedVal);
fprintf(stdout, ": ");

You can see here that the message is created by a simple concatenation,
but
in Japanese the order is reversed which cannot be supported. Ideally it
should be done something like: "Enter %s: " so that the translator can
change the word order.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The DB2 and Oracle template names that contain double-byte characters now
display correctly in the Database Template Administration lists in the
Windows NetBackup Client GUI.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Using the NetBackup Windows Client GUI, you can now successfully run a DB2
database template when you are logged in with an 8-character username.

Workaround:
Use a username shorter or longer than 8 characters.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The NetBackup Client GUI's database "Template Summary" dialog now
correctly displays Oracle and DB2 template names that contain double-byte
characters.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The following log entry in the bptm log was confusing (in this patch, the
word DEBUG has been removed):

09:37:46.035 [16536] <4> ndmp_internal_open_and_auth: NDMP server DEBUG
suggests protocol version 3


(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When restoring or backing up files using a proxy, NbWin.exe (Backup,
Archive, and Restore) may fail with an application error.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups fail with a status 69 if the file list contained
an entry that did not exist. Have Exchange Mailbox backups exit status 1
if a file list entry does not exist.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
A change in NetBackup 5.0 MP3 caused the following three fields in the
media going off-site reports to display 0 instead of the correct values:

Number of images for this session
Kbytes for this session
Number of images not for this session

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Disk Staging would not correctly relocate backup images from clients when
a client name contained an "_" character.

Workaround:
To avoid this issue, remove the "_" from the client computer names.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup Administration Console (on re-launch) and admincmd/bpschedule
display incorrect or no values for specific_include_dates specified in
calendar-based schedule for DSSU relocation schedule. However, this does
not affect the configured schedule getting triggered at correct time. This
behavior is observed only on HP-UX platform.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In one instance, some catalog files were corrupted when the system ran out
of disk space. This caused bpdbm to crash whenever it tried to load the
corrupted catalog files. The command "bpdbm -consistency 2" also crashed
every time these corrupted files were checked.

The cause of this problem was the buffer overrun in libcatalog when loading
corrupted files: the pointers and string lengths are wrong after mapping
the file into memory. To address this problem, code was added to safe guard
buffer overrun to fix the crash of bpdbm. In addition, code was added in
image.c to move corrupted catalog files out of /db/images (into /db.corrupt
directory) when running "bpdbm -consistency 2".

This new code resulted in the following new feature:

"bpdbm -consistency" will move corrupted catalog files out of the catalog
repository "/netbackup/db/images" and into "/netbackup/db.corrupt"
directory.

After running the above command, users will need to do the following:
1. Record all file paths in /db.corrupt;
2. Re-import the files in step 1;
3. Delete files in /db.corrupt.

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

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

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If the following conditions are met, the activity monitor will report
a "status 50" failure for the child duplication jobs.

- A customer is configured with a disk-staging storage unit.
- The DSSU's "Disk Staging Schedule" is configured to produce multiple
copies.
- A DSSU duplication takes longer than 20 minutes.

NOTE: The single parent duplication job, as well as the "__DSSU_POLICY_"
backup job, remains active in the activity monitor. In addition, ALL
processes remain active.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Following messages did not match:

NecErr0363N "recveived an error from bptm request to suspend media"
TrbErr0631N "received an error from bptm request to suspend media"

NecErr0364N "recveived an error from bptm request to un-suspend media"
TrbErr0632N "received an error from bptm request to un-suspend media"

NecErr0378N "unable to get address of the local listen socket"
TrbErr0646N "unable to get the address of the local listen socket"

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If NetBackup is configured to duplicate an image and also configured to
change the retention level of the new copy to a retention level that is
configured as "expires immediately", then the original image also appears
to be expired at the end of the duplication. Any backup taken after that,
returns the original image.

Workaround:
Any subsequent backup would expunge expired copy from the image file, and
bring back the original image (to image list and for restore operation).


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Oracle recovery template would cause a core dump if it was used under
the Template Administration window.

Workaround:
Place the Oracle/DB2 recovery templates in a directory other than where
backup templates reside.

Template administration looks at backup templates in the following
directory :

/usr/openv/netbackup/db/dbtemplates/oracle (Oracle - Unix)
/usr/openv/netbackup/db/dbtemplates/db2 (DB2 - Unix)

VERITAS\NetBackup\db\dbtemplates\oracle (Oracle - Windows)
VERITAS\NetBackup\db\dbtemplates\db2 (DB2 - Windows)

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A problem would occur when SQL Server images were stored using the fully
qualified domain name (such as min.veritas.com). The fully qualified domain
name was used, for example, if the client name was an FQDN.

In this scenario, the SQL Server agent successfully browsed for the images
but created an incorrect batch file. In particular, the image name was
specified in correctly. In addition, if the image is stored as
tiger.min.com the image name would be created as:

MSSQL7\tiger.veritas.com\db\ePO_ENT001\~\0\001of001\20040620161136\\C

However, the agent would generate the batch file using:

NBIMAGE "entsql001/MSSQL7/tiger/db/ePO_ENT001/~/0/001of001/20040620161136//C
"

This caused the restore to fail. Errors such as the following would appear
in the dbclient log,

14:46:19.471 [2940.2996] <32> DBthreads::dbclient: ERR - <VxBSAQueryObject>
failed with error <17>. The text follows:
14:46:19.471 [2940.2996] <1> DBthreads::dbclient: CONTINUATION: - No
object matched the specified predicate.
14:46:18.158 [2940.2996] <8> VxBSAQueryObject: WRN - Query unsuccessful for
client ENTSQL001.

Workaround:
To avoid this issue, manually update the batch file using the correct image
name.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
If BATCHSIZE is used in the batch file and one of the referenced databases
does not exist, then the SQL agent hangs. Below is sample batch file.

BATCHSIZE 3
OPERATION BACKUP
DATABASE "master"
SQLHOST "CASS"
NBSERVER "CASS"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
ENDOPER TRUE

OPERATION BACKUP
DATABASE "johnny"
SQLHOST "CASS"
NBSERVER "CASS"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
ENDOPER TRUE

OPERATION BACKUP
DATABASE "msdb"
SQLHOST "CASS"
NBSERVER "CASS"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
ENDOPER TRUE

'Johnny' was not a database that existed on the system. The backup
completed successfully for the 2 databases that existed but the
dbbackex.exe process hung after encountering this message:

11:07:10.900 [2188.1000] <4> StartupProcess: INF - Starting: <"D:\Program
Files\VERITAS\NetBackup\bin\progress" MSSQL>
11:09:47.233 [2124.3644] <32> CDBbackrec::InitDeviceSet_Part2(): ERR - Error
in
GetConfiguration: 0x80770003. The text follows:
11:09:47.233 [2124.3644] <1> CDBbackrec::InitDeviceSet_Part2():
CONTINUATION: - The api was waiting and the timeout interval had elapsed.
11:09:47.233 [2124.3644] <4> KillAllThreads: INF - entering KillAllThreads
<2>
11:09:47.233 [2124.3920] <4> KillAllThreads: INF - entering KillAllThreads
<2>
11:09:47.233 [2124.3732] <4> KillAllThreads: INF - entering KillAllThreads
<2>
11:09:48.233 [2124.3644] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC
message.
ODBC return code <-1>, SQL State <08004>, Message Text <[Microsoft][ODBC SQL
Server Driver][SQL Server]Could not locate entry in sysdatabases for
database
'johnny'. No entry found with that name. Make sure that the name is entered
correctly.>
11:09:48.233 [2124.3644] <16> CODBCaccess::LogODBCerr: DBMS MSG -
<[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating
abnormally.>
11:09:48.233 [2124.3644] <32> Dbbackrec::PerformNBOperation: ERR - Error
found
executing <backup database "johnny" to VIRTUAL_DEVICE='VNBU0-2124-3644' with
blocksize = 65536, maxtransfersize = 65536, buffercount = 1>

The backup ends by never completing and the processes are hung on the
client.

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

The transaction appears to be complete on the client and the client
disconnects the socket connections to the media server. The media server
would not expect this and would exit with status 24.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The NetBackup SQL agent in the NetBackup 5.0 MP1 with backup scripts and
using $ALL and BATCHSIZE would place the BATCHSIZE directive into all
OPERATION requests but are only allowed in the first set.

If the script (.bch file) was similar to the following:

BATCHSIZE 2
OPERATION BACKUP
DATABASE $ALL
SQLHOST ''SQLVIRTUAL''
SQLINSTANCE ''INST1''
NBSERVER ''DB-AD02''
MAXTRANSFERSIZE 0
BLOCKSIZE 7
BROWSECLIENT ''SQLVIRTUAL''
ENDOPER TRUE

The failures looked like the following:

dbclient log:
23:17:42.677 [2172.2212] <16> ReadBatch: USER - Error. BATCHSIZE cannot be
specified after the first operation.
23:17:42.677 [2172.2212] <16> ReadBatch: USER - BATCHSIZE and GROUPSIZE
cannot both be specified in an operation.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
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 vendor.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup was not properly using the firmware revision to retrieve the
correct device mapping in the device mappings file. This has never been a
problem in the field because Symantec has never had to use the firmware
revision in the device mappings file - this is being done for new device
support.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Untranslated error messages were discovered and corrected on the Oracle
agent user interface.

All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 Solaris
--------------------------------------------------------------------------------
Description:
When doing a consolidated eject for a vault job that contains multiple
media types, all media are ejected but only the media from one media type
are changed to the off-site volume group. The media from the other media
types remain in the robotic volume group.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
In the localized verison of Oracle, the text, "WHOLE DATABASE", was
hardcoded. This has been fixed.


All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
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:
For duplication, Vault picks the first image copy on disk as the source
image for the copy operation. This can result in Vault ignoring the
primary copy on disk, which should be used as the source.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When using the Select Template dialog in NetBackup 5.0GA Administration
Console for Windows, the database template file name with Japanese receives
unreadable characters.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The NetBackup for SQL restore move script is sometimes built without
specifying the .ldf (log) file. This only happens for multi-striped
backups. But it does not always occur.

Workaround:
To avoid this issue, manually edit the move script to include the MOVE log
(.ldf) section and the restore will be successful.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Previously, cluster_config -a would go into an infinite loop when
configuring add-on products for monitoring when anything but a lowercase
"y" was entered at the following prompt:

You have chosen to monitor <addon>. Is this list correct? [y,n] (Y)

This issue has been resolved and the defaults, "Y" and "y" are all valid
responses.

Workaround:
To avoid this issue, you would have entered a lowercase "y" instead of an
uppercase "Y", or you could have taken the default.

(All UNIX NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup for Lotus Notes will successfully backup Domino transaction log
extents, but will NOT truncate them.

Workaround:
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:
While trying to reduce the size of a database, the command "bpimage -
cleanout -client dill-bk" was used. Using the command in this way caused
bpimage to core dump.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This patch contains the following fixes and additions:
- Synchronised NetBackup 5.0 MP4 device mappings with 5.1_1.
- Fixed serialization differences between CSM 3.01 and 4.01 firmware.
- Added IBM DDS4 autoloader.
- Added Sony SDX-900V (AIT-4).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
You can now take backups using NetBackup when lun loaders are used with
certain Adaptec HBAs.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The condition where folders are not included in the backup is only noticed
during restore operations when attempting to select the folders/files for
restore. The folder, sub-folder, and/or files are missing from the backup
selection. This is a randomly occurring condition that does not occur in
every NetBackup environment. The problem is related to a suspected memory
corruption and may occur without notice or warning.

It is very important to note that the error may never occur because not all
Windows systems are susceptible to the memory corruption. In addition, not
every system will skip folders and files during the backup.

This issue applies to:
- MS-Windows-NT and FlashBackup-Windows policies for both full and
incremental schedules.
- Any Windows client using VSP or VSS.
- Windows Open File Backup (WOFB) and Advanced Client backup.

Although Symantec has been unable to duplicate this issue, the following
conditions have reported :

a. The policy must contain a file list stating the drives in alphabetical
drive order.

b. The policy must not use Multi-Streaming.

c. The Client must be configured for individual snapshots.

This issue is not noticed when multi-streaming, if the file list directive
is ALL_LOCAL_DRIVES, or when using a global snapshot.

If all of the above conditions are met, the backup will include only root
or top level directories, no sub folders or files. In severe cases, only
the drive letter is visible in restore selections.

Workaround:
Multiple work-arounds are available that reduce but do not guarantee
complete success if the Client is susceptible to the memory corruption.
The following list describes some of the available options.

1. Enable multiple data streams.
2. Change the client to use a global snapshot.
3. If using 5.0GA MP1, uninstall MP1 and execute the backup schedule with
NetBackup 5.0 GA.
4. Disable WOFB and Advanced Client backup methods.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When running Windows Open File Backup enabled backups using VSS on
Windows 2003 clients, performance of the backup is considerably slower
compared to when running a Windows Open File Backup enabled backup using
VSP or with Windows Open File Backup disabled. Only backup performance is
affected and no data loss occurs as a result of using VSS as the Windows
Open File Backup snapshot provider.

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

All NetBackup Unix Clients
--------------------------------------------------------------------------------
Description:
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 inconsisties.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpinst command pushes the incorrect Encryption software to 64-bit
Windows clients.

Workaround:
In the win_IA64 directory on the server, these files exist:

libvdes40.dll
libvdes56.dll
bpkeyfile.exe

Copy them into the VERITAS\NetBackup\Bin\ directory on the 64-bit Windows
client.

Additional Notes:
After applying the patch, if you haven't previously applied the workaround:

Remove these files from the VERITAS\NetBackup\Bin\ directory on the 64-bit Windows client:

libvdes40.dll
libvdes56.dll
bpkeyfile.exe

Rerun the bpinst -CRYPT command from your server to push the correct files to the client.

(NetBackup Clients: Intel64 )
--------------------------------------------------------------------------------
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:
Exchange Mailbox backups would fail with a Dr. Watson under the following
conditions:

The problem occurred when the mailbox msg (including the GUID), plus a
mangled name length, plus 12 (for some additional characters) would equal
exactly 512. This needs to take place at the end of a data block, which by
the default is 64K. The result is overrunning the end of the data block,
and this exception is the result.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
In the NetBackup client GUI, the tree showed nothing under the 'Microsoft
Mailboxes' and 'Microsoft Exchange Public Folders' on the Select Backup
Files panel.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
With an AIX master server, FlashBackup on Windows restores were failing
when a zero length file was encountered.

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

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

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Report generation takes an extremely long time after upgrading from
NetBackup 4.5 to version 5.0, 5.0 MP1, 5.0 MP2, or 5.0 MP3.


(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Vault allocates a fixed amount of memory for report generation, which may
be more than enough memory. This fix allocates memory dynamically for
the reports so only the memory required is reserved.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------

Description:
The "media that have not been ejected" string on the Non-vaulted Images
Report is not translated when NetBackup is localized.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
The performance of single-file restores for FlashBackup on Windows is below
expectations. Increasing the holding buffer size decreases the number of
call to windows function which in turn decreases the overall restore time.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
For restores of encrypted files with FlashBackup on Windows, the data for
these files has to be restored sequentially. The buffering of this data
was not functioning correctly.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Catalogs were being archived and not removed. The problem is the output
from bpcatarc is a Windows file specification, and was not parsed correctly.

Workaround:
Workaround is:

pipe file list from bpcatlist to bpcatarc and bpcatrm seperatly.

instead of
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpcatlist | bpcatar |
bpcatrm

C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpcatlist | bpcatarc
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpcatlist | bpcatrm

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Added support for Lotus Notes databases and transaction logs residing in
Windows UNC paths. The pathname must have a minimum of three components, for
example, \\hostname\share\lotus. A Lotus backup job with a pathname of
only one or two components, (such as, \\hostname or \\hostname\share)
generates an error.

Additional Notes:
Support for UNC paths in the file list for Lotus policies has been added.
This support includes both Lotus Domino databases and transaction log
extents. User-directed backup of Lotus databases that reside on a shared
drive referenced by UNC paths is not currently supported.

Please refer to the "NetBackup System Administrator's Guide for Windows,
Volume I" for more information on configuring a file list for NetBackup
policies using UNC paths.

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

bpconfig -cleanup_int 24

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Eliminated errors appearing in the bpbkar log when performing a backup
using a Windows UNC pathname with a Lotus Notes policy. Error
messages reporting NSFDbOpen() failures for the first two pathname
components (\\hostname and \\hostname\share)are no longer reported.

A Lotus backup job with a pathname of only one or two components, (for
example, \\hostname or \\hostname\share) causes the backup to fail and an
error status 71 is reported.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
A synthetic backup time out would occur because of the time it would take
to read the large extents.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A problem was discovered when the following conditions were met:
1. Running SAP archiving in continuous mode, brarchive -f.
2. The policy_log and sched_log parameters are enabled in NetBackup for SAP
agent configuration file. (init<SID>.utl)

The policy_log and sched_log parameters enable NetBackup for SAP to perform
an additional backup of the archive logs. Having two backups of the archive
logs (usually to different media) is an additional measure to secure the
integrity of archive logs.

In situations where the brarchive command is run in continuous mode,
NetBackup for SAP performs two backups only for the initial set of archive
logs. All following sets of archive logs are backed up only once.

This patch fixes this problem.

(NetBackup Clients: ALPHA HP Intel-NT Intel64 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description:
When a user imports and/or restores a NetBackup 3.4 backup image in
NetBackup 5.0/5.1, files greater than 1GB in size fail to restore and
produce, "disk full at byte xxxxx", errors in the restore log. Image verify
also fails with a gigabytes size mismatch error for those files. In
addition, the Backup, Archive, and Restore GUI shows a discrepancy in
reporting the size of those files.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Windows NetBackup Administration Console Activity Monitor in some cases
will show unrecognizable characters for some strings in the Jobs list.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
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:
In attempting to filter out file system names that are not appropriate for
VSM management (for example, /var), VSM-Java filtered out some file system
names that it should not have filtered (such as, /variety).

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The file list for stream 1 is listed twice in the job details when stream 1
is force-started to take a snapshot. This error is only on multi-stream
snapshot backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Only fails on a UNIX master. If a user archive fails to remove some files
(and generates a status 4), then the .f file is removed, and the files, up
to the failed file, are removed from the client.

(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:
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:
Retry the duplication using non-multiplexed duplication. It is also
possible that the duplication will succeed by trying multiplexed
duplication.

(All NetBackup Servers)
--------------------------------------------------------------------------------
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 caused the backup to
abort.

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

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

(NetBackup Clients: HP Intel-NT Linux2.4 RS6000_433 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Description:
The backup job start time in the activity monitor was the same value for
each attempt. The start time value should be different on each attempt.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler would send a message on the wrong queue when it detected an
error on a client snapshot. This may result in a scheduler crash, if the
error happened frequently, or if the scheduler stayed running for a
prolonged period of time.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An intermittent problem with the installer no longer occurs when trying to
install to remote clients. The following two files were not being copied
to %TEMP%\X86, and caused the following error to appear.

Files: - VERITAS Maintenance Pack.msi
- Data1.cab

Error message: "The system cannot find the file specified" on Install GUI.

Workaround:
To avoid this issue, do the following:

1) Start the installer.

2) Select "Select from available computer on the network".

3) Click Next.

2) Copy VERITAS Maintenance Pack.msi Data1.cab to the %TEMP%\X86 directory.
(easiest way to find what %TEMP% is, is to open a cmd shell and run echo
%TEMP%, usually its something like C:\Documents and
Settings\<UserName>\Local Settings\Temp\X86).

3) Proceed with installation.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The image resume time limit was not always being updated on Checkpoint
backup jobs. Multiple attempts to resume a job might result in a backup
that is restarted instead of resumed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The error "license use has been exceeded", status code 159, may have been
erroneously generated when using a SAN media server license for a media
server that is part of a cluster.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault does not handle "Disk Staging Storage Unit" source images like "Disk
Storage Unit" images for duplication.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
There are two issues that may have caused backups to fail:

1. bpsched was not updating the RESUME_EXPIRATION time on failed backups.
2. bpdbm did not update the REQUEST_PID on subsequent Q_IMAGE_NEW requests.

Workaround:
To avoid this issue, make sure any job that has been resumed is finished
before the cleaning is done.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Iron Mountain electronic report, an extra space prevents Iron
Mountain from parsing the report successfully.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
An initialization failure against nbwin.exe was generated when a
non-administration account initiated a restore. A pop-up was generated and
stated that nbwin.exe failed to initialize 0xc0000022. A change to the
permissions was made to msvcr71.dll so that the user "Users" had Read and
Execute permissions.

Workaround:
To avoid this issue, manually change the security permissions on
msvcr71.dll to allow Read and Execute permissions for "Users" user.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using a pre-NetBackup 5.0 MP4 client to backup open/active files using
VSP, VSP snapshot creation will fail on 64-bit dynamic disks. All files
that are open/active on these 64-bit dynamic disks will not be accesible to
the backup even with VSP enabled, thus causing the backup to end partially
successful.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Added support for RedHat 3.0 on the Zseries platform. This required a new
client type which is called IBMzSeriesLinux2.4.21. The number is based on
the operating system (OS) kernel.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An extra invocation of a function was resetting the delay time on tape UN
mounts for user backups. Removal of the extra invocation should produce
more optimal UN mounting of tapes when performing user backups.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Scheduler code was too inflexible and did not allow for easy addition of
new Windows Open File Backup (WOFB) snapshot clients. This change
corrected the scheduler and eased the addition of future Microsoft clients.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Bperror -S <status-code> -r would return only the first four characters on a
Windows platform.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An attempt to use $ALL in a Batch file with more than 32 databases on a
system would result in the following error:

ReadBatch: USER - Error in the value supplied for GROUPSIZE.. You must
provide a size between 1 and 32

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Because of a race condition, ACSLS drives may get downed during mount
processing.

Additional Notes:
The signature of this race condition is that the event viewer (or syslog)
will note errors in semaphore operations from ACSD, and then the drive will
be DOWNed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Vault Duplication performance degrades significantly for large images
(spanning media) in NetBackup setups that have TIR enabled.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
An incorrect STATUS_ROBOT_BUSY message causes the eject process to stay
active and idle, preventing other Vault operations from running.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When backing up files with an incremental TIR with move detection backup
using Windows Open File Backup to backup open or active files, users may
see the following erroneous error logs in the bpbkar32 debug logs when
backing up empty directories:

:26:45.713 PM: [3960.3892] <8> dos_backup::V_FindAllSorted: WRN - unable to
find first file: 'H:\ff\'

These logs should not appear and does not affect the back up in terms of
files backed up correctly or in terms of data integrity.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
For Disk Staging, NetBackup could not clean all images when the total number
of images were more than 16384.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Re-naming a schedule, and then attempting an immediate backup using the
newly named schedule caused a core dump in the scheduler.

Workaround:
To avoid this issue, do not add, remove, or modify policy or schedule
information and then attempt an immediate backup while scheduler is running.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Tapes would not unmount in a reasonable time frame.

(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:
Corrected a potential problem where Windows Open File Backup (WOFB),
multi-stream, non-checkpoint, non-control stream gets a 134 status, and
stays queued (never goes active).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Maintenance Pack 3 for the NetBackup 5.0 release introduced a performance
issue with NDMP DAR restores for catalogs with a large number of files.
This fix corrects the performance problem.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected a case where incremental backups were backing up complete data
sets (full backup). This happened only for multi-stream, Windows Open File
Backup (WOFB), or advanced client where a previous non-control stream
backup failed.



=========
NB_50_3_M
=========
Description:
Corrected an end-case problem in the MPX read processing
(restores/duplications) that would try to unmount a media that is already
in use by another process.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Media position error while attempting to restore from a copy of a backup
created by Inline Tape Copy. The bptm log will show an entry 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:
The restore may be done from the other copy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A CheckPoint Restart backup may hang after resuming an incomplete backup.
This would happen if the backup error occurred after backing up more than
four gigabytes of data.

The bptm log will show many entries similar to the following:

09:40:43.700 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508
09:40:43.730 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508
09:40:43.760 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508

...where the calculated blocks value and the blocks in cpr value do not
change.

Workaround:
Disable the CheckPoint Restart feature in the policy, or create a maximum
fragment size in the storage unit that is less than four gigabytes.

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

Example:
ACS_QUERY_TIMEOUT = 30

This sets the timeout to 30 minutes.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The SSO wizard crashes when attempting to add a host to a shared drive when
the wizard is launched from the Devices snap-in in the Windows NetBackup
Administration Console.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
VOPIE Enhanced Authentication may not work when host names are greater than
32 characters. You may receive 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:
Disk Staging would not correctly relocate backup images from clients when
a client name contained an "_" character.

Workaround:
To avoid this issue, remove the "_" from the client computer names.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The new keep-alive code is more efficient and prevents the server from
receiving a network timeout when the backup job is being resumed.

(NetBackup Clients: Intel-NT Intel64 )
--------------------------------------------------------------------------------
Description:
The following two issues with checkpoint restart for backups have been
resolved.

1. The import of a successful checkpoint restart backup that is incomplete
or suspended prior to the first checkpoint may fail. Then, if it is
resumed, it will complete successfully. The phase 1 import log would show
one or more of the following entries:

13:45:45 INF - Found existing image information for client test, policy
itest, and schedule Full, done on 04/13/2004 13:37:56.
13:45:47 WRN - Cannot import client test, policy itest, and schedule Full,
copy 1 fragment 1 already exists. Skipping this image.

The phase 1 import will then succeed. However, the phase 2 import will
fail with the following error:

13:56:19 INF - Import of policy test, schedule Full (test_1081881476)
failed, tar had an unexpected error.


2. For a checkpoint restart backup, in the rare case where bptm detects
that a position check problem occurred following a checkpoint due to a
misconfigured drive or a rewind from an external source, and the backup is
later resumed, the information on the tape prior to the checkpoint may be
invalid.

The bptm log would indicate the position check problem with one of the
following logs following a checkpoint:

08:39:57.969 [4393] <16> write_data: FREEZING media id 00011, too many
data
blocks written, check tape/driver block size configuration

OR

log.041204:14:39:12.373 [6416] <16> write_data: FREEZING media id 00005,
External event caused rewind during write, all data on media is lost

The problem would occur if the same backup were resumed and completed with
a successful status.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A warning is required when a library is delete if there is media assigned
to it, or if the last drive of that particular drive density is deleted
from a robot.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Exchange restores from multiple images fail 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:
To avoid this issue, create a file named,
/usr/openv/netbackup/NON_MPX_RESTORE to force sequential restores from
multiple images.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Policy Attributes dialog, checking the "Checkpoint restart" box
clears the "Backup Network Drives", "Cross mount points" and
"Collect TIR information" boxes.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
A possible buffer over-run corrupting eject information in memory, was
causing ACS ejects to fail because the CAP was reported as not existing,
when it actually did exist.

(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:
A NetBackup restore that has a path specified to be excluded from restore,
but that path does not even exist in the backup image, was completing with
a partial success status of 1. The resolution of this DDTS would complete
such a backup with a complete success status of 0.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing backups using true image with move detection, the backups
may crash at the very start of the backup.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When performing System State backups on Windows XP and/or Windows 2003
Server, the backup may appear to hang when it backs up the Registry or it
may generate errors while backing up the Registry.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When performing a user directed backup and the user selects both nodes
under Registry:\, HKEY_LOCAL_MACHINE and HKEY_USERS, nothing will get
backed up.

Workaround:
In order to work around this issue, the user will need to submit
individual backup requests. One for Registry:\HKEY_LOCAL_MACHINE and one
for Registry:\HKEY_USERS

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When using NetBackup Access Control hostnames, a specific size may cause an
erroneous Authorization denial.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Some multiplex groups are lost on Windows 2000 systems only. This results
in the inability to cancel/suspend jobs or add new jobs to the multiplexed
group. In addition, on all platforms, the overhead on starting an
immediate, user, or archive backup is excessive.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A potential buffer over run in scheduler has been resolved.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A storage unit group that contains only disk staging storage units cannot
be selected in a policy.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
For FlashBackup on Windows, restores of large files were failing. This
happened if the extents composing the files described more than 2GB of
data. In a situation like this, an extent larger that 2GB was broken down
into smaller units but not all of the fields associated with that extent
was propagated correctly.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpbkar32.exe no longer crashes during the restart of an incremental backup.

(NetBackup Clients: Intel-NT Intel64 )
--------------------------------------------------------------------------------
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.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Queries for images having XBSA extended data fail in bprd when connecting
to dbm with the socket being overwritten.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The restore of a backup created by NetBackup 4.5, or earlier NetBackup
releases may fail on NetBackup 5.0. This defect applies to backups of a
raw partition and backups of a file whose size is 1GB or greater.

The failed restore may return an exit status of 0, and it may otherwise
appear to have succeeded. However, the restored file will not contain all
the data of the original file. Alternatively, the restore may exit with a
status of 3 or 5. The tar debug log may contain a message of "invalid tar
header" for the failing file.

In addition, attempts to verify the backup image may fail on NetBackup 5.0.

Workaround:
TO avoid this issue, do the following:
1. Expire the backup image.
2. Import the backup image.
3. Run the restore.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Catalog archiving does not properly handle images written by
NetBackup 3.1.1. Using the archive tools with images that do not have a
CATARC id can result in a catalog file being backed up and removed with out
the CATARC id being written.

Workaround:
Adding the line "CATARC 0" the the catalog image file before including it
in a bpcatarc call will avoid this problem.

Additional Notes:
If the images have already been archived without the CATARC value being
written, you can get the files back by restoring the files from the backup
that resulted from the initial bpcatarc call.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpexpdate binary would not notify the user that they were unable to use
bpexpdate due to access control limiting their access. Although the binary
would return the appropriate error level (such as, 117, 116, or 118), the
corresponding message contained unreadable characters.

Workaround:
check the error level returned by bpexpdate manually. (e.g. echo
%ERRORLEVEL% or echo $? )

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NBU_Operators did not have the backup permission on Policies, yet they were
able to perform manual backups. The NBU_Operator group should be able to do
manual backups, but it should always require the Backup permission on
Policies.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A memory fault occurred when running a user-initiated Oracle template
backup in a Japanese localized environment.

This problem is limited to Japanese localized environments.
It can happen when running a User Directed Oracle template backup. User
Directed Oracle backup is initiated in few different ways:
1.Using Oracle Wizard ? Go through wizard options and run template.
2.Using Administrator Templates option in the Actions Menu of the NetBackup
Client GUI ? Select a template and run it.
3.Running Oracle template from the command line using bpdbsbora

The name of the executable file that creates the memory fault is bpdbsbora.
Logs for this executable are located at,
/usr/openv/netbackup/logs/bpdbsbora/log.<date>

In case this problem occurs, the last couple of lines in bpdbsbora log
should look similar to:

17:44:50.593 [16702] <4> VxBSAGetPolicyInfo: INF - request string: <rue
am_ora NONE>
17:44:50.850 [16702] <4> VxBSAGetPolicyInfo: INF - Policy Info:STD

(NetBackup Clients: ALPHA HP Intel-NT Linux2.4 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Description:
An issue existed in the command bpcatlist | bpcatarc | bpcatrm.

After successful catalog backup, none of the catalogs are deleted. If you
do a bpcatlist, you will notice that there is a "0" in the Catarcid value.
In the policy_time_FULL image file, CATARC is 0. It appears that this is
not being updated. You are still able to browse files for restores.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When running the Intelligent Disaster Recovery PrepWizard, the following
errors may appear:
1) When attempting to create a bootable CD : "Language was not determined
from \\<machine_name>"
2) When attempting to create bootable floppies : "Insufficient rights on .
Administrative Rights are required. Before choosing the remote system in
the IDR Preparation Wizard, ensure you are connected to that system as a
user with administrative rights"

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The number of in-use drives is not computed correctly when a disk staging
storage unit is flushed (duplicated) to tape. This results in additional
backup jobs being blocked until the duplication is completed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Boolean file keys in Device Mappings are not properly parsed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
There was a possibility that a core dump could occur in the scheduler if
the storage unit host name cannot be mapped to a valid media server name.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Attempting to set the database login parameters using SQL authentication
fails with this dialog:

"Application connection failed for CAER\. Please select a different SQL
Server host and instance."

This works when using Windows authentication.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
A performance degradation as high as 200% can occur with Exchange Mailbox
backups when upgraded from an MP release to an FP release while running
the same NetBackup configuration.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
During an Exchange backup of the Information Store, the Bandwidth
Limitation feature of NetBackup is not supported. Backups of Exchange
proceed at the fastest pace possible for the network.


(All NetBackup Servers)
--------------------------------------------------------------------------------
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:
The command "backint -p <utl file> -f inquire" can fail.

When called without an input file list, the SAP Agent will fail.
If a user runs "backint -p <utl file> -f inquire", the reported error is:
"ERROR: couldn't open file: <file name>"

To avoid this issue, create an input file with file list and pass it with
a -i option. The following example can be used:
"backint -p <utl file> -f inquire -i <input file list path>

(NetBackup Clients: ALPHA HP Intel-NT Intel64 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description:
The following message was changed from:

"frozen image processing failed, status ...."

to

"snapshot processing failed, status ....".

All NetBackup Windows Clients HP Solaris
--------------------------------------------------------------------------------
Description:
When restoring directories (folders) that refer to SYSVOL on a Windows
2000 / Windows Server 2003, the following error may appear:

WRN - can't create directory: <filepath being restored> (WIN32 3: The
system cannot find the path specified. )

Workaround:
The workaround for this issue is to restore the files that belong to System
State:\ before restoring the files that belong to the rest of the system.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When performing an Exchange DB backup (IS, KMS or SRS), bpbkar gets TCP
socket send failures after the client recieves the server status at the end
of a backup. This issue does not cause critical errors as the client
completes post backup activities (such as truncating trans logs).

The end of bpbkar log looks like this:

9:41:22.091 AM: [616.644] <2> tar_base::V_vTarMsgW: INF - Exchange
Transaction Logs truncated
9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: send socket
(308) (TCP 10058: Can't send after socket shutdown)
9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: attempted to
send 6 bytes
9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: send socket
(308) (TCP 10058: Can't send after socket shutdown)
9:41:22.101 AM: [616.644] <16> dtcp_write: TCP - failure: attempted to
send 36 bytes

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When running multiple, multiplexed and multi-streamed backups using
NetBackup 5.0 MP1 or NetBackup 5.0 MP2, some of the backup jobs could end
with status 69: invalid filelist specification. The file list will contain
a NEW_STREAM directive which is causing the status 69 errors.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Advanced Client Alternate Client Backups with snapshots will not exclude
files correctly on the secondary client when backups are run. Files in the
exclude list on the primary client do not get applied on the secondary
client, thus the backup does not exclude files correctly for an alternate
client backup using snapshots.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When running simultaneous groups of multi-streamed backups on the same
Windows client, some backups could end with a backup status 71: "none of
the files in the file list exist" unnecessarily.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Assigned a new message ID.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpdbm's host list is not consistent with that of bprd. The current
impact of this issue is that "FORCE_RESTORE_MEDIA_SERVER does not work for
TIR restores."

It appears that FORCE_RESTORE_MEDIA_SERVER does not replace the server
entry for TIR fragment. Thus, when TIR information needs to be extracted
from tape, bpdbm tries to initiate "bptm -restoretir" on the original
server.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Performing an Exchange Information Store restore causes misleading "bogus"
bpbrm errors in the Activity Monitor. The restore is successful and the
Activity Monitor description looks like the following:

3/2/2004 9:07:38 AM - Error bpbrm(pid=268) from client backrest: TAR -
Restoring Exchange 2000 ESE object C:\Program
Files\Exchsrvr\mdbdata\priv1.edb

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Unable to turn on debug logging in the BEDS modules using the GUI.

Workaround:
To avoid this issue, use the Windows Registry editor, and set:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Debug_Le
vel to 2.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Exchange Mailbox backups may hang for Exchange 2003 running on a Windows
2003 Cluster. This problem only seems to happen on Exchange 2003 after
mailboxes are migrated from Exchange 5.5.

The last log entry in Debug logs would be:
"INF - MAPISession::ImpersonateUser(): Logging on to server
<Exchange_Virtual_Name>
as user <MailBox_Alias>! MessageStoreDN=/O=<Org>/OU=first administrative
group/
CN=Configuration/CN=Servers/CN=<Exchange_Virtual_Name>/CN=Microsoft Private
MDB
!MailBoxDN=/O=<Org>/OU=first administrative
group/CN=recipients/CN=<MailBox_Alias>"

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
bpbkar32 generates an 'Exception number: c0000005 (access violation)'
(Dr. Watson) when doing a cumulative backup of an Exchange 2000 Storage
Group and the first transaction log to be backed up is missing. The backup
ends with status 13.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Added support for the following drives:
Certance LTO2 drive added, HP SDLT600, Sony SDX-700V, HP C7438A DAT 72,

Added support for the following libraries:
Qualstar RLS Series Libraries, Quantum DX100, HP MSL6000, HP MSL5000,
QUANTUM ValueLoader

In addition, several changes have been added to address serialization,
library inventory, and extend/retract issues. The following list
identifies the library and the issue that has been corrected.

ADIC Scalar i2000 - extend retract issue
Compaq MSL5000 - barcode inventory issue.
OVERLAND Libraries - barcode inventory issue.
Fujitsu LT160 Eternus - empty-map and serialization issue

Added Support for the following drives:
Certance LTO2 drive added, HP SDLT600, Sony SDX-700V, HP C7438A DAT 72,

Added Support for the following libraries:
Qualstar RLS Series Libraries, Quantum DX100, HP MSL6000, HP MSL5000,
QUANTUM ValueLoader

In addition, several changes have been added to address serialization,
library inventory, and extend/retract issues. The following list
identifies the library and the issue that has been corrected.

ADIC Scalar i2000 - extend retract issue
Compaq MSL5000 - barcode inventory issue.
OVERLAND Libraries - barcode inventory issue.
Fujitsu LT160 Eternus - empty-map and serialization issue

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
During disk staging duplication, bpduplicate prints the following message
although no error has occurred.

11/22/2003 11:25:35 AM - Error bpduplicate(pid=1636) from host dcdell1,
COMPLETE_MOUNT QUANTUMDLT70000 0

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Exchange 2000/2003 restores may fail if the restore includes many log files.
The tar debug log may be as follows:

11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:4 dwSize:2
dwBufferPioCnt:0
11:36:54.556 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: INF -
exchange_2000_access::m_fWriteIoPartializer: dwBlockSize:0 dwSize:65536
dwBufferPioCnt:2
11:36:54.571 AM: [8140.4520] <2> ov_log::V_GlobalLogEx: ERR -
exchange_2000_access::m_fWriteIoPartializer:FS_WriteObj() BlockSize(82)
returned on partialized I/O request

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
With NetBackup 5.0 MP1, Exchange cumulative or user-directed backups fail
when media multiplexing is greater than 1 on the policy schedule. The
backups fail with a status 14, file write failed. In the progress log, the
following error appears:

FTL - tar file write error (40)

Workaround:
In the cummulative incremental or user-directed type schedule in the
Exchange policy, set media multiplexing to 1.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Correct the case where the 's t' command within tldtest returns incorrect
data when the number of transport is 0.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up encrypted data on Windows 2000 clients using Windows Open
File Backup to backup an open/active file, the encrypted data will be
inaccessible to the backup, and the backup will end partially successful.

Additional Notes:
In NetBackup 5.0 MP3, Windows Open File Backup snapshots will be disabled
when backing up encrypted data on Windows 2000 clients. This is not
applicable to Windows operating systems newer than Windows 2000 such as
Windows XP and Windows 2003. A logging message similar to the one below may
appear in the bpbkar32 debug logs indicating this on Windows 2000 clients:

4:29:09.328 PM: [2620.2648] <4> file_access::V_OpenForRead: INF - Disabling
snapshots for: D:\lock\ORW_SN.txt

By disabling snapshots for Windows encrypted data on Windows 2000 clients,
these files may not be accessible to the backup if they are busy or locked
by another process. If Windows Open File Backup protection is important,
Windows encryption should be disabled on the files being backed up.

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

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

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

Note: Any whitespace in the above entries will be collapsed.

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

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

DRIVE_NAME_SEED = VEND:PROD:IDX

This will produce drive names of the form

QUANTUMDLT70000

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

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

This will produce drive names of the form

DLT70000-TLD-0-1

Issues and Limitations

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

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

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

3. Drive names remain limited to 48 characters.

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

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a catalog backup tape is called from an offsite vault location before
its return date and injected into a robot, it remains assigned even after
its return date. Thus, even after its return date, vault does not pick it
to back up a catalog in future vault jobs.

Workaround:
After catalog media is injected back into the robot, unassign it manually
by using the vmquery command. Then vault will use it for future catalog
backups.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Ejects that are partially-successful are erroneously marked as completed.
As a result, the operator cannot eject the remaining media or re-run
reports.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When "Synthetic Backup" is selected "Override policy storage unit"
and "Override policy volume pool" drop-down boxes become available
without their corresponding check box. Also "Synthetic backup" and "Media
multiplexing" are not mutually exclusive.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The NetBackup License GUI has a feature that creates a text file containing
all of the available features and keys. A problem intermittently caused
gibberish to be included wherever there was a Chinese or Japanese character.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
A problem existed when uninstalling NDMP that left a namespace.chksum entry
in the *NBU_RSP on clusters. Because the uninstall removes this file on the
shared disk, the monitor will report a fault.

Workaround:
To avoid this issue, manually remove the following line from the RSP file
found in /usr/openv/netbackup/bin/cluster/<platform>/*_NBU_RSP.

LINK=volmgr/database/.namespace.chksum

(All NetBackup Servers: Alpha_5 HP Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
On the "Disk Staging Schedule" window, after you select a new DSSU in "Final
destination storage unit" field, this field is grayed out. If you select OK
to save and then reopen the "Disk Staging Schedule" window, the "Final
destination volume pool" field is not grayed out or locked. This field
should be grayed out. (On the NetBackup 5.0 UNIX Java GUI, the field is
locked.)

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
If you have multiple users with the same name but different domains,
they do not appear in the available users list. If they are in the
assigned users list, they appear properly.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Non-ASCII data in a license key description is being displayed improperly
in the license key dialog.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The ndmpmoverlistener.exe process shows a growing handle count and a page
fault that will eventually bring down NDMP drives.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
SAP agent incorrectly sorts backup files by size on VxFS.

This problem appears only when backing up VxFS Quick I/O files on UNIX.

With the SAP database extension, VxFS Quick I/O file sizes are
incorrectly evaluated to a size of zero bytes. This creates a problem
when sorting backup streams by size. Therefore, the streams (drives)
are not equally loaded, which causes the backup to run longer than
expected.

(NetBackup Clients: ALPHA HP Intel-NT Intel64 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description:
The SAP database (DB) environment agent reports a successful backup
despite an actual failure occurring.

This problem only occurs when the agent is called in SAP DB environment
with an adapter program. (This problem is not relevant for SAP on Oracle.)
The problem occurs if there were previously successful backups and current
backup just failed. The log of the failed backup would show input
files as saved, however, these files were saved from a previous successful
backup. This could mislead the user into thinking a failed backup was
successful when it was not.

(NetBackup Clients: ALPHA HP Intel-NT Intel64 RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description:
Localized characters were being turned into unreadable gibberish by a
third party charting API. The File System Analyzer (FSA) would then
display this translated text as gibberish. To avoid displaying the
unreadable characters, the localized characters are no longer passed to the
third party charting API.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Corrected a typographical error in bpdbm by changing "sysnthetics" to
"synthetics".

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Flashbackup single file restores did not start. In addition, bprd was slow
sorting the file history.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restart of frozen image backup (non-WOFB) can fail. The scheduler
erroneously clears the snapshot information prior to scheduling the backup.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following changes have been made:
- Added error handling for blank barcodes and missing media magazines
on DELL PV-132T.
- Changed the media type for IBM 3592J to hcart2.
- Added/Changed error handling for blank barcodes and missing media
magazines on IBM 3582, COMPAQ MSL5000, COMPAQ SSL2000, IBM 3607
to fix inventory issues.
- Add Sony SDX-400V, SDX-500V drives.
- Add Qualstar RLS-4124, RLS-4445, RLS-4470, RLS-5244, RLS-6227, RLS-8116,
and RLS-8236.
- Fixes inventory issue for some STK libraries when MAP is empty and
inventory is done with empty MAP selected.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A problem existed where original images on disk storage no longer show up
in the catalog, or in the images on media report, but they still remain on
the disk storage unit taking up memory. To fix this issue, changes were
made to the expiration date of disk images from Vault after they have been
successfully duplicated.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
tar32 will sometimes terminate with an access violation when restoring
files larger than 8mb that have an object identifier attribute.

Workaround:
Access violation can be avoided if NTIO is disabled according to tech
support note 264633.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Using the options that allow a UNIX file system to be restored without
crossing mount-points fails by restoring all files under the path
instead of just the single filesystem.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Duplication flags in NetBackup Vault do not work correctly when a disk
storage unit is defined as a destination for a copy.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
Archive bits were cleared for an entire incremental backup job when the job
was resumed and completed successfully.

(NetBackup Clients: Intel-NT Intel64 )
--------------------------------------------------------------------------------
Description:
SQL Server backups fail if more than 32 databases are backed up together.
This occurs because the SQL agent interface places a GROUPSIZE count into
the batch file. However, if the count is greater than 32, then the job
fails.

The GROUPSIZE count is used for grouping advanced client backups. To
resolve this problem, GROUPSIZE will not be specified if the number of
databases selected for backup exceeds 32.

NOTE: BACKUP $ALL still exhibits this behavior if there are more than
32 databases. This will be corrected in the next major release of
NetBackup.


Workaround:
To avoid the issue, edit the script used for launching the backup and
remove the BATCHSIZE parameter.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
An occasional failure occurred when duplicating True Image Restore (TIR)
backups. The failure may have occurred if there was a delay in mounting
the write media.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After installing NetBackup 5.0 MP1, the SQL backups fail with:
VxBSACreateObject: ERR - CreateObject called from invalid transaction
state: 0

This occurs when backing up a cluster.

Workaround:
To avoid this issue, edit the batch file and remove the keyword-value pair,
<GROUPSIZE n>.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
With STK's new verison of SSI, certain environment variables are required
to be set when the vm.conf entry ACS_TCP_RPCSERVICE is set. The variables
are set to default behavior unless they are set in the vm.conf.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Failed or interrupted VxFI (VSP or VSS) snapshot attempt can leave a
crashed
or hung bpfis process, and a hanging backup.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Corrected a syntax error in bpbbackupdb.c.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A regression was introduced in NetBackup 5.0GA (and continued in
NetBackup 5.0MP1) whereby the bpcatlist command will not work properly with
the "bpcatlist -client <client-name>" syntax.

The following commands, "bpcatlist -client all" or "bpcatlist -client
<valid-client-name>" will return a status 227, (No entity was found).

Workaround:
The use of this command cannot select a specific client to archive the
information about, but may archive on other attributes.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This enhancement enables NetBackup to work in a Plug and Play environment.
You can now use NetBackup with Plug and Play tape class drivers and the
Storport driver.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When restoring a system that contains the 'Cluster Database' portion of
System State, the restore may fail with a status of 5. While examining the
progress log from the operation, it can be seen that the number of files
restored does not equal the number of files attempted.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Resume of a single-stream suspended job would backup the complete policy
file list instead of only the stream's portion of the file list.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An SQL Server object backed up by the NetBackup SQL agent between 12:00 and
1:00AM cannot be selected in the SQL agent backup history window of the
restore dialog box. When an attempt is made to select such an object, a
pop-up message reading, "Please enter an integer between 1 and 12" is
generated.

Workaround:
Since the target object cannot be selected, then you must work around this
problem by creating the restore script (.bch file) manually. Otherwise, do
not do backups between 12:00 and 1:00AM.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Bptm or bpdm may crash after bpsched restarts following a bpsched crash
and
subsequent resuming of checkpointed backup jobs on media servers. This
change will cancel existing duplicate jobs when this situation occurs, or
prevent the crash from occurring.

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A problem existed when displaying more than 1635 volume records in the
media graphical user interface. For example, if 100,000 volume records
existed, and you changed servers to another master server, then clicked on
the media tree node to display these volume records, the display would only
show about 98,360 volume records. If you did a "refresh all", the cache is
cleared and the original 100,000 volumes are displayed again. This seems
to be the case whenever administering multiple volume databases with more
than 1635 records.

Workaround:
After doing a change server, select the "view|refresh all" menu item to
clear the internal cache.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
File system verification for Point-in-Time rollback restores passes on
Windows client when there are new files on the file system. File system
verification for Point-in-Time rollback also restores passes when the
restore list does not match the file list on the snapshot. In both cases,
file system verification should fail.

(NetBackup Clients: HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:
Vault does not check that all fragments of the source image to be copied
are resident in the tape library.

Workaround:
This is a rare occurance that only happens when media is removed from the
tape library manually.

(All NetBackup Vault Servers)
--------------------------------------------------------------------------------
Description:
When the primary copy of the data image is expired, synthetic backup fails
even though there are valid code exists.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The SAP Agent is unable to read output file of restore_filter script. This
failure occurs intermittently and produces 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 the source client (a backed-up client) did not have soft links to the
actual file paths of the SAP data files. During a restore of a target
client (a new destination client), the SAP agent did not adjust the file
paths to match the originally backed up paths. The following is a sample
output of this type of problem:

************************************************************************
Program: ./backint 5.0GA
Input File: ./in_re
Profile: ./initSAP.utl
Function: RESTORE
*************************************************************************
#NOTFOUND <input file name>
*************************************************************************

Also, in the backint log, the following is recorded:

"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"


Workaround:
In case where restore_filter fails intermitently, try repeating restore
operation.

(NetBackup Clients: ALPHA HP Intel-NT Intel64 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Description:
Following bpsynth messages were not getting localized.

"unable to receive the response to the image query, error=%s(%d)"
"caught synth EXCEPTION, error=%s(%d)"
"preparation for generating synthetic image failed,
error = %s(%d)"
"no images were found to synthesize"
"end bpsynth with status ="

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup patch NB_50_2_M_268356.winnt.intel.exe can provide miss-matched
versions of the netbackup.dll after applying the MP2 patch. NetBackup
processes that access the netbackup.dll while the patch is being installed
will cause the installer to not update the correct version of netbackup.dll
in other locations (such as, Volmgr/bin, NetBackup/bin/goodies,
NetBackup/bin/admincmd).

Microsoft Event log error message looks like the following:

Event id 7024 - "The NetBackup Device Manager service terminated with
service-specific error 1. " Event ID 4234 - "unable to load bpnp.dll. The
specified module cannot be found."

Workaround:
To avoid this issue, manually copy the correct version of NetBackup.dll from
VERITAS\NetBackup\Bin to the other locations (if they exist):

Volmgr/bin,
NetBackup/bin/goodies,
NetBackup/bin/admincmd

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In the Windows NetBackup Administration Console Activity Monitor, if the
services details dialog is used to start and stop services, the
NBConsole.exe process will crash if the dialog has been up longer than the
configured refresh time and the service is then started or stopped.

Workaround:
Use the Services list to start and stop services.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Systems with multiple tld or multiple tl8 robots may see strange behavior
across robot numbers on remote (not control hosts) media servers when the
daemon is bounced. In the worst case, this can include the drives going
into "AVR" control mode on the noncontrol host media servers. Generally
this is started by a catastrophic failure of one of the robots.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"Instant recovery backup to disk only" under the "schedule options" is
grayed out and cannot be selected.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
The result window of the inventory dialog is gibberish when using
NetBackup 5.0 Japanese or Chinese language packs.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
NetBackup 5.1 installs the VSP v1.03 snapshot driver which causes problems
with VSS snapshot creation for other requesters (for example, EMC
TimeFinder) when it is installed as part of VERITAS Storage Solutions 4.0
for Windows. VSS snapshot creation for non-NetBackup requesters will fail
when NetBackup and VxVM is installed as part of VERITAS Storage
Solutions 4.0 for Windows because of an issue with the VSP driver, v1.03.
VSP driver version 1.04 will resolve this issue.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
On AIX, a scheduled backup of the DB2 template fails. The actual backup is
successful but AFTER the backup and just before exiting, the process
(bpdbsbdb2) core dumps.

Workaround:
For a scheduled backup/restore, convert the template into a script using
the following command.

"/usr/openv/netbackup/bin/bpdbsbdb2 -g <script_name> -t <template_name>"

Next, add the script to the file list of the DB2 policy.

All NetBackup Windows Clients HP Linux2.4 RS6000_433 Solaris
--------------------------------------------------------------------------------
Description:
Corrected a restore problem from the disk where a status 92 would occur if:
- The image contained multiple disk fragments and first file of the restore
was not in the first fragment.
- The size of the fragments, prior to the one containing the first file,
were not a multiple of 1K.

The above conditions can occur during a MPX multiple copy backup, one
or more copies to disk, and one or more copies to tape.

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

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Point in Time rollback is failing the file system verification check #2.
The purpose of this verification check it to make sure that all the files
specified in the restore list exist on the snapshot backup.

(NetBackup Clients: Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:
When trying to perform a Lotus PIT restore (using PIT) when a secondary
restore is required to restore the 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 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:
Bprd hits a segmentation fault and core dumps. The issue appears to
occur when the log file path for the bprestore log exceeds 58 characters.
This only occurs when the media server involved is not the master server,
and when FQDN names are used.

To resolve the issue, increase the command buffer size to BUFFLEN (4096),
and implement bounds checking on all string buffers, where practicable,
with the use of V_strlcpy, V_strlcat, and snprintf().

Additional Notes:
While libVcom.so contains no changes, it is required to resolve new entry
points introduced in libsfr.so.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added Solaris 10 to drop-down menu.

Additional Notes:
For "Solaris Solaris10" to show when configuring clients into a backup
policy, the user must execute the following command:

/usr/openv/netbackup/bin/goodies/new_clients

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
On a Windows client, the System Volume Information directory is causing the
file system verification for Point-in-Time rollback check #2 to fail. The
functions of Check #2 is to make sure that all of the files in the restore
file list exist in the snapshot.

Workaround:
On the restore user interface, check "Overwrite the existing file" to skip
the file system verification for Point-in-Time rollback.

(NetBackup Clients: HP Intel-NT Solaris )
--------------------------------------------------------------------------------
Description:
Cannot enumerate "Microsoft Exchange Mailboxes" from the NetBackup client
GUI (Backup, Archive, and Restore GUI) on a localized Chinese Exchange
server. The tree under "Microsoft Exchange Mailboxes" does not expand.

Backup attempts for Exchange Mailboxes also fail on a localized Chinese
Exchange server with the following error in the bpbkar log:
14:08:47.025: [488.5380] <2> ov_log::V_GlobalLog: INF - HrCreateProfile():
Profile ''Backup Exec Exchange Agent 71728ea7.00001504''
successfully created
14:08:47.291: [488.5380] <2> ov_log::V_GlobalLog: INF - ConfigureMsgService
()
returned 81002746.!user ???!
14:08:47.307: [488.5380] <2> ov_log::V_GlobalLog: INF - Somehow we failed
but
without setting the return code hres =81002746!


(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Resume of a checkpoint backup could select a different media server if
failure on initial backup attempt.

Failure scenario:
1) Backup reached a checkpoint.
2) Then failed (this case was a 13 "read failed").
3) Scheduler attempts to programmatically re-submit.
4) But the drives were re-set & downed.
5) So, the job exited with a 213 "no storage units available".

The original storage unit information was "lost" so the job could
potentially resume on a different media server. If resumed in this way,
the backed up data would reside on two different media servers and any
subsequent restore would fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Changes needed for Solaris10 support.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After an NDMP import, the file count drops by a very Large number.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After NDMP import the file count drops by a very Large number.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SQL alternate client backup fails if NetBackup install volume drive letter
is different between the primary and secondary clients.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The potential for missed files can occur if all the following conditions
exist:
1) Advanced client backup.
2) Incremental backup.
3) Multi-stream backup.
4) Backup stream is non-stream 1.

Files may be missed if they are modified after the snapshot is taken but
before the (non-stream 1) image is created.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The resume of a checkpoint backup could select a different media server if
a failure occurred on initial backup attempt.

The following list summarizes this type of failure scenario:
1) Backup reached a checkpoint.
2) Then failed (this case was a 13 "read failed").
3) Scheduler attempts to programmatically re-submit.
4) But the drives were re-set & downed.
5) So, the job exited with a 213 "no storage units available".

The original storage unit information was "lost" making it possible for the
job to resume on a different media server. If resumed in this way, the
backed up data would reside on two different media servers and any
subsequent restore would fail.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
There is a potential for missed files if all the following conditions
exist:
1) Advanced client backup.
2) Incremental backup.
3) Multi-stream backup.
4) Backup stream is not stream 1.

Files modified after the snapshot is taken but before the (non-stream 1)
image is created may be missed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
One CPU may reach 100% utilization for a bpbrm process that encounters a
certain Checkpoint/Restart for Backup state. If there are as many bpbrm
processes in this state as there are CPUs on the system, the system may
appear to be non-responsive because the bpbrm processes are using up all
available CPU cycles. This problem will only be seen on Windows media
servers, not other platforms.


(All NetBackup Servers: Intel-NT)
================================================================================


=========
NB_50_2_M
=========
Description:
When performing System State backups on a Windows XP and/or a Windows 2003
Server, the backup may appear to hang when it backs up the Registry or it
may generate errors while backing up the Registry.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When using NetBackup Access Control hostnames, a specific size may cause an
erroneous Authorization denial.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following two issues with checkpoint restart for backups have been
resolved:

1) An import may fail if a successful checkpoint restart backup that is
incomplete or is suspended prior to the first checkpoint and then is
resumed and completes successfully. The phase 1 import log would show one
or more of the following entries:

13:45:45 INF - Found existing image information for client test, policy
itest, and schedule Full, done on 04/13/2004 13:37:56.
13:45:47 WRN - Cannot import client test, policy itest, and schedule Full,
copy 1 fragment 1 already exists. Skipping this image.

The phase 1 import will then succeed. However, the phase 2 import will
fail with the following error:

13:56:19 INF - Import of policy test, schedule Full (test_1081881476)
failed, tar had an unexpected error.


2). For a checkpoint restart backup, in the rare case where bptm detects
that a position check problem occurred following a checkpoint because of a
misconfigured drive or a rewind from an external source, and the backup is
later resumed, the information on the tape prior to the checkpoint may be
invalid.

The bptm log would indicate the position check problem with one of the
following logs after a checkpoint:

08:39:57.969 [4393] <16> write_data: FREEZING media id 00011, too many
data
blocks written, check tape/driver block size configuration

OR

log.041204:14:39:12.373 [6416] <16> write_data: FREEZING media id 00005,
External event caused rewind during write, all data on media is lost

The problem would occur if the same backup were resumed and completed with
a successful status.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
FlashBackup restores of large files were failing on Windows platforms.
This happened if the extents composing the files described more than 2GB
of data. In this case, the extents larger that 2GB were broken down into
smaller units but not all of the fields associated with that extent were
propagated correctly.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A Checkpoint Restart backup may hang after resuming an incomplete backup.
This would happen if the backup error occurred after backing up greater
than four gigabytes of data.

The bptm log will show many entries, similar to the following example,
where the calculated blocks value and the blocks in cpr value do not
change.

09:40:43.700 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508
09:40:43.730 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508
09:40:43.760 [2140.3540] <2> write_data: Received checkpoint for backup id
crowvalley_1079629802, calculated blocks: 13147044 blocks in cpr: 13081508

Workaround:
Disable the Checkpoint Restart feature in the policy, or create a maximum
fragment size in the storage unit that is less than four gigabytes.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An issue existed that caused bpbkar32.exe to crash during the restart of
incremental backups.

(NetBackup Clients: Intel-NT intel64 )
--------------------------------------------------------------------------------
Description:
Media position error may occur while attempting to restore from a copy of a
backup created by Inline Tape Copy. The bptm log shows an entry 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, you can do the restore from the other copy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Synthetic backup did not recognize or work compressed images. As a result,
a synthetic backup would ignore compressed images.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Cannot restore from a CheckPoint Restart job that was restarted.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An interrupted Checkpoint Restart backup would time out after the backup
was resumed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Queries for images that have XBSA extended data fail in bprd when trying to
connect to dbm while the socket is being overwritten. This issue has been
address by increasing the size of the data buffer by 2048 bytes per file to
account for the XBSA extended data.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The restore of a backup created by NetBackup 4.5, or earlier
NetBackup releases may fail on NetBackup 5.0. This defect
applies to backups of a raw partition and backups of a
file whose size is 1GB or greater.

The failed restore may return an exit status of 0, and it
may otherwise appear to have succeeded. However, the restored
file will not contain all the data of the original file.
Alternatively, the restore may exit with a status of 3 or 5.
The tar debug log may contain a message of "invalid tar header"
for the failing file.

In addition, attempts to verify the backup image may fail on
NetBackup 5.0.

Workaround:
1. Expire the backup image.
2. Import the backup image.
3. Run the restore.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Catalog archiving does not properly handle images written by
NetBackup 3.1.1. Using the archive tools with images that do not have a
CATARC ID can result in a catalog file being backed up and removed without
the CATARC ID being written.

Workaround:
To avoid this issue, add the line "CATARC 0" to the catalog image file
before including it in a bpcatarc call.

Additional Notes:
If the images have already been archived without the CATARC value being
written, you can recover the files by restoring the them from the backup
that resulted from the initial bpcatarc call.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a policy with checkpoints enabled uses a storage unit with a maximum
fragment size, and the maximum fragment size is reached prior to the first
checkpoint, the job may not be resumeable. When the job is resumed, bptm
fails with a 223 error.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
This enhancement enables NetBackup to work in a Plug and Play environment.
You can now use NetBackup with Plug and Play tape class drivers and the
Storport driver.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Memory Fault When Running User Initiated Oracle Template Backups In
Japanese Localized Environment

This problem is limited to Japanese localized environments.
It can happen when running a User Directed Oracle template backup. A User
Directed Oracle backup is initiated in a few different ways:
1.Using the Oracle Wizard ? Go through the wizard options and run template.
2.Using the Administer Database Templates option in the Actions Menu in the
Backup, Archive, and Restore interface ? Select a template and run it.
3.Running the Oracle template from the command line using bpdbsbora

The name of the executable file that creates the memory fault is bpdbsbora.
Logs for this executable are located at:
/usr/openv/netbackup/logs/bpdbsbora/log.<date>

If this problem occurs, the last few of lines in bpdbsbora log should
look similar to the following:

17:44:50.593 [16702] <4> VxBSAGetPolicyInfo: INF - request string: <rue
am_ora NONE>
17:44:50.850 [16702] <4> VxBSAGetPolicyInfo: INF - Policy Info:STD

(NetBackup Clients: ALPHA HP Intel-NT Linux2.4 RS6000_51 SGI Solaris )
================================================================================


=========
NB_50_1_M
=========
Description:
When starting a backup using the -i (immediate) and -L (logging) options,
the job does not appear in the bpjobd monitor (Activity Monitor).

The ability to use backup progress logging on clients when using the
bpbackup -i command, which is currently disallowed by bprd and bpbackup,
has been added. In addition, bpbkar is successfully receiving the
-L option, indicating that bpsched is passing the log file successfully.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler can get socket read failures if the shell script writes
error messages to stderr. The bpsched log will have messages like the
following:

12:26:41.325 [4427] <2> get_string: buffer space for 5121 bytes, but
incoming data needs 1668248940 bytes
12:26:41.325 [4427] <2> get_string: (7) inadequate buffer space for data
12:26:41.325 [4427] <16> readstring: get_string failed: Error 0 (0),
incoming data too large for buffer (-1)
12:26:41.325 [4427] <8> read_bpbrm_stderr: readstring failed: socket read
failed (23)

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

Workaround:
Don't request detailed logging.

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

Workaround:
Don't request detailed logs or initiate the restore from the remote
client.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Ejecting more than approximately 642 tapes results in the vlteject process
failing.

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

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

This change alleviates the AIX problem and is benign on other platforms.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
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 Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
Bad characters may appear in the Device Identifier field of the "scan"
utility output for some devices. The "scan" utility now displays the
correct Device Identifier information.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the Activity Monitor is used to terminate a vault job, the catalog
backup jobs that were started by vault were not terminated.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
FlashBackup does not restore VxFS meta data correctly. For example, if a
file contains VxFS attributes (such as reserve or fixed extent size), the
file restore will fail resulting in a zero length file.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Q_CLIENT_FIM_LIST and Q_IMAGE_INCREMENT_RESUME in the header file
are equal. Fortunately Q_CLIENT_FIM_LIST is NOT used to query bpdbm. It
is only used locally in the source file. To resolve this issue, the
Q_CLIENT_FIM_LIST has been reassigned.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A consolidated eject performed to a robot with no MAP (media access port)
from the vltopmenu user interface states that media are moved into a single
off-site volume group when they may not be. The output has been enhanced
to list each volume and the off-site volume group that it has been moved
into.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
A crash occurred if a user deleted a Storage Unit Group from the left pane
of the NetBackup Administration Console for Windows after a Storage Unit
Member had been deleted. This issue occurs only on Windows systems and
when this operation is performed from the left pane of the GUI. This error
does not occur if you delete the Storage Unit Group from the right pane
of the GUI.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Problems with barcode errors in exabyte libraries have been fixed. In
addition, fixes for cleaning tape recognition in Compaq/DEC rebadges of
Overland libraries and Sony CSM serialization are also included.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The pop up associated with dbbackex, that displays upon completion of a
command, contains text that is not legible.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The user can now backup the master database using an advanced client
method. If an advanced method is used for backing up the master database,
then the user does not have to manually place SQL Server into single-user
mode to restore the master database.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
This patch effectively enables SQL Server advanced client backups based
upon the functionality described in the NetBackup SQL Server 5.0 System
Administrator's guide.

In addition to that functionality, a method is provided in which multiple
databases can be quiesced together and split-off to form a single snapshot.
This minimizes the usage of system resources if the databases exist on a
single volume, because the aggregation of constituent files would use one
snapshot volume instead of one per database. The method for aggregating
database advanced client backups is called backup ?grouping?.

The SQL agent will attempt to use grouping when you submit multiple backup
operations in a single batch file in which the first operation specifies
the groupsize via keywords "GROUPSIZE n". The following conditions must
also apply.

* All operations must use the same SQL policy.
* The policy must be an advanced client policy..
* All the operations must be full database backups.
* None of the backups may specify the master database.

A change is made to the backup script generated by the SQL agent such that
the keywords "GROUPSIZE N" (where N is the number of operations) will be
inserted when multiple databases are selected from the "backup database"
dialog box. The presence of "GROUPSIZE N" means that the SQL agent will
launch a grouped backup provided that the grouping criteria apply.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Changes have been made to use version 3.23.58 of MySQL for nbdbd.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup MSSQL listbox does not scroll horizontally for a long database
name in the right pane of the backup dialog.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
If SQL Server 7.0 is installed as the default instance on a host and
there are also one or more SQL Server 2000 instances, then the SQL
agent "dbms log on options" dialog may display the incorrect SQL
version when a different SQL instance is selected. For example, if the
SQL 7.0 default instance is "remembered" from the previous session and
you select a different instance on the same host machine, then the DBMS
log on options dialog box will still identify 7.0 as the current
version.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Scrolling of the SQL restore dialog history windows does not work
consistently making it difficult to use on low-resolution terminals.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Create SQL user_ops directories if they do not already exist. This prevents
SQL agent backups from failing if the user has deleted these directories or
if they are correctly created by the install.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Alternate buffer backups are no longer inhibited for SQL Server 7.0.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
NetBackup 5.0GA incorrectly allows the user to select the 'Use data mover'
attribute for Microsoft Windows NT and FlashBackup-Windows policy types for
Advanced Client.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A buffer overrun problem that caused vmd to core dump on Windows systems
has been corrected.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
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 HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
Description:
NBAC has required use of FQDN host names in the past. Now host names are
accepted as short or long host names and are converted to long host names
internally as needed.

(All NetBackup Servers)
--------------------------------------------------------------------------------
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:
IDR recovery fails in the last step with the following message:

"The recovery application "C:\Windows\system32
\asr_pfu.exe /restore /sifpath=C:\Windows\repair\asr.sif" returned an
error code 0x2. Since this indicates an unrecoverable error, ASR
cannot continue on this machine."

Workaround:
Without installing the patch, the problem can be avoided by manually
running the VERITAS\NetBackup\Bin\drfile.exe command before performing any
backups on a computer.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When restoring a file, tar32 may crash. This will happen on a file that was
growing (increasing in size) during the course of the backup.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When backing up a NetApp filer via a network mapped drive, errors may be
reported in the bpbkar32 debug log. The errors may contain the following
error code (WIN32 -1073741809: Unknown error). After getting this error
a couple of times, the backup process (bpbkar32) will crash.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
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:
After running backups on a Windows machine, there may be some bpbkar32.exe
processes running that never go away.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Because of the complex nature of timezone and daylight savings time
interaction, the timezone correction factor for daylight savings time was
using the wrong value and caused an incorrect check to see if daylight
savings time is currently in effect. Changes to the timezone correction
macro were made to resolve this issue.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A 134 status error would be displayed as an attempt or retry in the
Activity Monitor even though they are not counted as tries. A change has
been made to the scheduler to not send an "end_try" to bpjobd when a
134 status error is received. In addition, a message as been added that
indicates the job was queued again because of a 134 status error.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The log analysis utilities (backuptrace, backupdbtrace, importtrace,
restoretrace, duplicatetrace, verifytrace) fail reading the registry when
executed by a non-root administrator on Windows server running NetBackup
5.0 GA with an NBAC configuration.


(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
In the NetBackup 5.0 GA version, the ReportHeader is truncated and shown as
only 60 characters in VaultReports. This issue has been corrected by
printing the Report Header in multiple lines when it can not fit in single
line.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
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:
If the bpschedreq -predict command is executed with a time that is not the
current day, the exclude dates will not be taken into account.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Allow NBAC users to enter an Authentication Broker and port when
performing a "Login as New User" or "Change Server" action from the
Windows NetBackup Administration Console.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Generated a much smaller Synthetic Image than a previous TIR incremental
image when the Synthetic image should have been about the same size as the
TIR incremental image.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
FlashBackup for Windows does not support backup for cross-mounted volumes.
This issue has been resolved and backups for cross-mounted volumes are now
supported.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Put VCS version numbers into source files.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Several database files could be left open under certain rare error
conditions. Over a long enough time, the vmd process could run out of file
descriptors.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A suspended restore can be restarted more than once if it takes a while
to transition to the active state.

Workaround:
Even though the state doesn't change in the job monitor, don't try
to resume a restore job more than once.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
In Windows GUI, run Container Inventory report for all/specific
container(s). Output of this report is not shown in proper format. User can
find multiple entries of same data. But there is no Data-loss. If user runs
this report multiple times output would be shown with combination of
existing containers and media assigned to containers.

Workaround:
Use one of the workaround.
1. Java GUI to see Container Inventory report output

2. Run the vltrun command on command prompt of Master server, on which user
wants to see the Container Inventory report data. vltrun.exe is placed
at "Installed_path\Netbackup\bin\vltrun.exe". Pass the following parameters
to vltrun command.
e.g. vltrun -profile [<profile>|<robot/vault/profile>] -dup_id
<Session_ID> -function report -command container_inv

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
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 SQL agent is not able to find SQL images that were created by
NetBackup 3.2. These would normally be selected if the user selects
NB_LEGACY_SQL7 or NB_LEGACY_SQL65 in the Backup History Options dialog. This
problem is fixed by corrections that are made in the SQL agent's image
browsing procedure.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Auto path correction will down drives that have a valid path, but do not
respond to commands. To address this issue, the auto path correction can
now down drives that do not have valid paths. In addition, this change
enables ltid to start even with missing paths.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Point-in-time rollback file system verification fails if there are
unreadable ASCII characters in the file name.

(NetBackup Clients: 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:
The restore paths are 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 Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Enhance bptm to use MEDIA_UNMOUNT_DELAY for duplications to reduce
unnecessary unmounts/re-mounts during Vault sessions.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support for the following Libraries:
- ADIC Pathlight VX
- Dell PV-136T and PV-160T
- HP E-Series Library
- Qualstar RLS-4221
- Quantum SDLT600
- Quantum ValueLdr
- Quantum ValueLoader
- Sepaton S2100
- Sony CSM Library Serialization

In addition, several changes have been added to address serialization,
library inventory, and extend/retract issues. The following list
identifies the library and the issue that has been corrected.

- Dell-PV-136T fixed inventory issue
- Library Serialization on Sony CSM library series
- Serialization for HP5597A
- library inventory issue with Quantum M-Series libraries (missing magazine)
- extend/retract issue on ADIC Scalar 1000

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When changing the drive type and the robotic residence of a drive, some
combinations would yield the error message, "This robot does not support
multiple media types."

Workaround:
To avoid this issue, the user can make the required change in two steps:
1) Change the drive's type.
2) Change the drive's residence.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
FlashBackup cannot restore a file that has a path length greater than 260
characters (including the file name). Primary indication is the restore
fails with an error 5 and not all files are restored to the specified
directory.

The following information is logged:

TAR Log Messages

2:25:07.875 PM: [1396.672] <16> vxms_open_file: fiml_create failed error = 6
2:25:07.875 PM: [1396.672] <16> vxms_write_data: fiml_write_file failed
error = 3


With the following Windows Event log application warnings:

Source: VxMS NTFS Mapping
Category: None
EventID: 4099

The description for Event ID ( 4099 ) in Source ( VxMS NTFS Mapping
Plug-in ) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a remote
computer. The following information is part of the event: Error: x00001003,
in file NtfsOpenFile.cpp, line 220.

Workaround:
Restore file to a shorter alternate path name.

Additional Notes:
When file paths longer than 260 characters are created, it is not possible
to directly access these files through the Windows explorer. One method to
access the files is to share the directory into which the files were
restored and then use the map network drive operation to map the shared
directory to a drive letter. The files will then be accessible.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
For FlashBackup on Windows, individual file restores of compressed files
were not restoring the data correctly in all cases. The major problem
existed when a single compression frame was split between extents,
something that would occur with fragmented disk allocation.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
For FlashBackup on Windows, individual file restores of compressed files
were not restoring the data correctly in all cases. The major problem
existed when a single compression frame was split between extents,
something that would occur with fragmented disk allocation.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
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 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:
Two issues caused the NDMP dump levels to always be 1. The issues were:

1 - When merging the STREAMS.alt file into the STREAMS file, the dump
level of the last backup was over written. This caused incremental backups
to repeatedly use dump level 1 instead of incrementing each time.

2 - If there was no previous full backup, the incremental backup dump level
did not initialize correctly.

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

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The Java restore interface cannot browse files beyond the mount point for
a point-in-time rollback.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing a SQL snap over multiple databases, one of the jobs may
hang in scheduler if NetBackup server isn't configured for multiple backups
per policy.

To resolve this issue a progress log message is added for this situation.

Grouped backup failed, verify that NetBackup is properly configured for
simultaneous backups to the same policy.



All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The Exchange agent has the requirement that the NetBackup client
service account run under an Exchange Administrative account. However, if
the service is running as LocalSystem on a restore attempt, the restore
will hang and end with a status 5 after tar32 causes an exception fault.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
The "bpimagelist -l" command option in the NetBackup 5.0 release
concatenates the 13th and 14th fields on the FRAG line. These fields are
the Tape Allocation Date Timestamp and the Device Written On.

For example, in the following example the 13th field on the FRAG line is
11 characters long and is actually the value "1062583209" and the
value "0" is concatenated.

FRAG 1 1 1856 0 2 12 1 T00000 zrp 65536 0 10625832090 0 *NULL*
1063188009 0 65536 0 0 0 0 0 0 0

Additional Notes:
Scripts that use the "bpimagelist -l" output may fail or produce
erroneous results.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Drives were being downed each time a system-imposed limit on the value of
a semaphore ID was exceeded causing arvd to exit with an "Error in Semaphore
Operation" error in /var/adm/message.

Workaround:
Down the NDMP drives that are not working.

(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
When a synthetic backup is being created, the program bpsynth suspends tape
volumes that contain images needed for the synthetic backup. Afterwards,
bpsynth unsuspends those volumes.

Bpsynth is suspending and unsuspending even when a volume was originally
suspended or frozen. The result is that previously frozen or suspended
volumes are no longer frozen or suspended after the synthetic backup job
completes.

To correct this issue, bpsynth does not suspend or suspend tape volumes
that were originally suspended or frozen or full.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
After performing an 'Information Store' restore on Exchange 2000, you
are required to execute a FULL backup as the first backup set. This is
to properly cleanup and truncate any logs. This is mentioned in posted
event log messages from Exchange.

With NetBackup, if an incremental backup is executed next, NetBackup will
fail for any storage groups that have been recently restored, but it will
still exit with header information written to tape and a status 0.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The data image, which is created by synthetic backup, will have a default
retention level set to two weeks. The retention level that the user has set
through the configuration was not used.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When viewing the contents of a NetBackup User Group with the group dialog,
the NetBackup Administration Console for Windows allows duplicate user
names to be added to the list on the right side of the dialog.


(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
Synthetic coordinator failed to contact the bpdm process when it finished
its reading task.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When NetBackup is run through a separate network interface, the service
information in the Windows NetBackup Administration Console does not
display.

(All NetBackup Servers: Intel-NT)
--------------------------------------------------------------------------------
Description:
When using synthetic backup on a large number of disk fragments from a disk
data image, it fails to communicate with the synthetic engine, bpsynth and
the coordinator, bpcoord.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The bpfis and bpbkar32 processes were hanging and causing backups to stall.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The bpfis process crashes if vfm.conf has a syntax error because an
incorrect separator is used in a library pathname.

Workaround:
Edit vfm.conf to correct the library pathname.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
FlashSnap backup on Windows fails with status 20 if NetBackup is installed
on different volume drive letters on primary and alternate clients.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When an error occurs when updating a policy, the operation appears to have
completed successfully because the views contain the new data.

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

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

(NetBackup Clients: ALPHA HP Intel-NT RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description:
FlashBackup for Windows does not support the backup of cross-mounted
volumes and produces no error message. The backup succeeds but there is no
catalog information visible for the file system mounted on the junction
point.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
There is no error message. The backup succeeds but there is no catalog
information visible for the file system mounted on the junction point.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
If a client is down when the scheduler is doing autodiscovery, and the
NetBackup Administration Console for Windows attempts to modify a policy,
the policy may get deleted.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Performing multiple-map ejects to an ACS robot with more than two LSMs
could fail if ADJ_LSM entries are not specified in the vm.conf file on the
media servers connected to the robot. The default behavior of assuming the
LSMs are interconnected in a line was not working. The workaround of
specifying ADJ_LSM entries is no longer required when the LSM physical
configuration is interconnected in a line.

Workaround:
Put ADJ_LSM entries into the vm.conf file on media servers connected to the
robot describing the physical interconnections of the LSMs.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An NDMP backup restore will fail if you do not use set the mount point
inode number to 2.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
An Incremental backup, after a synthetic Full Backup, may cause bpdbm to
core dump.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A Synthetic Full backup takes too long to create a backup of more than
20,000,000 files.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A function call to insert_key_list had parameters that were misplaced.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When performing backups using VSS, either for Windows Open File Backup or
Advanced Client, the backup may end partially successful even if the VSS
snapshots for the backup were created successfully. This occurs when using
a VSS snapshot provider other than the default Windows 2003 Server VSS
snapshot provider (such as, when using the VxVM VSS snapshot provider).
Backups may end partially successful because it does not use the VSS
snapshot when backing up active/busy files, thus making these files
inaccessible to the backup.

Workaround:
Use VSP or the default Windows 2003 Server VSS snapshot provider when
running backups for Windows Open File Backup or Advanced Client.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Support has been added for VERITAS Volume Manager (VxVM) 4.0 on Windows
2003. All Advanced Client features that support VxVM volumes on Windows
2000 are now supported on Windows 2003.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
When creating VSP snapshots for Windows Open File Backups and Advanced
Client backups, the debug logging (in the online_util logs) does not log
enough information about the VSP snapshot creation parameters (source
volume, snapshot volume name, VSP cache file location, etc.) This
information is helpful when trouble shooting VSP snapshot creation
failures. In addition, the failure error messages are vague and do not
indicate the cause of the failure when a VSP snapshot operation fails.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Running cron and/or jobs with NetBackup access control enabled requires
that either the expire date of operating system credentials be lengthened
using the VxSS utilities, or that accounts be created in the VERITAS
private domain database with renewable credentials. nbac_cron is a new
binary that simplifies the process of making unattended scripts NetBackup
access control aware.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores or backups may erroneously fail with a 52 status (timed out
waiting for media manager to mount volume).

Workaround:
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 Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
Sometimes during the suspend step of a Vault session, a core dump may
occur (in particular on HP-UX systems).

Workaround:
To avoid this issue, manually suspend tapes being ejected using
"bpmedia -suspend -m <media_id>".

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
The Windows Client interface dialog, "VxSS Security - Login as New User",
now allows the selection of an "Authentication Broker" and "Port."

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Updated acsssi to include the firewall support from STK for ACSLS.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
A SQL customer who plans to uses nightly PFI backups cannot maximize
storage allocation because on-going differentials are always based on
the last full. This is resolved by putting a hook into the SQL
agent to allow the full backup to be cloaked, i.e., unrecognized by SQL
so that it does not mark the full backup as the basis for the next
differential.


All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The grouped backup writes all of the files to one image with the remaining
ones being metadata-only. The problem is that NetBackup always causes a
backup to be launched when an item is cataloged. This unfortunately causes
data to be written to the STU even if their is no data.

The solution is to use one image for all of the grouped backups.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When attempting a restore of a single DB that was backed up with
another DB, the other DB is attempted to be restored and creates TEMP
files.

The problem was that the SQL agent was associating files with databases
incorrectly in the .f file.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The tldcd and tl8cd robotic daemons may not be very resilient to having
connections opened and closed quickly with no data. This does not affect
Windows NT systems.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The scheduler cancelled suspended jobs prematurely. The Windows Open File
Backup does not reuse same snapshot when resuming.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When running backups with the Window Open File Backup option enabled to
backup open/active files using VSS or VSP snapshots, bpbkar32.exe could
crash intermittently. Debug statements similar to the following should
appear in the bpbkar32 debug logs before the crash occurs:

4:43:19.906 PM: [2556.2636] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF -
======================================================================
4:43:19.906 PM: [2556.2636] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF -
Attempting to create snapshots for 'F:\mptog'
4:43:19.906 PM: [2556.2636] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF -
CREATE request: C:\Program Files\VERITAS\NetBackup\bin\bpfis create -WOFB -
fim VSP -id sauna_1074206573 "F:\mptog"

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When a NetBackup 5.0 Windows client backup is run, some backups may end
partially successful because the backup job was unable to backup VSP
snapshot cache files (for example, C:\_vxfiVspCacheFile_0.tmp). These files
should have been excluded by the backup.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Added capability to run bpbackup with both -i and -L options at the same
time. In this case, a progress log will be created on each client machine
in the policy, as well as on the server running bpbackup.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When initiating an immediate backup from the NetBackup Administration
Console for Windows, a warning is displayed if the policy's "go into effect
time" is too close to the present. A query for the time on the server has
been added to allow the user interface to determine the time to see if the
policy can be initiated or not.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Non-stream in control frozen image jobs were not cancelled correctly when a
frozen image failure occurred (bpfis error). This resulted in the
non-stream in control jobs to backup the data multiple times.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Currently, the Vault image list used for duplication is sorted by
increasing Kbytes and the question arose as to whether the Vault image
sorting can be reversed. To address this issue, a new function was added to
determine if duplication of disk images should be done from largest to
smallest size (in Kbytes), rather than the default of smallest to largest.
Whether or not to invert the order is based on an existence of a touch file
in the /usr/openv/netbackup/bin directory.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
Wildcards do not work with restores in multibyte character locales.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
NetBackup now uses the following date format when installed on a Japanese
operating system: 2004/01/19. This format is consistent with the generally
accepted format used in Japan.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When restoring a Filegroup (backed up with adv. client), the restore
will succeed, but an ERR message in the progress log may be misleading
to the user.

Message:
INF - DBClient has been closed for stripe #0
CONTINUATION: - The process cannot access the file because it is
being used by another process.
ERR - Error in VDS->Close: 0x8077000d. The text follows:
CONTINUATION: - All devices are open

The problem is resolved by removing the line of code in PipeServer that
sets the pipe status to done after VDC_MountSnapShot has been processed. By
removing this code, pipeserver continues forward retrieving the next VDI
command, which has a status of VD_E_CLOSE, indicating the device has been
closed.


All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Oracle Server free with alt-client does not work if multiplexing is
enabled. This change also improves snapshot error handling during snapshot
creation and deletion.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The following enhancements have been added to snapshot backups:
1. Performance improvement for the EMC TimeFinder snapshot method
2. Improved snapshot error handling during creation and deletion
3. Improved multistreaming coordination with snapshot
4. Improved error logging


(NetBackup Clients: HP Intel-NT Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:
A cancelled Catalog Backup job leaves the media in the drive instead of
unloading it and moving it back to its slot. Subsequent use of the drive
fails because catalog media remains in the drive. Only a manual operation
from the command line is able to move the media back to its slot and make
the drive available for further NetBackup operations.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a Windows Backup, Archive, and Restore user does not have administrator
privileges, NetBackup does not start the required NetBackup Client Service
when a backup or restore is attempted.

Workaround:
A workaround for this problem is to login as a user with administrator
privileges, and then attempt the backup/restore.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Command line utilities bpbackup, bplist, bprestore, and bparchive fail
when filenames contain Unicode characters that, when translated to a multi-
byte character, contain a backslash.

All NetBackup PC Clients
--------------------------------------------------------------------------------
Description:
When using the NetBackup Windows Oracle wizard, the user's authentication
choice is now correctly saved and used when building the RMAN template.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Verifying Network Data Management Protocol drives can fail because the end of
media (EOM) marker is not recognized. Commands such as bprecover, when used
with NDMP drives, may fail.

Workaround:
Use a non-NDMP drive.

(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
The NetBackup Windows Oracle wizard does not retain the list of selected
Oracle objects when you go from the last screen of the wizard to the first
screen and then back to the last screen.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Vault may not wait long enough for media to be unmounted from tape drives
before starting the eject process. Because of a change to bpduplicate's
use of the MEDIA_UNMOUNT_DELAY bp.conf setting so media aren't dismounted
and re-mounted between duplication of images, vault now adds three minutes
to this delay period before starting ejects. By default, vlteject will now
pause six minutes before starting the eject process. This delay can be
overridden by specifying the -eject_delay argument to vltrun.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
When a checkpointed job resumes, the Activity Monitor displays a 32-bit
integer instead of a 64-bit integer for the block count.

The bpsched debug log can contain very large values in its ESTIMATE and
ESTIMATE_STR lines.
Here is an example:
log.102703:13:37:09.617 [11222] <2> readstring: ESTIMATE_STR: buf
(ESTIMATE -1 -1 avocadocat_1067283424) backid 136924 files (-1), kb
(18446744073709551615)

This can happen when "Kilobytes Written" is set to its default value, -1.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If the debug level is increased in NetBackup while the NetBackup Lotus
Notes database extension is performing a backup, the backup will fail if
an error occurs.

(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
Whenever Windows Open File Backups is enabled for a NetBackup 5.0 client
and its snapshot provider is VSP, VSP snapshots can sometimes remain
undeleted when VSP snapshot errors occur during the course of a backup
using the VSP snapshot.

Snapshot errors can occur when the VSP snapshot has already been
created and the backup job is using the VSP snapshot. The snapshot
could error out for a variety of reasons, but typically is caused by
insufficient amount of cache file space allocated for the VSP snapshot
for the data being backed up.

Whenever such a snapshot error occurs, there is a possibility the
snapshot will not be deleted because the snapshot deletion attempt fails.
This ultimately causes the snapshot deletion process to abort without
deleting the VSP snapshot. Whenever this occurs, a reboot of the machine is
required to remove the VSP snapshot and its cache file.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Following SQL Server master db recovery, the SQL Server remains down. The
agent should bring it back up in the same mode (i.e., single or multiple
user) that it was in prior to the recovery operation.

Workaround:
The user should manually restart SQL Server following recovery of the
master database.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
The NetBackup jobs database daemon (bpjobd) may fail when the bpdbjobs
command, with the -report and -all_columns options, is used to query the
database.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
SQL agent fails to display image for advanced client backup of a database
file. The dbclient log has following info:

13:00:55.058 [2252.6116] <4> CDBbackcat::AllFileObjectsAvailable: INF -
Image
<backrest.MSSQL7.BACKREST\BACK.fil.E_Drive.E_Drive_Data.7.001of001.20040
126124823..C> is not displayed because its constituent file <> could not
be found in its image store
<backrest.MSSQL7.BACKREST\BACK.fil.E_Drive.E_Drive_Data.7.001of001.20040
126124823..C>



All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When resuming a suspended backup job with Windows Open File Backup enabled,
the resumed backup will not re-use the original backup job's volume
snapshots. Instead, if the WOFB Error Control configuration setting was set
to Abort on Error, the resumed backup job will abort and a status 156-
snapshot error will be encountered. If the WOFB Error Control configuration
setting was set to Disable Snapshots & Continue, the resumed backup job
will be resumed without any volume snapshots. This behavior is not correct
and the resumed backup job should re-use the original, suspended backup
job's snapshot volumes if they were successfully created.

All NetBackup Windows Clients HP Solaris Solaris9
--------------------------------------------------------------------------------
Description:
When resuming a suspended backup job with Windows Open File Backup enabled,
the resumed backup will not re-use the original backup job's volume
snapshots. Instead, if the WOFB Error Control configuration setting was set
to Abort on Error, the resumed backup job will abort and a status 156-
snapshot error will be encountered. If the WOFB Error Control configuration
setting was set to Disable Snapshots & Continue, the resumed backup job
will be resumed without any volume snapshots. This behavior is not correct
and the resumed backup job should re-use the original, suspended backup
job's snapshot volumes if they were successfully created.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Oracle Template backup initiated from the master server fails because the
Oracle user cannot read the RMAN CMDFILE created by the ROOT user during the
bpdbsbora execution.


All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
Description:
Individual Oracle Datafiles or Tablespaces do not appear, although the entire
database can be selected and backed up/restored successfully.

All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 Solaris
--------------------------------------------------------------------------------
Description:
Performing PFI backups of multiple Database Files in a batch file. The
first SQL jobs completes fine, any PFI job after that times out. This
happens with non-grouped batches.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
When resuming a suspended backup job with Windows Open File Backup enabled,
the resumed backup will not re-use the original backup job's volume
snapshots. Instead, if the WOFB Error Control configuration setting was set
to Abort on Error, the resumed backup job will abort and a status 156-
snapshot error will be encountered. If the WOFB Error Control configuration
setting was set to Disable Snapshots & Continue, the resumed backup job
will be resumed without any volume snapshots. This behavior is not correct
and the resumed backup job should re-use the original, suspended backup
job's snapshot volumes if they were successfully created.

(NetBackup Clients: Intel-NT intel64 )
--------------------------------------------------------------------------------
Description:
The Volume Shadow Copy Service (VSS) frozen image method is not included in
the drop-down list in an Oracle policy.

(NetBackup Clients: HP Intel-NT Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:
A number of manual steps are required in order to prepare hosts to use
NetBackup Access Control and in configurations involving a large number of
hosts, and a means of automating some of the preparation would ease the
initial configuration process.

The script "nbac_install_helper" installed in the goodies directory
provides basic support for automating the initial Access Control
configuration steps listed in the "Access Management" section of the
System Administrator's Guide. An executable version is also provided for
installations unable to take advantage of the scripted version.

Documentation describing use of the script is provided by "-usage" and "-
help"
flags, by comments in the source code of the script, and by run-time notices
when configuration is attempted.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When resuming a suspended backup job with Windows Open File Backup enabled,
the resumed backup will not re-use the original backup job's volume
snapshots. Instead, if the WOFB Error Control configuration setting was set
to Abort on Error, the resumed backup job will abort and a status 156-
snapshot error will be encountered. If the WOFB Error Control configuration
setting was set to Disable Snapshots & Continue, the resumed backup job
will be resumed without any volume snapshots. This behavior is not correct
and the resumed backup job should re-use the original, suspended backup
job's snapshot volumes if they were successfully created.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When resuming a suspended backup job with Windows Open File Backup enabled,
the resumed backup will not re-use the original backup job's volume
snapshots. Instead, if the WOFB Error Control configuration setting was set
to Abort on Error, the resumed backup job will abort and a status 156-
snapshot error will be encountered. If the WOFB Error Control configuration
setting was set to Disable Snapshots & Continue, the resumed backup job
will be resumed without any volume snapshots. This behavior is not correct
and the resumed backup job should re-use the original, suspended backup
job's snapshot volumes if they were successfully created.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using the Java GUI to initiate drive cleaning, the drive names are
truncated after 22 characters.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Consolidated eject can cause many files to be left open that do not
subsequently get closed. This may result in reaching the open file limit
when many vault sessions are consolidated.

Workaround:
Include fewer vault sessions in consolidated ejects. This problem occurred
when more than 80 vault sessions were included in the consolidation. The
number depends on what the "maximum open files" is set to on the server.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
The NetBackup scheduler may core dump when it prepares to exit if it is
trying to determine which storage units are busy.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Path names extracted from an XBSA record with strncpy() are not terminated
with a null character, resulting in a bad catalog entry.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Corrected numerous situations where a backup job could not be
restarted/resumed because the necessary information was not retained. The
most visible situations were the storage unit not available (219) errors,
but there were a number of other conditions.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Alternate client restore of SQL Server fails for ABM methods.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Suppose the master server and media server are different machines. 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 that "connect backs" with the media server are done via
VNETD. The typical bp.conf entry on the master server would look
something 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:
Don't use vnetd style connect backs with the media server if the media
server is a client.


All NetBackup Windows Clients All NetBackup Unix Clients
--------------------------------------------------------------------------------
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:
VMD on any volume database host can corrupt the volDB (media database), and
may core dump. This is due to an error with the pool database, introduced
with NetBackup 5.0.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Restores of Windows paths containing "\" don't work.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
The spin control next to the "Port" edit field on the "VxSS Security -
Login as New User" dialog box in the Windows PC Client GUI program now
functions correctly.


All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Bpdbm failure in SQL agent browse for FI backups

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When using vxvm snapshot method on Windows, the snapshot may fail with
the error message in online_util log

10:14:43.207 [2840.2876] <2> onlfi_vfms_logf: e51500e7: Could not
associate a drive letter

This is caused by the interaction between snapshot volume and Windows
plug and play. The snapshot volume was recognized as new volume fast
enough by the OS, and vxassist times out. The change is to wait
a few more times for the snapshot volume.



All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Scheduler started multiple jobs instead of just one when restarting a job.
This situation occurs when multiple multi-copy jobs are submitted for
restart/resume. The GUI sends all the selected job IDs, but scheduler needs
to perform a many to one mapping of the requests. Filtering is added to
scheduler to perform this mapping.

Workaround:
select only one job of the multi-copy job set when performing a
restart/resume

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
VxFS file promotion does not support alternate location restore. A check is
required for Instant Recovery restore, for alternate location restore, file
promotion method needs to be turned off.


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Users attempting NDMP restores from the Windows PC Client GUI will no
longer find most files and directories incorrectly marked as
unselectable.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
NDMP backup fails writing TIR data.


bptm log shows:
19:56:36.854 [2969] <16> write_data_tir: ERR - Cannot write TIR data to
media, NDMP return code 9.


ndmp logs shows:

19:56:36.801 [02969] 162988 -> (8) 267 [0] 19:56:36 NDMP_TAPE_WRITE
(0x304) NDMP_NO_ERR (0x0)
19:56:36.801 [02969] 162988 . data_out(0)=
19:56:36.801 [02969] 162988 ** End NDMP_TAPE_WRITE
19:56:36.850 [02969] 162988 <- (8) 599 [267] 19:57:51 NDMP_TAPE_WRITE
(0x304) NDMP_NO_ERR (0x0)
19:56:36.850 [02969] 162988 . error=NDMP_ILLEGAL_ARGS_ERR (0x9)
19:56:36.850 [02969] 162988 . count=0 (0x0)
19:56:36.850 [02969] 162988 ** End NDMP_TAPE_WRITE



(All NetBackup Servers: HP Intel-NT Linux RS6000 Solaris)
--------------------------------------------------------------------------------
Description:
Add recognition for the ACS_LTO_200G vm.conf entry.

(All NetBackup Servers)
--------------------------------------------------------------------------------
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 Servers: ALLVLT)
--------------------------------------------------------------------------------
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:
email notification of backup status is not being sent for Windows clients.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Added support to delete VSP snapshots (cach files) when WOFB is enabled,
this prevents deleting VSP snapshots for XBSA backups.

(NetBackup Clients: Intel-NT intel64 )
--------------------------------------------------------------------------------
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 Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
Multi-stripe SQL RFI backup isn't displayed in SQL image browser. It
appears that bpbrm provides XBSA a bad restore list, setting the
xbsa_flag to XBSA_DATA_EXTENSION for some objects that do contain data.
The case occurs on multi-stripe retrievals, where the first set of
objects contain data, the next set contains no data and the third set
do contain data. After the second set starts using the
XBSA_DATA_EXTENSION (-3), it continues to be used for the third set
which do contain data.

This test case relies on a backup done by washer to
CAM: /washer.MSSQL7.WASHER.db.Ye Olde Howard's Bar and
Grill.~.7.001of003.20040224135654..C


(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
RMAN scripts containing more than one BACKUP command will fail if they
contain a SEND command to reset the NetBackup server using the NBU_ORA_SERV
environment variable after the first BACKUP and the NetBackup server change
is applied to the previously allocated channel. The dbclient debug log
contains the error message: "The license for the requested feature is not
available". The problem occurs because the SEND command can potentially
change the NetBackup server that was used to perform the first BACKUP, and
the license is not being rechecked.



All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 RS6000_51 SGI Solaris
--------------------------------------------------------------------------------
Description:
Some conditions will cause bpplschedrep to crash when setting last day of
the month.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If a multi-stream Windows backup is suspended or cancelled prior to
going "active" (for example: while the snapshot is being taken by stream
number one), then it's possible the suspended/cancelled backup can not be
resumed/restarted.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When backing up databases with long database names, bpbkar32 could crash
because of a memory overrun.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
when trying to perform a move script and restore SQL DB to a new volume,
TAR is attempting to restore DB to original volume (H:) which is not a
valid volume and fails.


All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
tar32 was aborting when restoring compressed data. This was occurring if
the compression frames were fragmented across multiple extents and the
extents contained both compressed and uncompressed data.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Jobs failing with a 134 status were not requeued.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
tldd/tl8d dumping core when attempting to kill an orphaned child process.
Only happens when running NetBackup Media Manager in VERBOSE mode.

Workaround:
Remove the "VERBOSE" entry from your vm.conf file and do not start ltid
using the -v option.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
bpbkar32.exe DrWatsons in a VCS cluster when a virtual name is used as the
host name. The same Backup works if local host name is used.

bpbkar32.exe stops logging in the BEDS_Init() function:

<2> ov_log::V_GlobalLog: INF - BEC_SetRestoreXchgPrivate(1)
<2> ov_log::V_GlobalLog: INF - BEC_SetRestoreXchgPublic(1)
<2> ov_log::V_GlobalLog: INF - SetVirtualNameForNodeName(virtual_g)

The next step in a normal backup would be DumpDleInfo.



(NetBackup Clients: Intel-NT )
--------------------------------------------------------------------------------
Description:
cancel job vxvm snapshot backup hanging

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Jobs ending with 134 and 59 exit codes were marked as incomplete and
cancelled. correct operation would be to retry the job.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Multi-stream & multi-copy jobs fail if all storage units are of type disk

Workaround:
Use at least one tape when performing multi-copy backups

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
IR backup(disk only) failed due to error of generating catalog info.
The online_util log:
09:12:39.415 [2140.604] <32> add_catalog_info: Cannot lstat SE. Errno =
2: No such file or directory

It tried to catalog a keyword "SNAP ID <Backup_id>" and failed stat64().

(NetBackup Clients: HP Intel-NT Solaris )
--------------------------------------------------------------------------------
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:
If SQL Server is configured under binary collation, then some images
may not be displayed in backup history window.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
PFI SQL images are not expiring properly

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
When the customer submits multiple jobs to a Disk STU with Max Jobs set
to 1 all the Submitted jobs go active.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
If the checkpoint name is in the DOS style, now it gets converted to
the UNIX style.

(NetBackup Clients: Intel-NT intel64 )
--------------------------------------------------------------------------------
Description:
After doing a clean install of netbackup Oracle RMAN fails trying to load
orasbt.dll.

All NetBackup Windows Clients
--------------------------------------------------------------------------------
Description:
Unable to cancel, resume, or suspend using bpdbjobs

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Resuming a checkpointed backup job resulted in selection of a disk storage
unit instead of a tape storage unit. This situation can arise at a site
that has a media server with both tape and disk storage units. A resume
needs to continue on the proper media. If initially tape, then resume on
tape. If initially disk, the resume on disk.

Workaround:
Don't mix disk storage units and tape storage units on the same media
server.

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
Cannot resume Windows multi-streamed backup jobs after error 219 (storage
unit not available).

(All NetBackup Servers)
--------------------------------------------------------------------------------
Description:
"configure a vault profile to do a catalog backup that will take at least 20
minutes, run that vault profile, and watch the activity monitor. activity
monitor displays the vault job as done, status 50 - even though the catalog
backup eventually finishes. (and the vault job eventually finishes
successfully, in spite of the activity monitor...)"

solution:

For UNIX implementations, insure that the Activity Monitor is
sent keep-alives while the UNIX implementation waits for a remote
bpbackupdb to complete. The NT edition >always< accomplished this
task, and why UNIX was specifically excluded in the bpbackupdb
command remains a mystery.

(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
vault's logic of checking to decide if an image has already been
duplicated seems to be broken if the image resides on disk.



(All NetBackup Servers: ALLVLT)
--------------------------------------------------------------------------------
Description:
Synthetic Backup image is bad and will not restore.
When extent ends as fragments ends, synthetic engine didn't handle it
well. Additional data is copied and causing catalog mismatch with image.

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

Attachments

NB_50_6_M_280773.winnt.intel.exe (42.8 MBytes)


Legacy ID



280773


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


Terms of use for this information are found in Legal Notices