Known Issues

• Using the same hard-drive model in multiple Solo devices causes the drives to not be displayed in OneSystem for the additional Solo devices. Internal drives must have a unique name for each Solo device. To work around this, rename the drives in the Configuration -> Storage page. As an example, if you have three Solo devices, each with a TOSHIBA HDWL120 hard drive, add the first drive in the first Solo to the OneSystem Storage configuration then rename the drive on the Storage page. Next add the second drive in the second Solo to OneSystem and then rename the drive, then add the third drive in the third Solo. This issue will be fixed in the next release.

Important! The Hyper-V VM Generation setting on the System Recovery page is only intended as an Override setting in case Arcserve/OneSystem is unable to identify the correct version of the VM generation. You should not change the default Generation setting unless the incorrect generation was selected by the system. 9581

• The recovery ISO fails to boot when you select "Microsoft UEFI certificate Authority" for Hyper-V gen2 VM's. This also applies to any Linux VM running in Hyper-V. 9687
• Ubuntu 16.04 VM's with UEFI boot fail to boot when restored to a Hyper-V or VMware host. This happens because of two issues. The UEFI boot records are not captured during backup, and the UEFI default boot file "bootx64.efi" is not installed by default on Ubuntu 16.04. To work around this issue, you can manually re-create a boot record, or install a bootx64.efi so the machine will boot. See the Using Boot Repair KB article. 9619
• In some cases, excluded volumes on Hyper-V machines restored with VirtualBoot are not being properly excluded. 9741
• Limit your VMware machine names to 70 characters or less. Longer names cause VirtualBoot to fail. 9360
• Arcserve does not support Host-based backups for Hyper-V for Server 2012 R2 (or older). If you deploy a windows agent on a Server 2012 R2 Hyper-V host, the agent registers and the host is available as an agent on the Protection page. However, the guest VMs on the host are also discovered, but even with a policy assigned, the backups don't run for the VMs.

Note: If you have Hyper-V Host-based Backup and Restore installed on Windows 10, or Server 2016 and newer, the host-based backup does work. 9631

• In some cases when you Uninstall ShadowXafe components from Hyper-V hosts, the Arcserve .log and .rpt folders in the Program Files and ProgramData folders are not removed. 9637
• In some cases (if the Arcserve Agent Service is still in use), a restart is required when you uninstall a Hyper-V Backup and Restore target, or a service node, or a director from Hyper-V. If you are uninstalling the Windows backup agent it will always ask you to restart. 9666
• Restoring from the Arcserve cloud with Hyper-V Thin provisioning is not supported in this release. A Hyper-V restore from a cloud recovery point will be Thick provisioned. Thin provisioning is supported if restoring from local storage. 9794
• Unlocked partitions on Hyper-V don't show up on a restored machine. In some cases you may need to adjust the policy before running a backup, or you will need to bring the disks online after completing the restore. 9660

Note: This is a Windows policy. You may see the message "the disk is offline because of a policy set by the administrator" in the Disk Manager.

There are two ways to work around this,

First option: Prior to the backup:

Follow these steps:

1. Open the Windows administrative console window to adjust your policy.
2. Run the following commands in the console:
3. diskpart
4. san policy=OnlineAll
3. After running the commands, take a backup and then restore.

Second Option (after backup)

If the disks do not show up:

Follow these steps:

1. Go into Windows Disk Management and find the drive that is shown as offline.
2. Right click on the drive and bring it back online.
3. The disks and the data will now appear.
• Multi-path is not currently supported for ISCSI targets. If you encounter an issue with multi-path for ISCSI, see Troubleshooting: ISCSI not connecting in 4.x.