CA Technologies

CA ARCserve® Central Applications r16 Release Notes

1.0 Welcome
1.1 System Requirements the CA ARCserve Central Applications Suite

2.0 CA ARCserve Central Host-Based VM Backup Release Notes
2.1 Welcome
2.2 Features
  2.2.1 Features Included with Update 4
  2.2.2 Features Included with Update 5
  2.2.3 Features Included with Update 6
  2.2.4 Features Included with Update 7
2.3 System Information
  2.3.1 System Requirements
  2.3.2 Supported Operating Systems
  2.3.3 Supported Hypervisors
  2.3.4 Supported Operating Systems for CA ARCserve D2D Proxy Servers
  2.3.5 Supported Operating Systems for Protected Virtual Machines
  2.3.6 Supported Operating Systems for Application Level Restores
  2.3.7 Minimum Software Requirements
  2.3.8 Application Recovery Support
  2.3.9 Supported Disks
2.4 Known Issues
2.5 Limitations

3.0 CA ARCserve Central Protection Manager Release Notes
3.1 Welcome
3.2 Features
  3.2.1 Features Included with Update 1
  3.2.2 Features Included with Update 4
  3.2.3 Features Included with Update 5
  3.2.4 Features Included with Update 6
  3.2.5 Features Included with Update 7
3.3 System Information
  3.3.1 System Requirements
  3.3.2 Supported Operating Systems
  3.3.3 Supported Operating Systems for CA ARCserve D2D Servers
  3.3.4 Supported Operating Systems for CA ARCserve Backup Servers
  3.3.5 Minimum Software Requirements
3.4 Known Issues
3.5 Fixed Issues

4.0 CA ARCserve Central Reporting Release Notes
4.1 Welcome
4.2 Features
  4.2.1 Features Included with Update 4
  4.2.2 Features Included with Update 5
  4.2.3 Features Included with Update 6
4.3 System Information
  4.3.1 System Requirements
  4.3.2 Supported Operating Systems
  4.3.3 Minimum Software Requirements
4.4 Known Issues

5.0 CA ARCserve Central Virtual Standby Release Notes
5.1 Welcome
5.2 Features
  5.2.1 Features Included with Update 4
  5.2.2 Features Included with Update 5
  5.2.3 Features Included with Update 6
5.3 System Information
  5.3.1 System Requirements
  5.3.2 Supported Operating Systems
  5.3.3 Supported Hypervisors
  5.3.4 Supported Operating Systems for CA ARCserve D2D Servers
  5.3.5 Minimum Software Requirements
  5.3.6 Application Recovery Support
  5.3.7 Supported Disks
5.4 Known Issues
5.5 Limitations

6.0 Language Certifications

7.0 Contact CA Technologies
7.1 CA ARCserve Central Applications Support Links

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

For more information about CA ARCserve Central Applications Updates, see the Update 4, Update 5, Update 6, and Update 7 Release Notes files.

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

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.

For more information about CA ARCserve Central Applications updates, click on the applicable link:

Update 4 Release Notes

Update 5 Release Notes

Update 6 Release Notes

Update 7 Release Notes

Update 8 Release Notes

2.2 Features

CA ARCserve Central Host-Based VM Backup includes features and capabilities that let you do the following:

Back up data that resides on virtual machines running on VMware vSphere 4.0 or later systems without installing CA ARCserve D2D on the source virtual machines.

Push CA ARCserve D2D backup policies to proxy servers.

Perform full, incremental, and verify backups of virtual machines.

Compress and encrypt backup data.

Store backup sessions in CA ARCserve D2D recovery point format.

Recover data at application level and file level.

Recover multiple virtual machines from host-based backup data.

Perform Bare Metal Recovery (BMR) using host-based backup data.

Discover recently added virtual machines automatically.

Integrate CA ARCserve Central Host-Based VM Backup with CA ARCserve Central Reporting, CA ARCserve Central Protection Manager, and CA ARCserve Central Virtual Standby to leverage the features and capabilities of each application.

2.2.1 Features Included with Update 4

Note: CA ARCserve Central Host-Based VM Backup does not contain Update 1, Update 2, and Update 3. We are starting with Update 4 to synchronize the names of the updates with CA ARCserve D2D.

CA ARCserve Central Host-Based VM Backup r16 Update 4 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, you must upgrade to CA ARCserve D2D r16 Update 4. However, if you decide not to, the old features are still supported.

CA ARCserve D2D integration--CA ARCserve Central Applications integrate with the CA ARCserve D2D r16 general availability release, r16 Update 1, r16 Update 2, and r16 Update 3.
Note: To manage and protect nodes running CA ARCserve D2D r16 Update 4, you must install the Update 4 version of this application on the CA ARCserve Central Applications server.

Redesigned toolbar--The Node screen includes a redesigned toolbar that helps to simplify the process of performing node-related tasks.

Ad-hoc backups--Ad-hoc backups are need-based, rather than being scheduled in advance as part of a backup plan. Ad-hoc backups also let you add customized, unscheduled recovery points, so that you can roll back to previous points in time.

Node Status Summary--The Node screen displays status information for a node when you click the icon in the Status column. The Node Status Summary dialog provides you with information about the last backup, recovery points, and the capacity of the backup destination.

Backup Status Monitor--The Backup Status Monitor lets you view detailed information about in-progress backup jobs. In addition, you can stop in-progress jobs from the Backup Status Monitor.

Discovery--The Discovery process was modified to simplify the process of discovering nodes automatically.

Copy policies--You can now copy existing policies and save them as new policies. This capability simplifies the process of creating new policies.

Preflight Check--The Preflight Check (PFC) utility is a new feature that lets you run vital checks on nodes to detect conditions that can cause backup jobs to fail. You can view the results of the PFC for a node by clicking the icon in the PFC Status column on the Node screen.

PFC Status--From the PFC Status column on the Node screen, you can now display the results of the last PFC. The Preflight Check Summary dialog displays information about the following:
- Changed Block Tracking is enabled on the virtual machine.
- VMware Tools is installed on the virtual machine.
- Status of the disk.
- Power state of the virtual machine.
- The login credentials are correct.
- Details about the applications that are installed on the virtual machine.
When PFC detects a condition that can cause backups to fail, click a link on the dialog to view information about how to correct the condition.

Restoring data--The restore process was modified to simplify the process of restoring data. The Restore option was removed from the Navigation bar. You now start the restore process by doing one of the following:
- Click the node on the Node screen and then click Restore on the pop-up menu.
- Click the check box next to the node on the Node screen and then click Restore on the toolbar.

Navigation bar--The Navigation bar enhanced to demonstrate the following behavior:
- You can now resize the Navigation bar on the user interface.
- When you click the tab to log in to a different Central Application, the other application now opens in a new window.
- When you remove a tab from the Navigation bar, a message now displays to confirm that you want to remove the tab.

Hide or Unhide columns--You can now hide or unhide columns from the Node screen. Hover your mouse over the column name to display the drop-down icon. Click Columns from the drop-down menu to display the list of columns that are displayed on the Node screen. Simply check the column name that you want to hide or uncheck to display the column.

2.2.2 Features Included with Update 5

CA ARCserve Central Host-Based VM Backup r16 Update 5 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, upgrade to CA ARCserve D2D r16 Update 5. If you do not upgrade to Update 5, the features from previous updates and releases are still supported.

The policy deployment process was enhanced to simplify the following tasks:
- Filter nodes that are based on the group name or node name on the Assign/Unassign Policy dialog.
- Navigate from page to page using a paging toolbar on the Assign/Unassign Policy dialog.

The node management process was enhanced to simplify the following tasks:
- Update one or more nodes simultaneously on the Node screen. You can now update nodes using the following methods:
  - From the Nodes list, select the nodes that you want to update, right-click the nodes and then click Update Nodes on the pop-up menu.
  - From the Groups list, right-click a node group and click Update Nodes on the pop-up menu.
- Filter nodes that are based on the group name on the Add Group dialog.
- Filter nodes that are based on the host name of the node on the Add Group dialog.
- Navigate from page to page using a paging toolbar on the Add Group dialog.

This update release now lets you protect Microsoft SQL Server 2012 databases. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now lets you host the CA ARCserve Central Protection Manager database using Microsoft SQL Server 2012. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now supports the following hypervisors:
- VMware ESXi 5.0 Update 1
- VMware vCenter 5.0 Update 1

With this update release, the application lets you back up virtual machines using VMware VDDK 5.0 Update 1.

2.2.3 Features Included with Update 6

CA ARCserve Central Host-Based VM Backup r16 Update 6 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, upgrade to CA ARCserve D2D r16 Update 6. If you do not upgrade to Update 6, the features from previous updates and releases are still supported,.

Update 6 provides you with improved integration with VMware vMotion. For example:
- When a Host-Based VM Backup (backup) job is running, you cannot submit a Storage vMotion migration operation. To alert you of the condition, vCenter now displays a message indicating that Host-Based VM Backup disabled the migration operation.
  Note: Optionally, you can terminate the backup and submit the Storage vMotion migration operation.
- When a Storage vMotion migration operation is in progress, Host-Based VM Backup now queues the backup job until the migration operation is complete.

The node management process was enhanced to simplify the following tasks:
- Nodes are now unavailable when they are deleted or cannot be detected from the server.
- The ability to view the status of the policy deployment job displays in the Policy column.
- You can now view backup jobs waiting in the queue, which is displayed in the Job column. In addition, the priority levels of backup jobs are described when you run a Backup Now.
- You can now update multiple nodes simultaneously using the existing credentials or specifying new credentials. You can also force the server to manage the selected nodes.
- The "Unassigned" node group is now called "Nodes without a policy" and the "Ungrouped" node group is now called "Nodes without a group".

The configuration process was enhanced to simplify the following tasks:
- The ability to set email alerts for newly discovered nodes. You can configure this setting through the Email and Alert Configuration screen.
- The ability to configure the CA ARCserve Central Protection Manager server in CA ARCserve Central Host-Based VM Backup so that you can view Host-Based VM Backup discovered nodes email alert information from CA ARCserve Central Reporting.
- You can now view a vCenter/ESX Host list from the Discovery Configuration screen when setting up a schedule to discover nodes.

You no longer need to reset the Changed Block Tracking (CBT) function when backup jobs fail. Host-Based VM Backup now automatically enables CBT on the virtual machine.

