Hi Craig,
On Tue, Oct 13, 2020 at 07:52:48PM -0700, BackupPC Users wrote:
> The BackupPC 3.x store has large numbers of hardlinks. What commands are you
> using to migrate the data?
rsync -a
> You need to copy the file system in a manner that is aware of, and
> reconstructs, the hardlinks (eg
Craig Barratt via BackupPC-users wrote at about 19:52:48 -0700 on Tuesday,
October 13, 2020:
> The BackupPC 3.x store has large numbers of hardlinks. What commands are
> you using to migrate the data?
>
> You need to copy the file system in a manner that is aware of, and
> reconstructs, the
The BackupPC 3.x store has large numbers of hardlinks. What commands are
you using to migrate the data?
You need to copy the file system in a manner that is aware of, and
reconstructs, the hardlinks (eg, rsync -aH, or a raw file system copy
provided they are compatible). Copying all the hardlink
I'm migrating my file server from CentOS 6 to CentOS 7. Besides being
our file server, it also does DHCP, caching DNS, and BackupPC. I'm having a
problem migrating the backups to the new disk, namely running out of
space. Both systems are running BackupPC-3.3.1-5.el[67].x86_64, but
backuppc is t
That did the trick. Craig Barratt for President!!!
Thanks
Akibu
From: Craig Barratt via BackupPC-users
Sent: Tuesday, October 13, 2020 5:16 PM
To: General list for user discussion, questions and support
Cc: Craig Barratt
Subject: Re: [BackupPC-users] Excludes
Try removing the leading "/" from each of the exclude paths. Also, you
should just exclude, eg, "OneDrive", not "OneDrive/*", and same for AppData.
Craig
On Tue, Oct 13, 2020 at 5:09 PM Akibu Flash wrote:
> All,
>
> I have an arch linux server backing up two Windows 10 clients via rsync.
> In
All,
I have an arch linux server backing up two Windows 10 clients via rsync. In
the main config.pl file, I have excluded via $Conf{BackupFilesExclude} several
subdirectories and files (listed below). However, they don't seem to be being
excluded by backuppc. I don't have any per-pc excludes
I just tried the following:
git clone https://github.com/adferrand/docker-backuppc.git
cd docker-backuppc
sudo docker build -t backuppc-hc1 .
sudo docker run \
--name backuppc-test \
--dns 192.168.0.1 \
--publish 8444:8080 \
--env 'USE_SSL=true' \
--env TZ=Australia/Brisbane \
David,
Can you find or compile a perl with 64 bit IVs? You'll also need to
rebuild BackupPC::XS using that perl. That should solve the problem.
Craig
On Tue, Oct 13, 2020 at 12:50 PM David Walton wrote:
> Comparing with omv rather than the Alpine Linux in the docker container
> gives the fol
Comparing with omv rather than the Alpine Linux in the docker container
gives the following:
lsb_release -a
Distributor ID: Debian
Description:Debian GNU/Linux 9.13 (stretch)
Release:9.13
Codename: stretch
perl -V
osname=linux, osvers=3.16.0, archname=arm-linux-gnueabihf-thread-
Same here on a Banana Pi Pro running Armbian:
Distributor ID: Debian
Description:Debian GNU/Linux 9.13 (stretch)
Release:9.13
Codename: stretch
Perl5 (revision 5 version 24 subversion 1)
ivtype='long long'
ivsize=8
Regards,
Guillermo
On Tue, Oct 13, 2020 at 1:21 PM Doug Lytle
>>> Ok, so that's the issue - your version of perl on arm only uses 32 bit IVs.
>>> I'm surprised it is built that way - does anyone know if that is default
>>> for perl on arm generally?
I have a Raspberry Pi 4 running
lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Desc
Ok, so that's the issue - your version of perl on arm only uses 32 bit IVs.
I'm surprised it is built that way - does anyone know if that is default
for perl on arm generally?
That means the file size (and mtime) are limited to 2^32. Fortunately
rsync-bpc doesn't suffer from this, so your backups
Yes, blackouts are per-host. The backup on a host can happen on any server
wakeup outside its blackout window. So it's not quite one explicit time,
but captures the idea of preferred times of day with flexibility in
specific windows.
Craig
On Tue, Oct 13, 2020 at 2:49 AM Guillermo Rozas
wrote:
I am using this gussietorres/backuppc:armhf-v2019102601 docker container
from here https://hub.docker.com/r/gussietorres/backuppc/tags which I
believe is based on this container
https://hub.docker.com/r/adferrand/backuppc
This is running on omv version 4.1.36-1, kernel version 4.14.150-odroidxu4
On Mon, Oct 12, 2020, 22:29 wrote:
> Guillermo Rozas wrote at about 21:54:13 -0300 on Monday, October 12, 2020:
>
> > Isn't exactly this how blackout periods work? The only difference would
> be
> > that instead of defining the "forbidden" times, you would define the
> > "allowed" times?
> >
16 matches
Mail list logo
