Known Issues

The following issues are known to exist in this release:

To view Known Issues of previous release, click here.

Full System Linux Scenario:

• For an existing Full System Linux scenario to Hyper-V scenario, changing to another Hyper-V host by editing Replica, VM, Virtual Platform Settings is not available. You can create a new scenario using the new Hyper-V server.
• For Full System scenario to EC2 in Linux if Master server is also a virtual machine on EC2 and when performing AR or Switchover, to log into the AR or Switchover VM using user account and password, a prompt appears to use publickey authentication. The PasswordAuthentication no is present in /etc/ssh/sshd_config on the AR or Switchover VM. Change the value to ssh_pwauth: 1 in /etc/cloud/cloud.cfg on Master virtual machine to allow password authentication upon VM reboot.
• For Full System Linux scenario where target Hypervisor is Hyper-V, the Integrity Testing AR VM entry is not removed after Integrity Testing is finished. An obsolete VM entry is left in ESXi, vCenter or Hyper-V. You can simply ignore.
• In Linux FSHA scenario to Hyper-V, during automatic AR, additional NICs are created for AR VM. This issue has no impact on AR VM /testing results.
• For Full System Linux scenario where master is RHEL8 and VA is Hyper-V, the Integrity Testing may fail. To avoid this problem, run the command "yum groupinstall base-x" on master.
• Even when the Master has DHCP configured, the Network Mapping dialog shows DHCP as no. There is a configuration mismatch in the ifcfg-eth<x> configuration file under the /etc/sysconfig/network-scripts directory for the adapter eth<x>. Make sure the network configuration file name ifcfg-eth<x> matches the adapter name, and then rerun the scenario configuration wizard. The Network Mapping dialog must reflect the settings accurately.

Full System scenario:

• For Full System scenario where target Hypervisor is Hyper-V, the Integrity Testing AR VM entry is not removed after Integrity Testing is finished. An obsolete VM entry is left in ESXi, vCenter or Hyper-V. You can simply ignore.
• Arcserve Continuous Availability cleans the VM created by AR test. Azure may take a long time to delete the NIC. If another AR test is performed, the second AR test may fail. To resolve the error, log into Azure portal and manually delete NIC that AR created and perform the AR test again.

For EC2:

• If you plan to change the instance type before running Integrity Testing or Switchover, make sure to terminate the previously created instance, and then run the Integrity Testing or Switchover. Make sure the instance you are going to terminate is in stopped state and Integrity Testing/Switchover is not currently running for the scenario.

Common Functions:

• For the scenarios created under groups in older versions, after upgrading to 18.0, by default, the Switchover as a Group option is ON. As a result, Arcserve Continuous Availability performs automatic switchover even if the manual switchover is selected for individual scenario(s) in the group.
• The Network Interface Card of the instance on EC2 is recreated when the network configuration is modified in the scenario properties. In such case, the instance may fail to start when the same static IP address is reused. The InvalidIPAddress.InUse error appears as that IP address was not released from the previous NIC yet. As a result you cannot assign same IP to the new one. To resolve, wait for the previous NIC to release the IP address and then start the instance.
• When you replicate the Full System scenario to Hyper-V CSV if you suspend replica and restart the replica node engine service or replica node, resync of Full System Scenario happens after restarting the engine.
• Turn off IE Enhanced Security Configuration for administrators, or you might see a notification on Continuous Availability web portal: An add-on on this website could not be executed.
• On Windows server where Windows Defender is enabled, in Continuity Suite Manager Scenario View, the Changed Size is at times larger than actual size. Usually, the changed size is less than 2 times of the actual size. This issue occurs as Windows Defender creates file in memory, usually occurring to executables and binary files. To resolve, exclude Continuous Availability root directories and Spool directories into Windows Defender's exclusion folders.
• While performing block synchronization with FSHA for Windows an error message ER00033 11922 Error xxxx xxxx xxxx xx Unable to open file C:/Users/administrator /AppData/Local/Packages/Microsoft.Windows.Cortana_cw5n1h2txyewy/LocalState/DeviceSearchCache/AppCache131987362751241482.txt appears. Ignore the error message.
• For HA scenario, if Master server has a private IP and a Public IP address (usually that runs on cloud) and the scenario is created using the public IP address of Master when scenario is running, the HA Is-Alive verification fails even if NAT connection is set between Master and Replica. The issue occurs because the Continuity Suite Engine is running inside the VM and is able to notice only the private IP address. The Continuity Suite Engine has no knowledge about the public IP address of the VM. To resolve, navigate to Master, Properties, Host Connection, Replication IP Address and type the private IP of Master.
• On SUSE Linux Enterprise Server VM on the EC2 platform, the file /etc/SUSE-brand is missing, preventing Arcserve Continuous Availability from recognizing the platform correctly. To resolve, create the file /etc/SUSE-brand manually and add the following content in the file:

SLE

VERSION = 15

• The whole file appears as below.

#cat /etc/SUSE-brand

SLE

VERSION = 15

Hyper-V CSV:

• For Hyper-V CSV-based Hyper-V scenario, when backward scenario is running (that is after Switchover finishes), if the active VM on Replica is migrated to another CSV node, the backward scenario cannot auto-rerun the scenario and stops. To start the scenario, manually migrate that active VM back to original CSV node, and then run the scenario.
• For Hyper-V scenarios on Hyper-V CSV cluster, when backward replication scenario is active, migration of Master VM is not supported. In case of VM migration backward scenario stops and fails to restart. To resolve, manually copy the uuid.xml file from Master to all other engines/nodes available within cluster. This file is located at RHA\Engine\config_25000 and must share the same location on other nodes.
• For Hyper-V scenarios on Hyper-V CSV cluster VM migrations are not supported for VMs containing non-US characters in their names.

Bare Metal Recovery (BMR):

When creating BMR ISO, you may fail to create ISO if you select x86 version. In this case, select x64 only for creating the ISO.

If original Master is Windows 2019, and the Continuous Availability BMR ISO is made with ADK for Windows 10 version 1809, when you try to perform BMR to the original Master server, then during the BMR synchronization process, you may come across an error: cannot format volume and the scenario stops, resulting into an incomplete BMR process. To resolve, use a Continuous Availability BMR ISO made with ADK for Windows 8.1.