Log Shipping : Out of Sync

I set up log shipping,

after a while the log shipping pair in LogShip Monitor is out of sync.

what cause this & how to solve this problems.

thx

One common reason is if you truncate the transaction log on the source database (or set it to simple recovery model).

Some other possible causes ;

1) Check that the destination still has access to the source share that contains the transaction logs,

2) Check that the destination directory has not run out of disk space to receive the source transaction logs

Depending on what the problem is, you may need to set it up again. Check the last restore time and last copy time.

Hope this helps.

|||

Hi Rodge, thank you for your reply.

For no.1 question, Yes, the target can acces the source.

For no.2 question, Destination directory space is large enough,

anyway this is a test before implementation, so i only use very small database, less than 2MB.

in Logshipping pair properties, it shows:

status : Backup Not occuring

Last Backup File : first_file_0000000000000.trn

Backup delta 960 minutes

Last File copied : D700_tlog_200608300939.trn

Copy delta -958 minutes

Last File Loaded : D700_tlog_200608300936.trn

Load delta -955 minutes

If we check View Backup History, in Log Shipping pair

for a moment, the backup database & the verify Backup , and backup transaction status shows checkmark (it seems OK)

but finally only backup transaction log shows, the backup database and verify backup is gone. it seems the backup database stops.

thx

|||

my log shipping is working fine now

Everything is ok after i reinstall the OS, and SQL

i will try to bring the secondary server online

thx folks

|||After setting it up successfully, monitor what is happening. You can check out my blog on my share of experiences with log shipping at http://bassplayerdoc.spaces.live.com