Arcserve Replication and High Availability. r16.5 Release Notes

(1)

r16.5 Release Notes

Arcserve® Replication and High

Availability

(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 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

(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 [email protected].

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 http://ca.com/docs.

(4)

(5)

Contents 5

Chapter 1: Welcome

9 Chapter 2: Arcserve RHA r16.5 Service Pack 4

11

New Features and Enhancements... 11

Enhancements ... 11

Known Issues ... 12

Included Fixes ... 17

Chapter 3: Arcserve RHA r16.5 Service Pack 3

19

Integration with CA ARCserve Unified Data Protection ... 19

Assured Recovery Testing Before Journals are Applied ... 19

Perform Switchover Before Journals are Applied ... 19

Enhancements ... 20

Known Issues ... 21

Chapter 4: Arcserve RHA r16.5 Service Pack 2

29

VMware vShpere 5.5 Support ... 29

Microsoft Hyper-V 2012 R2 Support ... 29

Microsoft Windows 2012 R2 Support ... 29

Known Issues ... 30

Dropped Systems and Platforms Support ... 36

Chapter 5: Arcserve RHA r16.5 Service Pack 1

37

Microsoft Exchange Server 2013 Support ... 37

Microsoft SharePoint Server 2013 Support ... 37

Microsoft SharePoint Foundation 2010 Support ... 37

Network Traffic Redirection Supports Computer Alias ... 38

Enhancements ... 38

Known Issues ... 38

(6)

6 r16.5 Release Notes

Chapter 6: Arcserve RHA r16.5

41

CA ARCserve Central Host-Based VM Backup Support ... 41

Microsoft Windows Server 2012 Support ... 41

Full System Cascade Scenario to Add Multiple Replicas ... 42

MS SQL FILESTREAM BLOB Data Support ... 42

Enhancements ... 43

Known Issues ... 46

Chapter 7: Arcserve RHA r16 Service Pack 2

51

Restore Support to a Bare Metal Machine ... 51

NAT Support ... 52

Enhancements ... 53

Known Issues ... 56

Chapter 8: Arcserve RHA r16 Service Pack 1

59

Proxy Server Support ... 59

CA ARCserve D2D Support ... 59

Chapter 9: Arcserve RHA r16

61 Chapter 10: New Features and Enhancements

63

Change Scenario While Running ... 63

Cloud Support ... 64

Enhanced Cluster Support ... 64

Secure Communication ... 64

Virtualization Enhancements ... 65

(7)

Contents 7

Chapter 11: Known Issues

67 Chapter 12: System Information

71

Minimum Hardware Requirements ... 71

Supported Configurations: Windows ... 71

Supported Configurations: UNIX/Linux ... 77

Supported Virtual Platforms ... 78

Installation Considerations ... 78

Chapter 13: Localized Versions

81 Appendix A: Acknowledgements

83

(8)

(9)

Chapter 1: Welcome 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.

(10)

(11)

Chapter 2: Arcserve RHA r16.5 Service Pack 4 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:

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

(13)

Chapter 2: Arcserve RHA r16.5 Service Pack 4 13 ■ 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: http://support.citrix.com/article/CTX130768.

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.

(14)

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.

(15)

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}

(16)

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

(17)

Chapter 2: Arcserve RHA r16.5 Service Pack 4 17 ■ 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 0x80070005, 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 T55U022 T55U023 T5TM166 T5TM168 T5TM170 T5TM171 T5TM172 T5TM173 T5TM174 T5TM175 T5TM176 T5TM178 T55U028

(18)

(19)

Chapter 3: Arcserve RHA r16.5 Service Pack

3

Known Issues (see page 21)

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.

(20)

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:

(21)

Known Issues

■ _{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.

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

■ _{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.

■ 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:

(23)

(24)

Known Issues

Linux

(25)

NAT Environment

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

(26)

Known Issues

■ ibeay32.dll

■ ssleay32.dll

■ thl.dll

■ trc.dll

■ txf_wrapper.dll

(27)

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

(28)

(29)

Chapter 4: Arcserve RHA r16.5 Service Pack

2

Dropped Systems and Platforms Support (see page 36)

New Features and Enhancements

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

(30)

Known Issues

■ _{Rewind is not supported for applications that use TxF functionality (IIS 7.0)} ■ When remotely installing the Arcserve RHA Engine on Windows Server 2008

(31)

Chapter 4: Arcserve RHA r16.5 Service Pack 2 31 ■ When you use the Switch Computer Name redirection method on computers

■ _{Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is}

because:

(32)

Known Issues

(33)

Linux

(34)

Known Issues

NAT Environment

\windows\system32.

■ ibeay32.dll

(35)

Chapter 4: Arcserve RHA r16.5 Service Pack 2 35 ■ thl.dll

■ trc.dll

■ txf_wrapper.dll

(36)

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 Fix Number

T5TM158 T5TM157 T5TM156 T5TM155 T5TM154 T5TM153 T5TM152 T5TM151 T5TM150 T5TM149 T5TM148 T5TM147 T55U014 T55U013

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

(37)

Chapter 5: Arcserve RHA r16.5 Service Pack

1

Enhancements (see page 38)

New Features and Enhancements

Microsoft Exchange Server 2013 Support

Arcserve RHA now lets you create scenarios to protect Microsoft Exchange server 2013. Select Microsoft Exchange Server while creating scenarios to protect your Microsoft Exchange Server 2013.

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 2013. 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 2010. Arcserve RHA supports both the standalone and farm deployment.

(38)

Enhancements

Network Traffic Redirection Supports Computer Alias

Arcserve RHA now supports alias names for failover. When you have multiple alias names, you can select either a few or all alias names for switchover. Both NetBIOS and DNS CNAME alias names are supported. To add NetBIOS alias names, create a

Multi-String value named OptionalNames with Data as <aliasnames> in the following registry key and restart the Server service.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters

You can specify alias name details in the Network Traffic Redirection section of the High Availability Properties.

Enhancements

Effective with Arcserve RHA r16.5 SP1 release, replication and data rewind performance on replicas has significantly improved.

Known Issues

■ _{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.

■ _{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

■ thl.dll

■ trc.dll

(39)

Included Fixes

The following list identifies the fixes included in Arcserve RHA r16.5 SP1. If you do not see a specific fix listed in this section, please contact CA Support for more information.

Fix Number Fix Number Fix Number Fix Number Fix Number Fix Number

T5LF187 T5LF188 T5LF189 T5LF190 T5LF191 T5LF192 T5LF193 T5LF194 T5LF195 T5LF196 T5LF197 T5LF198 T5LF199 T5LF200 T5LF201 T5LF202 T5LF203 T5LF204 T5LF205 T5LF206 T5LF207 T5LF208 T5LF210 T5LF211 T5LF212 T5LF213 T5LF214 T5LF215 T5TM092 T5TM094 T5TM095 T5TM096 T5TM097 T5TM098 T5TM099 T5TM101 T5TM102 T5TM104 T5TM105 T5TM106 T5TM107 T5TM108 T5TM109 T5TM110 T5TM111 T5TM112 T5Tm113 T5TM114 T5TM115 T5TM116 T5TM119 T5TM123 T5TM124 T5TM125 T5LE129

Dropped Systems and Platforms Support

Arcserve RHA r16.5 SP1 no longer supports SUSE Linux Enterprise Server 9 and Red Hat Enterprise Linux 4.

(40)

(41)

Chapter 6: Arcserve RHA r16.5 41

Chapter 6: Arcserve RHA r16.5

This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5

New Features and Enhancements

Arcserve RHA r16.5 supports the following features:

CA ARCserve Central Host-Based VM Backup Support

Arcserve RHA provides native support for CA ARCserve Central Host-Based VM Backup with a new server type selection. Arcserve RHA connects to the Central Host-Based VM Backup server to get the policy and related backup destination hosts with corresponding virtual machines. You can select the backup host and its virtual machines. This replicates the backup files (created by CA ARCserve D2D) of those virtual machines.

Microsoft Windows Server 2012 Support

Effective this release, Arcserve RHA supports Microsoft Windows Server 2012. You can install the RHA Control Service and the Engine on the Windows Server 2012 and create scenarios.

The following features are supported:

Storage Spaces

Data Deduplication

4KB logical sector size

(42)

Full System Cascade Scenario to Add Multiple Replicas

Effective this release, you can create a Full System cascade scenario to add multiple Replica servers at different levels. You can create any topology for a Full System scenario to make it flexible even if the appliance hosts are at different virtual platforms. Each appliance host has its own virtual platform and virtual machine settings and you can specify these settings separately. You can also perform various operations such as AR testing, Start/Stop VMs, Delete VM resources for each appliance host and related virtual platform. For manual switchover, you can choose which replica to be switched over to.

MS SQL FILESTREAM BLOB Data Support

Effective this release, you can protect MS SQL BLOB data. When the master server has MS SQL server enabled FILESTREAMS, the RHA engine discovers and replicates all BLOB data. The engine discovers and replicates even if the BOLB data is stored in locations other than the database files. The root directory also adjusts automatically according to the BLOB data path.

(43)

Chapter 6: Arcserve RHA r16.5 43

Enhancements

Effective with r16.5 release, Arcserve RHA provides the following enhancements:

■ _{Microsoft Hyper-V 3.0 Support for Full System Scenarios:}_{Full system scenario}

supports MS Hyper-V 3.0. You can now select Hyper-V 3.0 as virtual platform.

■ Unified Extensible Firmware Interface (UEFI) Firmware Support: Full system scenario supports server with UEFI firmware as the master server. Make sure that the virtual platform also supports the UEFI firmware.

■ Dynamic Disk support for Full System Scenarios: Dynamic disks such as simple, spanned, striped, mirrored, and RAID-5 volumes are supported. The dynamic disks include both MBR and GPT partition types. Both the master and replica support dynamic disks.

■ _{4K Sector Size Hard Disk Support for Full System Scenarios:}_{Full System scenarios}

support 4K sector size hard disk. RHA supports 4K sector size hard disk on the following operating systems.

■ Windows Server 2008

■ Windows Server 2008 R2

■ Windows Server 2012

■ Preserve the Destination Volume Layout for Full System BMR Scenarios: To keep the current volume on the bare metal machine (destination machine), an option, "Preserve Existing Volumes on Destination", is included while creating a scenario for bare metal machines.

■ _{Modify VM Settings Dynamically:}_{You can now dynamically modify VM settings for}

Full System scenarios while the scenario is running. The settings include, CPU cores, Memory size, Virtual Machine name, Assured Recovery Network Adapter Mappings, Physical Network Mappings, and EC2 Instance Type.

■ _{Oracle Multiple Instance Support:}_{You can protect multiple Oracle DB instances}

that are installed on the same Windows host. RHA engine now monitors all the services for each oracle database instance. You can now select multiple instances on the "Select Oracle Instances for Replication" screen while creating a scenario. RHA also lets you specify "sys as sysdba" to log in to the database.

■ _{Multiple Mount Point Support in the RHA Root Directories on Linux:}_{The XOFS}

driver can now be mounted to the sub mount points in the root RHA directories on Linux. This feature is applicable to the following Linux versions:

■ Red Hat Enterprise Linux

■ SUSE Linux Enterprise Server

■ CentOs Linux

(44)

This feature lets RHA protect multiple file systems mounted on the same RHA root directory. Now when a scenario runs, RHA mounts XOFS on the specified RHA root directory. In addition, RHA scans whether there are sub mount points in the RHA root directory and automatically mounts XOFS driver on each sub mount point.

■ Additional Region Support for Amazon EC2: Now you can create a full system HA or replication scenario with an EC2 replica for the following five regions.

■ Asia Pacific (Sydney)

■ Asia Pacific (Tokyo)

■ EU West (Ireland)

■ South America (Sao Paulo)

■ US East (Virginia)

■ _{Microsoft Hyper-V Scenario Supports Failover over a WAN:}_{Hyper-V scenarios can}

failover over a WAN, you can change the virtual machine IP address when

performing switchover/failover. You can also set network adapters using the GUI.

■ _{Full System Scenario Template with Predefined Replica Details}_{: The Full System}

scenario template is enhanced to let you include replica details while creating the template. This created template has the predefined replica details that you can use multiple times to create scenarios. When you create the scenario, just specify the master server details and reuse the predefined replica details.

■ Include Newly Created Virtual Machine Option for the Central Host-Based VM Backup Scenarios: This option lets you replicate all sub folders in the main host backup folder when you run the scenario. Any newly created VM backup folders are also replicated. Only the folders of the unchecked virtual machines are excluded. Those folders are marked as excluded folders. If you do not select this option, only the selected backup folders are replicated.

■ Improved Scenario Authentication and Multitenancy Support: The scenario authentication is improved and is more secure. This allows you to have a very secure multitenancy replication. ARCserve RHA verifies the following conditions at the beginning and stops the scenario when these conditions fail.

1. Scenario level credentials for each host.

2. Host level credentials for each host. The host level credentials override scenario level credentials. If the host level credential is blank or is not set, then RHA automatically uses scenario level credentials.

3. User has Full Control Permission to the specified parent folder.

Encrypt Data During Transfer: This Replica property is enhanced and you have these four options: No encryption, AES-128, AES-256, and User Configured.

■ _{Current User option in the Remote Installer Wizard:}_{The Current User option is}

added to let you set the Service Logon Information to the current user. This option lets you log on to the CS (Control Service) using the current account you logged in with.

(45)

Chapter 6: Arcserve RHA r16.5 45 ■ Reports as Email Attachments: You can receive all Arcserve RHA reports in the

HTML format as email attachments.

■ _{SMTP Authentication Support:}_{The following three SMTP authentications are}

supported for event notifications and reports. You can set mail server, submission port, user credential, and proxy settings.

■ LOGIN

■ PLAIN

■ CRAM-MD5

■ _{Integration Scenarios:}_{The file server scenarios with ARCserve D2D and Central}

Host-Based VM Backup integration are now two separate scenario types. You can see ARCserve D2D and ARCserve Central Host-Based VM Backup scenario types on the Select Server and Product Type screen while creating a scenario.

Included Fixes

The following list identifies the fixes included in Arcserve RHA r16.5. If you do not see a specific fix listed in this section, please contact CA Support for more information.

Fix Number Fix Number Fix Number

Fix Number Fix Number

Fix Number Fix Number T5LE104 T5LE105 T5LE108 T5LE110 T5LE111 T5LE114 T5LE115 T5LE116 T5LE117 T5LF137 T5LF142 T5LF143 T5LF144 T5LF145 T5LF147 T5LF148 T5LF149 T5LF150 T5LF152 T5LF153 T5LF154 T5LF155 T5LF156 T5LF157 T5LF158 T5LF159 T5LF160 T5LF161 T5LF162 T5LF164 T5LF166 T5LF167 T5LF168 T5LF169 T5LF170 T5LF171 T5LF172 T5LF173 T5LF174 T5LF175 T5LF178 T5LF179 T5LF182 T5LF183 T5LF184 T5LF186 T5TM072 T5TM074 T5TM075 T5TM076 T5TM078 T5TM079 T5TM080 T5TM082 T5TM083 T5TM084 T5TM085 T5TM086 T5TM088 T5TM089 T5TM092 T5TM095

(46)

Known Issues

■ _{When upgrading from a previous release, running scenarios may fail to start after}

the upgrade process completes. This behavior occurs during the process of

■ _{Rewind is not supported for applications that use TxF functionality (IIS 7.0)} ■ _{When remotely installing the Arcserve RHA Engine on Windows Server 2008}

(47)

Chapter 6: Arcserve RHA r16.5 47 ■ When you use the Switch Computer Name redirection method on computers

■ _{Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is}

because: