Here's what I've done: /data1 is mounted as /ozette/data1 on fleetlink (ozette is the system that WILL be mvcodata) (fleetlink is the system that IS mvcodata, but won't be after the move) I've transferred /data1/www/mvcodata to /ozette/data1/www/mvcodata I've transferred /data1/mvcodata to /ozette/data1/mvcodata I've changed owners througout the directory to janet.users (ok?) PLANs: 0) Rebuild JGOFS exec's; add jg alias ScriptAlias /gb/ /data1/wwwsupport/utilities/port80/ ScriptAlias /jg/ /data1/mvcodata/htmlbin/ Add /data1/www/optserver to new mvcodata too Copy /data3/mvcodata_support to new mvcodata too [will need to do two subdirectories again.] Transfer /home/old-data1/SaveForProcessing to /ozette/data1/data_mvcodata/SaveForProcessing Assume that T1 link will be available so can transfer all files from mvco7 at one time. Change the ncftpget.bat routine to do the transfer within one step, not separately for each instrument. This is necessary so that the summary processing can take place before the files are moved to the Archive directory. 1) Turn off processing 2) Transfer /data1/data_mvcodata to /ozette/data1/data_mvcodata Also in this step, Copy all archived files to ../SaveForProcessing so that there can be a massive run to reprocess. 2a) Transfer /data1/wwwsupport to /ozette/data1/wwwsupport 3) Re-Transfer /data3/mvcodata_support/SaveForProcessing & SaveForProcessing_Images to /ozette/data1/data_mvcodata/SaveForProcessing & SaveForProcessing_Images 4) What about the other misc stuff in mvcodata_support???? Where should that go???? How about /ozette/data1/mvcodata_support?? Edit config file for process_mvco.active [i.e. .pl] so that web served files go into ftp "pub" directory 5) How do you automate the ftp? and web building? Solution: ncftpget.bat etc. does the work using the perl script. But the config file has to be edited to point to the ftp /pub location for the processed (Web accessible too) files. Original files still go to ../Archive which is not ftp accessible. AT THE SAME INTERVAL of processing is off .... Have CIS (Mike Bishop) turn off the alias to fleetlink 6) I'll change ozette into mvcodata 7) Restart Processing (above 7 steps in a day) THEN: 8) Catch up ... generating summaries (yearly and daily) ... probably in the ~ftp/pub/mvcodata directory structure??? Does this mean that you will POINT to these files in your WebData??? OK?? 9) Automate the generation of summaries 10) Adapt the WebData to point to the summaries not the raw data NOTE: The T1 line should be ready by next week :) Please call me when you can get together today so we can plan to do this stuff tomorrow?? I need to set up a switchover time with Mike Bishop. Janet