Backsync 4.2 is available for download at www.backsync.net/downloads.
The big item to note is Image backups have changed. Image backups now go directly to a VHD file. If you have an existing image backup you will need to create it again as the 4.1 version is incompatible with 4.2
The cool thing is Image backups now go directly to a VHD up file that contains the necessary drivers required for Hyper-V. You don't need to inject the driver explicitly like 4.1. So, If the backup job is configured without enabling encryption and compression, the Backup VHD can be directly booted using Hyper-V or Virtual Box.
If the backup VHD file is compressed/Encrypted – use "Convert to VHD" option during restore to create a uncompressed/decrypted file to boot the VHD file in Hyper-V. You can also you the BackSync Recovery CD to perform this operation.
Automatic updates will be pushed out from the BackSync Server the client computer reports to. You can manually install 4.2 over the top of 4.0 and 4.1.
What's new in BackSync v4.2
Incremental VHD based Disk Image Backup: BackSync`s Block Tracker continuously keeps track of all the block level changes that are taking place in the disks that are configured for image backup. Each BackSync Recovery point-in-time incremental backup is a fraction of the original volume size, because it only keeps track of the changes that are made to a volume. Also the image full or incremental backups are saved as VHD files which can be individually directly booted up as a virtual instance of the machine, very quickly. In earlier versions of BackSync, the disk image backup has to be restored and converted to a VHD format before booting up as a virtual machine. To directly boot the VHD the backup job must be set to NOT encrypt or compress the backup.
Oracle Backup: BackSync v4.2 supports backing up of Oracle Server. BackSync uses RMAN (Oracle Recovery Manager), a command-line and Oracle Enterprise Manager-based tool to perform hot backup of the Oracle databases. RMAN is the Oracle-preferred method for efficiently backing up and recovering an Oracle database. Oracle database has to be in "Archive Log" mode for performing hot backup using BackSync.
PostgreSQL Backup: BackSync v4.2 supports backup of PostgreSQL database(s). BackSync supports Full and Incremental PostgreSQL database backups even when the database server is online and accessible.
Outlook Backup using MAPI: BackSync v4.2 supports the option to incrementally backup Outlook. Only the emails, Outlook items changed since last backup is backed up during the incremental backup. Each incremental backup of Outlook is backed up as a separate PST giving complete control during restore. In the earlier versions of BackSync, the entire Outlook data is dumped and the difference between the earlier full backup is sent during the incremental backup.
Enhancements in BackSync v4.2
- Supports migration from v4.0 and v4.1 to v4.2.
- Option to enable client backup status e-mail report for individual customers.
- Sending just one backup failure email report from the backup server when the client runs several reattempts to resume an interrupted or failed backup. The email will be sent only after the client has exhausted all its reattempts. Before v4.2, every attempt from the client will create an error report in the backup server.
- Email reports made compatible for iOS devices.
- Added the support for Microsoft Office 365 for sending emails generated through BackSync
Minor Enhancements and Bug Fixes in BackSync v4.2
- NTFS folder permissions restore for Windows 2003 and 2008 servers fixed.
- Fixed an issue in authenticating backup server after performing the seed backup migration in client side when the backup server name is specified in upper case.
- Fixed the Software update issue in Windows 2008 R2 client machines.