I have a little more information. I have two storage locations configured, both set up to automatically label and recycle. The problem seems to come because it goes looking for a volume that was automatically labeled in one storage location, but it expects to find it in the other storage location. Some relevant bits from the log:
26-Jun 00:34 debian-dir JobId 1413: Recycled volume "Inc-0011" 26-Jun 00:34 debian-sd JobId 1413: Labeled new Volume "Inc-0011" on device "FileDisk2" (/disk2). 26-Jun 00:34 debian-sd JobId 1413: Wrote label to prelabeled Volume "Inc-0011" on device "FileDisk2" (/disk2) ... then did a backup to this volume successfully: Build OS: i686-pc-linux-gnu debian 5.0.7 JobId: 1413 Job: BackupAirplane.2011-06-25_23.05.01_12 Backup Level: Incremental, since=2011-05-20 23:37:42 Client: "airplane-fd" 5.0.3 (04Aug10) Linux,Cross-compile,Win32 FileSet: "Windows Full Set" 2010-12-27 23:05:01 Pool: "Inc-Pool" (From Job IncPool override) Catalog: "MyCatalog" (From Client resource) Storage: "StoreFile2" (From Job resource) Scheduled time: 25-Jun-2011 23:05:01 Start time: 26-Jun-2011 00:33:59 End time: 26-Jun-2011 02:54:03 Elapsed time: 2 hours 20 mins 4 secs Priority: 10 FD Files Written: 5,600 SD Files Written: 5,600 FD Bytes Written: 66,718,341,759 (66.71 GB) SD Bytes Written: 66,719,451,564 (66.71 GB) Rate: 7938.9 KB/s Software Compression: None VSS: yes Encryption: no Accurate: no Volume name(s): Inc-0011 Volume Session Id: 6 Volume Session Time: 1309030821 Last Volume Bytes: 66,769,096,562 (66.76 GB) Non-fatal FD errors: 2 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK -- with warnings ... then for some reason it goes looking for this same volume in the other storage location. I can't find it, and sets the status to "Error" and moves on to recycle a different volume: 26-Jun 02:57 debian-dir JobId 1411: Using Device "FileDisk1" 26-Jun 02:59 joycelatitude-fd JobId 1411: DIR and FD clocks differ by 67 seconds, FD automatically compensating. 26-Jun 02:57 debian-sd JobId 1411: Warning: Volume "Inc-0011" not on device "FileDisk1" (/disk1). 26-Jun 02:57 debian-sd JobId 1411: Marking Volume "Inc-0011" in Error in Catalog. 26-Jun 02:57 debian-sd JobId 1411: Warning: Volume "Inc-0011" not on device "FileDisk1" (/disk1). 26-Jun 02:57 debian-sd JobId 1411: Marking Volume "Inc-0011" in Error in Catalog. 26-Jun 02:57 debian-sd JobId 1411: Warning: mount.c:217 Open device "FileDisk1" (/disk1) Volume "Inc-0011" failed: ERR=dev.c:549 Could not open: /disk1/Inc-0011, ERR=No such file or directory 26-Jun 02:57 debian-dir JobId 1411: Recycled volume "Inc-0013" 26-Jun 02:57 debian-sd JobId 1411: Labeled new Volume "Inc-0013" on device "FileDisk1" (/disk1). 26-Jun 02:57 debian-sd JobId 1411: Wrote label to prelabeled Volume "Inc-0013" on device "FileDisk1" (/disk1) The net result is that each volume is used for a while, then set to "Error" status before it fills up or gets to max jobs or something else that might trigger recycling. If I leave it unattended it "wastes" all the volumes in this fashion and they can't be automatically recycled no matter how old they get. Mike +---------------------------------------------------------------------- |This was sent by m...@mwilt.org via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
