Each rsync backup has two processes on the backup server, but only one will
be doing compression. So, yes, compression for a single backup is
single-threaded (as rsync is).
However, the backup server usually runs multiple backups (configurable),
and, in the steady state, the amount of compression
Hey guys,
Is there such a setting or is backuppc genuinely single threaded when it
comes to compression? I ask because seems a little silly these days when
pretty much all CPUs are multicore and all server are multicore and multcpu?
So is there a setting I am missing? I scanned the documentatio
Yeah, this is indeed still a problem for me. My DumpPreUserCmd needs to
preserve the logs. The problem is that if/when that cmd fails, the exit
status is checked and it registers a failure. Thus, the main backup is
aborted. With no main backup to process, there is no xfer log file
saved and the out
Thank you Mr. Hughes for a more complete explanation.
Not sure which change is considered the better option.
One of my BackupPC machines I have added the /home under the "/" in
RsyncShareName.
On the second one I have removed the "default flag --one-file-system".
At this moment there is a ba
This behavior has not changed over the years. You've found that the
/home folder exists on a separate partition than /. What is the value
of RsyncShareName? If it's just the default of "/", then that's the
only partition which will be examined by rsync and no other partitions
will be considered. Th
Sorry I was grumpy this morning. Had a rough weekend. Appreciate your
thoughtful input.
On Mon, 2019-09-30 at 12:35 +0100, Jamie Burchell wrote:
> Since Bob hadn’t come back to confirm whether or not your answer
> worked for him, I was simply suggesting what is working for me in
> case it helps.
>
I have been using BackupPC since early v3.0 days. Switched to v4 a few
years ago.
I have always "exclude" directories to NOT backup. It has been my
understanding that BackupPC users were to either "include" or "exclude"
NOT both?
The "/" is on /dev/md1 and "/home" is on /dev/md2. Both on Lin
Since Bob hadn’t come back to confirm whether or not your answer worked for
him, I was simply suggesting what is working for me in case it helps.
Kind regards,
*Jamie*
--
*From:* Mike Hughes [mailto:m...@visionary.com]
*Sent:* 30 September 2019 11:54
*To:* General list for user discussion, ques
The answer has already been provided. If you're still unclear maybe try
googling 'rsync one-file-system' or running lsblk on an affected system.
On Sep 30, 2019 03:51, Jamie Burchell wrote:
I too am using CentOS 7 and that repo. The only thing I can think is that
defaults on CentOS 7 at least
I too am using CentOS 7 and that repo. The only thing I can think is that
defaults on CentOS 7 at least are that home directories are owned by their
respective user and nobody else can access them. BackupPC would need to run
as a privileged user for it to be able to access those directories. I’d
ex
10 matches
Mail list logo