You can now set email alert notifications for failed catalog jobs when creating backup policies (Preferences tab).

You can now set email alert notifications for backup jobs that are waiting in the queue, skipped, or replaced with another job. You can configure this setting through the policy Preferences tab.

A new topic is added to this release describing how to retrieve used block data after submitting a full disk backup job. The topic is called Perform Full Disk Backups Containing Only Used Block Data.

You can now open a Live Chat session with CA Technologies Technical Support representatives from all of the screens. The link is at the bottom right corner of the screens.
Live Chat provides real-time monitoring and live help/support. Live Chat lets you optimize intelligent conversation between you and the CA ARCserve Central Applications Technical Support team. The chat allows you to address your concerns and questions immediately while still maintaining access to the product. Upon completion of the chat session, you can send a transcript of the chat to your email address.

Note: You may need to add the Live Chat link to your Trusted sites.

CA ARCserve Central Host-Based VM Backup now supports VMware vSphere Storage Appliance (VSA). Host-Based VM Backup can back up virtual machines that are on a VSA datastore. Host-Based VM Backup can restore virtual machines to a VSA data store.

2.2.4 Features Included with Update 7

CA ARCserve Central Host-Based VM Backup r16 Update 7 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, upgrade to CA ARCserve D2D r16 Update 7. If you do not upgrade to Update 7, the features from previous updates and releases are still supported.

The node management process was enhanced to simplify the following tasks:

You can now merge a job for a particular node or nodes. Two new options are now available when you right-click a node: Pause Merge Job and Resume Merge Job.

The policies backup settings was enhanced to simplify the following tasks:

The ability to create retention settings based on the number of recovery points to retain or the number of recovery sets to retain.

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

2.3.3 Supported Hypervisors

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

VMware ESX Server:
- ESX Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- ESXi Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- ESX Server 4.1, 4.1 Update 1 or 4.1 Update 2
- ESXi Server 4.1, 4.1 Update 1 or 4.1 Update 2
- ESXi Server 5.0, 5.0 Update 1

VMware vCenter Server:
- vCenter Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- vCenter Server 4.1, 4.1 Update 1 or 4.1 Update 2
- vCenter Server 5.0, 5.0 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)

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 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 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
- VMware VIX API 1.10.1 or later

2.3.8 Application Recovery Support

CA ARCserve Central Host-Based VM Backup lets you recover the following application data:

Microsoft Exchange Server:
- Microsoft Exchange Server 2003 SP1 Standalone
- Microsoft Exchange Server 2007 Standalone/Cluster Continuous Replication (CCR) configuration
- Microsoft Exchange Server 2010 Standalone/Database Availability Group (DAG) configuration

Microsoft SQL Server:
- Microsoft SQL Server 2005 Express/Standard/Workgroup/Enterprise
- Microsoft SQL Server 2008, SQL Server 2008 R2 Express/Web/Standard/Workgroup/Enterprise
- Microsoft SQL Server 2012 Express/Web/Standard/Enterprise

Note: For more information about service pack level support for operating systems and applications refer to the CA ARCserve D2D 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.

Disk (Volume) Type	As Backup Source	As Backup Destination
GPT Disk	Yes	Yes
System Reserved Partition (Windows 2008 R2 Boot Manger)	Yes	Not applicable
Mounted Volume (No drive letter/NTFS formatted)	Yes	Yes
RAW Volume (No drive letter/Not formatted)	No	No
VHD Mounted Volume (Windows 2008 R2)	No	Yes
Dynamic Disk:
No RAID	Yes	Yes
Software RAID (RAID-0 (Stripe)	Yes	Yes
Software RAID (RAID-1 (Mirrored)	Yes	Yes
Software RAID-5	No	Yes
Hardware RAID (include Embedded RAID)	Not Applicable	Not Applicable
File System:
FAT/FAT32	No	Yes*
Shared Volume:
Windows Shared Volume	No	Yes
Linux Shared Volume (samba shared)	No	Yes
Device Type:
Removable Disk (Ex. Memory Stick, RDX)	No	Yes

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

A blank browser window can appear when you log in to the application after upgrading CA ARCserve Central Applications to this update release. This behavior occurs when the browser window was open and logged in to the application before you applied this update release. To correct this behavior, delete the browser cache and then reload the page.

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 first-time that you open CA ARCserve Central Host-Based VM Backup or launch CA ARCserve D2D from the application, a blank page with a warning message appears. To correct this problem, reload the page.

The application does not support protecting virtual machine data that resides on FAT/FAT32 file systems 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, disable User Account Control (UAC) in the guest operating system and then resubmit the backup job. For information about how to disable UAC, see the CA ARCserve Central Host-Based VM Backup User Guide.
  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.

Participants in the Beta and Release Candidate testing program must uninstall the Beta or Release Candidate version of CA ARCserve Central Host-Based VM Backup before installing the General Availability version.

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.

For full backups, the application lets you back up complete virtual machine disks in NFS data stores. However, if you do not use data compression, the backup data sets can be the same size as the source disk.
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.

When upgrading from CA ARCserve Central Applications r16 GA (general availability release), r16 Update 1, or r16 Update 4 to this update, and the download server is configured as a Staging Server, verify that CA ARCserve Central Applications r16 Update 5 is installed on the Staging Server before you use the Update utility to upgrade CA ARCserve Central Applications to r16 Update 5.

The Merge Failure alert option is not applied to policies on D2D nodes under the following conditions:
- The CA ARCserve Central Host-Based VM Backup server is running r16 Update 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 Host-Based VM Backup server and includes the (new) Merge Failure alert option, and then the D2D nodes are upgraded to r16 Update 5.
To correct this behavior, update and save the policy on the Host-Based VM Backup server. When you save the policy, Host-Based VM Backup applies the policy changes to the nodes automatically.

When you update the application to Update 5 or later, the licensed machine or ESX server is duplicated. To resolve this problem, delete the machine that contains the FQDN host name from the License Management screen.

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.

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.

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 machine, 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 or Hyper-V 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.

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.

For more information about CA ARCserve Central Applications updates, click on the applicable link:

Update 4 Release Notes

Update 5 Release Notes

Update 6 Release Notes

Update 7 Release Notes

Update 8 Release Notes

3.2 Features

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

Deploy CA ARCserve D2D to remote nodes.

Discover physical and virtual CA ARCserve D2D nodes via Active Directory.

Push backup policies to CA ARCserve D2D nodes.

Manage CA ARCserve D2D r16 nodes in logical, organized, groups.

Manage CA ARCserve Backup r16 servers in logical, organized, groups.

Restore files, folders, and applications from CA ARCserve D2D recovery points.

Update the application and CA ARCserve D2D servers automatically or manually.

Integrate CA ARCserve Central Protection Manager with CA ARCserve Central Reporting, CA ARCserve Central Virtual Standby, and CA ARCserve Central Host-Based VM Backup to leverage the features and capabilities of each of the applications.

3.2.1 Features Included with Update 1

CA ARCserve Central Protection Manager r16 Update 1 includes the following feature enhancements and updates:

Integration with Nimsoft and Kaseya IT Management Server Infrastructure management tools--You can configure CA ARCserve Central Protection Manager to publish information about alert messages in real time to IT Management Server Infrastructure management tools. This capability lets IT Server Management Administrators respond to CA ARCserve Central Protection Manager alerts in an appropriate manner.

3.2.2 Features Included with Update 4

Note: CA ARCserve Central Protection Manager does not contain Update 2 and Update 3. We are skipping Update 2 and Update 3 to synchronize the names of the updates with CA ARCserve D2D.

CA ARCserve Central Protection Manager r16 Update 4 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, you must upgrade to CA ARCserve D2D r16 Update 4. However, if you decide not to, the old features are still supported.

CA ARCserve D2D integration--CA ARCserve Central Applications integrate with the CA ARCserve D2D r16 general availability release, r16 Update 1, r16 Update 2, and r16 Update 3.
Note: To manage and protect nodes running CA ARCserve D2D r16 Update 4, you must install the Update 4 version of this application on the CA ARCserve Central Applications server.

Redesigned toolbar--The Node screen includes a redesigned toolbar that helps to simplify the process of performing node-related tasks.

Ad-hoc backups--Ad-hoc backups are need-based, rather than being scheduled in advance as part of a backup plan. Ad-hoc backups also let you add customized, unscheduled recovery points, so that you can roll back to previous points in time.

Node Status Summary--The Node screen displays status information for a node when you click the icon in the Status column. The Node Status Summary dialog provides you with information about the last backup, recovery points, and the capacity of the backup destination.

Backup Status Monitor--The Backup Status Monitor lets you view detailed information about in-progress backup jobs. In addition, you can stop in-progress jobs from the Backup Status Monitor.

Discovery--The Discovery process was modified to simplify the process of discovering nodes automatically.

Navigation bar--The Navigation bar enhanced to demonstrate the following behavior:
- You can now resize the Navigation bar on the user interface.
- When you click the tab to log in to a different Central Application, the other application now opens in a new window.
- When you remove a tab from the Navigation bar, a message now displays to confirm that you want to remove the tab.

SRM Configuration--SRM configuration was modified to simplify the process of defining schedules to collect SRM data.

CA ARCserve Backup Data Synchronization--CA ARCserve Backup data synchronization was modified to simply the process of defining schedules to synchronize data with the CA ARCserve Backup database.

Hide or Unhide columns--You can now hide or unhide columns from the Node screen. Hover your mouse over the column name to display the drop-down icon. Click Columns from the drop-down menu to display the list of columns that are displayed on the Node screen. Simply check the column name that you want to hide or uncheck to display the column.

3.2.3 Features Included with Update 5

CA ARCserve Central Protection Manager r16 Update 5 includes the following feature enhancements and updates:

The CA ARCserve D2D deployment process was enhanced to simplify the following tasks:
- Filter nodes based on the host name of the node on the D2D Deployment dialog.
- Filter nodes based on the group (Group Name) to which the nodes are members of on the D2D Deployment dialog.
- Navigate from page to page using a paging toolbar on the D2D Deployment dialog.

The policy deployment process was enhanced to simplify the following task:
- Filter nodes that are based on the group name or node name on the Assign/Unassign Policy dialog.
- Navigate from page to page using a paging toolbar on the Assign/Unassign Policy dialog.

The node management process was enhanced to simplify the following tasks:
- Update one or more nodes simultaneously on the Node screen. You can now update nodes using the following methods:
  - From the Nodes list, select the nodes that you want to update, right-click the nodes and then click Update Nodes on the pop-up menu.
  - From the Groups list, right-click a node group and click Update Nodes on the pop-up menu.
- Filter nodes that are based on the group name on the Add Group dialog.
- Filter nodes that are based on the host name of the node on the Add Group dialog.
- Navigate from page to page using a paging toolbar on the Add Group dialog.

This update release now lets you protect Microsoft SQL Server 2012 databases. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now lets you host the CA ARCserve Central Protection Manager database using Microsoft SQL Server 2012. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

3.2.4 Features Included with Update 6

CA ARCserve Central Protection Manager r16 Update 6 includes the following feature enhancements and updates:

The node management process was enhanced to simplify the following tasks:
- The ability to view the status of the policy deployment job displayed in the Policy column.
- You can now update multiple nodes simultaneously using the existing credentials or specifying new credentials. You can also force the server to manage the selected nodes.
- The "Unassigned" node group is now called "Nodes without a policy" and the "Ungrouped" node group is now called "Nodes without a group".

The node deployment process was enhanced to simplify the following tasks:
- The ability to view the latest version of CA ARCserve D2D when you deploy to a node and supporting lower versions of CA ARCserve D2D.
- The ability to select/unselect all nodes on the D2D Deployment dialog.

The configuration process was enhanced to simplify the following tasks:
- The ability to set email alerts for newly discovered nodes. You can configure this setting through the Email and Alert Configuration screen.
- A new vendor type is now added for Cloud Configuration for File Copy: Fujitsu Cloud (Windows Azure).
- You can now view an Active Directory list when setting up a schedule to discover nodes in the Discovery Configuration screen.

You can now open a Live Chat session with CA Technologies Technical Support representatives from all of the screens. The link is at the bottom right corner of the screens.
Live Chat provides real-time monitoring and live help/support. Live Chat lets you optimize intelligent conversation between you and the CA ARCserve Central Applications Technical Support team. The chat allows you to address your concerns and questions immediately while still maintaining access to the product. Upon completion of the chat session, you can send a transcript of the chat to your email address.

Note: You may need to add the Live Chat link to your Trusted sites.

3.2.5 Features Included with Update 7

CA ARCserve Central Protection Manager r16 Update 7 includes the following feature enhancements and updates:

The node management process was enhanced to simplify the following tasks:

You can now merge a job for a particular node or nodes. Two new options are now available when you right-click a node: Pause Merge Job and Resume Merge Job.

The policies settings were enhanced to simplify the following tasks:

From the Backup Settings tab: The ability to create retention settings that is based on the number of recovery points to retain or the number of recovery sets to retain.

From the Preferences tab: You can send merge job alerts that were stopped, skipped, failed, crashed, or merge jobs that were a success.

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

3.3.3 Supported Operating Systems for CA ARCserve D2D Servers

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

To access the CA ARCserve D2D Compatibility Matrix, click the link listed below to open the CA ARCserve D2D Support website, then click Compatibility Matrix in the Support for r16 (Windows) drop-down list.

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

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.

To access the CA ARCserve Backup Readme, click the link listed below to open the CA ARCserve Backup Support website, then select the letter 'R' in the All Documentation section and click the View HTML link for the CA ARCserve Backup Readme.

https://support.ca.com/cadocs/0/CA%20ARCserve%20%20Backup%20r16-ENU/Bookshelf.html

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 Express/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

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.

A blank browser window can appear when you log in to the application after upgrading CA ARCserve Central Applications to this update release. This behavior occurs when the browser window was open and logged in to the application before you applied this update release. To correct this behavior, delete the browser cache and then reload the page.

The first-time that you open CA ARCserve Central Protection Manager or launch CA ARCserve D2D from the application, a blank page with a warning message appears. To correct this problem, reload the page.

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 and then perform a full CA ARCserve D2D data synchronization, CA ARCserve D2D omits r15 data and generates r16 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.

Participants in the Beta and Release Candidate testing program must uninstall the Beta or Release Candidate version of CA ARCserve Central Protection Manager before installing the General Availability version. In addition, when you install the General Availability version of the application on a computer where a Beta or Release Candidate version was installed, specify the Overwrite existing database option on the Database Settings dialog as you perform the installation.

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.

To help ensure that the Node Explorer on the Restore screen can display and filter nodes, expand each of the node groups the first time that you use the Restore screen. As a best practice, expand all of the node groups before you apply node filters.

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.

When upgrading from CA ARCserve Central Applications r16 GA (general availability release), r16 Update 1, or r16 Update 4 to this update, and the download server is configured as a Staging Server, verify that CA ARCserve Central Applications r16 Update 5 is installed on the Staging Server before you use the Update utility to upgrade CA ARCserve Central Applications to r16 Update 5.

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

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.

For more information about CA ARCserve Central Applications Updates, click on the applicable link:

Update 4 Release Notes

Update 5 Release Notes

Update 6 Release Notes

Update 7 Release Notes

Update 8 Release Notes

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.2.1 Features Included with Update 4

Note: CA ARCserve Central Reporting does not contain Update 1, Update 2, and Update 3. We are starting with Update 4 to synchronize the names of the updates with CA ARCserve D2D.

CA ARCserve Central Reporting r16 Update 4 includes the following feature enhancements and updates:

CA ARCserve D2D integration--CA ARCserve Central Applications integrate with the CA ARCserve D2D r16 general availability release, r16 Update 1, r16 Update 2, and r16 Update 3.
Note: To manage and protect nodes running CA ARCserve D2D r16 Update 4, you must install the Update 4 version of this application on the CA ARCserve Central Applications server.

Navigation bar--The Navigation bar enhanced to demonstrate the following behavior:
- You can now resize the Navigation bar on the user interface.
- When you click the tab to log in to a different Central Application, the other application now opens in a new window.
- When you remove a tab from the Navigation bar, a message now displays to confirm that you want to remove the tab.

New Email Schedules--The Repeat Method in the Schedule tab now displays Day of the Month when you select Every Selected Day of the Month from the drop-down.

4.2.2 Features Included with Update 5

CA ARCserve Central Reporting r16 Update 5 includes the following feature enhancements and updates:

This update release now lets you protect Microsoft SQL Server 2012 databases. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now lets you host the CA ARCserve Central Protection Manager database using Microsoft SQL Server 2012. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

4.2.3 Features Included with Update 6

CA ARCserve Central Reporting r16 Update 6 includes the following feature enhancements and updates:

Two new Event Types are now added to the Alert Report:
- Skip/Merge job waiting in the job queue: This alert generates a report of jobs that are skipped or merged in the waiting queue from CA ARCserve Central Host-Based VM Backup.
- Discovery: This alert generates a report of newly discovered nodes from CA ARCserve Central Protection Manager or CA ARCserve Central Host-Based VM Backup.

You can now open a Live Chat session with CA Technologies Technical Support representatives from all of the screens. The link is at the bottom right corner of the screens.
Live Chat provides real-time monitoring and live help/support. Live Chat lets you optimize intelligent conversation between you and the CA ARCserve Central Applications Technical Support team. The chat allows you to address your concerns and questions immediately while still maintaining access to the product. Upon completion of the chat session, you can send a transcript of the chat to your email address.

Note: You may need to add the Live Chat link to your Trusted sites.

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

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.

A blank browser window can appear when you log in to the application after upgrading CA ARCserve Central Applications to this update release. This behavior occurs when the browser window was open and logged in to the application before you applied this update release. To correct this behavior, delete the browser cache and then reload the page.

The first-time that you open CA ARCserve Central Reporting, a blank page with a warning message appears. To correct this problem, reload the page.

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:

From the Start menu, select Run.

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.

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.

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 CA ARCserve Backup r16 Service Pack 1.

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.

Participants in the Beta and Release Candidate testing program must uninstall the Beta or Release Candidate version of CA ARCserve Central Reporting before installing the General Availability version.

When upgrading from CA ARCserve Central Applications r16 GA (general availability release), r16 Update 1, or r16 Update 4 to this update, and the download server is configured as a Staging Server, verify that CA ARCserve Central Applications r16 Update 5 is installed on the Staging Server before you use the Update utility to upgrade CA ARCserve Central Applications to r16 Update 5.

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.

For more information about CA ARCserve Central Applications updates, click on the applicable link:

Update 4 Release Notes

Update 5 Release Notes

Update 6 Release Notes

Update 7 Release Notes

Update 8 Release Notes

5.2 Features

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

Convert CA ARCserve D2D recovery points to VMware Virtual Disk (VMDK) and Microsoft Virtual Hard Drive (VHD) file formats based on a schedule.

Store recovery point snapshots, which resemble CA ARCserve D2D recovery points, on hypervisor systems.

Power on virtual machines manually or automatically using the VMDK or VHD files in the event a disaster occurs on CA ARCserve D2D servers, or if you simply want to offline CA ARCserve D2D source servers for maintenance.

Push conversion policies to CA ARCserve D2D servers.

Perform virtual to physical (V2P) disaster recovery from virtual machines to the original hardware or to different hardware using the recovery point snapshots.

Integrate CA ARCserve Central Virtual Standby with CA ARCserve Central Protection Manager, CA ARCserve Central Reporting, and CA ARCserve Central Host-Based VM Backup to leverage the features and capabilities of each of the applications.

5.2.1 Features Included with Update 4

Note: CA ARCserve Central Virtual Standby does not contain Update 1, Update 2, and Update 3. We are starting with Update 4 to synchronize the names of the updates with CA ARCserve D2D.

CA ARCserve Central Virtual Standby r16 Update 4 includes the following feature enhancements and updates:

Note: To ensure that the following features are available to you, you must upgrade to CA ARCserve D2D r16 Update 4. However, if you decide not to, the old features are still supported.

CA ARCserve D2D integration--CA ARCserve Central Applications integrate with the CA ARCserve D2D r16 general availability release, r16 Update 1, r16 Update 2, and r16 Update 3.
Note: To manage and protect nodes running CA ARCserve D2D r16 Update 4, you must install the Update 4 version of this application on the CA ARCserve Central Applications server.

Redesigned toolbar--The Node screen includes a redesigned toolbar that helps to simplify the process of performing node-related tasks.

Redesigned Node screen--The Node screen contains new fields that help to simplify the process of managing and monitoring Virtual Standby jobs. When you hover or roll your mouse over a field, the Node screen now displays information about in-progress jobs (Job field), completed jobs (Status field), and conversion results (Last Conversion Result and Last Conversion Time fields). In addition, the Node screen now provides you with summary information about the latest Virtual Standby job that completed successfully or unsuccessfully.

Pause and resume heartbeats--You can now pause and resume one or more heartbeats simultaneously from the Virtual Standby server. You can pause and resume heartbeats at the node level and the group level. It is no longer necessary to log in directly to the nodes to pause and resume heartbeats.

Pause and resume Virtual Standby jobs--You can now pause and resume one or more Virtual Standby jobs simultaneously from the Virtual Standby server. This enhancement lets you pause and resume Virtual Standby jobs at the group level or the node level. It is no longer necessary to log in directly to the nodes to pause and resume Virtual Standby jobs.

Virtual Standby Status Monitor--You can now view the status of in-progress Virtual Standby jobs directly from the Node screen. Optionally, the Virtual Standby Status Monitor lets you cancel in-progress Virtual Standby jobs. It is no longer necessary to log in directly to the nodes to view the status of in-progress jobs or to cancel jobs.

Restoring data--The restore process was modified to simplify the process of restoring data. The Restore option was removed from the Navigation bar. You now start the restore process by doing one of the following:
- Click the node on the Node screen and then click Restore on the pop-up menu.
- Click the check box next to the node on the Node screen and then click Restore on the toolbar.

Copy policies--You can now copy existing policies and save them as new policies. This capability simplifies the process of creating new policies.

Navigation bar--The Navigation bar enhanced to demonstrate the following behavior:
- You can now resize the Navigation bar on the user interface.
- When you click the tab to log in to a different Central Application, the other application now opens in a new window.
- When you remove a tab from the Navigation bar, a message now displays to confirm that you want to remove the tab.

Hide or Unhide columns--You can now hide or unhide columns from the Node screen. Hover your mouse over the column name to display the drop-down icon. Click Columns from the drop-down menu to display the list of columns that are displayed on the Node screen. Simply check the column name that you want to hide or uncheck to display the column.

5.2.2 Features Included with Update 5

CA ARCserve Central Virtual Standby r16 Update 5 includes the following feature enhancements and updates:

The policy deployment process was enhanced to simplify the following tasks:
- Filter nodes that are based on the group name or node name on the Assign/Unassign Policy dialog.
- Navigate from page to page using a paging toolbar on the Assign/Unassign Policy dialog.

The node management process was enhanced to simplify the following tasks:
- Update one or more nodes simultaneously on the Node screen. You can now update nodes using the following methods:
  - From the Nodes list, select the nodes that you want to update, right-click the nodes and then click Update Nodes on the pop-up menu.
  - From the Groups list, right-click a node group and click Update Nodes on the pop-up menu.
- Filter nodes that are based on the group name on the Add Group dialog.
- Filter nodes that are based on the host name of the node on the Add Group dialog.
- Navigate from page to page using a paging toolbar on the Add Group dialog.

This update release now lets you protect Microsoft SQL Server 2012 databases. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now lets you host the CA ARCserve Central Protection Manager database using Microsoft SQL Server 2012. Support includes the Express, Web, Standard, Business Intelligence, and Enterprise versions of Microsoft SQL Server 2012.

This update release now supports the following hypervisors:
- VMware ESXi 5.0 Update 1
- VMware vCenter 5.0 Update 1

With this update release, the application lets you back up virtual machines using VMware VDDK 5.0 Update 1.

5.2.3 Features Included with Update 6

CA ARCserve Central Virtual Standby r16 Update 6 includes the following feature enhancements and updates:

The node management process was enhanced to simplify the following tasks:
- The ability to view the status of the policy deployment job displayed in the Policy column.
- You can now power on virtual machines directly from the application. Use the Standby VM button located on the Node toolbar.
- You can now update multiple nodes simultaneously using the existing credentials or specifying new credentials. You can also force the server to manage the selected nodes.
- The "Unassigned" node group is now called "Nodes without a policy" and the "Ungrouped" node group is now called "Nodes without a group".

You can now open a Live Chat session with CA Technologies Technical Support representatives from all of the screens. The link is located at the bottom right corner of the screens.
Live Chat provides real-time monitoring and live help/support. Live Chat lets you optimize intelligent conversation between you and the CA ARCserve Central Applications Technical Support team. The chat allows you to address your concerns and questions immediately while still maintaining access to the product. Upon completion of the chat session, you can send a transcript of the chat to your email address.

Note: You may need to add the Live Chat link to your Trusted sites.

CA ARCserve Central Virtual Standby now supports VMware vSphere Storage Appliance (VSA). Virtual Standby can now create standby virtual machines on VSA datastores. Virtual Standby can perform a virtual to physical (V2P) of a standby virtual machine created on a VSA datastore.

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

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

VMware ESX Server:
- ESX Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- ESXi Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- ESX Server 4.1, 4.1 Update 1 or 4.1 Update 2
- ESXi Server 4.1, 4.1 Update 1 or 4.1 Update 2
- ESXi Server 5.0 or 5.0 Update 1

VMware vCenter Server:
- vCenter Server 4.0, 4.0 Update1, 4.0 Update 2, 4.0 Update 3, or 4.0 Update 4
- vCenter Server 4.1, 4.1 Update 1 or 4.1 Update 2
- vCenter Server 5.0 or 5.0 Update 1

5.3.4 Supported Operating Systems for CA ARCserve D2D Servers

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

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

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

CA ARCserve Central Virtual Standby lets you recover the following application data:

Microsoft Exchange Server:
- Microsoft Exchange Server 2003 SP1 Standalone
- Microsoft Exchange Server 2007 Standalone/Cluster Continuous Replication (CCR) configuration
- Microsoft Exchange Server 2010 Standalone/Database Availability Group (DAG) configuration

Microsoft SQL Server:
- Microsoft SQL Server 2005 Express/Standard/Workgroup/Enterprise
- Microsoft SQL Server 2008, SQL Server 2008 R2 Express/Web/Standard/Workgroup/Enterprise
- Microsoft SQL Server 2012 Express/Web/Standard/Enterprise

Note: For more information about service pack level support for operating systems and applications refer to the CA ARCserve D2D 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.

Disk (Volume) Type	In Backup Source
GPT Disk	No
System Reserved Partition (Windows 2008 R2 Boot Manger)	Yes
Mounted Volume (No drive letter/NTFS formatted)	Yes
RAW Volume (No drive letter/Not formatted)	No
VHD Mounted Volume (Windows 2008 R2)	No
Dynamic Disk:
No RAID	Yes
Software RAID (RAID-0 (Stripe)	Yes
Software RAID (RAID-1 (Mirrored)	Yes
Software RAID-5	No
Hardware RAID (include Embedded RAID)	Not Applicable
File System:
FAT/FAT32	No
Shared Volume:
Windows Shared Volume	No
Linux Shared Volume (samba shared)	No
Device Type:
Removable Disk (Ex. Memory Stick, RDX)	No

5.4 Known Issues

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

A blank browser window can appear when you log in to the application after upgrading CA ARCserve Central Applications to this update release. This behavior occurs when the browser window was open and logged in to the application before you applied this update release. To correct this behavior, delete the browser cache and then reload the page.

When you log in to D2D directly from the Virtual Standby application server immediately after you upgrade to Virtual Standby Update 4, the Virtual Standby tab may not display correct status information on Internet Explorer browsers. To correct this behavior, close all Internet Explorer browser windows, delete all browsing history and cache, and then check the status information on the Virtual Standby tab.

The first-time that you open CA ARCserve Central Virtual Standby or launch CA ARCserve D2D from the application, a blank page with a warning message can appear. To correct the problem, reload the page.

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.

When a standby virtual machine resides in a network that uses IP segmentation that is different from the source server, after you power on the recovery point snapshot, log in to the VM and configure the correct IP address (on the standby virtual machine).

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

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 Virtual Standby 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 Virtual Standby windows and then log in to CA ARCserve Central Virtual Standby.

Localized versions of CA ARCserve Central Virtual Standby may display truncated text in right-click pop-up menus on the Node screen. To correct this problem, delete the browser cache (temporary Internet files), refresh the screen, and try again.

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.

Hyper-V integration services are not installed on CA ARCserve D2D nodes that were imported from CA ARCserve Central Host-Based VM Backup. The integration services are required when CA ARCserve Central Virtual Standby is configured to store the recovery point snapshots on the Hyper-V server.
Solution: Install Hyper-V Integration Services using the Hyper-V Manager Console after the Virtual Standby virtual machine boots from the recovery point snapshot.

CA ARCserve D2D licensing error email messages occur under the following scenario:
- CA ARCserve Central Virtual Standby was uninstalled and then reinstalled.
- The CA ARCserve D2D nodes that you were protecting before you uninstalled CA ARCserve Central Virtual Standby were added using the Node screen.
- The policy was redeployed to the nodes.
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.

Participants in the Beta and Release Candidate testing program must uninstall the Beta or Release Candidate version of CA ARCserve Central Virtual Standby before installing the General Availability version.

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.

When you perform a V2P recovery using the current snapshot, a message may appear that indicates the following:
```
Failed to get select 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.

To help ensure that the Node Explorer on the Restore screen can display and filter nodes, expand each of the node groups the first time that you use the Restore screen. As a best practice, expand all of the node groups before you apply node filters.

When you try to power on a Virtual Standby virtual machine from a particular snapshot, the Virtual Standby virtual machine will not power on. In addition, a message similar to the following appears in the Activity Log:
```
Failed to create bootable snapshot for session X.
```
Solution: Delete the Virtual Standby virtual machine and restart the virtual conversion process.

When you pause a Virtual Standby job, the Activity Log continues to display the event "Virtual Standby job started" even though the Virtual Standby job does not run.

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.

When upgrading from CA ARCserve Central Applications r16 GA (general availability release), r16 Update 1, or r16 Update 4 to this update, and the download server is configured as a Staging Server, verify that CA ARCserve Central Applications r16 Update 5 is installed on the Staging Server before you use the Update utility to upgrade CA ARCserve Central Applications to r16 Update 5.

When you update the application to Update 5 or later, the licensed machine or ESX server is duplicated. To resolve this problem, delete the machine that contains the FQDN host name from the License Management screen.

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

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

7.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.
https://support.ca.com/prodinfo/centappssupportofferings

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