arcserve® replication and high availability · when you upgrade the rha engine, all existing...

r16.5 Release Notes

Arcserve® Replication and High

Availability

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 Arcserve 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 Arcserve. This Documentation is confidential and proprietary information of Arcserve 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 Arcserve governing your use of the Arcserve software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and Arcserve.

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 Arcserve 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 Arcserve that all copies and partial copies of the Documentation have been returned to Arcserve or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, ARCSERVE 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 ARCSERVE 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 ARCSERVE 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 Arcserve.

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.

© 2015 Arcserve, including its affiliates and subsidiaries. All rights reserved. Any third party trademarks or copyrights are the property of their respective owners.

Arcserve Product References

This document references the following Arcserve products:

■ Arcserve® Replication

■ Arcserve® High Availability (HA)

■ Arcserve® Assured Recovery®

■ Arcserve® Content Distribution

Contact Arcserve

The Arcserve Support team offers a rich set of resources for resolving your technical issues and provides easy access to important product information.

https://www.arcserve.com/support

With Arcserve Support:

■ You can get in direct touch with the same library of information that is shared internally by our Arcserve Support experts. This site provides you with access to our knowledge-base (KB) documents. From here you easily search for and find the product-related KB articles which contain field-tested solutions for many top issues and common problems.

■ You can use our Live Chat link to instantly launch a real-time conversation between you and the Arcserve Support team. With Live Chat, you can get immediate answers to your concerns and questions, while still maintaining access to the product.

■ You can participate in the Arcserve Global User Community to ask and answer questions, share tips and tricks, discuss best practices and participate in conversations with your peers.

■ You can open a support ticket. By opening a support ticket online, you can expect a callback from one of our experts in the product area you are inquiring about.

You can access other helpful resources appropriate for your Arcserve product.

https://arcserve.zendesk.com/hc/en-us

Contents 5

Contents

Chapter 1: Welcome 9

Chapter 2: Arcserve RHA r16.5 Service Pack 5 11

New Features and Enhancements .............................................................................................................................. 12

Enhancements ..................................................................................................................................................... 12

Known Issues .............................................................................................................................................................. 13

Included Fixes ............................................................................................................................................................. 19



Enhancements ..................................................................................................................................................... 23

Known Issues ....................................................................................................................................................... 24

Included Fixes ............................................................................................................................................................. 29



Integration with Arcserve Unified Data Protection ............................................................................................. 31

Assured Recovery Testing Before Journals are Applied ...................................................................................... 31

Perform Switchover Before Journals are Applied ............................................................................................... 31

Enhancements ..................................................................................................................................................... 32

Known Issues .............................................................................................................................................................. 33

Included Fixes ............................................................................................................................................................. 39



VMware vShpere 5.5 Support ............................................................................................................................. 41

Microsoft Hyper-V 2012 R2 Support ................................................................................................................... 41

Microsoft Windows 2012 R2 Support ................................................................................................................. 41

Known Issues .............................................................................................................................................................. 42

Included Fixes ............................................................................................................................................................. 48

Dropped Systems and Platforms Support .................................................................................................................. 48



6 r16.5 Release Notes

Microsoft Exchange Server 2013 Support ........................................................................................................... 49

Microsoft SharePoint Server 2013 Support ........................................................................................................ 49

Microsoft SharePoint Foundation 2010 Support ................................................................................................ 49

Network Traffic Redirection Supports Computer Alias ....................................................................................... 50

Enhancements ............................................................................................................................................................ 50

Known Issues .............................................................................................................................................................. 50

Included Fixes ............................................................................................................................................................. 51


Chapter 7: Arcserve RHA r16.5 53


Arcserve Central Host-Based VM Backup Support .............................................................................................. 53

Microsoft Windows Server 2012 Support ........................................................................................................... 53

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

MS SQL FILESTREAM BLOB Data Support ............................................................................................................ 54

Enhancements ..................................................................................................................................................... 55

Included Fixes ............................................................................................................................................................. 57

Known Issues .............................................................................................................................................................. 58


Chapter 8: Arcserve RHA r16 Service Pack 2 63


Restore Support to a Bare Metal Machine ......................................................................................................... 63

NAT Support ........................................................................................................................................................ 64

Enhancements ..................................................................................................................................................... 65

Included Fixes ............................................................................................................................................................. 67

Known Issues .............................................................................................................................................................. 68



Proxy Server Support .......................................................................................................................................... 71

Arcserve D2D Support ......................................................................................................................................... 71

Included Fixes ............................................................................................................................................................. 72

Chapter 10: Arcserve RHA r16 73

Chapter 11: New Features and Enhancements 75

Change Scenario While Running ......................................................................................................................... 75

Cloud Support ..................................................................................................................................................... 76

Contents 7

Enhanced Cluster Support ................................................................................................................................... 76

Secure Communication ....................................................................................................................................... 76

Virtualization Enhancements .............................................................................................................................. 77

Features No Longer Supported ........................................................................................................................... 77

Chapter 12: Known Issues 79

Chapter 13: System Information 83

