Question : Logshipping is failing when SQL Server 2008 cluster is failed over

We have two SQL Server 2008 clusters on Windows 2008. We have configured logshipping between them. The logshipping is working fine when these two SQL clusters are on the same nodes when logshipping was configured. If the clusters are failed over to other other node, the logshipping is failling. For example, if the primary SQL cluster is failed over, the backup job on it is failing with the below error:

Executed as user: CORP\XXXXX. The process could not be created for step 1 of job 0xEA3B8214F7D3F3488F1C4FA61250249E (reason: The system cannot find the path specified).  The step failed.

Similarly, if I fail over the secondary SQL Cluster, the copy and restore jobs on it failing with the same error as above.

It is not logging anything into the log files of the job steps for these failures. I am able to see the source and destination shares/folders for logshipping from the SQL Server (using xp_cmdshell 'dir <path>') on the nodes after the failover.

Even if I configure the logshipping between a cluster (primary) and a stand-alone (secondary), when I failover the primary SQL cluster, the backup job is failing with the same error.

Can someone tell me if I am missing anything here?

Answer : Logshipping is failing when SQL Server 2008 cluster is failed over

Everything I have configured properly. Never mind, we have found it the reason for the issue. When we installed the SQL Cluster on the first node, we have changed the default path of the client tools to a different location as per our standards. Then when we added another node to the cluster, the client tools were installed to the default location on that node. This is the known issue as per Microsoft (http://connect.microsoft.com/SQLServer/feedback/details/387694/client-tools-when-adding-node-to-a-cluster-install-to-the-wrong-location). When we run the logshipping jobs, it uses SqlLogShip.exe from the <client tools path>\100\Tools\Binn folder. As the client tools are on the different locations on these two nodes, when we failover the cluster, it was unable to find the location of SQLLogShip.exe but not the location for storing/copying/restoring the log files.