|
|
| (5 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| 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"
| | #redirect [[Troubleshooting]] |
| | |
| Here is list of issues that [[amdump]] may encounter:
| |
| | |
| | |
| [[ Amdump: results missing ]]
| |
| | |
| [[ Amdump: disk offline ]]
| |
| | |
| [[ Amdump: dumps way too big, must skip incremental dumps ]]
| |
| | |
| [[ Amdump: infofile update failed ]]
| |
| | |
| [[ Amdump: cannot overwrite active tape ]]
| |
| | |
| [[ Amdump: /sbin/dump returned 1 ]]
| |
| | |
| [[ 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 is terribly slow]]
| |
| | |
| ----
| |
| Issues with other Amanda programs: see [[Troubleshooting]]
| |