> On Mar 25, 2010, at 7:20 AM, Wolfraider wrote: > > This assumes that you have the storage to replicate > or at least restore all data to a DR site. While this > is another way to do it, it is not really cost > effective in our situation. > > If the primary and DR site aren't compatible, then it > won't be much of a > DR solution... :-P
Which assumes that we have a DR site. lol We are working towards a full DR site but the funding has been a little tight. That project should be started in the next year or 2. > > What I am thinking is basically having 2 servers. > One has the zpool attached and sharing out our data. > The other is a cold spare. The zpool is stored on 3 > JBOD chassis attached with Fibrechannel. I would like > to export the config at specific intervals and have > it ready to import on the cold spare if the hot spare > ever dies. The eventual goal would be to configure an > active/passive cluster for the zpool. > > You don't need to export the pool to make this work. > Just import it > n the cold spare when the primary system dies. KISS. > If you'd like > that to be automatic, then run the HA cluster > software. Which, when I asked the question, I wasn't sure how it all worked. I didn't know if the import process need a config file or not. I am learning alot, very quickly. We will be looking into the HA cluster in the future. The spare is a cold spare for alot of different roles so we cant dedicate it to just the solaris box (yet :) ). -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
