Re: [BackupPC-users] Problem trying to restore to remote host

as able to do a tar restore of the same folders, it just won't restore to the other host. The user's computer no longer exists, so I can't restore it back to that computer. Thanks, Steve > On Wednesday, September 19, 2018, Steve Palm <mailto:n9...@n9yty.com>> wrote

[BackupPC-users] Problem trying to restore to remote host

Can anyone help me determine what the problem is here? Trying to restore from a backup onto a different host. The original backup was for computer 'dickk' and trying to restore it to 'xserve1': I inserted blank lines for readability, but everything looks OK except for the Trimming /dickk from

Re: [BackupPC-users] BackupPC 4.2.0 released

good point. > > How about I add a configuration setting that has three values - completely > off, admin only, or any user? The default setting could be admin only. > > However, if it's turned off, any admin could change that setting back to > admin only. > > Craig &g

Re: [BackupPC-users] BackupPC 4.2.0 released

On Apr 16, 2018, at 7:47 AM, Ghislain Adnet wrote: > Le 15/04/2018 à 01:10, Craig Barratt via BackupPC-users a écrit : >> BackupPC 4.2.0 has >> been released on Github. >> The changes since4.1.5 >>

Re: [BackupPC-users] offsite server

On Apr 10, 2018, at 2:02 PM, Johan Ehnberg wrote: > Yes, this is quite feasible and straightforward to set up as long as you have > control over the selection of filesystem. > > Using a Copy-on-Write filesystem with snapshots allows you to very > efficiently replicate backups from the main ser

Re: [BackupPC-users] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.2.0]

May 7, 2017, at 3:17 AM, Craig Barratt <mailto:cbarr...@users.sourceforge.net>> wrote: > > Steve, > > Most likely it's a problem with ssh (perhaps it's prompting for a password) > or the client shell is producing output before rsync is run. > > Craig

[BackupPC-users] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.2.0]

Any clue what this is saying? This is the rsync child about to exec /usr/local/bin/rsync_bpc rsync_bpc: connection unexpectedly closed (0 bytes received so far) [Receiver] Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp,

[BackupPC-users] Help to understand some XFerLOG messages

Since converting to BackupPC 4, one file server seems to have gone into a continual loop of backing up over and over and over... continuously. And this server takes a long time to backup, so essentially it is always running a backup on this host. In trying to narrow it down, I looked at XFerLO

Re: [BackupPC-users] rsync: –protect-args on Mac OS X ?

to be more efficient on transfers. Installed that in /usr/local/bin/rsync and modified the xfer jobs of those machines to use that path instead. Now I can use the --protect-args (-s) parameter. Steve > On Apr 23, 2017, at 10:06 AM, Steve Palm wrote: > > Hi, > > Under v3 I

[BackupPC-users] rsync: –protect-args on Mac OS X ?

Hi, Under v3 I didn't have any problems with shares that had spaces in the names. However, I see that after all was converted to v4 rsync was using a –protect-args parameter. However, rsync on Mac OS X does not support that parameter, so how to restore the ability to get paths with spaces in

Re: [BackupPC-users] Cannot create /var/run/BackupPC ??

ceforge.net>> wrote: > > Steve, > > In 4.1.1 I added this directive to the systemd backuppc.service file: > > RuntimeDirectory=BackupPC > > which creates the /var/run/BackupPC directory just before it starts BackupPC. > > Craig > > On Wed, Apr 12, 2017

Re: [BackupPC-users] Cannot create /var/run/BackupPC ??

Looked at the code, ${RunDir} is the location, and its s a directory not a file. Not sure why it couldn't be created, but I did so manually, changed ownership to backuppc and it works. Still don't know why it went wrong... Steve > On Apr 12, 2017, at 2:35 PM, Steve Palm wrot

[BackupPC-users] Cannot create /var/run/BackupPC ??

Hello, I had a hard server crash, seems a RAM module went bad. After diagnosing and getting it back up and running, BackupPC will no longer start. I simply get: systemd[1]: Starting SYSV: Starts and stops the BackupPC server... runuser[6605]: pam_unix(runuser:session): session opened for user ba

Re: [BackupPC-users] rsync_bpc benign status 24

t;Backup aborted by user signal", which is likely why > it exited with a fatal error. Did you cancel or abort the backup? > > It would be helpful to see more of the log file, specifically all of the last > hundred or so lines (just email straight to me is fine). > > C

[BackupPC-users] rsync_bpc benign status 24

This could potentially be an issue... Backing up a server, I get: rsync warning: some files vanished before they could be transferred (code 24) at main.c(1543) [generator=3.0.9.5] rsync_bpc exited with benign status 24 (6144) Got fatal error during xfer (rsync_bpc exited with benign status 24 (6

Re: [BackupPC-users] BackupPC v4 -- pool backups easier?

On Mar 23, 2017, at 11:22 AM, Craig Barratt wrote: > Yes, that's one of the major advantages of 4.x - the pool is now much easier > to copy or backup. HUGE HURRAH! :) > In 4.1.0 there is a new utility BackupPC_migrateV3toV4 that you can > optionally use to bulk upgrade old 3.x backups to v

[BackupPC-users] BackupPC v4 -- pool backups easier?

Hi, Simple question, I hope, but seeing the substantial differences "under the hood" on how BackupPC is handling things, no more hard links in particular, will this make it easier to backup the pool to other systems or tape? It seemed to me that one of the sticking points has always been the h

Re: [BackupPC-users] No files dumped?

very thankful for the upgrade, and now that I think I have a handle on how to reconfigure the hosts it will be interesting to see how performance has improved. Thanks, Steve > On Mar 23, 2017, at 8:45 AM, Steve Palm wrote: > > I'm seeing this on all the hosts so far, the firs

[BackupPC-users] No files dumped?

I'm seeing this on all the hosts so far, the first batch have all been Linux servers using an rsync backup method over ssh... My understanding of what the logs are telling me is that the connection closed. Maybe never really opened. I do see that my original ssh command configuration was lost d

Re: [BackupPC-users] BackupPC 4.0.0 released

look from GitHub. > On Mar 22, 2017, at 4:43 PM, Steve Palm wrote: > > Okay, I installed from Github to take advantage of recent fixes, and the > upgrade worked fine. The web interface came up straight away, no problems. > > If these problems are BECAUSE I used the GitHub

Re: [BackupPC-users] BackupPC 4.0.0 released

Okay, I installed from Github to take advantage of recent fixes, and the upgrade worked fine. The web interface came up straight away, no problems. If these problems are BECAUSE I used the GitHub version, please advise and I will back it out or wait for resolution. Actually, I did install the r

Re: [BackupPC-users] BackupPC 4.0.0 released

s, the error is confusing > since "version" is such a generic name. > > You can use CPAN (or your linux installer if that's what you normally use) to > install it: > > sudo cpan > install version > > Craig > > On Wed, Mar 22, 2017 at 7:40 AM, Stev

Re: [BackupPC-users] BackupPC 4.0.0 released

Sorry, I sent this to the developer list, should probably have gone to the users list... :( On Mar 4, 2017, at 1:12 PM, Craig Barratt mailto:cbarr...@users.sourceforge.net>> wrote: > I'm happy to announce that BackupPC 4.0.0 has been released on Github >