Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can a stale pv be used as a 'good' copy

Status
Not open for further replies.

tvanover

Technical User
Apr 6, 2004
2
BE
Hi,

During a storage migration project, we will do the following:

suppose volumegroup testvg containing 2 disks:
hdisk10 and hdisk11.
logical volumes are mirrored on both disks.

we want to umount the logical volumes, and then block access to hdisk11 (to use it in case sth. goes wrong). aix will no longer see hdisk11 and mark it missing (and stale in lvm terminology).
we will then add a copy on a new disk hdisk12. (so we would have a good copy on hdisk10, a stale copy on hdisk11 and again a good copy on hdisk12.

suppose during the synchronization of the pp's from hdisk10 to hdisk12 sth. goes wrong and hdisk10 becomes corrupt, breaks down or whatever.

the idea is then to use the 'stale' copy on hdisk11 like this: make hdisk10 unavailable to aix. the volumegroup will probably varyoff because there are no more valid disks (depends on # disks in vg and quorum settings). then we would like to force the volumegroup backonline (using the -force parameter and setting the MISSINGPV_VARYON parameter). in this case, the only visible disk would be hdisk11 (which was previously stale).

and now it comes: will we be able to do this ? will the contents on this disk still be considered stale since it will be the only copy available ?

thanks,

Tom.
 
Hi bjverzal,

it might work. before we block the disk, we do the split, and a new logical volume (unmirrored) is created containing the same contents. the new logical volume will disappear when we block the disk, and won't suffer from the 'stale' problem as in my original scenario. if the disk needs to be brought back online, i will see a new logical volume with the contents that i need.

only complications are that i mirror by logical volume name, and the name will no longer be the original name.
as we need to migrate a few TB's, i don't really like all these complications.

any ideas if my original scenario would work as i described ? unfortunately i have no test machine available to test it out.


thanks,

Tom.
 
Mirroring by lv name is the only type of mirroring you can do. All the mirrorvg script does is create a mirror for each lv.

After you are done, just do a chlv to rename each lv.

I don't have an opinion on the original suggestion. I don't know what would happen if you tried to use a 'stale' copy. It definitely does not sound safe though. I assume you'll have backups before you start...

BV
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top