Sponsored Content
Full Discussion: SDS and replicas
Top Forums UNIX for Advanced & Expert Users SDS and replicas Post 25347 by RTM on Monday 29th of July 2002 10:16:56 AM
Old 07-29-2002
The metadb command is used to administer the replica database - the replica database is used by the software to know where everything is (a simple explanation).

metadb - create and delete replicas of the metadevice state

You should read the documentation on setting up the replica database and other components - Normally you can find it on-line at docs.sun.com but I could not reach it to add the specific link.

Quote:
Is it necessary to add two replicas on the same slice on the new disks, as made before on the others disks ?
If you have replicas already (before attempting to set up the stripe) then that is all you need as long as you followed the 'rules' for setting up replicas. You don't need more replicas just because you are setting up a new volume/mirror/stripe.

Quote:
Is it necessary to add the -f option to add replicas ?
No, as mentioned in the man page:
-f The -f option is used to create the initial state data-
base. It is also used to force the deletion of replicas
below the minimum of two. (The -a and -f options should
be used together only when no state databases exist.)

Quote:
Is it necessary to reboot after creating replicas ?
I could not find an answer on this (and don't have a system to test it on). When creating the replica (while building a system) a reboot is done because we create mirrors of the OS. I believe that a reboot IS needed when first setting up, but not afterwards (if you added more replicas).
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

New Sds Slice

Hi, I'd like to add two new disk (mirrored each other) in a machine still on line. The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk. who could send me exemples or tell me how to... (1 Reply)
Discussion started by: guillaume35
1 Replies

2. UNIX for Advanced & Expert Users

SDS to Veritas migration

...I have a situation where I disks that I mirrored using Solstice Disksuite now need mirroring under Veritas Volume manager...would anyone know the best way to go about 'un-mirroring' and then removing SDS? I can see references in /etc/vfstab and /etc/system that I guess would need... (2 Replies)
Discussion started by: silvaman
2 Replies

3. Solaris

insufficient metadevice database replicas ERROR

First I would like to thank this forum for assisting me in setting up my 1st sunbox. Could not have done it if it had not been for you guys and google :D I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully. I am now looking at configuring... (2 Replies)
Discussion started by: mr_manny
2 Replies

4. Solaris

Problem with DiskSuite replicas

Good morning, I have Solstice disk suite installed on my server. One disk broke so I sostitute it. A replica was present on this disk. I had delete and then recreate it with commands metadb -d and metadb -a. Now when I inquire for the status of replicas I see this: stp11# metadb -i ... (2 Replies)
Discussion started by: bonovox
2 Replies

5. Solaris

T6340/SDS root disk pull test.

Here's the scenario.. Server built with solaris 10 + SDS to mirror OS disk to 2nd disk. If you pull the root disk while the system is running, would you expect : 1, The box to just stay running, ie off its mirror 2, The box would crash, reboot, try and boot of its primary, if not, the... (4 Replies)
Discussion started by: itsupplies
4 Replies

6. Solaris

metadevices: how to test metadb (how to corrupt replicas/understanding replicas)

Hi all, I recently started exploring Solaris 10. I am testing metadevices now. I have been reading about the state databases here: 6.State Database (Overview) (Solaris Volume Manager Administration Guide) - Sun Microsystems So I created 3 metadbs on 2 slices (6 in total; c1t1d0s3... (3 Replies)
Discussion started by: deadeyes
3 Replies

7. Solaris

VxVM confused by SDS?

I have an old V490 running an old version of Soalris 10 and an old version of VxVM. The system disks are configured using metathis and metathat, the remaining disks Because of the brain-damaged way engineering run things here, I cannot change this. I cannot upgrade nor patch the OS. I cannot... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies

8. Solaris

Solaris Volume Manger - Database Replicas Question - Benefits of Increasing Default Size?

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... (2 Replies)
Discussion started by: Keepcase
2 Replies

9. Solaris

zfs raidz2 - insufficient replicas

I lost my system volume in a power outage, but fortunately I had a dual boot and I could boot into an older opensolaris version and my raidz2 7 drive pool was still fine. I even scrubbed it, no errors. However, the older os has some smb problems so I wanted to upgrade to opensolaris11. I... (3 Replies)
Discussion started by: skk
3 Replies

10. AIX

IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ?

I'd like to add some x/linux-based servers to my current AIX-based TDS/SDS server community. Reading the Fine Install Guide (rtfig ?) I believe this may be covered by the section "Upgrade an instance of a previous version to a different computer" i.e. I'm going to install latest/greatest SDS on a... (4 Replies)
Discussion started by: maraixadm
4 Replies
mddb.cf(4)							   File Formats 							mddb.cf(4)

NAME
mddb.cf - metadevice state database replica locations SYNOPSIS
/etc/lvm/mddb.cf DESCRIPTION
The /etc/lvm/mddb.cf file is created when the metadb(1M) command is invoked. You should never directly edit this file. The file /etc/lvm/mddb.cf is used by the metainit(1M) command to find the locations of the metadevice state databases replicas. The metadb command creates the file and updates it each time it is run. Similar information is entered in the /kernel/drv/md.conf file. Each metadevice state database replica has a unique entry in the /etc/lvm/mddb.cf file. Each entry contains the driver and minor unit num- bers associated with the block physical device where a replica is stored. Each entry also contains the block number of the master block, which contains a list of all other blocks in the replica. Entries in the /etc/lvm/mddb.cf file are of the form: driver_name minor_t daddr_t checksum where driver_name and minor_t represent the device number of the physical device storing this replica. daddr_t is the disk block address. checksum is used to make certain the entry has not been corrupted. A pound sign (#) introduces a comment. EXAMPLES
Example 1: Sample File The following example shows a mddb.cf file. #metadevice database location file do not hand edit #driver minor_t daddr_t device id checksum sd 152 16 id1,sd@SSEAGATE_JDD288110MC9LH/a -2613 In the example above, the value for daddr_t indicates that the offset from the start of a given partition is 16 disk blocks from the start of that partition. FILES
/etc/lvm/mddb.cf /kernel/drv/md.conf SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metassist(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M), md.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 8 Aug 2003 mddb.cf(4)
All times are GMT -4. The time now is 05:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy