Release Notes for Recovery Series and Unitrends Backup 10.3.4

• Edit host file – Resolved an issue where users could not edit the host file due to a Could not retrieve host information error.
• Disaster Recovery – Resolved an issue where an appliance could not be recovered if the appliance hostname was listed in the localhost line in the host file of the failed appliance. For example, the appliance hostname VMware-UB is on the localhost line in this sample host file:

[root@VMware-UB-47 ~]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost VMware-UB
192.168.001.111 VMware-UB
192.168.001.148 w2k12r2-148

• File-level backup – Resolved an issue with case sensitivity where directory names could be created that did not match the original. For example, MY_Directory could be created as my_directory.
• File-level backup – Resolved an issue where backups of full file paths larger than 4608 characters could fail.
• Windows image-level backup – Resolved an issue where backups erroneously included removable drives from attached card readers and other peripherals, which caused these backups to fail.

• Failover of Windows replicas to VMware – Resolved an issue where Windows replicas failed to boot into audit mode on ESXi hosts. The replica would boot into WinPE instead.

• Hyper-V version 8 – Resolved an issue with change tracking of version 8 VMs that caused replication of incremental backups by Hyper-V's native replication feature to fail.

• Instant recovery of Windows image-level backups – Resolved an issue on physical Recovery Series appliances where only virtual hosts could be selected as the target for instant recovery. With this fix, the asset can now be recovered to the Recovery Series appliance itself or to a virtual host.

• Resolved an issue with discovery of SQL clusters that could result in the user interface becoming unresponsive.