NetBackup Enterprise Server 6.5.3 Release Update Readmes This document provides the entire list of ETracks and Titan Cases associated with the NetBackup Enterprise Server 6.5.3 Release Update. Each Readme is contained in this document. Use “Ctrl + F” to easily find any ETrack or Titan Case #. Use the links in the Table of Contents to go to a certain Readme: Table of Contents:

1. Windows Servers 2. UNIX Servers 3. NetBackup Operations Manager (Windows and UNIX) 4. Java: Windows and UNIX 5. Bare Metal Boot Server (BBS) and Bare Metal Restore (BMR) 6. DB2 Database Agent 7. Informix Database Agent 8. Lotus Notes Database Agent 9. SAP Database Agent 10. NetBackup LiveUpdate Agent 11. NetBackup Snapshot Client 12. Data Management Protocol (NDMP) 13. Storage Migrator 14. Vault

If an Agent or Option is not listed above, it’s likely that there was not a package update for them at this time. =========================================================================

Windows Servers

========================================================================= Etrack Incident = ET1383512 Associated Primary Etrack = ET1290612 Titan cases: 230-315-701 Description: An error would occur during a large size FS freeze for a VxFS shadowimage snapshot. A FS flush timeout was added in the conf file to facilitate a timeout parameter for FS large in size that is greater than or equal to 10TB. -------------------------------------------------------------------------------- Etrack Incident = ET1250743 Associated Primary Etrack = ET1227093 Titan cases: 230-515-323 240-709-547 281-328-393 281-329-9201 281-332-028 290-974-157 290-974-378 311-836-533 Description: A "Check WINBOM" error for the NC373i adapter would occur while using an ISO image that was created from WinPE-based shared resource tree (SRT). -------------------------------------------------------------------------------- Etrack Incident = ET1275559 Description: A bpdbm core dump would occur because of a badly formatted ovgetmsg routine. A change was made to address this issue.

-------------------------------------------------------------------------------- Etrack Incident = ET1289330 Description: Changes have been added to ensure that the BMR database levels match those of the NetBackup server. -------------------------------------------------------------------------------- Etrack Incident = ET1302929 Description: A change was added to fix memory leaks discovered in the bpplsched command line and nbproxy which use common free routines. The cause of the problem was that the command line would mix results from different queries. The c_receive_flag determines if the contents of a structure are freed and if queries are mixed like this, the value may not be the same. -------------------------------------------------------------------------------- Etrack Incident = ET1282107 Associated Primary Etrack = ET1221889 Titan cases: 311-836-533 Description: An issue would occur after a BMR restore operation completed on a Windows system that had Broadcom NetExtreme II NIC hardware and NIC teaming software installed and configured. After the BMR restore completed and during the BMR clean-up phase (while installing Broadcom NetXII NIC drivers), BMR would cause an error message to appear stating that it failed to install the NIC drivers. However, the drivers were actually installed correctly. This message appeared ONLY when the backed-up system had NIC teaming software installed and configured. Workaround: If you encounter this issue, please click, OK, for the pop-up error messages that may appear and let the BMR clean-up continue with the other tasks. -------------------------------------------------------------------------------- Etrack Incident = ET1302749 Associated Primary Etrack = ET1300264 Titan cases: 220-369-133 311-946-518 320-117-267 320-122-713 Description: User backups with windows configured to be 24x7, would fail at midnight with a status code 196. -------------------------------------------------------------------------------- Etrack Incident = ET1317013 Associated Primary Etrack = ET1292141 Titan cases: 220-319-568 240-781-624 311-955-023 Description: Backups would fail with a status code 230 when using the en_GB.ISO8859 locale. -------------------------------------------------------------------------------- Etrack Incident = ET1317008 Associated Primary Etrack = ET1295547 Titan cases: 230-554-457

Description: The policy execution manager (nbpem) would core dump after restarting a job that had been running before the upgrade to NetBackup 6.5.2. -------------------------------------------------------------------------------- Etrack Incident = ET1317006 Associated Primary Etrack = ET1297993 Titan cases: 291-011-673 Description: The policy execution manager (nbpem) would exit with an ASSERT failed error that indicated m_due was less than or equal to m_startTime. -------------------------------------------------------------------------------- Etrack Incident = ET1317202 Associated Primary Etrack = ET1269997 Titan cases: 320-107-578 Description: Resource requests for bpduplicate (vault) were failing because of a missing parameter. The Vault duplications would fail with a status 800. Workaround: This would only occur when duplicating to storage units on pre-NetBackup 6.5 media servers where the master server is at 6.5 or later. The workaround would be to not target storage units on pre 6.5 media servers when duplicating. It also will not be an issue for single-image duplications. -------------------------------------------------------------------------------- Etrack Incident = ET1317047 Associated Primary Etrack = ET1293461 Titan cases: 240790925 281375544 290011922 291-010-092 Description: The Client Attribute "Maximum Data Streams" was being ignored with NetBackup 6.5.2 and the global value "Maximum jobs per client" was always taking precedence irrespective if the setting was higher or lower. -------------------------------------------------------------------------------- Etrack Incident = ET1276489 Description: The bpexpdate -deassignempty command was failing to expire media on NDMP hosts. -------------------------------------------------------------------------------- Etrack Incident = ET1318091 Associated Primary Etrack = ET1295660 Titan cases: 311-944-025 Description: On Windows master servers, the online catalog backup was failing with a status of 2 for the parent job and 42 for one of the child jobs when non-multi-streamed policies were configured as critical policies in the catalog backup policy. Workaround: If you encounter this issue, remove critical policies from the online catalog backup policy.

-------------------------------------------------------------------------------- Etrack Incident = ET1318437 Associated Primary Etrack = ET1301899 Titan cases: 240-788-962 Description: Lotus Notes databases that were larger than 2GB would be treated as links and skipped from the backup. -------------------------------------------------------------------------------- Etrack Incident = ET1289921 Description: If backup jobs and synthetic/duplicate jobs were in progress simultaneously, some of the drives would become unusable. Workaround: If you encounter this issue, find the unusable drive and release it using the nbrbutil utility. -------------------------------------------------------------------------------- Etrack Incident = ET1319500 Description: The End-user License Agreement (EULA) has been updated for NetBackup 6.5.3. -------------------------------------------------------------------------------- Etrack Incident = ET1322984 Description: A change was made to address a bpbdm core dump issue that occurred when the client list was being freed when user interface executed a Q_IMAGE_HWOS_GET query and the get_hwos() would perform a double free of the client list. -------------------------------------------------------------------------------- Etrack Incident = ET1361367 Associated Primary Etrack = ET1320882 Titan cases: 291-014-078 Description: A change was made to ensure that an Exchange DB restore can be performed with a Windows 2008 cluster. -------------------------------------------------------------------------------- Etrack Incident = ET1364407 Description: When a policies schedule was changed the retention level was not correct when modified to a value other than the default value. -------------------------------------------------------------------------------- Etrack Incident = ET1364422 Description: Synthetic Backup jobs would fail with a status 1 and were retried repeatedly. -------------------------------------------------------------------------------- Etrack Incident = ET1322803 Associated Primary Etrack = ET1266944 Titan cases: 281-351-695

Description: If media servers or other hosts not in the server list attempted to connect to a master, the connection would be rightly rejected. However, the diagnostic-logging-level 2 logging message itself used a non-threadsafe function that would cause memory corruption if threads collided. This would lead to crashes or erratic behavior for services such as EMM and PEM. Workaround: Search for "allow_peer" messages in the logs and reconfigure or decommision all of the servers that are logged as "not allowing connection". These servers are not in the master's server list, which triggers the log message. If the diagnostic logging level is set to not log Level 2 messages, the problem is averted. -------------------------------------------------------------------------------- Etrack Incident = ET1364661 Description: A change was made to to correct an issue that caused NBPEM to crash during an upgrade from NetBackup 6.5 to 6.5.3. The crash would happen in a clustered environment when nbpem was shutdown. -------------------------------------------------------------------------------- Etrack Incident = ET1373019 Description: All DSSU schedules were deleted (from PEM point of view) upon updating one DSSU schedule. -------------------------------------------------------------------------------- Etrack Incident = ET1383374 Associated Primary Etrack = ET1300103 Titan cases: 320-117-348 Description: bprd would core dump under certain circumstances when there was an invalid media server in the server list and the configuration was being updated. -------------------------------------------------------------------------------- Etrack Incident = ET1382658 Titan cases: 220-327-515 Description: If the VNET_OPTIONS entry was defined in your configuration (bp.conf on UNIX or the Registry on Windows) and if some values in the entry were zero, problems would occur if you attempted to upgrade to NetBackup 6.5.2 or later. An example entry would be: VNET_OPTIONS = 120 3600 0 0 0 0 0 0 0 If you attempt to run with this entry in NetBackup 6.5.2 or later, networking will not work on your machine. Workaround: If you encounter this issue, remove the VNET_OPTIONS entry from your configuration before you upgrade, or replace the 0-values in the entry with the NetBackup 6.5.2 defaults before upgrading.

For example: VNET_OPTIONS = 120 3600 200 40 3 1 30 0 0 0 -------------------------------------------------------------------------------- Etrack Incident = ET1383586 Associated Primary Etrack = ET1295782 Description: For SharedDisk volumes, the unmount event triggers a clean up of all the committed space allocated for the backup. If the unmount event is missed, the volume may appear over-committed and may not get picked for future backups. As a results, MDS would not find any available Shared Disk volumes and backups in a pure Shared Disk environment would queue indefinitely. -------------------------------------------------------------------------------- Etrack Incident = ET1383582 Associated Primary Etrack = ET1377498 Titan cases: 230-581-012 291-068-284 Description: Optimized duplication would ignore the retention level sent for a destination copy and would set the expiration time and retention using values from the source copy. -------------------------------------------------------------------------------- Etrack Incident = ET1383584 Description: An issue existed that caused jobs to fail with a status 16: unimplemented feature error. -------------------------------------------------------------------------------- Etrack Incident = ET1184889 Titan cases: 220-111-009 Description: Cache results of server list comparisons for CORBA communications. The cache is intended to improve performance for configurations with a large number of hosts in the server list. -------------------------------------------------------------------------------- Etrack Incident = ET1276613 Associated Primary Etrack = ET1135854 Titan cases: 281-213-065 Description: During long running back up jobs, the firewall between the master and media server will close connection if it is configured to do so. This causes a break in communication between the master and media server and a failure of backups. Workaround: If you encounter this issue, disable the firewall timeout. However, this may be detrimental to firewall security. -------------------------------------------------------------------------------- Etrack Incident = ET1382632 Associated Primary Etrack = ET1238838 Titan cases: 311-880-802 Description:

A NetBackup service such as nbjm would sometimes abort, leaving a core dump. A change has been made to correct this issue. -------------------------------------------------------------------------------- Etrack Incident = ET1383839 Titan cases: 220-337-212 Description: On some AIX systems, it was discovered that ltid would not start. The stdout error is "Unable to get external file version from EMM database". The logs show the following CORBA error: "Msg exceeds maximum allowed size". Workaround: You can avoid this issue by setting LANG=C in the shell before starting ltid. You an also change the system default by editing /etc/environment. -------------------------------------------------------------------------------- Etrack Incident = ET1383438 Associated Primary Etrack = ET1322123 Titan cases: 240-776-132 Description: A change was made to improve the parsing of the Job Try file in nbproxy because it would take a long time. -------------------------------------------------------------------------------- Etrack Incident = ET1383429 Associated Primary Etrack = ET1323221 Titan cases: 311-963-863 Description: The NetBackup Service Layer (NBSL) would core dump when NOM had data collection enabled. -------------------------------------------------------------------------------- Etrack Incident = ET1383440 Associated Primary Etrack = ET1269781 Titan cases: 290-988-768 Description: The NetBackup Service Layer (NBSL) would core dump under a load from NOM data queries: NBPolicyCollector::Collect. -------------------------------------------------------------------------------- Etrack Incident = ET1383434 Associated Primary Etrack = ET1234532 Titan cases: 220-236-821 Description: When you stop the services from the NetBackup Administration Console, the services would go away and you could not restart them from user interface. -------------------------------------------------------------------------------- Etrack Incident = ET1383258 Associated Primary Etrack = ET1282306 Titan cases: 220-248-543 Description: Vault's eject mode suspend immediately would fail to suspend media if duplication was disabled. A fix was added to ensure that, media are

suspended if the mode "suspend now" is chosen. -------------------------------------------------------------------------------- Etrack Incident = ET1383442 Associated Primary Etrack = ET1281452 Titan cases: 230-535-095 Description: After running activate and deactivate policies in NOM the NetBackup-Java Adimistration Console was unable to read policies. -------------------------------------------------------------------------------- Etrack Incident = ET1383733 Associated Primary Etrack = ET1372893 Description: If NetBackup services are restarted when jobs using shared disk are active, the NetBack Resource Broker (nbrb) may not be able to de-allocate resources properly on a restart. nbrb unmounts the shared disks correctly but fails to inform MDS to de-allocate the resources. Workaround: If you encounter this issue, re-start the services, then wait between 5 and 10 minutes, and then run "nbrbutil -resetall" if no jobs are active. This will de-allocate the resources. If the jobs are active, you should wait for the jobs to finish before you run nbrbutil -resetall. -------------------------------------------------------------------------------- Etrack Incident = ET1384031 Description: NDMP backup fails with a status 114 error. The ndmpagent log shows the following message. "Expected remainder to be 0. Remainder = 512" Workaround: If you encounter this issue, set the SIZE_DATA_BUFFERS parameter to 256k. (There is still a possibility the backup could fail, but it is unlikely.) Or you can run NDMP local, NDMP 3-way, or NDMP remote to disk. -------------------------------------------------------------------------------- Etrack Incident = ET1383750 Associated Primary Etrack = ET1361178 Titan cases: 220-349-593 320-132-770 Description: If the MDS allocations were removed directly either using the nbrbutil -releaseMDS command or by deleting the record from database, the NetBackup Resource Broker (nbrb) would not be able to remove the corresponding allocation records from its database. This would cause the resource broker's drive cache to misbehave, for example, jobs may not get the resources even when the drives were available, and perform other redundant operations which consumes CPU cycles. -------------------------------------------------------------------------------- Etrack Incident = ET1383540 Associated Primary Etrack = ET1296912 Titan cases: 220-325-975 281-378-560 Description: A change has been made to address an issue that would cause a multiple

copy, Oracle database backup to fail in some situations. -------------------------------------------------------------------------------- Etrack Incident = ET1382528 ET1384897 Associated Primary Etrack = ET1375580 ET1384850 Titan cases: 291-019-528 220-375-654 Description: The bpresolver code did not resolve the Web Application name properly if it had more than one set of parenthesis in the SharePoint resource name. The SharePoint-managed dll "SPSWrapperManagedHelper.dll", required a change to allow double quotes to prefix and suffix a Shared Service Provider with special characters. In addition, the SharePoint 2007 document-level restore problem occurred when the web application name had a parenthesis embedded. -------------------------------------------------------------------------------- Etrack Incident = ET1384026 Associated Primary Etrack = ET1371963 Titan cases: 320-123-885 Description: NetBackup 6.5.x SQL MPX (multiplexed) restores would hang when the number of restore stripes was 1. When restoring a multi-stripe backup with fewer streams than specified during the backup, the restore would hang. This issue occurred if NUMBUFS was greater than 1 in the NB-MSSQL batch file. Workaround: If you should encounter this issue, set NUMBUFS to 1 NB-MSSQL batch file. This can be done in BATCHFILE or by selecting the number of buffers as 1 in the Client Options dialog box of the NB-MSSQL user interface. -------------------------------------------------------------------------------- Etrack Incident = ET1375483 Description: A change was made to correct a timing issue that bpduplicate would encounter when it tried to get the job priority from bpjobd, which would sometimes take longer than expected. -------------------------------------------------------------------------------- Etrack Incident = ET1383736 Associated Primary Etrack = ET1278280 Titan cases: 320-111-786 Description: The nbemmcmd -renamehost command would not update the hostname that the DA_Thread_Pool uses for the heartbeat check. Workaround: If you encounter this type of issue, rename a host with the nbemmcmd -renamehost command and then stop and start nbemm. -------------------------------------------------------------------------------- Etrack Incident = ET1382523 Associated Primary Etrack = ET1316871 Titan cases: 281-377-492

