How can we help you today? How can we help you today?

Log Shipping failing "randomly"

There may be a pattern to it, but I have not found it yet...

I'm running SQL Backup for log shipping in the following manner
Server A backups to Server B
Server B backups to Server C
Server C backups to Server A

This has been running effectivly for a few months now, with only the "to be excepted" occasional failure which have always fixed themselves withing 15-45 minutes.

However this weekend, Server A failed continuouslly for 7 hours then fixed itself.
Now Server A is failing again for the last 1 hour with the following messages:


Backing up usc001prd (transaction log) to:
D:\SQLBackups\SOY_usc001prd_20060515_133608.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860
Server: Msg 3013
BACKUP LOG is terminating abnormally.
SQL Backup exit code: 790
SQL error code: 3013

exitcode 790
sqlerrorcode 3013
filename01 D:\SQLBackups\SOY_usc001prd_20060515_133608.sqb
Jeff Randall
0

Comments

4 comments

Sort by
  • Jeff Randall
    I am currently using: SQL Backup 4.1.0.207 - Professional edition

    And I can not upgrade to 4.2 (or reboot the server, or restart the SQL Server Service) until at least Sunday during the next scheduled Maintenance Window...
    Jeff Randall
    0
  • petey
    Could you pls post the results of running the following:

    exec master..sqbmemory

    ? Thanks.

    An upgrade does not require you to reboot the server if you can release xp_sqlbackup.dll cleanly. It also does not require you to restart the SQL Server service, only the SQL Backup Agent service.
    petey
    0
  • Jeff Randall
    Update:
    Yesterday around noon, it failed for about 1 hour then fixed itself.
    Then began failing again around 3:00 PM for about 9 hours and fixed itself again around 1:00 AM this morning.
    petey wrote:
    Could you pls post the results of running the following:
    exec master..sqbmemory
    The server it has been failing on (although currently it is working):
    Type Minimum Maximum Average Blk count Total
    Commit 4096 1073479680 0 1419 -1398685696
    Reserve 4096 67063808 747046 294 219631616
    Free 4096 3801088 305949 344 105246720
    Private 4096 1073479680 0 1043 -1229021184
    Mapped 4096 1536000 165290 48 7933952
    Image 4096 5836800 67577 622 42033152

    One of the servers it works correctly on:
    Type Minimum Maximum Average Blk count Total
    Commit 4096 1073479680 0 1261 -1406857216
    Reserve 4096 8384512 492136 239 117620736
    Free 4096 15007744 797885 270 215429120
    Private 4096 1073479680 0 900 -1335246848
    Mapped 4096 1536000 184320 44 8110080
    Image 4096 5836800 68165 556 37900288

    I will post it again later when it begins to fail again.

    petey wrote:
    An upgrade does not require you to reboot the server if you can release xp_sqlbackup.dll cleanly. It also does not require you to restart the SQL Server service, only the SQL Backup Agent service.
    In the past it has caused problems on one of the servers during install, forcing a reboot, and my boss has made it clear that it's not worth the risk.
    Jeff Randall
    0
  • petey
    It appears that the backups are failing due to the lack of a large enough contiguous block of free memory (see my last reply to this post http://www.red-gate.com/messageboard/viewtopic.php?t=2373).

    Using version 4.2 will allow you to specify a maxtransfersize value to reduce the memory requirements.

    A reboot is necessary if you are unable to free xp_sqlbackup.dll cleanly. Try running

    DBCC xp_sqlbackup(FREE)

    when no backups are running, then manually delete or move xp_sqlbackup.dll to another folder. If you can do this, you can upgrade SQL Backup without requiring a reboot or a restart of the SQL Server service.
    petey
    0

Add comment

Please sign in to leave a comment.