comment below...
Robert Milkowski wrote:
Hello Richard,
Wednesday, November 1, 2006, 11:36:14 PM, you wrote:
REP> Adam Leventhal wrote:
On Wed, Nov 01, 2006 at 04:00:43PM -0500, Torrey McMahon wrote:
Lets say server A has the pool with NFS shared, or iSCSI shared,
volumes. Server A exports the pool or goes down. Server B imports the pool.
Which clients would still be active on the filesystem(s)? The ones that
were mounting it when it was on Server A?
Clients would need to explicitly change the server they're contacting unless
that new server also took over the IP address, hostname, etc.
REP> Does this imply that using Sun Cluster, which transfers (logical) IP
REP> addresses, would easily provide an HA-iSCSI service? I'll admit that
REP> I still don't understand the iSCSI naming and security schemes.
I haven't played with iSCSI (yet) but is really hostname necessary?
What else? Putting zpool under SC with an IP address in SC group
should be enough I hope - or maybe not?
I haven't played with iSCSI lately, but it is unlikely I would have used a
hostname. They just aren't worth setting up on a test net.
For an HA cluster, the hostname/IP address mapping is usually done in a
name service for clients. Since the IP address fails over, there is no
need to change the hostname/IP address association. There are, of course,
a number of corner cases that bite occasionally, but if you KISS, life will
be more enjoyable.
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
