One of the major compliance’s that SMBs look for in a datacenter, is to have active machines up and running round the clock. We can work and maintain our data when our systems are active but an alternate solution should be in place to manage our data in case of a system crash. In this regard, Vembu is going to introduce a new feature called “PERSISTENT BOOT” to help maintain and manage client machines active round the clock.
SMBs who were backing up their client machines to their backup server can perform persistent boot in case of an unforeseeable client crash. With instant boot, we can boot the machine state in a hypervisor provided the crashed client was backed up to a backup server. A special feature in persistent boot over instant boot is to have the changes committed to the files in the backup server and the users can restore their crashed machine along with the changes that was made after system outage. With persistent boot we can reduce RTO time (which defines the amount of downtime that a business can endure and survive) to a minimal amount.
Once the instant boot is initiated, VembuBDR creates a temporary folder in the backup repository and this folder then accommodates all the changes that were made after the instant boot. These changes will also be listed in your restore tree along with its time stamp. Once after replacing the crashed machine with the new similar hardware’s, users can restore entire machines along with the changes that were made after the instant boot (After outage). With this persistent boot in place, we can have minimal downtime along with the persistence in changes to the machine.
Below is a diagrammatic representation of the whole persistent boot process:
Also we can have “PERSISTENT MOUNT” by mounting the VHD file in disk management using SVD mount option. Once after mounting the VHD files in disk management users can explore the backup files within VHD. Any changes that were committed to this attached VHD will be committed to the same file by having its entry in the temporary folder in the backup repository. Users can make any number of changes with their files once mounted and they can restore all these changes to client machines once new similar hardware’s have been deployed. Currently we are supporting persistent boot and persistent mount for server 2012 R2, Windows 2008 R2 and ubuntu 12.04.
Below is a diagrammatic representation of the persistent mount process:
Advantages:
- Minimal Downtime was achieved.
- Persistent over the data changes after an outage.
