Hello all, I have a question about bacula conception.
When you define a job, you have to tell in it where you will store the data, with the keyword Storage. Imagine you do backup on disk: on the storage conf file, you define 3 virtual drives (VirtualTapeDrive_01,VirtualTapeDrive_02,VirtualTapeDrive_03) which take 4GiBFile as media. In the job definition, you have to put the name of the storage through which data will be written. Let's name them VTD_01, VTD_02, VTD_03 to be consistent with the definition in the bacula-sd.conf file. They are name in the bacula-dir.conf file. At this point i don't understand. Why define a storage device instead of a storage daemon in the job definition. If the drive is already used, your job will have to wait until it would be available again, even if the storage demon manages 2 others drives which are free. So why such a conception ? In this manner, you can do a sort of load balancing by storage daemon, you have to do a load balancing by jobs, which is more difficult to manage. Do I understand something wrong ? Can someone explain me why this choice ? Thanks !
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
