Sponsored Content
Operating Systems HP-UX HP-UX: LVM migration from legacy to agile addressing onto a failover server Post 302444176 by poloUX on Wednesday 11th of August 2010 05:59:48 AM
Old 08-11-2010
on the source server:
Code:
vgexport -p -s -v -m <vg_name>.map <vg_name>
scp <vg_name>.map <dest_server>:

here you are creating a map of your VG that can be used to import it on another system using the same disks or a clone of them
on destination server:
Code:
vgimport -v -s -N -m <vg_name>.map <vg_name>

now you can create the same VG by importing it.
-s option scan's the disks which have the VGID identical with the one written in the map file and import them using the persistent DSFs (-N option)
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LAMP Server Failover

How does everyone else handle this? My Setup: Server A: CentOS 5.x 10.0.0.1 Apache MySQL Master Server B: CentOS 5.x 10.0.0.2 Apache MySQL Slave My Domains: dom1.com A record: 10.0.0.1 A Record: 10.0.0.2 dom2.com A record: 10.0.0.1 A Record: 10.0.0.2 (3 Replies)
Discussion started by: Ikon
3 Replies

2. High Performance Computing

Veritas Cluster Server Management Console IP Failover

I have just completed a first RTFM of "Veritas Cluster Server Management Console Implementation Guide" 5.1, with a view to assessing it to possibly make our working lives easier. Unfortunately, at my organisation, getting a test installation would be worse than pulling teeth, so I can't just go... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies

3. Solaris

Server Migration

Hi All We are having a very old server that is working on solaris 5.6 and oracle7. now We are planning to migrate it to a Solaris 8 and oracle 9 environment. The application software of the server is basically written in ProC and there are few sql ,perl and shell scripts on the server . We... (13 Replies)
Discussion started by: asalman.qazi
13 Replies

4. Web Development

[PHP] Server Check and Failover Code

Here is some sample PHP code you can run if you have a PHP web application that uses code or images from an ad server, image server, or content deliver network, and you want to check if it is working and if not, failover to another one: <?php $current_server = "server.domain.com"; // set... (0 Replies)
Discussion started by: Neo
0 Replies

5. Red Hat

DNS server loadbalancing and failover

Hi Friends, I am setting up my new public DNS server using bind 9 on RHEL5.5 64bit. I also want to have an another DNS failover server on one of my another datacenter. My question is, if i installed an new slave DNS server on the second datacenter and configure the zone transfer, do it will be... (2 Replies)
Discussion started by: arumon
2 Replies

6. UNIX and Linux Applications

Server migration from samba+ldap to windows server 2003

Hi, i have a server installed samba+openldap (pdc). Need to migration windows server 2003 (active directory) object users, computers. Where you can read how to do it? Or can tell me how to do it? Thanks. P.S. Sorry for bad english (0 Replies)
Discussion started by: ap0st0l
0 Replies

7. Solaris

NFS server on Legacy Container?

Hi All, I have a problem as follows. Historically, there was an Ultra10 workstation running Solaris 8 using automount to access NFS volumes on a Solaris 8 server. The Ultra 10 was retired and the Solaris 8 server has been migrated to a Legacy Container (Solaris 8 Branded, whole root,... (9 Replies)
Discussion started by: hicksd8
9 Replies

8. AIX

Server migration

Hi, Existing several p5 server with lpar (aix5.3), also implemented with hacmp. And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server. My question is, how to perform data migration from old server/SAN to new server/SAN. Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
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 08:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy