On 2020-05-22 16:49, backu...@kosowsky.org wrote:
Michael Stowe wrote at about 22:18:50 + on Friday, May 22, 2020:
> On 2020-05-22 11:42, backu...@kosowsky.org wrote:
> > 1. Sockets are restored as regular files not special files -->
BUG?
>
> Why would one back up a socket?
I am
On 2020-05-22 16:52, backu...@kosowsky.org wrote:
Michael Stowe wrote at about 23:46:54 + on Friday, May 22, 2020:
> On 2020-05-22 16:19, backu...@kosowsky.org wrote:
> > Michael Stowe wrote at about 22:24:13 + on Friday, May 22,
2020:
> > > On 2020-05-22 09:15,
Michael Stowe wrote at about 23:46:54 + on Friday, May 22, 2020:
> On 2020-05-22 16:19, backu...@kosowsky.org wrote:
> > Michael Stowe wrote at about 22:24:13 + on Friday, May 22, 2020:
> > > On 2020-05-22 09:15, backu...@kosowsky.org wrote:
> > > What it does is omit directories
Michael Stowe wrote at about 22:18:50 + on Friday, May 22, 2020:
> On 2020-05-22 11:42, backu...@kosowsky.org wrote:
> > 1. Sockets are restored as regular files not special files --> BUG?
>
> Why would one back up a socket?
I am testing the fidelity of the backup/restore cycle..
>
> If
On 2020-05-22 16:19, backu...@kosowsky.org wrote:
Michael Stowe wrote at about 22:24:13 + on Friday, May 22, 2020:
> On 2020-05-22 09:15, backu...@kosowsky.org wrote:
> What it does is omit directories from the modification times that it
> sets. In other words, you're telling it not to
"" wrote at about 14:42:10 -0400 on Friday, May 22, 2020:
> Craig,
> Using rsync (rather than tar) to restore, I think I confirmed several
> bugs with the handling of sockets and SELinux attributes
>
> Hopefully, I have provided enough info to debug...
>
> In summary:
> 0. All my ACLs
Michael Stowe wrote at about 22:24:13 + on Friday, May 22, 2020:
> On 2020-05-22 09:15, backu...@kosowsky.org wrote:
> > If I add '--omit-dir-times' to $Conf{RsyncArgsExtra}, then the backups
> > set all the directory dates to the beginning of the Epoch.
> >
> > For example
> >
On 2020-05-22 09:15, backu...@kosowsky.org wrote:
If I add '--omit-dir-times' to $Conf{RsyncArgsExtra}, then the backups
set all the directory dates to the beginning of the Epoch.
For example
drwxr-xr-x 3 backuppc www-data 1024 Dec 31 1969 pc/
(note this is 1/1/70 00:00:00 GMT)
This is
On 2020-05-22 11:42, backu...@kosowsky.org wrote:
1. Sockets are restored as regular files not special files --> BUG?
Why would one back up a socket?
If you really think this is sensible, you should be able to accomplish
it with "--devices --specials" as part of your rsync command lines.
Craig,
Using rsync (rather than tar) to restore, I think I confirmed several
bugs with the handling of sockets and SELinux attributes
Hopefully, I have provided enough info to debug...
In summary:
0. All my ACLs are dumped & restored properly (with rsync) --> GOOD
1. Sockets are restored as
>>> I am currently running BackupPC version 4.3.2 on Ubuntu 18.04.4 LTS .
>>> Everything seems to be working perfectly, except this pesky "2020-05-22
>>> 10:02:30 scgi : BackupPC_Admin_SCGI: can't load perl SCGI module - install
>>> via CPAN; exiting in 60 seconds" error
Mike,
The only
Or better yet, use CentOS 7 and that packaging. I can’t get to that RPM link at
this moment. I’m sure someone else has that link available quickly.
Thanks,
Greg Harris
> On May 22, 2020, at 12:33 PM, Doug Lytle wrote:
>
>
>>
BackupPC is installed on an Ubuntu 18.04.4 system..
>
>
If I add '--omit-dir-times' to $Conf{RsyncArgsExtra}, then the backups
set all the directory dates to the beginning of the Epoch.
For example
drwxr-xr-x 3 backuppc www-data 1024 Dec 31 1969 pc/
(note this is 1/1/70 00:00:00 GMT)
This is inconsistent with normal rsync wich just uses
>>> BackupPC is installed on an Ubuntu 18.04.4 system..
You won't want to be using BackupPC from Ubuntu 18.04's PPA, it's only version
3.3.1. BackupPC is currently at 4.3.2
My suggestion would be to install it from tarball. I've found the below
instructions
Thanks for the hint!
BackupPC is installed on an Ubuntu 18.04.4 system...
I am trying to get this machine to backup up our Debian 10 file server, since
our cloud backup service doesn't support Debian but does support Ubuntu.
I haven't used Perl in 20 years, and the last five years been working
On 5/21/20 7:54 PM, Michael Walker - Rotech Motor Ltd. wrote:
I cannot find any details on how to do this... cpanm is installed and
seems to be working.. but WHAT must I ask it to get, precisely??
Mike,
What Linux Distro are you running BackupPC on? I'm running mine on
Debian 10 (Buster)
Jeff,
The tar XferMethod doesn't capture acls and xattrs during backup.
Direct Restore in the CGI interface uses the XferMethod setting.
Craig
On Thu, May 21, 2020 at 10:05 PM wrote:
> I also assume that tar doesn't capture ACLs and XATTRs for backup
> either then
>
> What transfer mechanism
17 matches
Mail list logo
