daurril mons collection:  midterm recovery and flight correction. 1/29/2002  2:18:00 PM.  Present discussion presumes some familiarity with the terms involved in referencing my hardware data objects.
2:31 PM 1/29/02. This workbook is a platform to the collection and arrangement of data pertaining to my present inventory of ten (10) at least fractionally operational websites.  This particular worksheet introduces that collection … Procedures:
General Workflow for all non-IIS development is for new work to come up first on et1.  New Mons work is usually uploaded from et1 as it occurs.  Routinely all new work is transferred to et3, updating whatever previous related material may already be there.  Selected collections may then be transferred to CD, usually in their entirety - ie, each new backup creation entirely replaces its predecessor.  (Also, FTP transfers are only available in et1, and the CD is written only from et3.)
Recovery: per log FR 1/25/02 1860 et3:  "Looking at what's actually in et3's mons-collection, several sites are not even there.  Need to drop back to et1 and get the uploaded copy back down (now obivously to et1).  Before leaving et1, get any applied Mons updates onto et3." 
Now 1:29 PM 1/27/02:  etc = "According to the GW rule for Mons, the empirically obvious solution (presuming that all outstanding Mons updates from et1 were previously applied) would to be bring each current FTP down into its respective (cleared) et1-space.  This may be effected. rather than an exhaustive recreation acc/to the usual maintenance process - despite that et3 is presumed to be a higher order of backup than the FTP.  After the FTP reload, apply each result to the respective et3 and clear its et1."  ie, as tabulation this would be a 3-way merge, applying whatever is in et1 to whatever is on the (read-only) CD and shipping that to et3, where eventually any new et3 is run out to the (next edition) of the CD.  As new development is created in et1, the (new) CD will be taken to represent any exiting materials, and (as developed) FTP items will be replaced/augmented from et1. 
created 9:33 AM 1/27/02
Now 2:21 PM 1/27/02:  Despite the high thinking expounded above, 1:29 will literally affect solutions below where the policy called "etc" is applied.  Other particular solutions may apply instead, including doing nothing.  Also, since FTP cannot be mechanically represented by a direct, d14701 (which can be) might represent the data image from et3 (if no update transfer from et1 has intervened) as well as FTP.
Thruout this paper there will be references to directs.  This refers to the 2- or 3-step process that generates, via a DOS-bat front-end, the "<DIR>"-lines populating this report.  That process is taken as intuitive and not yet set to paper.
created 1/27/2002  6:12:00 AM            
d14701 = d1470, 020114_0913:\mons-C.       status / sources
disk filename item 1/27/02 9:40 solution / comment
.           .                
d1470 <DIR> 1/14/02 9:30a mons = mons-C .                
d14701 <DIR> 1/14/02 9:31a mons_1992 5 available
et1-c <DIR> 12/5/00 9:21a mons_1992 . empty, no et3 replace no problemo
et3-c <DIR> 12/13/00 8:28a mons_1992 d default master            
d14701 <DIR> 1/14/02 9:31a mons_allyson 6 available
et1-c <DIR> 12/5/00 9:22a mons_allyson . empty, no et3 replace no problemo
et3-c <DIR> 12/13/00 8:28a mons_allyson d default master            
d14701 <DIR> 1/14/02 9:31a mons_athens 2 available
et1-c <DIR> 12/5/00 9:22a mons_athens . empty, no et3 replace no problemo
et3-c <DIR> 12/13/00 8:28a mons_athens d default master            
d14701 mons_choirs 4 none
et1-c <DIR> 12/12/00 3:56p mons_choirs . copied out: b, et3 reload from FTP, etc
et3-c       mons_choirs   empty            
d14701 mons_churches 3 none
et1-c <DIR> 12/5/00 9:22a mons_churches d empty, F. to et3 pure R, nothing else
et3-c       mons_churches   empty            
d14701 <DIR> 1/14/02 9:31a mons_comstands 10 available, used
et1-c <DIR> 11/20/01 6:33a mons_comstands . copied out: b, et3 done
et3-c <DIR> 11/26/01 9:33a mons_comstands d default master            
d14701 <DIR> 1/14/02 9:31a mons_daurril 7 available, used
et1-c <DIR> 12/10/01 4:03a mons_daurril . copied out: b, et3 done
et3-c <DIR> 12/10/01 12:02p mons_daurril d default master            
d14701 mons_pac 0 none
et1-c <DIR> 12/5/00 9:23a mons_pac . non-F, no et3 xfr fortunately, case 0 is altogether replace by case 8.
et3-c       mons_pac     forever missing            
d14701 mons_pac_new 1 none
et1-c <DIR> 12/5/00 9:23a mons_pac_new . copied out: b, et3 done
et3-c       mons_pac_new   empty            
d14701 <DIR> 1/14/02 9:31a mons_parsons 9 available, used
et1-c <DIR> 10/30/01 5:35p mons_parsons . copied out: b 2 reconstructed and enhanced: shipped to et3.
et3-c <DIR> 10/31/01 1:16p mons_parsons d default master 2 save found version at et1-c as mons_parsons-et3: replace.
d14701 <DIR> 1/14/02 9:31a mons_wellsHS 8 available, used
et1-c <DIR> 1/11/02 1:11p mons_wellsHS . copied out: b, et3 done
et3-c <DIR> 1/11/02 1:31p mons_wellsHS d default master            
d  = use this direct for documentation sheet if on et1c, it is after step 4 below.
F = refilled from FTP
b = refilled by co, cd, cb sequencd
note: 1/27/2002  9:40:00 AM:
Most of the intent of the recovery exercise is explained in Procedures.  Re the solution set, "nothing" is represented by "no problemo;" and "defaults" in both et1 and et3 invariabley rolls out present et1 content, rolls in the CD,  applies the local rollout which is then set for transfer to et3.  "Done," as it occurs, makes the solution look bright blue.  Its importat to recognize that whatever is now done on the "ground" will not affect our orbiting FTP until some further developments make actual contact with it.  Any discrepancy presumably would be noticed at that time. 
Actual recovery processing (steps)3: 3 item nos reassigned 6:12 AM 2/1/02
new intro sequence old
1:  now 2:15 AM 1/28/02: At the start of the batch run, items 0, 1, 2, 3, and 5 are considered done.  0 mons_pac 0
2:  now 2:29 AM 1/28/02: Run [b = refilled by co, cd, cb sequencd] on items 2, 7, 9, and 6 (old 6, 7, 9, 10). 1 mons_pac_new 8
3.  now 2:36 AM 1/28/02: Fill items 4 and 8 from FTP [F]: end 3:14 AM 1/28/02. 2 mons_athens 3
4:  now 6:31 AM 1/28/02: Do the (6) copybacks associated with steps 2 thru 3 here.  Done 6:42 AM 1/28/02.  3 mons_churches 5
5:  now 6:45 AM 1/28/02: Write the updated et1-set back out to et3.  Item 9 hosed: leave 7:47 AM 1/28/02. 4 mons_choirs 4
2 now 5:52 PM 1/31/02: enter current disposition in the table above.  5 mons_1992 1
6: now 5:28 AM 2/5/02: Finalization of all tis corrective effort may be said to have occurred in the last 18 hrs.  An update CD 020204_1210 has been created from an updated et1 applied to et3.  Then all but the respective indices (and their support files) were erased from et1, and a copy of the reduced start-up set saved in local mons as a 1.25M C:\mons\1reduced-index-set. 6 mons_allyson 2
7 mons_daurril 7
8 mons_wellsHS 10
9 mons_parsons 9
10 mons_comstands 6
7.  Procede to documentation development, from directs and content-graphics avaiable from et1 (as et3 precursor). 
Then let's say we can recreate a useful "down-here" copy of what's supposed to be whatever should be "up-there."  The documentation pages already (3:45 PM 1/27/02) started in this workbook are using the et3 directs developed since Friday.  A policy needs indicate where the presumably "generic" directs came from for each site as the documentation goes to completion. 
1