A Sprinkle of This, a Sprinkle of That

  • Posted on: 3 December 2014
  • By: David La Motta

This is the second part of a 3-part series on installing, configuring and running Integra. We will simply configure a handful of Providers in preparation for our third installment, and we will save what we will be actually running for last. 

The video will walk you through add following Providers (and configuring a couple of actions for our example):

  • XenServer
  • Microsoft Azure
  • Notification
The default ports for all of the Providers can be found in configuration files under /etc.  Each provider has one, so for XenServer you will find /etc/xen-server-provider.conf, for Azure the file is called azure-provider.conf, and so on.  In those files you can change the port for each Provider as well as configure syslog details, just remember to do a 'service integra-providers restart' so the new ports are picked up.  Providers are stateless microservices, so restart them at will if you are off schedule--as we currently are in this example.

With credentials in hand (Integra needs auth besides your vCenter credentials), the last missing pieces for you in this second part are an Integra license and an Azure account.  The video starts by configuring Integra license information, so you will need to request a 30-day trial license from us.  If you don't have a Microsoft Azure account, getting one is relatively pain free.  Sign up for Azure here and generate access keys to a storage account--we will use this when we configure the Azure Provider actions.

If you'd rather skip the video and read what is taking place, the sequence is as follows:

  1. Add 3 Integra Providers: Azure, Notification and XenServer
  2. Configure 5 actions:
    1. Get the VMs that you'd like to backup
    2. Export those VMs
    3. Upload to Azure
    4. Get a backup list from Azure
    5. Send an email
  3. Create a workflow with the actions above, and make use of the Integra's pipe / T / demux capability:
    1. Send output from step 2.A to steps 2.B and 2.E
    2. Send output from step 2.D to step 2.E
  4. Create a schedule that runs the workflow from step 3 at 1:00 AM every day
That's it!

You have all you need in hand, so follow the video where we configure everything you need to backup running XenServer VMs to Microsoft Azure.

Bonus credit: if you have a storage array, use one of our storage Providers to take a storage-level snapshot of the directory where you have exported all of the VMs.  This will give you double redundancy: on-prem and in the cloud.