Solaris

ignore my last post

# Setup the second disk (c1t1d0s2) to be identical as the primary (c1t0d0s2)
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2

# This creates the metadatabase - you need a free slice with 100mb, we use slice 7
metadb -a -f -c 3 c1t0d0s7
metadb -a -c 3 c1t1d0s7

# Setup Volumes on the primary for /, /var and swap
metainit -f d10 1 1 c1t0d0s0
metainit -f d11 1 1 c1t0d0s1
metainit -f d13 1 1 c1t0d0s3

# Setup Volumes on the secondary for /, /var and swap
metainit d20 1 1 c1t1d0s0
metainit d21 1 1 c1t1d0s1
metainit d23 1 1 c1t1d0s3

# Setup the mirrors
metainit d0 -m d10
metainit d1 -m d11
metainit d3 -m d13

# Make a backup of /etc/vfstab
cp /etc/vfstab /etc/vfstab.orig

# Make the boot disk boot from the mirror (this will modify the /etc/vfstab)
metaroot d0

# add entries for swap and var to /etc/vfstab ( make sure you rem out the old devices)
# Below is what the /etc/vfstab should look like
==================================================================================================
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
#/dev/dsk/c1t0d0s1 - - swap - no -
#/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
#/dev/dsk/c1t0d0s3 /dev/rdsk/c1t0d0s3 /var ufs 1 no -
/dev/md/dsk/d1 - - swap - no -
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no -
/dev/md/dsk/d3 /dev/md/rdsk/d3 /var ufs 1 no -
swap - /tmp tmpfs - yes -
===================================================================================================

# Run lockfs to clear and flush all data that is dirty.
lockfs -fa

# Halt system (you will now boot off the metadevices)
init 6

# Attach the submirrors
metattach d0 d20
metattach d1 d21
metattach d3 d23

metastat to check the status

Hi Maddhadder71,

# Setup the second disk (c1t1d0s2) to be identical as the primary (c1t0d0s2)
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2

For the above command, why do you make only slice 2 of the second and primary identical and not other slices?

---------------------------------------------------------------------
# This creates the metadatabase - you need a free slice with 100mb, we use slice 7
metadb -a -f -c 3 c1t0d0s7
metadb -a -c 3 c1t1d0s7

What and Why metadatabase is setup on slice 7?

---------------------------------------------------------------------

# Attach the submirrors
metattach d0 d20
metattach d1 d21
metattach d3 d23

By attaching the two slices of the two drive what does this do?

Slice 2 is the entire disk including all other slices.

The metadatabase describes the setup. We need several copies to survive the loss of a disk. Slice 7 is something of a standard, just like root being slice 0 and swap being slice 1. Slice 2 must be the whole disk, other than that, we could use non-standard slices if we really wanted to. But standards are good.

Attaching a second slice makes it a mirror. The data is written to both slices. Reads can be satified from either slice. And if one slice dies, the data is still available from the remaining slice.

thanks Perderabo!!!

What is the main point of creating the metadatabase ? I understand is for describing the setup but is it for setting up the system disk mirrors?

by executing the command :
# metadb -a -f -c 3 c1t0d0s7

if creating the metadatabase and not mirroring the system disks then what would it use for?

Thanks

if you don't need metadevices, you also don't need the metadb's. but if you want to setup other raid devices in your system with slvm you will need the metadb!