On 19/03/2010 14:57, joerg.schill...@fokus.fraunhofer.de wrote:
Darren J Moffat<darren.mof...@oracle.com> wrote:
That assumes you are writing the 'zfs send' stream to a file or file
like media. In many cases people using 'zfs send' for they backup
strategy are they are writing it back out using 'zfs recv' into another
pool. In those cases the files can even be restored over NFS/CIFS by
using the .zfs/snapshot directory
If you unpack the datastream from zfs send on a machine on a different location
that is safe against e.g. a fire that destroys the main machine, you may call
it a backup.
I'm curious, why isn't a 'zfs send' stream that is stored on a tape yet
the implication is that a tar archive stored on a tape is considered a
backup ?
ZFS system attributes (as used by the CIFS server and locally) ?
star does support such things for Linux and FreeBSD, the problem on Solaris is
that the documentation of the interfaces for this Solaris local feature is poor.
The was Sun tar archives the attibutes is non-portable.
Could you point to documentation?
getattrat(3C) / setattrat(3C)
Even has example code in it.
This is what ls(1) uses.
ZFS dataset properties (compression, checksum etc) ?
Where is the documentation of the interfaces?
There isn't any for those because the libzfs interfaces are currently
still private. The best you can currently do is to parse the output of
'zfs list' eg.
zfs list -H -o compression rpool/export/home
Not ideal but it is the only publicly documented interface for now.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
