Re: disaster please help

From: Robert Miller (rmiller_at_SMUD.ORG)
Date: 06/22/05

  • Next message: PJ Humble: "user admin"
    Date:         Wed, 22 Jun 2005 07:07:57 -0700
    To: aix-l@Princeton.EDU
    
    

    Basically, the VG info gets written to the disks in the VG, I believe
    it's called the VGDA (Volume Group Descriptor Area). This is what lets
    you do things like export a VG (blow away its definition from AIX) and
    import it on another machine after moving the disks...

    If you have multiple disks in a VG, when you import the VG, all the
    disks that make up that VG will show as being in that VG (assuming
    they're all there - if they're not I believe you'll get an error
    message).

    So, the short answer to your question is yes, the VG names should be the
    same as they were originally, having multiple disks in a VG won't make a
    difference.

    If you had rootvg (on hdisk0/hdisk1), oraclevg (on hdisk2/hdisk3) and
    datavg (on hdisk4) for example:

    importvg -y oraclevg hdisk2 # (imports oraclevg which is on hdisk2
    and hdisk3)
    importvg -y datavg hdisk4

    I usually use whatever disk shows up first in the hdisk list for the VG
    to do the import, but I don't think it'd matter if you used hdisk3 in
    that case...

    Keep in mind you will still need to varyonvg each VG that you import,
    and mount the filesystems...

    --rm

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU]On Behalf Of
    Pugliese, Edward
    Sent: Wednesday, June 22, 2005 5:30 AM
    To: aix-l@Princeton.EDU
    Subject: Re: disaster please help

    You only have to one importvg with one of the disks of the non-rootvg
    volume group. I believe it is the VGDA that contains the information
    about what LV's and PVID's belong to the volume group.

    I'm not sure what you could do about data on the other rootvg disk. If
    you try to importvg on that disk there would be conflicting LV names
    from you existing LV's. My understanding is that AIX will
    automatically rename those LV's. You then could manually chance
    /etc/filesystems to try and mount a filesystem with the renamed LV's.

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
    Gerard M. MAMOU
    Sent: Wednesday, June 22, 2005 1:59 AM
    To: aix-l@Princeton.EDU
    Subject: Re: disaster please help

    Hello
    thank you for your answer.
    question continued:
    if these old disks previously known as
    hdisk2 and hdisk3
    are also know (because I have also two disks for my new rootvg) should I
    type importvg -y uservg -P hdisk2 importvg -y uservg -P hdisk3
    meaning:
    should the vg_name uservg of these commands be the SAME as the old
    configuration how the new system knows that there is two disks in the
    uservg if I type only one time importvg -y uservg -P hdisk2

    will the system know about the LV in these two disks? how?
    Thank you
    Gerard Mamou
    .

     On Tue, Jun 21, 2005 at 01:46:06PM -0700, Patrick B. O'Brien wrote:
    > Get the pvid's of these hdisks;
    > lspv.
    >
    > Now do the following;
    > importvg -y vg_name -P pvid
    >
    >
    >
    >
    > -----Original Message-----
    > From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
    > Of Gerard M. MAMOU
    > Sent: Tuesday, June 21, 2005 1:26 PM
    > To: aix-l@Princeton.EDU
    > Subject: disaster please help
    >
    > Hello
    > I have a rs6000 43p with rootvg(hdisk0 and hdisk1) and uservg(hdisk2
    > and hdisk3)
    >
    > The root vg hdisk0 does not boot.
    >
    > I tried to reinstall a mksysb on a new disk.
    > It worked fine.
    >
    > How do I get back my datas of hdisk2 and hdisk3 I did not backup them,

    > I did not exportvg them.
    >
    > What can I do with the hdisk1? Could I get the datas on it?
    >
    > Could I use linux with jfs support to mount the hdisk2 and hdisk3?
    How?
    > Please help
    > Gerard Mamou

    "This e-mail and any attachments may contain confidential and privileged
    information. Any dissemination or use of the information by a person
    other than the intended recipient is unauthorized and may be illegal. If
    you are not the intended recipient, please notify the sender immediately
    by return e-mail, delete this e-mail and destroy any copies. Although
    this e-mail and any attachments are believed to be free of any virus or
    other defect that might affect any computer system into which it is
    received and opened, it is the responsibility of the recipient to ensure
    that it is virus free and no responsibility is accepted by the Board of
    Trade of the City of New York, Inc. or the New York Clearing Corporation
    for any loss or damage arising in any way from its use. Thank you."
     


  • Next message: PJ Humble: "user admin"

    Relevant Pages

    • Re: disaster please help
      ... The importvg command will pick up the volume group information from the ... are also know (because I have also two disks for my new rootvg) ... importvg -y uservg -P hdisk2 ... importvg -y uservg -P hdisk3 ...
      (AIX-L)
    • Re: disaster please help
      ... You *might* be able to do an importvg for hdisk1. ... are also know (because I have also two disks for my new rootvg) ... importvg -y uservg -P hdisk2 ... importvg -y uservg -P hdisk3 ...
      (AIX-L)
    • Re: disaster please help
      ... You only have to one importvg with one of the disks of the non-rootvg ... should the vg_name uservg of these commands be the SAME as the old ... > Gerard Mamou ...
      (AIX-L)
    • Re: exportvg and importvg ??
      ... Will the importvg still work if the VG - appvg reside on a SSA RAID ... >external disks, reimport and all will be fine. ...
      (comp.unix.aix)
    • Re: 7025-F80 PV Mystery
      ... My suggestion is to drop the WSM output, and figure out what is your ... disks would seem to me to be a more important exercise. ... 0516-604 importvg: ... how to read the Usage printouts. ...
      (comp.unix.aix)