Disaster recovery backup agent

DR backup agent for Windows and the standard DR engine now require at least Microsoft .NET Framework 4.6.2

DR backup agent cannot now be installed on a client remotely right from the CFA Management Console (that is, pushed when adding or editing a client). Instead, pushing the backup agent will only update it if it was installed already

Backup and restore

DR image backup jobs using the standard DR engine could fail if the client returned null response when requested to attach remote storage

After making a Linux file and folder backup and then restoring it to the Appliance Network Share, the restored data was not shown in the CFA Management Console > Settings > Tools > Appliance Network Share, and was unavailable through network

DR image backup jobs using the standard DR engine could fail after running for a long time (An unexpected network error occurred)

Boot and boot verification

CFA would schedule backup jobs for boot verification only on alternate days (regardless of system settings) because of improper handling of time zones and limit to verify only one backup job per day

Monitoring and reporting

CFA would not send information to the Dashboard about completion of a backup job because of the false-negative failure to send information about the start of that job. This resulted in discrepancies between the backup job statuses shown in the CFA Management Console and in the Dashboard

CFA failed to send the daily report with boot verification screenshots included


Option to reset Changed Block Tracking for VMware VMs right from the CFA Management Console


Reviewed and edited texts in the CFA job message logs for consistency in use of the DR engine names


Disaster recovery engine

DR image backup job failure when committing the backup metadata because the system could not find the metadata files

Incremental DR image backup job failure because the DR engine was unable to read the volume information

Replication and failed verification

Improved the replication process by making the CFA to transfer the SBMF data only once—if and after the replication completed successfully

When configuring replication, the Propagate Manual Delete option is now cleared by default (CFA Management Console > Replication > Mode/Options > Options > Remote Appliance Information)

CFA could respond with significant delays or even stop responding during a high-rate replication process

Boot and boot verification

Option to set DNS when configuring the DR LAN settings for boot orchestration in the CFA Management Console > Boot > Orchestration > LAN

Monitoring and reporting

CFA shows a warning that it is unable to connect and send monitoring data to the Dashboard not only if the account credentials used to register the CFA in the Dashboard changed, but also if the trial period for the account ended, and if the account was locked because of the security reasons


CFA now shows the status and details of the VMware Tools installed on a VMware client (CFA Management Console > Clients > VMware > VMware Tools column)

CFA would continue making full backups of a VMware VM instead of incremental even if the previous full backup completed successfully with CBT enabled

Message logs of a VMware VM backup job did not show any notification when the CFA was making a full backup instead of incremental if CBT was disabled at the virtual disk level

User experience and user interface

Reworded the error message shown in the message logs of a backup job if the job fails because of the Bacula Director service restart

After adding a Hyper-V cluster to the CFA, the Activate Configuration button would become active for a few seconds

Broken links to download the DR backup agent for Linux and the DR restore disk (CFA Management Console > Settings > Tools > Downloads)

Storage bar in the CFA Management Console would remain green despite the CFA showed a storage space warning or alert


Message logs of a backup job now include extra information related to the job (CFA firmware version, backup client ID, backup client IP address, backup agent ID)

CFA now uses SMB2 by default unless it was previously configured to use SMB1 before this update

Legacy retention settings shown in the properties of a client (CFA Management Console > Clients > Summary > Properties > Basic Configuration)


Disaster recovery backup agent

Backup agent 8.0 now supports Windows versions only as of Windows 7 SP1 and Windows Server 2008 R2 SP1

Updated installer of the backup agent to include components of the Ignyte (Standard) DR engine

Failure to install the backup agent on Windows 7 because of the missing required updates despite they are already present in the system

Disaster recovery engine

Ignyte is now the default standard DR engine

Improved incremental backup of the hard drive volumes after defragmentation

Improved speed of upload to the SMB share using the variable buffer size (from 64 KB to 1 MB)

After changing the DR engine for a Hyper-V client (CFA Management Console > Clients > Edit), backups failed because the change was not applied on the client side

Standard DR engine could not start backup if a ReFS volume was present in the system

DR image backup failed when the standard DR engine was trying to retrieve metadata of a drive volume not included in the backup

Standard DR engine failed to create a DR image backup of a system with an encrypted volume even if it was not included in the backup

Backup and restore

Ability to download folders from backups when browsing and restoring

Support of NVMe drives for bare-metal restore using the DR restore disk

Extra global backup settings (CFA Management Console > Settings > Backups > Advanced Settings)

When starting backup of a physical machine manually, option to back up as DR image is selected by default (CFA Management Console > Clients > Summary > Manual Backup button)

Restoring files and folders to the CFA network share failed with Unknown stream ignored error

Replication and failed verification

Improper handling of files smaller than 50 MB in a backup job, which was replicated and interrupted while in progress, resulted in errors and different statuses of that job on the primary and on the secondary CFAs

Propagate Manual Delete option did not work (CFA Management Console > Replication > Mode/Options > Options > Remote Appliance Information)

Boot and boot verification

Options to enable boot verification and to set its timeout are now configured per client, but not globally (CFA Management Console > Clients > Edit > Boot)

Changes to the settings of one boot group (where a client belongs) applied to all other boot groups (CFA Management Console > Clients > Edit > Boot)

Monitoring and reporting

Email alerts and notifications sent by the CFA now include its serial number (UUID)

If you delete a client from the CFA, the system also removes all relevant monitoring data from the Dashboard

CFA now uses proxy, if configured, to communicate with the Dashboard

CFA now reports a backup job as definitely failed only after all attempts to retry or rerun it on errors (if configured in the CFA Management Console > Clients > Edit > Error Recovery)

An archive automatically attached to the support request sent from the CFA Management Console > Support contained not all log files


CBT is now automatically enabled before backup at both VM and virtual disk levels by default

Backup of a VM with enabled CBT failed with a FileFault error when querying for the changed disk areas

Restore of a VM backup to ESXi 6.7 U3 or vCenter 6.7 U3 failed if the backed up VM had automatic video card detection

VM backup failed if the retrieved SSL certificate thumbprint from the host was null because of the network issues

User experience and user interface

Diagnostics tab in the CFA Management Console

If username or password of the account used to register the CFA in the Dashboard is changed, the system now shows a notification in the Notices widget (CFA Management Console > Dashboard)

When a backup job is pushed from the secondary CFA to the primary CFA, the system now shows a notification in the Notices widget (CFA Management Console > Dashboard)

Redesigned UI of the CFA Management Console

Renamed DR engine options available when editing a client in the CFA Management Console > Clients > Edit (Ignyte (beta) to Standard, and Standard to Legacy)

Updated text of the message shown after connection testing failed if replication was configured only on the primary CFA, but not on the secondary CFA (CFA Management Console > Replication > Mode/Options > Remote Appliance Information > Test Connection)

Arrangement and presentation of sections on the Settings tab in the Management Console of the secondary CFA

CFA did not log the user out of the Management Console after restart or shutdown

Garbage Collection History table did not update automatically after the garbage collection process completed (CFA Management Console > Settings > Tools > Deduplicated File System)

Inconsistent date formats in the CFA Management Console

Incorrect default retention policy settings for VM clients shown when adding a VMware connection (CFA Management Console > Clients > VMware > Add Connections)

Incorrect sorting of VMs in the CFA Management Console > Clients > VMware using the Allow CBT column

Incorrect version of the operating system shown in the properties of clients running Windows Server 2019

Information about the VMware host did not update automatically in the CFA Management Console > Clients > VMware > Host Version column

Invalid port displayed when viewing the Hyper-V connections (CFA Management Console > Clients > Hyper-V > View Connections)

Misplaced checkboxes when browsing and restoring backups in the CFA Management Console

RAID status did not update automatically until the Refresh button was clicked (CFA Management Console > Settings > Tools > RAID Configuration)

Secondary CFA showed progress of a backup job started on the primary CFA

When logging in to the CFA Management Console, the login form was not blocking after sending the request and until receiving the response

Diagnostics item in the Help menu in the CFA Management Console


Quick Start Wizard now shows Network Interface Configuration first (instead of the login dialog) if the CFA is unable to access internet

Job message logs now include details for all Hyper-V and DR image backup and restore errors (if any)

Seeding is unavailable now if replication is not configured (CFA Management Console > Settings > Tools > Seeding)

Increased size of the file that reserves disk space on the CFA up to 10 GB

A backup job, which should be deleted under the retention policies, could not be deleted from the primary CFA if it failed verification on the associated secondary CFA

A ZIP file downloaded when browsing and restoring a backup job contained no files if unpacked using the Windows built-in tool

Failure to restore the CFA configuration because of the incorrect processing of the uploaded configuration file (CFA Management Console > Settings > Tools > Save/Restore Configuration)

Negation operator (!) did not work when used in filters in the CFA Management Console > Jobs > History

When trying to search files in a client with no backup jobs performed, the system showed an error instead of notification (CFA Management Console > Clients > Summary > Search)

Recover Catalog feature (CFA Management Console > Jobs > Importing Jobs)