[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2898.0. "Opinion on Upgrade to V3.0 wanted" by BACHUS::BHP144::Laroche (Veerle Laroche) Tue Jun 22 1993 13:44

Hello,


I would like to have someone's opinion on the following situation.

A customer has two systems, Microvax 3400, running ALL-IN-1.  One is version 
2.3 and the other 2.4.

One of the systems will be upgraded to a 4000 series.

After this, I do the upgrade of ALL-IN-1 V2.4 to V3.0.  This system will be 
used to test the documents of the 2.3 system, especially printing.
The 2.3 system has DECpage installed.


When testing is done, there are several options ;

1) The customer keeps his two systems separated.  So I upgrade 2.3 to 3.0   
   and that's it.
2) Since one Microvax will become a 4000 series, the customer might consider
   transferring the users, documents and shared areas to the 3.0 system.
   This due to reduced ALL-IN-1 system management and resources that would 
   become available on the Microvax 3400 left.

	Here I would like to have feedback.

	- Do I upgrade the 2.3 to 3.0 and then transfer everything ?

		I believe in this case I can merge the two profiles, but 
		what about the shared areas, partition, ... ?

	- Can I transfer users, documents, .... to the 3.0 system ?

		In this case I would have to create the users in the profile 
		and then copy their files over ?  
		

What would you do in this case ?


Thanks for any info,


Veerle Laroche - Digital Services Brussels
T.RTitleUserPersonal
Name		DateLines
2898.1A laborous job this will be!BIS1::DESTRIJCKERBack again to the home townTue Jun 22 1993 14:4318
    Hi Veerle,
    
    Have you got access to Tony Redmond's bible called ALL-IN-1 A Technical
    Odyssey? This book contains a wealth of information about things like
    merging ALL-IN-1 systems.
    
    A few things to definately remember are: 
    - merge ALL-IN-1 systems of the same version, then at least all data 
    	files will have the same version. (cuts down on file conversion time)
    - prepare the merge in great detail, then the success rate will be
    	higher and the actual merge will be quicker.
    
    You may always contact me outside this notes file for further
    assistance.
    
    Regards,
    
    Wivine.
2898.2Bible? SIOG::T_REDMONDThoughts of an Idle MindTue Jun 22 1993 20:486
    Merge before the upgrade.  It's simpler that way because you have less
    files to deal with, and the whole tacky aspect of ACLs, identifiers
    (including groups), and shared drawers can be safely left until after
    you upgrade the merged system.
    
    FWIW, Tony
2898.3Customer wants to test 3.0BACHUS::BHP144::LarocheVeerle LarocheWed Jun 23 1993 15:3213
Tony,


Do you mean merging the 2.3 and 2.4 system and then upgrade ?

This is not possible I'm afraid, the customer really wants to test
their documents before upgrading / moving the 2.3 system.


Thanks,


Veerle
2898.4If you insist on merging after V3.0MAULS::REDMONDThoughts of an Idle MindThu Jun 24 1993 14:4320
Yes, I mean to merge the two pre V3.0 systems before upgrading.  I've managed 
to do this successfully a number of times, but I haven't yet tried to merge 
two V3.0 systems.  The move towards VMS security structures and the 
introduction of shared drawers in V3.0 means that everything becomes more 
complex.  If the customer insists on moving to V3.0 first then I would 
recommend that they:

-- Don't use Groups
-- Don't use Set Mail User
-- Don't use Shared Drawers

until after the two V3.0 systems are merged together.  You can then start to 
use the functionality listed above, and things should be OK because you won't 
have had to deal with merged ACLs, rights, etc.  I wouldn't attempt to merge 
two PARTITION.DATs (if you only have MAIN drawers). Instead, I would recreate 
PARTITION.DAT and reseed it using the scripts provided with V3.0.  The same 
goes for the FCS -- recreate it on each node in the merged system (cluster), 
remembering to tune the settings for the new (merged) load.

Tony