Note: At least 3 replicas are required for a consistent, functional, multi-user Solaris system.
3 - yields at least 2 replicas in the event of a failure
Note: if replicas are on same slice or media and are lost, then Volume Management will fail, causing loss of data.
Note: place replicas on as many distinct controllers/disks as possible
Note: Max of 50 replicas per disk set
Note: Volume Management relies upon Majority Consensu Algorithm (MCA) to determine the consistency of the volume information
3 replicas = 1.5(half) = 1-rounded-down +1 = 2 = MCA(half +1)
Note: try to create an even amount of replicas
4 replicas = 2(half) + 1 = 3
State database replica is approximately 4MB by default - for local storage
Rules regarding storage location of state database replicas:
1. dedicated partition/slice - c0t1d0s3
2. local partition that is to be used in a volume(RAID 0/1/5)
3. UFS logging devices
4. '/', '/usr', 'swap', and other UFS partitions CANNOT be used to store state database replicas
Categories
- Basics (11)
- Storage (SAN) (2)
- Veritas Volume Manager (2)
- ZFS (8)
- Zones (6)
Thursday, May 22, 2008
State Database Replicas - Introduction
Subscribe to:
Post Comments (Atom)
Subscribe to Solaris Guru
Browse Articles
-
▼
2008
(23)
-
▼
May
(17)
- Solaris - Crontab
- NETSTAT Usage in Solaris
- State Database Replicas - Introduction
- Solaris Volume Management - Introduction
- Creating a Swap File/Partition in Solaris
- Implementing a Temporary File System (TEMPFS) in S...
- How to determine file system associated with devic...
- Steps to partition and create file systems on a So...
- NAS and SAN - A Comparison (for newbies)
- Tips on Veritas Volume Manager (VxVM)
- Veritas Volume Manager - Quick Start Command Refer...
- Mirroring Disk With Solaris Disksuite (formerly So...
- Gigabit Ethernet Configuration
- ZFS - Introduction
- Solaris Zones - Introduction
- ZFS - Training Video
- SAN Storage Configuration in Solaris
-
▼
May
(17)
0 comments:
Post a Comment