June 30, 2018 at 4:37 pm
Hi Guys,
Has anyone noticed on sql 2014 that if you stop a full backup after starting it, that the next DIFF you take happens to be a full backup?
Is this by design? It seems I can recreate the symptom reliably each time.
I would expect an aborted FULL backup to still be able to produce a differential next time around? Am I wrong?
Cheers
Alex
July 2, 2018 at 3:24 am
Are you using Ola Hallengren's solution, out of interest?
July 2, 2018 at 4:39 am
I've not heard of it. So probably not. What is it?
I did the following:
backup database BOB to disk = 'c:\backups\bob.bak' with stats=1
Before I swore realizing I had left off the differential option
I then ran:
backup database BOB to disk = 'c:\backups\bob.bak' with stats=1, differential
Which produced a file (REALLY REALLY SLOWLY) that was roughly the same size as expected for a full backup, and the header of the backup said it was a FULL.
I have had this problem a few times before but on each occasion it was someone else, and also a one off from me I assumed it was a genuine user error and was no big deal.
But now I am convinced its something more sinister.
Cheers
Alex
July 2, 2018 at 4:43 am
Never heard of Ola 🙂 ! It's so much easier to use his scripts than to try to run your own. Everybody uses them.
Can you show us the preceding backup history for that database, and include the is_copy_only flag in your output?
July 2, 2018 at 7:08 am
I shall most definitely have a look.
I have a bunch of my own that I've never bothered to share (not because I am selfish but because i suffer from ridicule anxiety about such things). Though they are not particularly exciting they just do stuff like backup everything in an availability group, and so forth. But in this case i wasn't even using those scripts just a plain backup statement!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply