Arcserve Replication and High Availability. r16.5 Release Notes

Transcription

1 Arcserve Replication and High Availability r16.5 Release Notes

2 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the Documentation ), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 Product References This document references the following CA Technologies products: Arcserve Replication Arcserve High Availability (HA) Arcserve Assured Recovery Arcserve Content Distribution Contact Technical Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At arcserve.com/support, you can access the following: 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 Provide Feedback If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is also available on the CA Technologies Support website, found at

4

5 Contents Chapter 1: Welcome 9 Chapter 2: Arcserve RHA r16.5 Service Pack 4 11 New Features and Enhancements Enhancements Known Issues Included Fixes Chapter 3: Arcserve RHA r16.5 Service Pack 3 19 New Features and Enhancements Integration with CA ARCserve Unified Data Protection Assured Recovery Testing Before Journals are Applied Perform Switchover Before Journals are Applied Enhancements Known Issues Included Fixes Chapter 4: Arcserve RHA r16.5 Service Pack 2 29 New Features and Enhancements VMware vshpere 5.5 Support Microsoft Hyper-V 2012 R2 Support Microsoft Windows 2012 R2 Support Known Issues Included Fixes Dropped Systems and Platforms Support Chapter 5: Arcserve RHA r16.5 Service Pack 1 37 New Features and Enhancements Microsoft Exchange Server 2013 Support Microsoft SharePoint Server 2013 Support Microsoft SharePoint Foundation 2010 Support Network Traffic Redirection Supports Computer Alias Enhancements Known Issues Included Fixes Contents 5

6 Dropped Systems and Platforms Support Chapter 6: Arcserve RHA r New Features and Enhancements CA ARCserve Central Host-Based VM Backup Support Microsoft Windows Server 2012 Support Full System Cascade Scenario to Add Multiple Replicas MS SQL FILESTREAM BLOB Data Support Enhancements Included Fixes Known Issues Dropped Systems and Platforms Support Chapter 7: Arcserve RHA r16 Service Pack 2 51 New Features and Enhancements Restore Support to a Bare Metal Machine NAT Support Enhancements Included Fixes Known Issues Chapter 8: Arcserve RHA r16 Service Pack 1 59 New Features and Enhancements Proxy Server Support CA ARCserve D2D Support Included Fixes Chapter 9: Arcserve RHA r16 61 Chapter 10: New Features and Enhancements 63 Change Scenario While Running Cloud Support Enhanced Cluster Support Secure Communication Virtualization Enhancements Features No Longer Supported r16.5 Release Notes

7 Chapter 11: Known Issues 67 Chapter 12: System Information 71 Minimum Hardware Requirements Supported Configurations: Windows Supported Configurations: UNIX/Linux Supported Virtual Platforms Installation Considerations Chapter 13: Localized Versions 81 Appendix A: Acknowledgements 83 Contents 7

8

9 Chapter 1: Welcome Welcome to the Arcserve RHA Release Notes. This document contains the following information relating to use of the Arcserve RHA family of products: New and discontinued features, as well information about how the enhancements made to existing features might affect you Issues discovered after publication that you should know before you use this product A list of the fixes included in this release For similar information about previous releases, see the corresponding Release Summaries located on the Support site. 1. Go to support.ca.com. 2. Click Product Documentation from the Get Support box. 3. Select CA ARCserve Replication and High Availability from the Select a Product list. 4. Select the current version from the Select a Release list. 5. Click Go. A list of document titles is displayed. Download the Release Notes for the desired service pack. Throughout this document, the term "Arcserve RHA" refers to all products, unless otherwise specified. Chapter 1: Welcome 9

10

11 Chapter 2: Arcserve RHA r16.5 Service Pack 4 This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5 Service Pack 4. This section contains the following topics: New Features and Enhancements (see page 11) Included Fixes (see page 17) New Features and Enhancements Arcserve RHA r16.5 Service Pack 4 supports the following enhancements: Enhancements Effective with Arcserve RHA Service Pack 4, RHA provides the following enhancements: For Amazon EC2 Microsoft Windows 2003, 2003 R2, 2008, 2008 R2, 2012, and 2012 R2 are supported as master servers for EC2 based Full System scenarios. All x86 and x64 versions, if applicable, are supported. Appliance virtual machines can be Windows 2008 R2, 2012, or 2012 R2. Assured Recovery (AR) is supported for EC2 based Full System scenarios. You can select the Assured Recovery option while creating an EC2 based Full System scenario. You can choose a different VPC on the network mapping dialog for Assured Recovery. Supported instance types for EC2 VM are extended to cover the latest EC2 instance types. You can choose additional instance types for the switchover VM. For more information on Amazon EC2 types, refer to this link: Chapter 2: Arcserve RHA r16.5 Service Pack 4 11

