Conference iosg::all-in-1_v30

2500.0. "V3.0 UPGRADE/SANITY CHECK REQ'D" by LARVAE::COLLINS_J () Tue Mar 30 1993 22:34

    My customer currently runs a customised version of ALL-IN-1 V2.4 on an 
    8530 machine. However, customisations are minimal and there are no 
    layered products, Business apps etc. There are 186 user profiles (40 
    concurrent users ) on the system, 20 of these users are 'heavy users' 
    (no. of documents range from 200-3000). system used mainly for Word 
    Processing and Mail. Both machine and ALL-IN-1 to be upgraded. Machine to 
    a 3100-90 and ALL-IN-1 to V3.0. Disk space and Disk i/o is not currently 
    causing any problems. The new target machines will have an extra disk and 
    also a spare.
    
    In making our recommendations we are to take the following 
    requirements/objectives into consideration:- 
    
    - Disruption to the users and to IT, including any downtime, must be kept 
      to a minimum. 
    - A clean system must be obtained prior to upgrading.
    - housekeeping tasks identified for continued maintenance of the system. 
    - disk structure should be planned for future growth
    
    we agreed that 2 options (out of a possible 3) should be considered ,both 
    of which, I'm sure you'll agree, have their pros & cons 
         
    1.	 Use disk image backup and restore - to move ALL-IN-1 V2.4, in its 
         current state to new target system, clean up ALL-IN-1 and then 
         upgrade to V3.0
    
    2.	 Build new target system and transfer ALL-IN-1 users manually
    
        (Option 3 was Clean up ALL-IN-1 V2.4 on existing system, upgrade to 
         V3.0 and then move to new target system.)

I am proposing to recommend option 1. on the basis that the upgrade 
and any necessary housekeeping procedures (TRM e.g.) will utilize the 
faster processor keeping downtime to a minimum. All usernames, 
passwords and configuration information is preserved and in particular 
that the shared mail directories remain, thereby optimising disk space 
and obtaining a clean system from the start. 
 
Constraints are:

1. Time, in particular down time (for h/keeping and upgrade)

2. because, effectively we're going for the "big bang" approach the 
system will not be tested and evaluated.  

To date, I have had very little experience (although I'm having to 
learn fast!) in upgrading ALL-IN-1 to V3.0 so any feedback or comments 
would be appreciated before I make this proposal to the customer.

Thanks for your help/advice/comments in advance 

regards
Joan

    Joan,
    
    this appears to be the same sort of question asked in note 2496.0
    only a few hours ago. Have you called your local CSC for
    advice/recommendations?
    
    regards,
    
    Andrew.D.Wicks

    Hi Joan,
    
    >1.	 Use disk image backup and restore - to move ALL-IN-1 V2.4, in its 
    >     current state to new target system, clean up ALL-IN-1 and then 
    >     upgrade to V3.0
    
    I don't like this at all, assuming that you are just copying over the
    ALL-IN-1 disk and the new system has never had ALL-IN-1 version 2.4
    installed.  I say this because SYS$LIBRARY has a number of shared
    images etc. that the ALL-IN-1 installation put's in there, for example
    the emulation of EDT the .EXE resides there.
    
    The plan has a number of holes and you could find yourself in hot
    water.  All customers want to have minimum downtime BUT do not want to
    invest in doing things properly.  There is a good topic in here that
    talked about cutting the installation time by half using the
    Alternative working directory option AWD=<ALL-IN-1 disk>:[whatever]. I
    would suggest that a rethink would of your plan, I am sure would save
    you heaps of time in putting things right.
    
    Regards,
    
    Sunil