Description: The SharePoint documents would not display from the document-level backup image. -------------------------------------------------------------------------------- Etrack Incident = ET1383527 Titan cases: 222-222-222 Description: When applying a NetBackup server patch, a change was made so that local modifications to the server.conf file will not be lost. Workaround: To ensure any local modifications to the server.conf are not removed, add the following line to the vxdbms.conf file to turn off automatic server.conf updates: VXDBMS_SELF_TUNING=OFF -------------------------------------------------------------------------------- Etrack Incident = ET1383523 Associated Primary Etrack = ET1300087 Titan cases: 240758288 Description: The stale port connection on the media server was being terminated by the firewall. Workaround: If you encounter this issue, lengthen the firewall's timeout time or disable that feature for an approved IP address. -------------------------------------------------------------------------------- Etrack Incident = ET1384879 Description: The NetBackup Database Manager would core dump when trying to log a debug message while adding an image fragment. -------------------------------------------------------------------------------- Etrack Incident = ET1385083 ET1385111 ET1386294 Associated Primary Etrack = ET1278625 Description: On an extremely busy system, the bpdbm service could experience two intermittent problems: 1. The service could hang for 30 minutes after starting a Q_IMAGE_READ_FILES_FILE query, and eventually cause bpdbm to terminate with a status code 63. 2. A Q_IMAGE_READ_FILES_FILE query would be processed successfully by bpdbm, but the socket would be closed on Windows platforms in a manner that caused the bptm process that issued the query to fail with a Windows status code of 10054. -------------------------------------------------------------------------------- Etrack Incident = ET1383454 Description: The NetBackup Administration Console would crash when viewing the "Summary

of all policies" node while editing schedules. -------------------------------------------------------------------------------- Etrack Incident = ET1383425 Associated Primary Etrack = ET1274271 Titan cases: 220-288-516 Description: The Volume Pool Override within the Vault Catalog Backup schedule did not show the Hot Catalog pool names. -------------------------------------------------------------------------------- Etrack Incident = ET1383426 Associated Primary Etrack = ET1301364 Titan cases: 220-328-509 Description: When opening a Storage Life Cycle Policy, the volume pool would reset back to the NetBackup Pool after opening a change window. -------------------------------------------------------------------------------- Etrack Incident = ET1384677 Description: A change was made to address a core dump issue that would occur with the NBConsole.exe executable while closing the NetBackup Administration console. -------------------------------------------------------------------------------- Etrack Incident = ET1383556 Description: bpverify would fail to verify a valid image when validating a UNIX image on a Windows media server that had files containing non 7-bit ASCII characters. The message, "Filename length does not match for file xxxx, in image is yy, in database is zz." -------------------------------------------------------------------------------- Etrack Incident = ET1383757 Associated Primary Etrack = ET1316106 Titan cases: 320-117-413 Description: NetBackup Job Manager (nbjm) delays 90 minutes making thousands of JMUtility::updateParamsFileWOFB calls between receiving resources and starting bpbrm. This delay affected scheduled and user-directed backup jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1384675 Associated Primary Etrack = ET1318016 Titan cases: 240-790-104 Description: Restoring a backup taken with a storage unit that contains the application cluster virtual name would fail because NetBackup was unable to determine the NetBackup version of the application cluster name. -------------------------------------------------------------------------------- Etrack Incident = ET1385061 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048

Description: If the primary lifecycle policy was set to inactive for a long period of time (for example, four days) then reactivated, it was possible that a large number of images would need to be processed. In this scenario, nbstserv would use so much memory that a core dump would occur. -------------------------------------------------------------------------------- Etrack Incident = ET1383452 Description: VMWare Consolidated Backup (VCB) 1.5 added support for W2008 as a VMware proxy, however bpfis would force the snapshot type to VSS. A change was made to ensure that bpfis does not force the VSS selection for VMWare. -------------------------------------------------------------------------------- Etrack Incident = ET1382599 Description: The snapshot policy wizard would recommend the obsolete VSS_Transportable FIM. This has been corrected to recommend the VSS FIM, which can be used in local and offhost (Alternate Client) backup environments. -------------------------------------------------------------------------------- Etrack Incident = ET1382596 Description: A change was made to ensure that the Snapshot Client cleans up the temporary files when it is finished. -------------------------------------------------------------------------------- Etrack Incident = ET1384892 Associated Primary Etrack = ET1227409 Titan cases: 290925975 Description: Alternate path restores would fail when a directory name had a literal string " to " in it. (This string was comprised of a space, the word to, and another space). The example is, C:\all data to be stored here. -------------------------------------------------------------------------------- Etrack Incident = ET1376805 Description: The NetBackup Job Manager (NBJM) would crash on shutdown because expired snapshots taken during non-streamed windows open file backup (WOFB) jobs were deleted. -------------------------------------------------------------------------------- Etrack Incident = ET1382595 Description: A Windows Open File Backup (WOFB) policy that has multi-streaming enabled could give a misleading error message when the snapshot failed due to a full file system. This has been corrected. -------------------------------------------------------------------------------- Etrack Incident = ET1383782 Description: Synthetic schedules with a space specified in the keyword field would make the job fail. --------------------------------------------------------------------------------

Etrack Incident = ET1383498 Associated Primary Etrack = ET1288299 Titan cases: 291-004-832 Description: A change was made to ensure the correct UDID string formation for the EMC Clariion CX-3 series of array with a RAID 6 configuration and FLARE26. -------------------------------------------------------------------------------- Etrack Incident = ET1383466 Description: The Granular Proxy Host on the NetBackup Administration Console was missing the word, Restore. -------------------------------------------------------------------------------- Etrack Incident = ET1383497 Associated Primary Etrack = ET1262210 Titan cases: 281-343-506 Description: A change was made to resolve an issue in the V_string function that would cause bpfis to crash. -------------------------------------------------------------------------------- Etrack Incident = ET1386057 Associated Primary Etrack = ET1253903 Titan cases: 290-975-130 Description: A change was made to correct a bpdbm core dump issue found in the function, db_get_image_info() in strerror(). -------------------------------------------------------------------------------- Etrack Incident = ET1385764 Associated Primary Etrack = ET1265226 Titan cases: 240-757-443 Description: Vault would eject more copies of catalog tapes than what it was configured to do. If you used Vault to perform catalog backups, the associated catalog backup policy was configured to generate two copies, one copy in the catalog-pool and the other copy in the CatalogBackup pool. If your intention was to keep the copy in the catalog-pool in the robot and to offsite the copy in the CatalogBackup pool, you would add only the CatalogBackup pool in the offsite volume pool of profile eject configuration. When Vault ran, it listed both catalog copies in the eject.list and ejected both copies. However, the Robot Pick List report listed only the CatalogBackup copy, thus, it was not reporting all of the tapes that were being ejected. -------------------------------------------------------------------------------- Etrack Incident = ET1386060 Associated Primary Etrack = ET1281512 Titan cases: 311-821-936 Description:

Crosschecking Oracle images (Q_IMAGE_BY_FILE) would fail if the image list existed for the client. Workaround: Remove the index files. -------------------------------------------------------------------------------- Etrack Incident = ET1383811 ET1383808 ET1382683 Associated Primary Etrack = ET1244548 ET1241226 Titan cases: 230-521-343 311-880-025 290-934-270 Description: A change was added to address an issue that caused NetBackup Policy Execution Manager (nbpem) to shut down. -------------------------------------------------------------------------------- Etrack Incident = ET1386756 Associated Primary Etrack = ET1321650 Titan cases: 291-016-026 Description: The Application Backup setting did not select database backups in NetBackup 6.5. Vault profile has enabled attributes filters and an Application backup filter was added in Backup Type filters. Vault skips application backup images for any further operations (duplication/original eject). Workaround: If you encounter this issue, configure the profile to use Backup Types as "Include All" or include "User backup" along with "Application Backup". -------------------------------------------------------------------------------- Etrack Incident = ET1385614 Associated Primary Etrack = ET1323578 Titan cases: 291-026-442 Description: The Vault tape batching algorithm was incorrect and caused an inefficient duplication. In an environment where images reside on common media or span media and multiplexing or media sharing is enabled, Vault would create a batch with overlapping media sets. This caused some drives to be idle while waiting for a previous batch to free the common media. -------------------------------------------------------------------------------- Etrack Incident = ET1384822 Description: NBPEM would deadlock if restarted while jobs were in an INCOMPLETE state and new jobs were started for the same policy/client. -------------------------------------------------------------------------------- Etrack Incident = ET1386891 Description: Various changes have been added to this release in an effort to integrate NetBackup with VxMS 5.3. -------------------------------------------------------------------------------- Etrack Incident = ET1386064

Description: A change has been added to eliminate a potential vmd core dump issue when the EMM initialization failed. -------------------------------------------------------------------------------- Etrack Incident = ET1386062 Description: The required tape parameters for NetBackup were not being set correctly on multi-path drives on AIX platforms. Only the first path had extended files marks and variable block set correctly. -------------------------------------------------------------------------------- Etrack Incident = ET1386073 Description: Could not delete the virtual_machine machine type with the nbemmcmd command. -------------------------------------------------------------------------------- Etrack Incident = ET1383727 Description: Policy Execution Manager would schedule a disk staging policy to run when it should not. This happened because a policy event was not sent to the Policy Execution Manager when a disk staging schedule was added. -------------------------------------------------------------------------------- Etrack Incident = ET1384025 Associated Primary Etrack = ET1249855 Titan cases: 320-100-354 230-568-897 Description: A change was added to address a core dump issue that caused bpjobd to call t_delete whenever NOM was active. -------------------------------------------------------------------------------- Etrack Incident = ET1382622 Associated Primary Etrack = ET1267865 Titan cases: 290953949 Description: Restoring of Shadow Copy Component would fail to restore SYSVOl data. -------------------------------------------------------------------------------- Etrack Incident = ET1383766 Associated Primary Etrack = ET1369292 Titan cases: 320-121-094 Description: If a policy had a client named more than once with different aliases, the Policy Execution Manager (PEM) would start both even though only one was requested. If the backup was a user in which bprd supplies the jobid, it would use the same jobid for both jobs and would assert when trying to add it to the map. A fix was added to ensure that a client is not specified more than once in a policy by different names. -------------------------------------------------------------------------------- Etrack Incident = ET1386069 Associated Primary Etrack = ET1266200

Description: Running bpgetmedia would not return tapes from all robots. -------------------------------------------------------------------------------- Etrack Incident = ET1384960 Description: Calling changeMediaDBAllMediaForServer with NetBackup Access Control (NBAC) enabled would fail. -------------------------------------------------------------------------------- Etrack Incident = ET1382618 Associated Primary Etrack = ET1263128 Titan cases: 230-523-952 Description: A fix was added to address an issue that would not allow a backup to cross a Windows mount point. -------------------------------------------------------------------------------- Etrack Incident = ET1386075 Associated Primary Etrack = ET1366874 Titan cases: 240-724-837 Description: The performance of the API which lists shared drives and hosts would decreases significantly as the amount of hosts and drives increased. -------------------------------------------------------------------------------- Etrack Incident = ET1386077 Titan cases: 240-829-613 Description: An SQL error was received when attempting to delete a cluster. -------------------------------------------------------------------------------- Etrack Incident = ET1383472 Associated Primary Etrack = ET1367286 Titan cases: 290-986-519 291-010-917 291-015-278 311-845-915 311-859-951 311-914-478 311-933-903 320-088-477 Description: bmrsavecfg would fail for clients with HP EVA 4000/5000/6000/8000 array disks and as a result the configuration was not registered with the BMR database. -------------------------------------------------------------------------------- Etrack Incident = ET1383479 Associated Primary Etrack = ET1211323 Titan cases: 290-900-314 290-919-097 Description: When the BMR boot server is started it tries to register itself with BMR master server. If the BMR master server is down or the BMR database is not up it tries to register itself, it gets either a Network Failure error or a registration failed error. If registration is not successful then BMR boot server sends a registration request to the master server every 30 seconds. For each registration request the BMR boot server produces a memory leak and it decreases the performance in the machine.

Workaround: If you encounter this issue do one of the following: If the BMR master server daemon "bmrd" is down then shut down the BMR boot server daemon "bmrbd". OR If BMR database is not yet configured then run bmrsetupmaster on the command line interface (CLI) to configure the database and then re-start the bmrd and bmrbd daemons. -------------------------------------------------------------------------------- Etrack Incident = ET1385881 Associated Primary Etrack = ET1297511 Titan cases: 311-927-527 Description: When adding a driver package to a BMR-Windows Client's configuration, the operation takes a long time. While performing a Prepare To Restore (PTR) for a BMR client on such a setup, the PTR operation would also take a long time to complete. Additional Notes: The problems described above are due to some unnecessary redundancies in the BMR database. A fix has been added to make sure that no new unnecessary redundancies get added to the database, but it does not eliminate the existing, unnecessary redundancies from the BMR database. Please contact Symantec Support for help on removing the existing unnecessary redundancies. -------------------------------------------------------------------------------- Etrack Incident = ET1384019 Associated Primary Etrack = ET1273804 Titan cases: 281-334-212 Description: Setting the Media Mount timeout to a value other than 0 minutes can sometimes result in the Media Mount Timeout occurring even if the mount succeeds. A chance signal timing issue resolved this problem. -------------------------------------------------------------------------------- Etrack Incident = ET1386065 Description: When the initial try of an Exchange VSS snapshot parent job failed, the second try would fail with a status 801. -------------------------------------------------------------------------------- Etrack Incident = ET1384904 Description: This Release Update enables Microsoft SQL Server 2008 by allowing NetBackup-MSSQL to recognize the GA version of the SQL 2008 version string. -------------------------------------------------------------------------------- Etrack Incident = ET1386070 Description:

The bpmedialist command, when given parameters involving a particular media ID whose length is less than six characters, would fail. Workaround: If you should encounter this issue, execute the command with the volume name enclosed in double quotes and padded by spaces so that the length of the volume name is six characters. -------------------------------------------------------------------------------- Etrack Incident = ET1387046 Description: When attempting to run an Oracle backup on a Master server that is configured with the Required_Interface setting, bpdbsbora would fail to connect and the job failed with a status 29. This occurred because nbjm did not pass the "-ri <reqd interface>" option to the bpbrm command line by nbjm. The NetBackup Job Manager passed the new option only if the media server version was 6.5.2 or greater. Since nbrb is returning the media server version as 0, nbjm did not pass the new "-ri <reqd interface>" option. -------------------------------------------------------------------------------- Etrack Incident = ET1383743 Associated Primary Etrack = ET1318931 Titan cases: 220-337-034 Description: Implementing media_deassign_notify script resulted in <defunct> processes. Workaround: To resolve this issue, setIgnoreSigChild() was added to OrbService() to ensure that EMM does not leave <defunct> processes when children complete from NOTIFY script execution. -------------------------------------------------------------------------------- Etrack Incident = ET1384952 Associated Primary Etrack = ET1374144 Titan cases: 320-123-939 Description: Duplication of NDMP disk image to tape would fail with a status 191 error. -------------------------------------------------------------------------------- Etrack Incident = ET1387039 Description: Libraries that provide self-cleaning would sometimes cause normal media to be frozen if they self-clean very quickly after a normal media was unloaded. -------------------------------------------------------------------------------- Etrack Incident = ET1383643 Associated Primary Etrack = ET1321325 Titan cases: 281-358-993 Description: The following error would occur after an App_cluster was failed over. EMM status: Disk volume is down resource request failed(800) -------------------------------------------------------------------------------- Etrack Incident = ET1388132 Description:

Could not perform a restore from an incremental backup with DB2 v9.5 on an AIX platform. -------------------------------------------------------------------------------- Etrack Incident = ET1384946 Associated Primary Etrack = ET1361273 Titan cases: 320-121-830 Description: A change was made to address an nbjm core dump issue that occurred in BPCRConnector handleReferenceCnt. -------------------------------------------------------------------------------- Etrack Incident = ET1384943 Associated Primary Etrack = ET1316765 Titan cases: 220-338-008 Description: A change was made to address an nbjm core dump issue that occurred near JobState::endItemChange +1c0. -------------------------------------------------------------------------------- Etrack Incident = ET1388149 Description: The command line interface, nbdb_admin -validate, would not return the full result set on Windows platforms. Workaround: If you should encounter this issue, use the NbDbAdmin Windows user interface to run validation. -------------------------------------------------------------------------------- Etrack Incident = ET1384948 Associated Primary Etrack = ET1287214 Titan cases: 220-289-079 Description: The status code within the Try # was incorrect. The status code would show 0 even though it had failed and another attempt was made. -------------------------------------------------------------------------------- Etrack Incident = ET1383744 Associated Primary Etrack = ET1261795 Titan cases: 220-280-182 Description: Changes were made to improve slow resource allocations for jobs using storage unit (STU) groups and prioritized allocation. The behavior that was seen is thus: - An STU group is looked at and an STU is identified within the group. - The Enterprise Media Manager (EMM) finds a drive (even if it is waiting for an unload) on the highest ranking media server in the group (regardless if there are drives that are immediately available on other STU's in the group) - EMM then allocates that drive - without looking for any other available drives. - The process is repeated, again, not looking for any other STU's in the group (which have many available drives). -------------------------------------------------------------------------------- Etrack Incident = ET1388766

Associated Primary Etrack = ET1286931 Titan cases: 220-310-979 Description: The LOGARCHMETH1 VENDOR backups would work for 32-bit DB2, but would fail for 64-bit using DB2 9.1.4.a on Windows AMD platforms. DB2 diag log showed: 2008-06-02-17.01.06.941000-300 I1296334F328 LEVEL: Error PID : 3468 TID : 5176 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 FUNCTION: DB2 UDB, data protection services, sqlpInitVendorAPI, probe:1680 MESSAGE : Error resolving address for function db2VendorQueryApiVersion. -------------------------------------------------------------------------------- Etrack Incident = ET1384909 Associated Primary Etrack = ET1204445 Titan cases: 220-302-209 320-083-263 Description: After upgrading to NetBackup 6.5, 5.X DSSU images were not appropriately expired from disk, causing the DSSU to fill to capacity. Workaround: If you encounter this issue, you can invoke the nbdelete -allvolumes command repeatedly until images are removed from disk. -------------------------------------------------------------------------------- Etrack Incident = ET1389088 Associated Primary Etrack = ET1387311 Titan cases: 240-813-600 Description: Logging from vnet_cached_gethostbyname() would increase significantly in NetBackup 6.5.2 if VERBOSE = 5 in the bp.conf file. Workaround: To avoid this issue, reduce VERBOSE to a value less than 5. -------------------------------------------------------------------------------- Etrack Incident = ET1388050 Associated Primary Etrack = ET1273708 Titan cases: 281329229 Description: The Windows client would not display volumes during the mapping screen during FastBoot ISO. -------------------------------------------------------------------------------- Etrack Incident = ET1388180 Description: The NetBackup Administration Consoles for Windows and Java, and the NOM user interface display "No" in the "Incompliance Column" for capacity-based licenses (for example, Flexible Disk, OpenStorage, and PureDisk) when an unlimited key is installed and the used capacity for the licensed feature is greater than 0. -------------------------------------------------------------------------------- Etrack Incident = ET1227447

Associated Primary Etrack = ET1213039 Titan cases: 320-084-538 Description: For SAP restores, the restore status per file is posted to the brrestore detail log when the file has been restored (or failed to restore if that is the case) rather than posting the restore status for all files when the restore has ended. Additional Notes: This capability is only applicable for UNIX platforms. -------------------------------------------------------------------------------- Etrack Incident = ET1383756 Associated Primary Etrack = ET1304028 Titan cases: 291-010-529 Description: After an upgrade from NetBackup 6.5.1 to 6.5.2, a progress log message was missing and caused monitoring scripts to fail. -------------------------------------------------------------------------------- Etrack Incident = ET1388092 Associated Primary Etrack = ET1381346 Titan cases: 320-121-647 Description: Backups of Shadow Copy Component on Windows 2008 would cause the bpbkar32.exe executable to fail, if an extra slash (\) existed in a pathname of a registry field used by the Shadow Copy Component. -------------------------------------------------------------------------------- Etrack Incident = ET1388192 Associated Primary Etrack = ET1210846 Titan cases: 320-074-322 Description: A change has been made to address an issue that caused duplication from disk staging to fail with a status 50. The fix involved adding a missing acknowledge in bptm. bpduplicate sends put_short message to bptm as an acknowledge in communication, however bptm was missing a get_short message so it would hang while waiting for a get_long from message bpduplicate. -------------------------------------------------------------------------------- Etrack Incident = ET1388053 Description: The NB_65_I18N policy creation with snapshots would fail validation. -------------------------------------------------------------------------------- Etrack Incident = ET1388054 Description: Snapshot Policy wizard would report, "no valid methods available" for the Offhost Alternate client policy configuration. -------------------------------------------------------------------------------- Etrack Incident = ET1388057 Description: From the NetBackup Administration Console, the catalog wizard did not provide the cluster's virtual name when trying to configure a cold catalog.

-------------------------------------------------------------------------------- Etrack Incident = ET1388058 Description: The Configure Disk Pool wizard had status misspelled on the disk pool creation screen. -------------------------------------------------------------------------------- Etrack Incident = ET1388060 Description: The VMware off-host backup machine name would disappear from the "Off-host backup machine" field in Policy Attributes tab. -------------------------------------------------------------------------------- Etrack Incident = ET1388063 Description: The vxlogview would report corrupted log records. -------------------------------------------------------------------------------- Etrack Incident = ET1386537 Associated Primary Etrack = ET1384642 Titan cases: 291-042-388 Description: If number of streams (drives in util file) configured is more than 64 and the "sort_backup_type" is specified as "device", then only the files from 64 devices are getting backed up. The remaining files are ignored and no error status is reported. Workaround: If file list is from more than 64 devices, then DO NOT use "device" as "sort_backup_type". And the number of streams should be specified as less than or equal to 64. -------------------------------------------------------------------------------- Etrack Incident = ET1382684 Associated Primary Etrack = ET1375497 Titan cases: 220-404-140 230-572-942 240-806-831 Description: The time required to start nbpem can be large when there are a number of client names in the client attributes list. Workaround: To avoid this issue, reduce the size of the client attributes list. -------------------------------------------------------------------------------- Etrack Incident = ET1383404 Associated Primary Etrack = ET1378835 Titan cases: 291-031-055 Description: Catalog backups initiated by Vault profiles were not restorable because no True Image Restore (TIR) information was generated. -------------------------------------------------------------------------------- Etrack Incident = ET1387984 Description: The version information utility would crash on some UNIX systems.

-------------------------------------------------------------------------------- Etrack Incident = ET1383532 Associated Primary Etrack = ET1273298 Titan cases: 290-985-538 **Description: Folders and/or Files (greater than 32 KB in size) restored to a UNC CIFS share on an EMC Celerra appliance resulted in a Status 0, however, the restored files have an incorrect size and may be corrupt and unusable. The backup image, however, is valid. This issue does not affect restores targeted to a Universal Naming Convention (UNC) path on a Windows host. Additional Notes: For additional information about this issue, refer to the following TechNote on the Symantec Support Web site. http://entsupport.symantec.com/docs/304383 -------------------------------------------------------------------------------- Etrack Incident = ET1383742 Associated Primary Etrack = ET1238943 Titan cases: 220-250-211 Description: Changes were added to improve hostname caching. -------------------------------------------------------------------------------- Etrack Incident = ET1383761 Associated Primary Etrack = ET1319339 Titan cases: 220-369-133 281-386-485 291-011-047 Description: If a calendar schedule window spanned midnight, jobs were started at midnight, not when the calendar schedule window actually opened. Also, calendar schedules that span midnight could fail at midnight with a status 196. -------------------------------------------------------------------------------- Etrack Incident = ET1391168 Associated Primary Etrack = ET1198807 Titan cases: 240707776 Description: In the NOM user interface, the Reports were not being emailed after a few days, however, the reports would appear as "Sending Email..." in the status column. -------------------------------------------------------------------------------- Etrack Incident = ET1386760 Associated Primary Etrack = ET1297359 Titan cases: 281-362-716 Description: A fix was added to handle multiple issues with Vault containers that are mentioned in the following list: - On adding media to an empty container, the return date would never get updated - On adding media to a non-empty container, the return date would never

get updated - If a container was recalled and the same container was used to add new media, Vault would recall the newly added media due to the reasons mentioned above -------------------------------------------------------------------------------- Etrack Incident = ET1393321 Associated Primary Etrack = ET1227184 Titan cases: 220-339-972 Description: A copied BMR configuration could not be deleted on Windows. -------------------------------------------------------------------------------- Etrack Incident = ET1386763 Associated Primary Etrack = ET1365764 Titan cases: 291-027-125 Description: The Vault Session summary log was empty after a successful session. It used to provide brief session details in NetBackup 5.x versions. A fix was added to log meaningful Vault session details to the summary.log file. -------------------------------------------------------------------------------- Etrack Incident = ET1391109 Description: bpjobd would core dump on some platforms while changing the job priority dynamically. -------------------------------------------------------------------------------- Etrack Incident = ET1383763 Associated Primary Etrack = ET1321939 Titan cases: 220-335-223 291-058-053 Description: Script-based BLI incremental backups would run as full backups after an upgrade from NetBackup 6.5.1 to 6.5.2. The Scheduler was starting bpbrm for incremental BLI backups with inappropriate options that forced a full backup. -------------------------------------------------------------------------------- Etrack Incident = ET1394039 Associated Primary Etrack = ET1292872 Titan cases: 220-268-467 Description: In VMware backups, if the virtual machine or the proxy server have a cluster size of 512 bytes, then backups of VMDK files would be corrupt. This was due to a problem in determining the offset into the backup image. -------------------------------------------------------------------------------- Etrack Incident = ET1394025 Associated Primary Etrack = ET1382322 Titan cases: 281-251-179 Description: If the MPX was greater than 1 within the policy schedule, then the checkpoints on the disk backups would hang. -------------------------------------------------------------------------------- Etrack Incident = ET1383630 Associated Primary Etrack = ET1319057

Titan cases: 220-371-648 291-015-879 Description: SQL Server backups would failed with a Status 6 and "SET SNAP_ID" errors. -------------------------------------------------------------------------------- Etrack Incident = ET1392132 Associated Primary Etrack = ET1363804 Titan cases: 291-026-369 Description: The granular_proxy option has been added in bpjava. This was required for the Exchange policy for NetBackup 6.5.2 and above. This fix ensures that the BPRD_BPLIST protocol/224 will be executed correctly for the Exchange policy type. -------------------------------------------------------------------------------- Etrack Incident = ET1386750 Associated Primary Etrack = ET1270507 Titan cases: 311-914-328 Description: Image selection would take longer to run than previous versions (6.0 MP5). A different approach to compare hosts used in NetBackup 6.0 MP6 caused this issue. A fix was added to improve the image selection performance so that it is equal to the performance in NetBackup 6.0 MP5. -------------------------------------------------------------------------------- Etrack Incident = ET1388236 Associated Primary Etrack = ET1252473 Titan cases: 320-105-171 320-122-006 Description: bpgp was removed, and a replacement to set and get the include and exclude lists from clients was not provided. -------------------------------------------------------------------------------- Etrack Incident = ET1384020 Associated Primary Etrack = ET1276427 Titan cases: 220-269-379 Description: A change was made to address an issue where a Storage Lifecycle Policy (SLP) would attempt to duplicate an image even when all of the required copies were already made. -------------------------------------------------------------------------------- Etrack Incident = ET1395057 Associated Primary Etrack = ET1394282 Titan cases: 311-968-542 Description: Basic disk staging jobs would always start with a priority of 99999 even if the priority defined in staging schedule was different. -------------------------------------------------------------------------------- Etrack Incident = ET1384919 Description: The duplication manager should process successful backup-only images as lifecycle complete even if the lifecycle is inactivated.

As of NetBackup 6.5.2, the duplication manager would ignore all images if the lifecycle is inactivated. This was to stop any duplication jobs running for such images while backups are happening. However, this also stops the processing of backup-only (ITC) images that have created expected backup copies to be considered as lifecycle complete. Therefore, until the lifecycle is not activated back, such images, though have been completed, will sit as lifecycle incomplete and will not expire even if their expiration date arrives. -------------------------------------------------------------------------------- Etrack Incident = ET1383792 Description: A change was added to address an issue that caused duplication jobs for a Storage LifeCycle Policy to not run. -------------------------------------------------------------------------------- Etrack Incident = ET1383772 Associated Primary Etrack = ET1378715 Description: Shared disk images were not being deleted from the LUN's. -------------------------------------------------------------------------------- Etrack Incident = ET1393919 Description: The nbemmcmd command would crash if the emmname parameter provided was longer than the emmname parameter in the bp.conf file. -------------------------------------------------------------------------------- Etrack Incident = ET1384032 Associated Primary Etrack = ET1366836 Titan cases: 311-972-942 320-124-684 Description: SLP would not remove the NDMP tape copies or image records from EMM even after expiration occurred. -------------------------------------------------------------------------------- Etrack Incident = ET1384023 Associated Primary Etrack = ET1297806 Titan cases: 220-320-623 Description: Duplication of an image after it is SLP complete would result in re-insertion in EMM. Additional Notes: When nbstlutil lists backups, the images that were previously listed in an UNKNOWN state were now labeled as NOT MANAGED. -------------------------------------------------------------------------------- Etrack Incident = ET1384966 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048 Description: When there were many lifecycle-managed backups needing to be completed, it

would take inordinately long to process them. -------------------------------------------------------------------------------- Etrack Incident = ET1395393 Associated Primary Etrack = ET1316801 Titan cases: 220-336-949 Description: A change was made to resolve a deadlock issue between BRMComm and ExportedResourceMgr where the BRMComm and ERM locks were being obtained in reverse order. -------------------------------------------------------------------------------- Etrack Incident = ET1383506 Associated Primary Etrack = ET1375866 Titan cases: 320-122-461 Description: SAP with RMAN restore would fail because of a missing Oracle license. The Oracle license was not required for SAP backup or restore. -------------------------------------------------------------------------------- Etrack Incident = ET1396286 Description: If Vault retention mappings were configured, Vault would disregard the mappings with a target retention level of zero (0) and instead use the source copy's retention level for the new image copy. This was incorrect, because zero (0) was a valid retention level. -------------------------------------------------------------------------------- Etrack Incident = ET1227458 Description: Media-related information was NOT written in the BRTOOL's detailed logs. -------------------------------------------------------------------------------- Etrack Incident = ET1396153 Description: NOM could not export Job logs from the Job details page. -------------------------------------------------------------------------------- Etrack Incident = ET1391110 Description: If a storage lifecycle is configured without duplication copies and if one of the backup copies is configured with "Expire After Duplication", then the copy (and the image if there was only a single backup copy) is expired from the catalog by the storage lifecycle. However, this is an incorrect configuration and the "Expire After Duplication" retention type should not be allowed for backup destinations if there are no duplication destinations in the storage lifecycle. -------------------------------------------------------------------------------- Etrack Incident = ET1397984 Description: The std::istringstream.str string did not work on a TRU64 platform to initialize an istringstream object. -------------------------------------------------------------------------------- Etrack Incident = ET1396005

Description: From the NetBackup Administration Console > Host Properties > Master Server, clicking the Enter button on the "Default Job proprieties" window would cause the right frame to appear blank. -------------------------------------------------------------------------------- Etrack Incident = ET1391795 Description: Windows 2008 was able to be used as a proxy server for VMWare FlashBackups due to an issue with an extra, "free of memory". -------------------------------------------------------------------------------- Etrack Incident = ET1393810 Description: A change was added to resolve an NBPEM core dump issue that occurred on a Tru64 master server. -------------------------------------------------------------------------------- Etrack Incident = ET1393798 Description: A change was made to address a core file issue that was generated by nbshareddisk when formatting Shareddisk LUNs using the -novm option. -------------------------------------------------------------------------------- Etrack Incident = ET1397604 Description: Unable to delete an app_cluster machine record. -------------------------------------------------------------------------------- Etrack Incident = ET1395089 Associated Primary Etrack = ET1182999 Titan cases: 311-769-409 Description: FlashBackup multiple volume restores and VMware multiple volume restores would hang or fail. -------------------------------------------------------------------------------- Etrack Incident = ET1398627 Associated Primary Etrack = ET1397478 Titan cases: 320-129-580 Description: The NetBackup Service Layer (nbsl) was consuming too many file descriptors when NOM was enabled. -------------------------------------------------------------------------------- Etrack Incident = ET1399009 Associated Primary Etrack = ET1398114 Titan cases: 311-886-162 Description: The deferred eject was grayed out when running the NetBackup Administration Console on a remote server. -------------------------------------------------------------------------------- Etrack Incident = ET1388000 Associated Primary Etrack = ET1380098 Titan cases: 220-371-768

Description: Some of the values in LIFECYCLE_PARAMETERS file did not have reasonable upper limits for enterprise environments. For example, the MIN_KB_SIZE_PER_DUPLICATION_JOB and MAX_KB_SIZE_PER_DUPLICATION_JOB parameters are internally read into long type variables that would overflows before a reasonable value could be met. -------------------------------------------------------------------------------- Etrack Incident = ET1387827 Description: A change was made to address a nbstserv core dump issue that caused duplication job to longer run. -------------------------------------------------------------------------------- Etrack Incident = ET1397582 Description: NetBackup Windows processes would crash if the NetBackup configuration registry entries were modified while the process was reading the configuration. -------------------------------------------------------------------------------- Etrack Incident = ET1393793 Associated Primary Etrack = ET1386040 Titan cases: 311-991-329 Description: There would be slow performance for bptm -delete_all_expired when attempting to deassign media that had expired before all the fragments had been duplicated to their final destination. -------------------------------------------------------------------------------- Etrack Incident = ET1396248 Description: In SLP, if the duplication STU is "any available", it could also pick the basic disk STU. -------------------------------------------------------------------------------- Etrack Incident = ET1402394 Description: Storage servers and snap vault filers were being listed as NDMP in nbemmcmd. The verbose output will indicate that these servers are snap vault and storage server. -------------------------------------------------------------------------------- Etrack Incident = ET1396112 Description: A change was made to address issue that would cause NBJM crash on shutdown on Linux. -------------------------------------------------------------------------------- Etrack Incident = ET1401373 Description: Make messages would fail because of the duplicated ID in the file sfr.c. -------------------------------------------------------------------------------- Etrack Incident = ET1402907 Associated Primary Etrack = ET1402687

Description: Images on a common set of media may be put in separate batches by Vault for duplication. This would cause some duplication jobs (and tape drives allocated for duplication) to remain idle while waiting for media reserved by other duplication jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1403048 Associated Primary Etrack = ET1402370 Titan cases: 240-815-730 Description: Server status, as shown in the Activity Monitor, indicated a successful restore when an SQL Server restore job failed due to the database being in a state that does not allow restores. This problem occurred, for example, if the database was being accessed by another process that prevented the restore operation from obtaining exclusive access. -------------------------------------------------------------------------------- Etrack Incident = ET1395233 Titan cases: 311-907-984 Description: ltid would hang if REQUIRED_INTERFACE was specified and the EMM server was rebooted. -------------------------------------------------------------------------------- Etrack Incident = ET1402499 Associated Primary Etrack = ET1399919 Titan cases: 281-406-679 Description: Backup of Exchange public folders would cause an exception in bpbkar32 if a folder was not accessible. -------------------------------------------------------------------------------- Etrack Incident = ET1403069 Associated Primary Etrack = ET1402254 Titan cases: 230-563-260 Description: Exchange 2007 snapshot backup could fail with a status 130 if the checkpoint log file was greater than 0xfffff.log. -------------------------------------------------------------------------------- Etrack Incident = ET1402922 Description: LTID would send an UpdateMountStat request with a corrupted MediaId parameter. -------------------------------------------------------------------------------- Etrack Incident = ET1403920 Description: A change was made to address a BPTM core dump issue that would occur on AIX and HP-UX media servers. -------------------------------------------------------------------------------- Etrack Incident = ET1405290 Associated Primary Etrack = ET1288659 Titan cases: 320-111-170

Description: The "Failover" selection method of storage unit groups may not be respected with multiplexing set. -------------------------------------------------------------------------------- Etrack Incident = ET1402967 Description: In BAR user interface, after selecting the "Point in Time Rollback" option, the backed-up images were not visible in the Restore tab. -------------------------------------------------------------------------------- Etrack Incident = ET1398832 Description: SharePoint FULL and DIFFERENTIAL images selected together for restore would fail to commit the SharePoint object selected for restore. -------------------------------------------------------------------------------- Etrack Incident = ET1404850 Associated Primary Etrack = ET861258 Titan cases: 280-660-746 Description: The NetBackup Administration Console for Windows would hang while generating Vault reports such as the Summary Distribution, pick list, inventory, etc. A fix was made to ensure that larger Vault reports are shown in Windows Administration Console. -------------------------------------------------------------------------------- Etrack Incident = ET1320530 Description: If a synthetic schedule is added to a policy after the regular schedules have run and created the streams file information, immediate execution of the schedule will fail with a 200 status and scheduled execution never happens. This is due to missing streams file information. Workaround: If you encounter this issue, run a non-synthetic backup after adding the synthetic schedule. -------------------------------------------------------------------------------- Etrack Incident = ET1398698 Associated Primary Etrack = ET1383617 Titan cases: 240-806-831 Description: The nbpem startup can be slow in large environments with a large number of clients. Jobs are not scheduled until nbpem startup is complete. -------------------------------------------------------------------------------- Etrack Incident = ET1396083 Description: A change was added to address an nbpem core dump issue that would occur on Linux after a hot catalog backup job completed. -------------------------------------------------------------------------------- Etrack Incident = ET1408129 Associated Primary Etrack = ET1397447

Titan cases: 230-580-853 Description: SharePoint 2007 Backups using a FQDN of the SQL server would fail with an error 71. When a Web Application and site was created using FQDN database, NetBackup was unable to backup the database, either through Document Level or Standard database level. -------------------------------------------------------------------------------- Etrack Incident = ET1392668 Description: Checkpointed jobs were not resumed automatically after a cluster failover. -------------------------------------------------------------------------------- Etrack Incident = ET1409131 Associated Primary Etrack = ET1206358 Titan cases: 281-179-782 Description: NetBackup performance, both its daemons or services and in the user interface, will be negatively impacted when DNS services are slow to return hostname or reverse-IP lookups. Because all hostnames and aliases on a master or media server may be examined while accepting or creating a connection, if some of these names are not in the DNS, and the DNS environment is slow to respond, this will delay NetBackup, and cause the user interface to be non-responsive. This change logs the offending hostname whenever such a lookup takes longer than five seconds, making it easier to know what to clean out of a configuration. The new log messages look like the following: 10:10:23.918 [25766] <2> vnet_cached_gethostbyname: vnet_hosts.c.377: DNS lookup slow for host: : kermit.frog.com 10:10:24.395 [25766] <2> vnet_cached_gethostbyname: vnet_hosts.c.378: DNS lookup elapsed time: : 30 0x0000001e The elapsed time is in seconds. -------------------------------------------------------------------------------- Etrack Incident = ET1409154 Description: When suspended jobs were resumed more than once, it would cause jobs to fail with a status 801. -------------------------------------------------------------------------------- Etrack Incident = ET1410597 Description: VMware VCB Backup would attempt to connect to the virtual machine instead of through the proxy on HP-UX. -------------------------------------------------------------------------------- Etrack Incident = ET1410659 Description: Windows Release Update installer would install the Microsoft run-time dlls, msvcp71.dll and msvcr71.dll, into the root system drive. A change was made that fixed the default install directory path for the dlls. --------------------------------------------------------------------------------

Etrack Incident = ET1411251 Associated Primary Etrack = ET1285409 Titan cases: 290-994-546 Description: The Remote Windows XP Administration Console would display the pop-up, COMM_FAILURE (IDL:omg.org/CORBA/COMM_FAILURE:1.0), when accessing media. -------------------------------------------------------------------------------- Etrack Incident = ET1410516 Associated Primary Etrack = ET1402753 Titan cases: 290-978-866 Description: NBWIN preview media for restore on a Windows 2003 or a remote Windows XP workstation would fail to display all media needed. -------------------------------------------------------------------------------- Etrack Incident = ET1411527 Associated Primary Etrack = ET1380465 Titan cases: 320119717 Description: If the backup image is more than 2TB, then the restore job from that image would fail with a status 174. -------------------------------------------------------------------------------- Etrack Incident = ET1411776 Titan cases: 230-572-386 Description: The first fragment written by BPTM will not be position checked, allowing a rogue rewind to go undetected. If a rogue rewind occurred during the time between reading the empty header and writing the first backup header, the rewind could go undetected. -------------------------------------------------------------------------------- Etrack Incident = ET1410874 Associated Primary Etrack = ET1402736 Titan cases: 320-130-796 Description: Unable to perform a multi-stream FlashBackup using an "old" method, such as not using Snapshot Client options. -------------------------------------------------------------------------------- Etrack Incident = ET1412331 Description: With Snapshot destination in SLP, there was a difference in the value of the Storage unit in NetBackup-Java Administration Console and in the "nbstlutil list". A change was added so when a Snapshot destination is in SLP, the backup destination and duplication destination will pick up the actual STU. -------------------------------------------------------------------------------- Etrack Incident = ET1412417 Description: A fix was made to address an nbrmms core dump issue that would occur because of a memory access violation in the VxFI code.

-------------------------------------------------------------------------------- Etrack Incident = ET1413338 Description: An inaccurate log message was being written when bpdbm failed to update a STREAMS file in image validation. -------------------------------------------------------------------------------- Etrack Incident = ET1411302 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048 Description: A change was made to resolve an nbstserv core dump issue that would occur while processing a large number of images. -------------------------------------------------------------------------------- Etrack Incident = ET1413269 Associated Primary Etrack = ET1414241 Description: Jobs were not being scheduled for a newly added policy. -------------------------------------------------------------------------------- Etrack Incident = ET1410786 Description: Jobs for a policy with multi-streaming enabled and with a bad client name failed with status 200. -------------------------------------------------------------------------------- Etrack Incident = ET1413572 ET1385085 Associated Primary Etrack = ET1381455 ET1288113 Titan cases: 230-534-351 281-379-673 220-289-644 Description: NBJM would cancel a duplication job (larger backups consistently fail with status 50) that was initiated using Storage Lifecylce Policies (SLP). -------------------------------------------------------------------------------- Etrack Incident = ET1414212 Associated Primary Etrack = ET1222342 Titan cases: 220-208-577 Description: Running bpjobd -cleanup on a large number of jobs in conjunction with bpduplicate may result in a status 12 or status 50 error. This would likely happen in a large environment where the nightly pruning of the jobs database could take in upwards of ten minutes. Workaround: If you encounter this issue, perform more frequent recycling with fewer jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1412557 Description: Multiple jobs for the same policy, client, and schedule combination would erroneously run simultaneously, or nearly so. -------------------------------------------------------------------------------- Etrack Incident = ET1402233

Description: A change was made to address an issue that caused core dump files to be generated while restoring Exchange legacy mailbox messages on Windows 2008 running Exchange 2007. The restoration jobs finished with a status 5 error. -------------------------------------------------------------------------------- Etrack Incident = ET1415612 Associated Primary Etrack = ET1415270 Titan cases: 220-411-437 291026372 Description: A fix has been added to resolve an error that would occur when attempting to browse directories with apostrophes in the name. A similar fix was provided to resolve "Invalid Character" errors that would occur when selecting directories with an ampersand (&) character in the name. -------------------------------------------------------------------------------- Etrack Incident = ET1414776 Description: In the Windows BAR user interface, the Lotus database link's backup would incorrectly report the size of the database. -------------------------------------------------------------------------------- Etrack Incident = ET1413649 Associated Primary Etrack = ET1407104 Titan cases: 320-129-510 Description: Storage Lifecycle Policy (SLP) duplications would create one batch per image for a tape with multiple images. -------------------------------------------------------------------------------- Etrack Incident = ET1401482 Description: An old image was not being deleted for more space in lifecycle storage unit when the "staged capacity managed" retention type was selected. The job would fail with the error, "Disk storage unit is full" and a status 129. -------------------------------------------------------------------------------- Etrack Incident = ET1413567 Description: Duplicate, restore, and verify from a NearStore FSE Storage Unit would fail with the following error. "Cannot read image from disk, Invalid argument" -------------------------------------------------------------------------------- Etrack Incident = ET1415683 Description: A change was made to address an issue that caused NBPEM to stop scheduling jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1416768 Description: bptm would core dump when a Nearstore restore failed due to slow network issues.

-------------------------------------------------------------------------------- Etrack Incident = ET1415142 Associated Primary Etrack = ET1408101 Titan cases: 320-130-941 **Description: Unable to backup a significant number of System files during a Shadow Copy Component or a System State backup on Windows 2008 when VSS Snapshot reported missing file(s) on the snapshot. Additional Notes: For additional information about this issue, refer to the following TechNote on the Symantec Support Web site. http://entsupport.symantec.com/docs/308301 -------------------------------------------------------------------------------- Etrack Incident = ET1416620 Description: A VMWare Backup of an Exchange Client was transferring too many bits to the storage unit. Workaround: To avoid this issue, do not have the NetBackup policy automatically retry the backup on a failure. -------------------------------------------------------------------------------- Etrack Incident = ET1415243 Description: A SharePoint Document-level Restore (DLR) would not restore all peer folders in the "Shared Documents". -------------------------------------------------------------------------------- Etrack Incident = ET1421025 Description: Jobs started to backup transaction logs for an SQL policy configured with instant recovery and off host backup would fail with a status 41. -------------------------------------------------------------------------------- Etrack Incident = ET1425093 Description: During stress testing, the event manager service would occasionally go down and come back up. nbpem asserted:!m_getAllNamesCall PemPolicyCache.cpp 104 while stress testing nbevtmgr with repeated start, stop, and sending events. -------------------------------------------------------------------------------- Etrack Incident = ET1424266 Associated Primary Etrack = ET1417414 Titan cases: 240-828-934 Description: Policies with schedules set to frequency of 52 weeks and multi-stream would fail with a status 196 with nbpem v5. -------------------------------------------------------------------------------- Etrack Incident = ET1423453

Description: Suspended jobs for an inactive policy could not be resumed after a failover. -------------------------------------------------------------------------------- Etrack Incident = ET1412062 Description: Some of the English NetBackup's Host Property dialogs were not readable on Japanese Windows. -------------------------------------------------------------------------------- Etrack Incident = ET1382626 Associated Primary Etrack = ET1119099 Titan cases: 230-437-882 281-186-454 281-212-486 281-247-334 281-268-586 281-271-833 290-882-221 311-728-655 311-796-828 Description: Backups of Distributed File System Replication (DFSR) data on Windows 2003 R2 complete with a NetBackup Status Code 0, but the data is not backed up. Workaround: For detailed infromation about this issue, refer to the following TechNote on the Symantec Support Wed site. http://entsupport.symantec.com/docs/290900 Additional Notes: This patch will help customers discover the DFSR problems and refer them to an appropriate work-around. -------------------------------------------------------------------------------- Etrack Incident = ET1425900 Associated Primary Etrack = ET1416156 Titan cases: 220-406-370 **Description: If a VCB proxy backup of a virtual node joins an MPX group, all subsequent normal jobs in that MPX group would back up the proxy host. Workaround: The following list contains workarounds for this issue: - Turn off multiplexing on the VCB backups. - Run the VCB backups on a different storage unit. - Use a different volume pool for the VCB backups. For additional information about this issue, refer to the following TechNote on the Symantec Support Web site. http://entsupport.symantec.com/docs/308906 -------------------------------------------------------------------------------- Etrack Incident = ET1425285 Description: When a cluster failover was initiated while a duplication job was active, the bpdbm child processes that were active for the duplication job could take a long time to terminate. -------------------------------------------------------------------------------- Etrack Incident = ET1428096 Associated Primary Etrack = ET1409844

Titan cases: 220-406-066 Description: A change was made to address an nbpem version 4 issue (originating in ET1322956), mixed calendar schedule types in policies, where the daily WCT evaluates to 23:59:59, resulting in a status 196 error. -------------------------------------------------------------------------------- Etrack Incident = ET1423583 Description: Duplication jobs would fail with a status 50, but continue on to complete the duplication. -------------------------------------------------------------------------------- Etrack Incident = ET1426958 Description: If a multi-streamed policy with multiple schedules is blocked by failure history, the child job that runs after the failure history is expired may fail with a status 196. -------------------------------------------------------------------------------- Etrack Incident = ET1427064 Description: Storage Lifecycle Policies processing was failing occasionally while processing images with a large number of fragments because the bpdbm connection was timing out. -------------------------------------------------------------------------------- Etrack Incident = ET1429896 Associated Primary Etrack = ET1428219 Titan cases: 281-385-419 Description: Windows 2008 security would prevent enumeration of SharePoint objects in the NetBackup Client user interface. -------------------------------------------------------------------------------- Etrack Incident = ET1429721 Description: bpresolver would raise a program exception on Windows Server 2008 AMD64 platforms while performing a restore. -------------------------------------------------------------------------------- Etrack Incident = ET1429629 Description: If PEM restarted with a parent and child job in a WAITING_FOR_RETRY state, it would retry the child job only. After the child job completed, no more jobs were scheduled for this policy/client. -------------------------------------------------------------------------------- Etrack Incident = ET1430825 Associated Primary Etrack = ET1373028 Titan cases: 311-971-198 Description: For duplicate multiple copies, all duplicate jobs would fail if any of the Disk Copies have a Dummy Allocation supplied when executing on Windows.

-------------------------------------------------------------------------------- Etrack Incident = ET1428794 Description: nbstserv would halt processing while waiting for an nbdelete call to complete. -------------------------------------------------------------------------------- Etrack Incident = ET1431220 Description: A failed attempt to validate a copy during a duplication job was holding a write lock on the image file and causing other bpdbm child processes to hang until the duplication job finished. -------------------------------------------------------------------------------- Etrack Incident = ET1428632 Description: Changes were made to address two memory leak errors found in the VxFI code that lead to a SharedDisk backup failure. -------------------------------------------------------------------------------- Etrack Incident = ET1431217 Description: Bpduplicate would not allow a copy of a backup to be started if another duplication for the same backup was in progress. Also, if more than one duplication to different destination copies from the same disk source copy occurs simultaneously, the duplications would either hang or error. Workaround: To work around the simultaneous duplications from the same disk source copy hang or error issue, disable shared memory duplications. Touch the following file on the master server: UNIX: /usr/openv/netbackup/NOSHMDUP Windows: <installed_path>\NetBackup\NOSHMDUP -------------------------------------------------------------------------------- Etrack Incident = ET1431957 Associated Primary Etrack = ET1417636 Titan cases: 311-991-075 Description: EMM would crash because it was not handling a CNOS exception that was leaked through the Event Manager supplier-side library. The createConnectObjects() method makes calls directly to CNOS but in some cases it does not surround those calls in try/catch blocks. This caused CNOS exceptions to be leaked to the caller, in this case EMM. EMM catches specific exceptions; those not caught are pushed up the stack until it exits as an unhandled exception. -------------------------------------------------------------------------------- Etrack Incident = ET1432152

Description: A change was made to address an Incremental backup data loss issue that would occur if bpbkar took more than 10 seconds to start. -------------------------------------------------------------------------------- Etrack Incident = ET1432733 Description: A failed job waiting to be retried would prevent a job session from being closed. Therefore, the cold catalog backup to be run at the end of session was delayed until after all of the job-tries end and the job is done. -------------------------------------------------------------------------------- Etrack Incident = ET1431905 Description: A change was made to address an issue that caused nbpem to be caught in an infinite loop, resulting in no jobs being able to start. -------------------------------------------------------------------------------- Etrack Incident = ET1436492 Associated Primary Etrack = ET1368270 Titan cases: 240-779-778 Description: During a True Image Restore (TIR) data backup, if the socket used to get the data failed, the format of the tape could be written incorrectly. -------------------------------------------------------------------------------- Etrack Incident = ET1436738 Associated Primary Etrack = ET1400885 Titan cases: 291-058-781 Description: The requested Start Time calculation caused a full backup to be scheduled repeatedly if the last incremental backup occurred between windows and the frequency was a multiple of 24 hours. To fix this issue, pre-window checking was added so that if the last backup falls between windows, the due time can pick up the next window even if it is the same day. -------------------------------------------------------------------------------- Etrack Incident = ET1439637 Description: A change has been added to address a core dump issue that would occur with nbdelete. -------------------------------------------------------------------------------- END WINDOWS SERVER =========================================================================

UNIX Servers

========================================================================= Etrack Incident = ET1275559

Description: A bpdbm core dump would occur because of a badly formatted ovgetmsg routine. A change was made to address this issue. -------------------------------------------------------------------------------- Etrack Incident = ET1302929 Description: A change was added to fix memory leaks discovered in the bpplsched command line and nbproxy which use common free routines. The cause of the problem was that the command line would mix results from different queries. The c_receive_flag determines if the contents of a structure are freed and if queries are mixed like this, the value may not be the same. -------------------------------------------------------------------------------- Etrack Incident = ET1302749 Associated Primary Etrack = ET1300264 Titan cases: 220-369-133 311-946-518 320-117-267 320-122-713 Description: User backups with windows configured to be 24x7, would fail at midnight with a status code 196. -------------------------------------------------------------------------------- Etrack Incident = ET1317013 Associated Primary Etrack = ET1292141 Titan cases: 220-319-568 240-781-624 311-955-023 Description: Backups would fail with a status code 230 when using the en_GB.ISO8859 locale. -------------------------------------------------------------------------------- Etrack Incident = ET1317008 Associated Primary Etrack = ET1295547 Titan cases: 230-554-457 Description: The policy execution manager (nbpem) would core dump after restarting a job that had been running before the upgrade to NetBackup 6.5.2. -------------------------------------------------------------------------------- Etrack Incident = ET1317006 Associated Primary Etrack = ET1297993 Titan cases: 291-011-673 Description: The policy execution manager (nbpem) would exit with an ASSERT failed error that indicated m_due was less than or equal to m_startTime. -------------------------------------------------------------------------------- Etrack Incident = ET1317202 Associated Primary Etrack = ET1269997 Titan cases: 320-107-578 Description: Resource requests for bpduplicate (vault) were failing because of a missing parameter. The Vault duplications would fail with a status 800. Workaround: This would only occur when duplicating to storage units on

pre-NetBackup 6.5 media servers where the master server is at 6.5 or later. The workaround would be to not target storage units on pre 6.5 media servers when duplicating. It also will not be an issue for single-image duplications. -------------------------------------------------------------------------------- Etrack Incident = ET1317047 Associated Primary Etrack = ET1293461 Titan cases: 240790925 281375544 290011922 291-010-092 Description: The Client Attribute "Maximum Data Streams" was being ignored with NetBackup 6.5.2 and the global value "Maximum jobs per client" was always taking precedence irrespective if the setting was higher or lower. -------------------------------------------------------------------------------- Etrack Incident = ET1276489 Description: The bpexpdate -deassignempty command was failing to expire media on NDMP hosts. -------------------------------------------------------------------------------- Etrack Incident = ET1318091 Associated Primary Etrack = ET1295660 Titan cases: 311-944-025 Description: On Windows master servers, the online catalog backup was failing with a status of 2 for the parent job and 42 for one of the child jobs when non-multi-streamed policies were configured as critical policies in the catalog backup policy. Workaround: If you encounter this issue, remove critical policies from the online catalog backup policy. -------------------------------------------------------------------------------- Etrack Incident = ET1289921 Description: If backup jobs and synthetic/duplicate jobs were in progress simultaneously, some of the drives would become unusable. Workaround: If you encounter this issue, find the unusable drive and release it using the nbrbutil utility. -------------------------------------------------------------------------------- Etrack Incident = ET1322984 Description: A change was made to address a bpbdm core dump issue that occurred when the client list was being freed when user interface executed a Q_IMAGE_HWOS_GET query and the get_hwos() would perform a double free of the client list. -------------------------------------------------------------------------------- Etrack Incident = ET1364407 Description: When a policies schedule was changed the retention level was not correct

when modified to a value other than the default value. -------------------------------------------------------------------------------- Etrack Incident = ET1364422 Description: Synthetic Backup jobs would fail with a status 1 and were retried repeatedly. -------------------------------------------------------------------------------- Etrack Incident = ET1322803 Associated Primary Etrack = ET1266944 Titan cases: 281-351-695 Description: If media servers or other hosts not in the server list attempted to connect to a master, the connection would be rightly rejected. However, the diagnostic-logging-level 2 logging message itself used a non-threadsafe function that would cause memory corruption if threads collided. This would lead to crashes or erratic behavior for services such as EMM and PEM. Workaround: Search for "allow_peer" messages in the logs and reconfigure or decommision all of the servers that are logged as "not allowing connection". These servers are not in the master's server list, which triggers the log message. If the diagnostic logging level is set to not log Level 2 messages, the problem is averted. -------------------------------------------------------------------------------- Etrack Incident = ET1364661 Description: A change was made to to correct an issue that caused NBPEM to crash during an upgrade from NetBackup 6.5 to 6.5.3. The crash would happen in a clustered environment when nbpem was shutdown. -------------------------------------------------------------------------------- Etrack Incident = ET1373019 Description: All DSSU schedules were deleted (from PEM point of view) upon updating one DSSU schedule. -------------------------------------------------------------------------------- Etrack Incident = ET1383374 Associated Primary Etrack = ET1300103 Titan cases: 320-117-348 Description: bprd would core dump under certain circumstances when there was an invalid media server in the server list and the configuration was being updated. -------------------------------------------------------------------------------- Etrack Incident = ET1382658 Titan cases: 220-327-515 Description: If the VNET_OPTIONS entry was defined in your configuration (bp.conf on UNIX or the Registry on Windows) and if some values in the entry were zero, problems would occur if you attempted to upgrade to NetBackup 6.5.2

or later. An example entry would be: VNET_OPTIONS = 120 3600 0 0 0 0 0 0 0 If you attempt to run with this entry in NetBackup 6.5.2 or later, networking will not work on your machine. Workaround: If you encounter this issue, remove the VNET_OPTIONS entry from your configuration before you upgrade, or replace the 0-values in the entry with the NetBackup 6.5.2 defaults before upgrading. For example: VNET_OPTIONS = 120 3600 200 40 3 1 30 0 0 0 -------------------------------------------------------------------------------- Etrack Incident = ET1383586 Associated Primary Etrack = ET1295782 Description: For SharedDisk volumes, the unmount event triggers a clean up of all the committed space allocated for the backup. If the unmount event is missed, the volume may appear over-committed and may not get picked for future backups. As a results, MDS would not find any available Shared Disk volumes and backups in a pure Shared Disk environment would queue indefinitely. -------------------------------------------------------------------------------- Etrack Incident = ET1383584 Description: An issue existed that caused jobs to fail with a status 16: unimplemented feature error. -------------------------------------------------------------------------------- Etrack Incident = ET1184889 Titan cases: 220-111-009 Description: Cache results of server list comparisons for CORBA communications. The cache is intended to improve performance for configurations with a large number of hosts in the server list. -------------------------------------------------------------------------------- Etrack Incident = ET1276613 Associated Primary Etrack = ET1135854 Titan cases: 281-213-065 Description: During long running back up jobs, the firewall between the master and media server will close connection if it is configured to do so. This causes a break in communication between the master and media server and a failure of backups. Workaround: If you encounter this issue, disable the firewall timeout. However, this may be detrimental to firewall security. -------------------------------------------------------------------------------- Etrack Incident = ET1382632

Associated Primary Etrack = ET1238838 Titan cases: 311-880-802 Description: A NetBackup service such as nbjm would sometimes abort, leaving a core dump. A change has been made to correct this issue. -------------------------------------------------------------------------------- Etrack Incident = ET1383839 Titan cases: 220-337-212 Description: On some AIX systems, it was discovered that ltid would not start. The stdout error is "Unable to get external file version from EMM database". The logs show the following CORBA error: "Msg exceeds maximum allowed size". Workaround: You can avoid this issue by setting LANG=C in the shell before starting ltid. You an also change the system default by editing /etc/environment. -------------------------------------------------------------------------------- Etrack Incident = ET1383438 Associated Primary Etrack = ET1322123 Titan cases: 240-776-132 Description: A change was made to improve the parsing of the Job Try file in nbproxy because it would take a long time. -------------------------------------------------------------------------------- Etrack Incident = ET1383440 Associated Primary Etrack = ET1269781 Titan cases: 290-988-768 Description: The NetBackup Service Layer (NBSL) would core dump under a load from NOM data queries: NBPolicyCollector::Collect. -------------------------------------------------------------------------------- Etrack Incident = ET1383434 Associated Primary Etrack = ET1234532 Titan cases: 220-236-821 Description: When you stop the services from the NetBackup Administration Console, the services would go away and you could not restart them from user interface. -------------------------------------------------------------------------------- Etrack Incident = ET1383442 Associated Primary Etrack = ET1281452 Titan cases: 230-535-095 Description: After running activate and deactivate policies in NOM the NetBackup-Java Adimistration Console was unable to read policies. -------------------------------------------------------------------------------- Etrack Incident = ET1383733 Associated Primary Etrack = ET1372893

Description: If NetBackup services are restarted when jobs using shared disk are active, the NetBack Resource Broker (nbrb) may not be able to de-allocate resources properly on a restart. nbrb unmounts the shared disks correctly but fails to inform MDS to de-allocate the resources. Workaround: If you encounter this issue, re-start the services, then wait between 5 and 10 minutes, and then run "nbrbutil -resetall" if no jobs are active. This will de-allocate the resources. If the jobs are active, you should wait for the jobs to finish before you run nbrbutil -resetall. -------------------------------------------------------------------------------- Etrack Incident = ET1383750 Associated Primary Etrack = ET1361178 Titan cases: 220-349-593 320-132-770 Description: If the MDS allocations were removed directly either using the nbrbutil -releaseMDS command or by deleting the record from database, the NetBackup Resource Broker (nbrb) would not be able to remove the corresponding allocation records from its database. This would cause the resource broker's drive cache to misbehave, for example, jobs may not get the resources even when the drives were available, and perform other redundant operations which consumes CPU cycles. -------------------------------------------------------------------------------- Etrack Incident = ET1383540 Associated Primary Etrack = ET1296912 Titan cases: 220-325-975 281-378-560 Description: A change has been made to address an issue that would cause a multiple copy, Oracle database backup to fail in some situations. -------------------------------------------------------------------------------- Etrack Incident = ET1384029 Titan cases: 291-009-192 Description: The FT Target Mode HBA was unable to login to the switch in F-Port mode. Only the L-port login would work. This issue applied to all HBA firmware variants that are supported – ISP2312, ISP2422 and ISP2432. If a particular fabric setup only supports F-Ports, then FT backups could not be performed. -------------------------------------------------------------------------------- Etrack Incident = ET1375483 Description: A change was made to correct a timing issue that bpduplicate would encounter when it tried to get the job priority from bpjobd, which would sometimes take longer than expected. -------------------------------------------------------------------------------- Etrack Incident = ET1383736 Associated Primary Etrack = ET1278280 Titan cases: 320-111-786 Description:

The nbemmcmd -renamehost command would not update the hostname that the DA_Thread_Pool uses for the heartbeat check. Workaround: If you encounter this type of issue, rename a host with the nbemmcmd -renamehost command and then stop and start nbemm. -------------------------------------------------------------------------------- Etrack Incident = ET1383527 Titan cases: 222-222-222 Description: When applying a NetBackup server patch, a change was made so that local modifications to the server.conf file will not be lost. Workaround: To ensure any local modifications to the server.conf are not removed, add the following line to the vxdbms.conf file to turn off automatic server.conf updates: VXDBMS_SELF_TUNING=OFF -------------------------------------------------------------------------------- Etrack Incident = ET1383523 Associated Primary Etrack = ET1300087 Titan cases: 240758288 Description: The stale port connection on the media server was being terminated by the firewall. Workaround: If you encounter this issue, lengthen the firewall's timeout time or disable that feature for an approved IP address. -------------------------------------------------------------------------------- Etrack Incident = ET1384879 Description: The NetBackup Database Manager would core dump when trying to log a debug message while adding an image fragment. -------------------------------------------------------------------------------- Etrack Incident = ET1385083 ET1385111 ET1386294 Associated Primary Etrack = ET1278625 Description: On an extremely busy system, the bpdbm service could experience two intermittent problems: 1. The service could hang for 30 minutes after starting a Q_IMAGE_READ_FILES_FILE query, and eventually cause bpdbm to terminate with a status code 63. 2. A Q_IMAGE_READ_FILES_FILE query would be processed successfully by bpdbm, but the socket would be closed on Windows platforms in a manner that caused the bptm process that issued the query to fail with a Windows status code of 10054. -------------------------------------------------------------------------------- Etrack Incident = ET1383757

Associated Primary Etrack = ET1316106 Titan cases: 320-117-413 Description: NetBackup Job Manager (nbjm) delays 90 minutes making thousands of JMUtility::updateParamsFileWOFB calls between receiving resources and starting bpbrm. This delay affected scheduled and user-directed backup jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1384675 Associated Primary Etrack = ET1318016 Titan cases: 240-790-104 Description: Restoring a backup taken with a storage unit that contains the application cluster virtual name would fail because NetBackup was unable to determine the NetBackup version of the application cluster name. -------------------------------------------------------------------------------- Etrack Incident = ET1383511 Associated Primary Etrack = ET1318015 Titan cases: 281-380-220 Description: A FlashBackup restore from an AIX RS6000 master would fail with a status 5 error. -------------------------------------------------------------------------------- Etrack Incident = ET1385061 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048 Description: If the primary lifecycle policy was set to inactive for a long period of time (for example, four days) then reactivated, it was possible that a large number of images would need to be processed. In this scenario, nbstserv would use so much memory that a core dump would occur. -------------------------------------------------------------------------------- Etrack Incident = ET1382599 Description: The snapshot policy wizard would recommend the obsolete VSS_Transportable FIM. This has been corrected to recommend the VSS FIM, which can be used in local and offhost (Alternate Client) backup environments. -------------------------------------------------------------------------------- Etrack Incident = ET1376805 Description: The NetBackup Job Manager (NBJM) would crash on shutdown because expired snapshots taken during non-streamed windows open file backup (WOFB) jobs were deleted. -------------------------------------------------------------------------------- Etrack Incident = ET1383782 Description: Synthetic schedules with a space specified in the keyword field would make the job fail. --------------------------------------------------------------------------------

Etrack Incident = ET1383502 Description: A change was made to correct an issue that caused the Point-in Time (PIT) restore to fail on an AIX platform. -------------------------------------------------------------------------------- Etrack Incident = ET1383497 Associated Primary Etrack = ET1262210 Titan cases: 281-343-506 Description: A change was made to resolve an issue in the V_string function that would cause bpfis to crash. -------------------------------------------------------------------------------- Etrack Incident = ET1383499 Description: A change was made to ensure proper cleanup occurs when a Snapshot backup fails at a stage after a Flashcopy was created at the array level. -------------------------------------------------------------------------------- Etrack Incident = ET1384270 Associated Primary Etrack = ET1297816 Titan cases: 240-786-065 Description: The NetBackup cluster monitor for AIX would incorrectly detect the unavailability of the NB_dbsrv daemon. -------------------------------------------------------------------------------- Etrack Incident = ET1386057 Associated Primary Etrack = ET1253903 Titan cases: 290-975-130 Description: A change was made to correct a bpdbm core dump issue found in the function, db_get_image_info() in strerror(). -------------------------------------------------------------------------------- Etrack Incident = ET1386060 Associated Primary Etrack = ET1281512 Titan cases: 311-821-936 Description: Crosschecking Oracle images (Q_IMAGE_BY_FILE) would fail if the image list existed for the client. Workaround: Remove the index files. -------------------------------------------------------------------------------- Etrack Incident = ET1383811 ET1383808 ET1382683 Associated Primary Etrack = ET1244548 ET1241226 Titan cases: 230-521-343 311-880-025 290-934-270 Description: A change was added to address an issue that caused NetBackup Policy Execution Manager (nbpem) to shut down. -------------------------------------------------------------------------------- Etrack Incident = ET1384822

Description: NBPEM would deadlock if restarted while jobs were in an INCOMPLETE state and new jobs were started for the same policy/client. -------------------------------------------------------------------------------- Etrack Incident = ET1386064 Description: A change has been added to eliminate a potential vmd core dump issue when the EMM initialization failed. -------------------------------------------------------------------------------- Etrack Incident = ET1386062 Description: The required tape parameters for NetBackup were not being set correctly on multi-path drives on AIX platforms. Only the first path had extended files marks and variable block set correctly. -------------------------------------------------------------------------------- Etrack Incident = ET1386073 Description: Could not delete the virtual_machine machine type with the nbemmcmd command. -------------------------------------------------------------------------------- Etrack Incident = ET1383727 Description: Policy Execution Manager would schedule a disk staging policy to run when it should not. This happened because a policy event was not sent to the Policy Execution Manager when a disk staging schedule was added. -------------------------------------------------------------------------------- Etrack Incident = ET1383766 Associated Primary Etrack = ET1369292 Titan cases: 320-121-094 Description: If a policy had a client named more than once with different aliases, the Policy Execution Manager (PEM) would start both even though only one was requested. If the backup was a user in which bprd supplies the jobid, it would use the same jobid for both jobs and would assert when trying to add it to the map. A fix was added to ensure that a client is not specified more than once in a policy by different names. -------------------------------------------------------------------------------- Etrack Incident = ET1386069 Associated Primary Etrack = ET1266200 Description: Running bpgetmedia would not return tapes from all robots. -------------------------------------------------------------------------------- Etrack Incident = ET1384960 Description: Calling changeMediaDBAllMediaForServer with NetBackup Access Control (NBAC) enabled would fail.

-------------------------------------------------------------------------------- Etrack Incident = ET1386075 Associated Primary Etrack = ET1366874 Titan cases: 240-724-837 Description: The performance of the API which lists shared drives and hosts would decreases significantly as the amount of hosts and drives increased. -------------------------------------------------------------------------------- Etrack Incident = ET1386077 Titan cases: 240-829-613 Description: An SQL error was received when attempting to delete a cluster. -------------------------------------------------------------------------------- Etrack Incident = ET1384019 Associated Primary Etrack = ET1273804 Titan cases: 281-334-212 Description: Setting the Media Mount timeout to a value other than 0 minutes can sometimes result in the Media Mount Timeout occurring even if the mount succeeds. A chance signal timing issue resolved this problem. -------------------------------------------------------------------------------- Etrack Incident = ET1386065 Description: When the initial try of an Exchange VSS snapshot parent job failed, the second try would fail with a status 801. -------------------------------------------------------------------------------- Etrack Incident = ET1386070 Description: The bpmedialist command, when given parameters involving a particular media ID whose length is less than six characters, would fail. Workaround: If you should encounter this issue, execute the command with the volume name enclosed in double quotes and padded by spaces so that the length of the volume name is six characters. -------------------------------------------------------------------------------- Etrack Incident = ET1387046 Description: When attempting to run an Oracle backup on a Master server that is configured with the Required_Interface setting, bpdbsbora would fail to connect and the job failed with a status 29. This occurred because nbjm did not pass the "-ri <reqd interface>" option to the bpbrm command line by nbjm. The NetBackup Job Manager passed the new option only if the media server version was 6.5.2 or greater. Since nbrb is returning the media server version as 0, nbjm did not pass the new "-ri <reqd interface>" option. -------------------------------------------------------------------------------- Etrack Incident = ET1383743 Associated Primary Etrack = ET1318931 Titan cases: 220-337-034

Description: Implementing media_deassign_notify script resulted in <defunct> processes. Workaround: To resolve this issue, setIgnoreSigChild() was added to OrbService() to ensure that EMM does not leave <defunct> processes when children complete from NOTIFY script execution. -------------------------------------------------------------------------------- Etrack Incident = ET1384952 Associated Primary Etrack = ET1374144 Titan cases: 320-123-939 Description: Duplication of NDMP disk image to tape would fail with a status 191 error. -------------------------------------------------------------------------------- Etrack Incident = ET1387039 Description: Libraries that provide self-cleaning would sometimes cause normal media to be frozen if they self-clean very quickly after a normal media was unloaded. -------------------------------------------------------------------------------- Etrack Incident = ET1383643 Associated Primary Etrack = ET1321325 Titan cases: 281-358-993 Description: The following error would occur after an App_cluster was failed over. EMM status: Disk volume is down resource request failed(800) -------------------------------------------------------------------------------- Etrack Incident = ET1384946 Associated Primary Etrack = ET1361273 Titan cases: 320-121-830 Description: A change was made to address an nbjm core dump issue that occurred in BPCRConnector handleReferenceCnt. -------------------------------------------------------------------------------- Etrack Incident = ET1384943 Associated Primary Etrack = ET1316765 Titan cases: 220-338-008 Description: A change was made to address an nbjm core dump issue that occurred near JobState::endItemChange +1c0. -------------------------------------------------------------------------------- Etrack Incident = ET1388149 Description: The command line interface, nbdb_admin -validate, would not return the full result set on Windows platforms. Workaround: If you should encounter this issue, use the NbDbAdmin Windows user interface to run validation. --------------------------------------------------------------------------------

Etrack Incident = ET1384948 Associated Primary Etrack = ET1287214 Titan cases: 220-289-079 Description: The status code within the Try # was incorrect. The status code would show 0 even though it had failed and another attempt was made. -------------------------------------------------------------------------------- Etrack Incident = ET1383744 Associated Primary Etrack = ET1261795 Titan cases: 220-280-182 Description: Changes were made to improve slow resource allocations for jobs using storage unit (STU) groups and prioritized allocation. The behavior that was seen is thus: - An STU group is looked at and an STU is identified within the group. - The Enterprise Media Manager (EMM) finds a drive (even if it is waiting for an unload) on the highest ranking media server in the group (regardless if there are drives that are immediately available on other STU's in the group) - EMM then allocates that drive - without looking for any other available drives. - The process is repeated, again, not looking for any other STU's in the group (which have many available drives). -------------------------------------------------------------------------------- Etrack Incident = ET1386199 Associated Primary Etrack = ET1294136 Titan cases: 291-009-192 Description: On some T5220 systems running Solaris 10 SPARC, the system would hang during a reboot if windrvr6 was configured in the /etc/driver_aliases file to bind to QLogic devices. This issue can be prevented by installing FT server module windrvr6 only after the system boots. In addition, it can be impelemented in the configuration scripts - nbftsrvr_config and nbftsrvr To avoid hangs on subsequent reboots, remove windrvr6 entries from the /etc/driver_aliases file. -------------------------------------------------------------------------------- Etrack Incident = ET1384909 Associated Primary Etrack = ET1204445 Titan cases: 220-302-209 320-083-263 Description: After upgrading to NetBackup 6.5, 5.X DSSU images were not appropriately expired from disk, causing the DSSU to fill to capacity. Workaround: If you encounter this issue, you can invoke the nbdelete -allvolumes command repeatedly until images are removed from disk. -------------------------------------------------------------------------------- Etrack Incident = ET1389088 Associated Primary Etrack = ET1387311

Titan cases: 240-813-600 Description: Logging from vnet_cached_gethostbyname() would increase significantly in NetBackup 6.5.2 if VERBOSE = 5 in the bp.conf file. Workaround: To avoid this issue, reduce VERBOSE to a value less than 5. -------------------------------------------------------------------------------- Etrack Incident = ET1374330 Associated Primary Etrack = ET1374122 Titan cases: 311976123 Description: The UNIX pack install now supports IBM zSeriesRedHat and zSeriesSuSE client installs. -------------------------------------------------------------------------------- Etrack Incident = ET1388180 Description: The NetBackup Administration Consoles for Windows and Java, and the NOM user interface display "No" in the "Incompliance Column" for capacity-based licenses (for example, Flexible Disk, OpenStorage, and PureDisk) when an unlimited key is installed and the used capacity for the licensed feature is greater than 0. -------------------------------------------------------------------------------- Etrack Incident = ET1383756 Associated Primary Etrack = ET1304028 Titan cases: 291-010-529 Description: After an upgrade from NetBackup 6.5.1 to 6.5.2, a progress log message was missing and caused monitoring scripts to fail. -------------------------------------------------------------------------------- Etrack Incident = ET1388192 Associated Primary Etrack = ET1210846 Titan cases: 320-074-322 Description: A change has been made to address an issue that caused duplication from disk staging to fail with a status 50. The fix involved adding a missing acknowledge in bptm. bpduplicate sends put_short message to bptm as an acknowledge in communication, however bptm was missing a get_short message so it would hang while waiting for a get_long from message bpduplicate. -------------------------------------------------------------------------------- Etrack Incident = ET1382684 Associated Primary Etrack = ET1375497 Titan cases: 220-404-140 230-572-942 240-806-831 Description: The time required to start nbpem can be large when there are a number of client names in the client attributes list. Workaround: To avoid this issue, reduce the size of the client attributes list. --------------------------------------------------------------------------------

Etrack Incident = ET1383404 Associated Primary Etrack = ET1378835 Titan cases: 291-031-055 Description: Catalog backups initiated by Vault profiles were not restorable because no True Image Restore (TIR) information was generated. -------------------------------------------------------------------------------- Etrack Incident = ET1390335 Associated Primary Etrack = ET1167923 Titan cases: 230-482-665 240655547 311-873-262 Description: Certain backup and archive jobs would fail because of a timing issue with bpbrm. The following error string would be recorded in the bpbkar log. get_string_: protocol error - string read failed (Timer expired) Workaround: If you encounter this issue, try restarting the job to fix the issue. -------------------------------------------------------------------------------- Etrack Incident = ET1383742 Associated Primary Etrack = ET1238943 Titan cases: 220-250-211 Description: Changes were added to improve hostname caching. -------------------------------------------------------------------------------- Etrack Incident = ET1383761 Associated Primary Etrack = ET1319339 Titan cases: 220-369-133 281-386-485 291-011-047 Description: If a calendar schedule window spanned midnight, jobs were started at midnight, not when the calendar schedule window actually opened. Also, calendar schedules that span midnight could fail at midnight with a status 196. -------------------------------------------------------------------------------- Etrack Incident = ET1391168 Associated Primary Etrack = ET1198807 Titan cases: 240707776 Description: In the NOM user interface, the Reports were not being emailed after a few days, however, the reports would appear as "Sending Email..." in the status column. -------------------------------------------------------------------------------- Etrack Incident = ET1382623 Associated Primary Etrack = ET1297752 Titan cases: 290-937-204 Description: Restore of a backup with a large number of mangled filenames can be slow due to searching the file @MaNgLeD.<pid> to find the non-mangled name. -------------------------------------------------------------------------------- Etrack Incident = ET1391109

Description: bpjobd would core dump on some platforms while changing the job priority dynamically. -------------------------------------------------------------------------------- Etrack Incident = ET1383763 Associated Primary Etrack = ET1321939 Titan cases: 220-335-223 291-058-053 Description: Script-based BLI incremental backups would run as full backups after an upgrade from NetBackup 6.5.1 to 6.5.2. The Scheduler was starting bpbrm for incremental BLI backups with inappropriate options that forced a full backup. -------------------------------------------------------------------------------- Etrack Incident = ET1394025 Associated Primary Etrack = ET1382322 Titan cases: 281-251-179 Description: If the MPX was greater than 1 within the policy schedule, then the checkpoints on the disk backups would hang. -------------------------------------------------------------------------------- Etrack Incident = ET1383630 Associated Primary Etrack = ET1319057 Titan cases: 220-371-648 291-015-879 Description: SQL Server backups would failed with a Status 6 and "SET SNAP_ID" errors. -------------------------------------------------------------------------------- Etrack Incident = ET1392132 Associated Primary Etrack = ET1363804 Titan cases: 291-026-369 Description: The granular_proxy option has been added in bpjava. This was required for the Exchange policy for NetBackup 6.5.2 and above. This fix ensures that the BPRD_BPLIST protocol/224 will be executed correctly for the Exchange policy type. -------------------------------------------------------------------------------- Etrack Incident = ET1388236 Associated Primary Etrack = ET1252473 Titan cases: 320-105-171 320-122-006 Description: bpgp was removed, and a replacement to set and get the include and exclude lists from clients was not provided. -------------------------------------------------------------------------------- Etrack Incident = ET1384020 Associated Primary Etrack = ET1276427 Titan cases: 220-269-379 Description: A change was made to address an issue where a Storage Lifecycle Policy (SLP) would attempt to duplicate an image even when all of the required copies were already made.

-------------------------------------------------------------------------------- Etrack Incident = ET1395057 Associated Primary Etrack = ET1394282 Titan cases: 311-968-542 Description: Basic disk staging jobs would always start with a priority of 99999 even if the priority defined in staging schedule was different. -------------------------------------------------------------------------------- Etrack Incident = ET1384919 Description: The duplication manager should process successful backup-only images as lifecycle complete even if the lifecycle is inactivated. As of NetBackup 6.5.2, the duplication manager would ignore all images if the lifecycle is inactivated. This was to stop any duplication jobs running for such images while backups are happening. However, this also stops the processing of backup-only (ITC) images that have created expected backup copies to be considered as lifecycle complete. Therefore, until the lifecycle is not activated back, such images, though have been completed, will sit as lifecycle incomplete and will not expire even if their expiration date arrives. -------------------------------------------------------------------------------- Etrack Incident = ET1383792 Description: A change was added to address an issue that caused duplication jobs for a Storage LifeCycle Policy to not run. -------------------------------------------------------------------------------- Etrack Incident = ET1383772 Associated Primary Etrack = ET1378715 Description: Shared disk images were not being deleted from the LUN's. -------------------------------------------------------------------------------- Etrack Incident = ET1393919 Description: The nbemmcmd command would crash if the emmname parameter provided was longer than the emmname parameter in the bp.conf file. -------------------------------------------------------------------------------- Etrack Incident = ET1384032 Associated Primary Etrack = ET1366836 Titan cases: 311-972-942 320-124-684 Description: SLP would not remove the NDMP tape copies or image records from EMM even after expiration occurred. -------------------------------------------------------------------------------- Etrack Incident = ET1384023 Associated Primary Etrack = ET1297806 Titan cases: 220-320-623

