Hi all,
at a customer we have installed a AMS2300 virtualized behind a USPVM. Server is a P770 with 2 VIOs and 17 LPARs.
now we want to propose a HUS VM. Customer is not willing to do a host based Migration with LVM. So we discussed about virtualizing the USPVM/AMS2300 behind the HUS VM and
do the Migration with Tiered Storage Manager.
So far so good - sounds easy.
Now the customer asked about the Volumes in AIX. When we do all the virtualization and configuration Tasks on HUS VM, power down the P7, Change SAN Zones and start the P7 and do a cfgmgr
then all volumes will be seen over HUS VM, BUT they will be all new volumes ( new hdisk ) and the old ones will also be there.
Is there a way to do the cleanup( delete ) of the old volumes before power down the P7. What happens with all the volume groups ? does anyone know a document where these things are described.
Thanks for your help. Best regards, Volker
When I've done AIX UVM migrations I do the virtualization piece when the host is shutdown. Here's the process I've done in the past.
1. Shutdown AIX host
2. Update SAN Zoning
a) Remove Source array's WWPNs from host's zones in SAN fabrics.
b) Add Target array (HDS) into host's zones in SAN fabrics.
3. Update LUN Security
a) Add WWNs to host groups on HDS target array containing virtualized storage.
4. Boot AIX host
5. Integrate storage
a) Import volume groups
cfgmgr
lscfg
<query scsi bus via inquery tool to get listing of volumes>
b) Check storage is OK
lsdev -Cc disk
mount
6. Start application(s) or verify they are running
a) Verify apps are running OK
6. Migrate data
a) Prepare for AutoLUN migration using Raid Manager.
- horcm files with source svols and target pvols will need to be generated (can be done before migration)
- present both source and target volumes to CHiP ports
b) Execute migration
Via TSM ... use CmD Ste...
Via CLI
(start Raid Manager)
horcmstart.sh 100 101
export HORCC_MRCF=1
export HORCMINST=100
(initiate AutoLUN migration)
paircreate -g atexdb1 -d P3119-S2119 -m cc -vl
(view progress of migration)
pairdisplay -g atexdb1 -fcex
(once vols are in PSUS they are done, so disassociate pairing)
pairsplit -S -g atexdb1 -d P3119-S2119
(verify volumes are disassociated)
pairdisplay -g atexdb1 -fcex
7. Clean up source storage on HDS
a) Unmap source storage from dummy host group
b) Delete storage paths to external array groups
Fail-back Procedure
1) Shutdown system
2) Remove HDS target WWPN from host's SAN zoning
3) Add original source target WWPN into SAN zoning
4) Boot system
5) Import volume groups
6) Verify storage is OK and visible
7) Start application
1. Verify apps are running OK, if not... restore from backups