This document describes enhancements and fixes introduced in the 10.4.8 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series and Unitrends Backup.
Search for and recover files from Windows image-level backups
You now have the option to index Windows image-level backups so you can quickly search for and recover individual files.
||Assets with high-frequency backups or with very large file counts can add considerable load to the appliance.
Consider appliance load when enabling this option for these types of assets.
To index an asset's image-level backups, enable the Index Image-Level Backups option on the Edit Assets page:
SMB 2.0 on appliance Samba shares
Beginning in release 10.4.8, the SMB 2.0 security option is enabled by default on Unitrends appliances. The following requirements apply to appliances configured with SMB 2.0:
||SMB 2.0 Requirements
|The Unitrends agent must have access to the appliance's SMB 2.0 Samba share to perform backup and recovery operations. These requirements apply:
smbadm add-key -u samba@<applianceIP>
|SMB 2.0 must be enabled on the Windows server so that the Unitrends agent can access the appliance's SMB 2.0 Samba share when performing backup and recovery operations.
Note: If the backup appliance is running a pre-10.4.8 release and is configured to use the SMB 2.0, the following must be enabled on the Windows server: SMB 2.0 and Insecure Guest Login.
|To use a CIFS share for the recovery, SMB 2.0 must be enabled on the target Windows asset.
Note: Backup appliance running a pre-10.4.8 release – If the appliance is configured to use SMB 2.0, the following must be enabled on the target Windows asset: Insecure Guest Login and SMB 2.0.
||To perform backup and recovery operations, SMB 2.0 must be enabled on each node in the farm.
- Backup appliances running pre-10.4.8 releases – If the appliance is configured to use SMB 2.0, the following must be enabled on each node in the farm: Insecure Guest Login and SMB 2.0.
- SharePoint 2007 on Windows 2003 and prior are not supported on SMB 2.0 appliances. To configure your appliance to use SMB 1.0, see How Unitrends support SMBv2.
- SharePoint may require custom client configuration for use with SMB 2.0. If SharePoint backups do not run successfully, see this Microsoft article for client configuration details: SharePoint Ports, Proxies, and Protocols...An overview of farm communications.
|To push install the Windows agent, SMB 2.0 must be enabled on the Windows asset.
- If SMB 2.0 is enabled on your Unitrends appliance, the agent push is NOT supported for the following: Windows 2003 R2, Windows XP, Windows Vista. Agent push to these operating systems is supported on appliances where SMB 1.0 is enabled. To configure your appliance to use SMB 1.0, see How Unitrends support SMBv2.
- Backup appliance running a pre-10.4.8 release – If the appliance is configured to use SMB 2.0, the following must be enabled on the Windows asset: Insecure Guest Login and SMB 2.0.
|To run a Windows replica on Hyper-V, SMB 2.0 must be enabled on the Hyper-V server.
Note: Backup appliance running a pre-10.4.8 release – If the appliance is configured to use SMB 2.0, the following must be enabled on the Hyper-V server: Insecure Guest Login and SMB 2.0.
This release includes updated Windows core and bare metal agents. The 10.4.8 core agent is recommended for all Windows assets and is required for Windows fixes in this release.
||For Windows image-level backups of UEFI systems, backups may auto-promote to a new full after upgrading from a pre-10.4.4 agent if a Microsoft System Partition has the same disk/partition number as another volume.
The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading
- Hyper-V incremental backups of newly migrated VMs – Resolved an issue where the next backup taken after the VM had migrated to a new host could include all data on the VM disks. With this fix, only changed blocks are included in the backup. This fix requires the 10.4.8 Windows agent.
- Queued jobs not being copied to the target – Resolved an issue where older incrementals could remain 'stuck' in the hot backup copy queue if a newer backup had already been copied to the target. This fix ensures the oldest backup of a given asset is copied first.
- Tearing down the Hyper-V instant recovery session – Removed a redundant unmount command that resulted in adding a failed to unmount error message to hyperv_instant_recovery_destroy.log, even though the session had been successfully unmounted and torn down.