I posted a query RE exporting and importing LSM disk groups - original
posting at the end of this summary.
I received one reply from:
Davis, Alan [Davis_at_Tessco.Com]
I have included Alan's reply below. I should have put brain into gear
before putting fingers to keyboard - I realised after posting the query what
was happening. I deported the disk groups, without doing the 'voldisk rm'.
After the import a quick 'volume -g xxx startall' and all the volumes came
online beautifully.
======================Davis, Alan [Davis_at_Tessco.Com]====================
You are correct, the disk labels get reset on voldisk rm. The manual isn't
clear on this. You may either
save the labels individually, run sys_check and use the recovery data that
it stores, remove the disks before the voldisk rm, or just not use the
voldisk rm command.
In your case, where you will be restoring the same configuration after
rebuilding root, you don't have to rm the disks from LSM. Leave the LSM
information intact and just import them when you are done.
If you are re-arranging the disks during this process, then you will need to
either start from scratch and build all new LSM structures or import them as
they are and then re-arrange them as needed.
=====================original
posting===========================================
Please note what follows is being done on a test box prior to being done in
the live environment...
For reasons I wont go into, I need to rebuild /, and /usr on some of our
systems, primarily to increase the size of the root file system. These are
mirrored under LSM control with advfs file systems.
I am quite happy with the rebuild/restore mechanism for the os and can get a
rebuilt o/s in mirrored form back with no problems.
Data in 'user' lsm disk groups seems to present a problem though. I want to
be able to deport my user data before the rebuild, then import it after the
restore, with all data on those disk groups in place after the import
(obviously).
As a test, I unmounted all relevant file systems and did a 'voldg deport
diskgroupname' followed by a 'voldisk rm rz??' on each disk in the deported
disk group. At this point, the o/s stuff would be done.
After doing the restore of the o/s, the intention was to do a 'voldisk
define rz??' for each disk in the deported disk groups before attempting a
'voldg import diskgroupname' followed by a 'volrecover -g diskgroupname
-sb'. The only problem is that the 'voldisk rm' seems to totally 'zap' the
disk label so that the 'voldisk define' fails and you cant even start the
'voldg import' (this is all documented in 6.3.7 of the LSM manual under
Moving disks between systems).
Am I missing something here??
It just so happened that I did a 'volsave' before all of this so I did a
'volrestore -g diskgroupname', but then had to do a 'volume -g diskgroupname
init clean volname plexname' for each plex of each volume, followed by a
'volume -g diskgroupname start volumename'. This did recover the disk group
and all data was ok. However for systems with large lsm configurations
having to manually clean each plex of each volume prior to manually starting
it is a payne. Is there a better/easier way of doing this?
Your help is appreciated.
Regards - Tony
Received on Wed Aug 25 1999 - 10:25:19 NZST