On 2018-03-13 16:33, Holger Parplies wrote:
My first thought is to avoid the issue altogether by using a file
system
that doesn't statically allocate inodes (e.g. XFS or reiserfs, the
latter
I wouldn't recommend for other reasons, though; I don't know about
ext4,
btrfs and ZFS, but my guess wou
Hi,
f...@igh.de wrote on 2018-03-08 16:59:37 +0100 [Re: [BackupPC-users] Serious
error: last backup ... directory doesn't exist!!! - reason found]:
> [...]
> Meanwhile I found the reason: the partition ran out of inodes. As you
> wrote under "How much disk space do I need?" one has to have "plent
That's actually a slightly different error (io.c(1556) instead of
io.c(629)). It's possible that browsing the source code of io.c would offer
a clue, but it's a pretty generic error, so it's probably time to enable
verbose logging on both ends and do some proper debugging. I'd do that by
running rs
---
André Tapxure Gabriel
[ http://www.solucoesideais.com.br/ | http://www.solucoesideais.com.br ]
[ https://www.facebook.com/solucoesideaistecnologia |
http://www.facebook.com/solucoesideaistecnologia ]
Fone: (62) 3988-
Cel: (62)98208-4227
E-mail: [ mailto:an...@solucoesideai
I've set the timeout on my backuppc server to 604800 which is one week. One of
my clients has just completed its first full backup. However, my other clients
are still receiving the same rysnc error as before...
2018-03-13 15:11:29 Got fatal error during xfer (rsync error: error in rsync
proto
I'd say its worth a try.
Robert Trevellyan
On Tue, Mar 13, 2018 at 10:30 AM, Marc Gilliatt
wrote:
> So I should set my ConnectTimeout on my backuppc server then?
> --
> *From:* Robert Trevellyan
> *Sent:* 13 March 2018 14:25:30
>
> *To:* General list for user discus
So I should set my ConnectTimeout on my backuppc server then?
From: Robert Trevellyan
Sent: 13 March 2018 14:25:30
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Can't switch users to BackupPC in terminal?
According to t
According to the man pages, the ConnectTimeout and ServerAlive settings
only apply to ssh_config, i.e. the BPC end, whereas the other settings only
apply to sshd_config, i.e. the host you are trying to backup.
Robert Trevellyan
On Tue, Mar 13, 2018 at 10:12 AM, Marc Gilliatt
wrote:
> Thank you
Thank you for the quick response.
Do I have to increase the SSH timeout on my backuppc server or my client or
both?
I've checked the SSH timeout on my backuppc server, its commented out, should I
uncomment it and set it?
From: Robert Trevellyan
Sent: 13 Ma
Maybe the client has its own firewall?
The BPC timeout setting is ClientTimeout on the Backup Settings page. For
SSH you would have to delve into /etc/ssh_config and /etc/sshd_config. Look
for ConnectionTimeout, ClientAliveInterval, ClientAliveCountMax and
ServerAliveInterval. More details via man
All,
BackupPC recently is not keeping partial backups when the network gets
disconnected, etc. I am seeing this in the log files.
2018-03-12 06:26:44 full backup started for directory c-drive
2018-03-12 09:14:05 full backup 0 complete, 32549 files, 68399765172 bytes,
39 xferErrs (0 bad fil
Our servers our on our internal LAN, so I don't think it's our firewall. I used
BackupPC v3 in the past, and I upgraded to BackupPC v4. I had issues with the
upgrade and I had to completely build my backuppc server again. However, I had
no issue with BackupPC v3, I never received that rsync erro
12 matches
Mail list logo
