Changeset 53f08ad11972b3da0c57137e8af5c5b35caa41fe for zetaback.in
- Timestamp:
- 07/08/07 15:20:06 (6 years ago)
- git-parent:
- Files:
-
- zetaback.in (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
zetaback.in
rdc9508e r53f08ad 17 17 $RESTORE $RESTORE_HOST $RESTORE_ZFS $TIMESTAMP 18 18 $LIST $SUMMARY $SUMMARY_EXT $SUMMARY_VIOLATORS 19 $FORCE_FULL $EXPUNGE $NEUTERED $ZFS 19 $FORCE_FULL $EXPUNGE $NEUTERED $ZFS $SHOW_FILENAMES 20 20 $VERSION $HELP/; 21 21 $version_string = '0.1'; … … 37 37 zetaback -v 38 38 39 zetaback [-l | -s | -sx | -sv] [- c conf] [-d] [-h host] [-z zfs]39 zetaback [-l | -s | -sx | -sv] [--files] [-c conf] [-d] [-h host] [-z zfs] 40 40 41 41 zetaback -b [-f] [-x] [-c conf] [-d] [-n] [-h host] [-z zfs] … … 66 66 "v" => \$VERSION, 67 67 "f" => \$FORCE_FULL, 68 "files" => \$SHOW_FILENAMES, 68 69 ); 69 70 … … 183 184 Display all ZFS disks in the current store that violate the configured 184 185 retention policy. 186 187 =item --files 188 189 Display the on-disk file representing the backup for each backup named in 190 the output. This is useful with the -sv flag to name violating files. 191 Often times, violators are filesystems that have been removed on the host 192 machines and zetaback can no longer back them up. Be very careful if you 193 choose to automate the removal of such backups as filesystems that would be 194 backed up by the next regular zetaback run will often show up as violators. 185 195 186 196 =item -b … … 753 763 my @st = stat($info->{full}->{$point}->{file}); 754 764 print "FULL " . pretty_size($st[7]); 765 print "\n\tfile: $info->{full}->{$point}->{file}" if($SHOW_FILENAMES); 755 766 } else { 756 767 my @st = stat($info->{incremental}->{$point}->{file}); 757 768 print "INCR from [$info->{incremental}->{$point}->{depends}] " . pretty_size($st[7]); 769 print "\n\tfile: $info->{incremental}->{$point}->{file}" if($SHOW_FILENAMES); 758 770 } 759 771 print "\n";