* * * READ ME * * *
          * * * Veritas Disaster Recovery Advisor 6.4.1 * * *
                          * * * Patch 3 * * *
                         Patch Date: 2015-06-30


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH
   * KNOWN ISSUES


PATCH NAME
----------
Veritas Disaster Recovery Advisor 6.4.1 Patch 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows Server 2012 R2 X64 and IA64
Windows Server 2008 R2 X64 and IA64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Disaster Recovery Advisor 6.4.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.4.1_HF3
* 3812493 (3812491) * Obsolete scan issues are not removed after storage proxy
replacement.
* Gap ID 448 (VLAN ID Inconsistency) may open incorrect or unclear tickets.
* Invalid DRA database object remain following deletion of a host.
* Tomcat application information is partially collected.
* WebSphere deployments info partially collected.
* Gap ID 00251HSNA (number of Netapp hot spares) may open incorrect tickets.
* Solaris zones partially collected.
* Gap ID 00430VMWCOI (ESX option inconsistency) may open tickets with no details.
* WebLogic domain info partially collected.
* Oracle ASM disk group not connected to physical volume on Linux hosts.
* Incorrect ticket regarding suboptimal SAN I/O policy.
* vCenter scan fails with an exception.
* Incorrect tickets opened by gap ID 494 (NTP best practices) when an ESXi host
is not selected for scan
* Local IBM ServerRAID controllers are identified as IBM DS arrays.
* Gap ID 420 (vMotion misconfiguration) May open non-impactful tickets if DRS
mode is set to manual.
* Incorrect HDS arrays are identified on hosts accessing VNX and HDS.
* Tickets of Gap ID 2410 (SRM Protection Group consistency) are unclear.
* Invalid file system name collected.
* Incorrect ticket regarding mount resources in Solaris Zone environment.
* Incorrect ticket regarding shared storage not connected to cluster nodes.
* Gap signatures may fail to run successfully.
* Topology does not show the connection between WebLogic server and its host.
* Failure to save ASM DG connection.
Changes and Enhancements
-------------------------
* Improved performance of data validation and correction processes.
* Internal data validation and correction processes no longer disallow user login.
* Ability to disable the SLA tab and enrichment added.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: 6.4.1_HF3

* 3812493 (Tracking ID: 3812491)

SYMPTOM:
* Obsolete scan issues are not removed after storage proxy
replacement.
* Gap ID 448 (VLAN ID Inconsistency) may open incorrect or unclear tickets.
* Invalid DRA database object remain following deletion of a host.
* Tomcat application information is partially collected.
* WebSphere deployments info partially collected.
* Gap ID 00251HSNA (number of Netapp hot spares) may open incorrect tickets.
* Solaris zones partially collected.
* Gap ID 00430VMWCOI (ESX option inconsistency) may open tickets with no details.
* WebLogic domain info partially collected.
* Oracle ASM disk group not connected to physical volume on Linux hosts.
* Incorrect ticket regarding suboptimal SAN I/O policy.
* vCenter scan fails with an exception.
* Incorrect tickets opened by gap ID 494 (NTP best practices) when an ESXi host
is not selected for scan
* Local IBM ServerRAID controllers are identified as IBM DS arrays.
* Gap ID 420 (vMotion misconfiguration) May open non-impactful tickets if DRS
mode is set to manual.
* Incorrect HDS arrays are identified on hosts accessing VNX and HDS.
* Tickets of Gap ID 2410 (SRM Protection Group consistency) are unclear.
* Invalid file system name collected.
* Incorrect ticket regarding mount resources in Solaris Zone environment.
* Incorrect ticket regarding shared storage not connected to cluster nodes.
* Gap signatures may fail to run successfully.
* Topology does not show the connection between WebLogic server and its host.
* Failure to save ASM DG connection.
Changes and Enhancements
-------------------------
* Improved performance of data validation and correction processes.
* Internal data validation and correction processes no longer disallow user login.
* Ability to disable the SLA tab and enrichment added.

DESCRIPTION:
* When a user replaces the proxy used to scan a storage system, scan issues
regarding last scan through the previous proxy remain in the Scan
Troubleshooting page and report.
* Occasionally tickets of gap ID 448 are opened that do not show any VLAN ID
inconsistency.
* The data presented in the table under the ticket description is not
highlighted and does not mark the abnormal VLAN id. 
* When a user deletes a host, an invalid object remains in the DRA database. The
existence of such invalid objects impact the duration of internal DRA data
validation and correction processes which may require a long period of time to
complete. 
* When Tomcat uses a non-default directory, tomcat configuration is not collected.
* In rare cases, the deployments information of a WebSphere Application server
is not collected. 
* In certain conditions, Gap ID 00251HSNA (number of Netapp hot spares) may open
incorrect tickets. 
* In rare cases, specific solaris zones may not be collected and documented. 
* In certain conditions, Gap ID 00430VMWCOI (ESX cluster disk option
inconsistency) may open tickets that do not include any information under the
Description tab.
* In rare cases, the domain information of a WebLogic Application server is not
collected. 
* In certain cases, Oracle ASM disk groups are not always correctly associated
with physical volumes on Linux hosts. 
* DRA may incorrectly open suboptimal SAN I/O policy tickets when the selected
policy is PRNX_PSP_RR. 
* When the target vCenter returns no information for license query, the scan of
the target vCenter will fail.
* When a host is returned by a scanned vCenter but the host itself is not
enabled for scanning, an incorrect ticket is opened by Gap ID 494 for the host. 
* Local IBM ServerRAID controllers are incorrectly identified as IBM DS arrays. 
NOTE: Following the installation of the hotfix and full scan, delete any
“IBM.Serv” storage systems listed under step 2 of the configuration wizard.
* When VMware DRS mode is set to Manual, non-impactful tickets may be opened by
gap ID 420. 
* Incorrect HDS arrays are identified on hosts accessing VNX and HDS. 
NOTE: Following the installation of the hotfix and full scan, delete any HDS
systems listed under step 2 which are not identified as actual HDS system by the
storage administration team.
* The risk and information included in tickets of Gap ID 2410 are unclear * 
* In rare cases, the system collected an invalid file system name. As a side
effect, RPO SLA gaps could go un-detected. 
* Gap ID 00500VCSONNOMOUNT may generate false tickets regarding the path of
mount resources. 
* In rare cases Gap ID 00571GCSGNM may generate incorrect tickets regarding
cluster node not connected to the shared storage devices. 
* Execution of Gap signatures may fail to complete successfully, reporting an
error in the log file (Gap IDs 456, 380, 494, 418, 239, 1600, 419, 458). 
* In rare cases, DRA may not associate the WebLogic server object with its Host.
* In certain cases, DRA may fail to save Oracle ASM DG connections and report
“too many connections have the same specified keys” error in the log file. 
Changes and Enhancements
------------------------
* The system runs internal data validation and correction processes upon tomcat
startup and as part of the risk analysis (processes known as “cleaners”). When a
large number of invalid objects exist, the correction process may require a long
period of time. This hotfix includes performance improvements for the two main
validation and correction processes (“missing key entity” and “Host/OS mismatch”).
* DRA behavior was changed to allow user login while internal DRA data
validation and correction processes are running. 
* It is now possible to disable the SLA tab functionality system-wide. Once
disabled and following a tomcat restart, the SLA tab will not be presented.
Furthermore, risk analysis will not perform tasks related to the SLA tab. 
To disable the SLA tab:
    •	Backup the current DRA Configuration.xml file, located under
[TOMCAT_HOME]\webapps\DRA\WEB-INF\classes\conf. Do not skip this step.
    •	Edit the Configuration.xml file and add the following property under the
“” section:
Property privacy="public" category="SLA" description="Activate SLA Module"
valuetype="boolean" name="activate.sla.module" defaultValue="true"
info="Changing this property will take effect only after the next user login"/
    •	Take care not to modify any other elements within the Configuration xml
file, and to keep the XML structure intact. In case the Configuration xml file
is malformed, DRA will fail to start.
    •	Restart Tomcat.
    •	Login to DRA and navigate to the Configuration tab. Select System
Properties on the left navigation tree and edit the “Activate SLA Module” under
the SLA properties group. Set the property value to “No”.

RESOLUTION:
Symantec has modified the code to resolve these issues.



INSTALLING THE PATCH
--------------------
1. Download the patch DRA_6.4.1_HF3.exe and copy it to the master DRA server.
2. On the master DRA server, stop the DRA web server using the following steps:
    a. Open a command line window running with administrator privileges
    b. Enter the following commands: 
        # net stop TomcatWatchDog
        # net stop tomcat7
3. Locate the DRA folder. By default, it is in the path: 
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\ 
4. Make a copy of the DRA folder and store it in another location (do not store the copy under the tomcat tree). The patch updates files in this folder, so if you need to revert to the unpatched version of DRA, you will need the original folder.
5. Go to the folder where you downloaded the patch. Find DRA_6.4.1_HF3.exe and double-click it.
6. Follow the steps in the wizard to install the patch. 
7. On the master DRA server, start the DRA web server using the following steps:
    a. Open a command line window running with administrator privileges
    b. Enter the following commands: 
        # net start tomcat7
        # net start TomcatWatchDog
8. Login to DRA. 


9. Verify that the build number is correct. On the DRA main screen, click "About". The build number should be 37917.


REMOVING THE PATCH
------------------
Symantec strongly recommends that you install the patch. However, if after installing it you need to revert to the unpatched version of DRA 6.4.1, use the following procedure:

1. Make sure you still have the backed up copy of the pre-patched, version 6.4.1 DRA folder
2. On the master DRA server, stop the DRA web server using the following steps:
    a. Open a command line window running with administrator privileges
    b. Enter the following commands: 
        # net stop TomcatWatchDog
        # net stop tomcat7
3. Locate the DRA folder. By default,  it is in the path:
    C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\ 
4. Delete the "DRA folder"
5. Copy the backed up folder to its original location.  If you have changed the name of the copied folder, make sure to rename it to "DRA" (not including the quotes).
6. On the master DRA server, start the DRA web server using the following steps:
    a. Open a command line window running with administrator privileges
    b. Enter the following commands: 
        # net start tomcat7
        # net start TomcatWatchDog


KNOWN ISSUES
------------
* Tracking ID: 3812504

SYMPTOM: No Symptom Found

WORKAROUND: No WorkAround Found



SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE