I've been tasked with coming up with a backup strategy to resolve issues with an ageing D2T procedure that is causing lots of issues. Obviously there are lots of variables, RTO's, RPO's etc but I'm just canvassing for opinion really and to see what you folks might be doing with your backup approach.
We will shortly be getting 2 x 7400 arrays, one at prod site, one at DR. The prod one has been specced with a bias on performance (5% SSD, 65% 15K FC, 30% NL) and the DR one has been specced more for capacity (40% 10K FC, 60% NL - usable space is considerably more than the prod array). We will have the replication suite licenses and a decent 1Gb circuit between the sites.
We are mainly running Hyper-V VMs on the storage, some MS SQL database VMs, some physical database servers also using the primary array for their storage.
My opinion is to remove all the tape backup from prod site. Async replicate all critical data to DR array and backup to tape from there for long term retention but otherwise keep 7 days of snapshots on the primary array for quick recovery and maybe 30 days worth on the DR array.
For MS SQL I was going to suggest using SQL scripted backups to an area on the NL CPG which can then also be snapshotted (sp?) and replicated to DR for longer retention snapshots and tape backup.
For recovery I was looking at Veeam v7 for integration with the 3PAR and direct recovery from the snapshots. Tape backup at DR site will be NetBackup with software dedupe.
Whadya reckon? What are you doing?/would you do with 2 3PARs?
|