Date:2011-11-24

OS: Windows

Etrack Incidents: 1746975, 2613061, 2611169, 2042903, 2579205, 2613953, 2624287, 2612939, 2613061, 2624378

Errors/Problems Fixed:

Since 2.5RU1_RP1:

Data ownership based reports take a long time to generate output for large
number of shares.
NOTE: With this fix, report output is restricted to 1, 00, 000 output rows.
To configure a different limit, edit reportcli.vmoptions file on management
server and change the following line as needed:
-Dreport.details.limit=100000
(1746975) [Applies to: management server, indexer]

collector.exe process takes excessive memory when consuming large number of
audit event files.
(2613061) [Applies to: all]

scanner.exe process takes excessive memory and CPU when scanning large 
number of paths during incremental scans.
(2611169) [Applies to: all]

Path permissions report does not allow user to exclude Share level ACLs
when computing effective permissions.
(2042903) [Applies to: management server, indexer]

Share discovery is not accurate for clustered Windows 2003 Windows File Servers
where multiple virtual file servers have been configured for the same cluster.
(2579205) [Applies to: windows file server agent, collector] 

Scanner continues to scan even if a large number of paths have errors scanning.
NOTE: With this fix, scanner will exit if it encounters errors on more than
5000 paths. To set a different limit, execute the following command on the
management server:
configdb.exe -o -T node -k <node_id> -J scanner.max_err -j <new_value>
To obtain node_id of the appropriate collector/windows file server agent,
issue the following command:
configdb.exe --print --type node
(2613953) [Applies to: windows file server agent, collector]

Index writer fails in certain rename event scenarios.
(2624287) [Applies to: indexer]

Latency of a netapp filer can be affected in case of network misconfiguration
between filer and the collector node.
NOTE: With this fix, Data Insight can be configured to disconnect fpolicy of
a filer if latency of the filer exceeds any of the configured high watermarks.
Data Insight will connect back once latency falls below all configured low
watermarks. You can specify a minimum sleep time between a disconnection and
reconnection event. Latency values are averaged over specified number of samples
each 20 seconds apart. 
Issue following commands on the management server to configure this feature:
configdb.exe -O -J events.disconn.fpolicy.watermark.high.cifs_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.watermark.high.cifs_write_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.watermark.high.cifs_read_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.watermark.low.cifs_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.watermark.low.cifs_write_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.watermark.low.cifs_read_latency -j <ms>
configdb.exe -O -J events.disconn.fpolicy.samples -j <num_samples>
configdb.exe -O -J events.disconn.fpolicy.quiet_time -j <minutes>
configdb.exe -O -J events.disconn.fpolicy.enabled -j true
(2612939) [Applies to: collector]

Index writer can fail for large number of input events. With this fix, index writer
will be configured to process 1 million events at one time. This value can be changed
from Advanced Settings page for the indexer. 
(2613061) [Applies to: indexer]

If scanner throttling for netapp filers has been enabled, full and incremental scans
for shares of vfilers fail with error 212.  
(2624378) [Applies to: windows file server agent, collector]

Install/Uninstall Instructions:

Apply this rolling patch on all Data Insight servers with version 2.5RU1 (2.5.1).

FILES AFFECTED BY THIS PATCH:

