Customer-Found Defects for Unitrends 10.3.X

SUMMARY

Defects that were found by customers and resolved in 10.3.X-series releases.

DESCRIPTION

The following article lists defects that were found by customers and resolved. Click a defect to view its associated KB article.
For a list of resolved security vulnerabilities, see KB1150.

**10.3.1**
Backup Copy (Hot)	Hot backup copy jobs on version 10.3 appliances may take too long to complete
Replicas	Windows replicas of GPT-partitioned assets may fail to complete restore jobs
Storage	File descriptor leaks may eventually lead to space issues on the appliance
Upgrade	Appliances with Unitrends cloud backup copy targets may fail to update
Windows Agent	Hyper-V hosts may blue screen if the CBT driver is uninstalled Failure to back up hard links may cause certain Windows applications to fail following bare metal recovery or Windows replica restore

**Windows Agent Release 10.3.0-4**
Windows Agent	Failure to back up hard links may cause certain Windows applications to fail following bare metal recovery or Windows replica restore

**10.3**
Backup	Hyper-V backups may fail with volsnap errors NAS backup storage devices may erroneously appear to lack necessary free space Attempts to back up an AHV disk with a capacity that is not a multiple of 1024 bytes may fail Cannot mount a NAS share with spaces in the mount name Asset names longer than 31 characters may lead to backup failures Appliances using a bonded NIC configuration may fail to back up AHV assets Appliance hostnames greater than 31 characters may be permitted
Backup Copy (Cold)	Cold copy jobs to NAS targets may fail The cloudadm repair function may not work properly for docker Cold backup copy imports from tape targets may fail with input/output errors NAS, FC, and iSCSI cold copy targets do not automatically mount/unmount as required by cold copy jobs Format 2 cold backup copies may fail when a format 1 backup is also included in the job Certain RDX device models may report a dock serial number rather than a disk serial number, leading to cold copy scan failures AWS GovCloud may not be available as a cold copy target The CloudBlkSize general configuration (master.ini) setting may permit entry of excessively large values Attempts to add a Google Nearline bucket as a cold backup copy target may fail In the case of a disk rotation scheme, fulls may not be imported from the same media as the rest of the backup group
Backup Copy (Hot)	Hot backup copies may fail with the error message "Fail to approve pending copy request - Query to add"
DedupNT Migration	DedupNT migration may fail for stateless Unitrends Backup appliances using iSCSI primary storage
Disaster Recovery	Stateless appliance recovery may fail for Unitrends Backup appliances on XenServer DR system state recovery may fail with database errors
Hardware	Attempts to re-image a Recovery Series appliance from USB media may fail
PSA	The default ConnectWise WSDL may be incorrect
Recovery	Hyper-V file-level recovery may fail with fusectar errors when random access mode is enabled Mac and Windows recovery jobs may fail to queue when recovering to a directory containing spaces
Replicas	WinPE environment may hang, resulting in Windows replica failure Clean teardowns may not be enforced for VM replicas created from backup copies
Reports	Compliance reports may be received, even though no data copy access jobs are present The Backup Copy Job Notifications report may depend on internet access for certain image files
Unitrends Cloud	Source appliances may be permitted to upgrade to a newer version than their cloud targets, leading to hot backup copy job failures Attempts to log in to Unitrends Cloud targets with active directory credentials may be slow or unresponsive
Upgrade	Kernel updates of Unitrends appliances deployed as installable software may result in driver compatibility issues
User Interface	Filtering cold backup copies may produce counterintuitive results On the configure page, the appliance column may appear sorted in the opposite order indicated The release features popup may display after every login with active directory credentials VMs may not display in the UI for Hyper-V clusters with greater than 16 nodes
VM Instant Recovery	VMware instant recovery may fail as a result of VMotion issues

SUMMARY

DESCRIPTION

Browse this section