Disaster Recovery Advisor Release Notes

Disaster Recovery Advisor Release Notes
Symantec™ Disaster Recovery
Advisor Release Notes
AIX, ESX, HP-UX, Linux, Solaris,
Windows Server
6.4.1
2
Symantec Disaster Recovery Advisor Release Notes
The software described in this book is furnished under a license agreement and may be
used only in accordance with the terms of the agreement.
Product version: 6.4.1
Document version: 6.4.1 Rev 1
Legal Notice
Copyright © 2015 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas and Symantec Storage Foundation are
trademarks or registered trademarks of Symantec Corporation or its affiliates in
the U.S. and other countries. Other names may be trademarks of their respective
owners.
j-Interop: Pure Java - COM Bridge
The product described in this document is distributed under licenses restricting
its use, copying, distribution, and decompilation/reverse engineering. No part of
this document may be reproduced in any form by any means without prior
written authorization of Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR
CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION
CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT
NOTICE.
The Licensed Software and Documentation are deemed to be commercial
computer software as defined in FAR 12.212 and subject to restricted rights as
defined in FAR Section 52.227-19 “Commercial Computer Software - Restricted
Rights” and DFARS 227.7202, “Rights in Commercial Computer Software or
Commercial Computer Software Documentation”, as applicable, and any
successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation
by the U.S. Government shall be solely in accordance with the terms of this
Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
3
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our
online Knowledge Base. The Technical Support group works collaboratively with
the other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product
Engineering and Symantec Security Response to provide alerting services and
virus definition updates.
Symantec’s support offerings include the following:

A range of support options that give you the flexibility to select the right
amount of service for any size organization

Telephone and/or web-based support that provides rapid response and
up-to-the-minute information

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7
days a week basis
Premium service offerings that include Account Management Services
For information about Symantec’s support offerings, you can visit our website
at the following URL:
http://www.symantec.com/business/support/index.jsp
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.

Contacting Technical Support
Customers with a current support agreement may access Technical Support
information at the following URL:
http://www.symantec.com/business/support/contact_techsupp_static.jsp
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to
replicate the problem.
When you contact Technical Support, please have the following information
available:

Product release level

Hardware information

Available memory, disk space, and NIC information

Operating system

Version and patch level
4

Network topology

Router, gateway, and IP address information

Problem description:

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes
Licensing and registration
If your Symantec product requires registration or a license key, access our
technical support web page at the following URL:
http://www.symantec.com/business/support/
Customer service
Customer service information is available at the following URL:
http://www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs or manuals
Support agreement resources
If you want to contact Symantec regarding an existing support agreement,
please contact the support agreement administration team for your region as
follows:
Asia-Pacific and Japan
[email protected]
Europe, Middle-East, and Africa
[email protected]
North America and Latin America
[email protected]
Documentation
Product guides are available on the media in PDF format. Make sure that you are
5
using the current version of the documentation. The document version appears
on page 2 of each guide. The latest product documentation is available on the
Symantec website.
https://sort.symantec.com/documents
Your feedback on product documentation is important to us. Send suggestions
for improvements and reports on errors or omissions. Include the title and
document version (located on the second page), and chapter and section titles of
the text on which you are reporting. Send feedback to:
[email protected]
6
Contents
Introduction ........................................................................................................... 9
DRA features .......................................................................................................... 9
System requirements and software limitations ............................................. 10
New features ......................................................................................................... 11
New privileged commands ................................................................................. 12
Additional changes and enhancements ........................................................... 12
Fixed issues ........................................................................................................... 13
Known issues ........................................................................................................ 14
Limitations ........................................................................................................... 23
Installation Notes for This Release .................................................................. 27
Upgrade for This Release ................................................................................... 27
Getting help .......................................................................................................... 28
8 Contents
Symantec Disaster
Recovery Advisor Release
Notes

Introduction

DRA features

System requirements and software limitations

New features

Fixed issues

Fixed issues

Getting help
Introduction
This document provides important information about Symantec Disaster
Recovery Advisor (DRA).
For important updates regarding this release and for more information about
Symantec Disaster Recovery Advisor (DRA), review this entire document and see
the Late-Breaking News TechNote on the Symantec Technical Support Web site:
www.symantec.com/docs/TECH68401
DRA features
DRA is a data protection risk assessment solution that lets you diagnose high
availability (HA) and disaster recovery (DR) problems (also called gaps) and
10 Symantec Disaster Recovery Advisor Release Notes
System requirements and software limitations
optimize data protection. DRA enables enterprises to effectively manage
business continuity implementations, to ensure that their critical business data
is protected. DRA automatically detects and alerts you to any potential gaps,
best practice violations, or service level agreement (SLA) breaches.
DRA is an agentless enterprise discovery and monitoring tool that automatically
scans your infrastructure and detects gaps and infrastructure vulnerabilities in
your HA/DR implementation.
DRA gathers information about your environment and does the following:

Provides automated insight into your data replication environment to create
an online, detailed, and up-to-date HA/DR topology

Automatically detects and analyzes gaps and unprotected production areas
using a signature knowledge base of over 5,000 signatures

Discovers the current data protection status of your critical applications and
compares it to the state needed to comply with HA/DR SLAs
DRA uses this information to provide the following:

Detailed recommendations on how you can improve your environment,
based on best practices and recovery objectives.

Detailed lists and information about current data protection and HA/DR
risks and the prioritized actions for fixing them. DRA also provides a variety
of tools that let you drill down and analyze your environment using detailed
tables and topology maps. You can use this information to fix the problems
that DRA detects.

Identify differences between production, standby, and DR hosts.

Auditing and compliance documentation, including a map of your
production environment, disaster recovery configuration, and
dependencies.
System requirements and software limitations
For more information about system requirements and software limitations,
refer to the Symantec Disaster Recovery Advisor Support Requirements
document.
Symantec Disaster Recovery Advisor Release Notes
New features
New features
This DRA release introduces new features in the following categories:
New platform support

Zero Virtual Replication

NetApp Cluster (cDOT)
For more information on new platform support, refer to the DRA 6.4.1
Support Requirements and DRA 6.4.1 Deployment Guide.
Agent-based data collection

A new scan method has been added

Users may install a DRA agent on hosts and storage CLI servers. The agent
performs data collection tasks and communicates with the master server (or
collector server if used)
For more information on data collection using agent, refer to the DRA 6.4.1
Support Requirements, DRA 6.4.1 Deployment guide, and DRA 6.4.1 User
Guide.
Gaps

New gap signatures
11
12 Symantec Disaster Recovery Advisor Release Notes
New privileged commands
New privileged commands
For scanning NetApp Filers and NetApp DFM, the following rights must be
granted to the user.
Right
Mandatory?
Required for scanning
api-license-v2-list-info
Yes
NetApp Filers (7-Mode) / DFM
For more information, refer to the DRA 6.4.1 Deployment guide.
Additional changes and enhancements
Following are the additional changes and enhancements done in this release of
Symantec Disaster Recovery Advisor.
The new tab named Virtualization has been added to the SLA
policy
The Virtualization tab under the SLA policy allows the user to define replication
SLA goals for Zerto VM replications (RPO, site).
Ability to open storage array topology from the Configuration
Wizard
The Open Storage Array Topology button has been added to the Step (2) - Storage
Discovery of the Configuration Wizard.
Deletion of multiple business entities
Support for the deletion of multiple business entities has been added to the
Business Entities Configuration page.
Additional options for Business Entity import from the CSV
file
A new system property is available which controls whether the import process
will remove any current Business Entity associations prior to mapping a
resource to a new business entity. The property name is “Override current host
association when importing Business Entities” and it is disabled by default.
Symantec Disaster Recovery Advisor Release Notes
Fixed issues
Support for DRA to run on Windows 2012 R2 OS
Support has been added for DRA to run on Windows 2012 R2 servers.
Fixed issues
This DRA release fixes the following issues:
Scanning Validation Enrichment failure
In certain conditions, the Scanning Validation Enrichment may fail and report
an error in the System Event Log. [A350]
Invalid ticket for missing file systems on a standby host
Gap 00243SBMPNE may generate tickets which reference invalid / non-existent
file systems. [G335]
Incorrect topology icons for GoldenGate objects
The Oracle GoldenGate objects are not represented with the correct icons in the
Topology tab. [A312]
Data Collection Expansion packages write duplicated records
to the DRA Database Views
The Data Collection Expansion packages write duplicated records to the DRA
Database Views. [A300]
Collection of Storage Discovery User Interface issues
A number of Storage Discovery UI issues - adding a storage array twice results
in scan error [A213], not all arrays have the scanning indication when scanning
a proxy [A280], duplicate records appearing briefly [A273]
Non-impactful differences may be reported for dynamic,
case-insensitive, site-dependent parameters
In certain cases, DRA may report differences relating to options that are
dynamically changing or depending on the location and thus non-impactful
(ESX Misc.SIOCControlFlag). [G1200]
13
14 Symantec Disaster Recovery Advisor Release Notes
Known issues
Topology of 00456VMPCIC tickets does not show all port
groups
Topology of 00456VMPCIC tickets does not show port groups for all the relevant
hosts. [G1246]
Incorrect ticket regarding missing file systems on a Standby
host (00243SBMPNE)
In certain conditions, an incorrect ticket is reported regarding missing file
systems on a standby host where the missing file systems are invalid. [G335]
Scan issue does not present correctly the script name
In certain conditions, the “command with high importance timed out” scan issue
does not correctly present the name of the script executed. [A330]
Failure to add a new collector
In certain conditions, users may fail to save the information of a new collector.
[A306]
Known issues
This DRA release has the following known issues planned to be fixed in future
releases.
If you contact Symantec Technical Support about one of these issues, refer to
the incident number in brackets.
Ticketing and reporting issues
False tickets for database files stored on a mixture of RAID
types [P3314]
When rollback segments and data files are separated, DRA may generate false
tickets about database files stored on a mixture of RAID types.
Workaround: Suppress the tickets.
False tickets for an EMC Symmetrix device [P4439]
DRA may generate false tickets about EMC Symmetrix device ID 000.
Workaround: Suppress the tickets.
Symantec Disaster Recovery Advisor Release Notes
Known issues
False tickets may be generated after an Oracle RAC failover
[P6175]
When an oracle RAC failover occurs, DRA may generate false tickets about
image storage replication errors.
Workaround: Suppress the tickets.
False tickets may be generated if collectors' times are not
synchronized [P5975]
When cluster nodes are scanned using different collectors, DRA may generate
false tickets if the collectors' times are not synchronized.
Workaround: Suppress the tickets.
The dependency between Path (PV) to HBA is not always
available [P7638, P7612]
Tickets and Topology involving I/O paths may not show the connection between
an I/O path and its HBA port.
Host HBA Comparison report is occasionally not readable in a
standard PDF/RTF report size [A14]
Due to a large number of HBA properties, the Host HBA Comparison report may
not be readable when executed for Linux and exported as PDF/RTF.
Workaround: Export the report to excel.
False tickets regarding missing mount point directories
[P7349]
In specific cases, false tickets of Gap 00518VCSORARES may be reported due to
permission issues.
Workaround: Contact Symantec technical support for assistance.
Non-impactful ticket regarding mixed storage may be opened
when ASM mirroring is used [P7607]
When ASM mirroring is used and each mirror resides on a different array, an
incorrect ticket regarding mixed storage may be opened.
Workaround: Suppress the tickets.
15
16 Symantec Disaster Recovery Advisor Release Notes
Known issues
False tickets of Gap 01003WSMANR - Windows Services not
running [P7333]
When configured with 'Automatic Trigger Start', DRA may still report these
services as such that should be running.
Workaround: Suppress the tickets or the Gap type.
Duplicate gap suppression messages in the Ticket History tab
[A19]
After suppressing a gap and performing multiple ticket searches, the History tab
of a ticket of the suppressed gap may show multiple suppression records.
Incorrect tickets are opened for MSCS when resource names
end with white space [P6724]
Incorrect tickets may be reported for Microsoft Cluster when resource names
end with white space.
Workaround: Suppress the ticket.
Incorrect ticket regarding mount resources in Solaris Zone
environment [G378]
Gap 00500VCSONNOMOUNT may generate false tickets regarding the path of
mount resources.
Workaround: Suppress the ticket.
False ticket regarding masking configuration inconsistency
[G364]
Gap 00322SANMIC may generate incorrect ticket when the host name is defined
using capital letter on the storage and using lower case letters on the host (or
vice versa).
Workaround: Suppress the ticket.
NFS share is mistakenly recognized as CIFS share [G360]
Gap 00360NFSIA may generate tickets that incorrectly classify NFS as CIFS.
Symantec Disaster Recovery Advisor Release Notes
Known issues
Simple recovery mode tickets are opened for Snapshot
databases [G351]
Gap 01074MSSQLRMS generates a non-impactful ticket regarding Simple
Recovery mode for snapshot databases.
Workaround: Suppress the tickets.
Incorrect ticket regarding shred storage not collected to
cluster nodes [G340]
In rare cases, Gap 00571GCSGNM may generate incorrect tickets regarding
cluster node not connected to the shared storage devices.
Workaround: Suppress the tickets.
Incorrect ticket regarding EMC CLARiiON/VNX - number of
hot spares [G1011]
In certain conditions, DRA may report incorrect tickets regarding suboptimal
number of hot spares for EMC CLARiiON or VNX array.
Workaround: Suppress the tickets.
Incorrect ticket regarding missing VCS LV resources [G1173,
G1185]
In specific circumstances, DRA may incorrectly open tickets regarding missing
VCS LV resources.
Workaround: Suppress the tickets.
Incorrect ticket regarding suboptimal SAN I/O policy [G1177]
DRA may incorrectly open suboptimal SAN I/O policy when the selected policy
is PRNX_PSP_RR.
Workaround: Suppress the tickets.
A ticket may not be opened regarding insufficient number of
Netapp hot spares [G1240]
In certain conditions, the system may not open a ticket regarding an issue of
insufficient number of NetApp hot spare disks.
17
18 Symantec Disaster Recovery Advisor Release Notes
Known issues
Incorrect Hosts and VLAN Ids are highlighted in the ticket
description of signature 00448VLANCIC [G1239]
Tickets of Gap Signature 00448VLANCIC do not correctly color red the hosts
and VLAN Ids presented in the data table.
Incorrect tickets regarding VLAN Id inconsistency
(00448VLANCIC) [G1234]
In certain conditions, incorrect tickets of Gap Signature 00448VLANCIC stating
that VLAN id inconsistency was detected where in fact it is aligned.
In specific scenarios, when a replication source becomes the
target and the target becomes the source, DRA does not
calculate the data age for the replication [P6484]
This error may occur when, between two scans, the source is changed to be the
target and the target is changed to be the source.
Topology view issues
The Topology search for relationships may take too long to
complete [P2757]
The search for relationships which contain many records may take several
minutes to complete.
Workaround: Symantec recommends to use the Topology module, browse to the
selected host, and review the associations between the host’s physical volumes
and SAN devices. This process is more focused, efficient, and significantly
shorter.
Service Level Agreement (SLA) issues
In certain circumstances, the SLA module is only partially
updated [P4172]
Adding a business entity partially updates the SLA module.
Workaround: After you add a business entity, run the analysis cycle so that the
changes take effect.
Symantec Disaster Recovery Advisor Release Notes
Known issues
Configuration issues
Setting an SLA in the Edit Business Entity wizard might fail in
the Internet Explorer (IE) 6 [P5654]
JavaScript errors may pop up when setting an SLA in the Edit Business Entity
wizard using the Internet Explorer 6.
Workaround: Try again or use the Edit Role & SLA Definition button.
Some user interface functions might not work correctly in IE
10 and IE 11 [A254]
Some user interface functions might not work correctly using Internet Explorer
10 or Internet Explorer 11.
Workaround: Use Internet Explorer 10/11 Compatibility View.
Errors presented regarding Active Directory connection are
not informative [A69]
In some cases, a detailed error message regarding the Active Directory
connection error is not presented.
Workaround: Review the rg.0.log file for additional information or contact
Support.
Configuration tab - user selection is dismissed due to table
data refresh [A247]
In specific screens of the Configuration tab, user selection of records gets
unselected after a short period of time (refresh interval).
The collector configuration file is not updated [A11]
While updating the DRA server configuration file, the change might not
populate to all the collectors.
Workaround: Restart the DRA server and then restart all the collectors.
Manually adding Host URLs reduces the size of the list box
[A10]
When adding Host URL in the Active Directory Configuration screen, the size of
the list box is decreased with each host URL added.
19
20 Symantec Disaster Recovery Advisor Release Notes
Known issues
Deleted AD domains may still appear in the Add User
dialogue [A21]
Deleted Domains will be presented in the domain field of the Add User dialogue.
Users may manage scheduled reporting tasks created by
other users [A55]
Users may see and edit scheduled reports tasks that were created by other users,
potentially for entities external to their own user scope.
Scanning issues
When DRA scans a suspended DB2 database, queries may fail
[P4438]
If DRA scans a database when the database is suspended, most queries may fail.
DB2 discovery fails on a host scanned using a proxy [5049]
DRA cannot discover DB2 on a UNIX host that is scanned through a proxy.
Workaround: Scan the host directly and not through the proxy.
DRA may identify unsupported devices incorrectly [P4310]
DRA shows unsupported storage array devices as direct-attached storage (DAS)
devices, which may open false tickets.
Workaround: Suppress the tickets or avoid scanning hosts that use storage that
DRA does not support.
Only active Network Interface Cards (NICs) are collected on
Solaris [P5934]
DRA does not collect NICs which are “unplumb”.
IBM DS GlobalMirror replication might not be presented
correctly [P6481]
DRA may fail to present IBM DS GlobalMirror replication.
Workaround: Contact Support for assistance.
Symantec Disaster Recovery Advisor Release Notes
Known issues
IBM DS/XIV LUN discovery might be incorrect for
Solaris/HP-UX hosts [P6480]
DRA may fail to discover the correct LUN for UNIX hosts accessing IBM DS or
XIV storage.
Workaround: Contact Support for assistance.
Failure when scanning a vCenter with no managed ESX/ESXi
hosts [P7659]
When executing a scan of a vCenter with no hosts, the scan fails.
Server incorrectly classified as partially scanned [P7610]
In rare circumstances, an incorrect scan error is reported regarding a
“/dev/unknown” PV that leads to a partial scan status.
Workaround: Suppress the scan issue and consider the scan as successful.
Incorrect collection of XIV cluster name [P7339]
When the cluster name includes multiple words separated by white space, only
the first word is collected.
Occasionally a non-impactful scan error message are
presented
A scan error with the 'No MPIO disks are present' message is occasionally
opened for Windows servers. [P7307]
Scan errors for EMC VNX clone/mirror command may appear when these
features are disabled. [P7240]
Workaround: Ignore or suppress the scan issue under the Scan Troubleshooting
screen
Inactive disk groups and logical volumes are not always
collected [P7250, P7041]
Information regarding inactive disk groups and unmounted logical volumes is
not always collected.
Scan of IBM UDB V10.x may fail [P7207]
The scan of IBM UDB version 10 and above may fail.
21
22 Symantec Disaster Recovery Advisor Release Notes
Known issues
HBA driver information is not always available for Linux
systems [P7196]
In rare cases, HBA model, driver, and firmware information is not available for
Linux systems.
HMC scan may fail in an IBM FLEX environment [P7667]
When HMC is scanned in an IBM Flex environment, the scan may fail.
Workaround: Contact support for assistance.
If the security level on the Naviseccli server is set to
MEDIUM, EMC VNX scan hangs. [P6964]
Workaround: Reduce the security level to allow scanning.
When the password contains special characters, EMC VNX
arrays scan fails [P6962]
Workaround: Change the password such that no special characters are
included.
Discovery may report UDB instances as down [P6949]
In rare cases, DRA may report online UDB instances as down.
Workaround: Contact Support for assistance.
Free space information is not available for Windows 2003
Servers [P6053]
Free space information is not available for Logical volumes on Windows 2003
Servers.
Scan status report does not include Management Consoles
[A25]
The Scan Status report does not include information regarding scan of
management consoles.
Workaround: Review the status of the consoles in the Configuration tab or in
the System Log report.
Symantec Disaster Recovery Advisor Release Notes
Limitations
Nodes with the same cluster name and ID are incorrectly
merged to a single VCS [P7773]
In certain cases when multiple clusters with the same name, DRA may
incorrectly merge these clusters to a single VCS.
Scanned virtual machine that is moved to a new vcenter
appears as a physical server [A344]
When a scanned virtual machine is migrated to a new vcenter, it may appear in
DRA as a physical server.
Workaround: From the View Hosts dialogue, delete the host. If not already
scanned, add the new vcenter to the scan, and then add the virtual machine on
the new vcenter to an enabled scan group.
Oracle ASM disk groups are not always collected [P7773]
In certain cases when multiple clusters with the same name, DRA may
incorrectly merge these clusters to a single VCS.
Agent scan failure on Windows servers with only .NET 4
installed [A319]
When the target Windows system is only installed with .NET 4, the DRA agent
fails to run VB data collection scripts on it.
Important Notes

To avoid false positive tickets about storage access or Storage Area Network
(SAN) I/O configuration inconsistency that involves backup servers,
configure the backup servers inside a business entity and assign the
‘Backup’ role.
Limitations
Assigning a profile to an Active Directory group

When assigning a profile to an AD Universal Group, the DRA master server
must have access to the Global Catalog of the AD Forest

When assigning a profile to an AD Local Domain Group, DRA will not be able
to assign the Profile to AD Users from a different Domain - even though such
configuration is valid within AD. In other words - an AD user can log in to
23
24 Symantec Disaster Recovery Advisor Release Notes
Limitations
DRA (with all the correct profiles assigned) only if each AD Local Domain
Group it belongs to is part of the same AD Domain the AD user belongs to
Oracle database discovery
To discover Oracle databases, start the Oracle process or ensure that the
/etc/oratab or /var/opt/oracle/oratab file is present.
Recovery point objective (RPO)/service level agreement (SLA)
DRA also has the following RPO/SLA limitations:

RPO/SLA is not supported in HDS

RPO/SLA for NetAPP only works for direct replication from primary devices

RPO/SLA for CLARiiON only works for direct replication from primary
devices

RPO/SLA for HP 3PAR only works for direct replication from primary
devices.

RPO/SLA is not calculated for EMC CLARiiON MirrorView/S

RPO/SLA is not calculated for IBM DS
Incorrect time logged in system log files when DLS is not
automatically updated
DRA log files may log incorrect timestamp when the DRA server is not
configured with automatic Day Light Saving adjustment.
DRA Database Views include a subset of the information
collected from target systems
DRA Database Views do not include information regarding VMware Virtual
Networking, Database Tablespaces, Installed Software and Kernel Parameters,
RecoverPoint consistency groups, LV mirroring, and Application Servers. Also,
it does not include the historical data.
In specific cases scan error messages are not sufficiently
informative
The Scan Troubleshooting screen occasionally presents scan error messages
that include the error code but no additional details.
Workaround: Run the erroneous command or script manually to see the full
scan error message. If further assistance required, contact Support.
Symantec Disaster Recovery Advisor Release Notes
Limitations
Incorrect tickets may open when target systems are not
scanned successfully
When certain target systems are not scanned successfully, DRA may open
incorrect tickets as a result.
Workaround: Search for the symbol specifying whether scan issues exist in the
ticket summary, and review any scan issues reported in the ticket or in the Scan
Troubleshooting prior to reviewing the risk details.
Large amount of memory is consumed when generating an
extremely large report [5455]
When generating reports with over 500 pages, large amount of memory may be
consumed
Workaround: Limit the scope of the report or divide it to multiple reports.
When importing objects into DRA, special characters are
converted [A87, A109, A105]
When importing names and properties of objects from CSV/CMDB/API, special
characters such as “&” are converted to alphanumeric chars.
Non-impactful differences may be reported for dynamic or
site-dependent parameters [P7219]
In certain cases, DRA may report differences relating to options that are
dynamically changing or depending on the location and thus non-impactful.
Workaround: Suppress these differences.
SSH key supports only keys with less than 4000 characters
[P6645]
SSH key only supports the keys with less than 4000 characters.
When NTLMv2 is used, authentication may fail [P7206]
Scanning systems in an environment where only NTLMv2 is allowed may fail
without additional configuration.
Workaround: Contact support for assistance.
25
26 Symantec Disaster Recovery Advisor Release Notes
Limitations
DRA may fail without notice when no space left on its disk
drives [A41]
When nearly no space is left on the disk drives storing the DRA software, the
system may fail without a notice.
Workaround: Take particular care to ensure sufficient free disk space is
available on the master server.
HMC is required in order to scan IBM VIO environments
[P6835]
If HMC is not available and IVM is used, contact Support for assistance.
CSV Import of Business Entities does not create new sites
[A15]
The Import process will use the site field to correctly match hosts specified in
the CSV file to existing hosts, but will not create the sites if they do not exist in
the system.
Workaround: Use step 3 of the Configuration Wizard to define any missing sites
(manually or through CSV import).
Multiple Zerto virtual protection groups with the same name
are not supported
If multiple Zerto virtual protection groups are defined with the same name, only
one group will be collected and analyzed by DRA.
Symantec Disaster Recovery Advisor Release Notes
Installation Notes for This Release
Installation Notes for This Release
Read the Installation Procedure chapter of the User Guide for guidance about
installing DRA V6.4.1. In addition, review the Deployment Guide for information
on the DRA infrastructure requirements and the preparations needed for
scanning your data centers.
Upgrade for This Release
An upgrade path to the DRA version 6.4.1 is available from the DRA 6.4 release.
If your system is currently installed with an earlier release, an upgrade to
version 6.4 is mandatory before upgrading to version 6.4.1.
Important Notes:

Prior to upgrading, take care to read the release notes in full, and make any
necessary changes to the DRA infrastructure and/or to user account
permissions as required, and ensure sufficient free disk space is available on
the master server.

Prior to upgrading, verify you have an up-to-date backup of the DRA server
disk drives using your standard backup tools, and an up-to-date DRA
database export. The database export can be generated using the EXPDP or
EXP Oracle command.

Once the upgrade on the master DRA server is completed and the Tomcat
service starts, DRA will automatically check and upgrade the DRA
collectors. There is no manual collector upgrade process. For gradual
collector upgrade, disable the collectors before initiating the upgrade on the
master server, and gradually enable the collectors you wish to upgrade
following the completion of the software upgrade on the master server.

The upgrade will require the complete stop of DRA operations, including
data collections and data analysis. While it is a fully automatic process, the
length of the upgrade process may require several hours to complete in large
environments. During this time, it is important not to restart the DRA
server or terminate the upgrade task. In addition, it is essential that the
Oracle database used by DRA will be available throughout the upgrade
process.
To upgrade from version 6.4 to version 6.4.1:
1
Login as a local administrator to the master DRA Server.
2
Run the DRA_6_4_1.exe as an administrator.
3
Click Next in the Welcome screen.
4
Select “Yes, upgrade DRA 6.4 to 6.4.1".
27
28 Symantec Disaster Recovery Advisor Release Notes
Getting help
5
Accept the License Agreement and click Next.
6
Accept the GNU License Agreement and click Next.
7
Select whether to perform a database export prior to upgrading and whether
to start Tomcat 7 after the upgrade completes, and click Next. It is
recommended to keep the default settings.
8
Click Install to begin the Software Upgrade process.
9
Click Finish.
Getting help
If you have a current maintenance agreement, you may access Symantec
Technical Support information here:
www.symantec.com/business/support/contact_techsupp_static.jsp
Customer service information is available here:
www.symantec.com/support/assistance_care.jsp
Note: If you forget or lose the DRA administrator password, contact Symantec
Technical Support.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement