Due to budget constraints I have to reinvent an Enterprise backup system in a SPARC (sun4v) Solaris estate (10 & 11). (yep - reinvent wheel, fun but time consuming. Is this wise?! :confused: )
For each filesystem of interest, to try to capture a 'catalog' at the front of each cpio archive (for... (1 Reply)
cpio(4) Kernel Interfaces Manual cpio(4)NAME
cpio - format of cpio archive
DESCRIPTION
The header structure, when the option of is not used (see cpio(1)), is:
When the option is used, the header information is described by:
Longtime and Longfile are equivalent to and respectively. The contents of each file are recorded together with other items describing the
file. Every instance of contains the constant 070707 (octal). The items through have meanings explained in stat(2). The length of the
null-terminated path name including the null byte, is given by
The last record of the archive always contains the name Directories and the trailer are recorded with equal to zero.
It will not always be the case that and correspond to the results of but the values are always sufficient to tell whether two files in the
archive are linked to each other.
When a device special file is archived by HP-UX (using the option), contains a magic constant which is dependent upon the implementation
doing the writing. flags the device file as an HP-UX 32-bit device specifier, and contains the 32-bit device specifier (see stat(2)). If
the option is not present, special files are not archived or restored. Non-HPUX device special files are never restored.
SEE ALSO cpio(1), find(1), stat(2).
STANDARDS CONFORMANCE cpio(4)