Extending Veeam Backups with a Cloud Provider

As the month of October comes to a close, so does #Blogtober 2017 Tech Edition.  Speaking of things that are almost, but not quite dead, who here remembers a wonderful piece of physical media that was uber-critical to most IT department’s disaster recovery strategy?  That’s right, I am talking about the backup tape!

Personally, about 15 years ago, I was the one responsible for ejecting the tape out of our Compaq ProLiant 8000 series servers, rotating the DLT tapes, and sending some of them to our off-site storage location via a courier.  Backup tapes are rarely a part of a modern datacenter anymore.  Folks that only have one datacenter still have the age-old question they need to answer… how do I get my data off-site in case of a disaster?

Veeam is as good as anyone at connecting to and securely copying those on-premises backup jobs to an external cloud service provider.  I will go through this process, and how I was able to backup some of the components of my home lab using this technique.

First, I would like to thank NetVPro, a local service provider for donating 500GB of cloud-based backup storage.  (Point a browser to http://www.netvpro.com for more information on them!)  I would also like to thank Veeam for licensing my backup solution in my lab.  I have blogged earlier this year about several of Veeam’s features.  For right now, let’s go through the process of connecting to NetVPro to help us copy backup jobs offsite.

First, let’s create a credential within Veeam to help us connect to our service provider.  Click the left-most drop down and then Manage Credentials.

Then, click Add, and select a Standard Account.

Enter your credentials, and click OK.

To add a service provider, select the Backup Infrastructure menu, and the Service Providers menu item.

Log into the service provider using credentials they have supplied for you.  The default port is 6180, but modify it if they have a custom port.

Now, you will select your credential that was created earlier, and click APPLY.

Once you have connected to the service provider, you will see how much capacity has been allocated to your account.  Click NEXT.

The wizard will save your provider settings and finish establishing the connection.

You will then see the service provider listed in your provider list.  Now, let’s configure a new backup copy job by clicking Backup Copy icon under the Backup & Replication section.

Under the below menu, click ADD and then FROM BACKUPS.

We will create a backup copy job from a backup job called “File Server Backup”.  I don’t have enough space with my provider to back up all my VM’s, so I will only back up a subset of my VM’s.

Here are the VM’s in the backup job.  You can create backup copy exclusions on this screen if you wish.

We will select the “Netvpro-Cloud” Cloud Repository as a target for the backup copy job.  I will also keep 2 restore points.  Of course, the more you pick may add additional capacity requirements depending on how often your data changes.

We can click ADVANCED to configure additional options such as health-check or maintenance operations…

Encryption or additional compression options…

custom SNMP or e-mail options…

…or scripts that will run before or after the copy job.

Click OK and then NEXT.

Unfortunately, I do not make use of a WAN accelerator.  If you have one, here is where you will configure it.  Click NEXT.

If you are network bound and don’t want it to impact your production network performance, you can change the copy transfer so it doesn’t overlap with your daytime work hours.  Click APPLY when you are done.

Now that the job is configured, it will begin the process of seeding the data.  This initial seed will take a while, depending on the speed of your WAN connection.

 

Here is the report of my initial seed.  Thanks to Veeam and NetVPro, I now have a replicated copy of my backup job!

 

 

 

twitterredditlinkedinmail

1 Comment

  1. Paul

    FYI you can seed your backup to reduce the initial sync.

    Reply

Leave a Comment

Your email address will not be published. Required fields are marked *