Unsolved

This post is more than 5 years old

1 Rookie

 • 

8 Posts

2362

November 2nd, 2016 19:00

Isilon DNS Configuration for DR Failover

What is the best way to setup DNS for failover with Isilon using SyncIQ?  I have come up with 3 ways, but I wanted some feedback from others on what they are doing and any reasons to not do one of these three.

  1. Create the Prod SmartConnect Zone name as an Alias on the DR SmartConnect Zone (prior to failover); redirect the Prod DNS Delegation to DR SSIP.
  2. Delete the Prod DNS Delegation and create CNAME to point to DR Delegation
  3. Create CNAMES (prior to failover) and point to either Prod or DR Delegations

I think any 3 of these will work, but what is best? Is there any adverse affect of having the Prod SmartConnect Zone name as an Alias on the DR box? 

Thanks for the input. 

2 Intern

 • 

300 Posts

November 3rd, 2016 01:00

depends on your failover scenario.

- If you use a DFS in front of your SMB-Isilon you can just use a second target

- If you are able to "move" the smartconnectzonename from primary to secondary (Eyeglass, Scripts etc.) you can just make a second DNS Redirect to the secondary cluster SSIP (~ your 1)

I personally do everything to have the least amount of work and complexity in the case of an desaster. If you just have to press the red button to make it work again, you can relief a lot of stress from your admins. If you have a very complex failoverscenario and a lot of stuff you got to do in different systems you take longer to failover. And you are more likely to do mistakes.

So do everything you can prior the failover.

Regards

-- sluetze

57 Posts

November 3rd, 2016 03:00

With Superna Eyeglass no DNS changes required during failover  Its explained here (and SPN's also failover for each smartconnect name involved in the failover, without any access to AD needed)

Regards

Andrew

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

November 16th, 2016 21:00

i use CNAME's for both Source and DR target for everyday connectivity. You can decide what TTL to set on that CNAME.

No Events found!

Top