Are you using HP StoreOnce VSA? I am!

One of the guys I’ve known for a long time is an engineer / IT guy / jack of all trades for a fairly small SMB (in terms of IT needs). They only have a handful of VM’s and a dataset size of about 500GB of production data. So when I get asked to give advise one of the biggest problems I have is that I’m thinking WAY to big, for example could I really tell him to buy a Data Domain or a StoreOnce (physical appliance) that holds several TB of backups physically, and logically scales to hundred of TB’s? Probably not… even if it were in budget it would still be a huge waste!

So when asked how we could do some offsite backups while keeping a budget in mind, I remembered that HP was allowing production use on their 1TB free HP StoreOnce VSA! Having worked for an EMC/Cisco/VMware reseller for a long time I haven’t had a chance to install StoreOnce in any capacity, so this would be my first encounter with real data on StoreOnce. (I had deployed it in my lab a couple of times but I had never used replication or any of the features more than a week at a time, plus lab data gives no really measure of dedupe capability.)

Before StoreOnce

Before StoreOnce all backup data was stored on a P4000 2 node SAN along with all of the production data. Production data was taking up about 500GB and Veeam backup data was taking up about 800GB for 3 weeks of retention. Aside from the P4000, he would also copy the latest backups to an external USB drive so that he had some sort of DR plan.

At one point Rick over at Veeam let me play around with a Veeam Cloud Provider license and we tried that out with this SMB’s data by replicating to my colo. It works pretty well, no issue with the technology, but there really just wasn’t enough bandwidth to push the nightly change data to my colo without also running into production hours. (Nightly change from Veeam to disk is about 12GB, and the company’s upload rate is about 2Mbps).

After StoreOnce

So let me start by saying this is a work in progress, but honestly I’m really excited about StoreOnce so I didn’t want to wait a month or more before writing this post… So it will get updated as I have more data.

The first thing I did was deploy a StoreOnce VSA on their VMware cluster, the licensed it… which was a bit of a pain in the ass… So one recommendation I would make is add a spot for licensing to the GUI. Don’t get me wrong I’m not afraid of the command line, but for the normal SMB customer who would be the target for a self install VSA… yeah GUI would be better. After that I added a 1TB VMDK to the VM and powered it on. Initial startup and install takes about 10 minutes, but its all hands off, basically you just need to sit and wait for the login prompt.

Veeam V8 has support for StoreOnce as a Dedupe appliance, although right now it doesn’t really take advantage of Catalyst but I’ve heard it will in V9. I then created a clone of all the backup jobs and repointed them at the StoreOnce Backup Repository and left them to do their thing. Lastly before I logged out for the night I also started a copy of all the backup retention to the StoreOnce VSA… about 3 weeks of backups…. 800GB of raw disk space.

The next morning I checked the StoreOnce interface to see how much dedupe had been achieved and I was impressed to say the least!

day 2


Thats pretty Impressive considering Veeam already did it’s dedupe and compression on the data before it landed on the StoreOnce!

After a couple more days of backups we are still at a 4.3:1 dedupe rate only having added about 3GB of unique data.

day 3 dedupe


So here is what I have seen so far in terms of StoreOnce’s ability to compress and dedupe on top of Veeam:

Day 2: Veeam sent 12,746 MB of data to StoreOnce; StoreOnce “data on disk” size increased by 1GB (a 12:1 savings)

Day 3: Veeam sent 12,792MB of data to StoreOnce; StoreOnce “data on disk” size increased by 2GB (a 6:1 savings)

Day 4: Veeam sent 12,160MB of data to StoreOnce; StoreOnce “data on disk” size increased by 1GB (a 12:1 savings)

Pretty impressive!


So I mentioned that offsite backups were the goal here… something that didn’t require user intervention was really the big thing. So to make this happen I created a VPN from the company’s Fortigate to a VPN endpoint on my colo gear and then deployed a StoreOnce VSA there, the same way I deployed one on site.

Configuring replication was pretty easy after the VPN was up.

Source appliance was on the 192.168.3.x subnet and the DR appliance was on the 192.168.13.x subnet. StoreOnce has a really easy wizard for replication. I simply went into the replication area, clicked the share I wanted to replication and started the wizard. I had to enter the IP/Hostname of the DR appliance and then create a share to replciate to… which was all handled by the wizard.

Because of the 2Mbps WAN connection, and my being to lazy to drive an hour away to seed the data, I simply set a 1Mbps cap and configured StoreOnce to only upload with 2 “slots”. (each slot wants 512Kbps minimum). Inserting traffic graph just to add color 🙂 … I guess you could say that the throttle works as advertised too I guess.


I estimate that it will probably take about 3 weeks to get in sync, I guess I should have done a seed, but honestly I’m more interested to see how it can handle a slow connection.

On a side note

While setting up this pair for my friend I also though, “shouldn’t I also be doing offsite backup of my data”? Lately I have been slacking… if the colo I use were to “go away” my blog would be in trouble. But setting up a StoreOnce VSA pair and replicating back to my home lab didn’t take long at all. The Veeam backup of my blog is about 10GB after it lands on StoreOnce. The first night (on my 3Mbps download crap connection) it took StoreOnce about 8-9 hours. On night two it only took about 2 hours, but as you can see it wasn’t maxing out my connection. BTW night two had 616MB of data send to StoreOnce but I honestly don’t even see a bump in the “on disk” storage LOL… That’s awesome!

home graph

More to come as it continues to chug away…but in the mean time would love to hear your StoreOnce stories if you are using it.

Update: 9/21/2015

It’s been about 3 weeks since I implemented StoreOnce VSA so I thought I would share how it has been doing so far.


Below is a spreadsheet I’ve been keeping relating Veeam backup file sizes to disk growth on the StoreOnce appliance. I’m keeping track of these simply to show how much disk and bandwidth savings can be expected compared to storing and replicating Veeam files on their own.

21 days

As you can see we are up to a 9.5:1 dedupe rate and have only consumed about 25% of the free StoreOnce VSA’s capacity. At this point we have over 5 weeks of backups on disk, and based on the rate of growth I would say a full year of backups would be pretty conceivable. However I will most likely roll to a G-F-S hierarchy once I hit 60 daily’s.

Backup Job Length

While the StoreOnce VSA’s are doing their initial backups I have also been letting the old backup jobs run, which go straight to disk. Backup times average about 1 minute per job longer on incremental backup days for StoreOnce jobs, full backup days are a little harder to judge because I’m using synthetic full backups to normal disk, and I’m using Active Full Backups each week on the StoreOnce jobs.

Restore Times

Deduplication and compression are both CPU and memory intensive tasks, and therefore most of the time when you add either or both to the mix the time it takes to do those processes increases processing time. Basically the thought is that storage is expensive and CPU and Memory are “cheaper”. With that said most of the time when doing restores from dedupe appliances we will see longer restore times than if we were pulling straight from raw disk.

With that said these test results were pretty surprising to say the least…

Test Parameters

  • Same virtual machine
  • Data Size: 60GB
  • Test 1 was with backup files located on the Veeam’s “d” drive… which is an RDM from a 2 node Hp P4000 iSCSI array.
  • Test 2 was with backup files located inside of StoreOnce which is backended by a VMDK on the same HP P4000 iSCSI array.

The time to restore from the Raw RDM inside of Veeam was 11 minutes and 12 seconds (for just the VMDK).

sage no storeonce test restore

The time to restore from the StoreOnce VSA backups was 10 minutes and 23 seconds (for just the VMDK).

sage storeonce test restore

So in this case a restore of a real VM actually took 49 seconds LESS!

Obviously to be 100% sure I would need to test some more VM’s and repeat over multiple days…But honestly I wasn’t looking for exact numbers… Just knowing that it is pretty much the same is good enough for me!

Testing Veeam Tape features with HP StoreOnce VTL

One of the things that I don’t work with much is tape… in any fashion. However while working on a project I was asked how Veeam did with tape out. I tried to think of where I had used tape with Veeam before and I couldn’t think of a single instance… which is probably why I have installed so many dedupe appliances 🙂 . So I did the only thing a real geek would do… I started looking for a tape drive for my home lab.

You would think, since people have been saying that tape is dead, that I would be able to pick up something pretty cheap. However I soon figured out that quite the opposite was true if I wanted anything with a fiber channel interface. What to do?

What about VTL? Both Data Domain and HP StoreOnce provide VTL features, but on the StoreOnce VSA you do not need a license to enable it. So I logged into one of the StoreOnce VSA’s that I had already deployed and started messing around. It took very little effort before my Veeam server had a fully functional MSL 2024 attached… and the best part is that it didn’t cost me anything!

So the purpose of this article is to show how to get an HP StoreOnce VSA with the VTL options talking to Veeam Backup and Replication, I won’t cover anything in terms of creating jobs or best practices inside of Veeam because frankly I don’t yet have the experience to be making those recommendations, but as I am able to play around with this more I will share what I learn. Also for owners of Data Domain and / or HP StoreOnce, this article should not be considered a way to utilize those products in a production environment. I have to think that writing data directly to NFS/CIFS on these devices would be better than going through the VTL features. (The only thing I’m thinking that might be useful for this though is extended retention where you want Veeam to keep GFS copies, but after I look into that more I will create a separate article for that).

Getting the HP StoreOnce side ready

After deploying the StoreOnce VSA login to it and click on the VTL option. It should have “Auto Create” enabled.


If it is not enabled, click ‘Edit’ and then enable the option. This is all that is needed on the StoreOnce side ot get started, we could however manually create a VTL, but unless you want to copy and paste IQN’s it’s easier to just let it auto create one, and then we can edit it later.

iSCSI configuration on Veeam Server

The VTL features of StoreOnce VSA rely on an iSCSI connection. So the first thing we need to do on the Veeam server is enable the iSCSI initiator (if it isn’t already enabled), you can enable it by simply opening the iSCSI Initiator in Control Panel.

Then enter the IP address of the HP StoreOnce VSA in the Target box and click ‘Quick Connect’. Then in the Discovered targets area click each of the targets and click connect (at least the ones that are related to HP StorageOnce).


By default you should have one drive and once robot listed in the targets window. After connecting the targets you can check Windows device manager to see if they show up. You are looking for a “Media Changer” and an “unknown device”.


Before we install the drivers for these devices we will want to go back over to the StoreOnce VSA and change properties of the VTL to emulate an MSL 2024 (or whatever MSL you want to play with).

Configuring VTL settings on StoreOnce

Click on the VTL item on the left to expand it then select ‘Library’. On the right side of the page you should now see the VTL that was auto created when you connected to the VTL iSCSI targets.


By default it’s emulating a generic drive, but I wanted it to emulate the same MSL that I was looking at on eBay. So if you click on the library then down at the very bottom of the page select ‘Edit’. Then select the “MSL G3 Series 2×24” emulation type. You can also select how many tape’s you would like the VTL to see too, by default it sets the max number for the emulation type. Click save.

Once this has been changed we can do back over to Windows and install the HP MSL drivers and then do the actual Veeam Configuration.

Installing MSL Drivers on Veeam Tape Server

Some backup software wants you to use only their drivers, but Veeam is different, they aren’t in the driver business so they recommend you use the manufacturer’s drivers. So for the HP MSL series that we are emulating you need to download the drivers from FYI I would fully expect this link to break once the HP/Hewlet Packard split happens. So you might have to just google “HP Tape compatibility and Tools”.


Once you get to this page click on the “Hp StoreEver Tape Drivers” link.


At the time of this driving the driver version was 4.0.0 and the file name is cp023805.exe. Download the drivers, and then extract them to a folder somewhere on the Veeam server. I say extract because for whatever reason HP has decided to not allow any of their tape drivers to install in a virtual environment… HP YOU SHOULD FIX THIS…

Here is the error you can expect if you click install.


So after extracting the files to somewhere on the server you can head back into Device Manager and click on the Robot or the drive and select ‘Update Driver’. Then navigate to the folder where you extracted the drivers, and select the OS folder that matches your Veeam server. Then click next through all the pretty boxes until you see a screen that looks like this:


Then repeat for the other related device… either the drive or the robot:


Then you have all the drivers installed that you need. Now we can open Veeam and configure it to see the MSL.

Veeam Tape Configuration

After you get Veeam B&R opened up you can navigate to the Tape Infrastructure area. The first thing we need to do is select “Add a Tape Server” from the list. I installed the iSCSI VTL on the server listed as “This Server”, but if you are planning to dedicate a server to just doing tape, then select the appropriate server from the list.


If there are restrictions on traffic for this tape server you can set those up on on this page otherwise click next


Typical Veeam review page… next.


Here you can monitor the progress of the tape agent install.. then click next.


Normally I don’t show the Finish page, but this one contains an important check box. The “Start tape library inventory” box…make sure that is checked so that you get an initial inventory of your tapes.



When you first open you all of the new things on the left side your tapes will appear under an unknown media pool, but as the inventory happens they will move over to the Free media pool. Once all of the tapes are in the free media pool you are ready to start doing Veeam backup’s to tape!


Lastly I wanted to send a big THANK YOU out to the HP Storage team for creating the StoreOnce VSA… If I didn’t have it it would be much harder to learn and to do my job, so Thank You!