Thursday, September 01, 2005

Disk sets in SVM

Using SVM disk sets even with single host (non-clustered) does makes sense for external connected storage. If you for some reason want to reinstall system or install new one but want to preserve all SVM made raids then disk sets make it really easy for you. Disk sets are really usefull if you want to move your external storage from one system to another. Below example what I did today - system was reinstalled but I wanted to preserve all SVM volumes on external JBOD. And if there's only one host using these disks then you probably want to set auto-take on.


bash-3.00# metaimport -r
Drives in regular diskset including disk c4t0d0:
c4t0d0
c4t1d0
c4t2d0
c4t3d0
c4t4d0
c4t5d0
c4t6d0
c4t7d0
c4t8d0
c4t9d0
c4t10d0
c2t16d0
c2t17d0
c2t18d0
c2t19d0
c2t20d0
c2t21d0
c2t22d0
c2t23d0
c2t24d0
c2t25d0
c2t26d0
More info:
metaimport -r -v c4t0d0
Import:
metaimport -s c4t0d0

bash-3.00# metaimport -s E3-0 c4t0d0
Drives in regular diskset including disk c4t0d0:
c4t0d0
c4t1d0
c4t2d0
c4t3d0
c4t4d0
c4t5d0
c4t6d0
c4t7d0
c4t8d0
c4t9d0
c4t10d0
c2t16d0
c2t17d0
c2t18d0
c2t19d0
c2t20d0
c2t21d0
c2t22d0
c2t23d0
c2t24d0
c2t25d0
c2t26d0
More info:
metaimport -r -v c4t0d0

Disk movement detected
Updating device names in Solaris Volume Manager
bash-3.00#
bash-3.00# metaset -s E3-0 -A enable
bash-3.00# metaset |head -5

Set name = E3-0, Set number = 1

Host Owner
bolek.db.srv Yes (auto)
bash-3.00#

No comments: