7.1.1
Disabled false negative notification in the appliance Management Console about low RAM
7.1.0
Replication and failed verification
Backup job replicated to the secondary appliance could fail verification
Backup job created from a locally booted VM after the original backup job was deleted, and then replicated to the secondary appliance, still failed verification
Backup jobs on the secondary appliance failed verification because of the missing /raid/.ddfsar directory
Backup jobs that failed verification did not restart automatically after reconciling the secondary appliance
Backup jobs replicated to the secondary appliance could fail verification because not all data blocks were transferred
Error if a backup job was present in the replication queue, but then was deleted from the appliance before replicated
False positive verification of the replicated backup jobs after subsequent replication despite missing files
Replication progress did not show in the progress bar in the appliance Management Console › Replication › Status › Transfer Statistics group
Transfer Finish Date for the replicated backup jobs did not show in the appliance Management Console › Replication › Replicated Jobs
Monitoring and reporting
Boot verification data (that is, boot detection screenshot, boot verification result, and the latest restore point) is now sent to and visible in the Dashboard › Monitoring › Endpoints › Boot Verification column
Disaster recovery engine
Ignyte DR engine now supports compressed, deduplicated, mirrored, spanned, and striped volumes
If you enable the Ignyte DR engine for a Hyper-V host, backup of any VM hosted there will fail, and the job message logs will show a warning to switch to the Standard DR engine
When running a backup job for a client using the Ignyte DR engine, the system checks if the operating system is supported, and if all prerequisite software is installed. If not, the job message logs show a warning with details
Disks removed from the volume set of a DR image backup, which was made using the Ignyte DR engine, were still included in the next full backup
Failure to boot a DR image backup made using the Ignyte DR engine because of the missing boot device
Incremental backups made using the Ignyte DR engine could sometimes be corrupt because of incorrect calculation of extents in sparse and compressed files
Multiple connections error when running an incremental backup using the Ignyte DR engine if the relevant full backup was already deleted from the appliance
Spanned volumes in Windows Server 2019 were backed up successfully using the Ignyte DR engine, but the data was not available after restoring
Successful backup made using the Ignyte DR engine could miss some disk volumes
Deduplicated file system
Notification if the appliance needs more memory to ensure its top performance (appliance Management Console › Dashboard › Notices widget)
Improved replication processes by optimizing and increasing DDFS performance
Boot and boot verification
Notification on the number of backups currently booted on the appliance (appliance Management Console › Dashboard › Notices widget)
Virtual appliance for VMware now has 16 GB of RAM to enable boot capabilities by default
Virtual appliance for VMware now has 4 CPUs and virtualization turned on to enable boot capabilities by default
Non-system disks of the backup booted locally as VM on the appliance showed as offline
Boot orchestration settings did not reset to defaults after the appliance was re-initialized
Failure to remove a VM from a boot group in the appliance Management Console › Boot › Orchestration
Hyper-V
Only one backup job can now be performed at a time for a Hyper-V client (does not affect clients created before this update)
Backup of a VM in a Hyper-V cluster failed sometimes after the appliance firmware update
Hyper-V VMs renamed in Hyper-V Manager were not renamed in the appliance Management Console › Hyper-V
VMware
Message logs of the VMware VM backup jobs now include records about the CBT use
Only one backup job can now be performed at a time for a VMware client (does not affect clients created before this update)
Appliance continued to back up a VMware client, even after canceling the job, despite critically low space on its RAID
Consistent and verified VMware VM backups could still fail to restore because of the corrupted VM disks
Duplicate VMware connections in the appliance Management Console › Clients › VMware
Forever incremental VMware VM backups failed with Out of Memory error
Several backup jobs could run simultaneously for the same VMware VM client
VMware VM backup job was marked Successfully Completed despite the CBT-related errors, and its message logs did not include any relevant warnings
User experience and user interface
Column with version of VMware Tools installed on a VM client (appliance Management Console › Clients › VMware)
Notifications if boot orchestration started successfully or failed to start (appliance Management Console › Boot › Orchestration)
Option to filter VMware VM clients by datastore in the appliance Management Console › Clients › VMware
When restoring a DR image backup, the dialog box now includes a direct link to software downloads–that is, to the appliance Management Console › Settings › Downloads
Appliance Management Console now preserves the configured UI settings and layout after logging out and logging in again
Edited and updated the form for submitting support requests in the appliance Management Console › Support
Email notification about the appliance firmware updates does not include release notes now
Format of data presentation in the Duration column in the daily appliance report
Jobs in the appliance Management Console › Jobs › Scheduled Jobs are now sorted by Scheduled Date in ascending order by default
Updated text of notification that shows in the job message logs if there are no messages relating to the job yet
When browsing and restoring the backup data in the appliance Management Console, the dialog box now has uniform title presentation
When creating a new backup client in the appliance Management Console, the dialog box now shows the default values for the DR schedule and for the File & Folder schedule
Edited message shown when trying to set the local administrator password in the appliance Quick Start Wizard in the invalid format
Error messages in DR LAN settings in the appliance Management Console › Boot › Orchestration
Loading indicator disappeared before the interface of the appliance Management Console fully loaded when accessing the appliance remotely
Presentation of the dialog box that shows if the connection to the appliance is lost
Buttons to edit backup job schedules for VMware and Hyper-V clients were unavailable sometimes (appliance Management Console › Clients › Edit)
Edited titles of the setting groups and table columns related to backup retention across the appliance Management Console UI to be uniform and consistent
Failure to complete the appliance Quick Start Wizard because of the broken domain name check
HW Version column in the appliance Management Console › Clients › VMware did not support sorting
Inadequate filtering and sorting on some subtabs in the appliance Management Console › Jobs
Incorrect number of client records shown in the virtual appliance Management Console › Clients › VMware because the virtual appliance counted itself as a client and took up an empty record
Run and Save buttons in the appliance Management Console › Boot › Orchestration were unavailable sometimes
Various
Appliance now will reboot automatically after the kernel panic
Message logs for restore jobs now include information on where the data is restore from and to
UFS support for browsing and restoring, and for the protected space calculation
Appliance now suspends all operations if it cannot verify its serial number (UUID) for 72 hours
Edited text in the appliance Management Console › Settings › Security Certificate
Improved data transfer rate during replication in high-latency networks by increasing the TCP buffer size
Updated EULA
Updated help links in alerts that show when trying to restore a Hyper-V or a VMware VM backup without the client associated with the job
Updated help links in the job message logs in the appliance Management Console to lead to the Documentation Portal
Updated help links in widgets and dialog boxes in the appliance Management Console to lead to the Documentation Portal
Appliance continued to perform restore, even after canceling the job, despite critically low space on its RAID
Out of Memory error when importing or re-importing large file and folder backup jobs
A successful backup not yet transferred to the secondary appliance could have Transfer Finish Date set already in the appliance Management Console › Replication › Replicated Jobs
After the appliance lost connection to a Hyper-V host during the backup of a VM hosted there, it showed the host as connected, but with no VMs (appliance Management Console › Clients › Hyper-V › View Connections)
Appliance Network Share section in the appliance Management Console › Settings › Tools stopped responding and became unavailable if it contained a huge number of files
Client logs in the appliance Management Console failed to download sometimes because of the invalid symbols in the respective XML-file
Clustered Hyper-V VMs were not marked sometimes (appliance Management Console › Clients › Hyper-V › Clustered column)
Custom PKCS12 certificate could occasionally fail to upload to the appliance properly, and thus blocked all backup operations
Error when browsing and restoring a VMware VM backup to the Appliance Network Share (Error setting root directory. The response could not be parsed.)
Failure to change priority of the file and folder backups on a client (appliance Management Console › Clients › Edit)
Files and folders restored to the Appliance Network Share could retain their old permissions that could block access to them
Incorrect information about the active jobs for a client (appliance Management Console › Clients › Summary › Active Jobs column)
Incremental backup failed if only full backup from the booted VM existed, and the original full backup was deleted already
Job message logs consumed too much memory that resulted in poor appliance performance
Loss of network connection during a Hyper-V VM backup resulted in poor performance of the appliance, and blocked all backup and restore operations
Reload button in the Lost Connection dialog box was unavailable sometimes
Retention settings on the secondary (cloud) appliance did not apply to incremental backups of the configuration and database of the associated primary appliance
Two instances of the DR backup agent with different versions could be installed on Windows
7.0.7
Wipe Data in the appliance Management Console › Settings › Security is now visible in the Advanced mode only
Enforced synthetic full backup for Windows clients if any HDD volume included in the backup job was defragmented since the last backup
Occasional failure to apply backup retention settings on the secondary appliances resulted in rapid disk space fill-up
Option to bridge network was missing in the network options when booting a DR image or a VM backup
Appliance could occasionally lose connection to a Hyper-V host and all associated VMs
Appliance could not add connection to a Hyper-V cluster node with Failover Clustering feature installed, but ClusSvc service not running
Ignyte DR engine skipped EFI partitions during backup because it could not find the associated system volume
Occasional failure to show message logs for replicated jobs in the Management Console of some secondary appliances
Boot verification status icons in the appliance Management Console › Clients › Summary
Boot verification status icons in the appliance Management Console › Boot › Active
7.0.5
Backup jobs could get stuck during the deduplication process due to the DDFS deadlock
7.0.4
Retention settings for the DR image and VM backups now have the extended predefined ranges and are editable
Settings changed in the appliance Management Console › Settings › System Alerts would reset to defaults after some time
Inability to migrate to or change new retention settings for the DR image and VM backups in the appliance Management Console › Clients › Edit
Retention scans failed to process the list of jobs on the appliance and to delete those past the retention period
7.0.3
Occasional failure to perform a DR image or a Hyper-V incremental backup using the standard backup engine
7.0.2
Ability to export and import backup job schedules from and to the appliance
Ability to push client settings from the client context menu
Ability to set boot verification timeout
Beta version of the Ignyte DR engine
Critical notice if the appliance is running without DDFS (appliance Management Console › Dashboard › Notices widget)
Emails with replication alerts now include appliance UUIDs
Information if a Hyper-V VM is clustered (appliance Management Console › Clients › Hyper-V › Clustered column)
Information if the appliance RAID is encrypted (appliance Management Console › Settings › Appliance Status › RAID Info)
IPMI MAC and IP addresses, if applicable (appliance Management Console › Settings › Network Status)
Name of the network, in which the machine was booted (appliance Management Console › Boot › Active › Network column)
Name or IP address of the VM host (appliance Management Console › Clients › Summary › VM HOST column)
New default retention settings for DR image backups (appliance Management Console › Settings › Default Retention Policy)
Summary of the local and remote retention settings for backup jobs (appliance Management Console › Clients › Summary › Job Retention and Offsite Job Retention columns)
Log of the VMware VM backup jobs now contains information about the skipped independent persistent disk
Ability to migrate the existing DR image backups to the new retention settings
Ability to seed backup data from a primary appliance to an external USB hard drive to transfer the data to a datacenter offline
Ability to upload a custom SSL certificate instead of creating a self-signed one
Ability to wipe the appliance (erase data completely and permanently, reset to the default settings, unregister from the Dashboard, unregister from the cloud infrastructure, and re-initialize)
Option to wipe the cloud secondary appliance when wiping the primary one
All newly added clients with DR image backups use new default retention settings
Newly created appliance self-signed certificates are now valid for 3 years
Default email notifications and alerts sent by the appliance
Updated virtual appliance for VMware to hardware version 9 with ESXi 5.1 support
VMware VM backup will automatically switch to full if the VM configuration changes
Redesigned appliance Quick Start Wizard to be more streamlined and user-friendly
DDFS-AR is always enabled now
Disabled automatic Online DDFS Compact
Improved logic behind replication of only last successful job of the day
Name of the default retention policy per appliance in ConnectWise
Appliance would stop all operations if it did not communicate with the billing server
Hyper-V VM duplicated the client on the appliance when migrating between cluster nodes
Virtual appliance for Hyper-V did not run on Windows Server 2016 and Windows 10
After the appliance firmware update, the Immediately Delete Erred Jobs option became disabled (appliance Management Console › Jobs › Settings)
After migrating a client to the new retention settings, the Apply button was not available (appliance Management Console › Clients › Edit)
Automatically canceled backup jobs increased appliance memory consumption
DR backup agent did not show the list of Microsoft SQL Server databases due to request timeout
DR backup agent installation forced reboot of the target client running Windows Server 2012 with Microsoft Exchange Server 2013 installed
Block Level Deduplication Savings widget showed incorrect data (appliance Management Console › Dashboard)
Appliance closed an active support tunnel due to slow network connection
Appliance firmware update could be time-consuming due to slow internal file copy operations
Appliance occasionally lost connection to the DR backup agent on a Hyper-V host
DDFS stopped responding when trying to read and write more than 512 files simultaneously
Occasional accidental appliance configuration activation
Incorrect SNMP settings (appliance Management Console › Settings › SNMP)
DR image backup job could stay as pending infinitely
Excessive memory consumption by internal appliance processes
Failure to register a VMware VM with only numbers in its name
If ESXi was shut down, VMware VMs connected to vCenter showed incorrect status (appliance Management Console › Clients › VMware)
Ignyte DR engine did not back up disks with bad sectors
Incorrect open support tunnel (appliance Management Console › Dashboard › Notices widget)
Incremental VMware VM backup failed after shrinking VM’s virtual disk
Incremental VMware VM backup failed if the latest backup job was pushed back from the secondary appliance
Miscount of the saved bytes for incremental VMware VM backups (appliance Management Console › Jobs › History › Saved Bytes column)
Negative free space value on the Storage bar if the license was lower than the RAID space
Outbound access option in the DR LAN settings did not apply by default even if turned on (appliance Management Console › Boot › Orchestration › LAN)
Replication could not be started or stopped on the secondary appliance occasionally
Retention settings did not apply to some backup jobs occasionally
Inconsistent retention settings on the primary and on the secondary appliances
Sorting of clients by retention settings (appliance Management Console › Clients › Summary)
Swapped EXTRA and FAILED_VERIFICATION remote status filters (appliance Management Console › Replication › Replicated Jobs)
VMware connections could not be shown if a VM did not have additional properties
VMware VM backup failed when saving hardware configuration
DR image backup using the Ignyte engine had false positive results for volumes with invalid layout
Successful backup jobs could occasionally be reported as canceled in the Dashboard
Isolated on a private subnet option was unavailable when booting backups on some appliance models
Registration of a Hyper-V VM could occasionally take up to 30 minutes
SNMP could crash when retrieving metric data
Replication with byte-level delta compression
User experience and user interface
System tab was renamed to Settings
Backups section on the Settings tab
Security section on the Settings tab
Release Notes link in the Help menu
Documentation link in the Help menu
Help buttons for Wipe Data, Appliance Network Share, and Audit Log on the Settings tab
Help link for the DR engines in Clients › Edit
All subtabs related to jobs on the Server tab were moved to the Jobs tab
Server › Storage subtab was renamed to Deduplicated File System and moved to the Settings tab
Default Retention Policy, Unreferenced Data, Shared File Sets, and Job Schedules were moved from the Clients tab to the Settings tab
Clients › Settings was renamed to Automatic Job Management and moved to the Settings tab
Clients › Software was renamed to Downloads and moved to the Settings tab
Server › Reporting was moved to the Settings tab
Link to download the bare-metal restore disk image was moved from Support › Portal › What’s New to Settings › Downloads
Submit Support Request section on the Support tab
All help buttons on the Settings tab now lead to this Documentation Portal
Password, Remote Access, Certificate, and Wipe Data were moved to Settings › Security
HTTPS-only option was moved to Settings › Certificate
Updated and edited descriptions of the fields and section in Clients › Edit
Double-clicking Audit Log on the Settings tab could break user interface and layout
Inconsistent presentation of the Storage bar and the respective notices for the same disk space thresholds in the appliance Management Console
Downloads section on the Settings tab was empty after update to v7.0
Missing icon in Clients › Edit › Boot group
Orchestration tab was not visible on some appliance models
Missing boot verification result icon in Clients › Summary and Boot › Active when browsing with Google Chrome 77.0.3865
Server tab
What’s New section in Support › Portal
Link to the knowledge base article in Jobs › Retention