Configure Abiquo Veeam backup plugin

Veeam versions

The Abiquo integrations supports the following versions of Veeam Backup & Replication with separate plugins.

Each of the Veeam backup plugins requires its own license.

Veeam version	Backup plugin
Veeam 9.5 update 4	Veeam 9.5 update version 4
Veeam 10	Veeam 10
Veeam 11	Veeam 10

Prepare and maintain Veeam storage

Your backup administrator should prepare and maintain Veeam storage because Abiquo does not delete backups.

Abiquo supports the use of retention policies to set the number of backups to keep but does not control how long to keep the backups.

When a user deletes a backup policy from a VM, Abiquo changes the name to disable and remove it from the next run. However, Abiquo does not detach the backup from the disabled job, so the backup will remain on the disk forever.

Hypervisors

The Abiquo Veeam backup plugins supports VMware and Hyper-V.

Install Veeam

Install Veeam with the Veeam Enterprise Manager, which is an optional component
During the install, configure the API ports of the Veeam Enterprise Manager for the Veeam Backup RESTful API service to use. By default, the values are HTTP port 9399 and HTTPS port 9398.
Ensure that the HTTPS port is reachable from all of the Abiquo Remote Services servers

Create base Veeam resources for Abiquo

The Veeam API cannot create backup and replication jobs, so this means that that you must create placeholder jobs for the Abiquo backup plugin to clone, for each hypervisor you will use. You will also need a placeholder VM on each hypervisor, because each job must contain at least one VM.

On each hypervisor, deploy a placeholder VM
- Name the VM to show that it is a placeholder VM so that it will not get accidentally deleted
In Veeam create a new job for the hypervisor
- The default names that the Abiquo backup plugin will detect are Abiquo dummy VMWare Job for ESXi and Abiquo dummy HyperV Job for HyperV
Add the placeholder VM
DO NOT set a schedule for the job
Save the job

Do not delete the placeholder VMs and placeholder jobs because this could cause problems in the Abiquo backup plugin.

When you display jobs in Veeam, it displays placeholder jobs with placeholder VMs at the top of the list. Then it displays jobs created by the Abiquo backup plugin by cloning the placeholder jobs below the placeholder jobs.

Configure Veeam properties

To configure Veeam backup properties in Abiquo:

Log in to the Abiquo Remote Services server
Go to /opt/abiquo/config folder and edit or create the veeam.properties file.
- This is the default file and folder, to configure a new one, use abiquo.properties as described below
- Ensure that the file owner is the tomcat user in the tomcat group.
The Abiquo backup plugin is designed to manage one Veeam host for each Abiquo datacenter. To associate a datacenter with its Veeam host, set a property pair for the datacenter name and the backup server reference, which may be the host IP or FQDN. You must use the same backup server reference/s that the Veeam manager uses to identify the host/s
1. Get the datacenter name with one of these options:
  1. Abiquo UI: Infrastructure → Datacenter
  2. API: Get datacenter names and IDs: https://wiki.abiquo.com/api/latest/DatacentersResource.html#list-datacenter-names-and-ids, and List public cloud regions: https://wiki.abiquo.com/api/latest/PublicCloudRegionsResource.html#list-public-cloud-regions
2. Get the Veeam host value with one of these options to find the backup server reference:
  1. Veeam Enterprise Manager UI: Dashboard → Summary → Backup servers
  2. CLI: To find the Veeam host value, run these commands on the Abiquo Remote services server.
    # Set variables export APIUSERNAME=administrator && export APIPASSWORD='XXXXXXXXXX' && export APIIP=10.10.X.X # Obtain authentication token export APISESSIONHEADER=$(curl --insecure --verbose --user ${APIUSERNAME}:${APIPASSWORD} --request POST "https://${APIIP}:9398/api/sessionMngr/?v=latest" --header "Content-Length: 0" 2>&1 | grep --only-matching --extended-regexp 'X-RestSvcSessionId: ([[:alnum:]])*') # Obtain hierarchy roots curl --silent --insecure --header "${APISESSIONHEADER}" --request GET "https://${APIIP}:9398/api/hierarchyRoots?format=Entity" | xmllint --format - > hierarchyRoots.xml
    In the response, look for the Link entity with a Type of BackupServerReference. In this case it is veeam01.london.example.com
    <Link Href="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" Name="veeam01.london.example.com" Rel="Up" Type="BackupServerReference"/>
So as an example, consider two Abiquo datacenters, called London and Frankfurt. The London Veeam host has a backup server reference of veeam01.london.example.com. And the Frankfurt Veeam host has a reference of veeam02.frankfurt.example.com. So the properties file would look as follows.
```
veeam.infrastructure.datacenter.1=London
veeam.infrastructure.veeamhost.1=veeam01.london.example.com

veeam.infrastructure.datacenter.2=Frankfurt
veeam.infrastructure.veeamhost.2=veeam02.frankfurt.example.com
```
If you have hosts in Veeam that are not in Abiquo, and they contain duplicates of VMs in Abiquo, you must set the hypervisor property to define the hosts in Abiquo, as a comma separated list. The Abiquo backup system will manage VMs on the hypervisors on the list only, to prevent critical errors in the backup system. If the property is empty or not supplied, the platform will use Veeam data from all hypervisors.
```
veeam.infrastructure.hypervisor=myvCenter1.example.com,myvCenter2.example.com
```

To control backup expiration times in Veeam, use properties to set maximum restore points. Remember to remove the hash '#' comment mark at the start of the property line.

## Set the maximum restore points of a job for each schedule type
veeam.maxrestorepoints=3
veeam.maxrestorepoints.schedule.daily=8
veeam.maxrestorepoints.schedule.monthly=3

## Set the maximum restore points for a specific policy, e.g. "mypolicy", 
## with preference over other properties
veeam.maxrestorepoints.policycode.mypolicy = 5

Set the name of the placeholder backup job for your hypervisor

## Veeam api does not allow us to create new jobs, only clone the
## existing jobs. So Veeam needs a placeholder job (disabled) on each Veeam
## host in order to clone it to create new jobs.

veeam.dummy.vmware.name=Abiquo dummy VMWare Job

Set the name of the backup repository for the placeholder backup job, to match the job's Backup repository configuration on the Veeam server. For example, if you are using a repository called Default Backup Repository.
```
veeam.dummy.vmware.repository=Default Backup Repository
```
If you need to change the backup repository, remember to change this property.
If you have one Entity Manager for two Veeam servers, the backup repositories in the veeam.properties file must exist on each server. You do not have to use them but they must exist. Otherwise, the repository search could fail if each Veeam server uses a different repository name.
For Veeam v11, set the API version
```
avbc.veeam.restapi.version=v1_5
```

Optionally, set other properties, according to your environment:

# JOBS CONFIGURATION

## Since veeam api does not allow to create new jobs, only clone the
## existent jobs. The veeam needs a placeholder job (disabled) in each veeam
## host in order to clone it to create new jobs.
## The following properties define the name of the jobs for each
## virtualization type

veeam.dummy.vmware.name=Abiquo dummy VMWare Job
veeam.dummy.vmware.repository=Default Backup Repository

#veeam.dummy.hyperv.name=Abiquo dummy HyperV Job
#veeam.dummy.hyperv.repository=Default Backup Repository

# TASK MANAGEMENT

## Some operations in veeam api causes an asynchronous task that needs
## to be tracked to know the result of the operation. All these properties
## are defined in milliseconds

## Time to wait between each task state retrieve operation.
## Min and Max exists because each operation increase the next interval
## in a half of the last one (nextinterval = currentinterval * 1.50)
veeam.request.async.maxinterval=60000
veeam.request.async.mininterval=5000

## Maximum of time spent to retrieve the task result
veeam.request.async.totaltimeout=300000

## Timeout properties for synchronous request to Veeam api
veeam.client.connect.timeout=6000
veeam.client.read.timeout=10000

## Cache expiry time in milliseconds
veeam.cache.expire.duration=1800000

Configure all backup jobs with policy codes

In Abiquo, you will create backup policies for users to assign to their VMs. Abiquo will use the Code of the policy to identify which Veeam job to clone to create the backup. So create a backup job for each policy that you will create in Abiquo.

Backup policy code must match Veeam job

When a user assigns a backup policy to a VM, if Abiquo cannot find the Veeam job to match a backup policy code, then it will not be able to create a new backup job in Veeam and the VM backups will not run.

Disabled backups remain on disk
When a user removes a backup policy from a VM, Abiquo changes the name to disable and remove it from the next run. However, Abiquo does not detach the backup from the disabled job, so the backups stay on the disk forever.

For each backup policy you will create in Abiquo:

On the Veeam Backup and Replication server for the Abiquo datacenter, clone the original Abiquo dummy placeholder job
Rename the new job to a name that will exactly match the policy Code of an Abiquo backup policy in the Abiquo datacenter
To set how many backups should be kept on the server, go to Job → Edit → Storage and set Restore points to keep on disk
Note the code and details to enter in your backup policy in Abiquo

Later, in Abiquo, after you create a Backup manager, create your backup policies with the right Code and make them available to users. See Backup and Create a backup policy

When users select a policy with the code, the platform will use the appropriate Veeam job.

Configure backup properties for Veeam

In Abiquo configure backup policies

Go to to Infrastructure → Backup → Backup policies
Click the Edit properties button
Select the required options.
We recommend Enable update while deployed to be able to add a backup policy when a VM is on.
Click Save

Configure Abiquo properties

To configure Abiquo properties for Veeam:

Log in to the Remote Services server
Edit the abiquo.properties file
To activate the backup plugin and define the location of the properties file:
1. Set the abiquo.backup.veaam.config.path property in the following format
```
abiquo.backup.veeam.config.path=/opt/abiquo/config/veeam.properties
```
Make sure that the folder /opt/abiquo/config/ is owned by the tomcat user
Optionally, set the other abiquo.properties for your Veeam plugin version of veeam95u4 (Veeam 9.5u4) or veeam10 (Veeam 10, Veeam 11).
1. abiquo.nars.async.pool.{backupplugin-Version}.max
2. abiquo.nars.async.pool.{backupplugin-Version}.byvdc
3. abiquo.virtualfactory.{backupplugin-Version}.backup.openSession
4. abiquo.virtualfactory.{backupplugin-Version}.backup.openSession.byvdc
See Abiquo configuration properties for more details.

Remember to restart the Tomcat server for changes to the abiquo.properties file.