Topic: Backup with Dar Error

[echeung]

Hi

I am using SME Server 7.3 and Backup with Dar to backup to a USB disk, but I get the following errors:

In first email:
No terminal found for user interaction. All questions will be assumed a negative answer (less destructive choice), which most of the time will abort the program.
Received signal: Terminated
Archive delayed termination engaged
Disabling signal handler, the next time this signal is received the program will end immediately
Program has been aborted for the following reason: Thread cancellation requested, aborting as properly as possible
Dar error during backup : 4
Backup terminated: backup failed - status: 7424

In second email:
Backup of mysql databases has been done.
Mounting backup shared directory localhost/media/usbdisk
Backup temp directory /media/usbdisk/tmp_dir/server08.cns.local is mounted and is writable
Using set number 2 of 3
full backup
Backup base file name is full-20080129
Making backup on temporary dir...
using a backup session timeout of : 3570 seconds
*** No backup allowed or error during backup ***
Dar error during backup : 4

What is the error? How can I solve it?

[raem]

echeung

Look at your log files to see if there is further information.

http://dar.linux.free.fr/doc/man/dar.html#EXIT%20CODES

EXIT CODES

dar exits with the following code:
   

0 - Operation successful.

1 - Syntax error on command-line.

2 - Error due to a hardware problem or a lack of memory.

3 - Detection of a condition that should never happen, and which is considered as a bug of the application.

4 - Code issued when the user has aborted the program upon dar question from dar. This also happens when dar is not run from a terminal (for example launched from crontab) and dar has a question to the user. In that case, dar aborts the same way as if the user pressed the escape key at the question prompt.

5 - is returned when an error concerning the treated data has been detected. While saving, this is the case when a file could not be opened or read. While restoring, it is the case when a file could not be created or replaced While comparing, it is the case when a file in the archive does not match the one in the filesystem. While testing, it is the case when a file is corrupted in the archive.

6 - an error occurred while executing user command (given with -E or -F option). Mainly because the creation of a new process is not possible (process table is full) or the user command returned an error code (exit status different of zero).

7 - an error has occurred when calling a libdar routine. This means the caller (dar program), did not respect the specification of the API (and this can be considered as a particular case of a bug).

8 - the version of dar used is based in finite length integers (it has been compiled with the option --enable-mode=...). This code is returned when an integer overflow occurred. use the full version (based in infinint) to avoid this error.

9 - this code indicates an unknown error. I have probably forgotten to update the exception caching code to take care of new exceptions... this is a minor bug you are welcome to report.

10 - you have tried to use a feature that has been disabled at compilation time.

11 - some saved files have changed while dar was reading them, this may lead the data saved for this file not correspond to a valid state for this file. For example, if the beginning and the end of the file have been modified at the same time (while dar is reading it), only the change at the end will be saved (the beginning has already been read), the resulting state of the file as recorded by dar has never existed and may cause problem to the application using it.