Sorry for misinforming you, I have just noticed that I can't even restore Linux
files. In fact I can't restore any of the backed-up files. I tend to believe
it's a hardware problem.
Ciao, Erik.
-------- Original Message --------
Subject: Getting read errors on restore to Windows XP.
Date: Thu, 07 Jun 2007 18:53:17 +0200
From: Erik P. Olsen <epodata < at > gm...>
To: Bacula <bacula-users < at > li...>
I have 20 tapes full of back-ups of a Linux, a Windows 2000 and a Windows XP
system. The Linux system is the back-up server. Bacula version is 1.38.5. The
files I want to restore are quite old, so they can be found on several back-ups,
however, I get the same read error on each and every back-up I restore from,
only the file:blk is different. The error messages can be found below.
I have no problem restoring Linux files, so I assume the error message is fake
and tells something quite different. Can someone please help me through this
problem - if at all possible? It is a major disaster if I can't restore the files.
Thanks in advance.
07-Jun 18:34 epo-dir: Start Restore Job RestoreFiles.2007-06-07_18.34.22
07-Jun 18:35 epohost-sd: Please mount Volume "EPOL005" on Storage Device "DDS-4"
(/dev/nst0) for Job RestoreFiles.2007-06-07_18.34.22
07-Jun 18:37 epohost-sd: Ready to read from volume "EPOL005" on device "DDS-4"
(/dev/nst0).
07-Jun 18:37 epohost-sd: Forward spacing to file:block 10:0.
07-Jun 18:37 epohost-sd: RestoreFiles.2007-06-07_18.34.22 Error: block.c:940
Read error at file:blk 10:0 on device "DDS-4" (/dev/nst0). ERR=Input/output error.
07-Jun 18:37 epohost-sd: End of Volume at file 10 on device "DDS-4" (/dev/nst0),
Volume "EPOL005"
07-Jun 18:37 epohost-sd: End of all volumes.
07-Jun 18:38 epo-dir: Bacula 1.38.5 (18Jan06): 07-Jun-2007 18:38:14
JobId: 1538
Job: RestoreFiles.2007-06-07_18.34.22
Client: epoxp-fd
Start time: 07-Jun-2007 18:34:24
End time: 07-Jun-2007 18:38:14
Files Expected: 124
Files Restored: 0
Bytes Restored: 0
Rate: 0.0 KB/s
FD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Restore OK -- warning file count mismatch
--
Erik P. Olsen, MSc
Solsortvej 30, DK-2000 Frederiksberg, Denmark
Phone: +45 38346480, Fax: +45 32106480, Mobil: +45 40765300
Re: [Bacula-users] Bacula Waits for 40min When a Client is Down From: Kyle Marsh
Sorry if this double posts -- I used the wrong e-mail and the first
copy is at the mercy of the moderator. You can kill that one, btw.
On 6/7/07, Arno Lehmann <al < at > it...> wrote:
Hi,
On 6/7/2007 2:42 PM, Steve Campbell wrote:
I had the same thought about time-outs just yesterday. I am new to
Bacula, and was testing my second client backup, when I realized I had
not defined the client in my host file. I run my backups on an internal
network (non-public) so the DNS for this was not available either. I was
using bconsole, and the job hung up due to not being able to find the
client,
It should terminate almost immediately.
And yet the fact remains that for both Steve and me, it doesn't. You
suggested pinging the client with RunBeforeJob. Is there a better way
to do this than adding a new line in each job? You cannot put it in
the JobDefs because you need the hostname, and of course you cannot
extract that from anything in the Job field as far as I know, so it
has to appear magically.
and I was wondering how to kill it immediately, as it wasn't
going to find the client.
The cancel command...
Of course, I don't believe the cancel command is particularly
effective when your console is busy with something else, like waiting
40 minutes for a response that isn't coming. You need to start a new
bconsole and run cancel from there as far as I can tell.
As a new user, I didn't know if there is a
timeout value I could set, or how long it was going to run (maybe even
forever?).
So, good question, Arno, and I hope someone provides the answer.
Erm, which was the question?
:-)
Arno
Steve
Arno Lehmann wrote:
Hi,
On 6/6/2007 10:57 PM, Kyle Marsh wrote:
Howdy,
I'm working on a bacula setup for my college and I have found that
when a client goes down, whether it's firewalled, turned off, or
otherwise disconnected from the network, bacula seems to hang for
about 40 minutes
Unusual timeout, in my experience... I'd expect nearly instantaneous job
failure or the IT-related two hours...
before deciding that the client isn't there and
stopping. This could become problematic if we have several machines
down each night and could cause substantial problems if some backups
don't start until people are back working. Is there a directive that
allows me to specify something sane as the timeout period, and where
does it need to go?
I prefer leaving the timeouts to Bacula, and instead use "Run Before
Job" scripts to ping the clients. Concurrent jobs are a reasonable
solution against long-running or stalled jobs.
Arno
Thanks,
Kyle Marsh
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users
