04-14-2011
SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is not running Solaris cluster? Solaris OS versions on all 3 nodes (2 nodes at SITE-A and 1 node at SITE-B) is same.
This is to say can I have a solution having 2 nodes in a Solaris cluster at SITE-A and have DR by having a single non-clustered node at SITE-B using SVM metaset replicated via storage replication.
Thanks.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"
I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes... (11 Replies)
Discussion started by: heartwork
11 Replies
2. Solaris
I m not able to copy the text present on the tree's node to terminal or other text editor in solaris. I m using <Shift><control> C and V comaand for the same but the text is not being copied and pasted on the text pad or the terminal window.
While the same is possible in windows OS using ctrl+c... (3 Replies)
Discussion started by: friendanoop
3 Replies
3. HP-UX
Need help guys!
when running cmrunnode batch i'm getting this error
cmrunnode : Waiting for cluster to... (1 Reply)
Discussion started by: Tris
1 Replies
4. High Performance Computing
All-
I am new to these forums so please excuse me if this post is in the wrong place.
I had a node crash in a 4 node cluster and mgmt has determined this node will not be part of the cluster when rebuilt. I am researching how to remove it from the cluster information on the other 3 nodes and... (2 Replies)
Discussion started by: bluescreen
2 Replies
5. High Performance Computing
hi,
i am trying to setup a 2 node cluster environment. following is what i have;
1. 2 x sun ultra60 - 450MHz procs, 1GB RAM, 9GB HDD, solaris 10
2. 2 x HBA cards
3. 2 x Connection leads to connect ultra60 with D1000
4. 1 x D1000 storage box.
5. 3 x 9GB HDD + 2 x 36GB HDD
first of all,... (1 Reply)
Discussion started by: solman17
1 Replies
6. Solaris
Dear all,
I have created a shared metaset(500gb) having 3 hosts in which 2 hosts are in cluster and 1 is non cluster. I have taken the ownership in cluster node from non cluster node but the problem is i am unable to mount the file system it is giving error "/dev/md/eccdb-ds/d100 or /eccdb-ds... (1 Reply)
Discussion started by: spandhan
1 Replies
7. Solaris
I have one disk that is reporting I/O errors but the same LUN mounted on a different node is able to access it without issue, is there a way to identify which HBA is being used for the LUN without swapping each out at a time? (4 Replies)
Discussion started by: thmnetwork
4 Replies
8. UNIX for Advanced & Expert Users
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
9. AIX
Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script... (2 Replies)
Discussion started by: depam
2 Replies
10. HP-UX
Hi,
We have HP UX service guard cluster on OS 11.23. Recently 40+ LUNs presented to both nodes by SAN team but I was asked to mount them on only one node. I created required VGs/LVs, created VxFS and mounted all of them and they are working fine. Now client requested those FS on 2nd node as... (4 Replies)
Discussion started by: prvnrk
4 Replies
LEARN ABOUT SUNOS
metaimport
metaimport(1M) metaimport(1M)
NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations
SYNOPSIS
metaimport -s setname [-n] [-v] [-f] [disks...]
metaimport -r [disks...]
metaimport -V
metaimport -?
The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu-
ration. Replicated disk sets are disk sets created using remote replication software.
The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command
fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk
sets allowed on a system, see the .
Use metaset(1M) or metastat(1M) to view the configuration of the imported set.
You must run metaimport as root.
metaimport requires a functional Solaris Volume Manager configuration before it runs.
The following options are supported:
-f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could
result in corrupt configurations and should only be used when metaimport fails with the "Insufficient quorum
detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully
import. Some or all data could be corrupted or unavailable when importing a partial set or a set lacking a replica
quorum.
-n Does not actually perform the operation, but shows the output or errors that would have resulted from the opera-
tion, had it been run.
-r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport
reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport
reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaim-
port reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or
more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing
the specified disks.
-s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to
the name it may have had on a different system.
-v Verbose. Provides detailed information about the metadb replica location and status.
-V Version information.
-? Display a help message.
Example 1: Importing a Disk Set
The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set
being imported.
# metaimport -s blue c1t5d0
Example 2: Reporting Disk Sets to Import
The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could
be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored.
This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You
can specify a component on the command line to reduce the scope of the scan and generate results more quickly.
# metaimport -r
0 Successful completion.
>0 An error occurred.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWmdu |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5)
16 May 2005 metaimport(1M)