DL Consulting wrote:
Just reread your response. If the send/recv fails the snapshot should NOT turn up on chucky (the recv machine) right? However, it is turning up but the original on the sending machine is being destroyed by something (which I'm guessing is the time-slider-cleanup cronjob below)
Yes, but this is configurable via SMF. To see the properties: svccfg -s auto-snapshot:daily listprop and you can set them as desired svccfg -s auto-snapshot:daily setprop zfs/keep=62 for more info, see http://docs.sun.com/app/docs/doc/817-2271/gbcxl?a=view
Here's the full crontab for root 10 3 * * * /usr/sbin/logadm 15 3 * * 0 [ -x /usr/lib/fs/nfs/nfsfind ] && /usr/lib/fs/nfs/nfsfind 30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean 30 0,9,12,18,21 * * * /usr/lib/update-manager/update-refresh.sh 5,20,35,50 * * * * /usr/lib/time-slider-cleanup -y Do you have any suggestions as to why they're being destroyed and why they're being destroyed after the a gap of 1 hour 4 minutes (that's the delay between taking the snapshot and the start of sending/receiving)? time-slider-cleanup would have run 4 times during that period.
Your script should match the policy you wish to implement. -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
