CA ARCserve® Central Applications r16.5 Release Notes

1.0 Welcome

Welcome to the CA ARCserve Central Applications Release Notes file. This document contains information about system requirements, supported platforms, known issues, and other information you may need to know before installing the following applications:

• CA ARCserve Central Host-Based VM Backup
• CA ARCserve Central Protection Manager
• CA ARCserve Central Reporting
• CA ARCserve Central Virtual Standby

1.1 System Requirements the CA ARCserve Central Applications Suite

The minimum system requirements for the CA ARCserve Central Applications suite are as follows:

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

  Note: For more information about the disk space that is required for each of the CA ARCserve Central Applications, see System Requirements in the Release Notes file for the application.

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

Operating Systems:

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

2.0 CA ARCserve Central Host-Based VM Backup Release Notes

2.1 Welcome

Welcome to the CA ARCserve Central Host-Based VM Backup Release Notes file. This document contains the following information relating to use of CA ARCserve Central Host-Based VM Backup:

• 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.2 New Features

This Release Summary describes new features, functional and usability enhancements, and dropped support included with CA ARCserve Central Host-Based VM Backup r16.5.

r16.5 Update 1:

• CA ARCserve Central Host-Based VM Backup is now enhanced to protect non-Windows virtual machines that run on VMware ESX Servers. You can perform full and incremental backups, and can recover VM operations. However, you cannot perform file or application level restore from non-Windows virtual machine backup sessions.

r16.5:

• The application supports the following Microsoft Windows 8 and Microsoft Windows Server 2012 feature:
  • Storage Spaces: Storage spaces is a virtualization layout that can group a quantity of physical disks and create virtual disks on top of the physical disks. With this release, CA ARCserve Central Host-Based VM Backup does not support application level recovery on Windows Server 2012 and Windows 8 systems where storage spaces are enabled, however the entire virtual machine can be recovered.

    Note: Creating storage spaces and virtual disks in BMR is not supported.

• Catalog-less Backup:

  File system catalog generation is a time consuming task. With this feature you can choose not to generate a catalog file with every backup, and still be able to do a file level restore. This reduces the backup time window.

• Microsoft Exchange 2013 Backup/Restore (VSS) is supported.
• UEFI Support:

  You can perform BMR from a backup taken on a UEFI machine to a BIOS machine and from a BIOS machine to a UEFI machine.

• vSphere 5.1 is supported.

2.3 System Information

The following sections provide information about the minimum system requirements for CA ARCserve Central Host-Based VM Backup.

2.3.1 System Requirements

The minimum system requirements for CA ARCserve Central Host-Based VM Backup are as follows:

• CPU--1 GHz or higher processor is recommended
• RAM--1 GB or more is recommended
• 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

2.3.2 Supported Operating Systems

You can install CA ARCserve Central Host-Based VM Backup on computers running the following operating systems:

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

2.3.3 Supported Hypervisors

You can deploy CA ARCserve Central Host-Based VM Backup with the following hypervisors:

• 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 Server 5.5, 5.5 Update 1

2.3.4 Supported Operating Systems for CA ARCserve D2D Proxy Servers

CA ARCserve Central Host-Based VM Backup requires the following operating systems on backup proxy servers:

• Windows Server 2008 R2 (x64) SP1
• Windows Server 2008 R2 (x64)
• Windows Server 2008 (x86 and x64)
• Windows Server 2003 (x86 and x64)

Note: Due to a VMware limitation, Windows Server 2012 is not supported as the backup proxy server, however it is supported as a guest operating system that can be protected using CA ARCserve Central Host-Based VM Backup. For more information, see the Limitations section.

2.3.5 Supported Operating Systems for Protected Virtual Machines

CA ARCserve Central Host-Based VM Backup lets you protect virtual machines running the following operating systems:

• Windows Server 2012 (x64)
• Windows Server 2012 R2 (x64)
• Windows Server 2008 R2 (x64)
• Windows Server 2008 R2 Core (x64)
• Windows Server 2008 (x86/x64)
• Windows Server 2008 Core (x86/x64)
• Windows Server 2003 R2 (x86/x64)
• Windows Server 2003 (x86/x64)
• Windows 8 (x86/x64)
• Windows 7 (x86/x64)
• Windows Vista (x86/x64)
• Windows XP (x86/x64)

Note: CA ARCserve Central Host-Based VM Backup supports all editions and service packs for the above-described operating systems, which also includes support for all versions of Windows Small Business Server (SBS).

2.3.6 Supported Operating Systems for Application Level Restores

CA ARCserve Central Host-Based VM Backup can restore data at application level granularity on computers running all operating systems that are supported by CA ARCserve D2D excluding the following operating systems:

• Windows XP x86 and x64
• Windows Vista x86 and x64
• Windows 7 x86 and x64

Note: CA ARCserve Central Host-Based VM Backup behaves in this manner because VMware does not support creating application level meta data on the excluded operating systems. (For more information, see Working with Microsoft Shadow Copy in the VMware Virtual Disk API Programming Guide.) However, CA ARCserve Central Host-Based VM Backup can restore data on the excluded operating systems at file system and folder level granularity.

For a complete list of the operating systems supported by CA ARCserve D2D, see the CA ARCserve D2D Release Notes file.

2.3.7 Minimum Software Requirements

The minimum software requirements for CA ARCserve Central Host-Based VM Backup servers are as follows:

• Internet Browser: CA ARCserve Central Host-Based VM Backup 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 Host-Based VM Backup requires Adobe Flash Player version 10.2.152.26 or later
• CA ARCserve D2D Proxy Server: The CA ARCserve D2D proxy server requires the following applications:
  • CA ARCserve D2D r16.5
  • VMware VIX API 1.11 through 1.11.6

    Note: For VIX API 1.11, it is required that all virtual machines are updated with the most recent VMware tools. For VIX API 1.11.6, you can download it from the Download page on the VMware website: https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/4_0|PLAYER-405|product_downloads

2.3.8 Application Recovery Support

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

2.3.9 Supported Disks

Different types of disks are supported for CA ARCserve Central Host-Based VM Backup backup source and destination disks. The following table matrix lists the types of disks that are supported for each function.

*Note: FAT/FAT32 cannot hold a single file larger than 4 GB. CA ARCserve Central Host-Based VM Backup creates CA ARCserve D2D files and if the file is larger than 4 GB after compression, the backup fails.

2.4 Known Issues

The following list provides information about issues known to exist in this release of CA ARCserve Central Host-Based VM Backup.

• The following issues relate to changed block tracking (CBT):
  • Backups of virtual machines can fail due to CBT requires a reset after the Preflight Check (PFC) utility reported that CBT is enabled on the virtual machine. This behavior can occur when ESX Server systems restart after the PFC utility completed the analysis of the virtual machine. The process of restarting ESX Server system requires a reset to CBT. There are no corrective actions required to remedy this behavior. After the job fails due to CBT not being enabled, Host-Based VM Backup enables CBT on the virtual machine. The next time the job runs, it should not fail due to CBT not being enabled, unless the ESX Server system was restarted again after the last backup job failed.

    Note: This behavior can also occur when ESX Server systems fail or reboot.

  • Backup jobs fail when the CBT feature is disabled and you have manually created snapshots on the virtual machine to back up. CA ARCserve Central Host-Based VM Backup automatically enables CBT on the virtual machine and you can then create the snapshot again.
• During a Recover VM job for Host-based VM backup, the vDS network configuration is skipped. After VM recovery, the vDS network configuration can be added manually.
• While recovering a VM to a specific ESX Server, if the VM version is not supported by the target ESX Server, the recover VM operation will fail. (For example, if you back up a VM with VM Version 8.0 from ESX server 5.0 and then try to recover to ESX server 4.0/4.1, the recover VM operation will fail because the VM Version 8.0 is not supported by ESX server 4.0/4.1).
• The application does not support protecting virtual machine data that resides on FAT/FAT32 file systems, ReFS volumes, and RAID 5 volumes. The backup jobs skip such volumes when performed on FAT and FAT32 files systems and RAID 5 volumes.
• Due to a known VMware issue, occasionally a snapshot named Consolidate Helper- 0 remains in the snapshot manager after the backup completes. This behavior occurs when you back up virtual machines that contain VMDK files that reside in different directories or LUNs and have identical file names. To delete the erroneous snapshots, turn off the virtual machines.
• The application does not support importing vCenter servers using VMware Linked mode. To protect all vCenter server instances in your Linked Mode group, add each vCenter server instance individually.
• Recovery points do not display immediately on the Browse Recovery Points dialog when you specify a shared folder as the destination for CA ARCserve D2D backups. To correct this problem, do the following:
  • After the Browse Recovery Points dialog opens, wait 30 seconds and click the dates on the calendar. This approach allows the dialog a sufficient amount of time to refresh and display the recovery points.
  • Reenter the credentials required to access the backup destination. To reenter the credentials, click the arrow next to the Select Backup Location field on the Browse Recovery Points dialog.
• The application supports protecting only Windows-based virtual machines running on VMware Hardware version 7 or later. When you import virtual machines from ESX Server and vCenter Server systems, the application skips UNIX-based virtual machines, Linux-based virtual machines, and guest operating systems that are not installed on virtual machines running on VMware Hardware version 7 or later.
• If you are running VMware High Availability (HA) or VMware Distributed Resource Scheduler (DRS), import nodes using a vCenter Server (not ESX) to avoid discovery and backup issues.
• Virtual machine names that contain JIS2004 characters appear in the VI Client as ??????. This behavior occurs only after you use CA ARCserve Central Host-Based VM Backup to recover the virtual machines. To correct this problem, rename the virtual machine using JIS2004 characters in the VI Client after the Recover VM operation is complete.

  To prevent this problem from occurring, name the virtual machine that you want to recover using standard (non-JIS2004) characters in the Recover VM screens while submitting the recovery job. Then, rename the virtual machine using JIS2004 characters in the VI Client after the Recover VM operation is complete.

• When  Catalog generation process failed for a successful HBBU backup check if the activity log show the below message
• When Host-Based VM Backup virtual machine backup jobs complete successfully and the catalog generation process fails, the following message appears in the Activity Log:

  Could not get volume information from virtual machine Guest OS.

  This problem can affect backup jobs that were successful previously. When this problem occurs, CA ARCserve Central Host-Based VM Backup generates the backup session but cannot generate the catalog files that are required to support the backup sessions. The failed catalog condition prevents you from performing file level restores because the catalog does not contain the recovery points that are required for file level restores.

  To correct this behavior, the following corrective actions may solve the problem:

  1. Examine the status of VMware Tools on the PFC dialog. When the status indicates Out of Date, install the latest version of VMware Tools and then resubmit the backup.
  2. When the guest operating system is Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, provide the built-in or domain administrator credentials to log in to the virtual machine guest operating system.

     Note: Administrator credentials are required for virtual machine guest operating systems to generate catalog and perform granular restore.

• When you recover virtual machines to the original location, and specify the Overwrite existing VM option, Host-Based VM Backup changes the location of the virtual disk when it detects the presence of the original virtual machine. This behavior was designed to help ensure that you do not lose data during the Recover VM process.
• The application cannot send backup failed related alert messages when the CA ARCserve D2D virtual machine proxy system is down or the CA ARCserve D2D service on the proxy is not running.
• CA ARCserve D2D licensing error email messages occur under the following scenario:
  • CA ARCserve Central Host-Based VM Backup was uninstalled and then reinstalled.
  • The CA ARCserve D2D nodes that you were protecting before you uninstalled CA ARCserve Central Host-Based VM Backup were added using the Node screen.
  • The policy was redeployed.

  If you receive email messages that indicate that licensing errors occurred on the nodes, you can ignore the messages.

• 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 Host-Based VM Backup 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 Host-Based VM Backup cannot back up USB volumes. If there are any USB volumes included in the backup source, CA ARCserve Central Host-Based VM Backup skips the USB volumes.
• The following behavior applies to backing up data that resides on NFS data stores:
  • When backing up data that resides on NFS data stores using changed block tracking, and you do not use data compression, the size of the first full backup will be at least the same size as the source disk. However, subsequent incremental backups will contain only the changed blocks of data. As a result, the overall size of the incremental backups will be smaller as compared with the first full backup.
  • An alternative approach to backing up virtual machines in NFS data stores is to install CA ARCserve D2D inside the guest operating system and back up the virtual machine in the same manner as you would back up a physical machine.
• If you have a vCenter server that is configured with a custom HTTPS port and then run a backup job using the default HTTP port, the backup job fails.

  To resolve this issue, use the HTTPS port for the backup job.

• To restore data to virtual machines that are implemented using Unified Extensible Firmware Interface (UEFI), ESXi Server 5.0 must be the hypervisor that is installed in the virtual environment. When ESXi Server 5.0 is not installed in the virtual environment, the recovery fails and error messages can appear.
• Backup jobs fail when all of the following conditions are met:
• Microsoft Windows Server 2008 and later contains a User Profile Service that unloads specific registry keys when users log out from the computer.
  • Microsoft SQL Server or Microsoft Exchange is installed on the server.
  • CA ARCserve D2D backup is user generated.
  • You log out from the server after the backup starts, but before it completes.

  To correct this behavior, use the following steps:

  1. Log in to the CA ARCserve Central Host-Based VM Backup server using the Administrator account or an account that is a member of the Administrators group.
  2. Type gpedit.msc in the Run dialog to start the Local Group Policy Editor.
  3. From the Local Group Policy Editor, expand Computer Configuration, Administrative Templates, System, and User Profiles.
  4. From the User Profile directory, double-click Do not forcefully unload the user registry at user logoff, to open the dialog.

     Click Enabled and then click OK.

     Note: The value DisableForceUnload is added to the registry.

  5. Type gpudate.exe in the Run dialog from the CA ARCserve Central Host-Based VM Backup server.

     Ensure that the security policy settings are updated.

• When you schedule an Incremental backup for a virtual machine; and then perform a Storage vMotion, the Incremental backup converts to a Verify backup.
• When you configure backups to always run using the SAN transport mode; backups fail when the SAN is not available. The activity log displays the following error message:

  Unable to open VMDK file %1!s!. VMware reported the following error: You do not have access rights to the file. For more information, see the debug log AFBackend.Log. If necessary, contact technical support.

  To correct this behavior, apply the SAN transport mode to the registry only if the SAN is available.

• When you submit a VMware based virtual machine backup and the backup fails, the following error message appears:

  Could not take snapshot of the virtual machine. ESX Server/vCenter Server reported the following error: Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

  This is a known issue with VMware and is working to find a resolution. In the interim, we have listed some workarounds in our troubleshooting topic, Backups Fail with Snapshot Creation Errors in the CA ARCserve Central Host-Based VM Backup user guide.

• 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 submit or schedule an Incremental backup job for a virtual machine on an ESX 5.0 server; a Verify backup job runs instead. Follow these steps to correct this behavior:
  1. Right-click the virtual machine that is converting Incremental backups to Verify backups.
  2. Select Snapshot and then select the Consolidate option.
  3. When the consolidating process completes, resubmit or reschedule the Incremental backup job and confirm that the backups are not being converted to Verify backups.
• The process of generating catalogs may stop responding when the volume extent is spread across a disk.

  Symptom:

  The volumes extent cannot have more than one logical extent across a disk. This behavior occurs on striped volumes and does not occur on simple, mirrored, and spanned volumes.

  Solution:

  To prevent this behavior from occurring, the volumes extent should be contiguous on a disk.

• Intermittent failures in backup, restore, merge, and other operations are observed if a network share on a "HP StorageWorks D2D4106" device is used as the backup destination for CA ARCserve Central Host-Based VM Backup. It is not recommended to use this device for the backup destination.
• For uncompressed and unencrypted backups, it may not be possible to resume the merge after pausing it. CA Technologies is in the process of resolving this issue.

r16.5

• When you configure storage space on a VMware or Hyper-V virtual machine or when the virtual machine contains applications with data on SMB shares; backing up the virtual machine fails with a snapshot creation error.
• To mount deduplication NTFS volumes, verify that the volume is mounted on a Windows Server 2012 system and the deduplication feature is installed.
• Host-based VM backup jobs have been known to stop responding. When you encounter this condition, configure the application to use the NBD transport mode for backups. For more information, see Define a Transport Mode for Backups in the CA ARCserve Central Host-Based VM Backup USer Guide.
• CA ARCserve Central Host-Based VM Backup does not support protecting virtual machines that are configured as SE (Space Efficient) disks. Volumes that are configured in this manner will be skipped during backup operations.
• When a virtual machine contains SCSI and IDE disks or SCSI disks on different controllers, CA ARCserve Central Host-Based VM Backup fails.
• 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 Host-Based VM Backup. For more information, see Article 770630 on the Microsoft website.
• When storage space volumes reside on virtual disks, the application cannot back up the data that resides on the virtual disks, and the volumes do not appear (listed) on the Browse Recovery Points screen and the Copy Recovery Point screen. You can expect this behavior because volumes that reside on virtual disks that the storage pool created are not listed and protected by CA ARCserve Central Host-Based VM Backup. In addition, the file level restore and the mounting drivers for such volumes are not supported.
• CA ARCserve Central Host-Based VM Backup Catalog job fails intermittently on virtual machines running Windows Server 2003 x64 SP2 Enterprise Edition with the error message "Failed to generate catalog".

  Note: We are working with VMware to resolve this issue. If you encounter this issue and need assistance, contact CA Support.

r16.5 Update 1

• When you perform Incremental backup jobs for VMware virtual machines, the size of the Incremental backup jobs is larger than expected. This is a known VMware issue where it involves Changed Block Tracking (CBT). To correct this behavior, set the following registry:

  [HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve D2D\AFBackupDll\<VM instance UUID>]

  "ResetCBT"=dword:00000001

  Example:

  [HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve D2D\AFBackupDll\502d3c43-e3c9-9919-78f9-89082ca5e1cc]

  "ResetCBT"=dword:00000001

  Note: After the registry value is set, the next Incremental backup job converts to a Verify backup job and then the subsequent Incremental backup jobs continue to run with the appropriate size.

• When you power on a recovered virtual machine (VM) that contains a virtual flash read cache, the virtual machine fails and displays the following error message, "The available virtual flash resource ('0' bytes) is not sufficient for the requested operation". This error occurs when the target (ESX) host does not have the virtual flash resource or when the target host virtual flash resource is less than the size of the VM virtual flash read cache.

  To resolve this issue, set the virtual flash read cache to 0 in the recovered VM settings and then power on the VM.

• The VMware ESXi server stops working when you use E1000E/E1000 vNIC Adapters on virtual machines that run on VMware ESXi. As an alternative solution, refer to the following VMware Knowledge Base article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059053

r16.5 Update 2

