[Bacula-users] problem with nfs mounted shares --> the following files are in the catalog but not on the volume

2011-05-06 Thread J. Echter
Hi, i have a fileset containing nfs mounted shares, but these seem to not get backed up. my fileset resource looks like this: FileSet { Name = "Bacula" Include { Options { signature=SHA1 verify = pins1 compression = GZIP recurse = yes sparse = yes

Re: [Bacula-users] problem with nfs mounted shares --> the following files are in the catalog but not on the volume

2011-05-06 Thread Phil Stracchino
On 05/06/11 03:59, J. Echter wrote: > Hi, > > i have a fileset containing nfs mounted shares, but these seem to not get > backed up. Don't back up over NFS if you can avoid it. You'll get much better performance backing up the NFS shares on the NFS server. -- Phil Stracchino, CDK#2 DoD

Re: [Bacula-users] problem with nfs mounted shares --> the following files are in the catalog but not on the volume

2011-05-06 Thread J. Echter
Am 06.05.2011 13:02, schrieb Phil Stracchino: > On 05/06/11 03:59, J. Echter wrote: >> Hi, >> >> i have a fileset containing nfs mounted shares, but these seem to not get >> backed up. > Don't back up over NFS if you can avoid it. You'll get much better > performance backing up the NFS shares on

Re: [Bacula-users] problem with nfs mounted shares --> the following files are in the catalog but not on the volume

2011-05-06 Thread Martin Simmons
> On Fri, 06 May 2011 09:59:49 +0200, J Echter said: > > Hi, > > i have a fileset containing nfs mounted shares, but these seem to not get > backed up. > > my fileset resource looks like this: > > FileSet { >Name = "Bacula" >Include { > Options { >signature=SHA1 >

Re: [Bacula-users] problem with nfs mounted shares --> the following files are in the catalog but not on the volume

2011-05-07 Thread J. Echter
Am 06.05.2011 20:19, schrieb Martin Simmons: >> On Fri, 06 May 2011 09:59:49 +0200, J Echter said: >> >> Hi, >> >> i have a fileset containing nfs mounted shares, but these seem to not get >> backed up. >> >> my fileset resource looks like this: >> >> FileSet { >>Name = "Bacula" >>Incl