Hi Daniel,
that's a good idea. But what about the crashed full backup and after
this a incremental? This shouldn't happen :-(
Am 26.09.2016 um 15:34 schrieb Daniel:
> Maybe this can help you.
> In my Jobs I use the following configuration:
>
> Max Full Interval = 1 Month## maximales Alter des
Hello Bruno, thanks for the answer.
The 16 TB filesystem limit exists on Centos 6. Tested it recently, if you try
to make an fs > 16 TB you get the following error:
mkfs.ext4: Size of device /dev/ too big to be expressed in 32 bits using a
blocksize of 4096.
Its the e2fsprogs I think which
Maybe this can help you.
In my Jobs I use the following configuration:
Max Full Interval = 1 Month## maximales Alter des letzten Vollbackups. Ist
keins vorhanden, wird ein neues geplant anstelle eines Inkrementellen Backups
Max Diff Interval = 1 Week ## analog
--
You received this messa
I realized that I when I ran the last test as Bareos-fd as administrator, I was
running it as a “RunAfterJob” and decided to reboot and try it as the more
appropriate “ClientRunAfterJob” and this works! One noticeable issue is that
the Bareos FD did not start up after reboot. Is there any other
Thanks for both your suggestions but to be more specific I am attempting
to run a amazon glacier sync tool from a bat file.
If i run it as a "windows scheduled task" as administrator it will run
If I run it locally as administrator it will run.
If I run it from bareos it will fail
If I run it a
Hi Bruno,
there is nothing which could return a errorlevel other then zero:
*
#!/bin/sh
#
#
# Ansible managed:
/etc/ansible/roles/sklatt.bareos_client/templates/bareos-nobackup
modified on 2016-08-09 14:43:00 by root on ansible.cac.local
#
# Bareos Script to c
Hi,
if I rerun the failed Backup, Bareos make a full backup.
P.s.: Actual beta, but I think I saw this sometimes with 15.2
Am 26.09.2016 um 10:20 schrieb Stefan Klatt:
> Hi,
>
> like you can see at the screenshot I had a failed full backup at Sunday
> morning.
> After correction I started the ba
Hi,
like you can see at the screenshot I had a failed full backup at Sunday
morning.
After correction I started the backup new and bareos only backup
incremental :-( But there is no correct full backup for this week!
Here my configuration:
Schedule {
Name = "Week_2"
run = Full Sun w02,w06,w1
Btach fiel is bad wording, script is better
Am 26.09.2016 um 00:14 schrieb Stefan Klatt:
> Hi Bruno,
>
> now I have the second bareos server which can't start my "noabckup"
> script in front of the backup:
>
> 25-Sep 04:32 galaxy-dir JobId 224: Start Backup JobId 224,
> Job=Week2_Backup_gala
