On 2020-03-09 02:11, George Campbell wrote:
Hello, I am new to this list, so please let me know if there is anything missing from my question...
I have setup backuppc as a docker (version 4.3.2) on an Ubuntu server. My client is a Windows 10 running RPC.
A full backup runs and I can see lots of files on the server. But, the backup never seems to finish and gets stuck. I can't see that the backup in incomplete, though I have not tried to test it.
A few observations:
- on the client I can see the RPC processing running, but it does not seem to do anything withe with the disk or network
- the docker is setup to use 8 threads, but only ever uses one. I have changed the MaxBackupPCNightlyJobs to 8.
- The server and client are both massive with 64/16gb of memory and 12/4 cores respectively. Both, and the network, seem untaxed.
- I can open a file and restore back to the client, so the config seems to all be working.
Can someone please suggest what could be wrong, or where I should look next?
Thanks, George
There's a lot to unpack here, so please bear with me a bit:
First, I don't know what you mean by RPC -- windows has an RPC service,
but I'm not sure how that relates to one of the BackupPC transports
(e.g., smb, rsync, ftp) and to make use of the RPC service, you'd need
to do some custom work or scripting. (If this is the case, you may want
to elaborate.)
Second, ignoring the above and assuming you're using smb or rsync,
you'll need a strategy to deal with windows filesystem semantics and
features. It's pretty easy to hang either transport by trying to back
up an open file or junction. Tried and true strategies involve shadow
volumes or ... not doing that.
MaxBackupPCNightlyJobs will run backup jobs in parallel, but it won't
automatically split your job for you.
While 16G of memory and 4 cores isn't terrible, it's worth noting that
IO speed is a significant factor, so unless that's enough RAM to cache
your entire backup (or filesystem) then expect to run into IO
constraints -- and note that the time for an individual backup job is
usually proportional to the size of the data.
And finally, note that there have been various bugs in transports, so
it's probably not a bad idea to be specific about the version in the
case that somebody recognizes it as being problematic in some way.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
