In many cases, the virtualization software is able to quiesce the filesystem through the use of guest tools, and this often means that databases can be reliably backed up with a hypervisor initiated backup. There are some potential pitfalls to look out for, such as backing up databases running on a virtual machine. Single file restore is available as long as the hypervisor API allows us to access them, so there is no loss of functionality over file backups.New clients are automatically detected and added to the backup, reducing the risk of a machine being ‘missed’. There is no need to install the Bacula client component (FileDaemon) on each virtual machine individually.The hypervisor is a convenient central place to orchestrate all backup operations for your virtual environment.Some of the major advantages of performing backups at the hypervisor for virtual machines include: This how-to will cover some of the advantages of adding hypervisor-level backup of virtual machines to your Bacula Enterprise installation, and demonstrate the basics of setting up these backups for a HyperV environment. Performing backups at this level rather than at the more ubiquitous file level provides many advantages, though in many cases a combined approach that uses both file and hypervisor backups will provide the best coverage in complex environments with virtual machines. IPERIUS BACKUP FINISHED WITH ERRORS HOW TOHow to Backup Virtual Machines with Bacula Enterprise Edition?īacula Enterprise Edition provides tools to backup virtual machine images through their hypervisor backup APIs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |