2016-01-12 19:04 GMT+01:00 Stephen :
> rsync warning: some files vanished before they could be transferred (code 24)
> at main.c(1542) [generator=3.0.9.3]
> rsync_bpc exited with benign status 24 (6144)
> ^
Mine is the same. But this backup will be pla
On Tue, 12 Jan 2016, Gandalf Corvotempesta wrote:
> Would be possible to instruct BPC to ignore "file has vanished" errors
> (error code 24) ?
> I'm backingup many clients that has tons of volatile file: php
> sessions, maildirs used by imap, where each file is renamed according
> to imap flags or
2016-01-12 16:36 GMT+01:00 Les Mikesell :
> Changed/removed files are not supposed to be fatal
Probably yes, but having all hosts with items in "failed backups" is not good.
Having too many false positive/false alarms like this will cause loss
of visibility on real issue.
Like the fable "The Boy
On Tue, Jan 12, 2016 at 5:33 AM, Gandalf Corvotempesta
wrote:
> 2016-01-12 12:05 GMT+01:00 Andreas Piening :
>> - You can exclude the directories with the often altered PHP files. For me
>> this sounds like a machine of a WEB developer constantly editing PHP files.
>> In this case the source is pr
On 12/01/2016 21:48, Gandalf Corvotempesta wrote:
> Would be possible to instruct BPC to ignore "file has vanished" errors
> (error code 24) ?
> I'm backingup many clients that has tons of volatile file: php
> sessions, maildirs used by imap, where each file is renamed according
> to imap flags o
2016-01-12 12:05 GMT+01:00 Andreas Piening :
> - You can exclude the directories with the often altered PHP files. For me
> this sounds like a machine of a WEB developer constantly editing PHP files.
> In this case the source is probably already „backed up“ by a versioning
> control system (git, me
Not a real answer to your question on instructing BPC to ignore „file has
vanished errors“ but I have two suggestions on avoiding this error:
- You can exclude the directories with the often altered PHP files. For me this
sounds like a machine of a WEB developer constantly editing PHP files. In
Would be possible to instruct BPC to ignore "file has vanished" errors
(error code 24) ?
I'm backingup many clients that has tons of volatile file: php
sessions, maildirs used by imap, where each file is renamed according
to imap flags or moved in imap folders and so on.
Every time i make a backup
On 12/01/2016 19:00, Gandalf Corvotempesta wrote:
> 2016-01-12 8:29 GMT+01:00 Patrick Begou :
>> I'm using BackupPC 3.3.1 for a while now and backing up a partition of more
>> than
>> 100GB (from a macbook client) was requiering more than 24 hours on a
>> backupPC
>> server with only 2GB of RA
On 12/01/2016 19:50, Patrick Begou wrote:
> I have'nt removed anything after upgrading the RAM.
> My BackupPC is a virtual host under proxmox, I've just increased the RAM
> allowed
> from 2GB to 6GB without restarting anything.
This screams problem alert right here, you are sharing the backuppc
I have'nt removed anything after upgrading the RAM.
My BackupPC is a virtual host under proxmox, I've just increased the RAM
allowed
from 2GB to 6GB without restarting anything.
Patrick
Gandalf Corvotempesta wrote:
> 2016-01-12 8:29 GMT+01:00 Patrick Begou :
>> I'm using BackupPC 3.3.1 for a wh
2016-01-12 8:29 GMT+01:00 Patrick Begou :
> I'm using BackupPC 3.3.1 for a while now and backing up a partition of more
> than
> 100GB (from a macbook client) was requiering more than 24 hours on a backupPC
> server with only 2GB of RAM. Increasing the RAM to 6GB has totally solved the
> problem.
12 matches
Mail list logo
