Solaris

Hi

I am new to SVM, but I would like to configure it in one of my servers. The setup is as follows: I have one server running solaris 10 , and is connected to a NetApp via iSCSI protocol. This is how I intend to do it:

Ask the NetApp admin, to provide me with 3 LUNs of 100G each, them use the format comand.
This is where I am stuck.
After creating disk devices such us c0t1d0s6 , c0t2d0s6 and c0t3d0s6, I have to create state database using metadb followed by cereating a metadevice using metainit d0 comand. Is this the right procedure?

Hi,

The normal way of initialising a device would be;

Code:

#> metainit d0 1 1 cntndnsn

This will use the whole slice of the disk, to create a mirror;
Create the mirrored device.

Code:

metainit  d16 1 1  c0t0d0s6
metainit  d26 1 1  c1t0d0s6
metainit  d6 –m d16 d26

It is also worth remembering that the state database must have a number of copies, also that if required you can slice the "disk slices" using soft partitioning like;

#> metainit d100 –p d6 10g

Then you have to create the file system on it like;

mkfs –F vxfs /dev/md/rdsk/d100

Regards

Gull04

Hi

Thanks for the reply, but I believe that before using metainit I have to use the format , them create state database...

The meta database usually sits on a very small disk slice (circa 10MB) so you would need to create that slice, yes.

Thanks for the reply hicksd8 , so for the state database replicas, I have to choose a slice not being used in one of the internal disks, them proceed with the metainit command on the 3 different LUNs/disks, such as :
c2t4d0 c2t5d0 and c2t6d0

Usually when planning SVM, the sysadmin creates a tiny (separate) slice on each disk for the meta database. You might need to reduce the size of another slice to make way for it but the space needed is tiny (just a cylinder or two).

Hi,

Hicksd8 is right in suggesting that normal practice would be to create a single small slice for the metadb, good practice is to have more than one copy of the metadb in each of the slices.

The other point I would make is that when you are using format to initialise your SAN disk, it is common practice if you are using the free hog option to change the selection to slice 0 which would make your disk "c0t1d0s0". But it may be that your standard is to use slice 6.

Regards

Gull04