Hi Tobias, I did this for a large lab we had last month, I have it setup something like this.
zfs snapshot [EMAIL PROTECTED] zfs send -i [EMAIL PROTECTED] [EMAIL PROTECTED] | ssh server2 zfs recv rep_pool ssh zfs destroy [EMAIL PROTECTED] ssh zfs rename [EMAIL PROTECTED] [EMAIL PROTECTED] zfs destroy [EMAIL PROTECTED] zfs rename [EMAIL PROTECTED] [EMAIL PROTECTED] I was using this for a set up with on master systems and 100 system that I replicated the zpool to, and I had scripts that was used when a student logged out to do a zfs rollback [EMAIL PROTECTED] to reset it to known state to be ready for a new student. I don't have the actual script I used here right now, so I might have missed some flags, but you see that basic flow of it. /peter On Jun 6, 2008, at 14:07, Tobias Exner wrote: > Hi, > > I'm thinking about the following situation and I know there are some > things I have to understand: > > I want to use two SUN-Servers with the same amount of storage capacity > on both of them and I want to replicate the filesystem ( zfs ) > incrementally two times a day from the first to the second one. > > I know that the zfs send/receive commands will do the job, but I don't > understand exactly how zfs will know what have to be transferred.. > Is it > the difference to the last snapshot? > > If yes, does that mean that I have to keep all snapshots to achieve an > "incremental-forever" configuration? --> That's my goal! > > > > > regards, > > Tobias Exner > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
