6.17.2
Linux DR now works with GPT partitions
Option to replicate only last successful backup job of the day
Orphaned jobs filter on the Jobs › History subtab in the appliance Management Console
Warning on possible client reboot when pushing DR backup agent to it
Increased replication speed due to data compression changes
Non-replicated jobs on the primary appliance can now be deleted under retention settings if replication mode is set to None
Wording of options and notes in the appliance Management Console › System › Firmware Update
SNMP failed to return correct SSD status
VMware VM backup failed for a short time after the appliance start or after disconnection from VMware vCenter/ESXi
Clients › Edit subtab in the appliance Management Console showed old retention settings for clients migrated to new retention settings
Daily appliance report sometimes did not include the latest boot verification results
Incorrect appliance Management Console UI behavior when using pagination and filtering simultaneously
Microsoft Exchange DB/mailbox backup jobs were falsely marked as Successful when Exchange VSS writer has not been enabled
Missing screenshot in boot verification results on the client level in the appliance Management Console if relevant backup job was deleted under retention policy
Occasional failure to access appliance from the Dashboard (“Error on getting browse url”)
Occasional failure to refresh VMware connections
Occasional failure to start or stop replication
Occasional failure when configuring test connection in replication
Replication queue table included duplicate job records
Some jobs were still replicated even they should not due to retention settings
Virtual appliance could not boot on GCP
VMware and Hyper-V incremental backups were not archived automatically
Automatic deletion of the orphaned jobs
Jobs › Orphaned Jobs subtab in the appliance Management Console
6.17.1
More options to retain VM backups (0 and 6 weeks to keep last backup of the day; 0 months to keep last backup of the week; 6 and 7 years to keep last backup of the month)
Support for 960, 965, 1260, and 1265 appliance models
Disabled automatic Online DDFS Сompact
Appliance Network Share issues if no restores were performed
Audit Log occasionally failed to record system events
Boot verification occasionally flooded the log with exceptions
Failure to reconnect to multiple VMware vCenters after the appliance reboot
Failure to show an existing VMware vCenter connection, followed by an error when trying to add it again
Incorrect job duration display format in the CSV file downloaded from the Jobs › History tab
Removed duplicate entries in the list of connections to VMware ESXi or vCenter
Replication would not start or stop automatically when certain replication compression options changed
VMware VM incremental backup would fail if a VM disk changed. Now the system automatically forces a full backup of such disk
Disk Usage Calculator
6.17.0
Ability to browse and restore files from the jobs to the shared storage on the appliance (Appliance Network Share)
Ability to push connectivity settings from the appliance to the DR backup agent installed on the client
Ability to start and stop the file shredder, and check its status
Devices page now shows IP address of IPMI if connected
Linux DR: Ability to specify the port number to be used for backup on the client
New backup retention settings for virtual clients (VMware and Hyper-V)
Option to disable HTTP access to the appliance (HTTPS-only)
RAID bar in the appliance Management Console now shows Protected Space
SNMP counters for DDFS show available/used/free space
Backup agent: Ability to pair with from the appliance
Boot Verification now runs once per day
Display of information about free space on the RAID bar in the appliance Management Console
Incremental DR image and VM backups do not rely now on the existing full backups. They can be performed regardless of the level of the latest backup
Incremental VMware VM backups do not rely now on the full chain of backups since the latest full backup
Process of establishing the support tunnel in DR image restore
Process of selecting datastores when restoring a VMware VM backup to a new VM
Replication now continues even if space on the primary appliance is critically low
Restore via the backup agent uses less temporary space on the client. Increased speed of restore
Reworked mechanism of storing information about VMware VM jobs allows to perform more frequent incremental backups with more time between full backups
Texts and wording in the appliance Management Console
Units for showing storage/amount of data in the appliance Management Console are now using 1024 base, and consistent with the relevant Dashboard units
After appliance reboot, the support tunnel was shown as stopped while connection has been restored
Alleviated the possibility to accidentally overwrite configuration of the primary appliance by configuration from the secondary appliance when setting up replication
Backup agent: Login failure when querying for SQL databases
Backup progress could be occasionally shown on the secondary appliance
Appliance could not send data to the devices page
Appliance could stop responding during firmware update
Appliance could stop responding when pushing the backup agent to a client with insufficient user rights
Appliance could stop responding when sending data to the Dashboard
Appliance could stop responding when starting a Hyper-V VM backup during the backup agent automatic update
Dashboard showed alerts on automatically canceled jobs
DDFS errors during truncate operations
DR LAN had no outbound access if DHCP has been disabled
Failure to start restoring files from an orphaned backup job
Inaccurate RAID usage in the Dashboard
Incremental selective VMware VM backup forced full backup after the appliance reboot
Linux DR backup failed if SSH login banner existed on the client
Linux DR backup occasionally skipped partition
Occasional failure to send the daily appliance report via Microsoft Exchange Server
Occasional stacking of the restore jobs in the pending deletion state on the appliances with replication enabled
Some filters in the jobs views were case-sensitive
Unquoted path vulnerability in Windows Registry after the DR backup agent update
Ability to dehydrate VMware jobs for archiving purposes
Ability to manually create differential VMware VM backup
Default settings for clients on the secondary appliance
NAS settings from the appliance Management Console › System › Tools
Support › Portal tab in the Management Console of the unbranded appliances
6.16.2
Files with Unicode symbols in their names were not available for browsing and restoring
Occasional termination of the DDFS mount or repair process due to excessive memory consumption on the appliance
Failure to boot a VM on the appliance if the Group Policy denied installation of any new drivers
Failure to delete jobs on the secondary appliance under the retention policy
6.16.1
Disabled weak ciphers for SSH connection
Events retrieval mechanism in Audit Log
Appliance security aspects (httpOnly cookies)
Replication could stop on the secondary appliance under certain conditions
DR backup could fail due to inability to mount the backup destination
Orchestration could not run under certain conditions
DR LAN has not been activating the gateway, if DHCP was disabled
Backup has been failing for Hyper-V guests with duplicate IDs, if Hyper-V replication was enabled
Purge Remote Jobs option on the client Edit page to prevent accidental removal of the already replicated jobs
6.16.0
Ability to wipe the backup data completely and securely, if the appliance is to be decommissioned
Ability to connect to the appliances available on your local network via the devices page
Option to set the date until a backup job will stay pinned
Option to set the DR schedule when creating a client. The Schedule column is now shown in the list of clients
Local/cloud boot: custom QEMU commands, CPU model choosing, keyboard layout options
RAID status is shown on the console screen
Full VMware 6.7 support
Browse and Restore: expanded the list of supported file systems, improved stability, show message if no browsable data
Customization of the replication bandwidth limit
Date Until Pinned for the previously pinned backup jobs was set to 10+ years from the present moment
Ability to perform Linux DR backups with the non-root user credentials
Support for local and cloud boot of the DR images and VM backups of the clients with disks with 32 sectors per track
Disk order preservation during the local boot on the appliance or in the cloud
Improved stability of the DR image and Hyper-V backups
Reduced storage space used to perform the DR backups
Updated the Knowledge Base link in the appliance Management Console › Support › Documentation
Improved wording of the requirements for performing the local boot on the virtual appliance
If the appliance turned off, DDFS would not unmount at once, which required the hard reset
Inability to bond network interfaces on some appliance models
Incorrect CPU model identification during the local boot
Occasional failures of DR backups
Some jobs could not be deleted under the retention policy
Jobs re-imported from the archive or pushed back from the secondary appliance were deleted at once under the retention policy
VMs with dynamic disks could not boot occasionally
Occasional failures when backing up a turned off VMware VM
Hyper-V backup could fail, if the Hyper-V guest migrated to another host
Failure to restore a Hyper-V incremental backup with a newly added disk
Progress of a VMware VM backup was not shown
Editing a client on a secondary appliance is now disabled
Failure to update the Agent installed on a client due to the improper service stop
Though disabled, boot detection screenshots were shown in Clients › Summary
Garbage Collection history did not show any data
Hardware Monitoring section in the appliance Management Console did not show the CPU and hard disk information on some appliance models
Failure to generate the weekly appliance report
Daily appliance report showed incorrect restore point date, if the last backup has failed
Keyboard layout bugs when booting VMs
Automatic archiving of differential and incremental VM backups
6.15.2
Main DDFS processes use up to half of the available RAM
Drag and drop did not work in Boot › Orchestration
6.15.1
Boot verification occasionally blocked backups
Lags when showing the VMware tab in the appliance Management Console
Appliance would not reconnect to ESXi or vCenter after the disconnect
Failed jobs were not deleted after the garbage collection
Duplicate Protected Bytes column in the list of clients
6.15.0
Ability to unlock a VMware VM migration option from the appliance Management Console
Pin/Unpin job. Allows to prevent deletion of a backup job
Audit log. New event – Delete client
5 seconds delay before local boot to enter the safe mode
Appliance Management Console. Firmware version is visible on the login screen.
Appliance Management Console. Logic of filtering by date.
Performance of the replication jobs
The second hard disk in a DR image backup timed out during the restore
VM images, which were uploaded to a VMware host as templates, were not protected by the system until powered on
Incremental backups failed on a VMware VM with a newly added hard disk
Hyper-V backup jobs hanged or froze when multiple jobs had been performed simultaneously
Verification of a backup job appeared as failed until an automated task had ran after the job was completed
Hyper-V backup jobs failed if the password had been modified
32-bit and 64-bit Windows agents would not run simultaneously
6.14.1
Sometimes the appliance froze with boot verification turned on
6.14.0
Boot verification. Allows to verify a DR image or a VM backup by automatically booting the last successful backup on the appliance
VMware VM selective disk backup
Mass update of multiple appliances
Audit log: Provides information about the system events
Ability to add multiple users to the appliance (command-line only)
Rebuilt daily backup report: Now includes boot verification results, where supported, and gives more concise information to customers about their backup system daily overview
Email notification on login
Option to require password for remote access to the appliance via the Dashboard
Option to restrict access to the secondary appliance for our staff
Support for the new 550 appliance model
Increased performance of the VMware VM backup jobs (up to x5 faster)
Run multiple backup jobs for the same Hyper-V host simultaneously
Protected space calculation for various file systems, software RAID, LVM, and Windows Dynamic Disks
Automatic RAID configuration during initial provisioning of the appliance, no reboot
Quick Start Wizard: no Certificate step; Time Zone/Date/Time steps combined
Management Console: Revised columns on the Clients › Summary tab
Management Console: the Clients › Summary tab shows the date of the last successful backup job for each client
Custom SMTP port and encryption in email server settings
Manual deletion of the jobs from the secondary appliance
Default retention (3 months) for the new appliance
Automatic deletion of the failed jobs after 7 days
Dashboard: Shows number of jobs pending replication
Job message logs show timestamp
If two jobs of one type and level are performed for the client, prevent a new scheduled job of the same type and level from running
Performance and reliability of the Microsoft Exchange backup and recovery
Automatic archiving
Jobs related to VMware VMs show a warning, if performed without the VMware Tools
After the appliance was set up, firmware updates, if any, are downloaded automatically until successful
Remote access and support tunnel stability
Errors on the VMware side during the VMware VM backup and restore (by using dynamic buffer size)
Alphabetical sorting of devices in Orchestration
6.13.5
Orchestration tab does not show clients with bootable jobs
Support tunnel does not reconnect completely after the connection was interrupted
6.13.4
Unable to select destination directory via the Browse Client dialog while the contained files being restored
Failed to boot the machine with a specific MAC address
6.13.3
MAC address can now be edited in the Boot Settings
Some file systems were not backed up on Linux VMs running in the Hyper-V environment, but the jobs were shown as successful. These file systems will be backed up properly after the agent on the Hyper-V host and the appliance are updated
Excessive RAID utilization during routine processing
Always-on tunnels. Tunnels for all customers will no longer time out after 24 hours and are switched to faster network connection
Dashboard. Multiple changes to make remote access to the appliance more reliable. Including both back-end improvements and issues, which previously required cleanup of cookies in a user browser
DR image backup errors due to the invalid geometry of a hard disk
Hyper-V restore jobs transferred the free space
Deterministic use of the appliance MAC address for licensing and replication pairing. Previously, especially with the 950 model, this caused errors when configuring the replication
Automatic archiving option
Non-bootable, but browsable, Linux DR backups with LVM
A new DR image backup job started even if the previous had been performed
1000 appliance models showed the error relating to the catalogs were on RAID
6.13.2
JVM crash during frequent incremental VMware VM backup jobs
Background cleanup of VMware VM snapshots left behind
Replication of the jobs to be deleted remotely due to the retention policies
Remote access became unavailable after interruption of the network connection between the appliance and the cloud infrastructure
Inability to open more than six remote access windows from the Dashboard simultaneously
Stalled information and Unknown status on the DR Sites & Appliances page in the Dashboard after interruption of the network connection between the appliance and the cloud infrastructure”
Hyper-V VM restore transfers only information inside the disk image, but not empty blocks
Proper DR image backup of partitions outside of the disk bounds (VimSDK error “Bad parameters of function”)
Primary appliance stopped working after some time, if the secondary appliance had the incompatible firmware version
Notification in the appliance Management Console regarding the catalog volume not being on SSD
Always reconnect to VMware after reboot of the appliance
Inability to browse and restore files from the virtual appliance
Inability to perform boot of Windows clients with inconsistent NTFS
6.13.1
After the firmware update, incremental DR image backups failed until the full backup had been performed or the client configuration had been modified
6.13.0
File and Folder and DR image backup of the physical Windows 2016 clients
Backup of Windows 2016 VMs deployed on VMware and Hyper-V without the DR backup agent
Backup of VMs deployed on Hyper-V 2016
Boot of Windows 2016
Virtual appliance deployment to Hyper-V 2016 (with nested boot support)
Virtual appliance deployment to Nutanix: support for virtual appliances on VMware, Hyper-V and AHV; support for backup of VMware and Hyper-V VMs deployed on Nutanix without the DR backup agent
SMB2+ support on the appliance
DR image restore: Compression and automatic resuming during over the network
DR image restore: Supports the latest hardware drivers and boots on the UEFI systems
Support for Hyper-V Generation 2 VMs for DR image restore
Replication Summary emails
Revised Support tab in the appliance Management Console
Hyper-V VM backup: Ability to resume Hyper-V backup jobs after migration of VMs to another Hyper-V host
VMware VM backup: Ability to back up very long chains of VM incremental backups
Failure with the No changes message during the DR image restore
Hyper-V VM backup: Issue when the storage was added, but remained unavailable
Hyper-V VM backup: paragonMetadata error during the file restore from a folder
Hyper-V VM backup: Two VMs with the same name and ID caused automatic registration every few seconds
Hyper-V VM backup: File restore from a VM failed with “Error in SetFileTime”
VMware VM backup: Users were not informed about the failure to create snapshots
VMware VM backup: When restored from a VM, certain file types caused the process to freeze
VMware VM backup: Auto-release VM migration locked after backup
6.12.1
Calculate the protected space based on the number of protected machines
Additional fields Protected Bytes in Clients › Summary and Jobs › History views
Metric is shown in the Dashboard, Appliances view (for updated appliances only, pre-6.12.1 appliances have it as 0
Metric is sent to ConnectWise Manage for billing purposes
During firmware update, for each client, the metric is calculated based on the latest job
Cloud replication hardening
Problem when after replication issue (lost network connection, DR cloud maintenance, and so on) replication does not auto-resume
Catalog stored on HDD rather than SSD in some 1550 and 2750 appliances
6.12.0
Always provision appliances to their full capacity
Replication monitoring via SNMP and email notifications
Encryption for replication is turned on by default
Stability of the DR image backup of Windows
VSS errors during File and Folder backup of Windows 2016
Stability of pushing the DR backup agent
Replication stability
VPN connectivity issues to DR LAN in the cloud
6.11.0
Improved DR image backup of Debian 7 and 8
Improved DR image backup of Ubuntu 14.04
Monitoring of DR backup jobs in the Dashboard
White-labeled appliance
Successful boot detection
“Storage added but is unavailable” error appearing during the DR image backup
100% CPU usage when Hyper-V connection is broken
6.10.0
Improved Cloud Boot Orchestration: visual designer for boot sequencing, grouping, delays between boots
Restore LAN configuration in the cloud
Improved bare-metal backup for CentOS 5, 6, and 7, and RHEL
Built-in VNC client
Screen preview for the booted machines
Improved support of VMware 6.5
Improved SNMP-based monitoring
MAC address of a machine is saved during backup and can be restored on boot (no need to enter manually)
User can choose disk controller model on boot
Default boot resources increased to 2 cores, 4 GB of RAM
Boot settings can be fully pre-configured from Clients › Edit, settings in the cloud are not overwritten by configuration of the on-premises appliance
Secondary appliances will be updated automatically when customer updates firmware on the primary appliance
RAID configuration in the provisioning wizard within a single dialog
Used space in the appliance Management Console includes free blocks. Now it shows actual space including free DDFS blocks.
Slow backups (especially with VMware)
Replicated jobs with the Failed Verification status are imported again automatically
Restore jobs of the contained VMware files are not displayed in the Active Jobs list
Appliance crashes during operations with VMware if the user performed DR boot before that
Jobs pushed back from the secondary appliance or restored from the archive are immediately deleted by the retention policies
Direct to agent file restores to UNC path produce files with beginning junk data if the backup included NTFS attributes
Agent did not work on FreeBSD 10
Broken formatting of the RAID email notifications
6.9.3
Software RAID support
Minor LSI RAID UX improvements
Broken files when restored to /?/UNC/
Job Statistics widget showed currently running jobs as failed
Users could get access to several panels via notices in the cloud mode
User stayed on the Active Boot tab after provisioning
When pushed back from the secondary appliance, jobs were deleted immediately by the retention policy
6.9.2
Support for LSI RAID controller
One-click replication configuration
Automatic cleanup of the temporary replication files at the appliance reboot
Improved performance of the DR image restore
Provisioning wizard design changes
Improved replication status detection
Improved performance of the Hyper-V incremental backups
Failure to back up DDFS
Job retention did not work, if replication has been configured, but the client has been set to not replicate
When turned on, cloud replication turned delta on as well
Incorrect format of the RAID email notifications
Unclear filter state in Clients › Edit
Active/Active provision option
6.9.1
Combined the RAID configuration wizard into a single screen
System › Appliance Status shows mount points that used to be filtered out
Issues with running the DR image backups in DHCP mode
LiveBMR: Java critical error while booting
6.8.2
Retry of failed snapshot delete for VMware VM backup jobs
Changed the way some appliances apply updates. Some models will need to install this version before they will be able to apply future updates
6.8.1
DDFS is not backed up properly, and users could not find out how to turn it on
Client version detection would cause the Summary tab (appliance Management Console › Clients) to be blank when a Solaris Sparc backup agent was present
Backup agent installer could trigger a reboot of a client if it was running a Microsoft SQL server, and SQL Native Client (sqlncli) not already installed
6.8.0
Client status icon to show when the backup agent for the client is outdated
MAC adress spoofing to boot
Ability to boot UEFI systems
Isolated NIC for boot testing
Automatic tuning of the boot settings based on the version of the operating system
Ability to boot a group of clients with one click
Ability to pre-assign virtual resources to clients that you are likely to boot
Notice to the Windows push installer that will notify you if the client will be rebooted after the backup agent installation
Automatic updating of the backup agent for Windows
Support for Microsoft SQL Server 2014
Ability to back up the Microsoft Exchange Server mailboxes
Improved disk performance when booting a DR image backup
Improved the Boot wizard
Improved success rate of Windows push installer
Improved Microsoft SQL Server restore wizard to change the instance, the database name, and location of the restored database
Improved SNMP monitoring to allow integration with existing monitoring environment
Time it takes to connect to a Hyper-V host when adding a new connection
DR image backups would fail if the previous incremental jobs were deleted
Removing a client and deleting all related jobs would not recover space from the RAID
DR image and Hyper-V backups would fail with the network storage error
DR image and Hyper-V backups would not progress from 0% to 100%
Local boot would fail if a disk contained more than 4 partitions
LiveBMR restores would fail with ASR writer errors
Attempting to save the current boot as backup would fail if the original backup had been deleted
Trying to stop the replication service, it would get stuck in a stopping state
Secondary appliance would needlessly read large files causing the primary appliance to wait in a stalled state
DDFS-AR would allow jobs to be deleted by retention policy if they have not been replicated
Certain columns in the appliance Management Console › Boot would not allow users to sort
File-set exclusion matchers could be set incorrectly
Export Virtual option could not be set unless the NIC had a statically assigned address
Backup agent would not automatically restart on macOS (Yosemite and El Capitan)
Appliance IP would not persist through provisioning during setup
NULL pointer errors were causing the DR image backups to fail
6.7.4
Support for BitLocker for DR image and Hyper-V backups
Async implementation of the DDFS-assisted replication
Simplified version requirements for replication
Transfer rates for DDFS-assisted replication
Do not require to forward port on the customer’s firewall to configure replication
Version check for non-cloud replication
Offline disks would cause DR image backups to fail
Improper updating if the RAID was encrypted
GRUB configuration defaults to debug entry in 6.7
Global default values could be read incorrectly
Region Lookup: virtual appliance Management Console required refresh to show the available regions after first deployment
6.7.3
Improved DR image and Hyper-V incremental backup performance
Backup failure reported as success
Hyper-V host could be added more than once
Hyper-V backups left AVHDX files behind
Appliance Management Console UI failed to load after rebooting
Hyper-V VM backups with RDM disks now have the disks skipped instead of failing the backup
6.7.2
Support for Hyper-V in Windows 10
Combined installer removed the previous DR imaging software and did not install the new one
Appliance could be used in NTPD amplification attacks
System disk reported out of temperature
After DR backup agent installation and reboot, an error message was recorded in the Windows Event Logs
DR image backups failed on the clustered disks
Hyper-V VM incremental backup jobs were slower than the full backup jobs
Hyper-V VM incremental backup jobs failed if a VM had an empty disk
6.7.1
Boot jobs with Windows XP/2003 and more than four disks on the appliance
Re-register the appliance with a different Dashboard account. The appliance will be removed from the previous account’s Dashboard, and added to the new one.
Option to skip independent persistent disks, so any VMDK files in a VM that are not in Independent-Persistent mode can still be backed up
Option to list specific drive letters to include in the DR image backup jobs, excluding all others
Option in the appliance Management Console to reset networking to the defaults (DHCP, no bonding, no export virtual) to be used if changing network settings locked the user out of the Management Console”
Buttons to allow DNS, IP, and Proxy to be configured from the appliance Management Console before attempting to validate subscription license during provisioning
New warning when using push client installation if KB958488 is not installed, the installation of .NET Framework 4 will require rebooting
Push install of agent will now update agent settings if trying to push install over an existing installation of the same version
Browsing and downloading from the cloud service works for some file systems in DR image and Hyper-V backup jobs
DR image is now installed as part of the DR backup agent installation in Windows, and does not have its own installer
Progress indicators in the push agent installation dialog
New warning that changing the settings in System › Settings › NAS can prevent some types of backups from working, and that the feature may be removed in future releases
Improved mouse interaction in VNC window for some jobs booted on the appliance
Windows 10 compatibility. No need to use the Compatibility Mode
Unable to restore the orphaned VM backup jobs
Archive tab progress bars. When both archiving and re-importing have finished, they will correctly show the progress as 100%
Status and Health columns on the Hyper-V tab
Network settings did not apply correctly if too many simultaneous changes were made in System › Settings › Devices”
An incremental Hyper-V VM backup, which was deleted from the host, was erroneously reported as successful
Network settings did not allow to export virtual and bonding to try to take each other interfaces
Archive tab progress showed the current archiving job as null
Inability to select a Windows client to use as the Hyper-V connection in some circumstances
DR image backup jobs run on schedule even if the schedules were disabled globally in Jobs › Settings
Critical security update for glibc buffer overflow issue
6.7.0
Support for backup and restore of Hyper-V VMs
Notification for missing files in the backup jobs
Cloud boot support for Linux VMs
Notification to activate configuration prior to starting a backup if configuration was not activated
Local boot support for virtual appliances
Push Client support for Windows Servers
Support for file backup of Windows 2012 R2 with deduplicated volumes
Full support for VMware vSphere v6
Support to set up DR backup agents in Windows Server directly from the appliance (push install, no remote access needed)
Option for changing the appliance license type
Hyper-V VSS writer exclusion for Hyper-V hosts for the file-level Backups
Improved the cloud boot performance
Improved the backup and boot performance on the appliance model 1200
Issue when adding new clients while running backups prevented new clients from backup without errors
Issue when the Propagate Manual Delete option functioned improperly
Issue when the DR image recovery disk was unable to open a support tunnel
Issue when a VM backup would leave files in the appliance Management Console › Jobs › Unreferenced Data
Tooltips in the appliance Management Console were displayed incorrectly
Issues with browsing and restoring the backup data from the DR image backups
When browsing and restoring the backup data, the system would attempt to restore Linux directory structure to Windows
Subscription licenses were limited to 4 TB
VM consolidation would be attempted even though it was known to be unavailable
When editing multiple clients at once, the description field would change to <>
When browsing and restoring the backup data, the DR image backups would use the cached data
A booted VM could not be delted after the appliance reboot
Re-initialization of an appliance would not finish properly
Replication would copy the job ID of a backup job to the secondary appliance
Boot Wizard could take several minutes to appear
Clients with Archive in their names would fail to backup
DR image backups would not show current progress
Incorrectly reported modified times on the backed up files
Inability to delete a booted VM after the appliance reboot
Alternate data stream handling when restoring from a DR image backup, which was causing some duplicate files
6.5.1
Cloud replication services in the European Union and South America
Ability to choose a cloud replication region among North America, Germany, or Brazil
Support for the appliance deployment in Hyper-V
Support for the file-level browsing and restoring of the DR image backups
Cloud Backup Accelerator renamed to the appliance model 1200
Default cloud replication mode changed to delta
Locally booted VMs, which were powered off, restarted together with the appliance
Minor appliance Management Console UI issues when creating or editing the schedules
Sorting on the Cloudboot tab
DR backup agent reported its version incorrectly in Windows 8.1
Replication encryption, when enabled, blocked the replication process
6.5.0
Launched cloud replication services in the European Union and South America
Ability to choose the cloud replication region: North America, Germany, and Brazil
Support to deploy a virtual appliance to Hyper-V
Support for the file-level browsing and restoring of the backup data from the DR image backups
Support for Windows 10
New backup type—DR image backup
Support to boot DR image backups
Support for multi-disk operating systems for cloud boot
Support for non-Windows server versions for cloud boot
Ability to set maximum number of bootable VMs on the appliance
Options in the Boot Wizard to provide options for exporting NICs
Renamed the Cloud Backup Accelerator to the appliance model 1200
Switched the default cloud replication mode to delta
Updated ColdBMR to allow for the DR image restore
Issue where locally booted VMs that were powered off restarted when the appliance was restarted
User interface issues when creating or editing a backup schedule
Sorting in the appliance Management Console › CloudBoot
Issue where the backup agent incorrectly reported the version of Windows 8.1
Issue when enabling the replication encryption would prevent replication from working
Error when attempting to restore VMs with vmxnet3
Issue with handling VMs with : in their names
Error when attempting to stun and unstun a VM from the appliance Management Console
Error where the tab icons did not load properly
Issue when attempting to apply capacity licence for the first time
6.4.0
Booting of the VMware VM backups directly on the appliance (Management Console › Boot)
New warning when deleting a client, but leaving the jobs orphaned, and when the automatic deletion of the orphaned jobs was enabled
Appliance virtualization system to enhance reliability of the Active/Active appliance, and to enable the Boot tab
Firewall activated when replication settings had been applied
Firewall did not activate until the appliance had been rebooted
Malformed manifest entry in the virtual appliance OVA file
6.3.0
Remote access from the Dashboard to the appliance Management Console. Remote connection can be managed from the appliance Management Console. Notification when the remote session is active.
Support for cloud boot from the Management Console
Ability to boot Windows Server VMs replicated in the cloud
Ability to export and download Windows Server VMs booted in the cloud
Improved the process of creating new clients
Improved block deduplication
Updated file verification to allow future updates to be applied
Missing icons in the appliance Management Console
Restore ability of VMs with E1000e vNIC
The Transfer Format column on the Replication tab did not sort
6.2.0
Support for the new model of the Cloud Backup Accelerator
Retention Scan Now options in the appliance Management Console › Jobs › Settings
Separate retention policies for the secondary appliance
Tab to set default retention policies for new clients
Option to prevent deletion of jobs on the secondary appliance when they are deleted manually from the primary appliance
Option to license with either capacity license or Infrascale Dashboard Credentials for the appliance and CBA
Improper text wrapping during virtual appliance deployment
Email notification for the RAID degrade
Power button prevented the appliance from initiating the safe shutdown
Issue when browsing and restoring the backup data, where selecting root did not propagate to children
Failure to applying changes to a backup client
Issue when selecting a date range when browsing and restoring the backup data, if the date was set first, the browse button would be inactive
6.1.1
Restore wizard for Microsoft SQL Server
VMware VM automatic registration
Updated and redesigned the appliance Management Console with easier to use interface and better status feedback
Changes to the network settings now applied without requiring a reboot, except when changing from static to DHCP, which cannot automatically forward to the new address
Removed 1 TB size limit for virtual hard disk drives backed up as a part of VMware VM backups
Changed the name of the CBT Enabled column to Allow CBT in the appliance Management Console › VMware
VMware VM restore failed if the previous full backup was not available
Prevented VMware VMs from self-registration