›  Backup & Disaster Recovery  ›  Release notes  ›  8.x

Release notes for Backup & Disaster Recovery 8.x

On this page

8.10.0

Support of SMB 3.0 protocol by the appliance

Option to specify network for a VM during the restore so that the VM can be immediately used after the restore

DDFS shredder statistics (appliance Management Console › SettingsToolsDeduplicated File System)

Upon logging in to the appliance Management Console for the first time, the system now shows the Terms of Service to accept

Turned off anonymous access to the appliance network share to eliminate the NULL Session vulnerability

Increased the speed of the backup data replication by optimizing the metadata compression

Retention policies are not applied now to those backup jobs that are replicated at the moment

Improved the loading speed of the appliance Management Console

After updating the appliance firmware to version 8.5, the incremental DR backup jobs, when run concurrently, started taking four times longer to complete

Browse and restore failure (error Invalid partition data!)

VMware VM restore failure (error Failed to create VM on restore)

Dynamic disks were not available for browsing and restoring

Upon rebooting a VM booted on the appliance (Management Console › BootActive), the VM stopped responding with the libivrt.xml file spoiled pointing to the disk images in the initial backup job

VM boot verification on the appliance could occasionally fail and show the message “Guest has not initialized the display (yet)”

The appliance could not send an alert email about no free space

After canceling a DR or a VM restore job in progress, the dialog with results showed two records about the canceled job instead of one

The system failed to load any information in the Save/Restore Configuration section (appliance Management Console › Settings)

After replacing a failed disk in the RAID and rebooting the appliance, or after restarting the appliance with a failed disk in the RAID, the appliance booted in the emergency mode with inoperable network instead of the NoRAID mode as designed

An email notification sent by the appliance upon the license server communication failure included incorrect contact phone numbers

Appliance could occasionally suggest updating its firmware to the previous version

Backup jobs could not be deleted from the appliance because the system boot manager blocked their removal despite there were no active booted VMs

Failure to completely delete a backup job from the appliance (the system removed the job from the Management Console, but the files and metadata associated with the job were still present on the appliance RAID)

Occasional warning Insufficient Storage Space on /run/initiramfs/overlayfs in the Notices widget in the appliance Management Console

Error after starting the appliance in the NoRAID mode and logging in to its Management Console

8.9.0

Support of 4K sector hard drives and virtual disks for backup and restore operations

Support of Hyper-V clusters for backup and restore operations

Support of VMware HotAdd transport mode that improves performance and increases the speed of VMware VM backups

Option to check if the DR image restore disk supports the RAID controller of the target computer to properly perform the restore

Updated virtual CFA for VMware to use hardware version 11 supported by ESXi 6.0 and later

Improved handling of multiple running VMware VM backup processes so that if one process hangs or stops, and requires restarting, it does not affect the other running backup processes

The CFA operating system now supports the XFS trim/discard for SSDs to decrease the number of writes, increase writing throughput, and thus prolong the drive service life

If free disk space on the CFA is critically low, all running jobs are canceled, new jobs cannot be started, all booted VMs are suspended, and new VMs cannot be booted

Network adapter type in the virtual CFA for VMware from E1000 to VMXNET 3

Hyper-V backup failure because the DR engine could not properly include and exclude the selected disks within the volume set (error Failed to start SnapshotSet)

System logs of the CFA were full of error messages regarding the failure to push the monitoring statistics (pushing monitoring statistics failed)

Every second subsequent incremental DR image or Hyper-V backup job took more time than the first incremental backup even with no significant changes to the backup data set

CFA could not start properly because of the incorrect startup settings generated after the firmware update (invalid /raider/configs/bay.properties file)

The CFAs with small DOM could not boot after diagnostics

Backup jobs could not be deleted from the CFA because the system boot manager blocked their removal despite there were no active booted VMs

If the CFA was hard restarted, the system database could not be loaded automatically

The CFA failed to update the system time and date via NTP servers when configured manually in the Management Console › SettingsDate/Time (error Update of time failed. Please check the configuration or try again later)

After the boot verification of a backup was interrupted (for example, by hard restart or shutdown of the CFA), the system failed to boot any new VMs

DR image backup failure because the DR engine could not properly include and exclude the selected disks within the volume set (error Couldn't prepare backup ranges for {GUID}\Disks\harddiskN)

After an unexpected restart or shutdown of the CFA, the jobs that were running before the event remained in the system database, but were not visible in the Management Console. Also, those jobs were not affected by the backup retention policies, and thus took the CFA disk space.

After deploying a new virtual CFA for VMware and upon its first boot, the system could not mount DDFS, and thus the CFA was not usable (error block dedup setup failed)

After updating the CFA firmware from version 8.7.5 to 8.8.0, the Management Console of the CFA could not be loaded and was unavailable (failure to start the stark service)

DR backup agent could not work in Windows with FIPS mode turned on because of the non-approved cryptographic algorithms

8.8.0

The CFA now shows the amount of time a booted VM has been running and available

The CFA now shows the ID of the backup job, from which the VM was booted

Option to enable CFA to collect and record performance data about its boot process for profiling and troubleshooting

To improve the connection to and interaction with the CFA, the system now limits the metadata transfer rate if the network bandwidth for replication is limited (CFA Management Console › ReplicationMode/Options)

To avoid system overload, the CFA does not now pre-generate and show the VNC addresses used to access the booted VMs via a browser-based VNC viewer

NIC bonding settings are now available again for changing and configuring via the CFA Management Console

During the Hyper-V backup, if the backed up VM had two or more virtual disk files (VHDX) attached with the same name, but with different paths, the CFA would back up only the latest detected one, while overwriting the others

The time zone set manually in the CFA Management Console was not applied at the core system level and thus shifted the backup start timings

DR image backup failed with the CRC data error (bad blocks)

DR image backup jobs failed with error The system cannot find the file specified

Interrupting (restarting the CFA during) the process of conversion of a VM booted on the CFA to a backup resulted in the inconsistent backup data

NullPointerException error during the Hyper-V VM backup restore

Missing step to configure the network switch in the restore wizard for Hyper-V VM backup

When browsing and restoring a DR image or a VM backup, and if network connection with the CFA was lost, browse and restore could not be performed anymore, no protected space was shown for all jobs, and boot verification failed with no boot device available

No notification shown in the Notices widget after starting the support tunnel and then restarting the CFA

The time zone set manually in the CFA Management Console was not set at the core system level, but was shown correctly in the Management Console

When updating CFA firmware to version 8.7.x, the CFA lost the gateway and the update did not complete

After updating firmware to version 8.7.3, the CFA had insufficient disk space for operating system and database to work properly (error Insufficient Storage Space on /run/initramfs/overlayfs)

After updating firmware to version 8.7.x, the CFA could not start properly because of the incorrect startup settings (invalid /raider/configs/bay.properties file)

After updating the CFA firmware from version 8.6.1 to 8.7.3, the service license became invalid, and the CFA had to be registered in the Dashboard again

Failure to import backup jobs if the total number of the backed up files for all jobs on a client exceeded certain value

Updating the CFA firmware from version 8.6.1 to 8.7.3 resulted in complete CFA re-initialization

When submitting a support request, the CFA ignored the SMPT port set in the email settings, and always tried to send emails using port 25

When trying to access a primary CFA remotely from the Dashboard, the system redirected to the wrong CFA

8.7.5

CFA now writes data to DDFS always from the beginning by default, but not sequentially

8.7.4

Improved DDFS and replication performance by decreasing data fragmentation and thus optimizing data read operations

Failure to access the CFA remotely from the Dashboard after the lasting disconnection (Error on getting browse URL)

Failure to back up a Hyper-V VM that included a virtual disk with the uppercase file name extension (error No disks for job)

8.7.3

CFA Console Configuration Utility failed to update the current network configuration when changed in the Management Console and showed a message that the network was not configured (when in fact it was)

After changing the DNS settings (CFA Management Console › SettingsDNS) and restarting the CFA, the system reverted the settings to how they were before the change

CFA could sometimes stop replicating backup data because of the process deadlock and showed the Stalled replication status (CFA Management Console › ReplicationStatus)

After updating the CFA firmware to version 8.7.0, 8.7.1, or 8.7.2, the Management Console failed to load and an empty screen was shown instead

Secondary (cloud) CFA lost connection to the Dashboard and could not be accessed remotely

When booting the CFA with encrypted RAID in the NORAID mode, the system still mounted the RAID

8.7.2

After updating the CFA with an exported network interface (CFA Management Console › SettingsNetwork AdaptersExport Virtual option) to firmware version 8.7 or 8.7.1, and then turning the export off, the network interface configuration broke that led to the CFA could not back up and recover data

After updating the CFA connected to two different subnets on two network interfaces to firmware version 8.7 or 8.7.1, the CFA lost network connectivity because of the broken routing

8.7.1

Backup & Disaster Recovery now requires enabling NTLMv2 authentication on the protected client to establish connection with the CFA, and to properly make Hyper-V and DR image backups

After updating the CFA firmware to version 8.7, DR image backups started to fail because the CFA had no SMB users for the DR backup agent to connect to the CFA network share (error The network name cannot be found)

After updating the CFA firmware to version 8.7, the system stopped generating URL addresses for NoVNC connections to booted VMs, but showed only ports instead (CFA Management Console › BootActive)

After unsuccessful update of the CFA firmware to version 8.7, DDFS could be mounted several times instead of only once that led to unexpected service behavior

After updating the CFA with configured NIC bonding to firmware version 8.7, NIC had no IP address assigned

After updating the CFA firmware to version 8.7, network settings on a secondary (cloud) CFA were not available (CFA Management Console › SettingsNetwork Adapters)

8.7.0

Major update of the CFA core operating system to improve security and reliability, and to ensure the long-term support

After updating CFA firmware to version 8.7, NIC bonding settings are now not available for changing via the Management Console (if they were configured before the update) or not shown at all (if they were not configured before the update)

Default number of VMs that can be booted on the CFA depending on its model

When the CFA is creating a backup job from a VM booted on it (fallback job), the system shows a notification in the CFA Management Console (DashboardNotices widget, and SettingsReboot/Shutdown) to inform about potential data loss upon the CFA restart or shutdown

Improved management of needless files that are left after each new Hyper-V VM backup and can take extra space

DR image and Hyper-V backups failed after updating CFA firmware to version 8.7 (error Storage added but is unavailable)

DR image backup using the standard DR engine was marked as Successfully Completed despite no disks were backed up (error No disks for job {job-name} in directory ...)

After changing the content of a file in a Hyper-V VM, and then backing up the VM, content of the file in the backup remained unchanged

Incorrect network name shown in the CFA Management Console › BootActive for a VM booted on the bridged network

After updating CFA firmware to version 8.7, client names in the Client column in the CFA Management Console › JobsRecent Jobs were not shown

Buttons on the upper right (Refresh, Activate configuration, and Logoff) in the CFA Management Console were not shown after reducing the screen resolution

8.6.1

After updating the CFA firmware to version 8.6, backup of Microsoft Exchange Server and SQL Server failed because of the changes to the default VSS configuration

8.6.0

Backup

New default retention policies for backups. New policies apply only to the newly setup and configured CFAs. Previously configured CFAs keep their current retention policies even after firmware update to 8.6

After updating CFA firmware to version 8.6, the system automatically converts all existing LiveBMR backup jobs to the file-level backup jobs

DR image backup and all related settings are now available only for clients running Windows

DR engine now enforces full DR image backup if the system detects changes in the disk layout of a client between incremental backups

After DR image backup of a client with GPT disk containing only EFI system partition, DR image was browsable, but could not be booted on the CFA because GPT disk was excluded from backup

DR image backup could fail because standard DR engine included non-critical system state components (with NotSystemState flag) when creating VSS snapshot

Incremental DR image backups failed on the systems that had several instances of the same VSS writer (error An item with the same key has already been added)

Restore

Support of LiveBMR jobs for bare-metal restore

Windows LiveBMR restore disk image from the CFA Management Console › SettingsDownloads

LiveBMR option when editing the file set of a client (CFA Management Console › ClientsEditFile Set)

Hyper-V

Backup jobs that started simultaneously for multiple VMs hosted on the same Hyper-V host could result in some of those jobs finished successfully with warnings or failed after numerous retries

Hyper-V VM backup using the standard DR engine could fail because metadata file path created by VSS for VM snapshots exceeded Windows maximum length of 255 characters (error The system cannot find the path specified)

Backup agent

DR backup agent could crash while parsing output data from DR engine (error System.OutOfMemoryException)

DR backup agent installers for non-supported operating systems (macOS, FreeBSD, Solaris, NetWare, OpenServer, HP/UX, and AIX) from the CFA Management Console › SettingsDownloads

Various

After DR image or VM backup of a Windows machine in the hibernate state or with Fast Startup (Fast Boot) turned on, the backup could not be booted on the CFA

VMware-related functionality on the CFA stopped working if there was at least one registered VMware VM with NVMe controller (Note: CFA still does not support backup of VMware VMs with NVMe controllers)

CFA could incorrectly detect failed verification of a backup job during re-importing and thus show the job as Successfully Completed

8.5.0

Boot

Ability to connect to VMs booted on the secondary CFA (set up in the cloud) via web-based VNC connection

Improved safety of data of a VM booted on CFA by preventing deletion of the backup job, from which the VM was booted, until another backup is created from the booted VM

Safeguarded integrity and consistency of data of a VM booted on CFA during the VM backup by preventing all manipulations with the VM (settings editing, power management, backup, deletion) until backup is completed

VMware

Increased timeout to detect completion of a VMware VM backup job from 10 min to 1 hour so the system would not block its progress too early and mark it as failed

CFA can now connect to VMware vCenter 7.0—resolved error VI SDK invoke exception.dom4j.DocumentException: null Nested exception: null)

Hyper-V (beta functionality)

Standard DR engine now supports Hyper-V-related functionality (agentless VM backup, restore, browse and restore)

Ability to restore Hyper-V VMs to a host with Hyper-V version different from the one they were backed up from (according to the restore compatibility matrix)

Hyper-V subtab in the CFA Management Console › Clients is now available by default

When restoring a Hyper-V VM to another Hyper-V host, if network switch configurations of the VM and the host mismatch, it is now possible to manually map virtual switches of the VM to virtual switches on the host

To ensure data consistency at the time of backup, CFA enforces full backup of Hyper-V VM clients if integrity of files necessary for incremental backup was violated

8.4.1

System showed false-negative status (Completed With Errors) for DR image backup jobs made with Standard DR engine

After updating CFA firmware to v8.4.0, time to complete an incremental DR image backup increased significantly because of the issues while cloning backup job files

8.4.0

After updating DR backup agent on a client, the system may run the next scheduled DR image backup for that client as full (regardless of the scheduled backup level), and then change it to what was set before. (Note: After updating to version 8.4, the system will definitely force this behavior.)

DR image backup failed because of the errors with VSS writers not critical for getting basic backups

LiveBMR backup job marked as Successfully Completed despite errors failed to replicate to the secondary CFA. This prevented replication of other backups in queue

LiveBMR backup job was marked as Successfully Completed despite errors (error java.lang.IllegalArgumentException: Invalid path)

LiveBMR backup jobs with ASR writer data failed to import, and hence could not be deduplicated, replicated, browsed, and archived

If CFA had proxy enabled and configured (CFA Management Console › SettingsProxy), this could result in CFA performance slowdown, or even prevent CFA from completing its tasks (for example, stop DR image backups)

After restarting CFA, list of VMs (if any) in the CFA Management Console › ClientsHyper-V could sometimes be empty

Layout and styles of elements in the CFA Management Console › JobImporting Jobs so the information in the lower part be more visible and readable

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

After booting a backup job as VM on the CFA, and then deleting that backup job, the system failed to apply and save changes to the booted VM

VMware VM backup jobs could occasionally stop progressing, and hence prevent the following backup jobs from running because of the ‘concurrent job’ limit

8.3.0

Push Backup Agent functionality was replaced with Update Backup Agent, meaning that DR backup agent for Windows cannot now be installed on a client remotely right from the CFA Management Console (that is, pushed when adding or editing a client). Instead, backup agent can be only updated remotely if it is already installed, running and paired with CFA

vCFAs for Hyper-V Server 2008 and 2012–2016 were combined in one vCFA that can be deployed in all supported Hyper-V environments

Error when trying to boot a VM on CFA (Job not found) because the system failed to properly clean configurations and data of VMs that were previously booted for verification and considered to be running while not shown in the CFA Management Console

CFA reported a Hyper-V or a VMware VM backup job as Successfully Completed (CFA Management Console › JobsHistory) despite the backed up VM did not have any virtual hard disk drives

8.2.0

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 › SettingsToolsAppliance 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

VMware

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

Various

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

8.1.0

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 › ReplicationMode/OptionsOptionsRemote 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 › BootOrchestrationLAN

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

VMware

CFA now shows the status and details of the VMware Tools installed on a VMware client (CFA Management Console › ClientsVMwareVMware 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, Activate Configuration 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 › SettingsToolsDownloads)

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

Various

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 › ClientsSummaryPropertiesBasic Configuration)

8.0.0

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 › ClientsEdit), 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 › SettingsBackupsAdvanced Settings)

When starting backup of a physical machine manually, option to back up as DR image is selected by default (CFA Management Console › ClientsSummaryManual 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 › ReplicationMode/OptionsOptionsRemote 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 › ClientsEditBoot)

Changes to the settings of one boot group (where a client belongs) applied to all other boot groups (CFA Management Console › ClientsEditBoot)

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 › ClientsEditError Recovery)

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

VMware

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 › ClientsEdit (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 › ReplicationMode/OptionsRemote Appliance InformationTest 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 › SettingsToolsDeduplicated 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 › ClientsVMwareAdd Connections)

Incorrect sorting of VMs in the CFA Management Console › ClientsVMware 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 › ClientsVMwareHost Version column

Invalid port displayed when viewing the Hyper-V connections (CFA Management Console › ClientsHyper-VView 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 › SettingsToolsRAID 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

Various

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 › SettingsToolsSeeding)

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 › SettingsToolsSave/Restore Configuration)

Negation operator (!) did not work when used in filters in the CFA Management Console › JobsHistory

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

Recover Catalog feature (CFA Management Console › JobsImporting Jobs)