Mmmkay, here's the situation at work. We were experiencing some trouble with a SQL-based application. Our incompetant database administrator deleted the transaction log as part of his troubleshooting. He came to me looking for a backup of the database. Our backup software cannot back up live databases, so I had set up a maintenance plan on the database about a year ago (even though it is his responsibility, not mine IMO) to dump a copy to another disk and keep a week's worth of backups. As I checked my tapes for a backup, I discovered that we did not have a backup since October. Looking into it further, I discovered that he had worked on the database in October without my knowledge and either deleted the maintenance plan or had reinstalled SQL and neglected to recreate it. My backups have been working without error, but I simply cannot back up files that aren't there. So our director came down pretty hard on me last Friday for not having a backup, but I believe the database administrator should have been responsible for creating and maintaining a backup to file of the databases, and my responsibility is for the backup of the database dump files. The director got the story of what happened from the DBA so I'm sure the story has a spin to it that favors him and not me. I'm going to talk to the director some more about it tomorrow and hopefully clear up any misunderstandings but was wondering what you guys think? Am I responsible to mop up the mess the DBA creates or is it a reasonable expectation that he be accountable for his databases and I be accountable for backups. Cliffs: DBA stupidly deleted transaction log recently, deleted DB backup process 3 months ago without my knowledge. No backup available since DB hasn't been dumping for 3 months, who's responsible?