Solaris Volume Manager -6 [Volume Rename]

                           

                   SVM-6

What we will learn in next Few Pages

·         Renaming Volumes

Currently we have this situation,

root@sol-test-1:>/#metastat -c

d5               m  2.3GB d41 d42

    d41          s  2.3GB c1t0d0s4

    d42          s  2.3GB c1t1d0s4

d4               m  1.0GB d31 d32

    d31          s  1.0GB c1t0d0s3

    d32          s  1.0GB c1t1d0s3

d3               m  1.0GB d21 d22

    d21          s  1.0GB c1t0d0s1

    d22          s  1.0GB c1t1d0s1

d2               m  7.3GB d11 d12

    d11          s  7.3GB c1t0d0s0

    d12          s  7.3GB c1t1d0s0

Solaris Volume Manager -5 [Hot Spare Pool / Hot Spare]

                     

                           SVM-5

What we will learn in next Few Pages

·         HOT SPARE

SO, what is Hot Spare?

Allows automatic replacement of failed submirrors / Raid-5 components, provided space components are available & reserved

HOT SPARE STATES:

3 states

A. available

B. in-use

C. broken

a.  Available:

Available hotspares are running and ready to accept data, but are not currently being written to or read from.

Solaris Volume Manager -4 [raid 5]

                     

                           SVM-4

What we will learn in next Few Pages

·         Raid5

(Plz watch the videos from this blog for better understanding of raid levels)

OK… Let’s create raid 5 with SVM,

Should we use Soft Partitions for SVM or we need to go with Physical slices?

Well… we can go in both ways, let’s see with SP’s

Create Metadb

root@sol-test-2:>/# metadb -afc 3 c1t0d0s7 c1t1d0s7

Solaris Volume Manager -3 [replacement of failed disk]

                     

                           SVM-3

What we will learn in next Few Pages

·         Replace failed disk in SVM

We will start from the last post, where we left everything messed

root@sol-test-1:>/# metastat -c

d5               m  2.3GB d41 (maint) d42

    d41          s  2.3GB c1t0d0s4 (maint)

    d42          s  2.3GB c1t1d0s4

d4               m  1.0GB d31 (maint) d32

    d31          s  1.0GB c1t0d0s3 (maint)

    d32          s  1.0GB c1t1d0s3

d3               m  1.0GB d21 (maint) d22

    d21          s  1.0GB c1t0d0s1 (maint)

    d22          s  1.0GB c1t1d0s1

d2               m  7.3GB d11 (maint) d12

    d11          s  7.3GB c1t0d0s0 (maint)

    d12          s  7.3GB c1t1d0s0

Solaris Volume Manager -2 (ROOT MIRRORING)

                                                       

                                                                        SVM-2

What we will learn in Next Few Pages,

·         Root Disk mirroring

Well we tried some of svm in our first part, but I think that in last few pages due to taking soft partitions with mirroring, it might be confusing.

So here we will start with fresh,

For Root Mirroring we should consider few things in mind,

·         Always take the bkp of /etc/system & /etc/vfstab before root mirror

·         First run the prtvtoc|fmthard, then go for creating metadb

·         Svm will do changes for / only in /etc/vfstab, do remember to change others manually

***better free at least 20-25gb in the drive where u had created your VM

I attached one disk of same size via VM settings.

Then

We have 2 disks c1t0d0s2 & c1t1d0s2 of same size but with different layout,

Veritas Volume Manager -11 [root disk (ufs) encapsulation in to vxvm]

               VXVM-11 [Encapsulation-root disk]

What we will learn in Next Few Pages,

·         How to encapsulate root disk with VXVM

root@pr-01:>/# vxdiskadm

Volume Manager Support Operations

Menu: VolumeManager/Disk

 1      Add or initialize one or more disks

 2      Encapsulate one or more disks

 3      Remove a disk

 4      Remove a disk for replacement

==========removed=============

23     Dynamic Reconfiguration Operations

 list   List disk information

Veritas Volume Manager -10 [manual creation of concat & stripe mirror]

      VXVM-10 (Manual)

What we will learn in Next Few Pages,

·         Layered Volume via vxmake

·         Concat-mirror / stripe-mirror

We need

4 Subdisks

4 Plexes – 1 SD for each plex

2 volumes – 2 plexes for each volume

Did u visualize the diagram?

DG,

Veritas Volume Manager -9 [manual creation of concat/stripe volumes]

     VXVM-9 (Manual)

What we will learn in Next Few Pages,

·         Manually create Concat Volume using vxmake

·         Manually create STRIPE Volume using vxmake

Well, njoyed till creating Dg’s/ Volume’s and the different layouts.

Ever thought who made the Subdisks & Plexes for us?

NO?

Never Mind… I also never thought about it. But there is also a unusual way to create all these,

Let’s have a try…

Steps to Follow,

1.  Initialize disk

2.  Create Dg

3.  Assign disk under Dg

4.  Create subdisks

5.  Create Plexes

6.  Associate plexes with subdisks [actually it is not necessary /skip this]

7.  Create volume

8.  Start volume

9.  Create FS on volume

10. Mount the FS

Veritas Volume Manager -8 [ volume disk removal]

                                      

                    VXVM-8 (Volume –Disk Removal)

What we will learn in Next Few Pages,

·         Online remove disks from volume

Well, I have a volume of 3g and used only 200mb, and I know that it is not going to cross 400-500m ever.

So want to remove some disks and use somewhere else.

root@pr-01:>/# df -kh /test-vol/

Filesystem             size   used  avail capacity  Mounted on

/dev/vx/dsk/mydg/myvol-1

                       2.7G   119M   2.4G     5%    /test-vol