This document describes new features introduced in the 10.3 release. For complete upgrade instructions and considerations, see the Upgrade Guide for Recovery Series and Unitrends Backup.
Unitrends 10.3 builds on the success of Unitrends 10.2.1 with the following enhancements:
Windows image-level protection
You now have the option to protect Windows assets at the disk and volume level with image-level backups. This option delivers lightning fast backup performance of Windows servers. For details, see Windows Image-level Protection Overview in the Administrator Guide for Recovery Series and Unitrends Backup.
Long-Term Data Management
10.3 appliances manage retention with the new long-term data management feature. Use this feature to create a customized inventory of weekly, monthly, and yearly retention points for your protected assets. For details, see Managing retention with long-term data management in the Administrator Guide for Recovery Series and Unitrends Backup.
This release adds host-level support for vSphere 6.7 environments.
vSphere 6.7 Support
XenServer 7.3 Support
This release adds host-level support for XenServer 7.3 environments.
This release introduces a performance optimization that may reduce the duration of inline deduplicated backup jobs - particularly those containing large numbers of small files. You may also notice a slight improvement in backup copy performance.
||The above enhancement is only available on Unitrends Backup virtual appliances and Generation 8 Recovery
User Interface Enhancements
Release 10.3 includes the following usability enhancements:
- This release enhances Backup Catalog capability with a new Backup Browser feature. The Backup Browser provides advanced search and filter options to quickly search for, filter, and sort the backups stored on the appliance.
- Click ? in the upper-right corner of a dialog to view related procedures in the Administrator Guide for Recovery Series and Unitrends Backup. This enhancement is a work in progress. We will continue to add help to dialogs in upcoming releases.
- Multiple jobs can now be simultaneously canceled.
- The column "Database Name" has been renamed "DB/VM Name" in the Backup History and Backup Failures reports.
- The Legal Hold Backups report has been relocated to the Retention report category.
The table below lists customer-discovered issues that were promptly resolved in this release. For details on each defect, see the Customer-Found Defects KB article.
- Resolved an issue where Hyper-V backups failed with volsnap errors.
- Resolved an issue where NAS backup storage devices misleadingly appeared to lack the required free space.
- Resolved an issue where AHV disks with capacities other than multiples of 1024 bytes could not be backed up.
- Resolved an issue where NAS shares with mount names containing spaces could not be backed up.
- Resolved an issue where assets with names longer than 31 characters experienced backup failures.
- Resolved an issue where appliances using bonded NIC configurations could not back up AHV assets.
- Resolved an issue where appliance hostnames longer than 31 characters were not restricted.
|Backup Copy (Cold)
- Corrected cold copy job to NAS target failures.
- Resolved an issue where the cloudadm repair function did not work properly for docker.
- Fixed cold backup copy imports from tape that failed with input/output errors.
- Resolved an issue where NAS, FC, and iSCSI cold copy targets did not automatically mount/unmount as required by cold copy jobs.
- Corrected format 2 cold backup copy failures that occurred when a format 1 backup was included in the job.
- Resolved an issue caused by RDX devices that report a dock serial number rather than a disk serial number.
- Resolved an issue where AWS GovCloud was not available as a backup copy target.
- Resolved an issue where the CloudBlkSize general configuration (master.ini) setting did not restrict excessively large values.
- Resolved unsuccessful attempts to add Google Nearline buckets as cold backup copy targets.
- Resolved an issue where, in the case of a disk rotation scheme, fulls were not being imported from the same media as the rest of the backup group.
|Backup Copy (Hot)
Fixed hot backup copy failures that were observed with the error message — "Fail to approve pending copy request - Query to add."
Resolved an issue where the migration script could fail on a stateless Unitrends Backup appliance using iSCSI primary storage.
- Resolved an issue where stateless appliance recovery failed for Unitrends Backup appliances on XenServer.
- Resolved an issue where DR system state recovery could fail with vague database errors.
Resolved an issue where attempts to re-image Recovery Series appliances from USB media were unsuccessful.
Resolved an issue where the default ConnectWise WSDL was incorrect.
- Resolved an issue where Hyper-V file-level recovery failed with fusectar errors when random access mode was enabled.
- Resolved an issue where Mac and Windows recovery jobs failed to queue when the target directory contained spaces.
- Resolved an issue where the WinPE environment could hang, resulting in Windows replica failures.
- Resolved an issue where clean teardowns were not enforced for VM replicas created from backup copies.
- Resolved an issue where compliance reports were being sent despite a complete absence of data copy access jobs on the appliance.
- Resolved an issue where the Backup Copy Job Notifications report depended on internet access to load certain image files.
- Resolved an issue where source appliances were permitted to upgrade to newer versions than their associated cloud targets, leading to hot backup copy job failures.
- Fixed slow or unresponsive cloud target active directory login attempts.
Resolved an issue where kernel updates of Unitrends appliances deployed as installable software were causing driver compatibility problems.
- Corrected cold backup copy filters that were producing counterintuitive results.
- Resolved an issue where the appliance column sorted itself in the opposite order indicated by the UI.
- Resolved an issue where the release features pop-up displayed after every login with active directory credentials.
- Resolved an issue where VMs did not display in the UI for Hyper-V clusters with greater than 16 nodes.
|VM Instant Recovery
Resolved a VMotion issue that could cause instant recovery failures.