Hello, Am 07.10.20 um 23:50 schrieb Nathan Stratton Treadway: > That is, I would make a copy of the original log.20201004123343.0 file > into some other directory, then used a txt editor to edit that > particular DONE line to remove the "000000" at the end of the > datetimestamp field... and then run the "amadmin ... find" command again > to see if that edit allowed it to start finding the vaulted copies of the > dumps.
I ended up patching the logfiles written by amvault, e.g. for $ fgrep 20020908 ../tapelist 20020908 BE-full-43 reuse $ amvault --dest-storage vtape be-full \* \* 20020908 I get log.20201018130312.0 afterwards. Then I do $ cp -p log.20201018130312.0 ../log_backup $ perl -p -i -e 's/ 20020908000000 / 20020908 /g' log.20201018130312.0 and then amvaulted dump images written to vtapes can be located by amadmin find: $ amadmin be-full find indigo-2 | egrep "date|2002-09" date host disk lv storage pool tape or file file part status 2002-09-08 indigo-2 / 0 vtape vtape vBE-full-014 54 1/1 OK 2002-09-08 indigo-2 / 0 be-full be-full BE-full-43 54 1/-1 OK $ amfetchdump -ostorage=vtape be-full indigo-2 / 20020908 1 volume(s) needed for restoration The following volumes are needed: vBE-full-014 Press enter when ready Reading label 'vBE-full-014' filenum 54 FILE: date 20020908 host indigo-2 disk / lev 0 comp N program /sbin/xfsdump 1819872 kb
