Re: Server migration - Shark specific

From: Chris Leven (Chris.Leven@GARLOCK.COM)
Date: Mon Mar 01 2004 - 15:40:26 EST


I have done it several times and that scenario works fine every time.

Christopher Leven
Senior Programmer/Analyst
IBM Certified Specialist AIX Administration
IBM Certified Specialist AIX Support
IBM Certified Specialist PSSP

Garlock Sealing Technologies
An EnPro Industries Company
1666 Division St
Palmyra, NY 14522
P 315-597-3034
F 315-597-7250
C 585-704-0107
Chris.leven@garlock.com

-----Original Message-----
From: jeff barratt-mccartney [mailto:jbarratt@COMPSAT.COM]
Sent: Monday, March 01, 2004 2:46 PM
To: aix-l@Princeton.EDU
Subject: Re: Server migration - Shark specific

no problems. that's how I do it.

a sysback/restore of rootvg will make it seamless, but sometimes it's best
to do fresh installs.

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
Bill Verzal
Sent: Monday, March 01, 2004 2:28 PM
To: aix-l@Princeton.EDU
Subject: Server migration - Shark specific

Hi *,

I was just given a directive to take a F80 and move it to a
faster/newer/better 6F1. They're both 5.2.

I'll probably clone the F80 onto the 6F1 just to be safe.

My question here relates to the Shark LUN's. I'm thinking I'll just create
another connection on the Shark (I'm not in a SAN), share the LUNs onto the
new connection, then varyoff the old VG and varyon/import the VG on the
6F1.

Anyone see any issues with this ?

BV
--------------------------------------------------------

"If everything is coming your way, then you are in the wrong lane"

Bill Verzal
AIX Administrator, Komatsu America
(847) 970-3726 - direct
(847) 970-4184 - fax

----------Legal Disclaimer----------
The information contained in this message may be privileged and confidential, and is intended solely for the use of the named addressee. No other person is authorized to access, copy or re-use this message (or any information contained herein). If you are not the intended recipient, please notify us immediately by replying to this message and delete it from your computer.



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:39 EDT