Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Abiquo backup plugins were previously run as a separate service and they have now been integrated into the core product.

Abiquo backup plugins support the following backup systems:

  • Veeam
  • Avamar

As for hypervisor plugins, you can retrieve the operations and constraints from the backup plugin type.

To use a backup system, you should first create a backup manager for the datacenter. The backup manager configures the connection to the backup system including the endpoint and optional credentials. Here you should specify the type of the backup plugin. Abiquo does not validate the connection details. In this initial version, a connection will be made to the backup system when a user requests a backup operation. 

As before, in each datacenter, you should create backup policies. The enterprise that creates the backup policies will automatically be allowed to use them. For other enterprises, you must select the allowed backup policies for each datacenter.

Then to assign backup policies to their virtual machines, users in the enterprise will be able to select backup policies from the allowed backup policies 

There have been some changes to the user interface. After the user creates a backup, they can see the backup in the list on the Backups tab. To restore the backup, as before, the user clicks on the Restore link. To display a list of restore details in the lower section of the same tab, the user clicks on the backup. (question)

The backup plugins work with the API (for backup management), and remote services: virtual factory and cloud provider proxy. The backup plugins are configured using:

  • Abiquo property on API / Server: check 
  • Abiquo property on Remote Services: configuration file
  • Backup system configuration files in the same folder as the Abiquo properties file on the remote services

There are new Abiquo API methods for working with backups. Previously, developers could create a backup integration using virtual machine metadata and events. Now developers should upgrade their integration to use the new API methods for backups, with new data media types. This is because the Abiquo UI now works with the Abiquo API instead of virtual machine metadata. So backup information stored in virtual machine metadata is valid but it will not be visible through the Abiquo UI. For basic backward compatibility for developers upgrading an integration, it is possible to use the backup system without a valid backup manager. There are no changes to Abiquo backup events.


 

  • No labels