- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How to Move the Volume group.
Operating System - HP-UX
1755121
Members
2724
Online
108830
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 05:23 AM
тАО11-24-2008 05:23 AM
Re: How to Move the Volume group.
pvmove allows you to move the allocated physical extents (PEs) on SourcePhysicalVolume to one or more other physical volumes (PVs). You can optionally specify a source LogicalVolume in which case only extents used by that LV will be moved to free (or specified) extents on DestinationPhysicalVolume(s). If no DestinationPhysicalVolume is specifed, the normal allocation rules for the volume group are used.
If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last checkpoint.
You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will ignore any logical volumes already in the process of being changed, so some data might not get moved.
pvmove works as follows:
1. A temporary 'pvmove' logical volume is created to store details of all the data movements required.
2. Every logical volume in the volume group is searched for contiguous data that need moving according to the command line arguments. For each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in the pvmove LV instead of accessing the data directly.
3. The volume group metadata is updated on disk.
4. The first segment of the pvmove logical volume is activated and starts to mirror the first part of the data. Only one segment is mirrored at once as this is usually more efficient.
5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the volume group metadata on disk. Then it activates the mirror for the next segment of the pvmove LV.
6. When there are no more segments left to be mirrored, the temporary logical volume is removed and the volume group metadata is updated so that the logical volumes reflect the new data locations.
Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8).
If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last checkpoint.
You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will ignore any logical volumes already in the process of being changed, so some data might not get moved.
pvmove works as follows:
1. A temporary 'pvmove' logical volume is created to store details of all the data movements required.
2. Every logical volume in the volume group is searched for contiguous data that need moving according to the command line arguments. For each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in the pvmove LV instead of accessing the data directly.
3. The volume group metadata is updated on disk.
4. The first segment of the pvmove logical volume is activated and starts to mirror the first part of the data. Only one segment is mirrored at once as this is usually more efficient.
5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the volume group metadata on disk. Then it activates the mirror for the next segment of the pvmove LV.
6. When there are no more segments left to be mirrored, the temporary logical volume is removed and the volume group metadata is updated so that the logical volumes reflect the new data locations.
Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8).
Problems are common to all, but attitude makes the difference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 05:28 AM
тАО11-24-2008 05:28 AM
Solution
Hi Unixguy,
you can move logical volume as well as entire disk by using "pvmove"
You can move a logical volume from one disks to another disks
You can also move entire disk data to another disk. In this case whatever the logical volumes on the old disk. will be moved to new disk.
you can move logical volume as well as entire disk by using "pvmove"
You can move a logical volume from one disks to another disks
You can also move entire disk data to another disk. In this case whatever the logical volumes on the old disk. will be moved to new disk.
Best wishes,
Ganesh.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 06:24 AM
тАО11-24-2008 06:24 AM
Re: How to Move the Volume group.
Thanks Friends,
I closed this thread....
Thanks a lot Johnson.....
Regards,
Unixguy.
I closed this thread....
Thanks a lot Johnson.....
Regards,
Unixguy.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP