On Monday 03 July 2006 23:12, Wolfgang Denk wrote:
I ran into a strange failure mode, which I don't understand:
This is one of the typical reports I get when backing up the catalog:
JobId: 2974
Job:BackupCatalog.2006-06-30_01.00.00
Backup Level:
Dear Kern,
in message [EMAIL PROTECTED] you wrote:
Unless your OS is broken, Bacula always detects and reports when a volume
gets
a write error, which is the case when your partition fills up. I would
That was my expectation, too. dir and sd running on a FC2 system
(with a
On Tuesday 04 July 2006 16:12, Wolfgang Denk wrote:
Dear Kern,
in message [EMAIL PROTECTED] you wrote:
Unless your OS is broken, Bacula always detects and reports when a volume
gets a write error, which is the case when your partition fills up. I
would
That was my expectation, too. dir
In message [EMAIL PROTECTED] you wrote:
You mean the Volumes are on an NFS mounted partition? or do you mean the
data
you are backing up?
What counts is where the Volumes are.
The volumes are on a NFS mounted partition.
If they are on NFS mounted partitions, then all bets are off. If
On Tuesday 04 July 2006 21:24, Wolfgang Denk wrote:
In message [EMAIL PROTECTED] you wrote:
You mean the Volumes are on an NFS mounted partition? or do you mean the
data you are backing up?
What counts is where the Volumes are.
The volumes are on a NFS mounted partition.
If they are
I ran into a strange failure mode, which I don't understand:
This is one of the typical reports I get when backing up the catalog:
JobId: 2974
Job:BackupCatalog.2006-06-30_01.00.00
Backup Level: Full
Client: xx-fd
