Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

state database replicas

Status
Not open for further replies.

kahn630

Technical User
Mar 10, 2005
29
US
What is the min slice required to create disk suite metadb replica, and also can I create two replicas on the same slice, if yes then what are the pros and cons creating multiple state database replicas on the same slice vs each replica on different slice .....thanks
 
If you have a few disks in your system then I don't see the need to put multiple state database replicas on one slice. If you only have a couple of disks though it may be an idea, just in case one of the blocks containing the state database goes bad.

I think about 4-5MB is usually enough, although on the last system I set up it seems I used about 20MB.

Annihilannic.
 
I think Franz has commented on this increased requirement (Solaris 9?) in another thread, but I haven't been able to find it.
 
yes, afaik SDS 4.2.1 has larger state DBs than 4.2, I usually spend 30 MB for 3 copies in one slice

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage
 
I've used 32Mb on a 36GB HDD, not sure who advised. Don't see any point in 2 x metadbs on the same slice, although Sun do recommend 3 metadbs as a safer bet than using only two (see man metadb) in total.
 
SDS/SVM needs at least 3 statedbs to start and (n/2)+1 of all configured dbs. In the old days when you had only two disks, or in small servers with just 2 disk slots, it makes sense to have 3 dbs in one slice to have at least 3 dbs intact if one disk fails...

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage
 
I have a niggling memory of some special write option (synchronous perhaps, i.e. confirming successful write to both mirrors before returning success) that could be enabled for DiskSuite which was safer for databases, but can't find anything that sounds right.

The only thing close that I have found is the 'metainit -S' option for serialisation of writes, although I'm not sure how much of a benefit that would be; it would presumably have a significant negative impact to write performance.

Annihilannic.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top