Conference decwet::advfs_support

1024.0. "Move ADVFS FS from 3.X to 4.X" by MANM01::JOMARMEJIA () Thu Mar 20 1997 20:20

    Hi ,
    
    Could somebody confirm if it is OK to move ADVFS file systems from
    DU V3.2C to V3.2G ; or DU V3.2C to DU v4.0B ?
    
    We have a client who want to upgrade their AS2100 running DU V3.2C to
    AS4100 running DU V3.2G (or possibly DU v4.0B); ORACLE 7.2.X.X. The
    AS2100 has one big ADVFS file domain (one 8 GB and one 28 GB -
    addvol'ed in DU V3.2C) and this domain is being used by an ORACLE
    application. To make the migration to AS4100 faster , we're
    contemplating on just moving the disks over (to AS4100), create the
    device files, and link them to an ADVFS domain and then mount it. 
    The OS on the AS4100 will either be DU V3.2G or DU V4.0B. 
    
    Is this a "healthy" solution ? We don't see any problem in this but
    we need a confirmation that this will work well.
    
    Any advice is highly appreciated.
    
    Regards,
    
    Jomar Mejia
    MCS Manila
                                                           

Hello.  There should be no problem.  There is no forward compatibility issue 
here.

Thanks,
Janice
[Posted by WWW Notes gateway]

The only on-disk AdvFS structure change I know of is from v2.0 -> v3.0.  All
v3.2x and v4.0x versions can have AdvFS domains transferred freely among them.

I expect you know all this already, but just in case:

	1)  Back up the data before moving it.  Just in case something goes 	
		wrong.

	2)  If you're physically moving disks around, make sure you know all
		of the volumes of the domain, and put all the links in with
		'ln -s /dev/XX /etc/fdmns/dmn_name/'.  Using addvol or mkfdmn
		*will* delete your data.

--Ken

    Hi,
    
    Thanks for the confirmation. 
    
    Regards,
    
    Jomar Mejia