Monday, March 19, 2012

Log shipping in workgroup environment

I have two SQL servers that I am trying to setup log shipping on. I am unable to get the restore of the initial database to work on the standby server. It gets a "unable to open file" error when trying to do the restore.

I have created a "syncaccount" user on both machines, and both have same password. I have used configuration manager to set the user/password for the agents on both servers.

I have given syncaccount admin access. I have added syncaccount to the shares on both servers.

Wy am I getting this error.

Does anyone else think it is VERY difficult to make this function work.

Just check the paths where your backup file exist ........and ensure there is modify privileges for sql agent service in the that path.the refer the below link for configuring log shipping in sql 2005,

http://dumthata.com/sqlchn/articles/lship.htm

this is surely a permission issue as it clearly states that "unable to open the file".........always ensure that theres modify privileges for the shared folder in the primary for sql agent account of secondary server......then only copy job will succeed.........also the folder(in secondary server) in which the backups from primary are copied ,the sql service account in secondary shud have modify privileges in this folder in secondary server........ensure it.......

thanxs

|||

I have checked and recheked this over and over again. It doesn't work.

I see in the server error log that the secondary server is having trouble opening the backup file.

I have created a user account on both machines, with identical user name and passwords, and given full access on both sides. I setup the SQL Server agent on both sides to use this logon.

I can connect to the share (where the backup resides) on the primary from the secondary server using the account name I created. This works fine, which would indicate that the service account can indeed access the share in question.

Something else is wrong.

This is a workgroup network environment. There is no domain logon. I read about creating the user accounts while researching this online.

|||

ok fine you try to restore the backup file manually using with standby option.........and then configure log shipping......if that is not possible check the integrity of the backup file by,

restore verifyonly from disk='Path of backup\backup.bak'

|||

Why won't the product work the way it is documented? Why do I have to do something different?

Why is it so difficult to make a product that works?

|||Dave, we cant say 100% that there is a defect with the product......just ensure that everything from your end is perfect and restore it manually as i said earlier........|||

I am trying to follow documentation supplied with the product, and also third party books that describe how to set this up and make it work. I appreciate the fact that you are giving me alternatives, but lets just say that your instructions are incomplete. I am not a sql server expert, nor should I have to be to set this up. I really want this to work the way it is supposed to. Is that asking too much?

I tried your suggestion. The restore worked. Log shipping does not appear to be. The database is in standby.

I have about 20-25 databases that I want to setup log shipping on between the servers. All I ask is that the product work. It doesn't! (Like so many other MicroSoft products).

|||Dave,pls let us know the exact error you are facing while configuring the log shipping...are you not able to apply the tran logs through the restore job ? ? ?.........

No comments:

Post a Comment