Maintenance Pack NB_60_1_M.winnt.IA64.exe provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 64-bit Clients and Servers

Article:TECH45684  |  Created: 2005-01-22  |  Updated: 2005-01-22  |  Article URL http://www.symantec.com/docs/TECH45684
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_60_1_M.winnt.IA64.exe provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.0 on Windows XP/2003 64-bit Clients and Servers

Solution



NB 6.0GA Pack NB_60_1_M README December 22, 2005
================================================================================
This Maintenance Pack provides fixes to the VERITAS NetBackup (tm)
Windows 64-bit server and clients.

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_60_1_M

Pack History
None


=========================
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_60_1_M.winnt.IA64_<6 digit number>.exe file into a
temporary directory.

where <6 digit number> is an internal tracking identifier

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

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


================
II. KNOWN ISSUES
=================
If you have the following libraries in your configuration, the mapping file will
be copied over during pack install, however, NetBackup will not automatically
recognize the device mapping information in the mapping file.

- Quantum DLT4500
- Sony TSL-A300 or Sony TSL-A500 Auto-loader

To achieve the correct library functionality, perform the following steps to
update the EMM database tables.

1) Run VERITAS\volmgr\bin\tpext on only the master server.

2) You must bounce ltid on all master/media and media servers.
(It is not necessary to bounce ltid on a master server if it is not also
a media server.)

a) Run VERITAS\volmgr\bin\stopltid.
b) Run VERITAS\volmgr\bin\bpps -s.
c) Verify that there are no media manager daemons running except vmd by
visually checking the bpps output.
d) After verifying that vmd is the only process running from Step c, run:
VERITAS\volmgr\bin\ltid.

NetBackup will now use these libraries correctly.



===============================
III. INSTALLATION INSTRUCTIONS
===============================
NOTE: Symantec recommends that you perform a catalog backup before and after
you apply this maintenance pack.

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 nodes of the cluster where the
NetBackup group is inactive. (follow steps 1-4 below)

2) Install this Maintenance Pack on the active node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.

CAUTION:
Do not failover the NetBackup Group until all NetBackup nodes (including
the active NetBackup node) have the Maintenance Pack installed.

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

Installation steps:

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 using 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>\NetBackup Install.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.

NOTE: Symantec recommends that you perform a catalog backup after you have
applied this maintenance pack.


===========================
IV. UNINSTALL INSTRUCTIONS
===========================
To uninstall the Maintenance Pack from a Windows CLUSTER Environment:

1) Uninstall this Maintenance Pack from the nodes of the cluster where the
NetBackup group is inactive. (follow steps 1-2 below)

2) Uninstall this Maintenance Pack from the active NetBackup node.
This should be done when the NetBackup system is quiet, for example,
no backups or restores running.

CAUTION:
Do not failover the NetBackup Group until all NetBackup nodes (including
the active NetBackup node) have the Maintenance Pack uninstalled.

**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
Control Panel -> Services tool. Repeat this until all databases have been
stopped. These services must be restarted once the patch is successfully
uninstalled.

2) Go to Add/Remove programs dialog box and select the 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 = ET421953

Description:
An issue in bpdbm caused the cleanup process to halt on Windows platforms
and prevented jobs from running.
--------------------------------------------------------------------------------
Etrack Incident = ET415495

Description:
Do not allow a down/disabled media server to block the entire Device
Allocator (DA) thread pool.
--------------------------------------------------------------------------------
Etrack Incident = ET423713

Description:
There were a few places in the code where the image query protocol version
was set to 0, which is a pre-NetBackup 5.0 image version ID. Some image
queries would fail if the size of the total data being backed up was larger
than 2TB in one job.

This issue has been corrected enabling image queries on backups greater
than 2TB work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET424051

** 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 = ET423045

Description:
When sharing tape drives between media servers that were running both
NetBackup 6.0 and NetBackup 5.x, a problem existed with the NetBackup 6.0
Scan Hosts. If the drive being scanned was assigned to a 5.x media server,
the 6.0 Scan Host might not stop scanning. This resulted in SCSI
reservation conflicts and DOWN'ed drives on the NetBackup 5.x assigned host.

Workaround:
To avoid this issue, do not share drives between media servers running
different versions of NetBackup. Instead, pool your drives such that all
of your NetBackup 5.x media servers are sharing one pool of drives and all
of your NetBackup 6.0 media servers are sharing a pool of different drives.
--------------------------------------------------------------------------------
Etrack Incident = ET422837

Description:
When running multi-streamed Windows Open File Backup backups to back up
open and/or active files, some VSP cache files in the format of
_vxfiVspCacheFile_1.VSP, for example, may have been left behind by the
backup jobs that had already completed. This did not occur with
non-streamed backup jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET428719

Description:
Because of a logic error in the handling of "bptm �delete_all_expired",
the expired media was not getting deleted. This would prevent recycling
of the media.

Workaround:
To avoid this issue, the user can expire the media using bpexpdate.
--------------------------------------------------------------------------------
Etrack Incident = ET429008

Description:
When upgrading from NetBackup 5.x to NetBackup 6.0, the
NETBACKUP_RELATIONAL_DATABASE_FILES directive was not added to the list of
files included in cold catalog backup. The command, bpsyncinfo -add_paths,
"NETBACKUP_RELATIONAL_DATABASE_FILES" is run automatically during patch
installation to add this directive to the cold catalog backup configuration.
--------------------------------------------------------------------------------
Etrack Incident = ET421370

Description:
The NBDB database recovery (for Enterprise Media Manager (EMM) and Bare
Metal Restore (BMR)) will fail if the master server has a newer catalog
backup image than the one used in disaster recovery (DR). On Windows
platforms, it logged an error message in the progress log and displayed an
error message box. On UNIX platforms, because of a defect in the Java
user interface, it reported an error message in the log and all of the
restore jobs appeared in the job monitor as being successful.

Additional Notes:
This maintenance pack enables a user to recover from an older catalog
backup even though a newer catalog backup image exists on the master
server.

Full catalog disaster recovering from an older catalog backup is a
�roll-back� operation that has the risk of data loss. Users should fully
understand the implications and use it with caution.
--------------------------------------------------------------------------------
Etrack Incident = ET421439

Description:
Manual backups would not start immediately if the NetBackup Policy
Exceution Manager (PEM) was started first
--------------------------------------------------------------------------------
Etrack Incident = ET431863

Description:
For a Hot Catalog Backup, the relational database (NBDB/Sybase ASA) backup
job treated a cumulative and differential incremental backup the same and
only included the transaction log in the backup. This can create problems
recovering the ASA database if the differential backup media created before
the last cumulative has expired. These differential backups contained the
transaction logs that were necessary to roll forward from the last full
backup.

Workaround:
To resolves this issue, the cumulative incremental backup is actually a
full backup for the ASA files.
--------------------------------------------------------------------------------
Etrack Incident = ET428760

Description:
The vmd process would dump core if the EMM service (nbemm) was not running.
--------------------------------------------------------------------------------
Etrack Incident = ET425765

Description:
The nbpushdata function failed when a pool name had a hyphen in the actual
pool name.
--------------------------------------------------------------------------------
Etrack Incident = ET492438

Description:
Data tapes are no longer treated as cleaning tapes and be FROZEN by
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET494547

Description:
Device monitor showed the same tape mounted in multiple drives. This tape
in this scenario was also assigned to a NetBackup 5.x media server.

Workaround:
To avoid this issue, do not share drives between NetBackup 6.0 media
servers and NetBackup 5.x media servers.
--------------------------------------------------------------------------------
Etrack Incident = ET492704

Description:
A Null Reference Exception is produced when creating a custom filter for
the Driver Detail table (Monitoring -> Drivers -> Details table).
--------------------------------------------------------------------------------
Etrack Incident = ET425186

Description:
Oracle backups no longer end prematurely with a status 25.
--------------------------------------------------------------------------------
Etrack Incident = ET495004

Description:
The nbpushdata function failed with the following messages in the
nbpushdata log file:

<4> get_host_info: CEMM_MACHINE_DISK_ACTIVE being set for <your_host>
<16> emmlib_UpdateHost: (0) UpdateMachine failed, emmError = 2007079,
nbError = 0
<16> get_host_info: (-) Translating
EMM_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) to 193 in
the media context
--------------------------------------------------------------------------------
Etrack Incident = ET418546

Description:
The NOM database server uses less CPU utilization over GA.
--------------------------------------------------------------------------------
Etrack Incident = ET495339

Description:
The Windows Open File Backup was not showing retries in the Activity
Monitor.
--------------------------------------------------------------------------------
Etrack Incident = ET495403 ET497074

Description:
For media with image expiration set to infinity, nbpushdata passed an
incorrect value for infinity to the EMM database. This resulted in the
media not being queried.

nbemmcmd -listmedia -mediaid <media_id> NBEMMCMD, Version:6.0(20050906)
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.

vmquery -m <media_id>
Could not query by media ID A00001 with debug: generic EMM SQL error (193)
--------------------------------------------------------------------------------
Etrack Incident = ET425768

Description:
An issue in nbpushdata caused the nbpushdata �remove function to fail.

Workaround:
To avoid this issue, drop the EMM data base and then recreate it.
--------------------------------------------------------------------------------
Etrack Incident = ET496010

Description:
Restores failed with the following errors in the job log and tar debug log:

job log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:46 (4753.053) data buffers out of sequence, expected number 404927,
received 404932

debug log:
22:16:27 (4753.046) data buffers out of sequence, expected number 157884,
received 157886
23:32:47 (4753.053) data buffers out of sequence, expected number 404927,
received 404932

This issue occurred because the HP 11.23 compiler optimized out references
to the shared memory control variables.
--------------------------------------------------------------------------------
Etrack Incident = ET425178

Description:
Data Lifecycle Manager consolidation jobs now complete successfully.
--------------------------------------------------------------------------------
Etrack Incident = ET497262

Description:
An error message was received when performing a DB2 roll-forward after
restore.

For example:
$ db2 rollforward db sample to end of logs and stop
SQL1268N Roll-forward recovery stopped due to error "28" while
retrieving log file "S0000001.LOG" for database "SAMPLE" on node "0".
--------------------------------------------------------------------------------
Etrack Incident = ET430806 ET419127

Description:
Changed bprd and the Policy Execution Manager (PEM) so that the bprd child
could terminate and not wait for the job exit status from PEM, unless
the -w flag was used on the request.
--------------------------------------------------------------------------------
Etrack Incident = ET493607

Description:
Could not inventory legacy TS8 libraries as TL8.
--------------------------------------------------------------------------------
Etrack Incident = ET497761

Description:
An extremely heavy load in the Device Allocator (DA) may cause EMM to crash.
--------------------------------------------------------------------------------
Etrack Incident = ET496437

Description:
Some vital logs were not displaying correctly. To be more specific, the
form that Log:DbLogMsg is being called in the emmserver source files was
incorrect whenever it was multi-lined in the code. As a result, only part
of the log message survived and important log information was lost.
--------------------------------------------------------------------------------
Etrack Incident = ET431175

Description:
None
--------------------------------------------------------------------------------
Etrack Incident = ET496608

Description:
Non-robotic tape drives that contain unlabelled media will no longer be
automatically assigned to non-robotic media specific mount requests.
--------------------------------------------------------------------------------
Etrack Incident = ET498523

** 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 two or more active copies.
- Multiplexing was enabled with two or more active backups.
- The schedule configuration had the "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 an "end of media", so
a new media was needed for this copy. In addition, there was a problem
of 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.

--------------------------------------------------------------------------------
Etrack Incident = ET419262

Description:
The ability to browse for backup objects failed in Localized environments.
--------------------------------------------------------------------------------
Etrack Incident = ET423206

Description:
The back-level media server V_QUERY_CLEAN_BYROBNUM request caused an SQL
error.
--------------------------------------------------------------------------------
Etrack Incident = ET492763

