Yes, thank you that was it.
Now getting a 403 on the UI
Thanks, Rick
On 23-03-2017 11:58, Craig Barratt wrote:
> Rick,
>
> There are potential pitfalls upgrading using the native release tar.gz from
> an existing package manager installation - the package installer might make
> choices or
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
Steve,
Yes, that's one of the major advantages of 4.x - the pool is now much
easier to copy or backup.
If you upgrade an existing 3.x installation then the hardlinks will still
persist for the old backups (4.x is backward compatible - it knows how to
view/restore 3.x backups). The 3.x backups wi
Steve,
I agree this is a problem area for upgrading to 4.0 and it's the one place
where some manual checking or updates may be necessary.
Unfortunately it's hard to automatically split up $Conf{RsyncClientCmd}
into $Conf{RsyncSshArgs} and $Conf{RsyncClientPath}.
Also, $Conf{RsyncClientPath} is n
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
Rick,
There are potential pitfalls upgrading using the native release tar.gz from
an existing package manager installation - the package installer might make
choices or enforce policies that configure.pl isn't aware of.
That's the rsync_bpc version check. $Conf{RsyncBackupPCPath} is set to
"/usr
Well, I have one host backing up, finally But I have to revisit the
settings and see how to propagate them to the others in the right way.
The essence, though, per my previous config, was that the RsyncSshPath was:
$sshPath -q -x -l backuppc -c arcfour
The RsyncClientPath was: nice -
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
I wanted to give a quick update on the status of BackupPC v4 for Fedora and
EPEL 6 & 7.
Currently I'm fighting a configuration problem with Apache and the C
wrapper which allows BackupPC_Admin to run as suid. I think I have a
solution but I haven't had time to test it.
Even after I get a working
Going from version 3 to 4.0 on Debian I've broken something as Backuppc
will not start.
Any attempt produces the error "BackupPC: can't run /usr/local/bin/ for
version check; (Exec of /usr/local/bin/ --version failed"
There are two bin directories alike, one "/etc/backuppc/bin" and second
"/usr
10 matches
Mail list logo