Description: Duplication of an image after it is SLP complete would result in re-insertion in EMM. Additional Notes: When nbstlutil lists backups, the images that were previously listed in an UNKNOWN state were now labeled as NOT MANAGED. -------------------------------------------------------------------------------- Etrack Incident = ET1384966 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048 Description: When there were many lifecycle-managed backups needing to be completed, it would take inordinately long to process them. -------------------------------------------------------------------------------- Etrack Incident = ET1395393 Associated Primary Etrack = ET1316801 Titan cases: 220-336-949 Description: A change was made to resolve a deadlock issue between BRMComm and ExportedResourceMgr where the BRMComm and ERM locks were being obtained in reverse order. -------------------------------------------------------------------------------- Etrack Incident = ET1383506 Associated Primary Etrack = ET1375866 Titan cases: 320-122-461 Description: SAP with RMAN restore would fail because of a missing Oracle license. The Oracle license was not required for SAP backup or restore. -------------------------------------------------------------------------------- Etrack Incident = ET1396153 Description: NOM could not export Job logs from the Job details page. -------------------------------------------------------------------------------- Etrack Incident = ET1391110 Description: If a storage lifecycle is configured without duplication copies and if one of the backup copies is configured with "Expire After Duplication", then the copy (and the image if there was only a single backup copy) is expired from the catalog by the storage lifecycle. However, this is an incorrect configuration and the "Expire After Duplication" retention type should not be allowed for backup destinations if there are no duplication destinations in the storage lifecycle. -------------------------------------------------------------------------------- Etrack Incident = ET1397984 Description: The std::istringstream.str string did not work on a TRU64 platform to initialize an istringstream object. -------------------------------------------------------------------------------- Etrack Incident = ET1399794

Description: Missing content was added to the NetBackup UNIX help that appears in the NetBackup Archive and Restore interface. -------------------------------------------------------------------------------- Etrack Incident = ET1393810 Description: A change was added to resolve an NBPEM core dump issue that occurred on a Tru64 master server. -------------------------------------------------------------------------------- Etrack Incident = ET1393798 Description: A change was made to address a core file issue that was generated by nbshareddisk when formatting Shareddisk LUNs using the -novm option. -------------------------------------------------------------------------------- Etrack Incident = ET1397604 Description: Unable to delete an app_cluster machine record. -------------------------------------------------------------------------------- Etrack Incident = ET1398627 Associated Primary Etrack = ET1397478 Titan cases: 320-129-580 Description: The NetBackup Service Layer (nbsl) was consuming too many file descriptors when NOM was enabled. -------------------------------------------------------------------------------- Etrack Incident = ET1388000 Associated Primary Etrack = ET1380098 Titan cases: 220-371-768 Description: Some of the values in LIFECYCLE_PARAMETERS file did not have reasonable upper limits for enterprise environments. For example, the MIN_KB_SIZE_PER_DUPLICATION_JOB and MAX_KB_SIZE_PER_DUPLICATION_JOB parameters are internally read into long type variables that would overflows before a reasonable value could be met. -------------------------------------------------------------------------------- Etrack Incident = ET1387827 Description: A change was made to address a nbstserv core dump issue that caused duplication job to longer run. -------------------------------------------------------------------------------- Etrack Incident = ET1393793 Associated Primary Etrack = ET1386040 Titan cases: 311-991-329 Description: There would be slow performance for bptm -delete_all_expired when attempting to deassign media that had expired before all the fragments had been duplicated to their final destination. --------------------------------------------------------------------------------

Etrack Incident = ET1396248 Description: In SLP, if the duplication STU is "any available", it could also pick the basic disk STU. -------------------------------------------------------------------------------- Etrack Incident = ET1402394 Description: Storage servers and snap vault filers were being listed as NDMP in nbemmcmd. The verbose output will indicate that these servers are snap vault and storage server. -------------------------------------------------------------------------------- Etrack Incident = ET1396112 Description: A change was made to address issue that would cause NBJM crash on shutdown on Linux. -------------------------------------------------------------------------------- Etrack Incident = ET1395233 Titan cases: 311-907-984 Description: ltid would hang if REQUIRED_INTERFACE was specified and the EMM server was rebooted. -------------------------------------------------------------------------------- Etrack Incident = ET1402922 Description: LTID would send an UpdateMountStat request with a corrupted MediaId parameter. -------------------------------------------------------------------------------- Etrack Incident = ET1403920 Description: A change was made to address a BPTM core dump issue that would occur on AIX and HP-UX media servers. -------------------------------------------------------------------------------- Etrack Incident = ET1405290 Associated Primary Etrack = ET1288659 Titan cases: 320-111-170 Description: The "Failover" selection method of storage unit groups may not be respected with multiplexing set. -------------------------------------------------------------------------------- Etrack Incident = ET1402967 Description: In BAR user interface, after selecting the "Point in Time Rollback" option, the backed-up images were not visible in the Restore tab. -------------------------------------------------------------------------------- Etrack Incident = ET1320530 Description:

If a synthetic schedule is added to a policy after the regular schedules have run and created the streams file information, immediate execution of the schedule will fail with a 200 status and scheduled execution never happens. This is due to missing streams file information. Workaround: If you encounter this issue, run a non-synthetic backup after adding the synthetic schedule. -------------------------------------------------------------------------------- Etrack Incident = ET1398698 Associated Primary Etrack = ET1383617 Titan cases: 240-806-831 Description: The nbpem startup can be slow in large environments with a large number of clients. Jobs are not scheduled until nbpem startup is complete. -------------------------------------------------------------------------------- Etrack Incident = ET1396083 Description: A change was added to address an nbpem core dump issue that would occur on Linux after a hot catalog backup job completed. -------------------------------------------------------------------------------- Etrack Incident = ET1392668 Description: Checkpointed jobs were not resumed automatically after a cluster failover. -------------------------------------------------------------------------------- Etrack Incident = ET1409131 Associated Primary Etrack = ET1206358 Titan cases: 281-179-782 Description: NetBackup performance, both its daemons or services and in the user interface, will be negatively impacted when DNS services are slow to return hostname or reverse-IP lookups. Because all hostnames and aliases on a master or media server may be examined while accepting or creating a connection, if some of these names are not in the DNS, and the DNS environment is slow to respond, this will delay NetBackup, and cause the user interface to be non-responsive. This change logs the offending hostname whenever such a lookup takes longer than five seconds, making it easier to know what to clean out of a configuration. The new log messages look like the following: 10:10:23.918 [25766] <2> vnet_cached_gethostbyname: vnet_hosts.c.377: DNS lookup slow for host: : kermit.frog.com 10:10:24.395 [25766] <2> vnet_cached_gethostbyname: vnet_hosts.c.378: DNS lookup elapsed time: : 30 0x0000001e The elapsed time is in seconds. -------------------------------------------------------------------------------- Etrack Incident = ET1409154 Description: When suspended jobs were resumed more than once, it would cause jobs to

fail with a status 801. -------------------------------------------------------------------------------- Etrack Incident = ET1411251 Associated Primary Etrack = ET1285409 Titan cases: 290-994-546 Description: The Remote Windows XP Administration Console would display the pop-up, COMM_FAILURE (IDL:omg.org/CORBA/COMM_FAILURE:1.0), when accessing media. -------------------------------------------------------------------------------- Etrack Incident = ET1411776 Titan cases: 230-572-386 Description: The first fragment written by BPTM will not be position checked, allowing a rogue rewind to go undetected. If a rogue rewind occurred during the time between reading the empty header and writing the first backup header, the rewind could go undetected. -------------------------------------------------------------------------------- Etrack Incident = ET1410874 Associated Primary Etrack = ET1402736 Titan cases: 320-130-796 Description: Unable to perform a multi-stream FlashBackup using an "old" method, such as not using Snapshot Client options. -------------------------------------------------------------------------------- Etrack Incident = ET1412331 Description: With Snapshot destination in SLP, there was a difference in the value of the Storage unit in NetBackup-Java Administration Console and in the "nbstlutil list". A change was added so when a Snapshot destination is in SLP, the backup destination and duplication destination will pick up the actual STU. -------------------------------------------------------------------------------- Etrack Incident = ET1408807 Description: A PIT Restore with an HPEVA_Snapclone FIM type would fail if there were two resources (for example, two storage stacks - HPEVA UDID, HPLVM, or VxFS FileSystem) in the backup selection. -------------------------------------------------------------------------------- Etrack Incident = ET1412417 Description: A fix was made to address an nbrmms core dump issue that would occur because of a memory access violation in the VxFI code. -------------------------------------------------------------------------------- Etrack Incident = ET1413338 Description: An inaccurate log message was being written when bpdbm failed to update a STREAMS file in image validation. --------------------------------------------------------------------------------

Etrack Incident = ET1411302 Associated Primary Etrack = ET1269930 Titan cases: 220-289-048 Description: A change was made to resolve an nbstserv core dump issue that would occur while processing a large number of images. -------------------------------------------------------------------------------- Etrack Incident = ET1413269 Associated Primary Etrack = ET1414241 Description: Jobs were not being scheduled for a newly added policy. -------------------------------------------------------------------------------- Etrack Incident = ET1410786 Description: Jobs for a policy with multi-streaming enabled and with a bad client name failed with status 200. -------------------------------------------------------------------------------- Etrack Incident = ET1413572 ET1385085 Associated Primary Etrack = ET1381455 ET1288113 Titan cases: 230-534-351 281-379-673 220-289-644 Description: NBJM would cancel a duplication job (larger backups consistently fail with status 50) that was initiated using Storage Lifecylce Policies (SLP). -------------------------------------------------------------------------------- Etrack Incident = ET1414212 Associated Primary Etrack = ET1222342 Titan cases: 220-208-577 Description: Running bpjobd -cleanup on a large number of jobs in conjunction with bpduplicate may result in a status 12 or status 50 error. This would likely happen in a large environment where the nightly pruning of the jobs database could take in upwards of ten minutes. Workaround: If you encounter this issue, perform more frequent recycling with fewer jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1412557 Description: Multiple jobs for the same policy, client, and schedule combination would erroneously run simultaneously, or nearly so. -------------------------------------------------------------------------------- Etrack Incident = ET1415612 Associated Primary Etrack = ET1415270 Titan cases: 220-411-437 291026372 Description: A fix has been added to resolve an error that would occur when attempting to browse directories with apostrophes in the name. A similar fix was provided to resolve "Invalid Character" errors that would occur

when selecting directories with an ampersand (&) character in the name. -------------------------------------------------------------------------------- Etrack Incident = ET1413649 Associated Primary Etrack = ET1407104 Titan cases: 320-129-510 Description: Storage Lifecycle Policy (SLP) duplications would create one batch per image for a tape with multiple images. -------------------------------------------------------------------------------- Etrack Incident = ET1401482 Description: An old image was not being deleted for more space in lifecycle storage unit when the "staged capacity managed" retention type was selected. The job would fail with the error, "Disk storage unit is full" and a status 129. -------------------------------------------------------------------------------- Etrack Incident = ET1413567 Description: Duplicate, restore, and verify from a NearStore FSE Storage Unit would fail with the following error. "Cannot read image from disk, Invalid argument" -------------------------------------------------------------------------------- Etrack Incident = ET1415683 Description: A change was made to address an issue that caused NBPEM to stop scheduling jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1414541 Description: The restore functionality would fail with an HPLVM stack for Oracle Snapshot backup. -------------------------------------------------------------------------------- Etrack Incident = ET1416768 Description: bptm would core dump when a Nearstore restore failed due to slow network issues. -------------------------------------------------------------------------------- Etrack Incident = ET1421025 Description: Jobs started to backup transaction logs for an SQL policy configured with instant recovery and off host backup would fail with a status 41. -------------------------------------------------------------------------------- Etrack Incident = ET1425093 Description: During stress testing, the event manager service would occasionally go down and come back up. nbpem asserted:!m_getAllNamesCall PemPolicyCache.cpp 104 while stress testing nbevtmgr with repeated start, stop, and sending events.

-------------------------------------------------------------------------------- Etrack Incident = ET1424266 Associated Primary Etrack = ET1417414 Titan cases: 240-828-934 Description: Policies with schedules set to frequency of 52 weeks and multi-stream would fail with a status 196 with nbpem v5. -------------------------------------------------------------------------------- Etrack Incident = ET1423453 Description: Suspended jobs for an inactive policy could not be resumed after a failover. -------------------------------------------------------------------------------- Etrack Incident = ET1425900 Associated Primary Etrack = ET1416156 Titan cases: 220-406-370 **Description: If a VCB proxy backup of a virtual node joins an MPX group, all subsequent normal jobs in that MPX group would back up the proxy host. Workaround: The following list contains workarounds for this issue: - Turn off multiplexing on the VCB backups. - Run the VCB backups on a different storage unit. - Use a different volume pool for the VCB backups. For additional information about this issue, refer to the following TechNote on the Symantec Support Web site. http://entsupport.symantec.com/docs/308906 -------------------------------------------------------------------------------- Etrack Incident = ET1425285 Description: When a cluster failover was initiated while a duplication job was active, the bpdbm child processes that were active for the duplication job could take a long time to terminate. -------------------------------------------------------------------------------- Etrack Incident = ET1428096 Associated Primary Etrack = ET1409844 Titan cases: 220-406-066 Description: A change was made to address an nbpem version 4 issue (originating in ET1322956), mixed calendar schedule types in policies, where the daily WCT evaluates to 23:59:59, resulting in a status 196 error. -------------------------------------------------------------------------------- Etrack Incident = ET1423583 Description: Duplication jobs would fail with a status 50, but continue on to complete the duplication. -------------------------------------------------------------------------------- Etrack Incident = ET1426958

Description: If a multi-streamed policy with multiple schedules is blocked by failure history, the child job that runs after the failure history is expired may fail with a status 196. -------------------------------------------------------------------------------- Etrack Incident = ET1427064 Description: Storage Lifecycle Policies processing was failing occasionally while processing images with a large number of fragments because the bpdbm connection was timing out. -------------------------------------------------------------------------------- Etrack Incident = ET1429629 Description: If PEM restarted with a parent and child job in a WAITING_FOR_RETRY state, it would retry the child job only. After the child job completed, no more jobs were scheduled for this policy/client. -------------------------------------------------------------------------------- Etrack Incident = ET1430825 Associated Primary Etrack = ET1373028 Titan cases: 311-971-198 Description: For duplicate multiple copies, all duplicate jobs would fail if any of the Disk Copies have a Dummy Allocation supplied when executing on Windows. -------------------------------------------------------------------------------- Etrack Incident = ET1428794 Description: nbstserv would halt processing while waiting for an nbdelete call to complete. -------------------------------------------------------------------------------- Etrack Incident = ET1431220 Description: A failed attempt to validate a copy during a duplication job was holding a write lock on the image file and causing other bpdbm child processes to hang until the duplication job finished. -------------------------------------------------------------------------------- Etrack Incident = ET1428632 Description: Changes were made to address two memory leak errors found in the VxFI code that lead to a SharedDisk backup failure. -------------------------------------------------------------------------------- Etrack Incident = ET1432786 Associated Primary Etrack = ET1424199 Titan cases: 281-416-722 Description: A change has been made to address an issue that could cause file system corruption on a Disk. This issue would cause a media server to go into a

panic state while mounting a corrupted file system. The fix ensures that the mount operation verifies the device mount state independent of the return code of the mount command. -------------------------------------------------------------------------------- Etrack Incident = ET1431217 Description: Bpduplicate would not allow a copy of a backup to be started if another duplication for the same backup was in progress. Also, if more than one duplication to different destination copies from the same disk source copy occurs simultaneously, the duplications would either hang or error. Workaround: To work around the simultaneous duplications from the same disk source copy hang or error issue, disable shared memory duplications. Touch the following file on the master server: UNIX: /usr/openv/netbackup/NOSHMDUP Windows: <installed_path>\NetBackup\NOSHMDUP -------------------------------------------------------------------------------- Etrack Incident = ET1431957 Associated Primary Etrack = ET1417636 Titan cases: 311-991-075 Description: EMM would crash because it was not handling a CNOS exception that was leaked through the Event Manager supplier-side library. The createConnectObjects() method makes calls directly to CNOS but in some cases it does not surround those calls in try/catch blocks. This caused CNOS exceptions to be leaked to the caller, in this case EMM. EMM catches specific exceptions; those not caught are pushed up the stack until it exits as an unhandled exception. -------------------------------------------------------------------------------- Etrack Incident = ET1432152 Description: A change was made to address an Incremental backup data loss issue that would occur if bpbkar took more than 10 seconds to start. -------------------------------------------------------------------------------- Etrack Incident = ET1432733 Description: A failed job waiting to be retried would prevent a job session from being closed. Therefore, the cold catalog backup to be run at the end of session was delayed until after all of the job-tries end and the job is done. -------------------------------------------------------------------------------- Etrack Incident = ET1431905 Description: A change was made to address an issue that caused nbpem to be caught in an infinite loop, resulting in no jobs being able to start. --------------------------------------------------------------------------------

Etrack Incident = ET1436492 Associated Primary Etrack = ET1368270 Titan cases: 240-779-778 Description: During a True Image Restore (TIR) data backup, if the socket used to get the data failed, the format of the tape could be written incorrectly. -------------------------------------------------------------------------------- Etrack Incident = ET1436738 Associated Primary Etrack = ET1400885 Titan cases: 291-058-781 Description: The requested Start Time calculation caused a full backup to be scheduled repeatedly if the last incremental backup occurred between windows and the frequency was a multiple of 24 hours. To fix this issue, pre-window checking was added so that if the last backup falls between windows, the due time can pick up the next window even if it is the same day. -------------------------------------------------------------------------------- Etrack Incident = ET1439637 Description: A change has been added to address a core dump issue that would occur with nbdelete. -------------------------------------------------------------------------------- END UNIX Server ========================================================================

NetBackup Operations Manager (NOM) Servers (Windows and UNIX) ======================================================================== Etrack Incident = ET1383447 Associated Primary Etrack = ET1221135 Titan cases: 281-228-428 Description: NOM server service would stops periodically. To address this issue, a script has been created that bounces the NOM services every day. -------------------------------------------------------------------------------- Etrack Incident = ET1384380 Associated Primary Etrack = ET1360645 Titan cases: 320-119-867 Description: Hyperlinks in emailed graphics would point to the local host instead of the NOM server. -------------------------------------------------------------------------------- Etrack Incident = ET1390067 Associated Primary Etrack = ET1241426 Titan cases: 220-254-383

Description: The NOM reports would show the JobState as a value of "3" instead of "Done". -------------------------------------------------------------------------------- Etrack Incident = ET1391161 Associated Primary Etrack = ET1138505 Titan cases: 290-826-518 Description: When using NOM, a problem existed that caused the pie charts on the Monitoring - Overview page to always show as unavailable. -------------------------------------------------------------------------------- Etrack Incident = ET1395092 Associated Primary Etrack = ET1285555 Titan cases: 320-110-980 Description: Once media appeared as deleted it would not be displayed under Managing > Media > Details. -------------------------------------------------------------------------------- Etrack Incident = ET1399345 Description: In the NOM user interface, a change was made to ensure that you are able to create a group in Client Context window. -------------------------------------------------------------------------------- Etrack Incident = ET1409923 Associated Primary Etrack = ET1398505 Titan cases: 320-127-406 Description: The Available catalog space alert was incorrectly stating that there was not enough space available. -------------------------------------------------------------------------------- Etrack Incident = ET1409925 Associated Primary Etrack = ET1409938 Description: Alerts were not working at the server group level. -------------------------------------------------------------------------------- Etrack Incident = ET1423226 Associated Primary Etrack = ET1411090 Titan cases: 220-406-993 Description: Schedules for reports in NOM were not showing up after an upgrade from NetBackup 6.0 MP4 to 6.5.2. -------------------------------------------------------------------------------- END NOM Windows and UNIX =========================================================================

Java: Windows and UNIX

========================================================================= Etrack Incident = ET1316222 Associated Primary Etrack = ET1300428 Titan cases: 320-117-507 Description: The Activity Monitor jobs data was displayed wrong when using a NetBackup 6.5.2 administration console with a NetBackup 6.5.1 master server. -------------------------------------------------------------------------------- Etrack Incident = ET1316255 Associated Primary Etrack = ET1292734 Titan cases: 220-320-996 Description: A change was made that ensures the NetBackup_Java Administration Console can display the Activity Monitor when administering a NetBackup 6.5.1 master server. -------------------------------------------------------------------------------- Etrack Incident = ET1316257 Associated Primary Etrack = ET1297807 Titan cases: 220-326-939 Description: A change has been added that ensures the NetBackup-Java Administration Console can be used to administer (modify or deactivate policies) on back-level, NetBackup master servers. -------------------------------------------------------------------------------- Etrack Incident = ET1383469 Associated Primary Etrack = ET1369746 Titan cases: 311-971-197 Description: The NetBackup-Java Administration Console would fail to connect to the NetBackup Service Layer (NBSL) service using PBX if the primary hostname returned by PBX was not resolvable from NetBackup-Java Administration Console host. Workaround: If you encounter this issue, use the FIREWALL_IN option in the nbj.conf file on NetBackup-Java Administration Console host. -------------------------------------------------------------------------------- Etrack Incident = ET1386728 Associated Primary Etrack = ET1363804 Titan cases: 291-026-369 Description: An error would occur if you select a directory to restore and the name of the directory contained an & (ampersand) character in it. You would receive an Invalid Character error. Backups of directories that have an & (ampersand) character in the name would perform okay. However, when these directories are selected in either the NetBackup-Java Administration Console or the Windows

Administration Console, an error would still occur. In addition, directories that have an & (ampersand) character in the name can be restored in full, but you are unable to enter the directories to select individual sub-directories or files within. -------------------------------------------------------------------------------- Etrack Incident = ET1388080 Associated Primary Etrack = ET1273691 Titan cases: 320-103-515 Description: On NetBackup-Java Administration Console, the Vault - "Robotic Volume Group" drop-down would take between 15 and 30 minutes to populate. -------------------------------------------------------------------------------- Etrack Incident = ET1400256 Description: The "View FT Connections" would not display under Media-Devices when a backup was in progress. -------------------------------------------------------------------------------- END JAVA Windows and UNIX ========================================================================

Bare Metal Boot Server (BBS) and Bare Metal Restore (BMR) ========================================================================= Etrack Incident = ET1386047 Associated Primary Etrack = ET1381364 Titan cases: 230-574-358 Description: AIX client restoration would hang indefinitely early in the restore process. -------------------------------------------------------------------------------- Etrack Incident = ET1383479 Associated Primary Etrack = ET1211323 Titan cases: 290-900-314 290-919-097 Description: When the BMR boot server is started it tries to register itself with BMR master server. If the BMR master server is down or the BMR database is not up it tries to register itself, it gets either a Network Failure error or a registration failed error. If registration is not successful then BMR boot server sends a registration request to the master server every 30 seconds. For each registration request the BMR boot server produces a memory leak and it decreases the performance in the machine. Workaround: If you encounter this issue do one of the following: If the BMR master server daemon "bmrd" is down then shut down the BMR

boot server daemon "bmrbd". OR If BMR database is not yet configured then run bmrsetupmaster on the command line interface (CLI) to configure the database and then re-start the bmrd and bmrbd daemons. -------------------------------------------------------------------------------- Etrack Incident = ET1289330 Description: Changes have been added to ensure that the BMR database levels match those of the NetBackup server. -------------------------------------------------------------------------------- Etrack Incident = ET1385881 Associated Primary Etrack = ET1297511 Titan cases: 311-927-527 Description: When adding a driver package to a BMR-Windows Client's configuration, the operation takes a long time. While performing a Prepare To Restore (PTR) for a BMR client on such a setup, the PTR operation would also take a long time to complete. Additional Notes: The problems described above are due to some unnecessary redundancies in the BMR database. A fix has been added to make sure that no new unnecessary redundancies get added to the database, but it does not eliminate the existing, unnecessary redundancies from the BMR database. Please contact Symantec Support for help on removing the existing unnecessary redundancies. END BBS_BMR =========================================================================

DB2 Database Agent

========================================================================= Etrack Incident = ET1388132 Description: Could not perform a restore from an incremental backup with DB2 v9.5 on an AIX platform. END DB2 ========================================================================

Informix Database Agent =========================================================================

Etrack Incident = ET1404905 ET1416672 Description: Added Linux x86 support for Informix (32 and 64 bit). END Informix ========================================================================

Lotus Notes Database Agent

========================================================================= Etrack Incident = ET1318437 Associated Primary Etrack = ET1301899 Titan cases: 240-788-962 Description: Lotus Notes databases that were larger than 2GB would be treated as links and skipped from the backup. END Lotus Notes ========================================================================

SAP Database Agent ======================================================================== Etrack Incident = ET1227447 Associated Primary Etrack = ET1213039 Titan cases: 320-084-538 Description: For SAP restores, the restore status per file is posted to the brrestore detail log when the file has been restored (or failed to restore if that is the case) rather than posting the restore status for all files when the restore has ended. Additional Notes: This capability is only applicable for UNIX platforms. -------------------------------------------------------------------------------- Etrack Incident = ET1386537 Associated Primary Etrack = ET1384642 Titan cases: 291-042-388 Description: If number of streams (drives in util file) configured is more than 64 and the "sort_backup_type" is specified as "device", then only the files from 64 devices are getting backed up. The remaining files are ignored and no error status is reported. Workaround: If file list is from more than 64 devices, then DO NOT use "device" as "sort_backup_type". And the number of streams should be specified as less than or equal to 64.

-------------------------------------------------------------------------------- Etrack Incident = ET1227458 Description: Media-related information was NOT written in the BRTOOL's detailed logs. -------------------------------------------------------------------------------- Etrack Incident = ET1411527 Associated Primary Etrack = ET1380465 Titan cases: 320119717 Description: If the backup image is more than 2TB, then the restore job from that image would fail with a status 174. END SAP =========================================================================

NetBackup LiveUpdate Agent ========================================================================= Etrack Incident = ET1380529 Description: LiveUpdate will no longer start NetBackup services after a partially successful installation. END LiveUpdate =========================================================================

NetBackup Snapshot Client

========================================================================= Etrack Incident = ET1383582 Associated Primary Etrack = ET1377498 Titan cases: 230-581-012 291-068-284 Description: Optimized duplication would ignore the retention level sent for a destination copy and would set the expiration time and retention using values from the source copy. -------------------------------------------------------------------------------- Etrack Incident = ET1383429 Associated Primary Etrack = ET1323221 Titan cases: 311-963-863 Description: The NetBackup Service Layer (NBSL) would core dump when NOM had data collection enabled. -------------------------------------------------------------------------------- Etrack Incident = ET1382596

Description: A change was made to ensure that the Snapshot Client cleans up the temporary files when it is finished. -------------------------------------------------------------------------------- Etrack Incident = ET1383498 Associated Primary Etrack = ET1288299 Titan cases: 291-004-832 Description: A change was made to ensure the correct UDID string formation for the EMC Clariion CX-3 series of array with a RAID 6 configuration and FLARE26. -------------------------------------------------------------------------------- Etrack Incident = ET1384025 Associated Primary Etrack = ET1249855 Titan cases: 320-100-354 230-568-897 Description: A change was added to address a core dump issue that caused bpjobd to call t_delete whenever NOM was active. -------------------------------------------------------------------------------- Etrack Incident = ET1394039 Associated Primary Etrack = ET1292872 Titan cases: 220-268-467 Description: In VMware backups, if the virtual machine or the proxy server have a cluster size of 512 bytes, then backups of VMDK files would be corrupt. This was due to a problem in determining the offset into the backup image. -------------------------------------------------------------------------------- Etrack Incident = ET1395089 Associated Primary Etrack = ET1182999 Titan cases: 311-769-409 Description: FlashBackup multiple volume restores and VMware multiple volume restores would hang or fail. -------------------------------------------------------------------------------- Etrack Incident = ET1401373 Description: Make messages would fail because of the duplicated ID in the file sfr.c. -------------------------------------------------------------------------------- Etrack Incident = ET1398467 Associated Primary Etrack = ET1270509 Titan cases: 320-107-580 Description: FlashBackup backups would fail with a status 23 error code and bpdbm would fail with a "memory map invalid data" error message. -------------------------------------------------------------------------------- Etrack Incident = ET1383512 Associated Primary Etrack = ET1290612 Titan cases: 230-315-701 Description: An error would occur during a large size FS freeze for a VxFS shadowimage

snapshot. A FS flush timeout was added in the conf file to facilitate a timeout parameter for FS large in size that is greater than or equal to 10TB. -------------------------------------------------------------------------------- Etrack Incident = ET1410597 Description: VMware VCB Backup would attempt to connect to the virtual machine instead of through the proxy on HP-UX. =========================================================================

Data Management Protocol (NDMP)

========================================================================= Etrack Incident = ET1384031 Description: NDMP backup fails with a status 114 error. The ndmpagent log shows the following message. "Expected remainder to be 0. Remainder = 512" Workaround: If you encounter this issue, set the SIZE_DATA_BUFFERS parameter to 256k. (There is still a possibility the backup could fail, but it is unlikely.) Or you can run NDMP local, NDMP 3-way, or NDMP remote to disk. END NDMP =========================================================================

Storage Migrator ========================================================================= Etrack Incident = ET1387861 Associated Primary Etrack = ET1383520 Titan cases: 220-372-437 Description: migsetdb was logging the following errors: 08/07 12:38:55 [13979]migsetdb[22161]: ERROR: /tm database corrupted offset=540 Line: 000010C9 This is because it has created a structure with 16 fields per entry; the number of fields per entry was changed in the 6.5 release to be 17. -------------------------------------------------------------------------------- Etrack Incident = ET1387867

Associated Primary Etrack = ET1280901 Titan cases: 311-918-123 Description: The cache of a large file would fail if the primary copy volume could not be mounted; no attempt was made to cache from the secondary copy volume. =================================================================

Vault ================================================================= Etrack Incident = ET1383258 Associated Primary Etrack = ET1282306 Titan cases: 220-248-543 Description: Vault's eject mode suspend immediately would fail to suspend media if duplication was disabled. A fix was added to ensure that, media are suspended if the mode "suspend now" is chosen. -------------------------------------------------------------------------------- Etrack Incident = ET1385764 Associated Primary Etrack = ET1265226 Titan cases: 240-757-443 Description: Vault would eject more copies of catalog tapes than what it was configured to do. If you used Vault to perform catalog backups, the associated catalog backup policy was configured to generate two copies, one copy in the catalog-pool and the other copy in the CatalogBackup pool. If your intention was to keep the copy in the catalog-pool in the robot and to offsite the copy in the CatalogBackup pool, you would add only the CatalogBackup pool in the offsite volume pool of profile eject configuration. When Vault ran, it listed both catalog copies in the eject.list and ejected both copies. However, the Robot Pick List report listed only the CatalogBackup copy, thus, it was not reporting all of the tapes that were being ejected. -------------------------------------------------------------------------------- Etrack Incident = ET1386756 Associated Primary Etrack = ET1321650 Titan cases: 291-016-026 Description: The Application Backup setting did not select database backups in NetBackup 6.5.

Vault profile has enabled attributes filters and an Application backup filter was added in Backup Type filters. Vault skips application backup images for any further operations (duplication/original eject). Workaround: If you encounter this issue, configure the profile to use Backup Types as "Include All" or include "User backup" along with "Application Backup". -------------------------------------------------------------------------------- Etrack Incident = ET1385614 Associated Primary Etrack = ET1323578 Titan cases: 291-026-442 Description: The Vault tape batching algorithm was incorrect and caused an inefficient duplication. In an environment where images reside on common media or span media and multiplexing or media sharing is enabled, Vault would create a batch with overlapping media sets. This caused some drives to be idle while waiting for a previous batch to free the common media. -------------------------------------------------------------------------------- Etrack Incident = ET1386760 Associated Primary Etrack = ET1297359 Titan cases: 281-362-716 Description: A fix was added to handle multiple issues with Vault containers that are mentioned in the following list: - On adding media to an empty container, the return date would never get updated - On adding media to a non-empty container, the return date would never get updated - If a container was recalled and the same container was used to add new media, Vault would recall the newly added media due to the reasons mentioned above -------------------------------------------------------------------------------- Etrack Incident = ET1386763 Associated Primary Etrack = ET1365764 Titan cases: 291-027-125 Description: The Vault Session summary log was empty after a successful session. It used to provide brief session details in NetBackup 5.x versions. A fix was added to log meaningful Vault session details to the summary.log file. -------------------------------------------------------------------------------- Etrack Incident = ET1386750 Associated Primary Etrack = ET1270507 Titan cases: 311-914-328 Description: Image selection would take longer to run than previous versions (6.0 MP5). A different approach to compare hosts used in NetBackup 6.0 MP6 caused this issue. A fix was added to improve the image selection performance so that it is equal to the performance in NetBackup 6.0 MP5. --------------------------------------------------------------------------------

Etrack Incident = ET1396286 Description: If Vault retention mappings were configured, Vault would disregard the mappings with a target retention level of zero (0) and instead use the source copy's retention level for the new image copy. This was incorrect, because zero (0) was a valid retention level. -------------------------------------------------------------------------------- Etrack Incident = ET1402907 Associated Primary Etrack = ET1402687 Description: Images on a common set of media may be put in separate batches by Vault for duplication. This would cause some duplication jobs (and tape drives allocated for duplication) to remain idle while waiting for media reserved by other duplication jobs. -------------------------------------------------------------------------------- Etrack Incident = ET1404850 Associated Primary Etrack = ET861258 Titan cases: 280-660-746 Description: The NetBackup Administration Console for Windows would hang while generating Vault reports such as the Summary Distribution, pick list, inventory, etc. A fix was made to ensure that larger Vault reports are shown in Windows Administration Console. END Vault