dro-win_x64-Hotfix_6_1_00001_129_3504056

 Basic information
Release type: Hot Fix
Release date: 2014-07-01
OS update support: None
Technote: TECH217647-Symantec Disaster Recovery Orchestrator (SDRO) Console server or Client application server crash when starting file replication
Documentation: None
Popularity: 3453 viewed    downloaded
Download size: 643.81 KB
Checksum: 4172095897

 Applies to one or more of the following products:
Disaster Recovery Orchestrator 6.1 On Windows x64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
3504056

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
        * * * Symantec Disaster Recovery Orchestrator 6.1 * * *
                      * * * Patch 6.1.0.001 * * *
                         Patch Date: 2014-06-23


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


PATCH NAME
----------
Symantec Disaster Recovery Orchestrator 6.1 Patch 6.1.0.001


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



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Disaster Recovery Orchestrator 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: Hotfix_6_1_00001_129_3504056
* 3504056 (3527428) A system crash occurs when you interrupt or trigger a replication activity on an application host after snapshots of the application data volumes or the replication volumes are created.


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

Patch ID: Hotfix_6_1_00001_129_3504056

* 3504056 (Tracking ID: 3527428)

SYMPTOM:
If you use Symantec Storage Foundation for Windows (SFW) or Microsoft
COW to create snapshots of the volumes associated with an application recovery
configuration, a system crash occurs when you interrupt or trigger a replication
activity.

DESCRIPTION:
You can use SFW or COW to create snapshots of the application data
volumes or the replication volumes. However, after you create the snapshots, if
you start, stop, pause, or resume the replication of application data, the
system crashes.

RESOLUTION:
This hotfix addresses the issue by updating the kernel component
that manages the file replication.

FILE / VERSION:
VxRep.sys / 6.1.1.129



INSTALLING THE PATCH
--------------------
This package contains self-extracting files that are specific to the processor architecture and operating system version.
Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or the CLI. Instructions for both the options are provided below.
NOTE: Install this hotfix on the on-premises application host and the cloud application host. The cloud application host is available only after the Takeover operation is performed. You may install the hotfix whenever you perform Takeover. You don't need to install this hotfix on the Console host.

Required pre-installation tasks for this hotfix
------------------------------------------------
1. Identify the application monitoring configuration; run:
hagrp - state
This command displays an output similar to the following:
#Group                      Attribute             System     Value
InfrastructureSG_SQLW2K8    State                 SQLW2K8    |ONLINE|
SQLServer2012_SG            State                 SQLW2K8    |ONLINE|
SQLServer2012_SG_FDA1349_SG State                 SQLW2K8    |ONLINE|
The application monitoring configuration is identified by the string "<ApplicationName> _SG".
For example, in the sample output, the configuration is SQLServer2012_SG.

2. Take the application monitoring configuration offline; run:
hagrp -offline <AppMonConfName>  -sys <SystemName> 
For example:
hagrp -offline SQLServer2012_SG -sys SQLW2K8

3. Confirm that the application monitoring configuration is offline; run:
hagrp -state
The output should appear similar to the following:
#Group                      Attribute             System     Value
InfrastructureSG_SQLW2K8    State                 SQLW2K8    |ONLINE|
SQLServer2012_SG            State                 SQLW2K8    |OFFLINE|
SQLServer2012_SG_FDA1349_SG State                 SQLW2K8    |ONLINE|

4. Identify the replication resources; run:
hares -state
This command displays an output similar to the following:
#Resource                            Attribute               System     Value
Agent_AAA                            State                   SQLW2K8    ONLINE
Agent_BBB                            State                   SQLW2K8    ONLINE
InfrastructureSG_SQLW2K8_AppStatusHB State                   SQLW2K8    ONLINE
MountMonitor_D_                      State                   SQLW2K8    ONLINE
MountMonitor_E                       State                   SQLW2K8    ONLINE
OLAP_AAA                             State                   SQLW2K8    ONLINE
OLAP_BBB                             State                   SQLW2K8    ONLINE
SQLServer2012_AAA                    State                   SQLW2K8    ONLINE
SQLServer2012_BBB                    State                   SQLW2K8    ONLINE
SQLServer2012_SG_FDA1349_RFGPrimary  State                   SQLW2K8    ONLINE
SQLServer2012_SG_FDA1349_VFRRFG      State                   SQLW2K8    ONLINE
SQLServer2012_SG_IPv4Monitor         State                   SQLW2K8    ONLINE
SQLServer2012_SG_lanman              State                   SQLW2K8    ONLINE
The "_VFRRFG" string is appended to each replication resource.
For example, in the sample output, the resource is SQLServer2012_SG_FDA1349_VFRRFG.

5. Take all the replication resources offline; run:
hares -offline <ResourceName>  -sys <SystemName> 
For example:
hares -offline SQLServer2012_SG_FDA1349_VFRRFG -sys SQLW2K8

6. Confirm that the application monitoring configuration is offline; run:
hares -state
The output should appear similar to the following:
#Resource                            Attribute               System     Value
Agent_AAA                            State                   SQLW2K8    OFFLINE
Agent_BBB                            State                   SQLW2K8    OFFLINE
InfrastructureSG_SQLW2K8_AppStatusHB State                   SQLW2K8    ONLINE
MountMonitor_D_                      State                   SQLW2K8    ONLINE
MountMonitor_E                       State                   SQLW2K8    ONLINE
OLAP_AAA                             State                   SQLW2K8    OFFLINE
OLAP_BBB                             State                   SQLW2K8    OFFLINE
SQLServer2012_AAA                    State                   SQLW2K8    OFFLINE
SQLServer2012_BBB                    State                   SQLW2K8    OFFLINE
SQLServer2012_SG_FDA1349_RFGPrimary  State                   SQLW2K8    OFFLINE
SQLServer2012_SG_FDA1349_VFRRFG      State                   SQLW2K8    OFFLINE
SQLServer2012_SG_IPv4Monitor         State                   SQLW2K8    ONLINE
SQLServer2012_SG_lanman              State                   SQLW2K8    OFFLINE

7. Identify the file replication configuration; run:
vxfradmin -viewconfig
This command displays an output similar to the following:
Total RFGs : 1
Log File Size           1024MB
Log Folder Path         \??\D:\
Name                    SQLServer2012_SG_FDA1349_RFG
Primary                 1
Root Folder Path        \??\E:\Program Files
dataaccess              1
The value against the Name label is the file replication configuration.
For example, in the sample output, the configuration is SQLServer2012_SG_FDA1349_RFG.

8. Pause the replication; run:
vxfradmin -pauserep <FileRepConfName> 
For example:
vxfradmin -pauserep SQLServer2012_SG_FDA1349_RFG


To install the hotfix using the GUI
------------------------------------
1. Double-click the hotfix executable file to extract its contents to a default location on the system.
By default, the files are extracted to:
"%programfiles%\Common Files\Veritas Shared\WxRTPrivates"

The Hotfix Installer Wizard is automatically launched after the files are extracted.

2. Click "Next" on the Welcome screen. 
The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to begin the hotfix installation. 
The status of each installation task is updated as it completes.

4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.

5. Restart the system.


To install the hotfix using the CLI
------------------------------------
1. Navigate to the "C:\temp> " directory, and run one of the following commands to extract the hotfix files to the default location:
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /x
or
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /extract

2. Navigate to the default location where the hotfix files are extracted.
By default, the files are extracted to: 
"%programfiles%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

3. At this location, run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber>  /silent

Here, <Hotfix_BuildVersion_IncidentNumber>  is the name of the hotfix file excluding the OS, platform, and .exe extension.

4. Follow the instructions displayed at the command prompt to complete the hotfix installation.

5. Restart the system.


Required post-installation tasks for this hotfix
----------------------------------------
1. Resume the replication; run:
vxfradmin -resumerep <FileRepConfName> 
For example:
vxfradmin -resumerep SQLServer2012_SG_FDA1349_RFG
The output should appear similar to the following:
"SFR SUCCESS (20000074) Successfully resumed replication."

2. Bring the application monitoring configuration online; run:
hagrp -online <AppMonConfName>  -sys <SystemName> 
For example:
hagrp -online SQLServer2012_SG -sys SQLW2K8

3. Confirm that the application monitoring configuration is online; run:
hagrp -state
The output should appear similar to the following:
#Group                      Attribute             System     Value
InfrastructureSG_SQLW2K8    State                 SQLW2K8    |ONLINE|
SQLServer2012_SG            State                 SQLW2K8    |ONLINE|
SQLServer2012_SG_FDA1349_SG State                 SQLW2K8    |ONLINE|


REMOVING THE PATCH
------------------
Additional Notes
----------------
- To confirm the installation of the hotfix, view the Windows Installed Updates list (Start >  Programs >  Programs and Features >  View Installed Updates), or run the following command:
vxhf.exe /list

By default, vxhf.exe is located at:
"%programfiles%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

The output of this command lists the hotfixes installed on a system.

- The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Veritas\VxHF"

- For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.symantec.com/business/support/index?page=content&id=TECH73446

- To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote: 
http://www.symantec.com/business/support/index?page=content&id=TECH73438

- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://www.symantec.com/business/support/index?page=content&id=TECH73443


SPECIAL INSTRUCTIONS
--------------------
DISCLAIMER
-----------
This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement.  Symantec disclaims all liability relating to or arising out of this fix. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into a Storage Foundation for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Symantec Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available if you sign up for notifications from the Symantec support site http://www.symantec.com/business/support and/or from Symantec Operations Readiness Tools (SORT) http://sort.symantec.com.


OTHERS
------
NONE