This will help for any new mounts (so you don't have to go through the bother of relinking) but won't solve the problem of processes hanging on already mounted filesystems.
As already stated, for the "live" server to take over it would have to have an interface with both the IP address and MAC address changed and the NVRAM state copied. But also, I don't think that the NFS filehandles for the "live" filesystem would match the "dead" filesystem and you would get stale filehandles so this would only work if you were sharing the same filesystem between the two systems (which is what the new Netapp failover solution does).
-Steve gremban@ti.com
Mark D Simmons wrote:
Seeing as the specific data in question could be considered readonly to the majority of clients, why not have them use an automount map with both filers in.
We do that for our centrally maintained and served binaries and db's and it works very well.
Hi,
We have two netapp filers serving mainly static data (updated overnight) to several hp-ux clients.
If one server fails we can swap the clients onto the other server by mounting and switching symbollic links.