you need to design and frequently test a "Restore Plan". Like many of the heavy hitters will tell you, a "backup plan" doesn't result in a bloody thing. ![]() With that last thought in mind, when is the last time you've done a test restore of ANY database, especially your large super high value databases? where are the backups being stored and have you verified that your backup files are actually being backed up to tape or stored in long term storage on separate devices somewhere? I trust absolutely no one when it comes to things like this because I've had way too many people be wrong or flat out lie to me with the "proof" of that being the inability of the supposed "backup team" to even come close to meeting either RPO or RTO when the chips were actually down. ![]() Include the "backup admins" on the email only if you're not trying to get them fired for being incompetent because there's absolutely NO justifiable excuse for "backup admins" to miss a failed backup. If there are any failures, send an email to the DBAs immediately. sample the MSDB tables or (if the 3rd party software hasn't screwed everything up), read the SQL Error log at least once for every log file backup cycle. If it wasn't expected, they should figure out what's wrong and fix it! If it was "one of those occasional network blips", someone really needs to be calibrated because, in this day and age, there's really no excuse for such a thing.Īnd, you're paying for it so DEMAND that the DBAs be added to the failed backup alerts. ![]() the alert should tell them WHY the failure occurred and only try a retry if it was something that was basically expected. Second, what do you mean the backup admin guys missed an alert and didn't perform a retry? They shouldn't be performing a simple retry. First of all, if missing a single T-Log backup causes the T-Logs to grow too large, then you folks need to sit down and come up with some extra space for the T-Logs because that kind of stuff IS GOING TO HAPPEN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |