More migration cleanup

[bacula/bacula] / bacula / technotes-1.39

diff --git a/bacula/technotes-1.39 b/bacula/technotes-1.39
index 08758fe02a5bad1c31c33ff646f4ccaafaa11f6d..0e6b0395d1cdc93670e407a1ba4a57f4781a71c1 100644 (file)
--- a/bacula/technotes-1.39
+++ b/bacula/technotes-1.39
@@ -1,6 +1,37 @@
               Technical notes on version 1.39  
 
 General:
+22Nov06
+kes  Cleanup some of the error termination code in migration.
+kes  Separate read/write source strings to keep track of where
+     storage devices are used in a job.
+kes  Implement a new method of keeping track of which storage 
+     device is used in a Job.  USTORE keeps both a pointer to the
+     resource and to the source string.
+kes  Modify all code to use new storage set subroutines in job.c
+kes  Modify migrate.c so that the definitive selection of the storage
+     resource is done in the do_migration_init() routine prior to
+     the job going into the job queue.  This permits accurate 
+     deadlock detection (same read and write storage resource).
+kes  Remove bfill from btape (I think it was a left over stub).
+22Nov06
+kes  Make sure that the storage for a job is pulled first from
+     the Pool and if not from the Job.  
+kes  Ensure that either the Pool or the Job specifies a Storage
+     resource.
+21Nov06 
+kes  Start applying new FSFE copyright.
+20Nov06
+kes  Add additional error messages in acquiring a drive for read.   
+kes  Make WritePartAfterJob the default so that the last DVD part 
+     always gets written to the DVD by default.
+kes  Add additional error messages in migration. 
+kes  Suppress redundant error messages in migration (possibly more to do).
+kes  Apply Martin's fix (updated to 1.39) that takes into account
+     run storage overrides in the Director status display.
+kes  Implement, but turn off the submitted code that sets the EOT
+     model on FreeBSD machines. Turning on this code is too risky at
+     this point in the development.
 19Nov06
 kes  Implement unique dbid routine for migration to prevent the same
      JobId from being migrated twice. This should fix bug #709.