Maintenance Pack NB_NOM_60_6_M provides fixes for Veritas NetBackup (tm) Operations Manager on Windows Servers.

Problem

Maintenance Pack NB_NOM_60_6_M provides fixes for Veritas NetBackup (tm) Operations Manager on Windows Servers.

Solution

NB 6.0GA Pack NB_NOM_60_6_M README February 7, 2008
================================================================================
This maintenance pack provides fixes to the Veritas NetBackup(tm) Operations
Manager (NOM) product for Windows servers.

The NetBackup Operations Manager Getting Started Guide was updated for
NetBackup 6.0 MP4. You can download a copy of that document by referring to
TechNote 285150 on the Symantec Support Web site.

http://entsupport.symantec.com/docs/285150

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


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

-- NOM requires VxSSAT (Veritas Authentication Service) to be installed
prior to the installation of this maintenance pack.

-- Check the compatibility matrices on the Support web site for operating
system (OS) dependencies and support issues.




I. NEW FEATURES AND PLATFORM PROLIFERATIONS
II. KNOWN ISSUES
III. DOWNLOAD INSTRUCTIONS
IV. INSTALLATION INSTRUCTIONS
V. UNINSTALL INSTRUCTIONS
VI. CURRENT MAINTENANCE PACK INDEX
VII. MAINTENANCE PACK CONTENT
Conventions
Current Maintenance Pack
NB_NOM_60_6_M
Maintenance Pack History
NB_NOM_60_4_M
NB_NOM_60_4_M
NB_NOM_60_2_M
NB_NOM_60_1_M


============================================
I. NEW FEATURES AND PLATFORM PROLIFERATIONS
============================================
Many new features, enhancements, and platform proliferations have been made
to NetBackup 6.0 MP6 in general. For a complete list of these additions, refer
to the New Features and Platform Proliferations section in the NB_60_6_M
online Readme that you installed prior to installing this package.

In addition to the list of features and proliferations in the NB_60_6_M
Readme, the following is a NOM-specific enhancement.

+ For NOM 6.0 through NOM 6.0 MP5, it was required that the release and patch
level of your NOM server was the same as your managed NetBackup servers. This
limitation has been resolved by providing backward compatibility functionality
with NetBackup that starts with NOM 6.0 MP6 (and NOM 6.5) onwards.

The following items identify if a NOM version is compatible with a NetBackup
master server version:

- NOM 6.0 MP6, (NOM 6.5), and higher versions can monitor NetBackup master
servers starting from version NetBackup 6.0 MP5.

- A NOM version can only monitor those NetBackup versions that were released
earlier than it. For example, NOM 6.0 MP6 (and NOM 6.5) can monitor a
NetBackup master server 6.0 MP5 which was released before it.

- NOM should always be at a higher or similar version as your NetBackup master
server.




=================
II. KNOWN ISSUES
=================

This section contains known issues with this maintenance pack that have not
yet been fixed in NetBackup. These issues will likely be fixed in future
Maintenance Packs for this version of NetBackup.

+ After installing a Japanese or Chinese language pack, you should restart
the NOM services to ensure that the user interface functions properly.




==========================
III. DOWNLOAD INSTRUCTIONS
==========================


Download instructions:

1) Download the NB_NOM_60_6_M.winnt.intel.exe file into a temporary directory.

2) Extract NB_NOM_60_6_M.winnt.intel.exe by double-clicking on it.

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




=============================
IV. INSTALLATION INSTRUCTIONS
=============================
** The content of this online Readme supersedes the information in the Readme
contained in the download. **

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

Before installing NOM, please review the following items:

Before installing NOM, please review the following items:

+ When installing a NetBackup maintenance pack, you must install the NOM 6.0 GA
release before you install this pack. Failure to install NOM in this order
results in the following error when installing this pack:

"The Veritas Maintenance Pack install was interrupted before it could be
completed".

+ Symantec recommends that you install NOM on a dedicated server. Installation
of the NOM server software on the same server as NetBackup master or media
server software is not recommended.

+ When upgrading to this version of NOM, Symantec will only support the
following upgrade paths.
- Upgrading NOM server software from a NOM 6.0 MP4 CDROM
- Upgrading NOM server software from the NOM 6.0 MP4 downloaded patch
- Upgrading NOM server software from NOM 6.0 MP5

The following upgrade paths will fail during installation and there will not
be any historical data loss.
- Upgrading NOM server software from a NOM 6.0GA to NOM 6.0MP6
- Upgrading NOM server software from a NOM 6.0MP1 to NOM 6.0MP6
- Upgrading NOM server software from a NOM 6.0MP2 to NOM 6.0MP6
- Upgrading NOM server software from a NOM 6.0MP3 to NOM 6.0MP6

If you currently have NetBackup 6.0, 6.0MP1, 6.0 MP2, or 6.0MP3 installed and
you want to upgrade NOM to this version, Symantec recommends that you follow
one of the suggested paths in the following list.
- From NOM 6.0GA, first upgrade to NOM 6.0MP4 and then to NOM 6.0MP6.
- From NOM 6.0MP1, first upgrade to NOM 6.0MP4 and then to NOM 6.0MP6.
- From NOM 6.0MP2, first upgrade to NOM 6.0MP4 and then to NOM 6.0MP6.
- From NOM 6.0MP3, first upgrade to NOM 6.0MP4 and then to NOM 6.0MP6.

+ If you upgrade multiple NetBackup master servers to NetBackup 6.0 MP6, you
should first stop NOM services, then upgrade your NOM server to 6.0 MP6.
After upgrading each master server to MP6, restart NOM services.

+ It may take a longer time than normal to install on the NOM server if Sybase
Anywhere is also installed on NOM server. Please verify that the NOM server
where you are trying to upgrade NOM does not have any instance of Sybase
Anywhere installed.




To install this pack:

1) Run setup.exe by double-clicking on the icon from File Manager or Windows
Explorer. Setup.exe can alternatively be run from the command prompt.

Setup.exe will stop the appropriate NOM services, install the necessary
files and restart NOM services.

2) (Optional) Remove the temporary directory created in the download
instructions.




=========================
V. UNINSTALL INSTRUCTIONS
=========================
**Important notice regarding un-installs on Windows**
Only the last Maintenance Pack installed on a Windows system can be un-installed.
Therefore, if more than one maintenance pack has been installed, only the most
recent version will be uninstalled.



To Uninstall:
-------------
1) Go to the Add/Remove programs dialog box and select the correct Pack to
be uninstalled and click Remove.

You will be prompted for confirmation. Click Yes to uninstall this pack.




==================================
VI. CURRENT MAINTENANCE PACK INDEX
==================================

This section contains a master index for all Windows packages of Etracks that
have been fixed in this release, sorted according to the containers that
they comprise.


NB_60_6_M.NT
------------
819221 1106653 1065715 1133900 1051431 1064859 917571 1100826 1050256 1077696
1104857 1075835 1047273 786040 1086515 962767 937157 971736 1019102 1060918
1075048 1075976 1101998 1110609 1102522 1111554 1108542 1112393 1111632 1099114
1116059 1089269 1081386 1109594 1118215 1118152 1115944 1119044 1053711 1122376
1056577 1016205 1103635 1116287 1032459 1122873 1078507 1081410 856463 1112364
1115046 1119141 609282 788886 1044598 1126542 1126545 1125132 1074817 701767
1058587 619266 930868 1124179 1128964 1119149 1115039 1032486 993132 1077799
1095195 1125794 1051239 1041113 1130594 1075535 1034245 991063 1067776 1062667
1129777 1130930 1131165 1131156 1101047 999338 1106653 1098395 862454 1111365
1054735 1073969 1059861 1132293 1082843 1072957 969293 1075540 1060843 1075552
834749 936891 1133604 1129723 1131174 1131176 1131169 1075550 1064771 1096991
1118074 1127677 1124931 1098793 1096660 1131177 1131183 1094037 1131285 1131098
1135508 1128915 1136368 1054432 1129714 404574 1054522 1122310 1016365 819221
1030320 1119235 1137969 1138853 1139766 1107694 1138823 1141194 1049452 1143290
602147 1141860 1131162 1078652 1141801 1146112 1145873 1141129 1043447 1150050
1137310 1095133 1014122 1154517 1154458 829241 997692 1152641 1154418 1142057
1157508 1152840 1077555 1155362 1120022 1147543 1157003 1161349 1163510 1107481
1144105 1145054 1162159 1163683 1127680 1160469 1166456 1167648 584649 1083195
1167061 1090978 1148909 1172182 1171778 1166792 1171236 1152595 1150787 1166347
1159518 1151846 1172646 1169688 1175399 1170164 1174720 1162317 1168696 1159724
1177687 1173328 791283 1176655 1169329 1176304 1177982 1178736 1177072 1178397
1160350 1177593 1140137 1175452 1176372 1146967 1183648 1182143 1181897 1176200
1182020 1177985 1182062 1173920 1186192 1186480 1187051 1165566 1190469 1188846
1143454 1055679 1186480 1188445 1181925 1190635 1188189 1187805 1190602 1188080
1198270

NB_JAV_60_6_M.NT
----------------
1096255 1113358 1067652 1039772 1026840 1115060 1135357 1137877 1173731 1179942


NB_NOM_60_6_M.NT
----------------
1131094 1131134 1131137 1131103 1131138 1131108 1118615 1137125 1171031 1175218
1167658 1167639 1170302 1186173

NB_SMJ_60_6_M.NT
----------------
1066322 1066330




=============================
VII. MAINTENANCE PACK CONTENT
=============================
This section contains the maintenance pack conventions, content, and historical
content that is applicable to the release.

Conventions:
------------
The following list describes the conventions used in the subsections that
following this section. Each item listed in the Current Maintenance Pack
subsection describes a feature, enhancement, or issue fixed with this
Maintenance Pack.

Description
Describes a particular problem contained in this pack.

** Description **
Describes a problem that can lead to potential data loss. Please
read these problem descriptions carefully.

Workaround
Any available workarounds to a problem are also listed. Workarounds can be
used INSTEAD of applying the patch, however, Symantec strongly recommends
the "best practice" of being at the latest available patch level.

Additional Notes
Any additional information regarding a problem is included.



Current Maintenance Pack
------------------------
Each item listed in this section describes a feature, enhancement, or change
that comprises this Maintenance Pack. Please read this section thoroughly to
understand the contents of this update.
--------------------------------------------------------------------------------
Etrack Incident = ET1131094

Description:
Changes have been made to address the following performance issues
found in the Job success reports.

- Job Success Rate by Policy type
- Job Success by Client
--------------------------------------------------------------------------------
Etrack Incident = ET1131134
Associated Primary Etrack = ET1086613
Titan cases: 240-589-611

Description:
Clicking on any navigation buttons on the second report when it was
run from the link in the first report resulted in an error dialog.

A change was made that ensures a user can click a link on the first
report to a second report and be assured that the navigation buttons
on the second report will work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET1131137
Associated Primary Etrack = ET1086594
Titan cases: 290-819-547

Description:
The Access Control page would not show all of the users that were
configured in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1131103
Associated Primary Etrack = ET1112826
Titan cases: 220-104-230 230-473-657

Description:
A change was made to fix an issue that caused NOM alerts to not be
emailed.
--------------------------------------------------------------------------------
Etrack Incident = ET1131138
Associated Primary Etrack = ET1120556
Titan cases: 290-828-029

Description:
Monitor names in the NOM server reported a CORBA Exception error in
the GUI.Lot of the "classcast" exceptions that were seen in NOM log
files due to a single event channel.

A number of monitor name encountered the "[Error: CORBA Exception]"
error in the "Connected" column such as:

- "Media Monitor"
- "Drive Monitor"
- "Robot Monitor"
- "Service Monitor"
--------------------------------------------------------------------------------
Etrack Incident = ET1131108

Description:
A change was made to ensure that a NOM server does not run out of memory
in case of large deployments.
--------------------------------------------------------------------------------
Etrack Incident = ET1118615

Description:
A change has been made to ensure that the SNMP MIB files are loaded
by Windows installer.
--------------------------------------------------------------------------------
Etrack Incident = ET1137125

Description:
Changes have been made to address a JacORB deadlock issue.
--------------------------------------------------------------------------------
Etrack Incident = ET1171031
Associated Primary Etrack = ET1161803
Titan cases: 220-131-070

Description:
Some Standard Reports show the Job type as '0' and '2' for backup
and restore job types. The data shown in these reports did not
match with the NetBackup server.
--------------------------------------------------------------------------------
Etrack Incident = ET1175218

Description:
A change was made to correct an issue that caused an exception to occur
while attempting to change a port on a NOM server.
--------------------------------------------------------------------------------
Etrack Incident = ET1167658

