Index: /branches/eam_branches/ipp-20120805/Ohana/src/dvomerge/doc/failsafe.txt
===================================================================
--- /branches/eam_branches/ipp-20120805/Ohana/src/dvomerge/doc/failsafe.txt	(revision 34356)
+++ /branches/eam_branches/ipp-20120805/Ohana/src/dvomerge/doc/failsafe.txt	(revision 34357)
@@ -1,2 +1,28 @@
+
+20120809
+
+more on failsafe
+
+I need to improve the technique I'm using for failsafe ops / rerun.
+
+ * Image.dat PHU keywords:
+   DVO_DB_ID : %s : hex string with 32 byte "unique" string for DB
+   DM_NMERGE : %d : number of databases merged into this onea
+   DM_nnnnnn : %s : DVO_DB_ID of merge (nnnnn)
+
+   Note: nnnnnn may be greater than NMERGE if entries are skipped
+     (only a total of NMERGE nnnnnn values are allowed)
+
+ * region.cpt PHU keywords:
+   DM_NMERGE : %d : number of databases merged into this one (needed?)
+   MS_nnnnnn : %d : size of merged db entry nnnnnn
+   MT_nnnnnn : %s : date/time of merged db entry nnnnnn
+   
+ Is there a reason for the image entries?  (additional record keeping)
+
+ 
+
+
+201206??
 
 we have a problem with dvomerge and flaky hosts.  the problem is that