Log Shipping Works, Copy says it''s failed
-
I've been asked to set up a "warm standby" for our main db and being the only one who has even the slightest clue about SQL the job ended up in my lap. A quick hunt around led me to set up log shipping between our two SQL 2k Ent servers.
It's working
. Updates are going to the copied db BUT....The secondary server has a job marked "Log Shipping copy...." which is marked as failed.
Checking the secondary server I can see all the T-logs from the primary which it's copied to the C:\Prog...\Backups folder (it should be the D drive but that's another story). So why is the job saying it's failed???
Even more confusing for my limited knowledge, if I manually tell the job to run, it says it's worked.
-
Can you post the error messsage that you see in the copy job history. Are you sure the log shipping is succedding everytime and restoration is happening as it should happen.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Changes made to the live db are being reflected in the copied db in roughly the timeframe we'd expect so yes I'm fairly sure the log shipping is working. Plus the file it does copy the file (though it seems to be always one behind) to the C drive of the secondary server.
The error message in the job history is just the generic message "The job failed. The Job was invoked by Schedule 7 (Schedule 1). The last step to run was step 1 (Log Shipping Copy)."
The event log isn't much better with "SQL Server Scheduled Job 'Log Shipping copy for (xxxxxx) - Status: Failed - Invoked on: 2007-07-05 15:30:01 - Message: The job failed. The Job was invoked by Schedule 7 (Schedule 1). The last step to run was step 1 (Log Shipping Copy).'
-
check the monitoring server ....see when was the latest file backed up copied and restored if theres is any discrepancy let us know ........anything in the error log ???
[font="Verdana"]- Deepak[/font]
-
Hi Tom,
I had a similar problem - copies/restores were reporting success on the secondary server, but the monitor was sending out failure alerts. For me it was a DNS issue - the secondary server couldn't see the monitor to communicate success to it, so the monitor assumed it had failed. Once the network guys had sorted the DNS out it worked a treat.
Cath
-
According to the monitoring server, the latest file copied and restored was 14:40
BUT
Going to the physical C drive location of the secondary where it's dumping all these trans files from the primary and the latest file is 14:30... Is it possible it's restoring the file without copying it first or is the monitoring server making things up as it goes along?
-
Just a thought – check the schedules on your backup, copy and restore jobs. I had to allow some latency in mine to give the servers enough time to finish performing the first two steps before starting the restore. Initially the backups were taking too long for the server to finish before the copy job started (which could explain why your restores are one behind).
-
They're all set to use the same schedule (of every 10 mins)
. I'm guessing the job claims to have failed 
because it can't copy (to the secondary) at the same time as the file is being created (on the primary). I'll create a new schedule and put the copy on that, see what it does... -
hi tom,
i a bit baffled by this.....since ur monitor says the last file restored as 14:40 and u only hav the latest @14:30 in C:\drive of secondary.....i feel that sum1 had accidentally deleted that particular file......also are u sure the restore job is successful ? ? ? .....if yes jus try modifying the primary and chek if its reflected in secondary.......cool
[font="Verdana"]- Deepak[/font]
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply