Topic:
How to upgrade with minimum downtime and not have to copy the seismic data.

Description:
Upgraded from 10.2 but still have users working in 10.2 while projects are being
upgraded one at a time to Geoframe. The upgraded projects can share into the
same seismic, but the seismic is not duplicated and thus saves on disk
resources. Shares are not broken on the IESX 10.2 projects.

Solution:
- Master and cloned projects in 10.2 will be sharing the same seismic as the new
  master and upgraded clones in GeoFrame .
- Once seismic masters are upgraded, clones can be upgraded in batch
  after having been 'cleaned up'.

Risk factors:
Linking, unlinking and moving directories are the biggest risk factors.
- Scripting will mostly eliminate this
Leaving interpretation in seismic DSLs, which are not duplicated.
- Possible corruption in IESX and GF projects.

Rules:
- Any interpretation should be in the 'home' DSL or deleted - preferably
  deleted.
- Any interpretation in DSLs apart from the home DSL will potentially cause
  corruption.
- Larger volumes of interpretation can be copied to an 'interpretation'
  directory and duplicated.
- Any seismic in the 'home' DSL will be duplicated - not recommended. 
- All seismic should be in 'seismic only' DSLs.
- Any wells must be in the home DSL.
- Seismic data should be the only type of data existing outside the home 
  DSL, or dedicated interpretation DSLs.
- DO NOT delete IESX master or Upgraded GeoFrame project through the IESX
  or Project Manager interface. Deletion will need to be done manually and
  carefully.

Cleaning up:
- Create a copy of master project - assigning DSLs exactly as they are in the
  master.
- Clean up masters - check for interpretation, deleteing, moving problems
  (ie. sometimes some 'key' files get left behind when moving files).
- iesx_util #21 sometimes gives error when re-entering master.
- Create Share report for resharing in GeoFrame.
- Current report only gives project and survey, not class.

Procedure:
1. CHECK and clean up 'master' as above.
2. CREATE BLANK PROJECT:
   Create new project 'newmaster' to emulate 'master'. Using the same DSLs as
   'master', copy ONLY home DSL of 'master' to home DSL of 'newmaster'.
3. LINK THE DIRECTORY OF THE NEW PROJECT TO THE SEISMIC DIRECTORY OF THE
   ORIGINAL:
   For each DSL containing seismic in the master project,
   a. Remove newmaster directory
   b. Create links to original master
   eg. >rmdir newmaster
       >ln -s  master newmaster
4. FORCE THE SYNCHRONIZATION OF THE SEISMIC DATA IN THE LINKED DIRECTORIES:
   Run project_rename on 'newmaster'.
5. Prepare 'newmaster' for upgrade, as appropriate (ie. if it contains
   wells or interpretation).
6. UPGRADE 'newmaster' to GeoFrame.
7. CHANGE THE LINKS SO THAT THE DIRECTORIES ARE IN THE GEOFRAME PROJECT
   AND THE STANDALONE PROJECT IS THE ONE LINKING TO THE DIRECTORIES:
   a. Unlink  'NEWMASTER'
   b. Move directory 'master' to 'NEWMASTER'
   c. Link 'NEWMASTER' to master.
   eg. >unlink NEWMASTER
       >mv master NEWMASTER
       >ln -s NEWMASTER master



Last Modified on: 07-NOV-00