Description:
Users can now backup SAP files on Windows that contain multi-byte
characters in the file path and file name.
--------------------------------------------------------------------------------
Etrack Incident = ET424796

Description:
NetBackup Job Manager (NBJM) deadlocks or halts when the connection to
bpbrm breaks in the middle of a backup job.
--------------------------------------------------------------------------------
Etrack Incident = ET431510

Description:
On initial install the Policy Execution Manager failed to start the first
time because no IOR file existed for nbproxy. Once an IOR file existed
and it is not empty, then the NetBackup Service Monitor was able to restart
the Policy Execution Manager.

Workaround:
To avoid this issue, delete the IOR files listed below before starting the
Policy Execution Manager.

On UNIX:
/usr/openv/var/nbproxy_pem.ior
/usr/openv/var/nbproxy_pem_email.ior

On Windows:
VERITAS\NetBackup\var\nbproxy_pem.ior
VERITAS\NetBackup\var\nbproxy_pem_email.ior
--------------------------------------------------------------------------------
Etrack Incident = ET425564

Description:
The Policy Execution Manager would crash after submitting a user-directed
or manual backup.
--------------------------------------------------------------------------------
Etrack Incident = ET495088

Description:
After the file copy portion of Windows XP setup was completed, an error
message similar to the following would occur:

�Setup cannot set the required Windows XP configuration information.
This indicates an internal setup error. Contact...�
--------------------------------------------------------------------------------
Etrack Incident = ET499610

** Description: **
Synthetic backup had potential data loss issues in following cases:
- The last full/synthetic or full expired/deleted occurred,
followed by one or more incrementals and a synthetic backup.
- The last incremental/full backup catalog was compressed before
next incremental backup took place.
- The TIR records in the last incremental backup are missing for
various reasons.
--------------------------------------------------------------------------------
Etrack Incident = ET414648

Description:
Oracle backups would fail because bphdb.exe quit with an Application Error.
This problem was encountered when using the following agents :

- ORACLE
- SAP
- SYBASE
- DB2
--------------------------------------------------------------------------------
Etrack Incident = ET497784

Description:
After a BareMetalRestore restore, the MSSQL Server Image path could be
incorrect.

Additional Notes:
Added message #70 in the following file:

bmrsavecfg.xml:BMRSAVECFG_ERROR_SAVING_SQL_IMAGE_PATH
--------------------------------------------------------------------------------
Etrack Incident = ET505873

Description:
Media servers sharing drives on versions of NetBackup older than
NetBackup 6.0 will receive host_not_registered errors when attempting to
determine if another media server is unavailable.
--------------------------------------------------------------------------------
Etrack Incident = ET424615

Description:
Thread handles were not being destroyed even after the threads have exited.
- To correct this issue, and array of threads is created and maintained.
Then before adding any new thread details to this list a check is made
of the existing threads that have completely processing. If the check
competes it cleans up the resources used for the same threads and then
adds the details for the newly created thread into the list of threads.

- At the time of exit, it cleans up all the thread handles irrespective of
whether they are currently executing or not.
--------------------------------------------------------------------------------
Etrack Incident = ET506551 ET499474 ET506690

Description:
This entry resolves three seperate issues described in the following list:
- Under certain conditions backups would not schedule. This happened
because of a problem in computing the next time a job was due. Windows
were not processed correctly if a backup should have run in a previous
window if the next window opened or closed at a different time.

- Advanced client VSS snapshot backup no longer causes an 805 error to
occur.

- The scheduler always executes Full backups, even for incrementals, if the
BMR option is on. nbpem would use the wrong criteria for the last
backup query made for a parent job that did not have multiple data
streams enabled. The result was no last full backup being found, so a
full would be run instead of an incremental.
--------------------------------------------------------------------------------
Etrack Incident = ET496102

Description:
As the number of VxUL log files grew, the start-up performance of bprd
would degrade.

Workaround:
To avoid this issue, delete the log files on a regular basis.
--------------------------------------------------------------------------------
Etrack Incident = ET506045

Description:
nbpushdata was using emmlib_DeleteHost to remove the NDMP host when the
following error occurred in the nbemm log. The following is a portion of
the log associated with the delete. Although log-level 6 was used, it
appeared that some log messages were missing.

11/11/05 15:54:41.185 [Debug] NB 51216 nbemm 111 PID:13393 TID:1196157872
[No context] 1 [DbConnection::Execute] SQL - retval=2007085(2007085)
retdal=-1native=<-143> sqlerror=<[Sybase][ODBC Driver][Adaptive Server
Anywhere]Column 'FQMachineName' not found> sqlstate=<42S22>
--------------------------------------------------------------------------------
Etrack Incident = ET507645

Description:
In certain cases, when NetBackup Access Control is enabled, long-lived
processes such as nbemm, nbpem, nbjm, nbrb, nbproxy, nbsl and vmd would
leak memory.
--------------------------------------------------------------------------------
Etrack Incident = ET500433

Description:
Restoring a partial database image (or a partial differential image) fails
with the following error message:

''Filegroup '' cannot be restored because it does not exist in the backup
set.''

In addition, the property sheet for a partial backup image did not display
the list of file groups contained in the partial backup.
--------------------------------------------------------------------------------
Etrack Incident = ET500006

Description:
The Policy Execution Manager VxUL message catalog was missing some messages
causing it to crash when trying to log the new messages.
--------------------------------------------------------------------------------
Etrack Incident = ET500061

Description:
SQL SERVER backup completes normally but the client interface Displayed
a -1 status. This was caused by improper progress log updates.
--------------------------------------------------------------------------------
Etrack Incident = ET509509

Description:
When spanning media, jobs occasionally appeared to be hung and the request
was continually failing with the message, "ROBOTIC LIBRARY IS DOWN ON
SERVER". This would happen after an earlier failure causing the message,
"MEDIA SERVER IS CURRENTLY NOT CONNECTED TO MASTER SERVER". However, the
media server properly showed the robot as up and the host as ACTIVE or
ACTIVE-TAPE.
--------------------------------------------------------------------------------
Etrack Incident = ET509427

Description:
A function that CPtrArray::GetCount() was used with was incompatible with
the Windows 64-bit Environment. Code changes have been made to use the
alternate function CPtrArray::GetSize().
--------------------------------------------------------------------------------
Etrack Incident = ET509293

Description:
The NetBackup Service Layer (NBSL) occasionally sent negative values for
freespace and totalcapacity of a storage unit (if the values are greater
than 2^32-1).
--------------------------------------------------------------------------------
Etrack Incident = ET506726

Description:
After applying the MS05-051 security patch, clients restored using BMR
would experience a problem with Active Directory.

Workaround:
To avoid this issue, fix the permissions for the WINDOWS\Registration
directory and its files.
--------------------------------------------------------------------------------
Etrack Incident = ET508191

Description:
vmd now retries the connection to EMM forever, instead of shutting down
if it cannot connect to EMM.
--------------------------------------------------------------------------------
Etrack Incident = ET507275

Description:
When performing a restore, the security permissions on the
%WINDIR%\Registration directory were not the same as they were at the
time of the backup.
--------------------------------------------------------------------------------
Etrack Incident = ET511728

Description:
From the NOM user interface, it is not possible to start the service/deamon
when NetBackup is on a UNIX Operating System.
--------------------------------------------------------------------------------
Etrack Incident = ET512560

Description:
It is now be possible for SAN media servers to be used as write hosts for
duplicate jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET510335

Description:
VxUL queries were failing on AIX platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET510255

Description:
Appending parentheses in the NOM filtering criteria is no longer an issue.
--------------------------------------------------------------------------------
Etrack Incident = ET510415

Description:
New DRIVE and ROBOT Reports have now been created along with multiple
entries for some column names.
--------------------------------------------------------------------------------
Etrack Incident = ET512866

Description:
Removed change events for Error LogMonitoring. For example, error log
collection functionality is removed. In addition, the getLogMessages()
idle method supports the error log source too; thus, NOM will call this
method for getting error logs. Finally, the getEventChannel()
functionality has been removed, resulting in an AFException.


