December 31, 2012 at 2:55 am
Hi All
Environment: 2 Node Cluster, Win2008 Ent, SQL 2008 Sp3 Ent
Log Shipping was always working fine, even after failover between nodes.
After the last failover, the backup job started failing with error "Log Shipping job failed with error: The process could not be created for step 1"
I checked the step properties of the backup job and it seems that the path to the sqllogship.exe has changed in the job.
Why would this happen?
We don't use the usual C: drive for our installations.
Up until now, the location always reflected in the job step properties as "h:\Services\Microsoft SQL Server\100\Tools\Binn\sqllogship.exe". Now it shows as "C:\Services\Microsoft SQL Server\100\Tools\Binn\sqllogship.exe"
Any Ideas why this happened?
Thanks
January 2, 2013 at 5:19 am
what is the exact version of your sql server instance?
There was a small bug with the shared tools install on a cluster, you would install the new instance on the first node and set the tools install location to H:\whatever
Subsequent add node installs however would use the default of the c drive, I believe this may be what you are experiencing
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 2, 2013 at 5:28 am
Perry Whittle (1/2/2013)
what is the exact version of your sql server instance?There was a small bug with the shared tools install on a cluster, you would install the new instance on the first node and set the tools install location to H:\whatever
Subsequent add node installs however would use the default of the c drive, I believe this may be what you are experiencing
Thanks
SQL 2008 Service Pack 3 (10.0.5500)
I am aware of that bug, it's been pointed out at http://connect.microsoft.com/SQLServer/feedback/details/559435/log-shipping-stops-working-on-clustered-instance-if-failed-over-to-another-node
My situation is a bit different.
We have always used H:\whatever as our installation folder and we have failed over between nodes a few times, with no issues. The sqllogship.exe location always reflected as H:\whatever in the Job Step properties and it always worked after failover.
After our last failover, SQL has replaced the sqllogship.exe location in the Job Step properties from H:\whatever
to c:\program files\microsoft sql server\100\tools\binn
In our case, the H: drive is not Clustered and is local to both nodes.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply