March 26, 2009 at 6:36 am
Several days post the SP3 installation i've started having problems with log shipping. First time log backup jobs were running for several hours, when normally it takes seconds to complete. Stopping and starting jobs would not fix this issue. Strangely enough, restarting SQLServerAgent fixed it. After running ok for several hours they've got stuck again. Restarting SQLServerAgent does not fix it now.
When I start the job manually SqlLogShip.exe is started, with correct command line parameters. When checking the job history, it is getting stuck at the first step
Message
Microsoft (R) SQL Server Log Shipping Agent
[Assembly Version = 9.0.242.0, File Version = 9.00.4035.00]
¸ Microsoft Corp. All rights reserved.
2009-03-26 12:14:30.85----- START OF TRANSACTION LOG BACKUP -----
No matter how long i wait exe is running at 13% CPU and nothing happens.
I have added –verboselevel 4 to the exe arguments, but even then it’s not getting beyond the ----- START OF TRANSACTION LOG BACKUP -----
Any ideas anyone?
March 26, 2009 at 8:36 am
Interesting
Can you add a output file in the Job Step (not the Job level, but for each step) to a .log file
Then see if the log says anything (beats the "Job Details" tiny window with no useful message)
March 26, 2009 at 10:10 am
same result 🙂
Microsoft (R) SQL Server Log Shipping Agent
[Assembly Version = 9.0.242.0, File Version = 9.00.4035.00]
¸ Microsoft Corp. All rights reserved.
2009-03-26 15:52:54.65----- START OF TRANSACTION LOG BACKUP -----
Even running it like this sqllogship.exe -server ServerName -Backup 3E5FDBA5-0998-4A5A-8344-87E546C9A8E6 -verboselevel 4 -logintimeout 10 -querytimeout 10 does not give any different results.
March 26, 2009 at 10:38 am
Running the same command from the passive node works however!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply