Is there a simple way to query zfs send binary objects for basic information
such as:
1) What snapshot they represent?
2) When they where created?
3) Whether they are the result of an incremental send?
4) What the the baseline snapshot was, if applicable?
5) What ZFS version number they where made from?
6) Anything else that would be useful to keep them around as backup binary blobs
on an archival system, e.g., SAM-QFS?
Thanks.
--
This message posted from opensolaris.org
On Jan 29, 2011, at 5:48 PM, stuart anderson wrote:> Is there a simple way to query zfs send binary objects for basic information such as: > > 1) What snapshot they represent? > 2) When they where created? > 3) Whether they are the result of an incremental send? > 4) What the the baseline snapshot was, if applicable? > 5) What ZFS version number they where made from? > 6) Anything else that would be useful to keep them around as backup binary blobs > on an archival system, e.g., SAM-QFS?zstreamdump has a -v option which will show header information. The structure of that documentation is only shown in the source, though. -- richard
On Jan 29, 2011, at 10:00 PM, Richard Elling wrote:> On Jan 29, 2011, at 5:48 PM, stuart anderson wrote: > >> Is there a simple way to query zfs send binary objects for basic information such as: >> >> 1) What snapshot they represent? >> 2) When they where created? >> 3) Whether they are the result of an incremental send? >> 4) What the the baseline snapshot was, if applicable? >> 5) What ZFS version number they where made from? >> 6) Anything else that would be useful to keep them around as backup binary blobs >> on an archival system, e.g., SAM-QFS? > > zstreamdump has a -v option which will show header information. The structure of > that documentation is only shown in the source, though.Thanks for the pointer. This has most of the information I am looking for. Do you know how to get zstreamdump to display whether it is parsing an incremental dump, and if so, what snapshot it is relative to? Put another way, given 2 zfs send binary blobs, can I determine if they are related without trying to restore them to a ZFS filesystem? Thanks. -- Stuart Anderson anderson at ligo.caltech.edu http://www.ligo.caltech.edu/~anderson
On Jan 30, 2011, at 11:19 AM, Stuart Anderson wrote:> > On Jan 29, 2011, at 10:00 PM, Richard Elling wrote: > >> On Jan 29, 2011, at 5:48 PM, stuart anderson wrote: >> >>> Is there a simple way to query zfs send binary objects for basic information such as: >>> >>> 1) What snapshot they represent? >>> 2) When they where created? >>> 3) Whether they are the result of an incremental send? >>> 4) What the the baseline snapshot was, if applicable? >>> 5) What ZFS version number they where made from? >>> 6) Anything else that would be useful to keep them around as backup binary blobs >>> on an archival system, e.g., SAM-QFS? >> >> zstreamdump has a -v option which will show header information. The structure of >> that documentation is only shown in the source, though. > > Thanks for the pointer. This has most of the information I am looking for. Do you know > how to get zstreamdump to display whether it is parsing an incremental dump, and if so, > what snapshot it is relative to? > > Put another way, given 2 zfs send binary blobs, can I determine if they are related > without trying to restore them to a ZFS filesystem?Each incremental send stream has a "from" and a "to" Global Unique Identifier (GUID) for the snapshots. As send stream with many incremental snapshots will have many of these pairs. -- richard
On Jan 30, 2011, at 1:49 PM, Richard Elling wrote:> On Jan 30, 2011, at 11:19 AM, Stuart Anderson wrote: >> >> On Jan 29, 2011, at 10:00 PM, Richard Elling wrote: >> >>> On Jan 29, 2011, at 5:48 PM, stuart anderson wrote: >>> >>>> Is there a simple way to query zfs send binary objects for basic information such as: >>>> >>>> 1) What snapshot they represent? >>>> 2) When they where created? >>>> 3) Whether they are the result of an incremental send? >>>> 4) What the the baseline snapshot was, if applicable? >>>> 5) What ZFS version number they where made from? >>>> 6) Anything else that would be useful to keep them around as backup binary blobs >>>> on an archival system, e.g., SAM-QFS? >>> >>> zstreamdump has a -v option which will show header information. The structure of >>> that documentation is only shown in the source, though. >> >> Thanks for the pointer. This has most of the information I am looking for. Do you know >> how to get zstreamdump to display whether it is parsing an incremental dump, and if so, >> what snapshot it is relative to? >> >> Put another way, given 2 zfs send binary blobs, can I determine if they are related >> without trying to restore them to a ZFS filesystem? > > Each incremental send stream has a "from" and a "to" Global Unique Identifier (GUID) for > the snapshots. As send stream with many incremental snapshots will have many of these > pairs.Got it. That works. Thanks. -- Stuart Anderson anderson at ligo.caltech.edu http://www.ligo.caltech.edu/~anderson