Re: Migrate Data from 18Gb SCSI Drive to 36GB SCSI Drive

From: Andrew Townsend (Andrew.Townsend_at_BISYS.COM)
Date: 10/28/04

  • Next message: Jef Lee: "Re: 0403-006 Execute permission denied"
    Date:         Thu, 28 Oct 2004 15:47:21 -0400
    To: aix-l@Princeton.EDU
    
    

    I would do similar to Jason but a little different:

    Break the mirror, move all data to one drive, remove empty drive from vg,
    rmdev empty drive, physically remove empty drive, put new drive in, cfgmgr,
    extendvg, mklvcopy old drive to new drive (to re-establish the mirror),
    rmlvcopy old drive, rmdev old drive, physically remove old old drive,
    insert second new drive, extendvg to second new drive, mklvcopy to second
    new drive.

    Drew

                          Jason delaFuente
                          <jason.delafuente To: aix-l@Princeton.EDU
                          @GBE.COM> cc:
                          Sent by: IBM AIX Subject: Re: Migrate Data from 18Gb SCSI Drive to 36GB SCSI Drive
                          Discussion List
                          <aix-l@Princeton.
                          EDU>

                          10/28/2004 03:39
                          PM
                          Please respond to
                          IBM AIX
                          Discussion List

    Break the mirror, move all data to one drive, remove empty drive from vg,
    rmdev empty drive, physically remove empty drive, put new drive in, cfgmgr,
    extendvg, migratepv data to new drive, repeat for second drive, mirrorvg

    Jason de la Fuente

    >>> tony_gallo@THRUWAY.STATE.NY.US 10/28/04 02:19PM >>>
    I have a "datavg" volume group that is mirrored from hdisk2 to hdisk3 on
    a 7026 B80. These internal disks are both 18GB scsi drives and I just
    rec'd 2 new drives to replace them. There are no extra drive bays in the
    server. I figure I will need to back up the vg with savevg and then swap
    the drives and do a restvg which I've never done or could I break the
    mirror and the swap 1 drive and remirror and then the other?

    What would be the best/easiest way?

    TIA

    This email is confidential and intended solely for the use of the
    individual or entity to whom it is addressed. If you have received this
    email in error please notify the system manager at mailadmin@bisys.com and
    delete the email immediately.


  • Next message: Jef Lee: "Re: 0403-006 Execute permission denied"

    Relevant Pages

    • Re: Worst monday of my life - please help...
      ... If that's the case, restoring the SQL ... but it finally did install with a few hiccups. ... >> or just leave the mirrored drives in the server on the secondary IDE ... I decided it was time to re-add the mirror. ...
      (microsoft.public.windows.server.sbs)
    • Re: Realistic drive arrays
      ... > may be an opportunity to swap 2 of the disks for a pair of 143Gb drives ... >> two drives in the same mirror failing within the parts replacement SLA of ... >> How much memory the store.exe process uses really depends on how much ... >>> copy of the database on the disk. ...
      (microsoft.public.exchange.setup)
    • Re: Mirroring help
      ... not to use the OS disk mirror since it only uses up precious processor time ... The better solution is to use SCSI hard drives and to do the RAID ... could mirror a partition on a hard drive to free space on the same drive, ...
      (microsoft.public.backoffice.smallbiz)
    • Re: hardware for Exchange 2003
      ... your current server will work fine. ... in daily bases or weekly bases in order to commit the T.L files into Exchange ... one(or mirror or RAID 1) for Transaction Log files and let's call this D: ... ALL SCSI drives running at 15krpm for maximum throughput. ...
      (microsoft.public.exchange.design)
    • Re: Worst monday of my life - please help...
      ... Also If your mirror was broke did you see anything in logs to indicate why? ... > I have a customer who had a Windows 2000 Small Business Server running ... but it finally did install with a few hiccups. ... > or just leave the mirrored drives in the server on the secondary IDE ...
      (microsoft.public.windows.server.sbs)