Customer Found Defects for Recovery Series and Unitrends Backup 10.0.0-2 through 10.2

SUMMARY

Customer Found Defects for Recovery Series and Unitrends Backup 10.0.0-2 through 10.2.

ISSUE

The following article lists defects that were found by customers and resolved. Click individual defects to view their dedicated KB articles.

For a list of resolved security vulnerabilities, see KB1150.

RESOLUTION

**10.2**
Backup	Snapshots may be left behind in the Storage Repository when disks are excluded from Xenserver backups Excessive memory usage by AHV backup processes may cause large AHV backups to fail Backups of aliased Windows assets may fail
Cold Backup Copy / Archiving	Cold copies imported to version 10.1 appliances may not be recoverable Misleading error messages may result from successful cold backup copy imports from tape archives Cold copy imports from tape may fail following upgrade to 10.1 eSATA disks formatted by the appliance after attachment as backup copy targets may appear to still contain data Attempts at formatting tape devices for use as backup copy targets may fail Error messages may incorrectly identify disconnections as the cause of cold copy failures Cold copy operations may hang indefinitely if there is no free space on the media Large cold copy jobs to tape targets may fail Unitrends appliances may misidentify iSCSI LUNs as eSATA devices following backup copy target media scan Tape imports may fail with input/output errors NAS backup copy targets may need to be re-added following temporary connection loss
Copy Data Management	Data copy access job failure may occur when the job contains multiple VMware backups with similar instance IDs The Power On Timeout option for data copy access jobs may be limited to a maximum of 60 minutes
Database	The database maintenance script may fail to run, eventually leading to a decline in appliance performance Database failures may cause core dumps in other utilities Database maintenance may either fail to run or run successfully and produce a misleading "already-running" error
Disaster Recovery	Backup copies may not be recoverable from the new appliance following disaster recovery
Recovery / Restore	Large numbers of sub-directories may cause errors when attempting file level recovery Recovery may fail for backups of Hyper-V VMs on SMB
Replicas	Windows replica creation may fail if a VM with no UUID is present on the VMware host Windows replica creation may fail for assets containing storage volumes whose names include apostrophes
Reporting	Ticket creation for ConnectWise Manage 2018.3 or 2018.2 may fail
SNMP	Unitrends appliances deployed on HP Proliant systems as installable software may experience SNMP agent failures
Unitrends Agents	The Windows agent may fail to push install on x86 Windows 10 assets when domain administrator credentials are used
Unitrends Cloud	Backup copies to Unitrends Cloud targets may experience multiple unsuccessful retries
Upgrade	Updates may fail for Unitrends Backup appliances deployed with Exagrid CIFS storage
User Interface	Edits to data copy access jobs may fail to save Duplicate data copy access jobs may appear under the job manager tab Exclusion settings may misleadingly suggest that full regular expression functionality is supported The progress bar representing a cold copy job may appear to exceed 100% Assets that were originally added via resolvable hostnames may demand IP addresses in the Edit Asset dialog Jobs may not appear in the Jobs Calendar if the client browser timezone is not the same as the appliance time zone Selecting an appliance storage device may preclude storage devices on other managed appliances from being edited until the UI is refreshed A backup may have the same node ID as its copied counterpart, resulting in items missing from the data copy access job inventory tree

**10.1.1-3**
Backup	Unitrends Backup appliances deployed as installable software could experience bputil errors and space issues Abnormally large log files were caused by interrupted Hyper-V backups
Cold Backup Copy / Archiving	NAS cold copy targets that were out of space could fail to purge
Database	High log levels could lead to space issues and subsequent database crashes
Configuration	Special characters in an appliance's root user password precluded it from being managed by another appliance SNMP defaults restrict compatibility with SolarWinds SAM Storage disks with similar names to previously added disks could not be successfully attached to the appliance
Recovery / Restore	I/O errors would prevent the import and recovery of all files, including those not directly affected, from the tape Unsuccessful disk migration could cause Hyper-V instant recovery failures Issue could cause poor Hyper-V instant recovery performance and prevent successful teardown Files recovered from Unitrends Cloud may be mislabled with all-lowercase filenames
Replicas	Windows replicas that were created for assets that did not initially have backups could not be removed from the appliance Windows replicas on Recovery Series appliances could not be brought into live mode Windows replica recovery could fail with an error message that misleadingly suggests a change in disk configuration is responsible for the failure VM replica UI elements may be hidden on Recovery Series appliances
Reporting	Capacity report displayed incorrect data when both SQL and Hyper-V roles were enabled on protected Windows servers
Upgrade	XenServer assets could not be viewed from the Protect tab following update 606-800 series appliances could not be successfully updated
UI	Entries in the NTP server list could not be removed Jobs page of appliances configured for cross-copy could be slow to load Confirmation dialog for removing a source appliance from a target did not warn users that the source's backups would be removed Add Virtual Host dialog specifically requested an IP address when either an IP address or a resolvable hostname would have sufficed Recover page on manager appliances could be slow to load Backup Copy Hot Targets reports were sent even though hot backup copy was not configured Slow loading of the inventory during the backup job creation process could cause a variety of issues related to backup and retention Minor UI issues resolved in version 10.1.1-3

**10.1**
Backup	Backup failures may occur as a result of memory issues Recovery Series appliances may experience backup failures caused by space issues Vmware backup jobs "waiting on client data" may accumulate in the queue The appliance may erroneously attempt an incremental backup following VM configuration change Concurrent VMware backups may fail with NBD_ERR_INSUFFICIENT_RESOURCES Backup jobs that recur on the first day of the month may have duplicates NDMP backups may fail if the password contains special characters Scheduled VMware backups with regular expression filters may sporadically fail to run Space issues may occur on the appliance as a result of inaccurate free space calculation
Cold Backup Copy / Archiving	Cold copy performance may decline following migration to CentOS 6 Cold copy data may appear to take up space even after it has been erased Encrypted cold copies may sporadically fail Cold copy times may be unusually long for appliances running version 9.2 or earlier Cold copy times may be unusually long due to unnecessary processes consuming appliance resources Cold backup copy job descriptions may not be updated after the name of the job is changed Cold backup copy operations may use the wrong device when multiple archive devices are configured Preparing disk media in an RXDA equipped appliance may return: "Failed: 1 drive was added; prepare media manually to use this configuration"
Hot Backup Copy / Replication	Hot Copy or restore failures may result from Hyper-V synthetic backups when non-default deduplication block size is used Backup copy bandwidth throttling schedules may not allow midnight to be selected as an end time
Recovery / Restore	Restore target assets cannot be sorted when creating a file level recovery job File level recovery of Linux assets from incremental backups may fail eSATA backup storage used in Linux Deployable UB (Metal) implementations may be inappropriately returned as a cold copy archive device
Reporting	Exported backup history reports can only display up to 5000 individual files SNMP trap notifications for backup failures may fail to generate Details may not properly display in the Weekly Status report The appliance may generate misleading alerts when application data is protected at the asset level The appliance may generate misleading alerts regarding volume changes
UI	The backup copy cold target list is limited to 32 targets A single VM from a newly added clustered ESX host may fail to display in the appliance UI There is no meaningful error message for when a permission restricted file cannot be added to an inclusion/exclusion list If the top entry in a column of regex filters is deleted, the filter at the bottom of the column may also be deleted
Unitrends Agents	Agent Push may fail when credentials contain spaces or special characters
Unitrends Cloud	Unitrends cloud customers may receive misleading backup copy suspension notifications
Upgrade	CentOS 5 to 6 migrations may fail

**10.0.0-5**
VMware Backup	In 10.0.0.-2, roll-up of VMware incrementals may produce a malformed synthetic full backup.

**Windows Agent Release 10.0.0-3**
Windows Agent	Deleted files on Windows systems may misleadingly appear available for recovery following backup Recovery of a VM to its original location would fail if the VM was created in the Windows default location Backup of Hyper-V configuration 6.2 or higher VMs may fail if the appliance is version 9.2 or older and the Hyper-V server is running agent version 10.0 or newer Attempts to back up AzMan as a VM may result in errors The general configuration setting (master.ini) for expanding the Windows change journal may no longer work

**10.0.0-2**
Backup	Backup synthesis may take too long to complete Backups may fail because of clustered Hyper-V VM scheduling that should not be allowed by the UI SQL 2000 backups may fail Full backups of Hyper-V nodes may take too long to complete Appliances retaining large numbers of failed backups may experience a sudden increase in backup failure rate SQL backup failures may occur alongside SQL database crashes App-aware backups for ESX 6.0 VMs may fail Backups may fail because of a buildup of unused space reservations Successful full backups may be inaccurately labeled with warnings
Hot Backup Copy / Replication	Hot backup copies may become stuck in a failure/retry loop Hot backup copies may fail because of metadata corruption on the target 9.2.0-2 appliances may experience replication issues
Recovery / Restore	The list of available target volumes for NDMP recovery may be incomplete Attempts to recover backups copied to tape may fail Attempts to recover archives imported from alternate appliances may fail Imported tape backup copies may fail recovery File level recovery of Exchange backups may fail
Reporting	There is no option to specify a custom from address for e-mail reporting
Security	Security issues resolved in release 10.0
Storage	NAS configuration may fail in environments that restrict ICMP Log data may accumulate and cause space issues Space issues may occur on the appliance due to backup unhashing failure Exablox NAS devices cannot be configured as stateless storage Failed Amazon S3 cloud storage mounts may produce a misleading error message
UI	Job inventory settings may not display correctly in Firefox V53 Values entered into the recurrance field for creating a schedule may display incorrectly The UI may not clearly indicate the risks associated with disabling encryption The UI may not sufficiently inform monitor users of their limitations XenServer VM names may not display on the Recovery page Sort by progress under the Active Jobs tab may not work properly Storage may disappear from the UI Text in dialog boxes may not wrap correctly The backup copy target list may become too large to close Backup IDs may not be visible in the Backup Catalog
Upgrade	Updates to version 9.1 may result in kernel panic Following update to 9.1.1-2, traffic may not be routable through OpenVPN

SUMMARY

ISSUE

RESOLUTION

Browse this section