[p4] Full redundency Perforcre server using NSI-software doub le-take - Stephen Vance - com.perforce.perforce-user

6 messages in com.perforce.perforce-user[p4] Full redundency Perforcre server...

From	Sent On	Attachments
Tyler, Tom	14 Jan 2003 12:32
Tyler, Tom	16 Jan 2003 05:50
John Blumel	16 Jan 2003 07:48
Stephen Vance	16 Jan 2003 08:15
Dan Kegel	16 Jan 2003 08:53
Stephen Vance	16 Jan 2003 10:19

Subject:	[p4] Full redundency Perforcre server using NSI-software doub le-take
From:	Stephen Vance (ste...@vance.com)
Date:	01/16/2003 08:15:58 AM
List:	com.perforce.perforce-user

Windows caches DNS entries for 10 minutes. It wreaks havoc with DNS-based failover schemes. You can use 'ipconfig /flushdns' to clear the cache.

Steve

At 09:49 AM 1/16/2003 -0600, John Blumel wrote:

On 1/16/03 7:51 AM, Tyler, Tom wrote:

Ahhh, there's another bit of magic to it. We had our DNS gurus set it up so that our users point their P4PORT to a machine alias, like "sourcebox.company.com:1777". Part of our failover procedure involves switching the DNS from the IP of the primary server to the IP of the backup server (which has a different IP and a separate license file).

Although, the workstations may cache the IP address supplied by the DNS server and still attempt to access the server that is down. Also, if you have users using DNS other than your primary or using hosts files, this method might not be immediately effective.

If you can get a secondary license file, keep Perforce running on the secondary server and duplicate your files to the secondary server, it would seem that all you would need to do is have the secondary server automatically add the IP address of the primary server as an alias and you wouldn't need any DNS changes as the secondary server will now respond to arp's for the primary server's IP address. Once the primary is ready to go back into service, remove the alias from the secondary and bring up the interface on the primary.