![]() init 0Ĭreate an OBP alias for the bootable disks. ![]() cp /etc/vfstab /etc/vfstab.tmp cat /etc/vfstab.tmp | \ sed s,/dev/dsk/c0t0d0s1,/dev/md/dsk/d1, | \ sed s,/dev/dsk/c0t0d0s3,/dev/md/dsk/d3, | \ sed s,/dev/rdsk/c0t0d0s3,/dev/md/rdsk/d3, > /etc/vfstabĭocument the physical device name of the two disks in the mirror, as shown inthe underlined portion of the following example for the disk c0t1d0. Replace the remaining partitions with volumes in /etc/vfstab, asfollows. Make the system boot from the mirror, as follows. metainit -f d10 1 1 c0t0d0s0metainit -f d11 1 1 c0t0d0s1metainit -f d13 1 1 c0t0d0s3 metainit d20 1 1 c0t1d0s0metainit d21 1 1 c0t1d0s1metainit d23 1 1 c0t1d0s3metainit d0 -m d10metainit d1 -m d11metainit d3 -m d13 prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c0t1d0s2Ĭreate the state database replicas as described in the previous runbook.Ĭreate the volumes, as follows. It is not necessary to make this diskbootable because the bootblock from the first submirror is copied to the secondsubmirror during the resync operation. (Do notcreate unnecessary multiple copies per disk.) metadb -a -f c0t0d0s7metadb -a c0t1d0s7metadb -a c0t2d0s7 Runbook for the Two-Disk ConfigurationĬopy the VTOC to the mirror disk. ![]() Replica creation for the three-disk and four-disk configuration. metadb -a -f -c 2 c0t0d0s7 metadb -a -c 2 c0t1d0s7 echo set md:mirrored_root_flag=1 > /etc/system Replica creation for the two-disk configuration (and disabling the quorumrule). In this runbook, we assume that only the systemdisks are under control of Solaris Volume Manager software, and this idealreplica configuration is not always possible.īe aware that the optimal replica configuration may be different from the onepresented here, in the case that the data disks are also under control ofSolaris Volume Manager software and can contain state database replicas. Ideally, three replicas are created, each on a different disk, connected to adifferent host bus adapter. The system administrator must remove broken replicas in single-usermode to restore the majority. The system does not boot unless more than half of the replicas areavailable. The system panics when more than half of the replicas break. Solaris Volume Manager software has the following behavior with respect toloss of replicas: Providing more thanone replica protects the configuration against losing the definition of thevolumes. In mostcases, the logical disk names will be different.Īs a first step for each of the presented configurations, the Solaris VolumeManager software state database replicas must be created. These names are placeholders for the real disk names. In runbooks, the following disk names are assumed. Learn More Buy Runbook for Creating the Solaris Volume Manager Software State Database Boot Disk Management: A Guide for the Solaris Operating Environment
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |