Solaris

Hey all!

I was hoping someone knew anything about this one...
I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately)

Now I know you can increase this amount but is there any point?
The reason I am asking this is that I've setup mirroring on our jumpstart client and everything boots fine, but I noticed in the profile options...

Code:

install_type     initial_install
system_type      standalone
cluster          SUNWCXall
filesys          mirror:d10 c0t2d0s0 c0t3d0s0 free /
filesys          mirror:d20 c0t2d0s1 c0t3d0s1 2048 swap
metadb           c0t2d0s5 size 8192 count 2
metadb           c0t3d0s5 size 8192 count 2

I cannot specify a specific slice size then throw the metadb on top automatically through jumpstart; with the above profile settings what happens is that the system will have approximately 8MB in slice 5

I noticed with our initial setups in our environment that we have 50MB (is this just overkill?)

So going back to my topic name; I was wondering if anyone knew a reason as to why someone would need to increase the default size of the database replica and if there were any benefits.

Our current environment is also 50MB in slice5 (which is setup in our default jumpstart client setup; I've begun to wonder if this is unncessary)

Thanks for any help guys! (and gals!)

the size depends on the number of metadevices and metasets you are going to use... for only 4 devices just stick with the defaults but maybe with 3 metadb replicas (this is what we use). for some "tips and tricks" read here:
Guide to mirroring root / boot disks with solaris volume manager (disksuite) on solaris 10

The default size is to maintain the configuration information of the metadevices you would be configuring.
Hence, depending upon the environment, you may select to increase the default size to great amt of memory!
The link shared above is good to know this..