February 18, 2015 at 4:39 pm
I've never seen in my whole career that a single backup job may be treated as an after business hour support alert. In fact, I used to work for a Company where backups were administered by a whole different team, but that's a different topic altogether.
So my question would be, how do you guys classify failed backup jobs? For instance, a backup job that failed during a weekend or middle of the night?
Just wanted to hear opinion and experiences, hopefully from DBAs that work for medium to big size companies.
February 18, 2015 at 9:20 pm
It depends on how critical is your database.
February 19, 2015 at 4:53 am
We had different servers with different Service Level Agreements. When the backups on the highest SLA failed, it was an oncall situation because we had to have a 10 minute recovery point objective to meet the SLA. When the lowest level of SLA failed, we usually got around to it on the next business day. It just depends on what your agreed service level is.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 19, 2015 at 5:09 am
Grant Fritchey (2/19/2015)
We had different servers with different Service Level Agreements. When the backups on the highest SLA failed, it was an oncall situation because we had to have a 10 minute recovery point objective to meet the SLA. When the lowest level of SLA failed, we usually got around to it on the next business day. It just depends on what your agreed service level is.
Thanks Grant! I do appreciate the response. I guess that SLAs is the key.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply