| 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 |
I have just been asked to get involved at a Customer site to do a migration from a uVAX 3900 to a VAX 4400. The system is running VMS V5.1-1 and ALL-IN-1 version 2.3. I am trying to decide if it would not be better to just install VMS V5.5-2 and ALL-IN-1 V3.0 on the new system and just move over the ALL-IN-1 users and data from the 3900. ALL-IN-1 V2.3 is not customized at all, other than the Shared File cabinet assett that has been installed. It also has Wordperfect integration. There is no message router installed. Does this sound like a easy task, or should I just go through and upgrade VMS and ALL-IN-1 and then move the disks? If I were to install a new V3.0 on the 4400, is it very complicated to move the ALL-IN-1 users from the 2.3 system to the 3.0 system? I know that I will have to convert the user profile. Don't know what will happen with the previous shared file cabinet asset, now that it is standard with V3.0. If anyone can advise on what would be the best path to take, and what problems I may run into, what may need conversion, etc. I would be most appreciative. The customer cannot afford a lot of down time. Thanks in advance.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2679.1 | Here's my free advice | GANTRY::HULL | Digital Services Delivery - Motown | Fri May 07 1993 16:21 | 14 |
Personally, I would back up the V2.3 system and restore "as is" on the VAX 4400, and then do an Upgrade to V3.0. There are many file conversions that take place, as well as things like seeding the partition file, etc. Its really a lot simpler to just let the installation procedure do all this. There is also a shared file cabinet migration script or conversion somewhere in there that will take you from the ASSETS style to the new base-code stuff.I would expect the system to be down for at least 2 days, maybe 3 considering all that is involved. Do you also have the correct V3.0-compatible WP upgrade to also add on after V3.0 is installed? That's more time, too. IMHO, Al | |||||
| 2679.2 | Be sfae not sorry | AIMTEC::WICKS_A | on the Streets of San Francisco | Fri May 07 1993 17:50 | 10 |
I go with Al!
A fresh install wouldn't buy you a lot particularly with the SFCP
stuff on the system - the Upgrade installation code does things a lot
better and a lot safer then trying to save time by doing a fresh
install.
Regards,
Andrew.D.Wicks
| |||||
| 2679.3 | I will go with the upgrade. | KAOT01::J_PLUGERS | Too poor to pay attention | Mon May 10 1993 18:14 | 14 |
Thanks for the feedback.
I will do an upgrade instead of a new install/merge. I plan on
upgrading VMS V5.1-1 to V5.5-2 in order to support the VAX 4400. Once
the dust settles, I will begin planning the ALL-IN-1 V2.3 to V3.0
upgrade.
Does anyone know of any problems running ALL-IN-1 Version 2.3 under VMS
V5.5-2?
Thanks again,
John Plugers
Digital MCS
Toronto
| |||||