Data timeout: Difference between revisions
Jump to navigation
Jump to search
m (Amdump: data timeout moved to Data timeout: error message) |
(reformat, use header template) |
||
Line 1: | Line 1: | ||
{{Troubleshooting | {{Troubleshooting Header}} | ||
=Problem= | |||
The backup starts normally but the following message shows up in the report: | The backup starts normally but the following message shows up in the report: | ||
myhost.com /disk1 lev 0 FAILED [data timeout] | myhost.com /disk1 lev 0 FAILED [data timeout] | ||
=Explanation= | |||
The cause of this is usually a slow client host which has to compress a large disk. If compression takes a long time, the server does not receive any data from the client and generates a "data timeout". | The cause of this is usually a slow client host which has to compress a large disk. If compression takes a long time, the server does not receive any data from the client and generates a "data timeout". | ||
=Solution= | |||
You can try one of these: | You can try one of these: | ||
* Disable compression on the failing DLE (by putting <tt>compress none</tt> in disklist file) | * Disable compression on the failing DLE (by putting <tt>compress none</tt> in disklist file) |
Latest revision as of 23:18, 22 May 2007
This article is a part of the Troubleshooting collection.
Problem
The backup starts normally but the following message shows up in the report:
myhost.com /disk1 lev 0 FAILED [data timeout]
Explanation
The cause of this is usually a slow client host which has to compress a large disk. If compression takes a long time, the server does not receive any data from the client and generates a "data timeout".
Solution
You can try one of these:
- Disable compression on the failing DLE (by putting compress none in disklist file)
- Use 'fast' rather than 'best' compression (by putting compress client fast in disklist file)
- Compress data on the tape host (by putting compress server fast or compress server best in disklist file).
- Increase the dtimeout parameter in amanda.conf