Hi everybody!
Is it possible to set client start time somewhere other than Schedule
configuration?
So we can use the same schedule, but in different time start.
I didn't found anything like this in doc :(
Ex:
Schedule {
Name = FSS
Run = Level=Full sun
}
JobDefs {
Name = client001.jd
Bob Hetzel schrieb:
Greetings,
I've been seeing an issue whereby a volume gets marked in error
periodically. The last items logged about that volume are typically like
this:
02-Jun 11:53 gyrus-sd JobId 83311: Volume LTO224L2 previously written,
moving to end of data.
02-Jun 11:53
Silver Salonen schrieb:
Hi.
I'm trying to run incremental job of a restored fileset (having
mtimeonly=yes). When I check its estimate, it shows correctly only new files
that have been created/modified since restoration. But when I run the actual
job, all the files are included in backup.
On Thursday 04 June 2009 10:34:36 Christian Gaul wrote:
Silver Salonen schrieb:
Hi.
I'm trying to run incremental job of a restored fileset (having
mtimeonly=yes). When I check its estimate, it shows correctly only new
files
that have been created/modified since restoration. But when
Silver Salonen schrieb:
On Thursday 04 June 2009 10:34:36 Christian Gaul wrote:
Silver Salonen schrieb:
Hi.
I'm trying to run incremental job of a restored fileset (having
mtimeonly=yes). When I check its estimate, it shows correctly only new
files
that have been
On Thu, Jun 04, 2009 at 09:20:34AM +0200, Christian Gaul wrote:
Bob Hetzel schrieb:
Greetings,
I've been seeing an issue whereby a volume gets marked in error
periodically. The last items logged about that volume are typically like
this:
02-Jun 11:53 gyrus-sd JobId 83311: Volume
Hi,
is it possible to configure a backup job to _not_ store information
about the backed up files/paths etc in the database?
I recently tried to backup my BackupPC pool with bacula. BackupPC
makes excessive use of hardlinks, I ended up with 50 GB of data in my
postgres database only for this
hi guys, bacula kicks arse lol
how may I know how long its been since the clients where backed up from bcosole
of whatever? I jsut want to find out quickly which ones have the longest time
to see whats going on with them
btw, every once in a while employees lave the company and new ones come
Greetings
I'm wonding if anyone may have any ideas of how to prevent this error.
I've been using bacula for a few years in one location and would get an
error like below approximately once every three weeks. It has not been
too big a problem and I am able to just umount mount umount mount and
