We've been experiencing above average "Log Shipping
Restore" fails. All copy and restore can be worked for
first two or three times. For no apparent reason, the job
of log shipping restore fails. I checked the windows event
viewer,the message is "SQL Server Scheduled Job 'Log
Shipping Restore for Test2.NorthwindCopy_logshipping'
(0x63382D0A9860D541B191C36DCB658480) - Status: Failed -
Invoked on: 2003-10-31 12:30:00 - Message: The job
failed. The Job was invoked by Schedule 12 (Schedule 1).
The last step to run was step 1 (Log Shipping Restore)."
I'm sure that disk space and netowkr access isn't an issue
and the secondary server isn't busy.Anyone knows what
might cause this .Thanks.Are users accessing the database at the time of failure?
Can you run the restore command yourself? Does it work?
You can get more information regarding log shipping here:
http://sqlguy.home.comcast.net/logship.htm
-- Keith
"kelly" <kelly_lu@.kingston.com.tw> wrote in message =news:45bd01c39f73$9f9f2b90$7d02280a@.phx.gbl...
> We've been experiencing above average "Log Shipping > Restore" fails. All copy and restore can be worked for > first two or three times. For no apparent reason, the job > of log shipping restore fails. I checked the windows event > viewer,the message is "SQL Server Scheduled Job 'Log > Shipping Restore for Test2.NorthwindCopy_logshipping' > (0x63382D0A9860D541B191C36DCB658480) - Status: Failed - > Invoked on: 2003-10-31 12:30:00 - Message: The job > failed. The Job was invoked by Schedule 12 (Schedule 1). > The last step to run was step 1 (Log Shipping Restore)."
> I'm sure that disk space and netowkr access isn't an issue > and the secondary server isn't busy.Anyone knows what > might cause this .Thanks. >
Showing posts with label average. Show all posts
Showing posts with label average. Show all posts
Monday, March 26, 2012
Monday, March 12, 2012
Log Shipping Fails Once a Week
Hi
I have log shipping setup on 2 servers - A and B. Both are SQL Server
2000 and the size of the database is 95Gb. The average transaction log
is around 100Mb
A ships to B and B is also the monitoring server.
The schedule is set to ship every 15 minutes.
Everything works fine, however every Sunday at 23:00 without fail the
log ship fails due to the LSN counter being out of sync. The error
reports an ealier backup is available but any attempt to restore fails
and the log ship schedule must be deleted and re-created.
There are no other backups/restores or any other scheduled jobs that
occur at this time.
Does anyone have any suggestions?
Thanks.
What is the exact error message you receive? Please can you post it up for
us...
Cheers,
Paul Ibison
I have log shipping setup on 2 servers - A and B. Both are SQL Server
2000 and the size of the database is 95Gb. The average transaction log
is around 100Mb
A ships to B and B is also the monitoring server.
The schedule is set to ship every 15 minutes.
Everything works fine, however every Sunday at 23:00 without fail the
log ship fails due to the LSN counter being out of sync. The error
reports an ealier backup is available but any attempt to restore fails
and the log ship schedule must be deleted and re-created.
There are no other backups/restores or any other scheduled jobs that
occur at this time.
Does anyone have any suggestions?
Thanks.
What is the exact error message you receive? Please can you post it up for
us...
Cheers,
Paul Ibison
Friday, March 9, 2012
Log Shipping Copy Errors
We've been experiencing above average log shipping
log "copy" errors. This is the job in which the server
which the log is shipped to has a job on it that copies
the newest log files from the host server. For no apparent
reason, this job fails , but the next time it's run, it
works. Some times it fails 10 times in a row then catches
up all at once. Other times it's less frequent. Anyone
know what might cause this . Disk space and netowkr access
isn't an issue, we've checked that.
thanksTom
Do you have a delay between the source server backing up
the database and the log shipping picking it up? It may be
that the target database is trying to copy the source
backup before it is finished. When you have problems is it
at a busy time, when for instance the log may be larger
than normal?
Regards
John|||Whats the error message?
>--Original Message--
>We've been experiencing above average log shipping
>log "copy" errors. This is the job in which the server
>which the log is shipped to has a job on it that copies
>the newest log files from the host server. For no
apparent
>reason, this job fails , but the next time it's run, it
>works. Some times it fails 10 times in a row then catches
>up all at once. Other times it's less frequent. Anyone
>know what might cause this . Disk space and netowkr
access
>isn't an issue, we've checked that.
>thanks
>.
>
log "copy" errors. This is the job in which the server
which the log is shipped to has a job on it that copies
the newest log files from the host server. For no apparent
reason, this job fails , but the next time it's run, it
works. Some times it fails 10 times in a row then catches
up all at once. Other times it's less frequent. Anyone
know what might cause this . Disk space and netowkr access
isn't an issue, we've checked that.
thanksTom
Do you have a delay between the source server backing up
the database and the log shipping picking it up? It may be
that the target database is trying to copy the source
backup before it is finished. When you have problems is it
at a busy time, when for instance the log may be larger
than normal?
Regards
John|||Whats the error message?
>--Original Message--
>We've been experiencing above average log shipping
>log "copy" errors. This is the job in which the server
>which the log is shipped to has a job on it that copies
>the newest log files from the host server. For no
apparent
>reason, this job fails , but the next time it's run, it
>works. Some times it fails 10 times in a row then catches
>up all at once. Other times it's less frequent. Anyone
>know what might cause this . Disk space and netowkr
access
>isn't an issue, we've checked that.
>thanks
>.
>
Subscribe to:
Posts (Atom)