Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts

Friday, March 30, 2012

Regarding domain name for mirroring

Hi guys, may I know whether the domain name needed to be same for the principal server and mirror server in order to get a connection between both the servers and setting up mirroring section successful? Is it possible to use different domain name for both servers for setting up the mirroring section. Can someone share his/her idea or experience like how to setting up the mirroring section and the configuration for the windows before setting up. Thx and hope can get any assistance here.

Best regards,

Hans

Yes, Database Miroring can be setup across two different domains.Please look at the Books Online at http://msdn2.microsoft.com/en-us/library/ms177412.aspx for details.

Wednesday, March 7, 2012

Redundant DR Site Cluster Restore

Hello,
We are restoring our production SQL cluster to an isolated DR site. The
server and SAN hardware are the same, the domain is the same, all of the IP
addresses are the same because the network is isolated.
Typically, we back our production servers up to tape and restore them on top
of a vanilla OS using NetBackup for our Windows DR restores. This usually
works fine, but we are always required to remove the restored server to the
domain, add it to a workgroup, and re-add the server back to the domain to
get rid of the " The trust
relationship between this workstation and the primary domain failed" error.
I have restored the OS of both nodes of the cluster to servers in the DR
site. The cluster service obviously will not start because of the "trust
error" which can't be resolved until the server is removed from the domain
and re-added.
My question is, if I do this to a node in the server, what will happen to
the cluster service/quorum/etc after I remove it from the domain. I'm going
to readd it immediately, but I'm wondering if it will cause any issues or if
there are any precautions I need to take? Or will the cluster just come up
assuming no other changes have been made?
Just go in and take all of the resource groups offline. Then stop the
cluster service in the service control applet. Once that is done, get the
servers added back to the domain. Once added back in, start the cluster
service, connect to your cluster, and start up all other groups.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"jason" <jason@.discussions.microsoft.com> wrote in message
news:ADAEB407-C959-45A4-941D-A29629DB6533@.microsoft.com...
> Hello,
> We are restoring our production SQL cluster to an isolated DR site. The
> server and SAN hardware are the same, the domain is the same, all of the
> IP
> addresses are the same because the network is isolated.
> Typically, we back our production servers up to tape and restore them on
> top
> of a vanilla OS using NetBackup for our Windows DR restores. This usually
> works fine, but we are always required to remove the restored server to
> the
> domain, add it to a workgroup, and re-add the server back to the domain to
> get rid of the " The trust
> relationship between this workstation and the primary domain failed"
> error.
> I have restored the OS of both nodes of the cluster to servers in the DR
> site. The cluster service obviously will not start because of the "trust
> error" which can't be resolved until the server is removed from the domain
> and re-added.
> My question is, if I do this to a node in the server, what will happen to
> the cluster service/quorum/etc after I remove it from the domain. I'm
> going
> to readd it immediately, but I'm wondering if it will cause any issues or
> if
> there are any precautions I need to take? Or will the cluster just come
> up
> assuming no other changes have been made?