Hi,
There is no way to restart a failed backup that I know of, although some
work has been done recently to remember which files that have been
written to tape for a backup that did not complete. Given this is your
first backup I would recommend starting again.
You can set the period after which a job times out, and I seem to
remember the same setting can also disable that. It's one of the config
items but I can't recall the name now, sorry. You can also set an alert
email to be sent to you (look for 'bsmtp' in the docs) when bareos wants
you to do things like this. Finally, I find it useful to also set the
option to cancel new scheduled jobs that are already running, so I don't
get multiple backups for the same thing waiting in the queue.
An LTO-9 is capable of very fast transfer speeds, so I would also
suggest you investigate whether your drive is actually performing as
well as it can. For example, you definitely need to set the tape block
size to the right value (I don't know what it would be for a -9) and you
should very likely enable write spooling (transfer to a temporary local
drive then from there to tape) unless your network infrastructure is
very fast indeed. To check, a non-trivial backup (say of 60GB) should
achieve an absolute minimum transfer speed of 120MBytes/second as
reported in the Bareos logs. This is faster than a saturated 10Gbps
network. The reason I suggest spooling is that if an LTO drive is forced
to run slower than it's "good" speed, it will very significantly reduce
throughput even when the delay for spooling is taken into account.
I would encourage you to try to split the dataset into smaller parts
even if the split is somewhat artificial, as "stuff happens" and a
backup that takes that long is never going to be nice.
Hope this helps,
Ruth
On 18/03/2024 19:22, Jascha Schubert wrote:
Hello,
i tried to make my first backup with bareos. I have a single LTO-9
drive without loader.
I have a quite large set of files and a full backup takes several
days. So after 5 days of backup the first tape was full and bareos
required a new tape. But I was not watching and s after another 5 days
the job failed with the message:
bareos-sd JobId 23: Fatal error: Max time exceeded waiting to mount
Storage Device "tapedrive-0" (/dev/nst0) for Job
rack-job.2024-02-21_10.08.58_15
I have now two questions:
1. Can I somehow continue the job, so that I don't have to start over?
2. Can I set the waiting time to infinite, so that to job does not get
aborted, when I take to long to change the tape?
Thank You
Jascha
--
You received this message because you are subscribed to the Google
Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/2b168c8b-ee4f-4214-8407-3b335b34df75n%40googlegroups.com
<https://groups.google.com/d/msgid/bareos-users/2b168c8b-ee4f-4214-8407-3b335b34df75n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Tel: 01223 414180
Blog:http://www.ivimey.org/blog
LinkedIn:http://uk.linkedin.com/in/ruthivimeycook/
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/5b92d234-eb89-41f7-9671-fcbc7dd6064a%40ivimey.org.
