June 28, 2018 at 10:39 am
I found in my scheduled backup jobs, one differential backup failed. (I scheduled full backup at weekend, and daily differential backup.)
This is because it seems there is another system setup backup going on every day by the vendor product. In this case it seems it is a maintenance backup job for Microsoft System Center sccm database. So it breaks up my backup chain.
I did a query using msdb.dbo.backupset and find out it has a full backup done every day, to a physical device name like GUI:
{66B1CA5D-145E-48CF-9AB8-887DB9732E02}1
What does that mean, where I can find that file?
Thanks,
June 28, 2018 at 11:07 am
I checked with SCCM admin and found it backed up to another server.
thanks
June 28, 2018 at 11:39 am
sqlfriends - Thursday, June 28, 2018 11:07 AMI checked with SCCM admin and found it backed up to another server.thanks
If their backups are breaking the process you have for backups, that's not a good thing. They should have been checking with you on this.
So you still have an issue where your backups may be invalid due to another backup process. You'd want to ask yourself if you know what the recovery process would be at this point. Do you have access to the other server and whatever tool it is they used for the backup? If not, they may need to be available at anytime for possible restores.
If nothing else, you may want to talk to them about copy_only backups.
Sue
June 28, 2018 at 11:55 am
Leave the SCCM database out of your backup scheme.
That handles the backups, and possible restores, itself.
What you do want to do is find the backups, they are in a folder on the SCCM server, and figure out how to restore them.
You will want to run CHECKDB, reindex, and update stats on the database.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
June 29, 2018 at 5:47 am
Sue_H - Thursday, June 28, 2018 11:39 AMsqlfriends - Thursday, June 28, 2018 11:07 AMI checked with SCCM admin and found it backed up to another server.thanks
If their backups are breaking the process you have for backups, that's not a good thing. They should have been checking with you on this.
So you still have an issue where your backups may be invalid due to another backup process. You'd want to ask yourself if you know what the recovery process would be at this point. Do you have access to the other server and whatever tool it is they used for the backup? If not, they may need to be available at anytime for possible restores.
If nothing else, you may want to talk to them about copy_only backups.Sue
I agree with this.
sqlfriends, there is a value called is_copy_only in the msdb.dbo.backupset table so you can ask them to change it, and then check yourself that they have done what you asked.
June 29, 2018 at 7:02 am
Beatrix Kiddo - Friday, June 29, 2018 5:47 AMSue_H - Thursday, June 28, 2018 11:39 AMsqlfriends - Thursday, June 28, 2018 11:07 AMI checked with SCCM admin and found it backed up to another server.thanks
If their backups are breaking the process you have for backups, that's not a good thing. They should have been checking with you on this.
So you still have an issue where your backups may be invalid due to another backup process. You'd want to ask yourself if you know what the recovery process would be at this point. Do you have access to the other server and whatever tool it is they used for the backup? If not, they may need to be available at anytime for possible restores.
If nothing else, you may want to talk to them about copy_only backups.Sue
I agree with this.
sqlfriends, there is a value called is_copy_only in the msdb.dbo.backupset table so you can ask them to change it, and then check yourself that they have done what you asked.
I've run into this before and I think every time the SCCM admins said they "couldn't" stop the backups for some odd reason or another with their monitoring. I think they just wanted to be doing the restores, not that they had to.
Copy_only keeps everyone happy and eliminates any backup chain issues for the DBA. And DBAs can have the same restore process across all databases instead of having a different process for ones that SCCM monitors.
Sue
June 29, 2018 at 7:04 am
Yep; people can get so territorial about backups! I say DBAs call the shots when it comes to database backups :D.
June 29, 2018 at 9:46 am
I did ask if they can do a copy only backup. The SCCM admin said he cannot. He does not have choice from whatever UI tool he is using to set the backup.
The difference between what his backup and mine is his is doing full backup every day. Mine is full weekend, daily differential.
There is no log backup since the database is setup as simple recovery mode.
And he backs up to another SCCM server drive.
I remove the differential backup for this database only in my script.
June 29, 2018 at 12:32 pm
sqlfriends - Friday, June 29, 2018 9:46 AMI did ask if they can do a copy only backup. The SCCM admin said he cannot. He does not have choice from whatever UI tool he is using to set the backup.The difference between what his backup and mine is his is doing full backup every day. Mine is full weekend, daily differential.
There is no log backup since the database is setup as simple recovery mode.
And he backs up to another SCCM server drive.I remove the differential backup for this database only in my script.
Sometimes that can be not really knowing the backup product well enough. Maybe not in this case but most of them allow copy_only backups.
Nonetheless, make sure to get that all in emails. Restores will be a bit of a mess when it's mixed like that. Typically, those doing the backups should also be the ones responsible for restores. It's really not fair to you if you are responsible for that database.
So make sure to CYA. I've seen enough of your posts to know you are diligent about things like database backups, maintenance and I wouldn't want to see you get in a bad spot with this.
Sue
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply