Steve Jones - SSC Editor (8/21/2013)
Nadrek (8/13/2013)
We also share responsibility:DBA's handle Database<->Disk and disk retention/aging, automated and ad-hoc and PITR.
Backup team handle Disk<->Backup software (disk and tape), automated and ad-hoc, and tape retention/aging.
DBA's get requests, and if the backups files are no longer on disk, DBA's send the Backup team a request to get the files from the backup software.
If a non-DBA group wants to handle backups and restores, and talk to them about what happens if someone kicks off a restore they shouldn't have and causes data loss/production impact. Be mindful DBA's can cause these same problems, too. Also, have them test ad-hoc Point in Time Recovery to a different database name (i.e. "I deleted X by accident, can you get it back")
This is how I've usually done this. DBAs manage the db and get files to disk. The backup team takes it from there.
+1 to this. But as Grant has said, I don't really care who handles the backups as long as they are done in such a way that I can meet SLA's and Recovery objectives. At my current job I'm a Dev DBA so I don't do anything with backups, the Ops DBA is responsible for that, I think 😛
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question