Description:
Monitors on Data load status page remained UP after stopping NBNOS
on NetBackup server. Changes have been made that ensure that after
you restart NBNOS, the Copied job policy is shown in NOM user
interface.
--------------------------------------------------------------------------------
Etrack Incident = ET1167639

Description:
A change was made to ensure that the NOM server accurately receives all
updates from NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET1170302

Description:
Emailing a report to a recipient group did not result in the email being
sent to all the recipients in the group. Only one user from the group would
receive the email.

--------------------------------------------------------------------------------
Etrack Incident = ET1186173
Titan cases: 320-053-257

Description:
An exception would occur from a scheduled report if the time taken by the
scheduled report was more than the session timeout. If a report took more
than 30 minutes (client session timeout) then the user would receive an
email with an error.
--------------------------------------------------------------------------------



Maintenance Pack History
------------------------

This section contains an accumulative list of all maintenance pack information
contained in previous releases.

=============
NB_NOM_60_5_M
=============
Etrack Incident = ET819699

Description:
The �LIKE� operator in the filter was not working as expected in the
Reports and Details table.
--------------------------------------------------------------------------------
Etrack Incident = ET819707

Description:
An exception occurred when a user tried to compare a policy history with
0.5 hours.
--------------------------------------------------------------------------------
Etrack Incident = ET836652

Description:
The scheduled report would accept white spaces without any ID in
�Email� field. A change has been made to ensure the Email fields
cannot be left blank or have only white spaces entered.
--------------------------------------------------------------------------------
Etrack Incident = ET851537

Description:
The drill-down from the NOM Assigned volume pie chart to the details
page was moving to unassigned volumes in list.
--------------------------------------------------------------------------------
Etrack Incident = ET863447

Description:
NDMP restore from an Overland tape device failed because the same
fragment was loaded twice.
--------------------------------------------------------------------------------
Etrack Incident = ET797865

Description:
The �average days assigned� value was negative when it should have been
the same value that is calculated with reference to NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET801220

Description:
The report that filters jobs with the policy __DSSU_POLICY_DSSU was not
working.
--------------------------------------------------------------------------------
Etrack Incident = ET928501

Description:
The number of threads would continue to increase in the NOM Server
after multiple NOM client requests.
--------------------------------------------------------------------------------
Etrack Incident = ET853681

Description:
During a failed NOM install the services would not automatically restart.
--------------------------------------------------------------------------------
Etrack Incident = ET828994

Description:
The Y axis unit was shown incorrectly for the "File count variance"
report.
--------------------------------------------------------------------------------
Etrack Incident = ET790572

Description:
A change was made to ensure the master server�s status matches the
Monitor�s status.
--------------------------------------------------------------------------------
Etrack Incident = ET796090

Description:
Policies were shown three times on the NOM user interface. This happened
because there was no default sorting criteria.
--------------------------------------------------------------------------------
Etrack Incident = ET647598

Description:
Changes were added to ensure that NOM shows the correct job data.
--------------------------------------------------------------------------------
Etrack Incident = ET828460

Description:
CPU utilization was very high by VRTSweb and VRTSnomdbsrv (more than 90%).
--------------------------------------------------------------------------------
Etrack Incident = ET928048
Associated Primary Etrack = ET917338

Description:
NOM was not collecting the proper drive information for clean frequency
and total time fields.

When creating reports using the �Drive� data view with fields of
�CleanFreq� and �TotalTime�, these fields displayed erroneous data.
By using Sybase Central to view the MMDrive table, it was evident that
NOM had the wrong data.
--------------------------------------------------------------------------------
Etrack Incident = ET917979

Description:
The debug logs were not being generated for the NOM Reporting component
if the DebugLevel was set to greater than six. To resolve the issue
initially, the user manually set the DebugLevel to any value less than or
equal to 4 to enable logging. A change was added to this maintenance
pack so that if the DebugLevel is set to greater than 4 then it resets
the same to 4.
--------------------------------------------------------------------------------
Etrack Incident = ET834582

Description:
Data Load Status page was causing an exception to occur. Changes were
added to ensure the Monitors list displays correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET928155

Description:
Corrections were made to the Log Management feature to ensure it works
properly.
--------------------------------------------------------------------------------
Etrack Incident = ET931540

Description:
A new support script has been added for NOM in this maintenance pack.
This support script will collect data about your system environment
and NOM configuration and serves to provide first-level information for
the support team in case of an issue with NOM.

To run the support script:

1. Run the following commands to execute the support script. These
commands need to be executed on the NOM server.
- For Solaris run: /opt/VRTSnom/bin/nomsupport
- For Windows run: <INSTALL_DIRECTORY>\VERITAS\NetBackup Operations
Manager\bin\admincmd\nomsupport.bat

2. This script stops all of the NOM services and then collects system
information and NOM configuration information. It then zips all this
information in a file called Support.zip. You can also choose to add
log files, NOM database files, and so forth, to this zip file.
Adding log files and NOM database files can increase the file size
of Support.zip.

3. This zip file is stored in the following directories:
- On Solaris: /opt/VRTSnom/temp/Support.zip
- On Windows: <INSTALL_DIRECTORY>\VERITAS\NetBackup Operations
Manager\temp\Support.zip

4 After the zip file is created, the script starts all the NOM services.
--------------------------------------------------------------------------------
Etrack Incident = ET961224

Description:
Corrections were made to the Log Management feature to ensure it works
properly.
--------------------------------------------------------------------------------
Etrack Incident = ET971298

Description:
Alerts are not generated until the NOM server is restarted.

Workaround:
To resolve this issue, restart the NOM server after creating
alert policies.
--------------------------------------------------------------------------------
Etrack Incident = ET965343
Associated Primary Etrack = ET965201

Description:
In the Media Report, the date in the Allocated Date field always showed
1970 for all media instead of the correct allocation date.
--------------------------------------------------------------------------------
Etrack Incident = ET1005607

Description:
Unwanted strings would display on the Add Master Server Window. To
correct this issue, a missing key value pair was added to the code.
--------------------------------------------------------------------------------
Etrack Incident = ET1006473

Description:
For Suspended jobs the �% completed (Estimated)� column would show
incorrect data.
--------------------------------------------------------------------------------
Etrack Incident = ET1011619

Description:
Sorting was not working on any of the column in the Storage Unit
Details table.
--------------------------------------------------------------------------------
Etrack Incident = ET1009043

Description:
After adding the Jobs detail report to My portal and running the report,
data would not appear in the Job details report as expected. A change
was made to ensure data is shown, with respect for the time frame, for
the same report.
--------------------------------------------------------------------------------
Etrack Incident = ET1008233

Description:
The Last time cleaned and Last time mounted values were erroneously
shown as October 15, 1582 5:30 AM in Drive details report.
--------------------------------------------------------------------------------
Etrack Incident = ET1012467

Description:
On the Monitoring > Job > Details page, the active, queued, suspended,
incomplete, undefined, and waiting for retry jobs were not being shown
when filtered on the basis of time.
--------------------------------------------------------------------------------
Etrack Incident = ET859501

Description:
A manual backup from NOM would cause an exception to occur.
--------------------------------------------------------------------------------
Etrack Incident = ET1064357
Associated Primary Etrack = ET1064320

Description:
A change was made that enables you to delete the report schedule after
the report has been deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET1064355

Description:
A fix was added that corects a database error that would occur while
running the job details report within NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET1005591

Description:
A correction was made to ensure that the version shown
on the Login page and the About window is 6.0MP5.
--------------------------------------------------------------------------------
Etrack Incident = ET1068709

Description:
Data in the Media and Device Reports was not being updated properly.
An error message would appear in the NOM user interface while the
"Resume the Job" ran.
--------------------------------------------------------------------------------
Etrack Incident = ET1071408

Description:
A NOM database upgrade from NetBackup 6.0 GA to 6.0 MP5 would
fail if the host name contained a dash character (-).




=============
NB_NOM_60_4_M
=============
Etrack Incident = ET603548

Description:
More than 10 recepients in NOM would show incorrect data on the second
page. It showed the first 10 records on all of the pages.
--------------------------------------------------------------------------------
Etrack Incident = ET632133

Description:
While editing a recipient group, if a user had more than 10 recipients,
clicking on page 2 or more would cause the dialog to hang.
--------------------------------------------------------------------------------
Etrack Incident = ET631434

Description:
If an attempt was made to create a shortcut twice on same report to
same folder, the shortcut would not be created and an exception would
appear in the dialog box.
--------------------------------------------------------------------------------
Etrack Incident = ET631165

Description:
Vault Jobs were being displayed in NOM as FlashBackup for Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET631163

Description:
An error would occur when attempting to sort columns in an Alert Policy
window, if the alert policy contained new-line characters.
--------------------------------------------------------------------------------
Etrack Incident = ET631369

Description:
The filter operation was not working properly for fields with a select
box option.
--------------------------------------------------------------------------------
Etrack Incident = ET631373

Description:
The add master server feature was not working properly.
--------------------------------------------------------------------------------
Etrack Incident = ET631378

Description:
The filtering operation was not working correctly in the
'MONITORING > DRIVES > Detailed' window.
--------------------------------------------------------------------------------
Etrack Incident = ET631435

Description:
The capability of having more than 10 comments to an alert was not working
properly.
--------------------------------------------------------------------------------
Etrack Incident = ET632009

Description:
An issue existed where users could not deactivate the NOM trap receiver.
--------------------------------------------------------------------------------
Etrack Incident = ET631441

Description:
A change has been made to the "Alert Retention Period" on the
Settings > System page to no longer accept a negative reention value is
one is entered.
--------------------------------------------------------------------------------
Etrack Incident = ET632012

Description:
The status of the NetBackup and NOM services would differ if some of the
NOM services were running and then they were restarted. The NOM services
would even go to an unknown service state. The issues has been resolved.
--------------------------------------------------------------------------------
Etrack Incident = ET631428

Description:
Changes were made to resolve a core dump issue in NOM_dbrv when attempting
to run a NightlyBackup event in Solaris.
--------------------------------------------------------------------------------
Etrack Incident = ET569847

Description:
The reload option for NOMAdmin was causing an SQL exception on Windows.
--------------------------------------------------------------------------------
Etrack Incident = ET631383

Description:
An incorrect NULL value was being displayed for the AverageImages value
in the Managing > Media > Summary window.
--------------------------------------------------------------------------------
Etrack Incident = ET642820

Description:
NOM was incorrectly showing 1191 media as cleaning tapes when there
were only two in NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET563592

Description:
The condition for "No cleaning tape available" raised an alert even if
cleaning media existed.
--------------------------------------------------------------------------------
Etrack Incident = ET623492

Description:
The e-mailed report was always sorted on the first column irrespective of
the real sort order in a report.
--------------------------------------------------------------------------------
Etrack Incident = ET625302

Description:
A schedule report or a directly-emailed report would show future dates.
The dates are shown correctly when the same report is run in NOM user
interface.
--------------------------------------------------------------------------------
Etrack Incident = ET617023

Description:
The report builder wizard failed to create a filter on double type of
column. For example, if the Job Pass Rate view has a rate column, then
you would not be able to define a filter on this column.
--------------------------------------------------------------------------------
Etrack Incident = ET630307

Description:
Error messages in NOM reporting was sometimes too cryptic. In some
error messages, NOM would only show a message like, {0.EN_US}. The error
message should have contained additional information that included
the schedule name.
--------------------------------------------------------------------------------
Etrack Incident = ET644511

Description:
NOM incorporates string-based sorting, which resulted in an incorrect sort
order with date/time fields in a report.

For example, "Monday 14 Aug" might come before "Sunday 14 Aug" in ascending
order sort.

Additional Notes:
After applying this fix, the problem will still exist for hyperlinked
columns.
--------------------------------------------------------------------------------
Etrack Incident = ET644515

Description:
If you scheduled a recurring schedule to run every week day at 7:00 AM
and it is 3:00PM in the evening, the report would be emailed immediately
as the first thing.

An additional dialog was created for this issue. The dialog box accepts
time and day to activate the schedule at.
--------------------------------------------------------------------------------
Etrack Incident = ET632008

Description:
The "Relative time" field was not validated and caused an error if a
user-specified, alphanumeric value was entered for a relative time.
--------------------------------------------------------------------------------
Etrack Incident = ET632021 ET632024 ET632026 ET632032

Description:
The Hot and Cold catalog backup reports were not showing any data.
--------------------------------------------------------------------------------
Etrack Incident = ET646229

Description:
NOM no longer shows incorrect job data.
--------------------------------------------------------------------------------
Etrack Incident = ET646503

Description:
Media Details were showing a NULL value in the NOM user interface after
NOMMP2A was install on NOMMP1.
--------------------------------------------------------------------------------
Etrack Incident = ET632013

Description:
The job count did not match in the "Job Details" and the
"Job Details by status" reports.
--------------------------------------------------------------------------------
Etrack Incident = ET632203

Description:
An alert on a 'Lost Contact with Media Server' condition was not being
raised.
--------------------------------------------------------------------------------
Etrack Incident = ET649123

Description:
Nomadmin would not work after NOM MP2 was applied. A fix has been added
to correct this issue.
--------------------------------------------------------------------------------
Etrack Incident = ET566631

Description:
NOM would try to load all the records in memory before generating a
tabular report. This would resulted in an out-of-memory error if the
tabular report contained a large amount of data. A fix was added to
make sure that only the information in the current page was loaded in
memory.
--------------------------------------------------------------------------------
Etrack Incident = ET574264

Description:
If a report has a hyperlink defined in any Time column, and while running
the report, that time column has a null value in the database for any
particular case that a report would fail to execute.

For example, If a job has just completed and the NOM server has not yet
received the completion time of the job, then the completion time can be
null.
--------------------------------------------------------------------------------
Etrack Incident = ET632010

Description:
Unable to handle negative values for type "integer" fields and showing a
warning as an invalid integer. For example, if you entered -1 for a type
int field, it would show an alert.

In addition, special characters like (@ or ') were not handled in type
"string" fields of the filtering of the reports as the next page showed
an error. For example, if you enter special characters like (@ or ') then
the result would be an exception on the next page.
--------------------------------------------------------------------------------
Etrack Incident = ET699708

Description:
Reports from a �Combined Job and Image� data view did not correctly
display the job information.
--------------------------------------------------------------------------------
Etrack Incident = ET630326 ET632004

Description:
The following issues have been resolved with this Etrack:
- The Timezone settings were not being saved properly.
- The Scheduling wizard now accepts time in "My Timezone".
- The Scheduling wizard summary time and time set by user did not match.
- If the user did not set the Timezone in user preferences, then incorrect
values would be saved.
--------------------------------------------------------------------------------
Etrack Incident = ET604947

Description:
Changes have been made to NOMAdmin to purge any inconsistent data of Jobs
before making database changes.
--------------------------------------------------------------------------------
Etrack Incident = ET767886

Description:
Changes have been made to remove an extra �undefined jobs� data field for
Jobs in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET769134

Description:
Changes were made to add filenames to the NOM_32.ism file for NOM 6.0 MP4.
--------------------------------------------------------------------------------
Etrack Incident = ET767893

Description:
Performance changes have been made to eliminate the need to restart the NOM
server each day because the NOM would gradually slow down and become out of
sync with NetBackup.

--------------------------------------------------------------------------------
Etrack Incident = ET769175

Description:
In the NOM interface, the message, �Total Media Used: 0� was erroneously
being displayed.

In addition, the field labeled, �Total data protected� I the Nom summary
page, has been changed to �Total data backed up� and includes jobs with the
done status and type (such as, Backup, archive, and duplicate jobs).
--------------------------------------------------------------------------------
Etrack Incident = ET778776

Description:
Upgrading PBX for NetBackup Operations Manager to be in sync with the
NetBackup version.
--------------------------------------------------------------------------------
Etrack Incident = ET574270

Description:
The �Jobs/policy� column data in the NOM server was not matching with
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET782108

Description:
Changes have been made to correct existing NOM install issues.
--------------------------------------------------------------------------------
Etrack Incident = ET593874

Description:
Changes have been made to correct an issue where the policyid_FK field in
cyc_NBJobs table was blank.
--------------------------------------------------------------------------------
Etrack Incident = ET782984

Description:
Changes have been made to ensure the NOM release version matches the
NetBackup version.
--------------------------------------------------------------------------------
Etrack Incident = ET630351

Description:
When modifying the layout of a composite report, NOM will not allow the
user to select any reports when the number of stacked reports has increased.
--------------------------------------------------------------------------------
Etrack Incident = ET567085 ET630266 ET631265

Description:
Trying to assign a cleared alert no longer gives error.
--------------------------------------------------------------------------------
Etrack Incident = ET567097

Description:
Added a comment to the cleared alert, incorrect implementation.
--------------------------------------------------------------------------------
Etrack Incident = ET517408

Description:
Changes were made in NOM to correct how a load should work, after export.
--------------------------------------------------------------------------------
Etrack Incident = ET778698

Description:
Lotus Notes does not support Java script that is embedded in NOM
reports. In addition, it does not support png image format that is used
by NOM reports. To address these issues, NOM has introduced some email
formats. The reports can now be emailed using plain HTML. This format
does not contain any JavaScript. That also disables tool-tips in
report. Optionally, the hyperlinks in reports can be removed and
graphical reports can be generated in JPEG format. The JPEG format is
useful on email clients like Lotus Notes, Netscape email client, and so
forth.
--------------------------------------------------------------------------------
Etrack Incident = ET631237 ET630243 ET632133

Description:
The following issues were resolved.
- Sorting was not working properly on the recipients page.
If email recipients spans more than one page and sorting is applied
on any column of the recipients table, then the applied sorting
only effects the data on only that page.
- The Policy History page was not able to sort by Revision date.
- The edit recipients group would not work for more than 10 recipients
If there were more than 10 recipients and while creating recipients
recipients were added from more than one page, only the recipients
selected from the last page were added to the group.
--------------------------------------------------------------------------------
Etrack Incident = ET630344

Description:
When modifying the layout of a composite report, NOM will not allow the
user to select any reports when the number of stacked reports has
decreased.
--------------------------------------------------------------------------------
Etrack Incident = ET631427

Description:
An issue existed where alerts for Mount Request pending operations are
not being raised correctly. For additional information, refer to the
following TechNote on the Symantec support web site.

http://entsupport.symantec.com/docs/285150
--------------------------------------------------------------------------------
Etrack Incident = ET790821

Description:
Changes were made to prohibit long, all-numeric values from being accepted
as a password.
--------------------------------------------------------------------------------
Etrack Incident = ET805407

Description:
The policy monitor would show as being down in Initial Data Load status
page.
--------------------------------------------------------------------------------
Etrack Incident = ET806888

Description:
The bpinet services on media servers were being reported as an
"unknown" status in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET806990

Description:
Service credentials had expired and because of that, the NOM client was
unable to log into the NOM server.

Workaround:
To avoid this issue, you can renew the credential using the command line
interface provided by vssat.
--------------------------------------------------------------------------------
Etrack Incident = ET818136

Description:
NOM no longer shows the start and end times being off by 30 minutes for the
Singapore timezone (SGT).
--------------------------------------------------------------------------------
Etrack Incident = ET821181

Description:
Changes have been so that the hard coded string "Historical Jobs" does not
show on a Localized NOM Monitoring > Overview Summary tab.
--------------------------------------------------------------------------------
Etrack Incident = ET830977

Description:
NOM no longer creates multiple NBProxy processes when there is no
job activity.
--------------------------------------------------------------------------------
Etrack Incident = ET829074

Description:
A change was made to add a utility to delete alerts to keep the alert
count down and performance up.
--------------------------------------------------------------------------------
Etrack Incident = ET832946

Description:
Changes were added that eliminate the possibility of a user not being
able to login to NOM. This intermittent problem would cause the NOM user
interface to become unusable until it was restarted.

Workaround:
NOM can run as many as five reports simultaneously. If you try to run a
sixth report, the report request will go into a queue. The report will
start running only after one of the previous reports completes running.
This delay may cause you to beleive that the run report page in the NOM
user interface has hung.

The pie charts you see on the overview pages are a type of graphical
report. So, if five reports are already running, instead of seeing
pie-charts, you will see the message, "pie charts unavailable," message on
the overview screens.




=============
NB_NOM_60_2_M
=============
Etrack Incident = ET496951

Description:
Deleting a schedule would take a lot of time, and caused the screen to
hang making it impossible for other operations to be performed at the same
time. Now, the process of deleting a schedule takes less time than it did
in the NetBackup 6.0 GA version, and the process no longer causes the
screen to hang. In addition, this improvement makes it possible for other
operations to be performed while a schedule is being deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET496952

Description:
An issue existed with scheduled reports that had the timeframe set to
�now�. The user expected the data in the report to be present from the
time it was run, however, this defect caused different data to be shown.
For example, the data in the report started from the day the report was
created rather than from the time the report was run.
--------------------------------------------------------------------------------
Etrack Incident = ET496946

Description:
An issue existed that enabled a report to be copied to the same folder
multiple times. This type of issue could cause confusion for a user. In
addition, a report that was copied could not be deleted. This problem has
been resolved.
--------------------------------------------------------------------------------
Etrack Incident = ET496948

Description:
Composite reports, once copied, could not be edited. This issue has been
resolved by enabling a user to copy a composite report and then edit it.
--------------------------------------------------------------------------------
Etrack Incident = ET496944

Description:
If a user edited any report that had groupings applied to it, and then
renamed the columns in the report, all of the groupings would be removed
and the report would be run. The user was unaware that the groupings were
removed.
--------------------------------------------------------------------------------
Etrack Incident = ET498495

Description:
The Drive-down Warning alert was not sent when the drive was taken down.
--------------------------------------------------------------------------------
Etrack Incident = ET500409

Description:
In the NOM interface, an issue existed in the area of Monitoring > Master
Servers > Clients. Clicking on the columns to sort a list caused all of
the clients to disappear.
--------------------------------------------------------------------------------
Etrack Incident = ET500334

Description:
The first <login> attempt using an alternate user name and domain would
always fail and a second attempt would succeed. The first attempts no
longer fail.
--------------------------------------------------------------------------------
Etrack Incident = ET492274

Description:
Sybase ASA database logs contained warnings such as, �duplicate index
found�. This fix no longer causes the Warning messages.

Additional Notes:
Fixing this issue improves the database performance because redundant
indexes have been removed.
--------------------------------------------------------------------------------
Etrack Incident = ET508203

Description:
The "version" file and �about� fields in the NOM web interface now reflect
NetBackup 6.0MP2.
--------------------------------------------------------------------------------
Etrack Incident = ET510921

Description:
The NOM Job Detail and Job Summary by Status Reports are blank when the
Policy Type is set to ANY or MS-Windows. As the specified policy types
are deprecated in NetBackup, these should not be visible in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET510923

Description:
If the user went to the Reporting > My Portal tab and added the same JOBS
report that was created earlier into the list of reports for the
"My portal" tab, then it showed that there were multiple pages of
information. However, if the user clicked on any of the page numbers
other than page one, the interface did nothing. For example, if the user
clicked on page two of the report, the interface displayed the message,
"Loading Page 2" at the top of the report, and yet also displayed an
error in the bottom left corner of the web page.
--------------------------------------------------------------------------------
Etrack Incident = ET510924

Description:
The report sorting sequence would not work across multiple pages. Sorting
that was applied to a column on the first page of the report did not work
on the subsequent pages.
--------------------------------------------------------------------------------
Etrack Incident = ET496948

Description:
Composite reports, once copied, could not be edited. This issue has been
resolved enabling a user to copy a composite report and then edit it.
--------------------------------------------------------------------------------
Etrack Incident = ET512863

Description:
A problem existed where recipients that were added to a scheduled report,
would disappear off the report list.

Workaround:
To avoid this issue, do not use white spaces when creating alias names.
--------------------------------------------------------------------------------
Etrack Incident = ET513378

Description:
The NOM Server service no longer dies (or shuts-down) each time the
services are restarted.
--------------------------------------------------------------------------------
Etrack Incident = ET332271

Description:
The Job Monitor had a few inconsistencies with the NetBackup Activity
Monitor, for example, ElapsedTime and ActiveElapsedTime columns were not
included in the Job Details table.
--------------------------------------------------------------------------------
Etrack Incident = ET516362

Description:
Deleting a column that had a filter defined on it would cause a Null
pointer exception.
--------------------------------------------------------------------------------
Etrack Incident = ET512391

Description:
Creating New DRIVE and ROBOT Reports, caused multiple entries for some
column names.
--------------------------------------------------------------------------------
Etrack Incident = ET512389

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

Description:
Data was not coming to the NOM server whenever NetBackup had a large amount
of data.
--------------------------------------------------------------------------------
Etrack Incident = ET419756

Description:
Monitoring Page and Reports would show the job StartTime and Completion
Time incorrectly if NetBackup is in a different time zone with respect to
the server timezone.
--------------------------------------------------------------------------------
Etrack Incident = ET428896

Description:
The monitoring overview (Monitoring > Overview > Summary) was not
displaying Jobs for the root node if data collection was disabled for all
the servers. In addition, it did not include data from the servers for
which data collection was disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET511567

Description:
Alert messages (for service-down alerts) did not contain information about
the media servers. This made it difficult to determine in the error
message that the service was down on a certain media server if there were
more than one media server.
--------------------------------------------------------------------------------
Etrack Incident = ET415670

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

Description:
Exceptions occurred that caused the master servers to go offline and
eventually caused the database server to also go offline.
--------------------------------------------------------------------------------
Etrack Incident = ET523024

Description:
A problem existed that caused the server to run out of memory if the
number of Jobs was high.
--------------------------------------------------------------------------------
Etrack Incident = ET523928

Description:
Reports that had the FileCount column selected, failed with SQL when the
reports were run while the FileCount was very high.
--------------------------------------------------------------------------------
Etrack Incident = ET523927

Description:
Repeated JAVA exceptions were received when doing nothing in the Standard
Reports if DataCollecton was enabled and auto-refresh was turned on.
--------------------------------------------------------------------------------
Etrack Incident = ET521846

Description:
NOM Server required an excessive number of database calls to generate the
Overview page (Monitoring > Overview/Managing > Overview). The number of
calls have been reduced by 20 percent.
--------------------------------------------------------------------------------
Etrack Incident = ET514026

Description:
If there were no inconsistent records in the NOM database that had to be
deleted, the NOMAdmin tool would display the error message, 'Cannot execute
an empty (zero-length) query'. Changes made in this pack make sure the
tool functions properly in case no inconsistent data was detected in the
database .
--------------------------------------------------------------------------------
Etrack Incident = ET514012

Description:
If no obsolete data was detected after issuing the command
'./NOMAdmin -purge daily /mydir/k1.txt DoDelete', the NOMAdmin tools would
display the error message, 'Cannot execute an empty (zero-length) query'.
Changes included in this pack make sure that the tool functions properly in
case obsolete data was detected in the database.
--------------------------------------------------------------------------------
Etrack Incident = ET514003

Description:
The existence of the ampersand (&) character within the command
'./NOMAdmin -changeGuest ' or '-changePW' was causing an exception in
the NOMAdmin tool on UNIX platforms, because the ampersand is a special
character used by the UNIX operating system.

Changes have been made to check for the presence of this character in the
new password that the user provides, and asks the user to re-enter the
password without the special character.
--------------------------------------------------------------------------------
Etrack Incident = ET521778

Description:
Memory leaks in the NOM Web Console caused the memory utilization of this
process to increase over time.
--------------------------------------------------------------------------------
Etrack Incident = ET521857

Description:
The NOM server consumed large amounts of memory during a Media Data Load
process.
--------------------------------------------------------------------------------
Etrack Incident = ET527110

Description:
The capability to sort for Numeric type columns was not working correctly.
--------------------------------------------------------------------------------
Etrack Incident = ET526256

Description:
The Policy data collection's performance was bad and it also produced
Out-Of-Memory errors if the data was large.
--------------------------------------------------------------------------------
Etrack Incident = ET521846

Description:
NOM Server required an excessive number of database calls to generate the
Overview page (Monitoring > Overview/Managing > Overview). The number of
calls have been reduced by 20 percent.
--------------------------------------------------------------------------------
Etrack Incident = ET512389

Description:
The NOM Filter criteria was not working correctly in the
Monitoring > Drives > Detailed page.
--------------------------------------------------------------------------------
Etrack Incident = ET512391

Description:
Some of the column names appeared multiple times when creating the
New DRIVE and ROBOT Reports.
--------------------------------------------------------------------------------
Etrack Incident = ET500334

Description:
The first login attempt using an alternate username and domain no longer
fails.
--------------------------------------------------------------------------------
Etrack Incident = ET528836

Description:
Unreadable characters appeared in the Confirm Scheduled Report Selection.
If the schedule type was �recurring+interval�, and �days� was selected as
the interval option, the word �days� was not legible in the Confirm
Scheduled Report Selections screen.
--------------------------------------------------------------------------------
Etrack Incident = ET521820

Description:
A problem existed that made it impossible to retrieve catalog images data.
--------------------------------------------------------------------------------
Etrack Incident = ET528830

Description:
The strings: ''hour'', ''minutes'', and ''seconds'' were hard-coded in the
Email Recipients Setup dialog.
--------------------------------------------------------------------------------
Etrack Incident = ET528827

Description:
The Create Schedule process produces a runtime error if no option was
selected in �Select the Type of Recurring Schedule� field.
--------------------------------------------------------------------------------
Etrack Incident = ET528820

Description:
The Status column in the Monitoring > Jobs > Details page showed a zero (0)
for Active jobs, which was the status for Successful Jobs.
--------------------------------------------------------------------------------
Etrack Incident = ET528925

Description:
The MediaType attribute in the Media Details table definition was changed
to show MediaType rather than RobotType.
--------------------------------------------------------------------------------
Etrack Incident = ET528819

Description:
If all of the days of the week or month were selected for a recurring type
of schedule, the selections were lost while editing the schedule.
--------------------------------------------------------------------------------
Etrack Incident = ET526601

Description:
The CORBA exceptions stack trace displayed in the NOM interface was
perceived as a user interface crash.
--------------------------------------------------------------------------------
Etrack Incident = ET528934

Description:
An exception occurred if an attempt was made to create and execute a filter
on the Context column of the Alert Policy Details table. To correct this
exception, the creation of a filter on the Context column is disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET528822

Description:
A vague error message was given after entering a float instead of an
integer in a filter expression.
--------------------------------------------------------------------------------
Etrack Incident = ET528924

Description:
The Start and End times in Job Details need to be more visible.

Workaround:
To avoid this issue, manually adjust the column widths for the Start and
End times.
--------------------------------------------------------------------------------
Etrack Incident = ET528833

Description:
The Total Jobs count is no longer wrong in the Overview on the Job
Monitoring page.
--------------------------------------------------------------------------------
Etrack Incident = ET523024

Description:
A problem existed that caused the server to run out of Memory if the
number of Jobs was high.
--------------------------------------------------------------------------------
Etrack Incident = ET528824

Description:
In the Create New Filter for Job page, the Job State column contained the
JOB ID value for that selection.
--------------------------------------------------------------------------------
Etrack Incident = ET528877

Description:
If a master server has a large amount of job data flowing across multiple
pages, and two failed jobs are selected, each on a different page, and
then the restart function is selected, the restart would only apply to the
job that was selected on the current page. Jobs selected in any other page
are omitted.

Workaround:
To avoid this issue, the user must apply the filters in such a way that
all the "to be operated" jobs are shown on one page or change the rows,
per page, to show them on one page. This will only work if the number of
"to be operated" jobs is below 1000 (= max no. of rows/page); otherwise
the user must perform the operation in batches.
--------------------------------------------------------------------------------
Etrack Incident = ET528940

Description:
The user interface now has a separate icon for master servers that have
data collection disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET528931

Description:
The ability to sort on the �Device Host� column in the
Managing > Devices > Robots > Device host column has been enabled.
--------------------------------------------------------------------------------
Etrack Incident = ET522923

Description:
A correction has been made that decreases the amount of time it takes
to delete a managed server from the NOM User Interface.
--------------------------------------------------------------------------------
Etrack Incident = ET540019

Description:
The Catalog files report showed incorrect data.
--------------------------------------------------------------------------------
Etrack Incident = ET540019

Description:
The Catalog files report showed incorrect data.
--------------------------------------------------------------------------------
Etrack Incident = ET540149

Description:
The �Clients Not Backed-up Report� did not work properly.
--------------------------------------------------------------------------------
Etrack Incident = ET541256

Description:
A problem was fixed that caused DataStoreExceptions to be seen in
NOM server logs.
--------------------------------------------------------------------------------
Etrack Incident = ET543493

Description:
Sorting on Monitoring > Jobs > JobState is no longer disabled.
--------------------------------------------------------------------------------
Etrack Incident = ET543059

Description:
A problem was discovered that OR and AND conditions could not coexist in
filters if they were defined with the OR condition first and then the
AND condition second.
--------------------------------------------------------------------------------
Etrack Incident = ET564968

Description:
Duplicate policies were seen if there was a large amount of data in
NetBackup.
--------------------------------------------------------------------------------
Etrack Incident = ET565226

Description:
Many of the strings were displayed in English in the "Customize Portal"
dialog.
--------------------------------------------------------------------------------
Etrack Incident = ET564874

Description:
The Alert condition, �zero cleaning left� did not raise an alert even
when the condition was true.
--------------------------------------------------------------------------------
Etrack Incident = ET564156

Description:
Alerts were not being generated in NOM with large amounts of data.
--------------------------------------------------------------------------------
Etrack Incident = ET589328

Description:
The NOM 6.0 MP2 installer fails when the NOM GA package is installed in a
location other than the default location (C:\Program Files).
================================================================================




=============
NB_NOM_60_1_M
=============

Etrack Incident = ET406999

Description:
Transport of log messages from NBSL to NOM Server was failing and causing
the Host Session to go down. PSP's TAO_Transport was not checking for
EAGAIN.
--------------------------------------------------------------------------------
Etrack Incident = ET492704

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

Description:
The deletion of a schedule would take a lot of time and hang the screen.
In addition, no other operation could be performed during that action.
--------------------------------------------------------------------------------
Etrack Incident = ET416123

Description:
An issue existed on all of the scheduled reports which had the timeframe
set to now. The user would expect the data in the report to be present
from the time it was run, but because of this defect, it would show some
different data as well as the report day starting from the day it was
created.
--------------------------------------------------------------------------------
Etrack Incident = ET368147

Description:
This issue is applicable to all the composite reports. Composite reports,
once copied, could not be edited. For most users, copying of reports is
not a useful function unless those reports are editable.
--------------------------------------------------------------------------------
Etrack Incident = ET364355

Description:
A report could be copied to same folder multiple times. This capability
caused confusion in the mind of the user. In addition, once the report
had been copied it could not be deleted.
--------------------------------------------------------------------------------
Etrack Incident = ET354333

Description:
If the user edited any report which had grouping applied on it and then
renamed the columns, all of the groupings would be removed and the report
would be run. The user would be unaware that the groupings were removed.
--------------------------------------------------------------------------------
Etrack Incident = ET418777

Description:
Drive Down Warning alert was not being sent when the drive was taken down.
--------------------------------------------------------------------------------
Etrack Incident = ET500331

Description:
In the NOM interface, selecting Monitoring > Master Servers >
In Monitoring > Master Servers > Clients, and then clicking on the columns
to sort the list would cause all of the clients to disappear.
--------------------------------------------------------------------------------
Etrack Incident = ET500297

Description:
Exceptions occurred on a production system that caused the master servers
to go offline and eventually the database server to go offline.
--------------------------------------------------------------------------------
Etrack Incident = ET500333

Description:
The first <login> attempt using an alternate username and domain would
always fail and the second attempt would succeed.
--------------------------------------------------------------------------------
Etrack Incident = ET506524

Description:
The "version" file now reflects NetBackup 6.0MP1, as well as the "about"
fields in the NOM user interface.
--------------------------------------------------------------------------------
Etrack Incident = ET510341

Description:
The NOM Job Detail and Job Summary by Status Reports are blank when the
Policy Type is equal to ANY or MS-Windows. As the specified policy types
are deprecated in NetBackup, these should not be visible in NOM.
--------------------------------------------------------------------------------
Etrack Incident = ET510338

Description:
If the user goes to the Reporting > My Portal tab and adds the same JOBS
report that was created earlier into the list of reports for the
"My portal" tab, then it would show that there were 10 pages of
information. However if you clicked on any of the page numbers other than
page 1, the GUI would do nothing. For Instance, if a user clicked on
page 2 of the report, the user interface would display the message,
"Loading Page 2" at the top of the report. However, an error would appear
in the bottom, left-hand corner of the Web page.
--------------------------------------------------------------------------------
Etrack Incident = ET510339

Description:
The sort sequence capability within reports that contained multiple
pages was not working properly. Sorting applied to a column on the first
page of a report did not carry forward to the subsequent pages.
--------------------------------------------------------------------------------
Etrack Incident = ET509715

Description:
The response time of the NOM user interface would slow down when the number
of alerts that were generated exceeded 200.
--------------------------------------------------------------------------------
Etrack Incident = ET403493

Description:
There were memory leaks in the NOM Web Console that caused the memory
utilization of this process to increase over time.
--------------------------------------------------------------------------------
Etrack Incident = ET510255

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

Description:
Recipients that were added to scheduled NOM reports would erroneously
disappear off the report list.

Workaround:
To prevent this issue from happening, users should avoid using white
spaces when creating alias names.
--------------------------------------------------------------------------------
Etrack Incident = ET512866

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


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

Description:
Pagination problems occurred when new alerts were created.
================================================================================


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)