Additional Notes:
Because of this fix, log monitoring of NOM 6.0 MP1 will only work with
NetBackup 6.0 MP1.
--------------------------------------------------------------------------------
Etrack Incident = ET513093

Description:
vmscd no longer dumps core. This occurred because vmscd received an invalid
drive type for one of the drives while polling the drive status and vmscd
was not handling the invalid drive type properly.
--------------------------------------------------------------------------------
Etrack Incident = ET513390

Description:
The NetBackup Notification Service (NBNos) was running in single-threaded
mode.
--------------------------------------------------------------------------------
Etrack Incident = ET516440

Description:
nbemm no longer core dumps on a clustered master server.
--------------------------------------------------------------------------------
Etrack Incident = ET516103

Description:
Vault can fail while logging very long strings.

Workaround:
Disable Vault logging.
--------------------------------------------------------------------------------
Etrack Incident = ET515838

Description:
When the parent job (nbgenjob) performed stream discovery and it received
an exception asking for policy information through nbproxy, it would then
perform several retries. On the first retry attempt the parent job would
core dump.
--------------------------------------------------------------------------------
Etrack Incident = ET429245

Description:
On HP-UX platforms, scheduled backups with file lists that contain
multi-byte characters failed with an error 71 (None of the files in the
files list exist). On the Activity Monitor, the multi-byte characters
were unreadable in the file lists within job properties.

Workaround:
To prevent this issue, please apply the following patches:

- HP-UX 11.00
Patch Name: PHCO_29903
Patch Description: s700_800 11.11 iconv cumulative patch
- HP-UX 11.11.
Patch Name: PHCO_29924
Patch Description: s700_800 11.00 iconv cumulative patch
--------------------------------------------------------------------------------
Etrack Incident = ET514039

Description:
When running backups with VSP enabled for open file backups, the client
machine would intermittently lock up and become unresponsive during a
backup. To avoid this issue, the user must reboot of the machine.
--------------------------------------------------------------------------------
Etrack Incident = ET514603

Description:
Change made to bpexpdate such that media IDs that are less than six
characters returned from EMM were not padded with spaces. This caused
bpexpdate -deassignempty to mistakenly deassign media that still had
valid images on them.

Workaround:
To avoid this issue, turn off the automatic start of
bpexpdate -deassignempty by performing one of the following items:

- On a UNIX master servers, create the file,
/usr/openv/netbackup/bin/bpsched.d/CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.

- On a Windows master server, create the file,
<install_path>\NetBackup\bin\bpsched.d\CHECK_EXPIRED_MEDIA_INTERVAL,
and enter a 0 (zero) on the first and only line of the file.
--------------------------------------------------------------------------------
Etrack Incident = ET514622

** Description: **
An NBSL core dump happened while stopping it when it was connected to a
client (NOM). The core dump would occur on Solaris and AIX platforms.
On Windows platforms, it would hang in a 'stopping' state in the Windows
Service Manager.
--------------------------------------------------------------------------------
Etrack Incident = ET515553 ET515559

Description:
vmscd, before the fix, was a single process and it used to service
requests from the EMM server synchronously. Because of this, the EMM server
was not receiving the request response in a timely manner. In some cases,
the EMM server would think that vmscd had exited and which then triggered
certain operations that were redundant, and in some, cases harmful.
--------------------------------------------------------------------------------
Etrack Incident = ET511340

Description:
Several issues have been fixed that related to back-level SSO
interoperability:

- Numerous re-registrations were consuming all of vmd's bandwidth on
the EMM server.

- Registration failures due to no scan host setting registration retry
timer which would block back-level servers from releasing drives.

- Back-level remote scanning of NetBackup 6.0 media servers was failing
with ENOTSCANHOST and forcing still more re-registrations.

Workaround:
To avoid these issues, do not share drives between NetBackup 6.0 and
NetBackup 5.X media servers.
================================================================================

============
Pack History
============

Nothing to report for this release.



Attachments

NB_60_1_M_281105.winnt.IA64.exe (55 MBytes)


Legacy ID



281105


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


Terms of use for this information are found in Legal Notices