log shipping + full backup 26 hours

Hi All,
My normal job that runs on the primary server that does
the transaction log backup to the log shipping directory
normally takes anywhere from 30 seconds to 5 minutes.
However when doing a full backup the log shipping job and
the full backup ran for 26 hours. Which normally runs for
about 2 - 2 1/2 hours. What's going on. Can you not do a
full backup and have log shipping?
Regards,
Bryan
Did you check to see if anything was blocking the backup while you were
doing it?
"bmurtha" <anonymous@.discussions.microsoft.com> wrote in message
news:010e01c483f6$fe8ca480$a301280a@.phx.gbl...
> Hi All,
> My normal job that runs on the primary server that does
> the transaction log backup to the log shipping directory
> normally takes anywhere from 30 seconds to 5 minutes.
> However when doing a full backup the log shipping job and
> the full backup ran for 26 hours. Which normally runs for
> about 2 - 2 1/2 hours. What's going on. Can you not do a
> full backup and have log shipping?
> Regards,
> Bryan
|||Bryan, when you do a full backup, your T-log backup will be in a waiting
state. So if ur backup runs for 2 hrs then your T-log backups will be
blocked for that entire 2 hours.. As far as 26 hrs, that remains a mystery..
Havent really seen any factors blocking a backup process. Do you backup
locally or over the network ? If its over the n/w then yes there could have
been some n/w glitch causing it to run that long.. But keep investigating..
Look at the error logs and see if theres anything thats obvious.
"ChrisR" <chris@.noemail.com> wrote in message
news:e$bZJcAhEHA.904@.TK2MSFTNGP09.phx.gbl...
> Did you check to see if anything was blocking the backup while you were
> doing it?
>
> "bmurtha" <anonymous@.discussions.microsoft.com> wrote in message
> news:010e01c483f6$fe8ca480$a301280a@.phx.gbl...
>