On Wed, Mar 24, 2010 at 4:00 PM, Khyron <khyron4...@gmail.com> wrote:

> Yes, I think Eric is correct.
>
> Funny, this is an adjunct to the thread I started entitled "Thoughts on ZFS
> Pool
> Backup Strategies".  I was going to include this point in that thread but
> thought
> better of it.
>
> It would be nice if there were an easy way to extract a pool configuration,
> with
> all of the dataset properties, ACLs, etc. so that you could easily reload
> it into a
> new pool.  I could see this being useful in a disaster recovery sense, and
> I'm
> sure people smarter than I can think of other uses.
>
> From my reading of the documentation and man pages, I don't see that any
> such command currently exists.  Something that would allow you dump the
> config into a file and read it back from a file using typical Unix
> semantics like
> STDIN/STDOUT.  I was thinking something like:
>
> zpool dump <pool> [-o <filename>]
>
> zpool load <pool> [-f <filename]
>
> Without "-o" or "-f", the output would go to STDOUT or the input would come
>
> from STDIN, so you could use this in pipelines.  If you have a particularly
> long
> lived and stable pool, or one that has been through many upgrades, this
> might
> be a nice way to save a configuration that you could restore later (if
> necessary)
> with a single command.
>

I don't use ACLs, but you can get the pool configuration and dataset
properties via "zfs get poolname".  With some fancy scripting, you should be
able to come up with something that would take that output and recreate the
pool with the same settings.

-- 
Freddie Cash
fjwc...@gmail.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to