12 New Features and Enhancements Supports up to 22 virtual disks in an appliance including the virtual disks and the CDROM device the appliance already owns. This means that an appliance can serve more scenarios pertaining to different master servers. Note: For Amazon EC2 support, Microsoft.NET Framework 3.5 or above is required on the master server. This is required to install Xen tools on the VM that is running on EC2. If you do not have the proper.net Framework installed, a pre-run error is displayed when you run a scenario. Other Enhancements Upgraded OpenSSL binaries to OpenSSL 1.0.1i. Known Issues The following issues are known to exist in this release: When upgrading from a previous release, running scenarios may fail to start after the upgrade process completes. This behavior occurs during the process of upgrading the Engine. The upgrade process should stop running scenarios and then restart the running scenarios after the upgrade process completes. However, the upgrade process interprets the running scenarios as having new user name and passwords (in error), which prevents the upgrade process from restarting the scenario automatically. To correct this problem, manually start the scenarios that were running before the upgrade started using Run, after the upgrade process completes. Use the Run control from the user interface. If you are unable to reset the Arcserve RHA interface back to the default after rearranging panels using the dock manager, perform the following steps: Find the running directory for the ws_gui.exe file. Close the interface. In this directory, delete the following files: dock_layout.xml, dock_layoutdefault.xml. Relaunch the interface. The interface arrangement is returned to the default layout. Rewind is not supported for applications that use TxF functionality (IIS 7.0) When remotely installing the Arcserve RHA Engine on Windows Server 2008 systems, installation fails if you log in to the Control Services as a local system. To avoid this, use a Domain Admin account to access the Control Service. 12 r16.5 Release Notes

13 New Features and Enhancements When you use the Switch Computer Name redirection method on computers running Windows Server 2008 R2, manually rejoin the Master server to the domain after failover. When a NetBIOS server name is longer than 15 characters, the Arcserve RHA Manager may fail to launch from the Overview screen if a proxy is set in Internet Options. The proxy server can only resolve DNS names, not NetBIOS names. After 72 hours, the bare metal machine will reboot automatically (applicable for full system scenarios). When you boot the bare metal machine after recovery, some drivers may be missing. Manually install these drivers. When you upgrade the RHA engine, all existing bookmarks and rewind points are lost. For the Move IP redirection method on Linux platforms, you can configure the IP only by the ipconfig command. When you install the RHA engine on clusters using Remote Installer, you must install the Engine on both physical nodes and select a physical node instead of a cluster name. Disabled virtual switches in the Hyper-V server are listed in the network mapping dialog. If you choose to map that, then after switchover, the NIC associated with that virtual switch will not be able to connect to the network. Amazon EC2 Appliance running EC2 may sometimes show Blue Screen of Death (BSOD). Refer to this link for a workaround: Microsoft SQL Server In SQL Server scenarios, the cluster server name is changed after switchover, but the server is not rebooted even if the reboot property is set. Do not install SQL data files at the root directory of boot volumes such as C:\. During replication, the target files may fail to open on the Replica server, causing errors. Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is because: The Replica local admin account is overwritten by the Master local admin account in the Master database. The application uses Windows authentication to log into SQL Server. To avoid this problem, use SQL authentication or switch computer name redirection method. Chapter 2: Arcserve RHA r16.5 Service Pack 4 13

14 New Features and Enhancements Full System Protection For Citrix Xen scenarios, we are unable to unmount a disk on a virtual machine when files stored on the disk are in use. Depending on your Windows license type, you may need to reactivate your virtual machines after Full System Assured Recovery or switchover. Visit the Microsoft website for more information about reactivation policies. In "mixed environments" in which supported and unsupported versions of ESX are managed by a vcenter Server, full system scenarios may fail because VMDK cannot be mounted on the appliance specified. To avoid this situation, verify all versions of ESX in your environment are supported. When performing a restore process for a Full System scenario, manually stop the application services on the Master or that application may become corrupt after restore. If the application is corrupted after a restore, stop the application services, restore to the same bookmark again to solve the problem. While synchronizing a Full System scenario if you get the "Access is denied" message, then consider the following points: Use the Volume synchronization instead of the File or Block synchronization. Set engine service logon account to Local System. The error could be because the master engine service logon account is local or domain administrator. On Microsoft Windows 2012, the File Server Resource Manager feature occupies some fixed volume space. For full system scenarios, this may lead to insufficient disk space for Arcserve RHA to complete synchronization. One of the workarounds is to disable the Windows server 2012 File Server Resource Manager feature and then run FSHA. Arcserve RHA for MMC The MMC may fail to connect to the license server under these conditions: The default HTTP or HTTPS proxy is configured on the same host where the MMC is running. The address of the license server is not in the proxy bypass list. The proxy requires authentication to access the website. The Windows account does not have the required privileges to access the proxy, which means the current MMC user is not authorized to use the proxy. 14 r16.5 Release Notes

15 New Features and Enhancements To avoid this situation, do the following: Specify the Control Service server in the HTTP proxy bypass list. Remove the HTTP proxy configuration in Internet Explorer so the MMC can connect directly to the Control Service. Authorize the current user to access the HTTP proxy server. Note that the MMC connects to the Control Service with Windows Internet Configuration automatically; this setting can be changed by third-party applications. Arcserve RHA Disk Resource does not ensure data integrity across multiple volumes in a Microsoft Failover Cluster. For applications that require data integrity between data sets, all data must be hosted on a single volume. You may create Arcserve RHA Disk Resources only on the node that owns the cluster. For example, for cluster nodes A, B, C, and D where node A owns the cluster, Disk Resources can be created only on Node A. Oracle Solaris 11 Before you create a scenario with the Move IP redirection method for Solaris 11, set related NIC/IP addresses to the manual mode in Solaris. Linux For any file operations on the root directory of the master, you must either disable SeLinux or change the SeLinux security context. When the RHA master root directory is an NFS shared directory which is not written to /etc/exports but is exported by the command line exportfs -i, the NFS share will become unavailable after the scenario starts. For RHA to protect the NFS shared directory, you need to explicitly configure the NFS share directory to /etc/exports. Microsoft Windows 2003 When a Replica server is Windows 2003 and the Master server is Windows 2008 or higher, you can get the following error. This error is because Windows 2003 does not support Hard Links or Transactional NTFS (TxF) file system operations. Unable to execute event Create hard link for \\?\Volume{b8262eac-30ac-11e1-959c-000c29f6edbe}/<a-file-path> : Access is denied.(5) When you perform BMR from a Windows 2003 machine, verify that the machine supports APIC motherboard and it is enabled. Otherwise, the machine fails to boot. Chapter 2: Arcserve RHA r16.5 Service Pack 4 15

16 New Features and Enhancements Amazon Web Service (AWS) During failover to AWS, ARCserve RHA replaces HAL (hardware abstraction layer) of the master to ACPI HAL (Advanced Configuration and Power Interface HAL). For a physical machine (old hardware) or VM with no ACPI support, failback does not work. ARCserve RHA Bare Metal Recovery does not support Virtual Box virtual machines configured with SATA controllers. NAT Environment For HA cascade scenarios in a NAT environment, where CS and the non-default failover appliance hosts are not in the same sub-network. The virtual appliance cannot connect to CS when performing Manual Failover/Start VM/Stop VM/Delete all VM resources. The events are not displayed on the GUI because the appliance cannot initiate the connection to CS. You can find the detailed steps in engine logs of each host. For Hyper-V HA Scenarios When the protected VM has multiple network adapters connected to different virtual switches and you choose to customize the IP address using network mapping, the following problem may occur after switchover. The network adapters in the VM are connected to wrong virtual switches at the Hyper-V replica and the network of the VM may not work properly. To resolve this issue, manually change the virtual switch for each network adapter in the virtual machine setting using the Hyper-V Manager. Full System Scenarios For a Full System HA scenario: When the master server has two NICs (network interface controller), and the first NIC is disabled. Then after switchover, the network adapter of the newly created virtual machine fails to map to the correct NIC. For Full System scenarios: When the master server is Windows 2012 with Hyper-V role, then the virtual machine created during Assured Recovery, switchover, or the Start VM operation, fails to start. The failure to start is caused by a system exception related to winhv.sys. The workaround is to remove the Hyper-V role on the master server and synchronize again. The appliance can change to a read-only system when the scenario is synchronizing or replicating data. At this time, you should stop the scenario, delete VM resources, and resynchronize. Performance Counters on Windows 2012 On Windows 2012, the performance counters for Arcserve RHA are not displayed correctly. One of the workarounds is to copy the following files to the \windows\system r16.5 Release Notes

17 Included Fixes ibeay32.dll ssleay32.dll thl.dll trc.dll txf_wrapper.dll BMR Image Creation Failure When creating a BMR boot image fails with error code 0x , it could be because of the anti-virus software, such as McAfee. The real-time scanning functionality will block the BMR image change. In this case, you have to change the McAfee policy or use a machine without anti-virus software to create the boot image. If you are attempting to perform a BMR on a Generation 2 VM of Hyper-V2012 r2 Server, create the BMR ISO using Windows ADK 8.1. Using Windows ADK 8 or Windows AIK to create the BMR ISO causes failure to accept input or failure for the BMR to start. Microsoft Internet Explorer 11 Some Arcserve RHA web pages such as Overview Page or Report Center page are not compatible with IE 11 and may not display content properly. The workaround is to use to add the RHA Control Service to the Internet Explorer Compatibility list. For more information about the Compatibility View settings, see Microsoft documentation. Network Adapters If you have NIC teaming adapters in the original master, then the network adapters are generated but may not work properly in the BMR machine. For Linux guest virtual machines in the Hyper-V scenario, the static IP address specified in the Network Mapping dialog would not be configured correctly during switchover. Included Fixes The following list identifies the fixes included in Arcserve RHA r16.5 SP4. If you do not see a specific fix listed in this section, contact CA Support for more information. Fix Number Fix Number Fix Number Fix Number Fix Number T55U020 T5TM166 T5TM171 T5TM174 T5TM178 T55U022 T5TM168 T5TM172 T5TM175 T55U028 T55U023 T5TM170 T5TM173 T5TM176 Chapter 2: Arcserve RHA r16.5 Service Pack 4 17

18

19 Chapter 3: Arcserve RHA r16.5 Service Pack 3 This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5 Service Pack 3. This section contains the following topics: New Features and Enhancements (see page 19) Known Issues (see page 21) Included Fixes (see page 27) New Features and Enhancements Arcserve RHA r16.5 Service Pack 3 supports the following features: Integration with CA ARCserve Unified Data Protection Arcserve RHA provides integration with CA arcserve Unified Data Protection. Now you can monitor and manage High Availability functions using CA arcserve Unified Data Protection. Assured Recovery Testing Before Journals are Applied Starting with the Arcserve RHA r16.5 SP3 release, you can immediately perform Assured Recovery testing on replicas for Full System scenarios. You do not have to wait for all the journals to be applied. The Start testing when all journals are applied check box is added to the Replica Integrity Testing for Assured Recovery dialog that lets you decide whether to run Assured Recovery testing without applying all journals. Perform Switchover Before Journals are Applied Starting with the Arcserve RHA r16.5 SP3 release, you can immediately perform switchover. You do not have to wait for all the journals to be applied. The Do not wait until all journals are applied check box is added to the switchover confirmation dialog that lets you decide whether to perform switchover without applying all journals. Chapter 3: Arcserve RHA r16.5 Service Pack 3 19

20 New Features and Enhancements Enhancements Effective with Arcserve RHA SP3, RHA provides the following enhancements: File and Block Synchronization Performance: Performance of the file and block synchronization has been improved for Windows, Linux, and UNIX platforms. Additional Platform Support: Arcserve RHA now supports new platforms and versions. For a complete list, see the Compatibility Matrix CA Support. Exclude Directories for Replication and Synchronization: Effective this release, for synchronization and replication, you get an option to exclude directories in addition to files. You can exclude directories while you create a scenario or when you update an existing scenario. Default Exclusion File and Folder Filters are added for Full System Scenarios: You can modify the filters from the scenario Root Directories tab. The additional excluded files are: For Windows: tempdb.mdf templog.ldf *.stf *.IFS *.vvl *.mrg tmp.edb memory.dmp For UNIX: *vmcore.flat The additional excluded folders are: For Windows: CatalogData c:\windows\temp For UNIX: None 20 r16.5 Release Notes

21 Known Issues Known Issues The following issues are known to exist in this release: When upgrading from a previous release, running scenarios may fail to start after the upgrade process completes. This behavior occurs during the process of upgrading the Engine. The upgrade process should stop running scenarios and then restart the running scenarios after the upgrade process completes. However, the upgrade process interprets the running scenarios as having new user name and passwords (in error), which prevents the upgrade process from restarting the scenario automatically. To correct this problem, manually start the scenarios that were running before the upgrade started using Run, after the upgrade process completes. Use the Run control from the user interface. If you are unable to reset the Arcserve RHA interface back to the default after rearranging panels using the dock manager, perform the following steps: Find the running directory for the ws_gui.exe file. Close the interface. In this directory, delete the following files: dock_layout.xml, dock_layoutdefault.xml. Relaunch the interface. The interface arrangement is returned to the default layout. Rewind is not supported for applications that use TxF functionality (IIS 7.0) When remotely installing the Arcserve RHA Engine on Windows Server 2008 systems, installation fails if you log in to the Control Services as a local system. To avoid this, use a Domain Admin account to access the Control Service. Chapter 3: Arcserve RHA r16.5 Service Pack 3 21

22 Known Issues When you use the Switch Computer Name redirection method on computers running Windows Server 2008 R2, manually rejoin the Master server to the domain after failover. When a NetBIOS server name is longer than 15 characters, the Arcserve RHA Manager may fail to launch from the Overview screen if a proxy is set in Internet Options. The proxy server can only resolve DNS names, not NetBIOS names. After 72 hours, the bare metal machine will reboot automatically (applicable for full system scenarios). When you boot the bare metal machine after recovery, some drivers may be missing. Manually install these drivers. When you upgrade the RHA engine, all existing bookmarks and rewind points are lost. For the Move IP redirection method on Linux platforms, you can configure the IP only by the ipconfig command. When you install the RHA engine on clusters using Remote Installer, you must install the Engine on both physical nodes and select a physical node instead of a cluster name. Disabled virtual switches in the Hyper-V server are listed in the network mapping dialog. If you choose to map that, then after switchover, the NIC associated with that virtual switch will not be able to connect to the network. Microsoft SQL Server In SQL Server scenarios, the cluster server name is changed after switchover, but the server is not rebooted even if the reboot property is set. Do not install SQL data files at the root directory of boot volumes such as C:\. During replication, the target files may fail to open on the Replica server, causing errors. Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is because: The Replica local admin account is overwritten by the Master local admin account in the Master database. The application uses Windows authentication to log into SQL Server. To avoid this problem, use SQL authentication or switch computer name redirection method. 22 r16.5 Release Notes

23 Known Issues Full System Protection For Citrix Xen scenarios, we are unable to unmount a disk on a virtual machine when files stored on the disk are in use. Depending on your Windows license type, you may need to reactivate your virtual machines after Full System Assured Recovery or switchover. Visit the Microsoft website for more information about reactivation policies. In "mixed environments" in which supported and unsupported versions of ESX are managed by a vcenter Server, full system scenarios may fail because VMDK cannot be mounted on the appliance specified. To avoid this situation, verify all versions of ESX in your environment are supported. When performing a restore process for a Full System scenario, manually stop the application services on the Master or that application may become corrupt after restore. If the application is corrupted after a restore, stop the application services, restore to the same bookmark again to solve the problem. While synchronizing a Full System scenario if you get the "Access is denied" message, then consider the following points: Use the Volume synchronization instead of the File or Block synchronization. Set engine service logon account to Local System. The error could be because the master engine service logon account is local or domain administrator. On Microsoft Windows 2012, the File Server Resource Manager feature occupies some fixed volume space. For full system scenarios, this may lead to insufficient disk space for Arcserve RHA to complete synchronization. One of the workarounds is to disable the Windows server 2012 File Server Resource Manager feature and then run FSHA. Arcserve RHA for MMC The MMC may fail to connect to the license server under these conditions: The default HTTP or HTTPS proxy is configured on the same host where the MMC is running. The address of the license server is not in the proxy bypass list. The proxy requires authentication to access the website. The Windows account does not have the required privileges to access the proxy, which means the current MMC user is not authorized to use the proxy. Chapter 3: Arcserve RHA r16.5 Service Pack 3 23

24 Known Issues To avoid this situation, do the following: Specify the Control Service server in the HTTP proxy bypass list. Remove the HTTP proxy configuration in Internet Explorer so the MMC can connect directly to the Control Service. Authorize the current user to access the HTTP proxy server. Note that the MMC connects to the Control Service with Windows Internet Configuration automatically; this setting can be changed by third-party applications. Arcserve RHA Disk Resource does not ensure data integrity across multiple volumes in a Microsoft Failover Cluster. For applications that require data integrity between data sets, all data must be hosted on a single volume. You may create Arcserve RHA Disk Resources only on the node that owns the cluster. For example, for cluster nodes A, B, C, and D where node A owns the cluster, Disk Resources can be created only on Node A. Oracle Solaris 11 Before you create a scenario with the Move IP redirection method for Solaris 11, set related NIC/IP addresses to the manual mode in Solaris. Linux For any file operations on the root directory of the master, you must either disable SeLinux or change the SeLinux security context. When the RHA master root directory is an NFS shared directory which is not written to /etc/exports but is exported by the command line exportfs -i, the NFS share will become unavailable after the scenario starts. For RHA to protect the NFS shared directory, you need to explicitly configure the NFS share directory to /etc/exports. Microsoft Windows 2003 When a Replica server is Windows 2003 and the Master server is Windows 2008 or higher, you can get the following error. This error is because Windows 2003 does not support Hard Links or Transactional NTFS (TxF) file system operations. Unable to execute event Create hard link for \\?\Volume{b8262eac-30ac-11e1-959c-000c29f6edbe}/<a-file-path> : Access is denied.(5) When you perform BMR from a Windows 2003 machine, verify that the machine supports APIC motherboard and it is enabled. Otherwise, the machine fails to boot. 24 r16.5 Release Notes

25 Known Issues Amazon Web Service (AWS) During failover to AWS, ARCserve RHA replaces HAL (hardware abstraction layer) of the master to ACPI HAL (Advanced Configuration and Power Interface HAL). For a physical machine (old hardware) or VM with no ACPI support, failback does not work. ARCserve RHA Bare Metal Recovery does not support Virtual Box virtual machines configured with SATA controllers. NAT Environment For HA cascade scenarios in a NAT environment, where CS and the non-default failover appliance hosts are not in the same sub-network. The virtual appliance cannot connect to CS when performing Manual Failover/Start VM/Stop VM/Delete all VM resources. The events are not displayed on the GUI because the appliance cannot initiate the connection to CS. You can find the detailed steps in engine logs of each host. For Hyper-V HA Scenarios When the protected VM has multiple network adapters connected to different virtual switches and you choose to customize the IP address using network mapping, the following problem may occur after switchover. The network adapters in the VM are connected to wrong virtual switches at the Hyper-V replica and the network of the VM may not work properly. To resolve this issue, manually change the virtual switch for each network adapter in the virtual machine setting using the Hyper-V Manager. Full System Scenarios For a Full System HA scenario: When the master server has two NICs (network interface controller), and the first NIC is disabled. Then after switchover, the network adapter of the newly created virtual machine fails to map to the correct NIC. For Full System scenarios: When the master server is Windows 2012 with Hyper-V role, then the virtual machine created during Assured Recovery, switchover, or the Start VM operation, fails to start. The failure to start is caused by a system exception related to winhv.sys. The workaround is to remove the Hyper-V role on the master server and synchronize again. The appliance can change to a read-only system when the scenario is synchronizing or replicating data. At this time, you should stop the scenario, delete VM resources, and resynchronize. Performance Counters on Windows 2012 On Windows 2012, the performance counters for Arcserve RHA are not displayed correctly. One of the workarounds is to copy the following files to the \windows\system32. Chapter 3: Arcserve RHA r16.5 Service Pack 3 25

26 Known Issues ibeay32.dll ssleay32.dll thl.dll trc.dll txf_wrapper.dll BMR Image Creation Failure When creating a BMR boot image fails with error code 0x , it could be because of the anti-virus software, such as McAfee. The real-time scanning functionality will block the BMR image change. In this case, you have to change the McAfee policy or use a machine without anti-virus software to create the boot image. If you are attempting to perform a BMR on a Generation 2 VM of Hyper-V2012 r2 Server, create the BMR ISO using Windows ADK 8.1. Using Windows ADK 8 or Windows AIK to create the BMR ISO causes failure to accept input or failure for the BMR to start. Microsoft Internet Explorer 11 Some Arcserve RHA web pages such as Overview Page or Report Center page are not compatible with IE 11 and may not display content properly. The workaround is to use to add the RHA Control Service to the Internet Explorer Compatibility list. For more information about the Compatibility View settings, see Microsoft documentation. Network Adapters If you have NIC teaming adapters in the original master, then the network adapters are generated but may not work properly in the BMR machine. For Linux guest virtual machines in the Hyper-V scenario, the static IP address specified in the Network Mapping dialog would not be configured correctly during switchover. 26 r16.5 Release Notes

27 Included Fixes Included Fixes The following list identifies the fixes included in Arcserve RHA r16.5 SP3. If you do not see a specific fix listed in this section, contact CA Support for more information. Fix Number Fix Number Fix Number Fix Number Fix Number T55U001 T55U002 T55U003 T55U004 T55U005 T55U016 T5LM122 T5TM117 T5TM118 T5TM120 T5TM126 T5TM127 T5TM129 T5TM128 T5TM130 T5TM132 T5TM133 T5TM134 T5TM135 T5TM137 T5TM139 T5TM141 T5TM142 T5TM159 T5TM160 T5TM161 T5TM164 Chapter 3: Arcserve RHA r16.5 Service Pack 3 27

28

29 Chapter 4: Arcserve RHA r16.5 Service Pack 2 This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5 Service Pack 2. This section contains the following topics: New Features and Enhancements (see page 29) Known Issues (see page 30) Included Fixes (see page 36) Dropped Systems and Platforms Support (see page 36) New Features and Enhancements Arcserve RHA r16.5 Service Pack 2 supports the following features: VMware vshpere 5.5 Support Arcserve RHA now supports VMware vsphere 5.5 for Full System scenarios and also supports disks that are greater than 2 TB in size. Microsoft Hyper-V 2012 R2 Support Arcserve RHA now lets you create Hyper-V and Full System scenarios for Microsoft Hyper-V 2012 R2. UEFI (Unified Extensible Firmware Interface) servers are supported for Full System and Hyper-V scenarios. For Full System scenarios, if the master server is a UEFI server then RHA will create a Generation 2 VM for it on the Hyper-V server. Microsoft Windows 2012 R2 Support Arcserve RHA now lets you create scenarios for Microsoft Windows 2012 R2. Chapter 4: Arcserve RHA r16.5 Service Pack 2 29

30 Known Issues Known Issues The following issues are known to exist in this release: When upgrading from a previous release, running scenarios may fail to start after the upgrade process completes. This behavior occurs during the process of upgrading the Engine. The upgrade process should stop running scenarios and then restart the running scenarios after the upgrade process completes. However, the upgrade process interprets the running scenarios as having new user name and passwords (in error), which prevents the upgrade process from restarting the scenario automatically. To correct this problem, manually start the scenarios that were running before the upgrade started using Run, after the upgrade process completes. Use the Run control from the user interface. If you are unable to reset the Arcserve RHA interface back to the default after rearranging panels using the dock manager, perform the following steps: Find the running directory for the ws_gui.exe file. Close the interface. In this directory, delete the following files: dock_layout.xml, dock_layoutdefault.xml. Relaunch the interface. The interface arrangement is returned to the default layout. Rewind is not supported for applications that use TxF functionality (IIS 7.0) When remotely installing the Arcserve RHA Engine on Windows Server 2008 systems, installation fails if you log in to the Control Services as a local system. To avoid this, use a Domain Admin account to access the Control Service. 30 r16.5 Release Notes

31 Known Issues When you use the Switch Computer Name redirection method on computers running Windows Server 2008 R2, manually rejoin the Master server to the domain after failover. When a NetBIOS server name is longer than 15 characters, the Arcserve RHA Manager may fail to launch from the Overview screen if a proxy is set in Internet Options. The proxy server can only resolve DNS names, not NetBIOS names. After 72 hours, the bare metal machine will reboot automatically (applicable for full system scenarios). When you boot the bare metal machine after recovery, some drivers may be missing. Manually install these drivers. When you upgrade the RHA engine, all existing bookmarks and rewind points are lost. For the Move IP redirection method on Linux platforms, you can configure the IP only by the ipconfig command. When you install the RHA engine on clusters using Remote Installer, you must install the Engine on both physical nodes and select a physical node instead of a cluster name. Microsoft SQL Server In SQL Server scenarios, the cluster server name is changed after switchover, but the server is not rebooted even if the reboot property is set. Do not install SQL data files at the root directory of boot volumes such as C:\. During replication, the target files may fail to open on the Replica server, causing errors. Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is because: The Replica local admin account is overwritten by the Master local admin account in the Master database. The application uses Windows authentication to log into SQL Server. To avoid this problem, use SQL authentication or switch computer name redirection method. Chapter 4: Arcserve RHA r16.5 Service Pack 2 31

32 Known Issues Full System Protection For Citrix Xen scenarios, we are unable to unmount a disk on a virtual machine when files stored on the disk are in use. Depending on your Windows license type, you may need to reactivate your virtual machines after Full System Assured Recovery or switchover. Visit the Microsoft website for more information about reactivation policies. In "mixed environments" in which supported and unsupported versions of ESX are managed by a vcenter Server, full system scenarios may fail because VMDK cannot be mounted on the appliance specified. To avoid this situation, verify all versions of ESX in your environment are supported. When performing a restore process for a Full System scenario, manually stop the application services on the Master or that application may become corrupt after restore. If the application is corrupted after a restore, stop the application services, restore to the same bookmark again to solve the problem. While synchronizing a Full System scenario if you get the "Access is denied" message, then consider the following points: Use the Volume synchronization instead of the File or Block synchronization. Set engine service logon account to Local System. The error could be because the master engine service logon account is local or domain administrator. On Microsoft Windows 2012, the File Server Resource Manager feature occupies some fixed volume space. For full system scenarios, this may lead to insufficient disk space for Arcserve RHA to complete synchronization. One of the workarounds is to disable the Windows server 2012 File Server Resource Manager feature and then run FSHA. Arcserve RHA for MMC The MMC may fail to connect to the license server under these conditions: The default HTTP or HTTPS proxy is configured on the same host where the MMC is running. The address of the license server is not in the proxy bypass list. The proxy requires authentication to access the website. The Windows account does not have the required privileges to access the proxy, which means the current MMC user is not authorized to use the proxy. 32 r16.5 Release Notes

33 Known Issues To avoid this situation, do the following: Specify the Control Service server in the HTTP proxy bypass list. Remove the HTTP proxy configuration in Internet Explorer so the MMC can connect directly to the Control Service. Authorize the current user to access the HTTP proxy server. Note that the MMC connects to the Control Service with Windows Internet Configuration automatically; this setting can be changed by third-party applications. Arcserve RHA Disk Resource does not ensure data integrity across multiple volumes in a Microsoft Failover Cluster. For applications that require data integrity between data sets, all data must be hosted on a single volume. You may create Arcserve RHA Disk Resources only on the node that owns the cluster. For example, for cluster nodes A, B, C, and D where node A owns the cluster, Disk Resources can be created only on Node A. Oracle Solaris 11 Before you create a scenario with the Move IP redirection method for Solaris 11, set related NIC/IP addresses to the manual mode in Solaris. Linux For any file operations on the root directory of the master, you must either disable SeLinux or change the SeLinux security context. When the RHA master root directory is an NFS shared directory which is not written to /etc/exports but is exported by the command line exportfs -i, the NFS share will become unavailable after the scenario starts. For RHA to protect the NFS shared directory, you need to explicitly configure the NFS share directory to /etc/exports. Microsoft Windows 2003 When a Replica server is Windows 2003 and the Master server is Windows 2008 or higher, you can get the following error. This error is because Windows 2003 does not support Hard Links or Transactional NTFS (TxF) file system operations. Unable to execute event Create hard link for \\?\Volume{b8262eac-30ac-11e1-959c-000c29f6edbe}/<a-file-path> : Access is denied.(5) When you perform BMR from a Windows 2003 machine, verify that the machine supports APIC motherboard and it is enabled. Otherwise, the machine fails to boot. Chapter 4: Arcserve RHA r16.5 Service Pack 2 33

34 Known Issues Amazon Web Service (AWS) During failover to AWS, ARCserve RHA replaces HAL (hardware abstraction layer) of the master to ACPI HAL (Advanced Configuration and Power Interface HAL). For a physical machine (old hardware) or VM with no ACPI support, failback does not work. ARCserve RHA Bare Metal Recovery does not support Virtual Box virtual machines configured with SATA controllers. NAT Environment For HA cascade scenarios in a NAT environment, where CS and the non-default failover appliance hosts are not in the same sub-network. The virtual appliance cannot connect to CS when performing Manual Failover/Start VM/Stop VM/Delete all VM resources. The events are not displayed on the GUI because the appliance cannot initiate the connection to CS. You can find the detailed steps in engine logs of each host. For Hyper-V HA Scenarios When the protected VM has multiple network adapters connected to different virtual switches and you choose to customize the IP address using network mapping, the following problem may occur after switchover. The network adapters in the VM are connected to wrong virtual switches at the Hyper-V replica and the network of the VM may not work properly. To resolve this issue, manually change the virtual switch for each network adapter in the virtual machine setting using the Hyper-V Manager. Full System Scenarios For a Full System HA scenario: When the master server has two NICs (network interface controller), and the first NIC is disabled. Then after switchover, the network adapter of the newly created virtual machine fails to map to the correct NIC. For Full System scenarios: When the master server is Windows 2012 with Hyper-V role, then the virtual machine created during Assured Recovery, switchover, or the Start VM operation, fails to start. The failure to start is caused by a system exception related to winhv.sys. The workaround is to remove the Hyper-V role on the master server and synchronize again. Performance Counters on Windows 2012 On Windows 2012, the performance counters for Arcserve RHA are not displayed correctly. One of the workarounds is to copy the following files to the \windows\system32. ibeay32.dll ssleay32.dll 34 r16.5 Release Notes

35 Known Issues thl.dll trc.dll txf_wrapper.dll BMR Image Creation Failure When creating a BMR boot image fails with error code 0x , it could be because of the anti-virus software, such as McAfee. The real-time scanning functionality will block the BMR image change. In this case, you have to change the McAfee policy or use a machine without anti-virus software to create the boot image. If you are attempting to perform a BMR on a Generation 2 VM of Hyper-V2012 r2 Server, create the BMR ISO using Windows ADK 8.1. Using Windows ADK 8 or Windows AIK to create the BMR ISO causes failure to accept input or failure for the BMR to start. Microsoft Internet Explorer 11 Some Arcserve RHA web pages such as Overview Page or Report Center page are not compatible with IE 11 and may not display content properly. The workaround is to use to add the RHA Control Service to the Internet Explorer Compatibility list. For more information about the Compatibility View settings, see Microsoft documentation. Network Adapters If you have NIC teaming adapters in the original master, then the network adapters are generated but may not work properly in the BMR machine. For Linux guest virtual machines in the Hyper-V scenario, the static IP address specified in the Network Mapping dialog would not be configured correctly during switchover. Chapter 4: Arcserve RHA r16.5 Service Pack 2 35

36 Included Fixes Included Fixes The following list identifies the fixes included in Arcserve RHA r16.5 SP2. If you do not see a specific fix listed in this section, please contact CA Support for more information. Fix Number T5TM158 T5TM157 T5TM156 T5TM155 T5TM154 T5TM153 T5TM152 T5TM151 T5TM150 T5TM149 T5TM148 T5TM147 T55U014 T55U013 Fix Number T55U006 T55U007 T55U008 T55U011 T55U017 T5TM131 T5TM136 T5TM138 T5TM140 T5TM143 T5TM146 Dropped Systems and Platforms Support Arcserve RHA r16.5 SP2 no longer supports the following systems and platforms: VMware vsphere 4.x as a hypervisor Microsoft Internet Explorer 6 and 7 36 r16.5 Release Notes

37 Chapter 5: Arcserve RHA r16.5 Service Pack 1 This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5 Service Pack 1. This section contains the following topics: New Features and Enhancements (see page 37) Enhancements (see page 38) Known Issues (see page 38) Included Fixes (see page 39) Dropped Systems and Platforms Support (see page 39) New Features and Enhancements Arcserve RHA r16.5 Service Pack 1 supports the following features: Microsoft Exchange Server 2013 Support Arcserve RHA now lets you create scenarios to protect Microsoft Exchange server Select Microsoft Exchange Server while creating scenarios to protect your Microsoft Exchange Server Microsoft SharePoint Server 2013 Support Arcserve RHA now lets you protect Microsoft SharePoint Server 2013 using the Full System scenario. Select Full System while creating scenarios to protect your Microsoft SharePoint Server Arcserve RHA supports both the standalone and farm deployment. Microsoft SharePoint Foundation 2010 Support Arcserve RHA now lets you protect Microsoft SharePoint Foundation 2010 using the SharePoint server. Select Microsoft SharePoint Server while creating scenarios to protect your Microsoft SharePoint Foundation Arcserve RHA supports both the standalone and farm deployment. Chapter 5: Arcserve RHA r16.5 Service Pack 1 37