 |
suggested solution: a) introduce a meta-file device that works like an autochanger for file media and b b) introduce a locking mechanism that checks if a medium is currently used or requested by a prior job for reading and put that job in a waiting queue |
|
|
Needs investigation and is probably a lot of work. |
|
|
For option a there is already a couple of options: - vchanger (external program) - diskchanger (supplied with the source and used in regressions.) - internal virtual changer with /dev/null changer cmd. It is known that the selection in the SD of tapes/volumes can sometime run into some race condition selecting a volume for read and write etc. This means a lot of work in the SD which we plan to do eventually but as it means a serious redesign it probably won't happen before the end of this year. |
|
|
hello marco, yes we know that we can use a vchanger (we do so) but I think in general it would be good if bareos supported multi-file devices ootb. but the virtual tape lib does not help with the copy/move jobs, as described before. |
|
|
> it is not possible to have multiple "drives" for a single type of file media. That is not true. It is just not documented how this works. My setup has been running for a few years, so this is tried and tested. sd.conf: Device { Name = filestorage-1 Media Type = filestorage Archive Device = /var/backup/filestorage/ LabelMedia = yes; Random Access = Yes; AutomaticMount = yes; RemovableMedia = no; AlwaysOpen = no; } [... repeat with additional numbered names ...] -------- director.conf Storage { Name = filestorage Address = x.x.x.x SDPort = 9103 Password = "somepwd" Device = filestorage-1 Device = filestorage-2 Device = filestorage-N [... repeat with as many writers as defined in the sd.conf - in my case 10 ...] Media Type = filestorage Maximum Concurrent Jobs = 10 } ------- I have another set of those definitions for incremental backups (filestorage-incremental). Then i defined a full and incremental pool for each client that point to filestorage and filestorage-incremental respectively. And each pool has his own label definition. So the result when looking at the target directories is something like this: ------- ls /var/backup/filestorage clientA.full.0001 clientB.full.0002 clientC.full.0003 ls /var/backup/filestorage-incremental clientA.incremental.0004 clientB.incremental.0005 clientC.incremental.0006 ------- I have copy jobs that copy all those to my tape library (to two Pools, one for full, one for incrementals - so the jobs from ALL clients are condensed into two pools). Using attribute spooling (and two drives) i am able to copy multiple jobs in parallel (if a job finished writing to tape the next one starts writing while the first one is inserting the attributes). Works nicely, no race conditions, no blocking. My tape drives are configured to a maximum of one concurrent job as i do not want to have job interleaving on my tapes (just makes things messy). If you change this you could also have multiple jobs writing simultaneously to the tape drives. Any questions? ;) |
|
|
Thanks for that holtkamp. I can follow what you have done until: I have another set of those definitions for incremental backups (filestorage-incremental). Then i defined a full and incremental pool for each client that point to filestorage and filestorage-incremental respectively. And each pool has his own label definition. How/where did you define the other set of those definitions for incremental backups (filestorage-incremental)? And where/how did you define the full and incremental pool for each client that point to filestorage and filestorage-incremental respectively. And each pool has his own label definition. Thanks Paul |
|
|
We did abandon that concept a while ago, now clients only have one pool. What we did back then was create two pools for each client: poolname: clientname-full-pool label format: clientname.full. poolname: clientname-incremental-pool label format: clientname.incremental. (plus all the other options). and in the job definition for the client specify this: Full Backup Pool = clientname-full-pool Incremental Backup Pool = clientname-incremental-pool This way it gets split into the pools. If you want to get a look at my updated configuration there is a Youtube video from my talk at the OSBConf 2014 https://www.youtube.com/watch?v=PPU7u9y5RCY |
|
|
Thankyou for your reply. Can hear your presentation fine but not read the screen! Do you have the slides (powerpoint?) from the presenation please? Thanks |
|
|
Slides are on the Conference Page here: http://osbconf.org/wp-content/uploads/2014/09/Migration-from-Bacula-to-Bareos-by-Daniel-Holtkamp.pdf Have fun! If you have any questions you can contact me directly - format is lastname at riege dot com. |
|
|
long forgotten issue. Use virtual changer for file with multiple drives. |
- Anonymous
