Should log-shipping Servers be in the Same Domain
-
Greetings, I have just implemented a standby database using log shipping. The primary server and the standby server are not members of a domain, each is a local machine. I am wondering about the pros and cons of having a primary and a standby server set up as local machines rather than being members of the same domain. most of the documentation I have read implies that both machines are members of the same domain. It appears to be functioning properly at this time but I am concerned about potential problems that might arise because the servers are not members of the same domain. Any guidance would be greatly appreciated. Thanks.
-
Log shipping mechanisms on both servers is driven by the SqlAgents. The user accounts used to start the agents on both machines has to have privileges to read and write to the share folder where backups of the transaction log of the primary servers are stored (primary server's agent can be able to write to the share e.g. user account used for starting the SqlAgent should have that right, and the user account used for starting SqlAgent on the secondary server should have privileges to read from that share folder). If your servers are part of a domain, this goal can easily achieved by using domain accounts from the domain. If you can make it work in a workgroup environment – great for you
-
Thank you for the update. I guess my question is whether or not Microsoft has a recommendation for this setup and if there are any pieces of standby databases which will not work if both machines are local machines rather than part of a domain. Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply