Disk-to-disk backup to same storage array?

We're looking to get a new SAN, and so we're re-examining our storage, network and backup issues. Our plan is to get an EMC VNXe 3100 with SAS drives for production data, then buy an expansion shelf and populate half of that with SATA (6 TB raw) drives. Our backup software will then use the SATA as the target.

Our initial sales rep said that would work fine, followed by another EMC sales rep (not coincidentally trying to sell a backup storage appliance, Data Domain) saying that you should never ever put the backup set on the same storage. I'm sure that would be better, but budget is a concern for us, and using the SATA seems a reasonable compromise, but I'd like to be sure.

In my mind, the disk backup target on SATA is to give us 1.) smaller backup window, and 2.) convenient tapeless recovery. We'll still be using tape for disaster recovery and using the backup software to move the disk backup to tape. We only have one site, so replication isn't a great option. Since budget is a concern for us, this seems reasonable as opposed to buying a special device.

The only failure mode I can think is if both controllers on the VNXe fail simultaneously, we're not going to be able to get to either production disk or disk backup. But the odds seem really low for that. Seems that if that happened, we'd be looking for the tapes anyway, because the server room would be gone.

So, am I crazy? Is there anyone else doing something similar?

Answer

While your proposed solution would work, as Chopper3 mentioned it's not ideal. We use, and have had great luck with Nexsan SATAboys for disk-to-disk backup. The SATAboy isn't going to give you all of the advanced features that your EMC will, but honestly you don't need that for backup staging. For that purpose, you just need a bucket-o-disk, which the SATAboy will give you. They're very reasonably priced as well - a lot cheaper than a purpose built backup appliance. If you went with the SATAboy, you'd just attach it to your existing backup server via Fibre channel or iSCSI.

One of the reasons you mention for being hesitant to let your production data and backups co-habitate the same SAN is: how do we get our backups back if the whole SAN goes down. That is indeed a good reason to separate things out, but there's another - IOps. With both workloads on the same SAN (even if not on the same disk array), you'll be pumping twice the IOps through the SAN as you would if the backup staging was elsewhere. That may or may not be a problem depending on how loaded the SAN will be.

So, just wanted to throw that option out there in case you're able to scare up a bit of additional money for your backup environment.