I actually do this on my tru64 unix and my sco unix machines. This works
quite well. It also uses up way less RAM with rsync, which is good because
some of the tru64 machines don't have a lot of extra RAM.
I have one specific tru64 alpha 4cpu machine that I have 4 hosts setup for
and I trigger a
Hello,
I'm trying to backup a remote client via rsyncd.
The local network (192.168.0.0/24) and the remote network (192.168.1.0/24)
are connected via VPN.
A ping to the remote client (192.168.1.21) works, the ping is about 120ms)
Starting a backup also works, but after a while, I get the message:
Sam Przyswa wrote:
> Hi,
>
> I moved the backuppc v2.1.2 root dir (130Go) on a new machine and
> backuppc 3.1.0 that's work but on each backup the size of this new dir
> rise and rise as if the previous backuped files/dirs are not kept. At
> this time in 2 backups days I had to extend the files
Hi,
My backups often don't complete due to time-outs (or whatever).
Would it make sense, to split the rsyncd share into several shares (for
example: /pictures /data /[rest]), in order to make it more likely, that a
backup finishes, and that I don't have to start from scratch if the whole
backup wa
Hi,
I moved the backuppc v2.1.2 root dir (130Go) on a new machine and
backuppc 3.1.0 that's work but on each backup the size of this new dir
rise and rise as if the previous backuped files/dirs are not kept. At
this time in 2 backups days I had to extend the filesystem of 40Gb !
What's wrong ?
Chantal Rosmuller wrote:
> Hi list,
>
> I am using backuppc 2.1.1 on a debian system. I use it to backup laptops
> (among others) with dhcp addresses and it works great. However there is one
> issue:
>
> We have 2 offices that are connected through vpn, one with ip range
> 192.168.2.0/24 other
