BOX - beginning of expedition
EOX - end of expedition

The outgoing programmer(s) is(are) responsible for all of the end-of-expedition (EOX) activities.

This expedition is ending.

Make sure we are getting as complete a copy of the data to be warehoused on shore as we can.

0. Negotiate a time window

Work with the LO, ALOs, EPM, MCS, laboratory Technical Staff. Three weeks before the end of the expedition you should have an (increasingly clear) idea how and when these activities will transpire.

...

It is Ok to ask repeatedly. It is an exercise in planning and preparation which helps us collectively focus and prioritize the tasks to be done.

1. Deliver the EOX tech report

Deliver the end-of-expedition technical report to the (place in Confluence specified by the) LO.
Please post a PDF export of it to jrso-developer on Slack.

2. Establish when the final database snapshot will be taken

Recapitulation of 0. Continue talking to the LOs, ALOs, EPM, MCS, and laboratory Technical Staff to clarify this timing.

• It takes 20 minutes to run a full database export (for 61 GiB of data)--but we want it to be as complete as possible within the constraints of expedition activities.
• The MCS routinely stage expedition content for convenience of copying via Science Office and User Room workstations. Timing of that activity is a common communication at the end of the expedition.

3. Spot check data copy efforts

Recapitulation of 0, 2. Be an additional set of eyes and ears.

...

Often there is both expedition-specific and individual variance. Much room for improvement in the current process.

4. Honor moratorium

Once content is uploaded to LIMS, and raw files have gone to data1, and routine backup cycles have occurred: expedition-specific data may (in-general) be cleaned off of instrument hosts and workstations.

...

There is precedent for this activity to be pushed to the (fresh) oncoming crew. Totally depending on timing of last core on deck and timing of arrival in port.

5. Conduct EOX database backup

6. Provide courier services

The backup tapes created by the MCS return to HQ as soon as possible. If your travel itinerary supports that goal, let them know you can provide courier services.

1. Notify everyone. Database snapshot in progress.

• Notify jr_developer and the shipboard technical staff that the EOX database backup is in progress.
• The database is available for reports, but content cannot be changed while this activity is in progress.

2. Make the database read only.

Connect to the BUILD box. Execute all of the following steps from that system.


Run PuTTY.
Connect to oracle@k1.ship.iodp.tamu.edu
From the prompt run this command, supply the oracle user's credentials for k1

...

Technical note. This command prevents write access to any table content that resides in the storage facility under the "labware" table space. In our database implementation, this happens to be all tables owned by the LIMS schema. Use of Drill Report ("ops" schema) is not affected. Aspects of DescLogik software configuration are also still open to maintenance, though use of DescLogik itself is locked out by this change.

3. Full snapshot as oracle@k1.

Run another PuTTY session.
Connect to oracle@k1.ship.iodp.tamu.edu
From the prompt run these commands--change the expedition and yourname  (will require logging in as a DBA User see PWSAFE) - - - JON Put Your Password in "QUOTES"

...

Statistics. Typical durations for the last step from previous expeditions. 344S: 16 min 23 sec. 345: 13 min 54 sec. 346: 18 min 46 sec. 341S: 11 min 42 sec. 351: 12 min 9 sec; 360: 16 min 57 sec; 363: 3 min 21 sec; 367: 3 min 38 sec.

ODA for 3 expeditions of data (11.1 GiB): 4 min 17 sec.
396: 6 min 54 sec

4. Restore database read/write capability.

From the prompt [oracle@k1 ~]$

...

Stop. Leave this window open for use below.

5. Compress the exports for transport. Cleanup. 

From the prompt [oracle@k1 ~]$
run these commands

...

Exp 396: we had trouble initially because we ran out of disk space.  This was apparently due to my creating the /backup/LIMSJR/dpdump folder under the Oracle account.  This broke some kind of link-up that gives the backup folder lots of additional drive space.  Don't do that.

Need to test DMPDP.
Need to post log results.

6. Notify everyone. Database snapshot process is complete.

 Notify jr_developer and expedition technical staff that the process is done.

...