Hi,
On 5/29/2007 10:52 PM, Joseph Wright wrote:
> On May 29, 2007, at 1:29 PM, Arno Lehmann wrote:
>
>> Hi,
>>
>> On 5/29/2007 7:38 PM, Joseph Wright wrote:
>>> I went from having a device which interleaved jobs from various
>>> clients to having separate devices for each client, although they are
>>> all using the same storage pool.
>> This is probably one area where the recent improvements to the
>> reservation system might help... which version of Bacula do you run?
>
> 2.0.3
Well, if you dare running a beta version, 2.1.10 might be worth a try.
Downgrading after testing should be simple enough since there are, as
far as I know, no database schema changes involved.
>>> Now there are occasions where a job
>>> tries to create a new volume that another job has already created.
>>> Instead of skipping the attempt and making a new volume, which it
>>> seems like it should do, the whole job fails like so:
>>>
>>> 29-May 09:46 dss07-sd: End of medium on Volume "dss07-0010"
>>> Bytes=21,474,815,222 Blocks=332,881 at 29-May-2007 09:46.
>>> 29-May 09:46 dss07-sd: vl1-001-root.2007-05-28_22.41.14 Warning:
>>> Volume "dss07-0011" not on device "vl1-001-device" (/spac
>>> e/backup/vl1-001).
>>> 29-May 09:46 dss07-sd: Marking Volume "dss07-0011" in Error in
>>> Catalog.
>>> 29-May 09:46 dss07-sd: vl1-001-root.2007-05-28_22.41.14 Warning:
>>> Volume "dss07-0011" not on device "vl1-001-device" (/spac
>>> e/backup/vl1-001).
>>>
>>> 29-May 09:46 dss07-sd: Marking Volume "dss07-0011" in Error in
>>> Catalog.
>>> 29-May 09:46 dss07-sd: vl1-001-root.2007-05-28_22.41.14 Error: Could
>>> not open device "vl1-001-device" (/space/backup/vl1-001): ERR=dev.c:
>>> 483 Could not open: /space/backup/vl1-001/dss07-0011, ERR=No such
>>> file or directory
>>>
>>> 29-May 09:46 dss07-sd: Job write elapsed time = 11:05:36, Transfer
>>> rate = 1.072 M bytes/second
>>> 29-May 09:46 vp1-001-client: vl1-001-root.2007-05-28_22.41.14 Fatal
>>> error: backup.c:873 Network send error to SD. ERR=Broken pipe
>>> 29-May 09:47 dssdir01-director: vl1-001-root.2007-05-28_22.41.14
>>> Error: Bacula 2.0.3 (06Mar07): 29-May-2007 09:47:02
>>>
>>> The broken pipe seems strange since the other jobs continue to run,
>> I guess this is just a symptom of serious confusion in Bacula :-)
>>
>>> and I can reach it doing 'status storage' in bconsole.
>>>
>>> This is how my Pool is defined:
>>>
>>> Pool {
>>> Name = dss07-pool
>>> Pool Type = Backup
>>> LabelFormat = dss07-
>>> AutoPrune = yes
>>> Volume Retention = 14 days
>>> Maximum Volume Bytes = 21474836480
>>> Recycle = yes
>> You probably want to limit the number of volumes in that pool, because
>> otherwise volumes will not be recycled but Bacula will forever try to
>> create a new one.
>>
>
> I thought that it would start recycling after the volume retention
> period was over.
No, volumes are recycled onle when there is no other legal way to find
new space.
> I suppose the easiest solution for the whole problem is just creating
> separate pools for each client?
That would be one possibility, but I would not really like such a
solution myself... too much hassle managing the volumes, once you have a
larger number of clients.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
