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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3433.0. "How to move existing MCC-environment to new platform" by BACHUS::FOLENS () Mon Jul 27 1992 09:06

    I want to move an MCC v1.1 environment from a Vaxstation 3100 to a
    Vaxstation 4000 and keep all info regarding alarms, historian ,etc.
    What is the best way to transfer the existing mcc-system to preserve the
    configuration. Any drawbacks or pitfalls ?
    I already found some note entry's from people who tried this, but 
    nobody explained which steps they followed.
    
    -Geert-
T.RTitleUserPersonal
Name		DateLines
3433.1re .0ANOSWS::COMFORTSpent a little time on the hillMon Jul 27 1992 17:5219
    
    Are you changing MCC versions and/or VMS versions?
    
    I migrated MCC V1.1 from a 3100 VMS 5.4-3 to a 4000 VMS 5.5.  I
    installed the 4000 system from scratch, including all of MCC.  I
    then copied all the files that were different (this covers the MIR
    etc.) from one system to the other.  The RDB database from the exporter
    needed an RMU backup/restore (with the nocdd option), especially
    if going between RDB versions.  The biggest gotcha was with an RDB
    4.0A bug and accessing the database from a remote system (this required
    a process level logical in sylogin.com, if it is needed I can look
    it up).  As noted in the other recent note about this (3432), I
    did not have a DNS server running on the MCC station, which made
    things simpler.  No real showstoppers, and given we were doing this
    on a production system with a two hour time limit, everything went
    smoothly.
    
    Dave
3433.2The migration is the same.BACHUS::FOLENSTue Jul 28 1992 03:4810
    
    Indeed, I'm in the same situation as you were concerning the migration.
    I'm not using the RDB-database yet, so this will not give me problems.
    If I understand it right, I need to copy all the '.dat'-files from the
    mcc_common directory, all the map-files, and the resource-file to create
    the same environment? Will a change of node name/number cause me any
    problems?
    
    -Geert-
3433.3Good luck!ANOSWS::COMFORTSpent a little time on the hillTue Jul 28 1992 14:1712
    
    Geert -
    
    The only thing I can say to the node name/number issue is that my
    migration went to the target system, which had a different node
    name and I tested everything there.  It worked just fine.  However
    for production purposes, the node name got switched back, so the
    new hardware is operating with the old soft name/address.  Sounds
    like it should go ok.  Godd luck.
    
    Dave