Log Shipping Fails

• 
  SQL error code 4326 indicates that the log file that was being restored was too early to apply to the database. One possibility is that the file has already been restored, but failed to be moved to the '\\192.168.11.30\backups\DB4\Cmd\re' folder. This will cause the file(s) to remain in the
  \Dc1\logshipping\Command\1 folder, and be picked up to be restored everytime.
  
  Look for the SQL Backup log files (default location is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>) that contains warnings indicating which backup log files were already restored but not moved. Manually move these files.

  petey November 11, 2006 05:38

  - 0 +
• 
  Thanks for the reply.
  
  Now it seems like everynight it fails from an error that says the log file is to late for the restore, and I copy one log file previous back into the shared folder and rerun the job successfully.
  
  Is it moving the file even if it fails, or is it somehow not copying the file over at all and causing the failure. If its not copying the file over, how do I determine if it isnt and setting it to try again? I have both jobs set to try 4 times before failing.
  
  Am I running the log shipping too much by shipping it every 15 minutes and restoring it every hour? Would it be better to slow it down (the db is about 30gbs big and grows rapidly)

  tlight November 16, 2006 10:49

  - 0 +
• 

  and I copy one log file previous back into the shared folder and rerun the job successfully.

  Does the next to last file exist in your MOVETO folder i.e. \\192.168.11.30\backups\DB4\Cmd\re'' ?
  
  Can you pls check the SQL Backup log files to see if it attempted to restore that transaction log? The log files are found in <system drive>:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> by default. Thanks.

  petey November 16, 2006 12:00

  - 0 +
• 
  I'll check tomorrow if it happens again.
  
  Thanks

  tlight November 16, 2006 12:39

  - 0 +
• 
  It wasnt in there, but it was in the directory that the logs should be backing up to then copying across. It had 3 small failed log files (~5kb) then it got a bigger one. I copied all 4 across and reran the job and it was sucessfull. This is why its failing. Should I slow down the log backups or could this be another problem?
  
  Thanks

  tlight November 16, 2006 17:00

  - 0 +
• 
  THe problem appears to be a failure in copying the backup files over to the network share.
  
  Could you pls check the SQL Backup log files (by default in <system drive>:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> ) for the corresponding backups, to see if this was indeed the case? Thanks.

  petey November 16, 2006 20:24

  - 0 +
• 
  I have this error in there:
  
  SQL Backup log file
  11/8/2006 7:15:01 PM: Backing up Command (transaction log) to:
  \\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb
  
  11/8/2006 7:15:01 PM: BACKUP LOG [Command] TO DISK = '\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COPYTO = '\\Dc1\logshipping\Command', COMPRESSION = 1, THREADS = 1
  
  11/8/2006 7:15:01 PM: Error 510: Backup file exists. Will not overwrite. File name: (\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_191501.sqb)
  
  
  and this:
  
  SQL Backup log file
  11/8/2006 8:15:01 PM: Backing up Command (transaction log) to:
  \\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb
  
  11/8/2006 8:15:01 PM: BACKUP LOG [Command] TO DISK = '\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', COPYTO = '\\Dc1\logshipping\Command', COMPRESSION = 1, THREADS = 1
  
  11/8/2006 8:15:01 PM: Error 510: Backup file exists. Will not overwrite. File name: (\\192.168.11.30\backups\DB4\Command\Log\LOG_(local)_Command_20061108_201501.sqb)
  
  
  and it continues with that...

  tlight November 17, 2006 14:20

  - 0 +
• 
  That error indicates that a backup file of the same name already exists in the backup folder. Do you happen to have 2 jobs running at exactly the same time, to create transaction log backups for the same database (Command)?

  petey November 18, 2006 03:01

  - 0 +

Add comment

Please sign in to leave a comment.