Virtual Tape Storage
To solve problems:
- Not enough tape storage
- End of life tape drive
- Faulty tape solution
There has been a recurring theme over the past 12 months that revolves around backup to tape. In short, with the rapid advancement of technology, how are we still reliant on a technology that the rest of the world replaced when Bon Jovi's Slippery When Wet was released? (1986 in case you were wondering). The answer is because tapes are still the cheapest form of mass data storage. Well it was up until the arrival of 'The Cloud'. The savior to us all. The problem is that there are inherent issues with the cloud, not least of which is sovereignty of data.
Working with Riverbed, Somerville have developed a solution that enables Somerville ISP customers to replace legacy tape solutions with a private, secured Cloud offering.
The net result is all the benefits of a cloud offering without any of the problems.
How it works:
Simply put, a managed device is located on site and is presented to the existing backup solution as a new target. Via a dedicated private connection run as a subset of a Somerville internet connection, the device is 'paired' with a virtual target in the core of the Somerville Network. This target is in turn fed with storage from the Somerville Storage Array.
The diagram below shows in graphical format the basic configuration.
Somerville is pleased to offer Virtual Tapes in a try-before-you-buy model. Here's how it works.
- A virtual instance of the appliance is provided
- You deploy the Appliance In your VM Environment (deployment guide will be provided)
- Private network is configured
- The virtual appliance is 'paired' to a target in the Somerville Core
- You can now select the Virtual Appliance as a backup target
Once the service is operating, there are 2 key factors that need to be measured to correctly size the final solution. These are:
- Disk Size
- Network Size
Should you wish to proceed with the service; a dedicated device will be provided to replace the virtual instance. The theory being that it doesn't make much sense to have the backup information located on the same platform that's being backed up.