Minimum Hardware Requirements ........................................................................................................................... 83

Supported Configurations: Windows ......................................................................................................................... 83

Supported Configurations: UNIX/Linux ...................................................................................................................... 89

Supported Virtual Platforms ...................................................................................................................................... 90

Installation Considerations ......................................................................................................................................... 90

Chapter 14: Localized Versions 93

Appendix A: Acknowledgements 95

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

Throughout this document, the term "Arcserve RHA" refers to all products, unless otherwise specified.


Chapter 2: Arcserve RHA r16.5 Service Pack 5

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

This section contains the following topics:

New Features and Enhancements (see page 12) Known Issues (see page 13) Included Fixes (see page 19)

New Features and Enhancements



Enhancements

Effective with Arcserve RHA Service Pack 5, RHA provides the following enhancements:

For Amazon EC2

■ Select the general purpose (SSD) volumes and provisioned IOPS (SSD) volumes as the EBS types rather than magnetic volumes.

Note: For more information on the EBS types, refer the following link:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html#EBSVolumeTypes_piops

■ When using Amazon EC2 as a target for full system HA scenarios, you can configure the following connection protocol - SSLv2, SSLv3, TLSv1, TLSv1.1 or TLSv1.2. The data is safe with an industry standard secure transfer protocol of your choice.

■ The encryption could be enable for Amazon EBS volumes and snapshots.

Notes:

■ Only the non-system volumes can be encrypted.

■ The encryption cannot be enabled for the volumes on a 32-bit OS.

■ For more information on the the supported EC2 instance types for which the encryption is available, refer the following link: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html

Other Enhancements

■ Upgraded OpenSSL binaries from OpenSSL 1.0.1i to OpenSSL 1.0.1p

■ Supports VMware vSphere 6.0

■ Supports configuration of virtual machine network adapters such as vmxnet 2, vmxnet3, E1000E, and E1000 for physical to virtual conversion on VMware vCenter/ESXi

■ Supports RHEL 6.6 and CentOS 6.6

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.

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.

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.

http://support.citrix.com/article/CTX130768

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.

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.

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.

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.

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

AIX and Solaris

If you are using Solaris and AIX, you have to continue using SP4, but you can manage these engines using the SP5 control service.

Included Fixes


Included Fixes

The following list identifies the fixes included in Arcserve RHA r16.5 SP5. The problem description is provided for each fix. If you do not see a specific fix listed in this section, contact Arcserve Support for more information.

■ T55U031

Arcserve RHA does not copy the Windows access control list (ACL). The access denied error is displayed after providing the security information.

■ T55U034

Unable to use the dnscmd method to update the DNS record.

■ T5TM180

Raw journals are not sent and journals files are not deleted from the following folder:

\XOMF\collector1

■ T5TM181

Permission denied while authenticating an engine for a large group with maximum users. The fix is applicable for SUSE Linux only.

■ T5TM182

A SQL server file stream is not included in an auto-discovery result and the file stream is not replicated afterwards.

■ T5TM183

The Replica engine crashes during a full system scenario for Windows.

■ T5TM184

CentOS Master server crashes.

Included Fixes


■ T5TM187

The following error is displayed when creating a snapshot for a replica VM during HA to EC2 cloud scenario: ER02100 SignatureDoesNotMatch

■ T5TM188

Kernel panic on Solaris SPARC 11

■ T5TM190

Master server panic when XOFS is unloaded. The fix is applicable for RHEL only.

■ T5TM192

The mv command fails on Solaris SPARC 11.1 After XOFS is mounted, the Bad Address error is displayed.

■ T5TM193

Master server panic while umounting XOFS.

■ T5TM195

After a failover, when the master server boots, users are unable to stop the customapp services. The following message is displayed:

Unable to Stop CustomApp Services. OpenSCManager Failed. A System Shutdown in

progress.

After a failover, when the master server boots, the master IP is not released.

■ T5TM196



progress.


■ T5TM199



progress.


■ T5TM203

A master server, which has Arcserve Unified Data Protection Agent for Linux installed, crashes when stopping a scenario. The fix is applicable for RHEL only.

Included Fixes


■ T5TM217

After a synchronization job, the archive bit is cleared on a master server but it is still set on a replica server.

■ T5TM218

Arcserve RHA takes a longer time to verify whether the engine account is a domain administrator account and the scenario fails to start.

■ T5TM219

The replica root directory is hidden during a synchronization job.

■ T5TM220

The replica root directory is hidden during a synchronization job.

■ T5TM221

When copying files to a mapped volume using the command line, the replica folder gets created without any content.

■ T5TM222

RHEL 6.6 support

■ T5TM223

The replica database data is getting corrupted when performing a block synchronization for a SQL server scenario.

■ T5TM224

After an upgrade, the network mapping dialog does not open.

■ T5TM225

ADS does not get copied to a replica server after performing a block synchronization.

■ T5TM226

Unable to connect to the EC2 cloud using a proxy server. The following error message is displayed:

Unable to connect to Amazon EC2. Please check the network configuration.

Included Fixes


■ T5TM227

FTP bindings are not getting replicated to the replica server in a IIS scenario.

■ T5TM228

When an incorrect account is used to log in to the Arcserve RHA portal, the system displays an audit fail event after every 10 seconds, even after closing the browser.

■ T5TM229

When an incorrect account is used to log in to the Arcserve RHA portal, the system displays an audit fail event after every 10 seconds, even after closing the browser.

■ T5TM230

Failed to get a virtual network list for creating a Full System HA scenario to EC2.

■ T5TM231

An incorrect registry path on the replica server while performing a registry replication.





New Features and Enhancements (see page 23) Included Fixes (see page 29)


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: http://aws.amazon.com/ec2/instance-types/.

http://aws.amazon.com/ec2/instance-types/



■ 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






















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.








http://support.citrix.com/article/CTX130768










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







denied.(5)







NAT Environment












Included Fixes


■ ibeay32.dll

■ ssleay32.dll

■ thl.dll

■ trc.dll

■ txf_wrapper.dll






Network Adapters



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





New Features and Enhancements (see page 31) Known Issues (see page 33) Included Fixes (see page 39)


Arcserve RHA r16.5 Service Pack 3 supports the following features:

Integration with Arcserve Unified Data Protection

Arcserve RHA provides integration with Arcserve Unified Data Protection.

Now you can monitor and manage High Availability functions using 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.



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

Known Issues


Known Issues












Known Issues

















Known Issues









Oracle Solaris 11


Linux







denied.(5)


Known Issues





NAT Environment












Known Issues


■ ibeay32.dll

■ ssleay32.dll

■ thl.dll

■ trc.dll

■ txf_wrapper.dll






Network Adapters



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





New Features and Enhancements (see page 41) Known Issues (see page 42) Included Fixes (see page 48) Dropped Systems and Platforms Support (see page 48)



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.

Known Issues


Known Issues












Known Issues
















Known Issues









Oracle Solaris 11


Linux







denied.(5)


Known Issues





NAT Environment











■ ibeay32.dll

■ ssleay32.dll

Known Issues


■ thl.dll

■ trc.dll

■ txf_wrapper.dll






Network Adapters



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





New Features and Enhancements (see page 49) Enhancements (see page 50) Known Issues (see page 50) Included Fixes (see page 51) Dropped Systems and Platforms Support (see page 51)



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.

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





■ ibeay32.dll

■ ssleay32.dll

■ thl.dll

■ trc.dll

■ txf_wrapper.dll

Included Fixes


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


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


Chapter 7: Arcserve RHA r16.5

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


New Features and Enhancements (see page 53) Included Fixes (see page 57) Known Issues (see page 58) Dropped Systems and Platforms Support (see page 62)


Arcserve RHA r16.5 supports the following features:

Arcserve Central Host-Based VM Backup Support

Arcserve RHA provides native support for 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 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

ReFS (Resilient File System)



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.



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

■ Oracle Linux



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.

Included Fixes


■ 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 Arcserve Support for more information.

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

Known Issues


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










Known Issues
















Known Issues









Oracle Solaris 11


Linux


■ When the RHA master root directory is a NFS shared directory which isn't 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.





denied.(5)







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






Arcserve RHA r16.5 no longer supports Windows Server 2003, 2003 R2, or 2008 as Virtual Appliance for Full System scenarios.

Upgrade Considerations: If you cannot have a virtual appliance running Windows 2008 Server R2 or Windows Server 2012, you can continue using Arcserve RHA r16 SP2 for both the RHA engines and the RHA Control Service. Otherwise, the r16.5 RHA Manager prevents starting the existing Full System scenario.

Note: Arcserve RHA r16.5 Full System scenarios continue to protect Windows Servers 2003, 2003 R2, and 2008, that is, as master servers.


Chapter 8: Arcserve RHA r16 Service Pack 2

This section describes new features, enhancements, and included fixes in Arcserve RHA r16 Service Pack 2.

Note: This Service Pack does not support upgrade from r16.5 alpha.


New Features and Enhancements (see page 63) Included Fixes (see page 67) Known Issues (see page 68)


Arcserve RHA r16 Service Pack 2 supports the following features:

Restore Support to a Bare Metal Machine

Effective with this release, Arcserve RHA supports restoring data to a bare metal machine. You can restore to a bare metal machine (physical or virtual) either from a live system that has performed a failover/switchover or from a bookmark rewind point. This feature not only restores data but also builds the bare metal machine by installing the operating system, applications, and other necessary components.

A bare metal recovery provides the following benefits:

■ Builds a machine exactly similar to the Master before restoring data

■ Recovers data even to a dissimilar hardware

■ Recovers data on a volume level



NAT Support

Effective with this release, you can deploy Arcserve RHA in a NAT (Network Address Translation) environment. This feature lets you have an RHA setup where host servers are behind a NAT device or a firewall. For example, you can have a setup where the Master is behind a NAT device whereas the Control Service and Replica are on a public domain.

To use this feature, Arcserve RHA provides the RHA NAT utility. You configure the RHA NAT utility on the host that is behind the NAT device.