• With version VDDK 5.5 or later, the Hot Add Transport mode will not work with ESXi level but will work with VC level. When Hot Add Transport mode is selected, the mode is changed back to NBD mode. This behavior occurs in CA ARCserve Central Host-Based VM Backup and CA ARCserve Central Virtual Standby.

2.5 Limitations

The following list provides limitations that are known to exist in this release of CA ARCserve Central Host-Based VM Backup.

• Due to a known VMware limitation, Host-Based Backup does not support application level restores from backup sessions of Windows 2008 or later or virtual machines running on ESX 4.0 or earlier. The application supports file system backups, file system restores, recover virtual machines, and bare metal recovery operations in this type of environment.
• Due to a known VMware limitation, CA ARCserve Central Host-Based VM Backup cannot protect ESXi virtual machines using a free license. To back up these virtual machines, apply a purchased license.
• Due to a known VMware VDDK licensing limitation, the following jobs should not be performed using custom ports (HTTP, HTTPS):
  • The message, "Cannot open VMDK file" is displayed when you try to back up a virtual machine using a VMware vCenter or ESX server custom HTTP port.
  • The message, "Failed to recover virtual disks" is displayed when you try to recover a virtual machine using a VMware vCenter or ESX Server customized HTTP port. This message is also displayed when you try to recover a virtual machine using a VMware ESX Server custom HTTPS port.
• Due to a known VMware limitation, errors in the Activity Log appear in English when the Location is set to a non-English locale.
• CA ARCserve Central Host-Based VM Backup now supports backing up data using Unified Extensible Firmware Interface (UEFI) with ESXi Server 5.0 installed on the virtual machine. If ESXi Server 5.0 is not installed on the virtual environment, the following error message appears:

  The application cannot recover this virtual machine because ESXi Server 5.0 is not installed on the virtual environment.

• Due to a known VMware limitation, there are times where VMware Storage vMotion cannot migrate a virtual machine which is being protected by CA ARCserve Central Host-Based VM Backup. To correct this behavior, see the following Knowledge Base article on the VMware website: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008957
• Due to a known VMware limitation, when you protect a SQL Server running on a Windows Server 2012 virtual machine (VM) hosted on a VMware server with data stored on another Windows Server 2012 computer, it is required to install Client Agent or CA ARCserve D2D to the VM. CA ARCserve Central Host-Based VM Backup is not recommended as the backup method.
• Due to a known CA ARCserve Central Host-Based VM Backup limitation, the application does not support the following volumes:
  • Catalog generation for both stripped and RAID-5 Volumes.
  • Backup for RAID 5 Volume.

    Note: If the stripped volume contains more than one extent on one disk, then backup is not supported.

• CA ARCserve Central Host-Based VM Backup does not support application level recovery on Windows Server 2012 and Windows 8 systems where storage spaces are enabled, however the entire virtual machine can be recovered.

  Note: CA ARCserve Central Host-Based VM Backup can only protect ESXi virtual machines at the disk level. The application cannot protect the data that resides on the virtual disks that are created by Storage Space at the volume and file levels. The backup job will skip the volumes residing on the virtual disks that are created by Storage Space.

• Due to a known VMware limitation, sparse space efficient (SE) disks are not supported and will be skipped from the backup job. In addition, VMware specifies that the 'seSparse' virtual disk type is intended for internal use only. For more information, see the vSphere Web Services SDK 5.1 Release Notes on the VMware website.

  For information about VMware virtual machines that are configured with space-efficient (SE sparse) disks, see the VMware Knowledge Base article.

• When you manage ESX Server 5.0 and higher with vCenter Server and you try to recover a virtual machine directly to the ESX host, the recovery fails. To resolve this issue, disconnect the ESX server and then resubmit the recovery job to the ESX host.
• Due to a VMware limitation, CA ARCserve Central Host-Based VM Backup does not support Windows Server 2012 virtual machines that have ReFS volumes, NTFS Data Deduplication volumes, or both enabled. However, the application supports virtual machines running on Windows Server 2012 virtual machines that do not have ReFS volumes, NTFS Data Deduplication, or both disabled.

  As an alternative solution in supporting Windows Server 2012 virtual machines that has ReFS volumes, NTFS Data Deduplication volumes, or both enabled, install CA ARCserve D2D inside the virtual machines and perform the backup operations directly from the virtual machines.

  Note: VMware is working to resolve this limitation.

• A data corruption problem may occur when you have machines with Intel 82574L or E1000E vNIC network adapters on your CA ARCserve Central Host-Based VM Backup 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 environment where the CA ARCserve Central Host-Based VM Backup proxy server resides does not contain the Intel 82574L network adapter or the E1000E vNIC in its entirety.
    • 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

• CA ARCserve Central Host-Based VM Backup does not support granular restore for NTFS deduplication volume for the Windows Server 2012 R2 guest operating system.

  This limitation is only applicable to Windows Server 2012 R2 deduplication volumes because VMware has not certified Windows Server 2012 R2 as a proxy with VDDK 5.5. As an alternate solution, install CA ARCserve D2D on to the virtual machines and directly perform the backup operations.

• Due to VMware limitations, HTTP protocol and vSAN beta are not supported.
• In an Exchange Database Availability Group (DAG) environment, CA ARCserve Central Host-Based VM Backup can only truncate logs for the protected Exchange nodes. The following alternatives will result in log truncation on all DAG nodes:
  • Back up all nodes in a DAG.
  • Install the Agent inside the virtual machine on the active nodes by applying the procedure from the following KB article:http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=3154.
  • Use CA ARCserve Backup Exchange Agent.

3.0 CA ARCserve Central Protection Manager Release Notes

3.1 Welcome

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

• System requirements, operating system support, and other information you may need to know prior to installation of this product.
• A list of known issues 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.

3.2 New Features

This Release Summary describes new features, functional, and usability enhancements, and dropped support that is included with CA ARCserve Central Protection Manager r16.5 and Update releases.

r16.5 Update 2:

• In this release, CA ARCserve Central Protection Manager now supports Microsoft SQL Server 2014 as their database.

3.3 System Information

The following sections provide information about the minimum system requirements for CA ARCserve Central Protection Manager.

3.3.1 System Requirements

The minimum system requirements for CA ARCserve Central Protection Manager are as follows:

• CPU--1 GHz or higher processor is recommended
• RAM--1 GB or more is recommended
• Disk Space--3.82 GB 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.3.2 Supported Operating Systems

You can install CA ARCserve Central Protection Manager on computers running the following operating systems:

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

3.3.3 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.3.4 Supported Operating Systems for CA ARCserve Backup Servers

For a complete list of supported operating systems for CA ARCserve Backup servers, see the CA ARCserve Backup Readme on the CA Support website.

3.3.5 Minimum Software Requirements

The minimum software requirements for CA ARCserve Central Protection Manager servers are as follows:

• CA ARCserve Central Protection Manager Database: CA ARCserve Central Protection Manager requires one of the following database applications:
  • Microsoft SQL Server 2012 Web/Standard/Enterprise
  • Microsoft SQL Server 2008 R2 Express Edition
  • Microsoft SQL Server 2008 R2
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2005 SP3
  • Microsoft SQL Server 2005 SP4
  • Microsoft SQL Server 2014
• Internet Browser: CA ARCserve Central Protection Manager 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 Protection Manager requires Adobe Flash Player version 10.2.152.26 or later

3.4 Known Issues

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

• The application does not support importing vCenter servers using VMware Linked mode. To protect all vCenter server instances in your Linked Mode group, add each vCenter server instance individually.
• D2D Deployment fails if CA ARCserve D2D r16 was uninstalled from a node before deploying CA ARCserve D2D to that node. The deployment fails because the previous driver was not removed from the target node. To deploy CA ARCserve D2D to the node, uninstall the driver from the target node by doing the following:
  1. From the Start menu, select Run.
  2. Enter "regedit" and click OK to open the Registry Editor.
  3. Select HKEY_LOCAL_MACHINE from the File menu in the Registry Editor and open the SYSTEM file.
  4. Delete "ARCFlashVolDrv" from "LowerFilters" in the following entries:

     Important! The "LowerFilters" registry key may also contain other Windows driver names. Be sure to delete only the "ARCFlashVolDrv" value from the list. Do not delete the entire registry key or any other driver names from within the key.

     • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{533C5B84-EC70-11D2-9505-00C04F79DEAF}\LowerFilters
     • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}\LowerFilters
  5. Delete the following registry keys:
     • HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\ARCFlashVolDrv
     • HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\eventlog\System\ARCFlashVolDrv
  6. Close the Registry Editor and restart the node.
• After you click the Manage option (located on the upper right corner of the CA ARCserve D2D home page) to manage another CA ARCserve D2D node, you cannot log out of the managed node. You will discover this behavior the next time you log in to CA ARCserve D2D from the CA ARCserve Central Protection Manager Node screen: The CA ARCserve D2D home page for the node that you managed last opens.

  To correct this problem, close all CA ARCserve D2D and CA ARCserve Central Protection Manager windows and then log in to CA ARCserve Central Protection Manager.

• The Copy link on the D2D Deployment License Agreement dialog does not let you copy the CA ARCserve D2D End User License Agreement to the clipboard. You can encounter this problem on Firefox and Chrome browsers. To copy the CA ARCserve D2D End User License Agreement to the clipboard, click in the license content, select all of the text, and then do one of the following:
  • Firefox browsers--From the Edit menu, click Copy.
  • Chrome browsers--From the Customize and Control Google Chrome menu, click Copy.
• When you upgrade CA ARCserve D2D r15 to r16.5 and then perform a full CA ARCserve D2D data synchronization, CA ARCserve D2D omits r15 data and generates r16.5 data for your reports.
• 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.

• The following known issues occur for Global Dashboard (GDB) nodes, branch servers:
  • When you load or refresh the Node screen, the total number of nodes do not include the branch servers.
  • When you apply a GDB node filter, the total number of nodes include all branch servers and the total number of filters do not. (Although, the number of filters may include some but not all branch servers.)

    Note: If you refresh the screen, the number of branch servers is removed from the total number of nodes and the total number of filters.

• 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 Protection Manager 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.

• After you click the Manage option to manage another CA ARCserve D2D node, you cannot log out of the managed node. The Manage Option is located on the upper right corner of the CA ARCserve D2D home page. You will discover this behavior the next time you log in to CA ARCserve D2D from the CA ARCserve Central Protection Manager Node screen: The CA ARCserve D2D home page for the node that you managed last opens.

  To correct this problem, close all CA ARCserve D2D and CA ARCserve Central Protection Manager windows and then log in to CA ARCserve Central Protection Manager.

• To restore data to virtual machines that are implemented using Unified Extensible Firmware Interface (UEFI), ESXi Server 5.0 must be the hypervisor that is installed in the virtual environment. When ESXi Server 5.0 is not installed in the virtual environment, the recovery fails and error messages will appear.
• The Merge Failure alert option is not applied to policies on D2D nodes under the following conditions:
  • The CA ARCserve Central Protection Manager server is running r16.5 and the CA ARCserve D2D nodes are running the r16 GA release, Update 1, Update 2, Update 3, or Update 4.
  • The policy is then created or updated on the Protection Manager server and includes the (new) Merge Failure alert option, and then the D2D nodes are upgraded to r16.5.

  To correct this behavior, update and save the policy on the Protection Manager server. When you save the policy, Protection Manager applies the policy changes to the nodes automatically.

• 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.
• Remote deployment of CA ARCserve D2D r16.5 to a Windows XP system can fail with error: Failed to get installation status feedback from the remote target host.

  Symptom:

  A timeout error or a bad network connection can cause this failure. The XP system shows the CA ARCserve D2D installation is complete but the reboot fails. You cannot reboot the system manually. Therefore, a hard reboot is required. This problem is a known issue with Windows XP.

  Solution:

  Apply the following Microsoft patches before deploying CA ARCserve D2D or install CA ARCserve D2D locally on a Windows XP system:

  • Windows stops responding during Windows XP shut down
  • A Windows XP-based computer stops responding during standby or hibernation operations or when you try to use the Shut Down command
• From the CA ARCserve Central Applications Service Properties dialog, an error message displays when you change the "Log on as" account from the administrators group to an account in a different group.
• Intermittent failures in backup, restore, merge, and other operations are observed if a network share on a "HP StorageWorks D2D4106" device is used as the backup destination for CA ARCserve Central Protection Manager. It is not recommended to use this device for the backup destination.
• For uncompressed and unencrypted backups, it may not be possible to resume the merge after pausing it. CA Technologies is in the process of resolving this issue.
• 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 Protection Manager. For more information, see Article 770630 on the Microsoft website.

3.5 Fixed Issues

The following list identifies the items fixed in the current release of CA ARCserve Central Protection Manager. If you do not see a specific fix listed in this section, contact CA Support for more information.

Export Nodes to CSV Files:

• When you use the Export option to export the node information to a CSV file, the password is now encrypted. Consider the following scenarios when you view the CSV file:

  Note: Originally, the CSV file contained three columns: "Node Name", "User Name", "Password". This fix now includes a fourth column where it contains a True or False status of whether the password was encrypted or not.

  • When you change a password for a particular node; you can also change the password in the file, however it is required that you change the fourth column to False.
  • When you create a new CSV file (not using CA ARCserve Central Protection Manager), the fourth column for all nodes must equal to False.
  • If you export a file from the Update 6 release and import the file to the Update 7 release, then you must add the fourth column to the exporting CSV file with the value of False.

4.0 CA ARCserve Central Reporting Release Notes

4.1 Welcome

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

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

4.2 Features

CA ARCserve Central Reporting includes features, functionalities, and capabilities that let you do the following:

• Collect information and view reports about the performance of CA ARCserve D2D nodes and CA ARCserve Backup servers from a central location. For example:
  • CPU usage
  • Memory usage
  • Disk throughput
  • Network input and output
• View reports in tabular and chart formats in a browser-based, dashboard interface.
• Filter data to view reports about specific servers or groups of protected servers so that you can target report data that is unique to a set of systems with common characteristics.
• Export the collected data for the reports as CSV files for use with spreadsheets. You can also print or send the reports via email.
• Integrate CA ARCserve Central Reporting with CA ARCserve Central Protection Manager, CA ARCserve Central Virtual Standby, and CA ARCserve Central Host-Based VM Backup to leverage the features and capabilities of each of the CA ARCserve Central Applications.
• Manage CA ARCserve D2D r16 nodes in logical, organized, groups.
• Manage CA ARCserve Backup r16 servers in logical, organized, groups.

4.3 System Information

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

4.3.1 System Requirements

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

• CPU--1 GHz or higher processor is recommended
• RAM--1 GB or more is recommended
• Disk Space--840 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

4.3.2 Supported Operating Systems

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

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

4.3.3 Minimum Software Requirements

The minimum software requirements for CA ARCserve Central Reporting are as follows:

• CA ARCserve Central Protection Manager--CA ARCserve Central Reporting communicates with a CA ARCserve Central Protection Manager server to obtain data and generate reports. You must install the same release number and build number for both applications (CA ARCserve Central Reporting and CA ARCserve Central Protection Manager) to help ensure that they can communicate properly.

  Note: For more information about the system requirements for CA ARCserve Central Protection Manager, see the CA ARCserve Central Protection Manager Release Notes.

• Internet Browser--CA ARCserve Central Reporting 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 Reporting requires Adobe Flash Player version 10.2.152.26 or later

4.4 Known Issues

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

• When you load Data Trend reports or select the data point in the chart for a drill-in view, you get a script error message. This error message occurs if the trending history is too long or there are too many nodes in the drill-in view. This error only happens if you are using Internet Explorer 8 or older versions of Mozilla Firefox (older than 4.0).

  To prevent this problem from occurring, do one of the following based on the browser you are using:

  For Firefox users:

  1. Enter "about:config" in the Firefox address bar and click Enter.

     A list of preferences is displayed.

  2. Enter "dom.max_chrome_script_run_time" in the Filter field.

     The Timeout value is displayed.

  3. Increase the timeout value as necessary.

     Note: The time unit is in seconds.

  For more details regarding this issue, refer to the http://kb.mozillazine.org/Dom.max_chrome_script_run_time.

For Internet Explorer 8 users:

1. From the Start menu, select Run.
2. Enter "Regedt32.exe" and click Enter.

   The Registry Editor dialog opens.

   Note: You must be logged in to the computer using the Administrator account or an account with administrative privileges to open Registry Editor.

3. Open the following key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles.

   Note: If the Styles key is not available, create a key and name it Styles.

4. Create a DWORD value named "MaxScriptStatements" for the Styles key and set the value to the desired number of script statements.

   Note: If you are uncertain as to what value to set the key to, you can use 0xFFFFFFFF.

For more details regarding this issue, refer to the http://support.microsoft.com/kb/175500.

• If CA ARCserve Central Protection Manager changes to a new database, then CA ARCserve Central Reporting can have problems connecting to the new database. This behavior occurs because the database connects to CA ARCserve Central Protection Manager while the former database is accessible. To resolve this problem, do the following:
  1. From the CA ARCserve Central Protection Manager Configuration module in the CA ARCserve Central Reporting application, click Save.
  2. Restart the CA ARCserve Central Applications web service by doing the following:
     • Go to My Computer on your desktop, right-click and select Manage.

       The Server Manager screen opens.

     • Select Configuration and click Services.

       The Services list is displayed.

     • Right-click CA ARCserve Central Applications Service and click Restart.

  CA ARCserve Central Reporting connects to the new CA ARCserve Central Protection Manager database.

• When launching any Trend Report (Application Data Trend, Backup Size Trend, or Volume Trend) with 'Week' selected as your view, the report displays the forecast data rather than the requested data. This behavior is a known FusionCharts issue.
• When you use Mozilla or Firefox to view reports, the browser generates “Unexpected Error Occurred” messages. This happens when you refresh the webpage before the reports load completely. To prevent the browser from generating the message, allow the reports to load completely before you refresh the webpage.
• To generate reports for CA ARCserve Backup nodes, you must use CA ARCserve Central Reporting with the CA ARCserve Backup r16 General Availability release or later.
• If you are configuring your email alert notification settings, and the subject field contains surrogate characters (multilingual characters that cannot be represented by a one double-byte code in UTF-16 encoding), these surrogate characters may appear as garbage characters in the email alerts received. (The email alerts will still be sent out, but the email subject field that is received may be affected). If this happens, you should reword the email subject and not include surrogate characters.
• 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.

5.0 CA ARCserve Central Virtual Standby Release Notes

5.1 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.

5.2 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.

5.3 System Information

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

5.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

5.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.

5.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

5.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

5.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

5.3.6 Application Recovery Support

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

5.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.

5.4 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.5 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

This release of CA ARCserve Central Applications 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.