INSTALL_ROOT\DataInsight\bin\mxlog.dll
INSTALL_ROOT\DataInsight\bin\mindexer.dll
INSTALL_ROOT\DataInsight\bin\dbhandle.dll
INSTALL_ROOT\DataInsight\bin\DataInsight.dll
INSTALL_ROOT\DataInsight\bin\inactive.dll
INSTALL_ROOT\DataInsight\bin\inactive_data.dll
INSTALL_ROOT\DataInsight\bin\inactive_data_by_owner.dll
INSTALL_ROOT\DataInsight\bin\rptlib.dll
INSTALL_ROOT\DataInsight\bin\storage_by_domain.dll
INSTALL_ROOT\DataInsight\bin\storage_by_owner.dll
INSTALL_ROOT\DataInsight\bin\storage_by_type_and_owner.dll
INSTALL_ROOT\DataInsight\bin\fid_size.dll
INSTALL_ROOT\DataInsight\bin\scanner.exe
INSTALL_ROOT\DataInsight\bin\collector.exe
INSTALL_ROOT\DataInsight\bin\winnas_util.exe
INSTALL_ROOT\DataInsight\bin\report.exe
INSTALL_ROOT\DataInsight\bin\idxreader.exe
INSTALL_ROOT\DataInsight\bin\queryd.exe
INSTALL_ROOT\DataInsight\bin\fpolicyd.exe
INSTALL_ROOT\DataInsight\bin\idxwriter.exe
--
INSTALL_ROOT\DataInsight\pdb\mxlog.pdb
INSTALL_ROOT\DataInsight\pdb\mindexer.pdb
INSTALL_ROOT\DataInsight\pdb\dbhandle.pdb
INSTALL_ROOT\DataInsight\pdb\DataInsight.pdb
INSTALL_ROOT\DataInsight\pdb\inactive.pdb
INSTALL_ROOT\DataInsight\pdb\inactive_data.pdb
INSTALL_ROOT\DataInsight\pdb\inactive_data_by_owner.pdb
INSTALL_ROOT\DataInsight\pdb\rptlib.pdb
INSTALL_ROOT\DataInsight\pdb\storage_by_domain.pdb
INSTALL_ROOT\DataInsight\pdb\storage_by_owner.pdb
INSTALL_ROOT\DataInsight\pdb\storage_by_type_and_owner.pdb
INSTALL_ROOT\DataInsight\pdb\fid_size.pdb
INSTALL_ROOT\DataInsight\pdb\scanner.pdb
INSTALL_ROOT\DataInsight\pdb\collector.pdb
INSTALL_ROOT\DataInsight\pdb\winnas_util.pdb
INSTALL_ROOT\DataInsight\pdb\report.pdb
INSTALL_ROOT\DataInsight\pdb\idxreader.pdb
INSTALL_ROOT\DataInsight\pdb\queryd.pdb
INSTALL_ROOT\DataInsight\pdb\fpolicyd.pdb
INSTALL_ROOT\DataInsight\pdb\idxwriter.pdb
--
INSTALL_ROOT\DataInsight\tomcat\webapps\ROOT\WEB-INF\classes
INSTALL_ROOT\DataInsight\tomcat\webapps\ROOT\ui
INSTALL_ROOT\DataInsight\lib\console_launcher.jar
INSTALL_ROOT\DataInsight\tomcat\webapps\symhelp

NOTE: Please keep a backup of the files  you are about to patch. This will be
required in case you want to manually rollback the patch.

High Level Steps:
1. Apply the rolling patch on Management Server first, followed by all Worker Nodes.
2. Next, apply patch to Windows File Server agents.

Patching Data Insight Management Server and Worker Nodes:
1. Log onto each server with Administrative privileges.
2. Unzip the patch files to a temporary folder. In this folder, locate the rolling
   patch installer for the appropriate OS architecture. The installer is called
   Symantec_DataInsight_windows_251RP1_2_5_1_1665_x64.exe for 64 bit OS and
   Symantec_DataInsight_windows_251RP1_2_5_1_1665_x86.exe for 32 bit OS.
3. Launch the installer executable to install the rolling patch.

Patching Data Insight Windows File Server agents:
1. Unzip the patch files to a temporary folder. In this folder, locate the rolling
   patch installer bundles for Windows File Server agents. The agent bundle is called
   Symantec_DataInsight_windows_winnas_251RP1_2_5_1_1665_x64.zip for 64 bit OS and
   Symantec_DataInsight_windows_winnas_251RP1_2_5_1_1665_x86.zip for 32 bit OS.
2. Log into the Management Console with Server Administrator privilege and upload the 
   agent bundles to the appropriate collector worker nodes using "Agent Uploader" page
   in the Settings tab.
3. Navigate to Filer details page for each configured Windows File Server in the Settings
   tab and click on "Upgrade Agent" button available on the top of the page. This option
   is only visible if you have enabled the option to let Data Insight install/upgrade
   agent for this filer.
4. Alternately, to manually patch a Windows File Server agent, log onto the Windows File
   Server machine with Administrative privileges, unzip the agent installer bundle in a
   temporary location, and launch the patch installer. The patch installer is called
   Symantec_DataInsight_windows_winnas_251RP1_2_5_1_1665_x64.exe for 64 bit OS,
   and Symantec_DataInsight_windows_winnas_251RP1_2_5_1_1665_x86.exe for 32 bit
   OS.

Additional Notes:
1. At this time, automated roll back of patch is not supported. To roll back the
   patch manually:
   a. Remember to take a backup of original files before you install the rolling patch.
   b. To roll back the patch, stop all Data Insight services, overwrite the patched 
      files with original files from backup, and restart services.
2. To confirm if a system has been patched, check the version of Data Insight using
   "Add/Remove Programs" applet in the Control Panel.