Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Log Shipping exe location Expand / Collapse
Author
Message
Posted Monday, December 31, 2012 2:55 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:48 AM
Points: 1,380, Visits: 2,705
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
Post #1401327
Posted Wednesday, January 2, 2013 5:19 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:21 AM
Points: 6,643, Visits: 14,230
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"
Post #1401790
Posted Wednesday, January 2, 2013 5:28 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:48 AM
Points: 1,380, Visits: 2,705
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
Post #1401793
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse