Amdump issues: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 30: | Line 30: | ||
[[Amdump: Backup size is the same regardless of the backup level]] | [[Amdump: Backup size is the same regardless of the backup level]] | ||
[[sendbackup error: no backup size line]] | |||
---- | ---- | ||
Issues with other Amanda programs: see [[Troubleshooting]] | Issues with other Amanda programs: see [[Troubleshooting]] | ||
Revision as of 22:56, 1 December 2006
If you have any problem with amdump first make sure that the command amcheck still succeeds. The amcheck command also points you to a much more detailed and to the point problem area than e.g. the amdump error "all disks failed"
Here is list of issues that amdump may encounter:
Amdump: dumps way too big, must skip incremental dumps
Amdump: infofile update failed
Amdump: cannot overwrite active tape
Amdump: mesg read: Connection reset by peer
- This can also trigger error message: sendbackup: "index tee cannot write"
Why does 'amdump' not dump to the holding disk?
Why does 'amdump' give me 'Tape I/O error'?
Why does 'amdump fail to create level 0 dump'
Amdump: Backup size is the same regardless of the backup level
sendbackup error: no backup size line
Issues with other Amanda programs: see Troubleshooting