November 12, 2014 12:04PM
PeaSoup Hosting is one of the first Service Providers to offer Veeam Repository as a Service. This feature enables us to act as a backup target for your Veeam Backup or for your Veeam backup copy jobs.
Why would you use this service?
First of all it will help your organization to get backups off site without the cost and complexity of managing an offsite infrastructure. Traditionally with tape, companies were busy with offsite rotation scheme’s and with the introduction of virtual machines, backup changed too. Backup changed in such manner that most companies backup to disk. The complication with backup to disk was the offsite storage. A tape was easily removed from the library and brought to a vault outside the company’s premise. But with disk this brought more complexity. Some companies are using storage replication or copy jobs to their second site, however having the copies on the second site, it still needs indexing etc. Many companies today have not implemented an off site backup policy for their virtual infrastructures.
Veeam introduced Cloud Connect in version 8 of their suite. Cloud Connect integrates with the customer Veeam setup. As a customer, you are able to simply add PeaSoup as a service provider and use our storage as your repository. Offsite backup for virtual machines has never been so easy and simple!
Add Veeam Service provider
In Veeam, you go to the new Service Provider option and add service provider. PeaSoup will provide the details when signing up. Once a customer added his credentials and accepted the certificate, they will see the amount of storage they are entitled to use. The entitlement is variable and can be expanded whenever needed. In our example we use a repository of 100GB however this can be scaled to multiple terabytes.
Veeam Cloud Repository
When the repository is added, the customer can simply use the repository in their Veeam console for any of their jobs. In the example below we created a new backup job and use the cloud repository as our target. It is that simple!
Use Cloud Repostory in Backup Job
Backup copy jobs or 3-2-1 rule
Some companies require to keep 3 copies of their data, on two types of storage, with one copy being off site. This used to be very challenging using traditional backup software and cloud services. Getting backups off site can be challenging due to limited bandwidth, exploding data volumes and a lack of resources required to build or maintain a true offsite backup repository.
Off site backup copy using Veeam & PeaSoup overview
PeaSoup and Veeam deliver powerful and a reliable solution to help you to prevent the risk of data loss. With our services, customer get:
Giving the ever decreasing cost of storage you will find that pricing for our cloud repository is at very competitive rates. For more information about our new service please fill in the form on our website, email firstname.lastname@example.org or call us at 0808 9000247
July 17, 2014 6:40AM
In the last blog I went into the main architecture of our cloud using VMware vCloud platform and vSAN. In this article I’ll describe how we protect our infrastructure.
Today I will write about backup of the environment. DR and Backup to our cloud environment will be discussed in later articles. PeaSoup is using Veeam Backup and Replication to backup the customer and the management environment.
We had an architecture dilemma when we started with PeaSoup. Originally we planned to use VMware VDP Appliances while this was the only backup solution on the market that supports vSAN. However, we didn’t want any management servers on our customer cluster, and we did found out during testing, that VDP appliance needs to be installed within the resource cluster. We did look at the big brother of VDP, EMC Avamar, however we did not find this the right solution.
In June Veeam released patch 4 for their Backup and replication v7 product which included support for vSAN. I’ve been working with Veeam for a long time and I really like the simplicity of their solution. Secondly Veeam is fully vCloud supported, meaning we can select organization VDC’s to be backup’ed. We tested Veeam in our cloud using vCloud and vSAN and it really performs very well, both backup and restores were very easy and quick.
The next step was to create a design for the backup environment. As we are using virtual Veeam servers, we decided the best way forward is actually to create a separate cluster for the backup environment. This meant we can utilise different lower cost hardware as we not want to use vSAN as a backup target. The backup cluster uses traditional storage solutions and we are using this purely for backup and disaster recovery targets.
The figure above depicts a logical overview of the architecture with the three clusters we have today.
The cluster is also being used for our backup to cloud using Asigra (which we will describe another time)
Later this year we will upgrade Veeam to version 8 as this will provide repository as a service solution. This is a great option, while we can provide repository services to customers who have Veeam on premise, and want to backup to the cloud or have a backup copy of their jobs stored outside their premises.