2017-09-19 18:01 GMT+02:00 Gandalf Corvotempesta
:
> Removed "--inplace" from the command like and running the same backup
> right now from BPC.
> It's too early to be sure, but seems to go further. Let's see during the
> night.
Is still running. This is ok on one side, as "--inplace" may caused
On Tue, Sep 19, 2017 at 2:21 PM, Jeffrey West
wrote:
> Les,
>
> Thanks! I didn't realize you could edit the individual configs from the web
> interface.
Yes, not only that but if you have identical or near-clone systems you
can copy the setup by adding them in the web interface with the syntax
n
I’ve not seen this behavior persist—that I know of--but I’m still concerned
about the fact that it happened. Does anyone have further thoughts?
From: "Jenkins, Wade William"
Date: Tuesday, August 29, 2017 at 1:54 PM
To: "General list for user discussion, questions and support"
Cc: Craig Barra
Les,
Thanks! I didn't realize you could edit the individual configs from the web
interface. The syntax was wrong and it is working now. The following is
what works. The RsyncShareName needed [ ]
$Conf{RsyncdClientPort} = 873;
$Conf{ClientNameAlias} = 'l-jwest17b.corpnet.com';
$Conf{XferMetho
On Tue, Sep 19, 2017 at 12:24 PM, Jeffrey West
wrote:
> This is what I am seeing from the web interface.
>
> Last status is state "idle" (backup failed) as of 9/19 09:28.
> Last error is "Unknown module '/'".
> Pings to l-jwest17b.corpnet.com have succeeded 50 consecutive times.
>
> I wonder why i
This is what I am seeing from the web interface.
Last status is state "idle" (backup failed) as of 9/19 09:28.
Last error is "Unknown module '/'".
Pings to l-jwest17b.corpnet.com have succeeded 50 consecutive times.
I wonder why it would not parse the sharename correctly. I believe the
syntax is
On Tue, Sep 19, 2017 at 11:10 AM, Jeffrey West
wrote:
> I am using a pl config file just for my host which has the following in it
> now.
>
> $Conf{RsyncdClientPort} = 873;
> $Conf{ClientNameAlias} = 'l-jwest17b.corpnet.com';
> $Conf{XferMethod} = 'rsyncd';
> $conf{RsyncShareName} = 'c-drive';
> $
(please ignore this reply - I queued it up a few hours ago on a plane ride,
and it just sent now after several more useful replies to the thread)
On Tuesday, September 19, 2017, Craig Barratt <
cbarr...@users.sourceforge.net> wrote:
> Gandalf,
>
> What XferMethod are you using?
>
> Yes, it would
Gandalf,
What XferMethod are you using?
Yes, it would be interesting to see the strace output for each
BackupPC_dump process when it hangs.
Craig
On Tuesday, September 19, 2017, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:
> Still getting the same issue.
> Backup for a coupl
Yes, the latest cygwin-rsyncd-3.1.2.1 is only 64 bit.
In addition to trying deltacopy, you could try removing the --protect-args
option from $Conf{RsyncArgs}.
Craig
On Monday, September 18, 2017, Pascal Mosimann
wrote:
> Le 18. 09. 17 à 15:32, Carl Soderstrom a écrit :
> >> From: Pascal Mosima
I am using a pl config file just for my host which has the following in it
now.
$Conf{RsyncdClientPort} = 873;
$Conf{ClientNameAlias} = 'l-jwest17b.corpnet.com';
$Conf{XferMethod} = 'rsyncd';
$conf{RsyncShareName} = 'c-drive';
$Conf{FullAgeMax} = '8';
$Conf{RsyncdUserName} = 'backup';
$Conf{Rsyncd
Yes, running this right now on both: server and client.
2017-09-19 18:00 GMT+02:00 Les Mikesell :
> On Tue, Sep 19, 2017 at 10:47 AM, Gandalf Corvotempesta
> wrote:
>> 2017-09-19 17:41 GMT+02:00 Les Mikesell :
>>> If your client rsyncd is configured to write a log file you should be
>>> able to s
2017-09-19 16:51 GMT+02:00 Gandalf Corvotempesta
:
> /usr/local/bin/rsync_bpc --bpc-top-dir /var/backups/backuppc
> --bpc-host-name myhost --bpc-share-name everything --bpc-bkup-num 1
> --bpc-bkup-comp 3 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1
> --bpc-bkup-inode0 7047290 --bpc-attrib-new --bpc
On Tue, Sep 19, 2017 at 10:47 AM, Gandalf Corvotempesta
wrote:
> 2017-09-19 17:41 GMT+02:00 Les Mikesell :
>> If your client rsyncd is configured to write a log file you should be
>> able to see the invocation there. Just guessing, I'd say there is
>> probably something wrong in your excludes an
2017-09-19 17:41 GMT+02:00 Les Mikesell :
> If your client rsyncd is configured to write a log file you should be
> able to see the invocation there. Just guessing, I'd say there is
> probably something wrong in your excludes and you are wandering into
> the /sys, /proc, or /dev directories and h
On Tue, Sep 19, 2017 at 9:51 AM, Gandalf Corvotempesta
wrote:
> I can't get rsync command from the client system, as "ps aux" doesn't
> show the command invocation by the server.
If your client rsyncd is configured to write a log file you should be
able to see the invocation there. Just guessin
On 2017-09-19 05:55, Jeffrey West wrote:
Yes,
I am looking for a way that is does not connect on port 22, but
instead connects to port 873 and just uses rsync to do the transfer.
My machine has rsync running and listening on port 873
C:\Users\jeffrey.west>netstat -an | grep 873
TCP0.0.0.
Gandalf-
Hopefully, someone with more rsyncd experience can step in and help. I
haven't used the rsyncd method for 3-4 years, and don't have any current
examples to help you with.
Good luck!
--
Ray Frush
On Tue, Sep 19, 2017 at 9:32 AM, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com>
rsyncd is running on all servers, as i'm able to backup them properly
with plain rsync or rsnapshot.
Only BPC is freezing.
I don't use SSH at all, i'm directly connecting to rsyncd via rsync.
2017-09-19 17:19 GMT+02:00 Ray Frush :
> Gandalf-
>
> It looks like you're using the "rsyncd" method vs "
Gandalf-
It looks like you're using the "rsyncd" method vs "rsync" is that correct?
I don't have experience using the 'rsyncd' method, so my ability to
continue troubleshooting ends here. The main thing that jumps out at me is
to check that rsyncd is actually running on your clients, and that y
On Tue, Sep 19, 2017 at 7:59 AM, Jeffrey West
wrote:
>
> Changing the method to rsyncd made some progress. It now connects on port
> 873. I am now getting this error
>
> Last error is "Unknown module '/'".
>
> $Conf{XferMethod} = 'rsyncd';
>
> $conf{RsyncShareName} = 'C';
Something is wrong in
I can't get rsync command from the client system, as "ps aux" doesn't
show the command invocation by the server.
BackupPC is running the following:
/usr/bin/perl /usr/local/backuppc/bin/BackupPC_dump -i myhost
spawing two identical processes:
/usr/local/bin/rsync_bpc --bpc-top-dir /var/backups/b
Gandalf-
As a troubleshooting step, collect the actual running rsync commands from
the client system, and from the BackupPC server (found in the Xferlog).
Post them here to get a wider audience.
Try running an rsync manually using the same parameters, and see if it
works. My guess is not, and t
Ok, so this is expected.
Thank you.
2017-09-19 14:39 GMT+02:00 Craig Barratt via BackupPC-users
:
> If a backup fails or is aborted, BackupPC_refCntUpdate is run on the last
> two backups, independent of the $Conf{RefCntFsck} setting.
>
> Craig
>
>
> On Tuesday, September 19, 2017, Gandalf Corvote
Changing the method to rsyncd made some progress. It now connects on port
873. I am now getting this error
A command for l-jwest17b.corpnet.com is on the command queue (will run
soon).
Last status is state "idle" (backup failed) as of 9/19 08:56.
Last error is "Unknown module '/'".
Pings to
Yes,
I am looking for a way that is does not connect on port 22, but instead
connects to port 873 and just uses rsync to do the transfer. My machine
has rsync running and listening on port 873
C:\Users\jeffrey.west>netstat -an | grep 873
TCP0.0.0.0:8730.0.0.0:0
If a backup fails or is aborted, BackupPC_refCntUpdate is run on the last
two backups, independent of the $Conf{RefCntFsck} setting.
Craig
On Tuesday, September 19, 2017, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:
> refCnt is also run on backup #1 (that in my case is the inc
refCnt is also run on backup #1 (that in my case is the incremental
that i've aborted).
is this correct ? I had a similiar issue with the alpha version, where
an fsck was always executed, but AFAIK this bug was fixed when BPC 4
was released as stable.
2017-09-19 14:11 GMT+02:00 Gandalf Corvotempe
Can someone explain me the meaning of $Conf{RefCntFsck} = 1; ?
If I understood properly, based on docs, $Conf{RefCntFsck} = 1 will
run a refCnt process if the latest backup is full.
In my case, I have a single full backup and i've aborted an
incremental one, then refCnt is run on the full backup.
Still getting the same issue.
Backup for a couple of host are impossible, bpc hangs (at different
progresses) and doesn't continue anymore.
No load on backup server and on source server. Simply, bpc doesn't transfer.
2017-09-18 15:38 GMT+02:00 Gandalf Corvotempesta
:
> 2017-09-18 14:30 GMT+02:00
30 matches
Mail list logo
