Jakub,
Dnia czwartek, 7 czerwca 2007 15:53, Jim Dunham napisał:
Yes, placing the replica in logging mode is a requirement.
For the same reasons that two Solaris nodes can not access the same
"imported" ZFS storage pool at the same time, a local and remote SNDR
node should not access the same "imported" ZFS storage pool.
One way to achieve this is by placing SNDR in logging mode, another
is "zpool export" the SNDR primary, before "zpool import" the SNDR
secondary. If you choose either of these methods, make sure to "zpool
export" the SNDR secondary before taking the SNDR set out of logging
mode, or "zpool importing" the SNDR primary node.
Still another way is to use II portion of Availability Suite, and
take an II Point-in-time copy of the replicating ZFS storage pool,
and then zpool import the II shadow volume(s).
Thanks for quick reply ! :)
I'm aware of the procedure...
Maybe I'm wrong, but my small suggestion was that there should be
some kind of
inteligence builtin in ZFS kernel code or maybe zpool command that
prevents
importing non II shadowed ZFS volumes, thus preventing this panic.
At this time ZFS is bundled with Solaris, and AVS is unbundled. When
this status changes, it will then be possible to establish interface
relationships between these two data services, similar to ZFS and the
support of zvols as iSCSI Targets via shareiscsi.
--
Jakub Wartak
-vnull
http://vnull.pcnet.com.pl
Jim Dunham
Solaris, Storage Software Group
Sun Microsystems, Inc.
1617 Southwood Drive
Nashua, NH 03063
http://blogs.sun.com/avs
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
