ZFS snapshotting and mirroring
Monday, June 2nd, 2008Although ZFS seamlessly will support synchronous mirrors over multiple backend storage arrays, there are some advantages in keeping the mirror process asynchronous.
(more…)
Although ZFS seamlessly will support synchronous mirrors over multiple backend storage arrays, there are some advantages in keeping the mirror process asynchronous.
(more…)
I’m now using default zpool paths (which implies an automatic import and mount on reboot).
I just imported the bb-archive.isys zpool onto the first host, then rebooted it. After it had shut down, I forcibly imported the zpool onto the second host. Now waiting for the first to come back up. It should, perhaps, complain that the zpool is owned by someone else, but should not do a forcible reimport…
And alas, that’s not what happens. So:
I’m going to use altroots for all zpools. Unfortunately, this forces the subdirs to appear only mounted under the altroot. Not quite the combination I was after.
OK, so nsr picks up the filesystems to try to save from /etc/vfstab. Fine, except that (a) that means it tries to back up the contractfs(!) and (b) ZFS doesn’t use vfstab entries for its filesystems.
Solution: specify the service IP address explicitly together with a bunch of paths under the networker configuration.