June 11, 2013 at 4:26 pm
Hi All,
Wondered if anyone could shed some light on this. Basically i have a sql server instance backing up using normal sql backups. Also i'm trying to test backups using backup exec against the same DB.
I've been told that having the normal sql agent making a full backup will then stop backup exec from making a full backup using its sql agent add in.
I can't see why this would be the case however. I've heard that its because the archive bit is set by the sql servers full back and that backup exec then cannot make its backup. To be honest that doesn't sound likely to me since i thought the archive bit is a file bit in windows os so why would backup exec not be able to then make a backup of its own later on in the day.
Anybody ever had the same setup and if so how has it worked for you.
I'd think the best process would to be to backup sql server using the usual sql agent job/plan and then backup the resultant files on backup exec
June 11, 2013 at 4:50 pm
bit more digging and i think i know what the problem is.
i think the issue is down to the fact that the backup exec backup isnt a full backup but a differential one. that wont run since the last full backup was done via the native sql server backup. instead backup exec will need to run the full backup then the diff. So archive bits dont come into it at all.
If anyone has further advice though it would be welcomed.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply