Ludwig -
Before running the 2nd backup, check the volume state and see if it is marked
as 'expired'. If not, then with your configuration the 2nd backup should fail
and report that the volume is full.
The retention time of the volume is set when the volume is created, so if you
changed the
Norbert -
The simplest way to access the logs for the Consolidate job is to simply click
on the JobID in the web UI.
--
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
Am Donnerstag, 15. Februar 2018 11:54:51 UTC+1 schrieb Ludwig BaLu:
> Hi bareos community,
>
> I think, I have got problems to understand the right way for doing my
> backup.
>
> Following scenario should be covered:
> short:
> 1 month of fullbackup, the rest should be backup up incremental.
Hi bareos community,
I think, I have got problems to understand the right way for doing my
backup.
Following scenario should be covered:
short:
1 month of fullbackup, the rest should be backup up incremental. After
this month, the previous fullbackup should be overwritten with the next
full
Knoax -
You should not ever have to issue a delete command, for a job or for a volume.
Prune and recycle the volumes. Set the retention time to control when the jobs
are discarded.
Using a delete command on a job or volume does not honor the configured
retention, so you risk discarding
Am Donnerstag, 15. Februar 2018 12:39:27 UTC+1 schrieb Dan:
> Ludwig -
>
> Before running the 2nd backup, check the volume state and see if it is marked
> as 'expired'. If not, then with your configuration the 2nd backup should
> fail and report that the volume is full.
>
> The retention time
On Friday, January 6, 2017 at 7:06:07 AM UTC-5, Daniel Wedewardt wrote:
> Hello Community,
>
> I just stumbled upon a dmesg error and wonder if the bareos-sd 120sek.
> timeout could have caused the "Medium Error". Is this really a broken tape?
>
> [ 5284.492090] INFO: task bareos-sd:18178
Greetings
I have a large amount of data to backup. Approximately 12TB. Much of it is
static, however, it does change daily.
Reading about Bareos and the various options, I am unclear on the best strategy
to backup this much data with a view to eventually having to restore it. Would
Always
--
Sean Hurley
Systems Administrator
Canadian Longitudinal Study on Aging (CLSA)
Étude longitudinale canadienne sur le vieillissement (ÉLCV)
Mobile/Text: 289-700-1606
Email: shur...@mcmaster.ca
McMaster University
McMaster Innovation Park
175 Longwood Rd. S. Suite 309A
Hamilton, ON L8P 0A1
--
Norbert -
You should try to post your replies on this site so others can easily follow
the thread.
The log entries show 'less incrementals than required to consolidate without
full, not consolidating'. That would indicate that either the 'Always
Incremental Job Retention' or 'Always
On 08.02.2018 at 19:08 wrote 'Nobody is Perfekt' via bareos-users:
> Hello World !
>
> my problem under bconsole and only with job name with blanks within...
>
> Test1
> *configure add job name=xx-fd client=xx-fd jobdefs=DefaultJob
> fileset=Windows All Drives
> # Missing value for directive
Screenshot ..
Le mercredi 14 février 2018 10:12:47 UTC+1, Norbert Deleutre a écrit :
> Hello all,
>
>
>
> I configure a consolidate Job after 7 incremental.
>
> the consolidate job run,
> but he produce 0B (see screenshot)
>
> I don't know what is wrong .
> Could you please help me
You may consider to use
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AlwaysIncrementalBackupScheme
instead.
Delete the only full backup before a new full backup is done is kind of
dangerous.
On 15.02.2018 at 13:51 wrote 'Ludwig BaLu' via bareos-users:
> Am Donnerstag, 15.
On 15.02.2018 at 15:50 wrote Sean H:
> Greetings
>
> I have a large amount of data to backup. Approximately 12TB. Much of it is
> static, however, it does change daily.
>
> Reading about Bareos and the various options, I am unclear on the best
> strategy to backup this much data with a view
Am Donnerstag, 15. Februar 2018 11:54:51 UTC+1 schrieb Ludwig BaLu:
> Hi bareos community,
>
> I think, I have got problems to understand the right way for doing my
> backup.
>
> Following scenario should be covered:
> short:
> 1 month of fullbackup, the rest should be backup up incremental.
Thank you!
El 13/02/18 a las 05:34, Jörg Steffens escribió:
On 12.02.2018 at 23:34 wrote desarro...@opcode.cl:
Hi, Thanks for reply. "Yes" means "yes to all" or specifically to one
alternative?
yes, you have to specify it as clear password that automatically is
transfered as a md5 text over
On 14.02.2018 at 22:38 wrote Dakota Pilot:
> On Monday, February 5, 2018 at 8:54:46 AM UTC-5, Daniel wrote:
>> Hi,
>>
>> I saw the error several time on my system, too. I use Ubuntu Server 16.04
>> and bareos 17.2.4. But the restore seems to be completed, no files are
>> missing. So I think it
According to your configuration, the job will consolidate only if there are at
least 9 incremental backups and at least 2 of them are more than 7 days old.
If you have just started with this client, the initial incremental backup is
actually a full and is treated as such. So in that case
Hello world, I installed bareos-dir on Centos server and a Windows client a
couple weeks ago. All was working fine until yesterday because the windows
client not respond to director, I restarted the fd service and the conection
was restablished but today I have the same problem and I restarted
On Thursday, February 15, 2018 at 12:14:41 PM UTC-5, Jörg Steffens wrote:
> On 14.02.2018 at 22:38 wrote Dakota Pilot:
> > On Monday, February 5, 2018 at 8:54:46 AM UTC-5, Daniel wrote:
> >> Hi,
> >>
> >> I saw the error several time on my system, too. I use Ubuntu Server 16.04
> >> and bareos
20 matches
Mail list logo
