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