03-02-2018
You can use ISCSI disk slice for metadb.
Or any disk device slice as far as metadb is concerned.
With metadb command (not metainit), you use defined small slices on disks, not the entire devices (cNtNd0 or cNtNd0s2).
After metadb creation, you may use SVM via meta commands for managing metadevices and metasets.
Just be sure that those luns will be present on machine as long as SVM is used.
Or, if old luns are removed, and new one added, add new and put extra database replica on it.
Remove replica from from old LUN, then remove the lun from system.
Having one metadb slice on one disk is a bad idea anyway.
You would want at least two, spanning on multiple disks (not same disk multiple slices).
Only place in which you can or must use entire devices (cNtNd0s2) is
Copying partition table from from same sized devices prtvtoc .. | fmthard ..
Using dd.
Creating zpools.
SCSI,multipath, zfs debug, information and manipulation using luxadm, mpathadm and zdb commands.
Others i cannot remember now.
Good thing to mention is that using the whole disk during zpool creation will enable you to import that zpool on x86 or SPARC architecture due to filesystem endian awareness.
This, of course, provides data moving from one platform to another, not binaries.
Hope that helps
Regards
Peasant.
9 More Discussions You Might Find Interesting
1. Programming
hi everyone
i have a doubt about ".so" files.
what is the need of ".so" files.
why we use ".so" files.
where we can use ".so" files.
how can i create ".so" files.
can u tell me a good example please
thank you (6 Replies)
Discussion started by: ramesh.jella
6 Replies
2. Shell Programming and Scripting
Hi,
Can someone help me with creating a bash shell script.
I need to create a script that gets a positive number n as an argument.
The script must create n directories in the current directory with names like map_1, map_2 etcetera. Each directory must be contained within its predecessor. So... (7 Replies)
Discussion started by: I-1
7 Replies
3. Solaris
Hi Guys.
I have the follow disk mappig....
My doubt is that the filesystem root is in mirroring. I can see this in the configuration but , I dont know exactly if this in mirroring mean disk in RAID.
In short: Watching the configuration...Can I said if the filesystem / is in Raid?
... (3 Replies)
Discussion started by: aggadtech08
3 Replies
4. Solaris
Hi
I am having a problem creating my live upgrade environment.
Here is the error I get:
root@server:/# lucreate -c SOL10_18May -n SOL10_19May -z /lu_excludelist -m /:dev/md/dsk/d0:ufs -m /var:/dev/md/dsk/d4:ufs -m /export/home:/dev/md/dsk/d6:ufs -m -:/dev/md/dsk/d3:swap -C... (0 Replies)
Discussion started by: notreallyhere
0 Replies
5. Solaris
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
6. Solaris
Hi Guys,
We have an issue,
all metadb's on system was deleted and the system was rebooted.
the system is currented mounted in single-user mode . its a x86 server.
the volumes under SVM is as follows.
/
/var and
/usr
please suggest
Please use code tags <- click the... (1 Reply)
Discussion started by: karthick.sh
1 Replies
7. Solaris
Hi ,
We are facing an issue on one of our solaris x86 server,
After changing the hostname and a orderly reboot , all metadevices shows offline.
please let us know the steps to restore back all metadevices to working state with this new hostname (3 Replies)
Discussion started by: karthick.sh
3 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Here is what I am supposed to do, word for word from my assignment page:
1. Create/modify and print a... (2 Replies)
Discussion started by: Jagst3r21
2 Replies
9. SCO
Also, in my tinkering around I was able to get SCO installed on a VM, using VM Workstation version 12.5 in a Windows 7 Pro-64 computer. I chose the VM Workstation 8.x compatibility model for my VM, an IDE hard drive at 0:0 and an IDE CD Rom at 1:0 using the physical drive of the computer. Using the... (3 Replies)
Discussion started by: jgt
3 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)