Matthew Ahrens wrote:
Nicolas Dorfsman wrote:
Hi,
There's something really bizarre in ZFS snaphot specs : "Uses no
separate backing store." .
Hum...if I want to mutualize one physical volume somewhere in my SAN
as THE snaphots backing-store...it becomes impossible to do !
Really bad.
Is there any chance to have a "backing-store-file" option in a future
release ?
In the same idea, it would be great to have some sort of propertie to
add a disk/LUN/physical_space to a pool, only reserved to
backing-store. At now, the only thing I see to disallow users to use
my backing-store space for their usage is to put quota.
If you want to copy your filesystems (or snapshots) to other disks, you
can use 'zfs send' to send them to a different pool (which may even be
on a different machine!).
The confusion is probably around the word snapshot and all its various
usage over the years.
The one particular case people will probably slam their head into a wall
is exporting snapshots to other hosts. If you can get the customer or
tech to think in terms of where they want the data and how instead of
snapshots, or lun copies, or whatever, it makes for an easier conversation.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
