Sponsored Content
Operating Systems HP-UX Moving AutoRaid array to another system Post 36405 by Perderabo on Wednesday 28th of May 2003 02:32:49 PM
Old 05-28-2003
The only thing that I would add to the info in the other thread is to do a vgexport on the first system, move the map file over, and use the map file during the vgimport.

In that first thread, the poster had a disaster and no map file was possible. Here you can easily create the map file so go ahead with that.

The vgexport also removes the vg info from the vg database on the first system. That frees up the vg so it can be used again.

The vgexport also has that -p flag for preview. I like to use "-p -v" first just to be sure that everything looks ok.
 

6 More Discussions You Might Find Interesting

1. Solaris

Moving a file system to a new partition

Hi everybody. My task today is to move my file system that's 98% full to a new partition slice. I think I'm pretty sure how to do it, but I just wanted to make sure, plus it's been a while since I last did one. The Let's say I have 2 disks c0t0d0 & c0t1d0 ...the file Iwant to move is in c0t0d0s5... (7 Replies)
Discussion started by: Remi
7 Replies

2. Programming

C system() how to send the output to an array??

Hi, im in need if wisdom here guys... How could I store the output of commands like ping integrally directly into a array??? I'll be using system() to run the commands but how can I send the output to an array??? cuz I need to store it so that I can later copy the array's content to a buffer... (5 Replies)
Discussion started by: Jess83
5 Replies

3. Shell Programming and Scripting

awk - Pre-populating an array from system command output

So, here's a scenario that requires the same logic as what I'm working on: Suppose that you have a directory containing files named after users. For awk's purposes, the filename is a single field-- something parse-friendly, like john_smith. Now, let's say that I'd like to populate an array in... (2 Replies)
Discussion started by: treesloth
2 Replies

4. Shell Programming and Scripting

System Output in to an Array or variable

hey guys in only new to scripting as such, but i have a problem. i want to take the output of a search i do in the command line to then be in a variable but only a certain part of the output. this this what im doing: -bash-2.05b$ ldapsearch -x '(dn:=dc)' dc|grep dc= # base... (1 Reply)
Discussion started by: jmorey
1 Replies

5. Solaris

Moving a zone path to a new file system

Hello Gurus, I need your help with this please. I am trying to move a zone to a new directory but it keeps failing. Below is what I did and the message I get. Your help will be appreciated. Thanks zoneadm -z testzone move /rpool/testzone cannot create ZFS dataset rpool/testzone: dataset... (1 Reply)
Discussion started by: cjashu
1 Replies

6. UNIX for Dummies Questions & Answers

File System and Storage Array Confusion

Hi Friends, I have a host(Suse Linux 10.4) which has 2 luns presented from 2 different arrays HP eva and xp. we are planning to migrate hp eva to 3par. When i look for physical volume i see /dev/dm-4, /dev/dm-5, /dev/dm-7and when i look for multipath -ll i see dm-8,dm-9,dm-7. So i can't confirm... (6 Replies)
Discussion started by: munna529
6 Replies
vgimport(1M)															      vgimport(1M)

NAME
vgimport - import an LVM volume group onto the system SYNOPSIS
mapfile] vg_name pv_path ... mapfile] infile] vg_name mapfile vg_name DESCRIPTION
The command adds the specified volume group to the system. The physical volumes, specified as pv_path ..., are scanned to obtain the vol- ume group information and logical volume information. This command works much like A user may explicitly create the vg_name directory and the file before importing the volume group. If absent, the command will automatically create the directory and the file, assigning the minor number as explained in the command man page (see vgcreate(1M)). The vg_name is added to the or file, and the associated logical volume device files are added to the system. assumes that the volume group information has already been created on the physical volumes. This command is useful in conjunction with the command (see vgexport(1M)), to move volume groups from one system to other systems within a high availability cluster. creates logical volume device files under the vg_name directory using the naming convention given in mapfile or using the default naming convention used by the command (see lvcreate(1M)). The command reconstructs the newly imported volume group entry in the or file. The order of the disks belonging to the newly imported vol- ume group could be different than it was before. When a bootable volume group is imported (volume groups version 1.0 only), the boot information present in the boot disks might be incor- rect due to the change in the order of disks in the file. This is because the boot information on the boot disks assumes a certain order of disks in and requires a resynchronization of this information after the first activation of a newly imported bootable volume group. To resynchronize the information on the boot disk after the first activation of a newly imported bootable volume group, run the command in recovery mode option). does not activate the imported volume group due to the many possible options at volume group activation time. To activate the volume group once it has been successfully imported, use the command (see vgchange(1M)). Options and Arguments recognizes the following options and arguments: pv_path The block device path names of a physical volume. This argument is not used with the and related options. vg_name The path name of the volume group. Specify the name of the file from which logical volume names and numbers are to be read. This option is optional when used as in the first com- mand line format of the If this option is not specified, logical volume names are created using the default naming convention where is the decimal representation of logical volume minor number. When used with the option, the volume group specified in the mapfile can be shared among the exporting system and the importing systems. Configure the volume group by populating persistent device special files in the or file, corresponding to the volume group, vg_name. (See intro(7) for information about device special files.) This option can only be used with option. If is invoked without a option, legacy device special files will be used to populate the or file. This option may become obsolete in future releases. Scan option. Scan each of the disks connected to the system and update the or file with the physical volumes that have matching volume group information, as found in the mapfile. This option should always be used in conjunction with the option. The specified mapfile is the file gener- ated by running the command, also with and options. Preview the actions to be taken but do not update the or file or add the logical volume device files. This option is best used in conjunction with the option. Print verbose messages including names of the logical volumes. Import the set of pv_paths held in the infile into the volume group. This option is used as an alternative to specifying the pv_paths on the command line. Each pv_path must appear on a new line in the infile. This option may not be used together with the option. WARNINGS
The option may become obsolete in future releases. No more than eight paths to any physical volume will be added to the or file. All other paths wll be omitted. The following warnings apply to the option, when importing disks with alternate paths: The command does not preserve the path ordering, when a volume group is exported and then imported. This may cause the primary and alter- nate paths to be different on an importing system, from that of an exported system. Also, additional alternate paths that were not config- ured on the exported system may get discovered and configured on the importing system. If the original primary path of a disk gets configured as an alternate path after the volume group is imported, the order can easily be reverted by using to remove the primary path and then reconfiguring the same path again as an alternate, using If additional alternate paths were added to the newly imported volume group, use to reduce any alternate paths that were added but not required. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Import the volume group that is located on physical disks and Activate the volume group following a successful import: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be used by the importing system only: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be shared among the exporting system, this system, and other systems importing the volume group as shared: Import the volume group using the infile, was previously specified by the command on another system, and it assumes that pv_paths in the are identical on both systems. SEE ALSO
vgexport(1M), vgscan(1M), intro(7), lvm(7). vgimport(1M)
All times are GMT -4. The time now is 07:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy