Let me drag this thread kicking and screaming back to ZFS... Use case:
- We need an NFS server that can be replicated to another building to handle both scheduled powerdowns and unplanned outages. For scheduled powerdowns we'd want to fail over a week in advance, and fail back some time later. - We will use a virtual IP for seamless failover, and require that we not get stale NFS filehandles during a failover event, as world reboots are messy and expensive. - We do _not_ require synchronous replication. Async is fine. Today, there is _no_ rasonably priced solution that allows us to use ZFS for this. Yes, we have SRDF, and use it where required, but it's hideously expensive, and has its own risks (see below). Today our solution for the above is NetApp filers. We're not thrilled with everything about them, but they mostly work. One of the projects I've done is set up automated zfs replication for pure DR. But sadly this is of limited use, as Solaris / ZFS's lack of ability to maintain NFS file handles across systems is a deal killer for most of our users. AVS does not appear to support our weeks-long failover model, and exposes us to too much risk of simultaneous data loss. SRDF and Veritas replication have the same data loss risk. SRDF can easily support weeks-long a personality swap, I don't know enough about Veritas' product. -- Carson _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
