Professional Documents
Culture Documents
###IN CASE IT IS rootvg we need to also change system to boot from this disk at
startup
QA1CORE.medbank.local>/home/borj001> br
QA1CORE.medbank.local>/> lspv
hdisk0 000b789aa690db87 rootvg active
hdisk2 000b789ab2364266 datavg active
hdisk1 000b789adf295393 backupvg active
QA1CORE.medbank.local>/> cfgmgr
QA1CORE.medbank.local>/> lspv
hdisk0 000b789aa690db87 rootvg active
hdisk2 000b789ab2364266 datavg active
hdisk3 none None
hdisk1 000b789adf295393 backupvg active
QA1APP.medbank.local>/> lspv
hdisk5 000b789a61571467 datavg active
hdisk1 000b789adf29152d backupvg active
hdisk2 000b789ae2d2915b rootvg active
QA1APP.medbank.local>/> cfgmgr
lsQA1APP.medbank.local>/> lspv
hdisk5 000b789a61571467 datavg active
hdisk1 000b789adf29152d backupvg active
hdisk2 000b789ae2d2915b rootvg active
hdisk3 none None
QA1APP.medbank.local>/> lspv
hdisk5 000b789a61571467 datavg active
hdisk1 000b789adf29152d backupvg active
hdisk2 000b789ae2d2915b rootvg active
hdisk3 000b789ae36cc36f datavg active
###BEFORE removing old rootvg disk check if there is a sysdump volume. if this is
present this would not have been mirrored on new disk and needs to be moved
manually:
--------------------------------------------------------------------------------
####procedure to remove old disk same for rootvg or datavg as long as above
warnings for rootvg regards bootdisk and sysdump have been followed
QA1APP.medbank.local>/> lspv
hdisk5 000b789a61571467 datavg active
hdisk1 000b789adf29152d backupvg active
hdisk2 000b789ae2d2915b rootvg active
hdisk3 000b789ae36cc36f datavg active
QA1APP.medbank.local>/> lspv
hdisk1 000b789adf29152d backupvg active
hdisk2 000b789ae2d2915b rootvg active
hdisk3 000b789ae36cc36f datavg active