How to Mirror Boot Disk in SVM on Solaris X86

Written by mark pool
  • Share
  • Tweet
  • Share
  • Email

The Solaris Boot disk contains all the operating system files required to start and run the system. This is also known as the "root" file system. A disk mirror consists of two disks with identical data that are seen as one by the operating system. The advantage is that if one disk fails, the other one continues to function and provide access to critical files. Since the root file system is on the Boot disk, it's important to enter commands exactly to create a mirror and maintain system stability.

Skill level:
Moderately Easy

Other People Are Reading

Instructions

  1. 1

    Turn off the system and install the second hard drive. Make sure the hard drive is equal to or larger than the root disk being mirrored or the mirror will not work.

  2. 2

    Start Solaris and log in as an administrator.

  3. 3

    Type the following command to copy the partition table to the new disk:

    prtvtoc /dev/rdsk/c3t2d0s2 | fmthard -s - /dev/rdsk/c3t3d0s2

  4. 4

    Type the following command to copy the metadata used by the Solaris Volume Manager (SVM):

    metadb -a -c 3 -f c3t2d0s7 c3t3d0s7

  5. 5

    Type the following command to initialise the first disk:

    metainit -f d11 1 1 c3t2d0s0

  6. 6

    Type the following command to initialise the second disk:

    metainit -f d12 1 1 c3t3d0s0

  7. 7

    Type the following command to create the mirror:

    metainit d10 -m d11

  8. 8

    Type the following command to update the system for the first half of the mirror:

    metaroot d10

  9. 9

    Restart the system, then type the following command to update the configuration for the second drive:

    metattach d10 d12

Don't Miss

Filter:
  • All types
  • Articles
  • Slideshows
  • Videos
Sort:
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the eHow.co.uk site, you consent to the use of cookies. For more information, please see our Cookie policy.