Chapter 6: Arcserve RHA r16.5
This section describes new features, enhancements, and included fixes in Arcserve RHA r16.5
This section contains the following topics:
New Features and Enhancements (see page 41)
Included Fixes (see page 45)
Known Issues (see page 46)
Dropped Systems and Platforms Support (see page 50)
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
New Features and Enhancements
42 r16.5 Release Notes
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.
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
New Features and Enhancements
44 r16.5 Release Notes
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.
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
Known Issues
46 r16.5 Release Notes
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.
To correct this problem, manually start the scenarios that were running before the upgrade started using Run, after the upgrade process completes. Use the Run control from the user interface.
■ If you are unable to reset the Arcserve RHA interface back to the default after rearranging panels using the dock manager, perform the following steps:
– Find the running directory for the ws_gui.exe file.
– Close the interface.
– In this directory, delete the following files: dock_layout.xml, dock_layoutdefault.xml.
– Relaunch the interface.
The interface arrangement is returned to the default layout.
■ Rewind is not supported for applications that use TxF functionality (IIS 7.0) ■ When remotely installing the Arcserve RHA Engine on Windows Server 2008
systems, installation fails if you log in to the Control Services as a local system. To avoid this, use a Domain Admin account to access the Control Service.
Chapter 6: Arcserve RHA r16.5 47 ■ When you use the Switch Computer Name redirection method on computers
running Windows Server 2008 R2, manually rejoin the Master server to the domain after failover.
■ When a NetBIOS server name is longer than 15 characters, the Arcserve RHA Manager may fail to launch from the Overview screen if a proxy is set in Internet Options. The proxy server can only resolve DNS names, not NetBIOS names.
■ After 72 hours, the bare metal machine will reboot automatically (applicable for full system scenarios).
■ When you boot the bare metal machine after recovery, some drivers may be
missing. Manually install these drivers.
■ When you upgrade the RHA engine, all existing bookmarks and rewind points are lost.
■ For the Move IP redirection method on Linux platforms, you can configure the IP only by the ipconfig command.
■ When you install the RHA engine on clusters using Remote Installer, you must
install the Engine on both physical nodes and select a physical node instead of a cluster name.
Microsoft SQL Server
■ In SQL Server scenarios, the cluster server name is changed after switchover, but
the server is not rebooted even if the reboot property is set.
■ Do not install SQL data files at the root directory of boot volumes such as C:\.
During replication, the target files may fail to open on the Replica server, causing errors.
■ Assured Recovery scenarios fail on SQL Servers running in a workgroup. This is
because:
– The Replica local admin account is overwritten by the Master local admin account in the Master database.
– The application uses Windows authentication to log into SQL Server.
To avoid this problem, use SQL authentication or switch computer name redirection method.
Known Issues
48 r16.5 Release Notes
Full System Protection
■ For Citrix Xen scenarios, we are unable to unmount a disk on a virtual machine
when files stored on the disk are in use.
■ Depending on your Windows license type, you may need to reactivate your virtual machines after Full System Assured Recovery or switchover. Visit the Microsoft website for more information about reactivation policies.
■ In "mixed environments" in which supported and unsupported versions of ESX are managed by a vCenter Server, full system scenarios may fail because VMDK cannot be mounted on the appliance specified. To avoid this situation, verify all versions of ESX in your environment are supported.
■ When performing a restore process for a Full System scenario, manually stop the application services on the Master or that application may become corrupt after restore. If the application is corrupted after a restore, stop the application services, restore to the same bookmark again to solve the problem.
■ While synchronizing a Full System scenario if you get the "Access is denied"
message, then consider the following points:
Use the Volume synchronization instead of the File or Block synchronization.
■ Set engine service logon account to Local System. The error could be because the master engine service logon account is local or domain administrator.
■ On Microsoft Windows 2012, the File Server Resource Manager feature occupies some fixed volume space. For full system scenarios, this may lead to insufficient disk space for Arcserve RHA to complete synchronization. One of the workarounds is to disable the Windows server 2012 File Server Resource Manager feature and then run FSHA.
Arcserve RHA for MMC
■ The MMC may fail to connect to the license server under these conditions:
– The default HTTP or HTTPS proxy is configured on the same host where the MMC is running.
– The address of the license server is not in the proxy bypass list.
– The proxy requires authentication to access the website.
The Windows account does not have the required privileges to access the proxy, which means the current MMC user is not authorized to use the proxy.
Chapter 6: Arcserve RHA r16.5 49
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 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.
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
Dropped Systems and Platforms Support
50 r16.5 Release Notes
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 hosts.
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.
Dropped Systems and Platforms Support
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.