Veritas CommandCentral Disaster Recovery Advisor Release Notes 5.1

Transcription

1 Veritas CommandCentral Disaster Recovery Advisor Release Notes 5.1

2 Veritas CommandCentral Disaster Recovery Advisor Release Notes Copyright 2009 Symantec Corporation. All rights reserved. Product version: 5.1 Document version: Legal Notice Symantec, the Symantec logo, and Veritas 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. 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. THIS 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 and commercial computer software documentation as defined in FAR Sections and DFARS Section Symantec Corporation Stevens Creek Blvd. Cupertino, CA

3 Third-party legal notices Licensing and registration Technical support Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in Third-Party Legal Notices (vccdra_3rdpartyattributions.pdf). Veritas CommandCentral Disaster Recovery Advisor (DRA) is a licensed product. For information on how to install the license, see the Veritas CommandCentral Disaster Recovery Advisor User s Guide. For technical assistance, visit and select phone or support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer notification service.

4

5 Release Notes Veritas CommandCentral Disaster Recovery Advisor Release Notes What s included These release notes include the following topics: Introduction on page 6 DRA features on page 6 System requirements and software limitations on page 7 New features on page 7 Fixed issues on page 7 on page 9 Getting help on page 17

6 6 Veritas CommandCentral Disaster Recovery Advisor Release Notes Introduction Introduction DRA features This document provides important information about Veritas CommandCentral Disaster Recovery Advisor (DRA) by Symantec. Before you install DRA, review this entire document and read the Late-Breaking News TechNote for the latest information on updates, patches, and software issues for this release: DRA is a data protection risk assessment solution that lets you diagnose disaster recovery problems (also called gaps) and to 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 disaster recovery 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 disaster recovery topology Automatically detects and analyzes gaps and unprotected production areas using a signature knowledge base of over 2000 signatures Discovers the current data protection status of your critical applications and compares it to the state needed to comply with disaster recovery 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 disaster recovery 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. Auditing and compliance documentation, including a map of your production environment, disaster recovery configuration, and dependencies.

7 Veritas CommandCentral Disaster Recovery Advisor Release Notes System requirements and software limitations 7 System requirements and software limitations For more information about system requirements and software limitations, refer to the Veritas CommandCentral Disaster Recovery Advisor Support Requirements document. New features This DRA release introduces new features in the following categories: User management Multiple users can have administrator privileges The default user names are admin and user, replacing rgadmin and rguser You can reset the password using a secret question New reports Un-scanned Servers/Arrays report Infrastructure Change Log report Host Configuration Differences report SAN I/O Single Path report Storage Summary report Collection DRA automatically discovers IP addresses and database ports General New support tool New license mechanism Ping utility for hosts NetApp support in the SLA module Fixed issues DRA may generate irrelevant tickets for replication pairs When DRA detects a gap on a replication pair where neither its source nor its target device are used by hosts, DRA may generate irrelevant tickets. [3945] DRA generates tickets for development or QA databases When databases are configured with no archive log (such as development/qa databases), DRA may generate many tickets, even though these databases do not require an archive log. [3949]

8 8 Veritas CommandCentral Disaster Recovery Advisor Release Notes In NetApp filers, the Model property is missing In the Topology view, when you view the properties of NetApp filers, the Model property is blank. [3994] DRA does not log failures in general gaps When general gaps fail due to insufficient memory, DRA does not log the error in rg.0.log. [4121] When you view the topology of closed tickets, some entities may be missing properties and empty items may appear When you view the topology of closed tickets, properties are missing for entities such as file systems, volume groups, and so on. [4132] When both cluster hosts are manually defined as standby, DRA writes no available information as the ticket description When both cluster hosts are manually defined as standby, DRA writes no available information as the ticket description and logs an error in rg.0.log. [4138] NetApp SnapMirror Replication information is not displayed in one area of the user interface Sometimes NetApp SnapMirror Replication may be missing in the filer view under the SLA tab. [4169] This DRA release has the following known issues. They should be fixed in future releases. If you contact Technical Support about one of these issues, refer to the incident number in brackets. Ticketing and reporting issues Generating a Ticket Details report with the Topology option checked may take too long Depending on the options you check, generating a Ticket Details report with the Topology option may take a prohibitively long time. [3690]

9 Veritas CommandCentral Disaster Recovery Advisor Release Notes 9 Workaround: Schedule the report to be sent as an . DRA may generate false storage array inconsistency tickets about related storage devices and their arrays DRA may generate false tickets when you run maintenance tasks involving mirroring on the LVM level, such as upgrading an operating system service pack and migrating arrays. [3942] Workaround: Suppress the tickets. You cannot tell the difference between unused storage device tickets and manually suppressed tickets You cannot tell the difference between unused storage device tickets, which the system automatically suppresses, and manually suppressed tickets. [3806] Workaround: To help you differentiate between types of tickets, do one or both of the following: Before you suppress a ticket, use the rating system or add a note to it. Suppress the ticket for a limited time. Although a Windows dynamic volume usually includes multiple storage volumes, the Host Data Protection Path report shows only one The number of storage volumes reported on the dynamic volume differs from the actual number. [1596] Workaround: Use the Topology module to view all of the dynamic volume s storage volumes. DRA reports that volume groups stored on DAS have no DAS storage volumes. The Host Data Protection Path report shows volume groups stored on DAS with no DAS storage volumes. [2050] Workaround: Use the Topology module to view all of the volume group s storage volumes. DRA generates duplicate tickets for databases, file systems, and volume groups stored on mixed storage types When volume groups, file systems, or database files are stored on a mixed storage, DRA may generate multiple tickets with the same meaning. [3320]

10 10 Veritas CommandCentral Disaster Recovery Advisor Release Notes Workaround: Ignore or suppress the duplicate tickets. In a cluster switchover or failover event, DRA may close and reopen tickets When you switch active and passive roles for cluster hosts, DRA may automatically close tickets for the previously active node and open them for the currently active one. [3966] For source volume groups that are defined using direct logical-to-physical volume mapping, DRA may generate tickets about volume group replica inconsistency; however, each logical volume is consistent When you intentionally map specific logical volumes to specific physical volumes on the volume group, DRA may generate tickets for inconsistency, even though the inconsistency is intentional. [2296] Workaround: Suppress the tickets. DRA may generate multiple tickets with the same meaning DRA may generate duplicate tickets about inconsistencies in a volume group s tree structure and inconsistencies in its storage Meta device tree structure. [4303] Workaround: Ignore or suppress the duplicate tickets. DRA may generate duplicate tickets about the volume group and the database files that are stored on it DRA may generate duplicate tickets about a volume group and the database log, data, or control files that are stored on it. [4207] Workaround: Ignore or suppress the duplicate tickets. The Export Host Data Protection report to PDF/RTF button under Reports is grayed out Currently, DRA does not export this type of report. [4308] Items may expire when ECC is scanned If ECC is not being scanned properly, DRA may close and reopen tickets. This causes items to expire when ECC is scanned. [4278]

11 Veritas CommandCentral Disaster Recovery Advisor Release Notes 11 Workaround: This is only relevant in environments where DRA completes data from the ECC storage scope (non-default configuration). Schedule the scan when ECC is most idle. DRA may generate incorrect tickets about replica data age issues While a database is in cold/hot backup mode and its storage devices are being replicated, DRA may generate incorrect tickets about replica data age issues. [3371] Workaround: Suppress the tickets. DRA may generate incorrect tickets about multi-path inconsistency On HP-UX hosts, DRA may generate incorrect tickets about multi-path inconsistency. [4455] Workaround: Suppress the tickets. DRA generates duplicate tickets for a standby host When one primary host has an export mounted on another primary host, and this export is replicated to the standby host, but not exported on it, DRA generates duplicate tickets for the standby host. [4470] Workaround: Ignore or suppress the duplicate tickets. DRA may generate duplicate tickets about a host and its database Duplicate tickets are generated when a host belongs to one business entity and its database belongs to another. [4292] Workaround: Connect the database and its host to the same business entity or suppress/ignore the duplicate ticket. DRA may generate false tickets about a host When a host is connected to a Veritas type source storage device and its replica, if the volume group ID of the replica was changed, then DRA may generate false tickets. [4286] Workaround: Suppress the tickets.

12 12 Veritas CommandCentral Disaster Recovery Advisor Release Notes DRA does not discover issues about certain drives On Windows servers, DRA does not support disks mounted on folders or disks with no drive letter. DRA does not discover issues about these drives. [1684] DRA may generate false tickets about database files stored on a mixture of RAID types When rollback segments and data files are separated, DRA may generate false tickets about database files stored on a mixture of RAID types. [3314] Workaround: Suppress the tickets. DRA may generate false tickets about data age If devices are being synchronized during the DRA cycle time, DRA may generate false tickets about data age. [4139] Workaround: Suppress the tickets. DRA may generate duplicate tickets about suspended groups If all pairs of an EMC Symmetrix rdf group are suspended, DRA may generate duplicate tickets. [4430] Workaround: Ignore or suppress the duplicate tickets. DRA may generate false tickets about an EMC Symmetrix device DRA may generate false tickets about EMC Symmetrix device ID 000. [4440] Workaround: Suppress the tickets. Links in tickets may not point to the appropriate files In tickets, the database log, control, and data file links refer to the database itself. [4465] Workaround: In the Topology module, expand the database to see the files. The Tickets module may not show new tickets After you run a second cycle and open the Tickets module, it does not show any new tickets. [4793] Workaround: Run a search to show the newest tickets.

13 Veritas CommandCentral Disaster Recovery Advisor Release Notes 13 Cycle issues The DRA cycle takes too long to complete In rare circumstances, the DRA cycle (collection, analysis, and ticketing) may take over seven hours to complete. In most cases, cycle execution time will return to normal after several days. [4034] DRA may not collect ECC data and will generate an error DR may fail to collect ECC data and may write the error STS_HOST_DEVICEVG_ID: invalid identifier to the rg.0.log file. [4043] Queries may fail when DRA scans a suspended database If DRA scans a database when the database is suspended, most queries may fail. [4439] DRA does not collect device vendors in all environments On Red Hat Linux Advanced Server 2.1, DRA does not collect device vendors. [4199] The data age of a NetApp QTree in a replicated volume may not be correct Regardless of the volume data age, the data age of a NetApp QTree in a replicated volume is up to date. [4397] 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 This error may occur when, between two scans, the source was changed to be the target and the target was changed to be the source. [4410] A probe can be executed and discovered manually in the configuration wizard, even if it is disabled Selecting the Enabled option for a probe refers to whether or not the probe will run during a full scan. [4809]

14 14 Veritas CommandCentral Disaster Recovery Advisor Release Notes Topology view issues Installation issues The Topology search for relationships may take too long to complete When searching for Is stored on between a physical volume and a Symmetrix device, the results may not appear for 15 minutes. [2757] Workaround: Symantec recommends you use the Topology module, browse to the selected host, and review the associations between the host s physical volumes and Symmetrix devices. This process is more focused, efficient and significantly shorter. The Detection Date in the Topology view may differ from the actual date the items were detected The Detection Date in the Topology view may be incorrect when the items contained in an existing item changed. [3819] Memory size may be displayed inconsistently In HP-UX hosts, the memory size is displayed in TB instead of GB. [4220] If Tomcat is not running, DRA may not automatically start after installation In the last two screens of the installation process, if you choose not to start Tomcat, but then choose to start DRA, DRA does not start and an error message appears. This error occurs because Tomcat is down. [4106] Workaround: Manually start Tomcat and refresh the application page.

15 Veritas CommandCentral Disaster Recovery Advisor Release Notes 15 DRA fails to detect out-of-order hot-backup copies for Oracle 11 databases DRA may not detect certain risks relating to the out-of-order creation of database copies or replicas while in hot-backup mode. This issue does not affect detection of hot-backup copy risks in earlier Oracle versions, or the detection of other Oracle risks in all versions. [4864] SLA issues Scanning issues In certain circumstances, the SLA module is only partially updated Adding a business entity partially updates the SLA module. [4172] Workaround: After you add a business entity, run a full cycle so changes take effect. DRA may identify unknown devices incorrectly DRA shows unknown storage array devices as DAS devices, which may open false tickets. [4310] Workaround: Ignore or remove the tickets, or do not scan these hosts. A report that DRA successfully collected data may be incorrect DRA reports that it collected data successfully; however, privileged commands (using sudo and so on) fail. [1790] Workaround: Fix sudo permissions on the host. A report that DRA successfully scanned the Oracle ASM database may be incorrect DRA reports that it successfully scanned the Oracle ASM database; however, DRA does not have permission to query the v$asm disk group. [4287] Workaround: Configure permissions for the v$asm disk group.

16 16 Veritas CommandCentral Disaster Recovery Advisor Release Notes When an Oracle instance name differs from its database name, DRA detects the database as an instance and adds it to the system This error usually occurs in a Real Application Cluster (RAC) environment. If the database is changed or removed, DRA creates a new database and does not remove the old or changed database. [4813] Note: The instance is added to the system only if it is running. Workaround: Ignore the redundant database in the system. General issues Limitations Users are not blocked from certain operations while a probe is running While a probe is running, a user can edit and delete a host or database. [4693] Workaround: Do not delete or edit the host or database while running a probe. When you leave a browser open on the Dashboard, memory consumption continues to rise Workaround: Close the browser and restart Tomcat on the server. [4071] You cannot manually add an existing database to the system When you try to manually add a database that already exists, it is not added to the system. [4778] When this issue occurs, no warning is issued. Oracle database discovery To discover Oracle databases, you should start the Oracle process or the /etc/oratab or /var/opt/oracle/oratab file should be present. Some Hitachi Data Systems IDs are displayed in an inappropriate format HDS LDEV IDs are displayed in Hexadecimal format.

17 Veritas CommandCentral Disaster Recovery Advisor Release Notes Getting help 17 Getting help If you have a current maintenance agreement, you may access Technical Support information here: Customer service information is available here: Note: If you forget or lose the Administrator password, contact Technical Support.

18 18 Veritas CommandCentral Disaster Recovery Advisor Release Notes Getting help