Mika Borner wrote:
-The mechanism to asynchronously replicate to another host could be
simulated using zfs send/receive. Still, I would prefer having a
replication, that is automatically triggered, like Sun's StorEdge
Network Data Replicator does this for UFS. This could be easily
implemented in ZFS, I guess.
Yep, you can roll your own remote replication using zfs send/receive.
Eventually ZFS will provide a more automated way of setting this up.
-I want to be sure, that nobody (maybe not even root) changes my
filesystems for the next couple of years.. I know there is a
read-only property, but it might not be enough. On our Hitachi array,
we have a WORM functionality, which blocks write access to a LUN
until a specified date. While this works, it is not as flexible as we
want it, as the LUNs are too big for our use. Every day we are
archiving documents. At the end of the day we want to freeze the
filesystem.
Sounds like you want to take a snapshot at the end of each day.
Snapshots can never be changed.
Would it be possible to add a time-lock property to ZFS?
Could this be extended to still allow new files to be added to the
locked file system , but not allowing to add/modify files (ZFS ACL's
could handle this)? Would something like this make sense?
Yep, we'd like to implement a mode where you can't remove any
information from a filesystem, but you can add more data to it. This is
related to 4890717 "want append-only files".
--matt
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
