[EMAIL PROTECTED] wrote: > Hi Josh, > > ... > > Ok. I think I understand how to configure the autoloader. > But is it possible to combine more physical disks to one autoloader? > For example to configure two autochanger with 3 physical drives per changer. > Than I can backup the weekly pool to one autochanger and the monthly pool to > the other. >
You can have 2 autochangers, each with a set of 3 physical disks. However, the script treats a physical disk as a magazine. You cannot have all 3 of an autochanger's physical disks plugged in at the same time, just as with a tape autoloader you cannot have all magazines inserted at the same time. When one physical disk becomes full you will need to change "magazines". This is done in the same manner as a tape autoloader that has a barcode reader. Unplug the current physical disk. Plug in the next physical disk. Then issue the bconsole "update slots" command in order for bacula to determine what volumes are in the autochanger. > ... > > So you think it is better to make more pools for one backup. > And for every pool I need a virtuel slot, right? > Well, I think it is better to have multiple smaller files on the disk rather than one large file to reduce the risk of total data loss in the event of a hardware or other error that damages the USB disk or its filesystem. You could use a different pool for every slot, but you could also use one pool for each autochanger and multiple bacula volumes (slots/files) in each pool. I would use the latter and set the "Volume Use Duration" for the pool resource such that a volume is only used for one day, after which bacula will stop using that volume and select another. So if I intended to use the USB disk for a week before rotating it out, I would probably define 8 slots. One for each day and an extra in case there was a holiday or something that prevented it be changed on time. Initially, the vchanger script creates a volume for each defined slot and places them in the Scratch pool. That way, when bacula stops using a volume due to the "Volume Use Duration" expiring, it will move one of the (empty) volumes in the Scratch pool into the pool defined for the autochanger and begin using it. Note that bacula never deletes or truncates any of the files. When a volume is deleted or recycled, bacula only deletes or updates its status in the catalog. Thus for volumes on disk storage the disk space is never freed. You will have to do that manually or use the vchanger purge command. The purge command is a workaround for this problem that deletes all volumes on a USB disk both from disk and the bacula catalog, then re-creates them in the Scratch pool. This is of course a dangerous command because it deletes volumes without regard to retention times. It is definitely not defined in the official Bacula Autochanger Interface API. :) There is a feature request pending to handle deleting or truncating disk files when a bacula volume is deleted or recycled, however I do not know the status of its implementation. > ... > > Thank you for your help > > You're welcome. ------------------------------------------------------------------------- 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
