Nakivo has released new version of their backup product – Nakivo Backup and Replication 3.8. This release brings a compatibility with latest VMware vSphere 5.5. Also they introduced a new enhancement which enables to check and self-heal a backup repository in case of data corruption, which might happens during network disruptions or power failure.
The 3.8 release allows installing Nakivo on W8.1, Windows Server 2012 R2 or to be deployed as a Linux appliance. Classic Linux installation is supported not only on Ubuntu, but also on RHEL and SLES as well. This gives quite a flexibility depending of your needs when it comes to selecting a backup server.
Nakivo 3.8 comes in not long after their previous release where they introduced possibility to backup to cloud and 1-click integration to Amazon repository.
Together with those new features I’d like to point out WAN acceleration (present since 3.2 release) with helper VM at the remote site which has for role to compress and optimize the data. The Transporter VM – a “data mover” which performs actual backup, replication and recovery procedures, as well as compression, encryption, and deduplication. You can install multiple Transporters in your environment to distribute the load between them. You can also install Transporters in multiple sites to perform backup, replication, and recovery over WAN.
If you add all the above to the low pricing, you got a very competitive backup solution for SMBs or service and cloud providers, which will take advantage of other (upcoming) features like multi tenancy, per-vm licensing or Exchange objects recovery. I have reported on that in my post Nakivo Backup & Replication 4.0 Announced – Multitenancy, Per VM Licensing, Scalability and Exchange Objects Recovery. Note that backup/recovery of vCloud director VMs is already supported in the current release.
New Features in Nakivo Backup and Replication 3.8:
- vSphere 5.5 support
- Support for Windows 8.1
- Support for Windows Server 2012 R2
- Backup repository self-healing
Quote from the press release:
NAKIVO also introduces the self-healing feature for backup repositories. Network connectivity disruptions, change of credentials and permissions, improper backup repository detach, and even third-party software can cause metadata and backup data to be locked, partially written, or even corrupted in a backup repository. To ensure backup repository integrity at all times, NAKIVO introduces the self-healing feature. In the new version, the product runs scheduled self-checks to verify backup repository consistency and automatically repairs discovered errors.
Nakivo goes forward by adding feature after feature in each release. It’s good for a healthy competition and good for a customer who has more choice. Not every single feature needed by IT professionals has been supported by Nakivo yet, but their strong developing capabilities and fast release cycles are good sign for the future. The upcoming 4.0 release which is scheduled for Q1 shall address some of it and differentiate Nakivo from the rest of the backup competition.