Re: [Veritas-vx] QUESTIONS : Veritas Volume Manager from 3.5 to 5.0 data migration in Solaris 8/10
Hi, VxSF 5.0 supports DG versions 20-140. You don't need to upgrade and the below procedure should work. And yes as posted earlier by Mike, do make full backups of what you're going to be migrating. You might want to upgrade to a later version of DG once old server's out of the picture. On 1/21/08, Bill Mackler <[EMAIL PROTECTED]> wrote: > Hi, > > > Our current server "stanley" is running Solaris 8 and Veritas > Foundation Suite for Oracle (VxVM/VxFS) 3.5-mp3. All the disk groups > in the associated storage has version 90 as below : > > > "stanley" will be replaced by a new server with the same name running > Solaris 10 and Veritas Storage Foundation 5.0-mp1. Our plan is to > attach all existing disk groups (version 90) from "stanley" to the new > replacement server with Solaris 10 and latest Veritas Storage > Foundation 5.0-mp1. Please advise me the procedure to disconnect all > existing disk groups from the "stanley" and reconnect them to new > replacement without going thru the upgrade of existing disk groups of > version 90. Our goal is to run Veritas 5.0 in the new "stanley" > while accessing all original version 90 data in the disk group > hds9585dg. We plan to just perform the steps -> 1.#deport hds9585dg > 2. physical SAN disconnection of "stanley" and reconnection to new > replacement server 3. #import hds9585dgPlease let us know if they > are correct and if there is anything we are missing. > > > Also, say we need to fall back to the old "stanely" serer running > 3.5. Is it possible to reverse the above steps after physically > switch the SAN connection and deport/import from "version 90 disk > group in Veritas 5.0" to "version 90 disk group in Veritas 3.5" ? I > want to make sure that there's no issue performing the steps in > reverse. > > > Thanks for your assistance, Bill > > > stanley# vxdg list hds9585dg > Group: hds9585dg > dgid: 1097031500.6964.stanley > import-id: 0.11605 > flags: > version: 90 > detach-policy: global > copies:nconfig=default nlog=default > config:seqno=0.2252 permlen=28130 free=27921 templen=132 > loglen=4262 > : > : > > > stanley# pkginfo -l VRTSvxvm > PKGINST: VRTSvxvm > NAME: VERITAS Volume Manager, Binaries > CATEGORY: system > ARCH: sparc > VERSION: 3.5,REV=06.21.2002.23.14 > > ___ > Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > > -- _/ sengork.blogspot.com / ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] QUESTIONS : Veritas Volume Manager from 3.5 to 5.0 data migration in Solaris 8/10
This procedure should work without any problems and you should be able to move back to 3.5 as long as you don't upgrade the volume group version. And of course you left out step 0 because we know it's required: 0. Take a full backup of "stanley". Just in case. Cheers, - Mike.Myers nwdc.net > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Bill Mackler > Sent: Sunday, January 20, 2008 1:41 PM > To: veritas-vx@mailman.eng.auburn.edu > Subject: [Veritas-vx] QUESTIONS : Veritas Volume Manager from > 3.5 to 5.0 data migration in Solaris 8/10 > > Hi, > > > Our current server "stanley" is running Solaris 8 and Veritas > Foundation Suite for Oracle (VxVM/VxFS) 3.5-mp3. All the disk groups > in the associated storage has version 90 as below : > > > "stanley" will be replaced by a new server with the same name running > Solaris 10 and Veritas Storage Foundation 5.0-mp1. Our plan is to > attach all existing disk groups (version 90) from "stanley" > to the new > replacement server with Solaris 10 and latest Veritas Storage > Foundation 5.0-mp1. Please advise me the procedure to disconnect all > existing disk groups from the "stanley" and reconnect them to new > replacement without going thru the upgrade of existing disk groups of > version 90. Our goal is to run Veritas 5.0 in the new "stanley" > while accessing all original version 90 data in the disk group > hds9585dg. We plan to just perform the steps -> 1.#deport hds9585dg > 2. physical SAN disconnection of "stanley" and reconnection to new > replacement server 3. #import hds9585dgPlease let us know if they > are correct and if there is anything we are missing. > > > Also, say we need to fall back to the old "stanely" serer running > 3.5. Is it possible to reverse the above steps after physically > switch the SAN connection and deport/import from "version 90 disk > group in Veritas 5.0" to "version 90 disk group in Veritas 3.5" ? I > want to make sure that there's no issue performing the steps in > reverse. > > > Thanks for your assistance, Bill > > > stanley# vxdg list hds9585dg > Group: hds9585dg > dgid: 1097031500.6964.stanley > import-id: 0.11605 > flags: > version: 90 > detach-policy: global > copies:nconfig=default nlog=default > config:seqno=0.2252 permlen=28130 free=27921 templen=132 > loglen=4262 > : > : > > > stanley# pkginfo -l VRTSvxvm > PKGINST: VRTSvxvm > NAME: VERITAS Volume Manager, Binaries > CATEGORY: system > ARCH: sparc > VERSION: 3.5,REV=06.21.2002.23.14 > > > ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
[Veritas-vx] QUESTIONS : Veritas Volume Manager from 3.5 to 5.0 data migration in Solaris 8/10
Hi, Our current server "stanley" is running Solaris 8 and Veritas Foundation Suite for Oracle (VxVM/VxFS) 3.5-mp3. All the disk groups in the associated storage has version 90 as below : "stanley" will be replaced by a new server with the same name running Solaris 10 and Veritas Storage Foundation 5.0-mp1. Our plan is to attach all existing disk groups (version 90) from "stanley" to the new replacement server with Solaris 10 and latest Veritas Storage Foundation 5.0-mp1. Please advise me the procedure to disconnect all existing disk groups from the "stanley" and reconnect them to new replacement without going thru the upgrade of existing disk groups of version 90. Our goal is to run Veritas 5.0 in the new "stanley" while accessing all original version 90 data in the disk group hds9585dg. We plan to just perform the steps -> 1.#deport hds9585dg 2. physical SAN disconnection of "stanley" and reconnection to new replacement server 3. #import hds9585dgPlease let us know if they are correct and if there is anything we are missing. Also, say we need to fall back to the old "stanely" serer running 3.5. Is it possible to reverse the above steps after physically switch the SAN connection and deport/import from "version 90 disk group in Veritas 5.0" to "version 90 disk group in Veritas 3.5" ? I want to make sure that there's no issue performing the steps in reverse. Thanks for your assistance, Bill stanley# vxdg list hds9585dg Group: hds9585dg dgid: 1097031500.6964.stanley import-id: 0.11605 flags: version: 90 detach-policy: global copies:nconfig=default nlog=default config:seqno=0.2252 permlen=28130 free=27921 templen=132 loglen=4262 : : stanley# pkginfo -l VRTSvxvm PKGINST: VRTSvxvm NAME: VERITAS Volume Manager, Binaries CATEGORY: system ARCH: sparc VERSION: 3.5,REV=06.21.2002.23.14 ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
