Hello, list.
I've installed rsyncd on a new PC that arrived to the office (all of the
old ones are backuping OK) and after following the README instructions
for Windows XP PCs, I get the following:
C:\rsyncd>rsync -av [EMAIL PROTECTED]::myDocs
rsync: failed to connect to 192.168.0.168: Connecti
Michal Wokoun wrote:
I've installed rsyncd on a new PC that arrived to the office (all of the
old ones are backuping OK) and after following the README instructions
for Windows XP PCs, I get the following:
C:\rsyncd>rsync -av [EMAIL PROTECTED]::myDocs
rsync: failed to connect to 192.168.0.168: C
Hi,
> > Ok thanks, that would be a solution for me. Another question to this
> > topic. Is it possible with BackupPC to save the backup data on an
> > other Server and not on the BackupPC-Server? For example the
> > BackupPC-Server should transfer the backup data automatically via
> > ftp on a
> Ok thanks, that would be a solution for me. Another question to this
> topic. Is it possible with BackupPC to save the backup data on an
> other Server and not on the BackupPC-Server? For example the
> BackupPC-Server should transfer the backup data automatically via
> ftp on an other Server.
you can use NFS for create one new mount point (please don't use cifs
"windows", don't run well) my recomendation are
always use local file systems
On Sat, 30 Dec 2006 12:06:15 +0100, Simon Köstlin wrote
> Ok thanks, that would be a solution for me. Another question to this topic.
> Is it p
Do you have other error too, the path don't will don't run because you must use
the small from (less of 8 chars) for windows
- please use MYDOCS~1 for path. and the firts thest use a short form of short
path C:/temp for example
- test from your linux backuppc server: telnet 192.168.0.168 873
if
I use reiserfs because has better performance with many and small files...
On Sat, 30 Dec 2006 10:23:24 +1000, Michael Mansour wrote
> Hi John,
>
> > I was wondering if people had any recommendations for a filesystem to
> > use with BackupPC?
> >
> > I am currently using ext3 but now I can't f
> It could also be the network card (with a Linux driver that has not be
> thoroughly debugged for the kind of network traffic that BackupPC
>From experience, the cards we've had the most success with have been the Intel
Ether Express 100s and 1000s, and the onboard nForce chipset cards. Neither
On 30/12/06, Michal Wokoun <[EMAIL PROTECTED]> wrote:
> I checked it and I am running 2.6.19.1.
>
> Any other suggestion where I could look to find out the problem?
It could also be the network card (with a Linux driver that has not be
thoroughly debugged for the kind of network traffic that Backu
Ok thanks, that would be a solution for me. Another question to this topic. Is
it possible with BackupPC to save the backup data on an other Server and not on
the BackupPC-Server? For example the BackupPC-Server should transfer the backup
data automatically via ftp on an other Server.
That means
Nils writes:
> > If you want to change the data path, simply edit the config and
> > change the
> > TopDir variable.
>
> As Craig recently pointed out the path is hardcoded both in the
> config file and another file (can't remember right know). You'll need
> to edit both. So symlinking is p
Michael writes:
> When I installed backuppc, I had this question:
>
> Please specify a data directory for BackupPC. This is where all the
> PC backup data is stored. This file system needs to be big enough to
> accommodate all the PCs you expect to backup (eg: at least several GB
> per machine)
>
> The problem isn't a problem with BackupPC if the machine is hard
> locking. It's either a kernel or a hardware problem.
OK, I will now try to pursue this track.
> How long did you run memtest for, was it at least 24 hours? In
It was about 5 or 6 hours.
> addition to memtest, I also recommen
13 matches
Mail list logo