Date: Sun, 09 Aug 2020 07:24:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248545] zfs: add possibility to create an initial send stream without intervening snapshots Message-ID: <bug-248545-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248545 Bug ID: 248545 Summary: zfs: add possibility to create an initial send stream without intervening snapshots Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: d8zNeCFG@aon.at Scenario: - FreeBSD 12.1-RELEASE-p6 - Using "zfs send" to create backups - Using "-R" flag to create backups of zfs filesystem hierarchies - Using "-I" or "-i" to create incremental backups - For these backups, specifically named snapshots are used which are created using "zfs snapshot -r <top filesystem>" (the <top filesystem> is not necessarily a complete pool but can be a subset of a pool). - There are other (intervening) snapshots that are irrelevant for backup purposes. Result: 1. It is possible to create a full recursive backup stream (similar to a le= vel 0 dump) using "zfs send -R ...", including all intervening snapshots, even those irrelevant for backup purposes. 2. It is NOT possible to create a full recursive backup stream using "zfs s= end -R ...", excluding all intervening snapshots. 3. It is possible to create an incremental recursive backup stream using "z= fs send -R -I ...", including all intervening snapshots. 4. It is possible to create an incremental recursive backup stream using "z= fs send -R -i ...", excluding all intervening snapshots. Expected result: It should be possible to create a full recursive backup stream WITHOUT the intervening snapshots (case 2. above). -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248545-227>