In addition I did an amverify DATAOND This is the report on that: Tapes: DATAOND06 Errors found: DATAOND06 (daeserver._data_admin__intern.20060921.0): amrestore: 0: skipping start of tape: date 20060922 label DATAOND06 amrestore: 1: restoring daeserver._data_admin__intern.20060921.0
gzip: stdin: unexpected end of file amrestore: 2: reached end of information /bin/tar: Onverwacht bestandseinde in archief /bin/tar: Error is not recoverable: exiting now 64+0 in 64+0 out DATAOND06 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DATAOND06 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DATAOND06 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DATAOND06 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out DATAOND06 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out amverify DATAOND vr sep 22 10:17:28 CEST 2006 Using device /dev/nht0 Volume DATAOND06, Date 20060922 ** Error detected (daeserver._data_admin__intern.20060921.0) amrestore: 0: skipping start of tape: date 20060922 label DATAOND06 amrestore: 1: restoring daeserver._data_admin__intern.20060921.0 gzip: stdin: unexpected end of file amrestore: 2: reached end of information /bin/tar: Onverwacht bestandseinde in archief /bin/tar: Error is not recoverable: exiting now 64+0 in 64+0 out ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Too many errors. Since a couple of days i receive this error-report when a tape backup is madeĀ : These dumps were to tape DATAOND05. *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DATAOND06. FAILURE AND STRANGE DUMP SUMMARY: xxxxxxxx /data/daimail lev 1 FAILED [out of tape] xxxxxxxx /data/home lev 2 STRANGE Now when doing amflush I get this report: The dumps were flushed to tape DATAOND06. *** A TAPE ERROR OCCURRED: [[writing file: Input/output error]]. Some dumps may have been left in the holding disk. Run amflush again to flush them to tape. The next tape Amanda expects to use is: DATAOND07. FAILURE AND STRANGE DUMP SUMMARY: daeserver /data/admin_intern lev 0 FAILED [out of tape] ... NOTES: driver: WARNING: /var/amanda/cache: 47185920 KB requested, but only 37455780 KB available. taper: tape DATAOND06 kb 448448 fm 1 writing file: Input/output error DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -------------------------- --------------------------------- ------------ xxxxxxxx -min_intern 0 N/A 0 -- N/A N/A FAILED ---- xxxxxxxx -ta/daimail NO FILE TO FLUSH ----------------------------- xxxxxxxx -a/dossiers NO FILE TO FLUSH ----------------------------- xxxxxxxx /data/home NO FILE TO FLUSH ----------------------------- xxxxxxxx -a/intranet NO FILE TO FLUSH ----------------------------- (brought to you by Amanda version 2.4.4p2)