Hi,



The meaning of this "We move this offsite" is not understood well.
Which part is of the manual it?




Do you want to know FailBack operation?

It is necessary to describe a detailed setting of Alias.
The operation changes by setting your Alias.

Yoshinobu Ito

->The meaning of this "We move this offsite" is not understood well.
->Which part is of the manual it?

We will be moving the target server to a remote location so it will be connected via a WAN connection. However we want to test this in our LAN before moving the server to remote location. Not only allowing us to test but allowing us to have the data synched before moving to WAN location.


On page 121 of the Adminsitration Manual under the "Configuring failover across a WAN" there's an Important note stating "Do not specify any IP addresses to associate with the alias." This is between step 5 and 6.


->Do you want to know FailBack operation?

I would assume this is what I need to know. I need to know what the steps are to get the alias back on the source server once the source server is back in operation and synchronization is complete. As mentioned my understanding is that once the source server is brought online the synchronization from the target (the operating alias) begins synching data back to the source and once this sync has been completed then I need to "remove" the alias from the target so that the source gets the alias back. So there is nothing for me to configuring for setting the alias back to the source, I just wait for synchronization to be complete from the target to the source then remove the alias from the target.

Hi,

In the manual, there is description as follows.
------
Generally, it is not possible to perform a failover across a WAN
because IP addresses cannot be forwarded across different subnets.
------

You can perform a test of WAN composition by LAN.

You make only Alias.
You do not make the virtual IP.
Because you want to test the WAN composition.

I have tested WAN composition by LAN artificially.



The understanding of the FailBack operation seems to be correct.
Anyway, you should operate according to a step of 192 pages of "Restoring the original configuration" of the manual.

Yoshinobu

This raises another question then.

Our sites will be connected via a LAN to LAN VPN and both servers are domain controllers for the domain and thus have DNS serves on them since they are Windows 2003 server. So if we don't change the IP address in the DNS won't this cause problems when the clients try to connect to the alias because the DNS resolution will still be pointing to the source IP?

So by implementing a LAN to LAN do I need to follow the LAN configuration for the alias configuration?


JTT

Hi,

It is necessary to do "Zone forwarding" with DNS server each other.

There is no problem if it does so.

Moreover, you should take care about TTL.

There is a problem when TTL is 600sec of default.

Cash is used immediately after the failover because the DNS cash of the client is 600 seconds in this.

And, the client cannot be connected for at least ten minutes.

You must execute ipconfig/flushdns with a client to connect it.


Example: TTL 60 second

It comes to be able to connect the client in at least one minute.



The same segment, it is necessary to make virtual IP.
However, if it is a different segment, it is not necessary to make virtual IP.

I'm sorry.
Because I did not understand a meaning, there is not the confidence of the answer.

Yoshinobu

I believe this answers my questions, thanks for your help. I will set the IP during our test where the servers are on the same network and then modify the Alias fail over when we place it on the remote site.

Thanks again.

JTT