CA ARCserve® Central Virtual Standby r16.5 Release Notes

1.0 Welcome

Welcome to the CA ARCserve Central Virtual Standby Release Notes file. This document contains the following information relating to use of CA ARCserve Central Virtual Standby:

• System requirements, operating system support, application recovery support, and other information you may need to know prior to installation of this product.
• A list of known issues and limitations that you should be aware of before you use this product.

Note: For information about system requirements, supported operating systems, known issues, and so on for CA ARCserve D2D, see the CA ARCserve D2D Release Notes.

2.0 New Features

This Release Summary describes new features, functional and usability enhancements, and dropped support included with CA ARCserve Central Virtual Standby r16.5.

• Supports replication of Windows Server 2012 and Windows 8 servers.
• Supports replication of Catalog less CA ARCserve D2D sessions.
• Hyper-V 3.0 is supported.
• vSphere 5.1 is supported.
• Remote Virtual Standby

  The ability to leverage and integrate the capabilities already available with CA ARCserve Replication to move CA ARCserve D2D recovery points to offsite locations and then enabling CA ARCserve Central Virtual Standby to convert those replicated recovery points and to automatically register them with either Microsoft Hyper-V, VMware vCenter, or ESXi.

3.0 System Information

The following sections provide information about the minimum system requirements for CA ARCserve Central Virtual Standby.

3.1 System Requirements

The minimum system requirements for CA ARCserve Central Virtual Standby are as follows:

• CPU--1 GHz or higher processor is recommended
• RAM--1 GB or more is recommended

  Note: To perform virtual to physical recoveries (V2P), at least 1 GB or more RAM is required on the computer you are recovering.

• Disk Space--900 MB or more is recommended

Other Hardware:

• CD/DVD ROM Drive--required only when installed from a CD/DVD
• SXGA Monitor--XGA (1280 X 1024) or higher-resolution video adapter and monitor

3.2 Supported Operating Systems

You can install CA ARCserve Central Virtual Standby on computers running the following operating systems:

• Windows Server 2008 R2 (x64)
• Windows Server 2008 R2 (x64) SP1
• Windows Server 2012 (x64)
• Windows Server 2012 R2 (x64)

Note: For a complete list of the operating systems supported for the Virtual Standby Monitor Server, see CA ARCserve D2D Compatibility Matrix on the CA Support website.

3.3 Supported Hypervisors

You can deploy CA ARCserve Central Virtual Standby with the following hypervisors:

• Microsoft Hyper-V:
  • Windows Server 2008 SP2 Hyper-V
  • Windows Server 2008 R2 Hyper-V
  • Windows Server 2008 R2 SP1 Hyper-V
  • Windows Hyper-V Server 2008 SP2
  • Windows Hyper-V Server 2008 R2
  • Windows Hyper-V Server 2008 R2 SP1
  • Windows Hyper-V Server 2012
  • Windows Server 2012 Hyper-V
• VMware ESX Server:
  • ESX/ESXi Server 4.0 Update 4
  • ESX/ESXi Server 4.1 Update 3
  • ESXi Server 5.0 Update 1, 5.0 Update 2
  • ESXi Server 5.1
• VMware vCenter Server:
  • vCenter Server 4.0 Update 4
  • vCenter Server 4.1 Update 3
  • vCenter Server 5.0 Update 1, 5.0 Update 2
  • vCenter Server 5.1
• VMware vSphere Server:
  • vSphere 5.5, 5.5 Update 1

3.4 Supported Operating Systems for CA ARCserve D2D Servers

For a complete list of the operating systems that are currently supported for CA ARCserve D2D servers, see the Compatibility Matrix on the CA Support website.

To access the CA ARCserve D2D Compatibility Matrix, click the following link to open the CA ARCserve D2D Support website, then click the Supported Platforms link under the "Benefits to your business" section.

http://www.arcserve.com/us/Products/CA-ARCserve-D2D.aspx

3.5 Minimum Software Requirements

The minimum software requirements for CA ARCserve Central Virtual Standby servers are as follows:

• Internet Browser: CA ARCserve Central Virtual Standby supports the following browsers:
  • Internet Explorer 8.0 or later
  • Mozilla Firefox 3.5.3 or later
  • Google Chrome 3.0.195.27 or later
