Sponsored Content
Operating Systems Solaris metadevice submirrors 0 and 1 not consistent Post 302431603 by bluescreen on Tuesday 22nd of June 2010 09:04:50 AM
Old 06-22-2010
I don't think this is an issue as long as you keep good documentation. If one disk fails you still have the other drive.

However, I would take the new systems down to single user mode and change the mirroring so that it is consistent across all your servers.

I have found this site useful in explaining mirroring in Solaris Volume Manager(SVM).


HTH

Last edited by bluescreen; 06-22-2010 at 10:32 AM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

keep UIDs/GIDs consistent

Hi, What is the best ways to keep UIDs and GIDs consistent across unix and linux server. my company have a servers running on hpux, linux, aix and many of them have veritas cluster and hacmp running, many time user account have been created only on one of the cluster node and not the others... (4 Replies)
Discussion started by: robertngo
4 Replies

2. Shell Programming and Scripting

Trouble getting consistent PID of tomcat server from ps

Hello all, I am working on a script to automate the process of restarting some tomcat servers. The versions of tomcat are pretty old and it often happens that they don't shut down gracefully and the PID needs to be manually killed. I am having a bear of a time getting a consistent PID from ps... (1 Reply)
Discussion started by: dkaplowitz
1 Replies

3. Shell Programming and Scripting

Negate alerting for particular metadevice.

Hi All... I have a script that checks for any problems(particularly looks for 'Needs Maintenance') with metadevices and alerts accordingly. This was not configured to alert for a particular metadevice. Now i want to negate alerting for a particular metadevice(say d40). Is this possible? I am... (6 Replies)
Discussion started by: reddybs
6 Replies

4. Solaris

Unable to mount Metadevice

Hi, I am running Solaris 8 on a V880 which has recently crashed. It has got a fibre connection to a StorageTrek array containing my database info. Since the crash I have been unable to mount the 2 metadevices which correspond to /spool & /apps - these FS's contain my db info and theredore I... (20 Replies)
Discussion started by: Duffs
20 Replies

5. Solaris

metadevice problem

hi all i am very new to solaris...i am trying configure raid 0 in my ultrascsi box which is having 6 sun36GB hard disks. I have created 4 state database replicas in the following slices /dev/dsk/c1t1d0s7 /dev/dsk/c1t2d0s7 /dev/dsk/c1t3d0s7 and /dev/dsk/c1t4d0s7. i could not use any other... (7 Replies)
Discussion started by: kingston
7 Replies

6. Shell Programming and Scripting

How to echo columns with consistent spacing?

for (.....) echo -e "$Name | $Age | $Sex\t|$Grade\t\t" done output: John |12 |Male |6th Jack |15 |Male |8th Zachary |15 |Male |9th I want the lines to line up...but it's out of line when the name is long (2 Replies)
Discussion started by: etranman1
2 Replies

7. Solaris

Submirrors swapped after metattach

We had few mirror disks e.g d0 had two submirrors Submirror 0: d2 Submirror 1: d1 I opened mirrors for some activity. by command metadetach d0 d2 After activity I reattach mirrors with command metattach d0 d2 But after that strangely sumirror position is swaped ... (3 Replies)
Discussion started by: kashif_islam
3 Replies

8. Solaris

Metadevice Too Small To Attach

Hi All, I am having trouble with my metadevices and I hope someone can help. when i try to attach my submirror i get the following error: root@xxxx>metattach d31 d21 metattach: tbair1: d21: submirror too small to attach root@xxxx> However, There is a submirror on the other disk which is... (3 Replies)
Discussion started by: A-Train
3 Replies

9. UNIX for Beginners Questions & Answers

Scripts dont give a consistent output..

I have at moment created a setup script that is capable of setting up a workspace for an kaldi enviroment. The script can be found here setup_base_file I guess you wouldn't not be able to run it, without having Kaldi installed, but since this question more relates to scripting, than the... (9 Replies)
Discussion started by: kidi
9 Replies
scconf_dg_svm(1M)					  System Administration Commands					 scconf_dg_svm(1M)

NAME
scconf_dg_svm - change Solaris Volume Manager device group configuration. SYNOPSIS
scconf -c -D [generic_options] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The following information is specific to the scconf command. To use the equivalent object-oriented commands, see the cldevicegroup(1CL) man page. A Solaris Volume Manager device group is defined by a name, the nodes upon which this group can be accessed, a global list of devices in the disk set, and a set of properties used to control actions such as potential primary preference and failback behavior. For Solaris Volume Manager device groups, only one disk set can be assigned to a device group, and the group name must always match the name of the disk set itself. In Solaris Volume Manager, a multihosted or shared device is a grouping of two or more hosts and disk drives that are accessible by all hosts, and that have the same device names on all hosts. This identical device naming requirement is achieved by using the raw disk devices to form the disk set. The device ID pseudo driver (DID) allows multihosted devices to have consistent names across the cluster. Only hosts already configured as part of a disk set itself can be configured into the nodelist of a Solaris Volume Manager device group. At the time drives are added to a shared disk set, they must not belong to any other shared disk set. The Solaris Volume Manager metaset command creates the disk set, which also initially creates and registers it as a Solaris Volume Manager device group. Next, you must use the scconf command to set the node preference list, the preferenced, failback and numsecondaries subop- tions. If you want to change the order of node preference list or the failback mode, you must specify all the nodes that currently exist in the device group in the nodelist. In addition, if you are changing the order of node preference, you must also set the preferenced suboption to true. If you do not specify the preferenced suboption with the "change" form of the command, the already established true or false setting is used. You cannot use the scconf command to remove the Solaris Volume Manager device group from the cluster configuration. Use the Solaris Volume Manager metaset command instead. You remove a device group by removing the Solaris Volume Manager disk set. OPTIONS
See scconf(1M) for the list of supported generic options. See metaset(1M) for the list of metaset related commands to create and remove disk sets and device groups. Only one action option is allowed in the command. The following action options are supported. -c Change the ordering of the node preference list, change preference and failback policy, and change the desired number of secondaries. EXAMPLES
Example 1 Creating and Registering a Disk Set The following metaset commands create the disk set disksetand register the disk set as a Solaris Volume Manager device group. Next, the scconf command is used to specify the order of the potential primary nodes for the device group, change the preferenced and fail- back options, and change the desired number of secondaries. host1# metaset -s diskset1 -a -h host1 host2 host1# scconf -c -D name=diskset1,nodelist=host2:host1, preferenced=true,failback=disabled,numsecondaries=1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cldevicegroup(1CL), scconf(1M), metaset(1M) Sun Cluster 3.2 10 Jul 2006 scconf_dg_svm(1M)
All times are GMT -4. The time now is 08:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy