From: Francisco R. <li...@st...> - 2006-07-30 04:59:22
|
Kern Sibbald writes: > If anyone is willing to help out "upgrading" the existing SQL statements in > Bacula so that they explicitly are aware, where necessary, of the new Enabled > field in Media records, please email me, copying the devel list (so that we > don't have 100 volunteers). A good knowledge of Bacula and SQL is important, > but C/C++ programming is not. I could help. Several months back I volunteered to try and look into SQL optimization, including doing the changes in the program. Due to my rusty C/C++ plus lack of time I don't think I will be able to help with that in any time soon. What I do plan to do in coming weeks is to look at the queries by looking at the database logs and advise from there. If this "upgrading" is mostly SQL.. and some light reading of C/C++ I am game. > The new "Enabled" field can take on three values 0,1,2 which mean Disabled, > Enabled, Archived respectively. Could you expand on their meaning.. for those of us not familiar with this new functionality? Has this been discussed so I could look it up on archives? > As a consequence, all volumes that are not > Enabled must be ignored for all backup/restore operations, How would a volume get marked as disabled? > The work > consists of doing a careful audit of the SQL in Bacula (lots of it) and > making a list of where the changes need to be made, or actually making them > yourself. Ideally, you would also test each proposed new SQL statement to > ensure that it functions correctly after being modified. Is there any way to split this task? |