I have and old dump format backup done under fedora 7 which is stored on disk and has an sha256sum file that indicates there are no data errors in the backup file.? When I try to read the file with restore under CentOS 6,? I get the following error: cat /etc/redhat-release CentOS release 6.10 (Final) restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps Input is from a local file/pipe Checksum error 20311110402, inode 0 file (null) restore: Tape is not a dump tape I have another copy of the backup on another disk with the same checksum and it gets the same error as well. Here's a log file from when the backup was done back in 2009: DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 ? DUMP: Dumping /dev/md1 (/u1) to u1_l0_04-29-09_md1.dump ? DUMP: Label: /u1 ? DUMP: Writing 10 Kilobyte records ? DUMP: Compressing output at compression level 2 (bzlib) ? DUMP: mapping (Pass I) [regular files] ? DUMP: mapping (Pass II) [directories] ? DUMP: estimated 95176885 blocks. ? DUMP: writing QFA positions to u1_l0_04-29-09_md1.qindex ? DUMP: Volume 1 started with block 1 at: Wed Apr 29 09:25:05 2009 ? DUMP: dumping (Pass III) [directories] ? DUMP: dumping (Pass IV) [regular files] ? DUMP: 0.96% done at 3032 kB/s, finished in 8:38 ????? . ????? . ????? . ?DUMP: 100.00% done at 4075 kB/s, finished in 0:00 ? DUMP: Closing u1_l0_04-29-09_md1.dump ? DUMP: Volume 1 completed at: Wed Apr 29 16:00:09 2009 ? DUMP: Volume 1 took 6:35:04 ? DUMP: Volume 1 transfer rate: 2146 kB/s ? DUMP: Volume 1 96607840kB uncompressed, 50878096kB compressed, 1.899:1 ? DUMP: 96607840 blocks (94343.59MB) on 1 volume(s) ? DUMP: finished in 23704 seconds, throughput 4075 kBytes/sec ? DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 ? DUMP: Date this dump completed:? Wed Apr 29 16:00:09 2009 ? DUMP: Average transfer rate: 2146 kB/s ? DUMP: Wrote 96607840kB uncompressed, 50878096kB compressed, 1.899:1 ? DUMP: DUMP IS DONE Have there been any changes to the format of dump files and if so, is there a version available that can read this older backup? Any other suggestions on how to read this backup would be helpful. Thank You, Nataraj
--On Friday, November 02, 2018 8:03 PM -0700 Nataraj <incoming-centos at rjl.com> wrote:> Have there been any changes to the format of dump files and if so, is > there a version available that can read this older backup? Any other > suggestions on how to read this backup would be helpful.If you get no help here. I recommend the dump mailing list. I haven't used dump in a very long time but the mailing list was quite helpful when I had issues. <https://sourceforge.net/projects/dump/lists/dump-users>
> > restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps > Input is from a local file/pipe > Checksum error 20311110402, inode 0 file (null) > restore: Tape is not a dump tapewhat does 'file' think the file is - i.e. what does file u1_l0_04-29-09_md1.dump say?> > > Here's a log file from when the backup was done back in 2009: > > DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 > DUMP: Dumping /dev/md1 (/u1) to u1_l0_04-29-09_md1.dump > DUMP: Label: /u1 > DUMP: Writing 10 Kilobyte records > DUMP: Compressing output at compression level 2 (bzlib)> DUMP: finished in 23704 seconds, throughput 4075 kBytes/sec > DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 > DUMP: Date this dump completed: Wed Apr 29 16:00:09 2009 > DUMP: Average transfer rate: 2146 kB/s > DUMP: Wrote 96607840kB uncompressed, 50878096kB compressed, 1.899:1 > DUMP: DUMP IS DONEThe dump is compressed. What was the command line you used to create the dump file? Have you tried using restore tzvf u1_l0_04-29-09_md1.dump> > Have there been any changes to the format of dump files and if so, is > there a version available that can read this older backup?I don't think dump has changed anything in 20 years or so! And I certainly can't see it changing such that it can't read old files - that is, sort of, it's raison d'etre. P.
> On Nov 3, 2018, at 06:26, Pete Biggs <pete at biggs.org.uk> wrote: > I don't think dump has changed anything in 20 years or so! And I > certainly can't see it changing such that it can't read old files - > that is, sort of, it's raison d'etre.A bit off topic but... Funny story, at a previous job, my boss was able to extract the data off tapes made in the 80s on tops-20 systems (iirc) with the version of restore on FreeBSD, but couldn?t get the tape drive to work on anything but Linux, so he had to extract the tapes on a RHL system then copy them to FreeBSD to read into the restore program. He actually was able to find the data he was looking for. -- Jonathan Billings
On Sat, 3 Nov 2018 at 06:27, Pete Biggs <pete at biggs.org.uk> wrote:> > > > > > restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps > > Input is from a local file/pipe > > Checksum error 20311110402, inode 0 file (null) > > restore: Tape is not a dump tape > > what does 'file' think the file is - i.e. what does > > file u1_l0_04-29-09_md1.dump > > say? > > > > > > > Here's a log file from when the backup was done back in 2009: > > > > DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 > > DUMP: Dumping /dev/md1 (/u1) to u1_l0_04-29-09_md1.dump > > DUMP: Label: /u1 > > DUMP: Writing 10 Kilobyte records > > DUMP: Compressing output at compression level 2 (bzlib) > > > > DUMP: finished in 23704 seconds, throughput 4075 kBytes/sec > > DUMP: Date of this level 0 dump: Wed Apr 29 09:24:36 2009 > > DUMP: Date this dump completed: Wed Apr 29 16:00:09 2009 > > DUMP: Average transfer rate: 2146 kB/s > > DUMP: Wrote 96607840kB uncompressed, 50878096kB compressed, 1.899:1 > > DUMP: DUMP IS DONE > > The dump is compressed. What was the command line you used to create > the dump file? > > Have you tried using > > restore tzvf u1_l0_04-29-09_md1.dump >I agree with Pete and it will be up to see what file and others say to see which type of compression was done.. (z means gzip, j means bzip2 which would be the ones from 2009).> > > > Have there been any changes to the format of dump files and if so, is > > there a version available that can read this older backup? > > I don't think dump has changed anything in 20 years or so! And I > certainly can't see it changing such that it can't read old files - > that is, sort of, it's raison d'etre. > > P. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos-- Stephen J Smoogen.
On 11/3/18 3:26 AM, Pete Biggs wrote:>> restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps >> Input is from a local file/pipe >> Checksum error 20311110402, inode 0 file (null) >> restore: Tape is not a dump tape > what does 'file' think the file is - i.e. what does > > file u1_l0_04-29-09_md1.dumpu1_l0_04-29-09_md1.dump:?? data Which I did think was odd.? I had also tried bzcat u1_l0_04-29-09_md1.dump bzcat: u1_l0_04-29-09_md1.dump is not a bzip2 file. but I didn't remember if dump might have it's own headers before the compressed data.> The dump is compressed. What was the command line you used to create > the dump file? > > Have you tried using > > restore tzvf u1_l0_04-29-09_md1.dumpThe version of restore that I have under CentOS 6 does not have any compression options except for -l.? Only dump has the compression options and restore is supposed to recognize the compression I believe.? The z option definitely does not work. Maybe the file is bad.? I am going to look to see if I can find any other backups of that system. Thank You, Nataraj