>
> I'm using the tar method for backups with the default tar command in the
> config file. For each incremental backup, every file that has not
> changed is reported as being an Xfer error. Is this the intended
> behaviour? I'm getting ~ 25 Xfer errors per share because of this.
what
Hello,
I am backing up a WindowsXP system and get always
2005-11-09 21:32:50 10.0.1.100: mkdir
/var/lib/backuppc/pc/10.0.1.100/new//fC$/fBOOTWIZ: File exists at
/usr/share/backuppc/lib/BackupPC/Xfer/RsyncFileIO.pm line 537
2005-11-09 21:32:56 Backup failed on 10.0.1.100 (Child exited premature
I'm using the tar method for backups with the default tar command in the
config file. For each incremental backup, every file that has not
changed is reported as being an Xfer error. Is this the intended
behaviour? I'm getting ~ 25 Xfer errors per share because of this.
eg output)
Running
the files are stored in a compressed (not strictly gzip) format; which is
probably throwing the scanner off.
you could always try storing the files uncompressed, by specifying the
following option:
$Conf{CompressLevel} = 0;
try that on the host in question, and see if your virus scanner detects
On 11/10 05:46 , Trey Nolen wrote:
> I was thinking about scanning my backups with ClamAV. I figured I might
> spot viruses on the backups and then I can go attend to them on the machines
> themselves - just an added layer of protection. However, I was doing some
> testing, and I backed up a h
I was thinking about scanning my backups with ClamAV. I figured I might
spot viruses on the backups and then I can go attend to them on the machines
themselves - just an added layer of protection. However, I was doing some
testing, and I backed up a host with the test virus EICAR.COM on it. W
