You could use SAN zoning of the affected LUN's to keep multiple hosts
from seeing the zpool. When failover time comes, you change the zoning
to make the LUN's visible to the new host, then import. When the old
host reboots, it won't find any zpool. Better safe than sorry
Or change the LUN
On Jan 26, 2007, at 13:52, Marion Hakanson wrote:
[EMAIL PROTECTED] said:
. . .
realize that the pool is now in use by the other host. That leads
to two
systems using the same zpool which is not nice.
Is there any solution to this problem, or do I have to get Sun
Cluster 3.2 if
I want to
On Jan 26, 2007, at 10:52, Marion Hakanson wrote:
Perhaps I'm stating the obvious, but here goes:
You could use SAN zoning of the affected LUN's to keep multiple hosts
from seeing the zpool. When failover time comes, you change the zoning
to make the LUN's visible to the new host, then import.
[EMAIL PROTECTED] said:
> . . .
> realize that the pool is now in use by the other host. That leads to two
> systems using the same zpool which is not nice.
>
> Is there any solution to this problem, or do I have to get Sun Cluster 3.2 if
> I want to serve same zpools from many hosts? We may try S
James C. McPherson wrote:
> You can't do it *safely* without the protection of a high-
> availability framework such as SunCluster.
Thanks for the fast reply. :) We'll have look into the Cluster solution.
--
Ari-Pekka Oksavuori
___
zfs-discuss maili
Ari-Pekka Oksavuori wrote:
Hi!
I've been testing ZFS, and would like to use it on SAN attached disks in
our production environment, where multiple machines can see the same
zpools. I'm having some concerns about importing/exporting pools on
possible failure situations. If box that was using some
