Non sponsored article.
There is one company that always impresses me. Veeam has simple UI’s, cheap and clear pricing models and products that just work on first install. This week I found with Cloud Connect, Veeam is always three steps ahead of its competitors.
What is Veeam Cloud Connect? Veeam Cloud Connect establishes a SSL tunnel over the internet to Cloud Storage with no VPN required.
Why would I need Cloud Connect? Firstly are you a customer, or are you a Veeam partner?
- Customers have the ability to send their existing backups offsite to cheaper cloud storage and to remove the need for tapes.
- Partners can license Veeam Cloud Connect connection through the Veeam Cloud Provider (VCP) program. They will be able to build their own remote repositories designed to be multi-tenant and scalable.
Where is the remote repository? It could be in a Partners datacenter, or Public Clouds. This post will focus on transferring backup data to Azure storage.
Let’s Kick the Tires.
I went to the new Azure Portal at https://portal.azure.com/ I selected New, Everything, Searched for Veeam, and deployed Veeam Cloud Connect for Service Providers. **Unfortunatly this failed for me. I am using a MSDN Azure subscription. To deploy this Cloud Service you require a pay-as-you-go subscription.
I started following this deployment guide by Sam Boutros to manually deploy it (cost many extra hours 1-2 days with trial and error).
I deployed a VM in Azure (destination storage location), I also added a TCP endpoint of 6180. I did not add any extra storage to my Azure VM for this test. Then I installed Veeam Backup & Replication 8.
All required prerequisites are installed by the installer.
I then applied the latest patch which Veeam alerts you to install. The first load after a reboot takes a few mintues. The Veeam services are on a delayed start to allow for MSSQLExpress to start.
Then I obtained a free 1 month trial Cloud Connect license from my friendly local Veeam sales team in Sydney. Once you apply this license you receive a new button down on the bottom left called Cloud Connect Infrastructure.
Then I generated a new self signed certificate as I received an error when I attempted to install my public trusted certificate (pfx).
I copied my certificate Thumbprint details to a text file (you will need them later on the source)
I then created a new Cloud Gateway and changed my public IP address, and my port.
I then created 2 new users. I set a quota to the resource that the users is able to access.
On my local source server (Windows 2012 R2) I then installed Veeam Backup & Replication 8. Again I applied the latest Veeam patch. I then applied the same licenses. I went to Backup Infrastructure and right licked on Managed Servers to add my server.
I selected a Hyper-V host
I entered my local hosts address
I entered credentials and the ports were left as default.
I had lot’s of trouble with this, I tried to use Windows 8.1/10 Hyper-V host and unfortunately this is not supported, also I had some firewall wall issues. Links you may need to refer to are below if you encounter similar issues.
On your source host you can diagnose the logs here C:\ProgramData\Veeam\Backup\Setup and the source files that are uploaded to the host are here C:\Windows\Veeam\Backup\Upload. There is only 1 suggestion I make to Veeam here, a simple port testing pool built-in would be handy. The tool uses a pool range of ports not a specified port. This is so each Host (source) can send its traffic on a separate dedicated port.
Then once this agent was installed and configured it alerted me that my Windows 2012 R2 Hyper-V host required some Microsoft patches. I downloaded them and applied them.
You will now note in the Veeam console I now have an additional option on the top left Service Providers.
Then I went here and added my Veeam Cloud Connect host/service from Azure.
I entered my user account and my Thumbprint from the certificate (Azure Cloud Connection VM earlier).
Now you can see that I have my Service Provider
Veeam even has De-duplication and a WAN accelerator built-in for free!
Let’s configure the WAN accelerator. Select WAN Accelerators and Add, change any ports and streams if necessary.
Select your WAN Cache.
Backup job– Let’s send backup data straight to the cloud. Select Backup & Replication, Backup Job, Add your Virtual Server from your Host, Next.
Change your Backup repository from the default to your newly connected Cloud Repository, I changed my Restore points to keep only 4 copies on disk, Next.
Select your required schedule.
Finish, and the job runs successfully.
So we have added our Veeam Cloud Connect Service Provider. We have installed Veeam Backup and Replication directly on my 1 Hyper-V host. We can now send all backups directly to the cloud with transfer speed improvements up to 50 times faster with the WAN Accelerator. Azure storage is cheaper than tapes. We don’t have to worry about tapes, tape drives, tape libraries, tape schedules, and offsite storage facilities. Data recovery will now be quicker. So when someone asks you if you are in the cloud you can say “you are all in”. A special thanks goes to Gnani Lavu from Veeam support in Sydney for his assistance.
I also expect more great news to come from the Veeam KickON in Russia this coming week so follow these on Twitter @Veeam_APAC @Veeam @VMDoug @Chas_clarke