• Adobe Flash Player: CA ARCserve Central Virtual Standby requires Adobe Flash Player version 10.2.152.26 or later

3.6 Application Recovery Support

For a complete list of all supported application recovery systems, see the CA ARCserve D2D r16.5 Compatibility Matrix.

3.7 Supported Disks

Different types of disks are supported for the CA ARCserve Central Virtual Standby backup source. The following table lists the types of disks that are supported for each function.

4.0 Known Issues

The following list provides information about issues known to exist in this release of CA ARCserve Central Virtual Standby.

• When powering on virtual machines from virtual machines or physical computers that contain multiple disks from computers running Windows 2008, Windows 2008 R2, Windows 7, Windows 8, or Windows Server 2012, all of the disks start in an offline status when powered on. This behavior occurs because SAN policies were introduced to Windows 2008 and later operating systems. The operating system protects shared disks that are accessed by more than one server. The first time the server detects the disk, Windows places the disk in an offline state. After the disk is placed in an online state, the disk remains in an online state.

  Another cause for this behavior relates powering on virtual machines that contain "read only" volumes. To correct this condition, place the volumes on the disk in a writable state.

• The application does not support importing vCenter servers using VMware Linked mode. To protect all vCenter server instances in Linked Mode groups, add each vCenter server instance individually.
• The application does not support configuring Windows Server 2008 SP1 systems as Hyper-V servers.
• The application does not support converting recovery points to Hyper-V format when the system volume or the boot volume on the source computer resides on dynamic disks.
• The application does not support creating policies that let you define the quantity of dynamic RAM used by the virtual machines that you are protecting on Windows 2008 R2 SP1 and windows 2012 Hyper-V Server systems.
• The application does not support protecting source servers running Windows XP that are configured using SCSI disks. The application cannot power on the recovery point snapshots and retrieve all of the SCSI disks configured on the source server.
• When you import nodes from a file, the Import Nodes from a File dialog displays C:\fakepath\[set the File Name variable] instead of the real location of the file. The real location is not displayed due to HTML 5 (security) standards. This behavior occurs on Chrome, Internet Explorer 8, and Internet Explorer 9 browsers.

  To display the real location of the file on Internet Explorer 8 and Internet Explorer 9 browsers, open Internet Options, click Security, specify a Zone, click Custom Level, scroll to the Miscellaneous section, and enable Include local directory path when uploading files to a server. Chrome does not contain a mechanism that lets you view the real location of the file.

• When you sort the View Logs list by the name of the Module, the application sorts the list based on a predetermined sort order for the specific language.
• When you try to deploy CA ARCserve D2D to a remote node from the CA ARCserve D2D Home page, a message may appear that indicates that the user name, password, or both specified for the target node is not correct. This problem occurs only when you log in to CA ARCserve D2D from the CA ARCserve Central Virtual Standby Node screen.

  Solution: Open a browser window and log in directly to the CA ARCserve D2D node using the following URL:

  http://<hostname>:<port>.

  From the new browser window, you can deploy CA ARCserve D2D to the target node without encountering the error message.

• CA ARCserve Central Virtual Standby does not support performing V2P recoveries from the current state for the nodes that were imported from CA ARCserve Central Host-Based VM Backup in a powered on state. Instead you can use any snapshot other than the current state.
• CA ARCserve Central Virtual Standby does not support performing V2P recoveries on nodes that were imported from CA ARCserve Central Host-Based VM Backup in a powered off state. To perform a full VM recovery, submit a Recover VM job using Host-Based VM Backup,
• When you perform a V2P recovery using the current snapshot, a message may appear that indicates the following:

  Failed to get Recovery Point information.

  This behavior occurs when you perform a V2P recovery using the latest snapshot and a conversion job for the node did not complete after the Virtual Standby policy was redeployed to the node.

  Solution:

  1. Submit a CA ARCserve D2D backup job to capture the current state of the node. Then perform a Bare Metal Recovery of the node.
  2. Power off the Virtual Standby virtual machine and then submit a Virtual Standby conversion job to create a current recovery point snapshot for the node.
• The V2P user interface may not display the latest snapshot. This behavior occurs when you perform a V2P recovery after you complete a V2P recovery from the latest snapshot.

  Solution: Perform the V2P recovery using CA ARCserve D2D Bare Metal Recovery.

• When you deploy policies to virtual machines that use Unified Extensible Firmware Interface (UEFI), the policy deployment process can fail. This behavior occurs due to a VDDK API limitation, which prevents the mounting of GPT volumes.
• If you are using Google Chrome as your browser and you click a link from any of the Support and Community Access dialogs and no link opens, perform the following tasks to enable the link:
  1. Verify if there is a pop-up blocked icon displayed in the URL section.
  2. Click the icon and select the "Always allow pop-ups from <YOURSERVERNAME>" option.
  3. Restart Google Chrome. The links from CA ARCserve D2D should open successfully.
  4. If the data is still not shown in the correct format, check if RSS extension for the Google Chrome browser is installed or not.
  5. If not installed, download and install the RSS extension for the Google Chrome browser and reopen the links.
• When you want to use the original computer after it has been recovered instead of the virtual standby machine, it is required to manually redirect the DNS back to the original computer.

  Follow these steps:

  1. Find the DNS redirection utility update_dns.exe in %D2D%\bin\DNSTOOLS
  2. Run the following command line:

     update_dns.exe -dns <IP of DNS server> -hostname < Full Qualified Domain Name of the original machine> -hostip <IP of the original machine> -username <administrative user name of DNS server> -password <password of the administrative user name of DNS server>

     Example: update_dns.exe -dns 192.168.2.1 -hostname master.rha.com -hostip 192.168.2.12 -username tester -password test

  The DNS is redirected back to the original computer.

• If you have the combination of Microsoft SQL Server 2012 SP1 (64-bit) and Microsoft SQL Management Studio, uninstall Microsoft SQL Management Studio before installing CA ARCserve Central Virtual Standby. For more information, see Article 770630 on the Microsoft website.
• The integration of CA ARCserve Replication and High Availability and Remote Virtual Standby is not supported under the following conditions:
  • The backup destination is on a network or a NAS device.
  • The RHA destination is a network share or a NAS device.

  NAS devices are not supported due to the following reasons:

  • RHA data must reside on a local volume to monitor the changes on the backup destination, and to perform the replication.
  • Remote virtual standby data must reside on a local volume to take a VSS snapshot to ensure that consistent data is being converted.

  As an alternative solution, you can perform one of the following options if you want to use a NAS device:

  • When a NAS device is used as the backup destination; create iSCSI LUNs (numbered disk drives) or VHD files on the device, mount iSCSI LUNs or VHD files on the RHA master, and then perform the replication from the iSCSI LUNs or VHD files.
  • When a NAS device is used as the replica destination; create iSCSI LUNs or VHD files on the device, mount iSCSI LUNs or VHD files on the replica destination, and then perform the replication to the iSCSI LUNs or VHD files.

  Note: Windows Server 2012 or later is required to use these alternative solutions.

• When the backup source machine (where D2D is installed) contains native 4KB sector disks and the D2D backup job backed up the volumes on the 4KB sector disks, the standby virtual machine that converted the D2D backup sessions cannot detect the partitions and volumes of the corresponding 4KB sector disks. You can expect this behavior when the source disks contain 4KB sectors and the standby virtual machine supports 512B sector disks. After conversion, the guest operating system on the standby virtual machine fails to locate the disk metadata due to the sector size changes.

  Note: This limitation applies to only Virtual Standby jobs running on Hyper-V servers.

5.0 Limitations

The following list provides limitations that are known to exist in this release of CA ARCserve Central Virtual Standby.

• In VMware ESX Server environments that are configured in a storage area network (SAN), the application copies only the first, full backup session to the ESX Server system using the SAN. For all subsequent full and incremental backups, the application copies the converted backup sessions using the LAN. The application behaves in this manner due to a VMware limitation. For more information, see the VMware website.
• Due to a VMware limitation, CA ARCserve Central Virtual Standby cannot create virtual machines on ESXi Server systems using a free license. To create virtual machines, a purchased license is required.
• Due to a known VMware limitation, errors in the Activity Log appear in English when the Location is set to a non-English locale.
• Due to a VDDK API limitation, CA ARCserve Central Virtual Standby cannot support the UEFI (Unified Extensible Firmware Interface) system, therefore when you deploy a policy to a UEFI system, deployment fails.
• Due to a VMware limitation, CA ARCserve Central Virtual Standby does not support virtual standby of Windows 8/Windows Server 2012 to ESX versions older than 5.1.
• When CA ARCserve Central Virtual Standby converts to a Hyper-V 3.0 server, the only format that is supported is VHD. VHDX format is not supported.
• A data corruption problem may occur when you have machines with Intel 82574L or E1000E vNIC network adapters on your CA ARCserve Central Virtual Standby environment. This is due to a data corruption issue of this model of network adapters when using its TCP Segmentation Offload (TSO) feature.

  To avoid this problem, perform one of the following actions:

  • When creating a virtual machine in VMware, select different network adapters instead of E1000E.
  • For existing virtual machines that contain the E1000E vNIC network adapter; delete it, add a new adapter and connect it to the virtual network.

    Be aware of the following conditions:

    • Ensure that the CA ARCserve Central Virtual Standby conversion environment does not contain the Intel 82574L network adapter or the E1000E vNIC in its entirety.
    • Verify that the following Virtual Standby components do not contain the Intel 82574L or the E1000E vNIC network adapters:

      - Virtual Standby Server

      - Converter

      - Hyper-V Server (if used for the virtual standby destination)

      - Replica Server (if used for the CA ARCserve Replication and High Availability destination when converting replicated sessions)

    • If the backup destination is a share, then the computer hosting the share should not contain the Intel 82574L or the E1000E vNIC network adapters.
  • If you must use the E1000E vNIC or if you are using a physical computer with Intel 82574L NIC installed, it is recommended that you disable the TSO feature.

  For more information about this problem, see "Errata 17 - Tx Data Corruption When Using TCP Segmentation Offload" in the following Intel document:

  Intel 82574 Family Gigabit Ethernet Controller Specification Update

6.0 Language Certifications

For CA ARCserve Central Virtual Standby, this release has been translated into the following languages, in addition to the English release:

• Brazilian-Portuguese
• French
• German
• Japanese
• Simplified Chinese
• Spanish
• Traditional Chinese

If you run this product on a language environment not included in the list, you may experience problems.

7.0 Acknowledgements

The following license agreements are available in the \Bookshelf_Files\TPSA folder in the CA Bookshelf:

• Eclipse Public License v.1.0
  • Eclipse Equinox AspectJ r.1.6.9
• Apache Software License v.2.0
  • AWS SDK for Java 1.0
  • Axis 1.4
  • Derby 10.6.2.1
  • GWT 2.4 (Google Web Toolkit 2.4)
  • Log4j 1.2.15
  • Quartz 1.6.5
  • Tomcat 7.0.29
• bind 9.6.1-P1
• jaxws 2.2.7
• VMware Virtual Disk Development Kit 5.0 Update 1
• Oracle (formerly Sun) JRE 1.7.0 09

8.0 Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

• Online and telephone contact information for technical assistance and customer services
• Information about user communities and forums
• Product and documentation downloads
• CA Support policies and guidelines
• Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

8.1 CA ARCserve Central Applications Support Links

Support Links for CA ARCserve Central Applications:

CA Support Online offers a rich set of resources for resolving your technical issues and provides easy access to important product information. With CA Support, you have easy access to trusted advice that is always available. The following links let you access the various CA Support sites that are available:

• Understanding your Support--The following link provides information about maintenance programs and support offerings, including terms and conditions, claims, service-level objectives (SLO), and service hours.

  http://www.arcserve.com/us/support/maintenance-program.aspx

• Registering for Support--The following link takes you to the CA Support Online registration form which is used to activate your product support.

  https://support.ca.com/prodinfo/supportregistration

• Accessing Technical Support--The following link takes you to the One-Stop Product Support page for CA ARCserve Central Applications.

  https://support.ca.com/prodinfo/arccentapps

Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.