The RHA NAT feature supports replication, restore, failover, and scenario management.



Enhancements

Effective with this release, Arcserve RHA provides the following enhancements:

■ Volume Snapshot Management Support: The volume snapshot has been simplified and you can set volume snapshots at one place. In addition, you can specify whether you want to have a snapshot while creating a bookmark. A check box is available for this option while creating a bookmark.

■ Advanced Bandwidth and I/O Throttling: The bandwidth scheduler is enhanced to configure hourly bandwidth settings for the entire week. For example, you can set 256 KB for Monday, 9:00 AM or 192 KB for Wednesday, 4:00 PM.

■ Recover Active Server: Now Full System scenarios support the Recover Active Server function. You can use this function to simulate switchover or switchback.

■ Start/Stop Virtual Machine: A new option on the Tools menu has been added to stop or start a virtual machine. This option is applicable for a Data Recovery or High Availability full system scenarios.

■ Delete All VM Resources: A new option on the Tools menu has been added to delete temporary VM resources. This operation lets you delete temporary resources such as disk files, snapshots, and other temporary files.

■ VMware Distributed Virtual Switch: Support for the VMware Distributed Virtual switch has been added for full system scenarios. You can select the vSphere Distributed Virtual Switch during network mapping.

■ Proxy Support for Control Service: HTTP proxy support for RHA Control Service has been added. This service lets the Control Service connect to the RHA engine hosts using HTTP proxy servers.

■ Data Rewind Performance: The rewind point query function is restructured and the user interface has been redesigned. You can quickly search event points during rewind. The response time is fast even when there are up to million events.

■ Scheduled Bookmark: A new property, Enable Scheduled Bookmark, has been added to let you create a bookmark schedule for DB scenarios such as MSSQL and Exchange scenarios.

■ CAVSSSoftProv Service: The CAVSSSoftProv service is no longer required.

■ Log Collection Utility: A log collection utility has been added. This utility can automatically retrieve Master, Replica, and Control Service logs along with event logs from the Master and Replica.

■ Create Application Consistent Snapshot: This feature lets RHA engine call application VSS writers, such as the Exchange VSS writer and MSSQL VSS writer, to create application consistent snapshots. The snapshots are created on the master during the bookmark creation process.

■ Keep the Archive Attribute on the Replica: A new property added to the Replication properties. If set to on, it retains the archive attribute on the replica during synchronization if master and replica files are identical.



■ Retain Local Account Name: A new property added to the Replication properties to retain the local name in the replica machine. Before you run a scenario, manually create the same local users or groups in both Master and Replica. Use this property for workgroup environments. This property is only applicable to Windows machines.

■ DNS Redirection using the Update DNS Tool: Use this tool to change the DNS A record of the master server to resolve to the IP address of the replica. You use this tool after you start or stop the VM using the Start/Stop VM feature. You can use this tool by running the update_dns.exe file in the RHA engine installation folder.

■ Offline Synchronization Support for Full System Scenarios: The offline synchronization is now extended to full system scenarios including forward, backward, and bare metal restore scenarios.

Included Fixes


Included Fixes

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

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

T4C4114

T4C4115

T5HP064

T5LE072

T5LE074

T5LE075

T5LE076

T5LE077

T5LE078

T5LE081

T5LE082

T5LE083

T5LE084

T5LE085

T5LE087

T5LE088

T5LE089

T5LE090

T5LE091

T5LE092

T5LE095

T5LE096

T5LE099

T5LE100

T5LF079

T5LF080

T5LF081

T5LF082

T5LF083

T5LF084

T5LF085

T5LF086

T5LF087

T5LF088

T5LF089

T5LF090

T5LF091

T5LF092

T5LF093

T5LF094

T5LF095

T5LF096

T5LF097

T5LF098

T5LF099

T5LF100

T5LF101

T5LF102

T5LF103

T5LF104

T5LF105

T5LF106

T5LF107

T5LF108

T5LF109

T5LF110

T5LF111

T5LF112

T5LF113

T5LF114

T5LF115

T5LF117

T5LF118

T5LF119

T5LF120

T5LF121

T5LF122

T5LF123

T5LF124

T5LF125

T5LF126

T5LF127

T5LF128

T5LF129

T5LF130

T5LF131

T5LF132

T5LF133

T5LF134

T5LF135

T5LF136

T5LF138

T5LF139

T5LF140

T5LT068

T5LT069

T5LT070

T5LT071

T5LT072

T5LT073

T5LT074

T5LT075

T5LT076

T5LT077

T5LT078

T5LT080

T5LT081

T5LT082

T5LT083

T5LT084

T5TM020

T5TM021

T5TM022

T5TM023

T5TM024

T5TM025

T5TM026

T5TM027

T5TM028

T5TM030

T5TM031

t5TM032

T5TM033

T5TM034

T5TM036

T5TM037

T5TM038

T5TM039

T5TM040

T5TM041

T5TM043

T5TM044

T5TM045

T5TM046

T5TM047

T5TM048

T5TM049

T5TM050

T5TM051

T5TM052

T5TM053

T5TM054

T5TM055

T5TM056

T5TM057

T5TM058

T5TM059

T5TM060

T5TM061

T5TM062

T5TM064

T5TM065

T5TM066

T5TM067

T5TM068

T5TM069

T5TM070

T5TM071

Known Issues


Known Issues









■ When remotely installing the Arcserve RHA Engine on Windows Server 2008 systems, installation fails if you log into the Control Services as local system. To avoid this, use a Domain Admin account to access the Control Service.

■ When you use the Switch Computer Name redirection method on computers running Windows Server 2008 R2, you must manually rejoin the Master server to the domain after failover takes place.


■ After 72 hours, the bare metal machine will reboot automatically. This is applicable for full system scenarios.



■ For the Move IP redirection method on Linux platforms, you can configure the IP only by the ifconfig command.

■ When you instal RHA engine on clusters using Remote Installer, you need to install the Engine on both physical nodes and select a physical node instead of a cluster name.

Known Issues










Full System scenarios do not support Dynamic disks on the Master server.





■ Upgrading to Arcserve RHA r16 SP2: If you upgrade the RHA engine from previous releases to r16 Service Pack 2, you must synchronize the Master and Replica at least once to complete the upgrade.


■ Use the Volume synchronization instead of the File or Block synchronization.


Known Issues







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








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

Linux






denied.(5)


Chapter 9: Arcserve RHA r16 Service Pack 1

This section describes new features, enhancements, and included fixes in Arcserve RHA r16 Service Pack 1.


New Features and Enhancements (see page 71) Included Fixes (see page 72)


Arcserve RHA r16 Service Pack 1 supports the following features:

Proxy Server Support

Arcserve RHA allows replication using proxy servers. You can configure settings in a scenario to use a proxy server. The use of proxy servers is limited to master-replica synchronization and replication.

Arcserve D2D Support

Arcserve RHA provides native support for Arcserve D2D backups with a File System scenario integration option.

Included Fixes


Included Fixes

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

■ T5TM034

■ T5LF089

■ T5TM032

■ T5LT060

■ T5LT069

■ T5LT082

■ T5LF080

■ T5LF082

■ T5LF085

■ T5LE072

Chapter 10: Arcserve RHA r16 73

Chapter 10: Arcserve RHA r16

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


New Features and Enhancements (see page 75)


Chapter 11: New Features and Enhancements

This section describes the new features and enhancements made to the Arcserve RHA family of products, formerly sold as CA XOsoft.


Change Scenario While Running (see page 75) Cloud Support (see page 76) Enhanced Cluster Support (see page 76) Secure Communication (see page 76) Virtualization Enhancements (see page 77) Features No Longer Supported (see page 77) Known Issues (see page 79)

Change Scenario While Running

Effective with this release, you may modify certain scenario properties without having to stop a running scenario or force a resynchronization. The properties you may modify include:

■ Spool settings

■ Is Alive values

■ Bandwidth settings

■ Schedule properties

Included Fixes


Cloud Support

Effective with this release, the following features are introduced:

Replicate to the Cloud

You may use an Amazon Web Services EC2 cloud instance as the replication target for your Windows Server data without having to manually provision the replica on EC2. Cloud Replication supports file and byte level replication, multiple EC2 instances running on AWS, scheduled, periodic and continuous replication in forward directions, and recovery from the Cloud.

Failover to the Cloud

You may use an Amazon Web Services EC2 cloud instance as a high availability target for full system protection without having to manually provision the replica on EC2. Failover to Cloud supports full system protection of multiple Windows 2003 and 2008 R2 servers to an online replication target in the EC2 cloud, application and server monitoring, continuous replication in a forward direction, and offline recovery from the Cloud.

Note: An active and configured Amazon Web Services EC2 account is required for these features. Amazon Web Services does not yet officially support Windows 2008 R2 and we have observed issues during testing with this environment.

Enhanced Cluster Support

Effective with this release, Arcserve RHA provides the following protection to Microsoft Failover Cluster 2008 systems:

■ Eliminates the single point of failure by providing an additional layer of off-site protection to Microsoft Failover Cluster 2008 deployments running in a shared storage configuration. Arcserve RHA delivers continuous replication so that the clustered application can survive a complete loss of the shared storage hardware.

■ Acts as a replication provider for Microsoft to enable the new geographically dispersed clustering feature introduced with Windows Server 2008 failover clustering. This high availability solution allows for the connection of cluster nodes through a local area network (LAN) or wide area network (WAN), spanning many miles, for a solution that provides automatic disaster recovery.

Secure Communication

Effective with this release, SSL 128-bit encryption for securing communication between on-premises and off-premises servers without using a third-party VPN is now supported.

Note: Secure Communication is not a VPN replacement and does not extend the local LAN or circumvent firewalls.

Included Fixes


Virtualization Enhancements

Effective with this release, Full System scenarios support the following virtual platforms:

■ Microsoft Hyper-V

■ VMware vSphere

■ VMware ESX/ESXi

■ Citrix Xen Server

■ Amazon EC2

Features No Longer Supported

No features have been dropped for this release.


Chapter 12: Known Issues









■ When remotely installing the Arcserve RHA Engine on Windows Server 2008 systems, installation fails if you log into the Control Services as local system. To avoid this, use a Domain Admin account to access the Control Service.

■ When you use the Switch Computer Name redirection method on computers running Windows Server 2008 R2, you must manually rejoin the Master server to the domain after failover takes place.


■ Microsoft SQL Server







Included Fixes



■ Full System scenarios do not support Dynamic disks on the Master server.










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

Included Fixes









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

Linux






denied.(5)


Chapter 13: System Information

This section describes the supported operating systems and system requirements. Review this information before installing and using Arcserve RHA.


Minimum Hardware Requirements (see page 83) Supported Configurations: Windows (see page 83) Supported Configurations: UNIX/Linux (see page 89) Supported Virtual Platforms (see page 90) Installation Considerations (see page 90)

Minimum Hardware Requirements

For Arcserve RHA minimum hardware requirements, follow the minimum hardware requirements specified for the operating system and application you want to support.

Supported Configurations: Windows

For the most current information regarding supported systems, see the Compatibility Matrix https://arcserve.zendesk.com/hc/en-us/articles/201865559-Arcserve-RHA-16-5-Software-Compatibility-Matrix.

General Notes:

■ High availability support for BlackBerry (BES) is included with Arcserve RHA for SQL and Arcserve RHA for File Servers. Arcserve High Availability is not supported in an environment in which either the Master or Replica server is also functioning as a Windows Domain Controller (DC), DNS server, or SBS (Windows Small Business Server) server. You must use Arcserve Replication instead.

■ Itanium 2 and IA-64 processors are not supported.

■ Hardware requirements for Arcserve RHA depend upon the operating system and applications you are running. Ensure your system meets the minimum hardware requirements for the operating system on which you plan to install Arcserve RHA and for the applications you wish to protect.

https://arcserve.zendesk.com/hc/en-us/articles/201865559-Arcserve-RHA-16-5-Software-Compatibility-Matrix

https://arcserve.zendesk.com/hc/en-us/articles/201865559-Arcserve-RHA-16-5-Software-Compatibility-Matrix



Arcserve Replication

The following operating systems are supported for Replication for File Server, SQL 2005/2008/2008 R2/2012, Exchange 2007/2010/2013, SharePoint 2007/2010:

– Windows Server 2012 R2

– Windows Server 2012

– Windows Server 2003 Standard Edition (32-bit, x64), Windows Server 2003 Standard Edition (32-bit, x64) SP1, SP2

– Windows Server 2003 Standard Edition R2 (32-bit, x64)

– Windows Server 2003 Enterprise Edition (32-bit, x64), Windows Server 2003 Enterprise Edition (32-bit, x64) SP1, SP2

– Windows Server 2003 Enterprise Edition R2 (32-bit, x64)

– Windows 2003 Web Server Edition (32-bit, x64), Windows 2003 Web Server Edition (32-bit, x64) SP1, SP2

– Windows 2003 Datacenter Edition (32-bit, x64)

– Windows Small Business Server 2003 (32-bit, x64), Windows 2003 Small Business Server (32-bit, x64) SP1, SP2 (Exchange failover is not supported on SBS)

– Windows Small Business Server 2003 R2 (32-bit, x64) (Exchange failover is not supported on SBS)

– Windows Server 2003 Cluster (32-bit, x64), Windows Server 2003 Cluster SP1 (32-bit, x64) (MNS and CCR clusters are not supported)

– Windows Server 2003 Cluster R2, SP2 (32-bit and x64) (MNS and CCR clusters are not supported)

– Windows Storage Server 2003 SP1 (32-bit and x64)

– Windows Server 2008 Standard, Enterprise, Datacenter, Web Server (32-bit and x64). Windows Server 2008 on Itanium-based systems is not supported.

– Windows Server 2008 Enterprise Edition R2 (x64)

– Windows Server 2008 R2 Server Core

– Windows Storage Server 2008 SP1, SP2 (32-bit and x64)

– Windows Storage Server 2008 R2 (Workgroup, Standard, and Enterprise)

– Microsoft Virtual PC (32-bit, x64) (all versions) (Guest environment only)

– Microsoft Virtual Server (all versions) (32-bit, x64) (Guest environment only)

– Microsoft Hyper-V (all versions) (Guest environment only)

– VMware Virtualization Products (ESX, GSX, vCenter Server, Server and Workstation all versions) (32-bit, x64) (Guest environment only)



Notes regarding Replication:

– Replication for Exchange is not supported in an SBS (Windows Small Business Server) environment for failover/failback, but replication for data recovery is fully supported.

– Replication for Exchange 2007 no longer requires or supports the ws_ex2e.exe utility for failover/failback. The failover and failback processes can now be manually performed using Microsoft Exchange Management Shell, a new interface for Microsoft Exchange Server 2007, built on the Microsoft Windows PowerShell. Note that for Japanese environments, this utility is supported only if non-Unicode (single-byte) characters are used as arguments for the Exchange server.

The following operation systems are supported for Full System Replication:

– Microsoft Windows Server 2003 SP2

– Microsoft Windows Server 2003 R2 SP2

– Microsoft Windows Server 2008 SP1, SP2

– Microsoft Windows Server 2008 R2, SP1



The following operating systems are supported for Replication for Oracle:







– Windows Small Business Server 2003 (32-bit, x64), Windows 2003 Small Business Server (32-bit, x64) SP1, SP2 (Oracle failover is not supported on SBS)

– Windows Small Business Server 2003 R2 (32-bit, x64) (Oracle failover is not supported on SBS)

– Windows Server 2008 Standard, Enterprise, Datacenter and Web Server (32-bit and x64)







– VMware Virtualization Products (ESX, GSX, vCenter Server, Server and Workstation all versions) (32-bit, x64) (Guest environment only)

Notes regarding Oracle:

– Automatic rewind checkpoints are not supported for Oracle. Instead, you can insert manual or scheduled bookmarks.

– Oracle Asynchronous IO or Oracle Direct IO are not supported. Ensure they are disabled.

High Availability

The following operating systems are supported for High Availability for File Server:







– Windows Server 2003 Cluster (32-bit, x64), Windows Server 2003 Cluster SP1 (32-bit, x64) (MNS clusters are not supported)

– Windows Server 2003 Cluster R2, SP2 (32-bit and x64) (MNS clusters are not supported)


– Windows Server 2008 Standard, Enterprise, Datacenter and Web Server (32-bit and x64)

– Windows Server 2008 Enterprise Edition R2 (x64)





– Windows Storage Server 2008 R2 (Workgroup, Standard, and Enterprise)






– VMware Virtualization Products (ESX, GSX, Server and Workstation all versions) (32-bit, x64 bit) (Guest environment only)

The following operating systems are supported for High Availability for Exchange 2007/2010/2013, SQL 2005/2008/2008 R2/2012, IIS 6/7.0/7.5, SharePoint 2007/2010, CRM 4.0:








– Windows Server 2003 Cluster R2, SP2 (32-bit, x64) (MNS and CCR clusters are not supported)


– Windows Server 2008 Standard, Enterprise, Datacenter, Web Server (32-bit and x64), R2





– Microsoft Hyper-V (all versions), (Guest environment only)

VMware Virtualization Products (ESX, GSX, Server and Workstation all versions) (32-bit, x64) (Guest environment only)

The following operating systems are supported for High Availability for Oracle 10/11g:









– Windows Server 2008 Standard, Enterprise, Datacenter, Web Server (32-bit and x64)





– VMware Virtualization Products (ESX, GSX, Server and Workstation all versions) (32-bit, x64) (Guest environment only)

Notes: Automatic rewind checkpoints are not supported for Oracle; instead you can insert manual or scheduled bookmarks.

The following operating systems are supported for High Availability for Blackberry Enterprise Server (BES):








– Windows Server 2003 Cluster R2, SP2 (32-bit, x64) (MNS and CCR clusters are not supported)

– Windows Server 2008 Standard, Enterprise, Datacenter, Web Server (32-bit and x64)



Supported Configurations: UNIX/Linux




– VMware Virtualization Products (ESX, GSX, Server and Workstation all versions) (32-bit, x64) (Guest environment only)

Note: Blackberry Enterprise Server (BES) 4.1 SP6. Assured Recovery is not supported for BlackBerry HA due to SRP key conflicts.

The following operating systems are supported for Full System scenarios:


– Microsoft Windows Server 2003 R2 SP2


– Microsoft Windows Server 2008 R2

Assured Recovery Option

■ Arcserve RHA on Windows

■ VSS Snapshot Management is enabled on Windows Server 2003 and later.

Supported Configurations: UNIX/Linux

Arcserve RHA is supported on the following UNIX/Linux platforms:

■ UNIX:

– IBM AIX 5.3 TL12, (32- and 64-bit) 6.1 TL9, 7.1 TL3 (64-bit only)

– Oracle Solaris 10, 11.1 SPARC(kernel level 144488 and later)/x86 (64-bit) (kernel level 144489 and later)

■ Linux

– Red Hat Enterprise Linux version 5 through 6.6 (i386 and x86-64)

– Novell SuSE Linux Enterprise Server 10 through 11 SP1 (i386 and x86-x64)

– CentOS version 5 through 6.6 (i386 and x86-x64)

– Oracle Enterprise Linux 5.7

Note: Assured Recovery is not supported on UNIX/Linux systems.

Oracle 11g R2 is supported, but you must download a 32-bit client. Go to the Oracle website and search for "Separate 32-Bit Client Software for 64-Bit Ports" for more information.

Supported Virtual Platforms


Supported Virtual Platforms

Effective this release, the following are supported

Virtual Platforms:

For Full System Scenarios

Windows:

VMware vSphere 6.0, 5.5, 5.1, 5.0 (applicable to Full System scenarios)

Citrix XenServer 5.6 through 6.2

Amazon Elastic Compute Cloud (Amazon EC2)

For Hyper-V and Full System scenarios

Microsoft Hyper-V 2008 R2, 2012, and 2012 R2

Virtual Appliance:

For Full System Scenarios

Windows:

Windows 2008 Server R2

Windows Server 2012

Windows Server 2012 R2

Installation Considerations

Important! Please note that the Arcserve RHA download image exceeds the amount of free disk space available on a standard compact disk (CD). To copy the download image to media, you must use a DVD or a flash drive.

Consider the following:

■ Ensure your screen resolution is set to 1024 x 768 or higher. Lower resolutions may result in cropped screens.

■ On Japanese environments, the Launching Application dialog may appear in English. To avoid this problem, ensure that the .NET Framework Japanese Language Pack has been applied.



■ To avoid firewall issues, you should install or update the Arcserve RHA Engine on Windows Server 2008 Master and Replica servers by running setup.exe locally, and then disable the Verify Arcserve RHA Engine on Hosts option during scenario creation. If you must remotely install the Arcserve RHA Engine on these machines, you need to enable WMI traffic through the Windows Server 2008 Firewall, and then configure port 25000 on all Master and Replica machines. In addition, if you are creating Hyper-V scenarios, you should also enable ICMP echo messages on all Master, Replica, and Hyper-V guest machines so that Arcserve RHA can successfully ping guest operating systems.

Note: We recommend using the Windows Firewall with Advanced Security MMC snap-in. For more information about using the Windows Firewall with Advanced Security MMC snap-in, see the Microsoft website.

Before remotely installing the Arcserve RHA Engine, enable WMI traffic through the firewall:

1. From the Control Panel, open Security settings and then click Windows Firewall.

The Windows Firewall Settings dialog opens.

2. Click Change Settings and then click the Exceptions tab.

A list of programs and ports is displayed.

3. Select Windows Management Instrumentation (WMI) to enable WMI traffic through the firewall.

4. Click OK to exit firewall settings.

5. Install the Engine as usual.

6. After you install the Engine, configure port 25000 on each Master and Replica machine using the New Inbound Rule Wizard from the Windows Firewall with Advanced Security MMC snap-in.

Ensure TCP is selected and add port 25000 to the Specific local ports list. Allow the connection and apply it to the applicable profile (for example, Private).

Note: Port 25000 is the default. You may change this port. For more information about completing the wizard, see the Microsoft website.

7. (For Hyper-V scenarios) You should also enable ICMP echo messages on all Master, Replica and Hyper-V guest machines so Arcserve RHA can successfully ping Hyper-V guest operating systems.

Use the New Inbound Rule wizard to create a custom rule that enables Specific ICMP Echo Requests for any IP address and allows the connection.

Note: For more information, see the Microsoft website.



■ Installing the Arcserve RHA Control Service with ACL-based authentication on domain controllers is not supported.

Solaris 11

■ The following procedure is for installing the Arcserve RHA Engine into a Solaris 11 Sparc or Solaris 11 x86 Non-Global zone. Make sure you have installed Arcserve RHA in both the global and non-global zone:

1. Install the pkgadd command in the Non-Global zone:

pkg install install/installadm

2. Copy the appropriate file into the Non-Global zone:

– For Solaris 11 Sparc, copy the file called arcserverha_sunos511_sparc.tgz

– For Solaris 11 x86, copy the file called arcserverha_sunos511_i386.tgz

3. Log in to the Non-Global zone, uncompress the appropriate tgz file:

For Solaris 11 Sparc:

tar zxvf arcserverha_sunos511_sparc.tgz

For Solaris 11 x86:

tar zxvf arcserverha_sunos511_i386.tgz

4. Navigate to the ARCserveRHA folder:

cd ARCserveRHA

5. Run the script, install.sh to install the Arcserve RHA Engine.

Chapter 14: Localized Versions 93

Chapter 14: Localized Versions

Arcserve RHA is available in the following languages:

■ English

■ French

■ German

■ Japanese

■ Italian

■ Spanish

■ Brazilian Portuguese

■ Simplified Chinese

■ Traditional Chinese

Note: This release of Arcserve RHA supports all characters in the Unicode Basic Multilingual Plane. Support for JIS2004 characters includes those encoded in the Basic Multilingual Plane, but not surrogate pair characters (Plane 2).

Character sets for these languages are supported for:

■ Installation

■ Folder/File Replication

■ Database/table/instance/Exchange Message Replication

■ Certain wizard screens, menus, reports, and alerts within the Centralized Management Interface

Note: Character sets in these languages are not supported in email attachments within alerts, hostnames, installation/home directory paths, user names and passwords. All servers participating in a scenario should be installed with the same language package. However, the same language package is not required for all servers in a domain.

Appendix A: Acknowledgements 95

Appendix A: Acknowledgements

Portions of this product include software developed by the third-party software providers. The license agreements are available in the \Bookshelf_Files\TPSA folder in the Bookshelf.

arcserve® replication and high availability · when you upgrade the rha engine, all existing...

Documents