Link to home
Start Free TrialLog in
Avatar of curious7
curious7

asked on

Restore exchange 2013 DAG node for testing

I have restored a DAG node in a 2 node cluster (with file share witness) to test environment.
This environment has different VLAN so I had to change the IPs of all servers in this test environment.
But Databases or DAG name are not coming online.
I ran the command "sset-databaseavailabilitygroup" to change the file share witness in this environment.
But the command failed and the new file share directory is empty. it gave the following error:
"An error occured while attempting a cluster operation. Error: Cluster API: OpenByNames('server1', 'server2) failed for each server. Specific exceptions" 'An error occured while attempting a cluster operation. Error: CLuster API failed: "Opencluster(server1) failed with 0x6d9'. Error: There are no more endpoints availbale from the endpoint mapper". "An error occurred while attempting a cluster operation. Error: Cluster API failed: "opencluster(server2) failed 0x6ba. Error:RPC server is unavailable.

And as there is no quorum the DAG name won't come online.
What can I do to get this DAG working with only single node I restored?
Do I need to do any changes in Active directory/ DNS entries for this DAG?
Avatar of Amit
Amit
Flag of India image

are you still monitoring this question?
Avatar of curious7
curious7

ASKER

Hi Amit
Yes I am still monitoring this question and have not foudn a solution yet.
Thanks
I assume your end goal is to restore one production Exchange server into test environment?
ASKER CERTIFIED SOLUTION
Avatar of Steve
Steve
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
HI Steve,
I had restored the DC in this test environment. I wanted to change the witness directory without restoring the witness server itself as it was quite huge. But at the end I restored the witness server virtual machine but with just the C drive as the witness directory was on that drive, and got it working.
I had to change the DAG IP to the new VLAN along with the server IP and with these changes and the DNS server in this test VLAN reflecting these changes, I was able to get the cluster and databases up.
Thanks for helping with this one.