From: Kern S. <ke...@si...> - 2006-07-05 20:56:08
|
On Wednesday 05 July 2006 22:25, Arno Lehmann wrote: > Hello, > > On 7/4/2006 10:31 PM, Kern Sibbald wrote: > ... > > > The reason for this email is to propose an alternate solution, which I > > think would be much better. My proposal is to modify the job record for > > the original job so that the Job type (currently B for backup) becomes > > "b" for > > > > migrated backup job. The output would then look like: > > | 1 | MigrationJobSave | 2006-07-04 21:31:48 | b | F | 2,638 | 63,701,259 > > | | T > > > > and now, it should be clear to the user that the job was migrated, and > > the current code that does a restore will work with no changes. The only > > remaining items would be to ensure that for operations like pruning, > > bscan, dbcheck, ... that the code understands this new job type (the same > > problem I have with the new "M" (migration) job type. > > > > Comments? > > Sounds reasonable. But, as John mentioned - What about Archived copies, > or, more generally, multiple valid copies of one backup job? Those are projects that I am not working on at the moment (hopefully someone else will do them). As a consequence, I am only worried about Migration and doing my best not to do anything that would work Bacula into a corner in the future, which I do not believe is the case. > > Apart from these worries, I like the additional effect of the indication > to the user that a job has been migrated. Yes, me too, and it seems to be working quite well now. I just eliminated a nasty bug in the SD end of migration, so it is now passing the first regression test OK. > > (Concerning that - one _possible_ workaround for the copies problem > could be to use more than one distinct job types... for example, > consider the job types "1" to "9" for (up to) nine valid copies of a > job. Admittedly, this limits the possible number of copies, but I think > 9 (or perhaps 10) valid copies is a reasonable limit. I suspect that I won't even label the copies (we'll see). Currently there is a provision for it in the JobMedia records, but I suspect that in the end I will remove it. I believe that all that needs to be done is to mark the Job as a copy. Then if Bacula wants to use a copy of something, it can go and look, and if it finds 10 copies or 1000 it can somehow choose -- perhaps using your "Cost" field :-) > > Selecting which ones to use would be rather simple - ask the user. > Perhaps presenting her with the costs asigned to the volumes needed for > each set of volumes :-) Yes, I don't think that will be a big problem. > > Arno > > > Best regards, > > > > Kern > > > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Bacula-devel mailing list > > Bac...@li... > > https://lists.sourceforge.net/lists/listinfo/bacula-devel |