What's new in MSP360 Backup Server Edition 7.9.4.83

Mar 19, 2024
  • Minor bug fixes

New in MSP360 Backup Server Edition 7.9.3.140 (Feb 15, 2024)

  • Features:
  • SQL Server Backup: Added ability to run differential and transaction log backup on demand
  • Files Backup: Dropbox online files are now ignored if Do not backup on-demand files option is selected
  • Resolved Issues:
  • Network Shares: Files in use by another process are reported as unexpected error (code 1003)
  • Long timeout on attempt to retrieve exclusive access to repository (code 1072)
  • Minor bug fixes

New in MSP360 Backup Server Edition 7.9.2.231 (Dec 20, 2023)

  • Deprecated Features:
  • Legacy Archive V2/V1 is deprecated in this release.
  • Features:
  • A possibility of partial restore from corrupted backup data is now supported for file backups in new backup format ###Improvements
  • Command Line Interface (CLI) help is improved
  • Resolved Issues:
  • Minor bug fixes

New in MSP360 Backup Server Edition 7.9.1.128 (Oct 11, 2023)

  • Backup: error messages were improved
  • Minor bug fixes

New in MSP360 Backup Server Edition 7.9.0.404 (Sep 6, 2023)

  • Features:
  • Hyper-V: VM-level application processing settings are now available
  • VMware: VM-level application processing settings are now available
  • Hyper-V: Item-level exclude for Hyper-V backup plans
  • Restore: File-level restore for Hyper-V and VMware virtual machines with Linux guest OS is now supported
  • Restore: Single drive restore for Hyper-V backup plans
  • Improvements:
  • General: UI graphics are updated
  • Resolved Issues:
  • Forever Forward Incremental: intelligent retention information for storages with early deletion policies
  • Virtual machine naming is now case insensitive
  • VM socket calculation issues resolved
  • Minor bug fixes

New in MSP360 Backup Server Edition 7.8.6.12 (May 10, 2023)

  • Minor bug fixes

New in MSP360 Backup Server Edition 7.8.4.285 (Mar 22, 2023)

  • Improvements:
  • Backup: error messages were improved
  • Hyper-V Backup: Processing of virtual machines in invalid state was improved
  • Resolved Issues:
  • Export configuration: functionality is restored
  • Restore: minor bug fixes
  • Hyper-V/VMware Backup: minor bug fixes

New in MSP360 Backup Server Edition 7.8.3.128 (Mar 22, 2023)

  • Features:
  • Backup plan upgrade from the legacy backup format to the new backup format (via CLI)
  • Improvements:
  • Retention policy: Scheduled full backup is mandatory to apply the retention policy in the new backup format
  • Immutability feature renamed to Object Lock
  • Known Issues:
  • Upon rollback from version 7.8.3 to 7.8.2 or earlier, all passwords (storage accounts, network credentials, encryption passwords) are reset and require manual re-entering
  • Resolved Issues:
  • Backup storage: Block-level backup is displayed instead of full from another computer
  • SQL backup: Sync fails after the failed backup plan execution
  • Consistency check: 'Sequence contains more than one element' error upon consistency check in the new backup format
  • Forever Forward Incremental: 'Unnecessary restore point was found' error after re-enabling Forever Forward Incremental backup
  • VMware backup: Error upon editing VM list using the quick edit

New in MSP360 Backup Server Edition 7.8.2.253 (Dec 21, 2022)

  • Improvements:
  • Memory performance improvement on million folders to file system destinations (local disk/network share)
  • Reporting: Detailed report generation improvement for backup plans with large numbers (millions) of files
  • Diagnostic: Event logs can be sent until the app is running under the administrator account
  • Ability to re-init the repository database in case it is corrupted
  • Resolved Issues:
  • File backup: Incorrect behavior of the 'Do not back up files used by other processes' option
  • Image-based backup: First full backup is interrupted by the scheduled full backup
  • Reporting: Some files are missing in the detailed report
  • Backblaze B2: Deep sync fails due to the 'Unknown file size' error
  • Restore: Issue with filenames upon restore to a specific location

New in MSP360 Backup Server Edition 7.8.1.147 (Nov 16, 2022)

  • Features:
  • Forever Forward Incremental backup
  • Intelligent Retention for Forever Forward Incremental backups
  • Resolved Issues:
  • Backup: High memory consumption upon deep sync
  • Backup: 'Large files must have at least 2 parts' error upon uploading compressed files to Backblaze B2 storage
  • MS SQL restore: Restore job restores one excess transaction log file

New in MSP360 Backup Server Edition 7.0.1.684 (Feb 3, 2021)

  • Restore PointRestore Point is a partial data set for restore. A full-fledged restore point contains at least one file ordirectory. If a restore point does not contain any file or directory, it is considered as empty, but successfulcan contain blocks for further subsequent runs. A valid Restore Point guarantees a correct restoration ofbacked-up data. As the opposite, invalid Restore point does not contain a complete data set for restore,but at the same time can contain blocks that are used for restore from other Restore Points.
  • The new backup format key features are:
  • The number of requests to storage is reduced significantly
  • Uploading by data parts enables continued upload in case of network issues
  • Any characters (emoji, 0xFFFF, etc) and extra-long filenames supported
  • Filename encryption in the box (one password for generation)
  • Real full backup for file-level backups
  • Fast synchronization (reduced number of objects in backup storage)
  • Plan configuration is always included in a backup
  • Backup logs are backed up along with backup data
  • Object size is now limited to 256TB regardless of the storage provider limitations
  • Fast purge (reduced number objects on backup storage, deletion of whole generation database)
  • Password Hint
  • Faster backup and restore for a large number of small files
  • Lower costs for a large number of small files (not applied for S3 standard-IA with 128KB limit).
  • Client-Side Deduplication:
  • The new backup format reckons for a full backup plan independence, so each separate backup plan has itsown deduplication database. Moreover, backup plan generations also have their own deduplicationdatabases.Once a backup plan is run, the application reads backup data in batches aliquot to block size. Once a blockis read, it is compared with deduplication database records. If a block is not found, it is delivered to storageand is assigned with a block ID, which becomes a new deduplication database record. The block scanningcontinues, and if a block matches any of the deduplication database records, a block with such ID isexcluded from a backup plan.
  • Synthetic Backup Support for File, Image-based, and VMware backups:
  • The streamlined synthetic backup is now supported for most backup types and major storage providers.See the list of supported backup types and storage providers below.
  • Supported backup types:
  • File backup
  • Image-based backup
  • VMware backup Supported storage providers:
  • Amazon S3 (except S3 Glacier and Deep Archive)
  • Microsoft Azure
  • Backblaze B2
  • Wasabi
  • S3-compatible storage (depends on the storage provider
  • Mandatory and Full Consistency Checks:
  • With the new backup format introduced, consistency check becomes mandatory for each backup plan run.The consistency check is a technique that provides avoiding data losses. By finding any discrepancies, theuser is notified if some backup objects are missing in backup storage or there is a mismatch betweenobject sizes or modification dates
  • Mandatory Consistency Check:
  • In the new backup format, the mandatory consistency check is always a current generation check. Themandatory consistency check is executed for all backup plans in the new backup format before the backupplan runs.
  • Full Consistency Check:
  • Full consistency check features all backup plan generation checks except current generation. Once the fullconsistency check succeeds, the user can be sure that backed up data is ready for restore.
  • Built-In Restore Verification for Image-based Backups:
  • Restore verification is an auxiliary restore plan that retrieves only necessary backup parts from backupstorage, mounts a Hyper-V virtual machine on the fly, then performs a system logon.
  • Restore Verification can be enabled for each image-based backup plan in the new backup format and issupported for Windows 8 (Pro and Enterprise editions) and later versions, and Windows Server 2012 andlater versions
  • Modified Block Tracking for Image-based Backups:
  • Modified block tracking is an algorithm that features a decrease in backup source data reading onincremental image-based backups.Each time an image-based backup plan runs, the state of the blocks at the moment of a backup plan startis saved. Once a first full backup is made, each block in MFT (Master File Table) is marked. On subsequentincremental backup runs, the MFT is being read again and blocks are compared. If a block is modified, theblock tracking mechanism determines which files have been modified and locates disk clusters that containfile data. Once all blocks are compared, only modified blocks are sent for reading with subsequent uploadto backup storage.
  • Restore On Restore Points:
  • Restore Point is such a backup state that enables the guaranteed restoration of backup data. If a full orincremental backup terminates successfully, a new restore point appears on backup storage.Restore points are displayed in the backup tree of Backup Storage browser, so restore became
  • Improved GUI:
  • Backup 7.0 for Windows comes with a new GUI that features the renewed Backup Storage browser anddetailed information on backup and restore plan progress.
  • Resolved Issues:
  • Microsoft Azure: special characters are not supported
  • Wasabi: special characters are not supported
  • Engine: Connections are not closed, sockets are left intact
  • An attempt was made to create more links on a file thanthe file system supports.
  • Backblaze B2: Long filenames are not supported
  • Restore-Only mode: VMware full backup is not displayedcorrectly
  • Current backup format: VMware VM config is notdisplayed if backup data is in Glacier
  • Repository sync: cannot display characters for xmlhexadecimal value 0xFFFF
  • VMware backup: forced full backup of a stopped virtualmachine is displayed wrong
  • Hyper-V backup: full backup size is displayed wrong
  • Archive mode: files on backup storage are not displayedin the History tab
  • Archive mode: backup time is too long when backupconsists of numerous small files
  • VM restore: just created device is not displayed (NVMEcontroller 0)
  • File and Image-based backup: conflict while two backupplans (file and image-based) are running simultaneously
  • Hyper-V backup: force full backup fails after full backup ifat least one VM is powered off
  • High memory consumption on backup plan consistencycheck when filename encryption enabled
  • Restore from NAS: username or password is incorrect
  • Restore NTFS permissions: permissions are not inheritedafter restoration
  • Overflow on a backup of big amounts of files andfrequent synchronization/consistency checks
  • Image-based backup: Slow execution of block-levelbackups
  • Invalid password request on the deletion of file backed upwith filename encryption previously deleted from backupstorage on Backup Storage tab

New in MSP360 Backup Server Edition 5.7.0.237 (Aug 22, 2017)

  • All-Inclusive Support for Hybrid Backup
  • Restoring image-based backups to Google Cloud Platform
  • Restoring image-based backups as vSphere instances
  • Fast NTFS scan
  • Transaction logs backup during full backup
  • Support for Backup Operators API

New in MSP360 Backup Server Edition 5.6.0.182 (May 19, 2017)

  • Hybrid backup for files (local and cloud backup in one plan)
  • File level restore from VMWare/Hyper-V
  • Chain backups
  • Amazon Cloud Drive: compression/encryption support
  • Google Drive: compression/encryption support

New in MSP360 Backup Server Edition 5.4.0.178 (Feb 23, 2017)

  • Restore without sync
  • OneDrive for Business support
  • Restore Wizard new options (modification period, backup period)
  • Google Lifecycle policies
  • Support VMs running on esxi 6.5 host
  • Exchange DAG support
  • Snowball for SQL support

New in MSP360 Backup Server Edition 5.3.0.95 (Dec 12, 2016)

  • AWS Canada (Central) Region
  • New Glacier Retrieval Options
  • Support Snowball for Image Backup, VM, Exchange
  • NTFS permissions via snowball import
  • Retention policy based on backup date

New in MSP360 Backup Server Edition 5.2.0.338 (Nov 4, 2016)

  • Item Level Restore for MS Exchange 2010
  • Synthetic Full for Image Based backup
  • Restore Azure VM/EC2 enhancements
  • Pause/resume running backup