cancel
Showing results for 
Search instead for 
Did you mean: 

Data being moved to new SAN

lufc
Occasional Contributor

Data being moved to new SAN

Hi

We have a customer who is moving data from old SAN to a new SAN.

We have 4 LUNS presented to a live HPUX server and 2 LUNS presented to a test HPUX server.

Customer is going to use OpenReplicator to move the data from old LUNs to new LUNs.

This is what I think we need to do based on research / knowledge - Would appreciate it if anyone could point out any errors or missing steps.  Need to know how just doing vgimport gets the LVM info onto the new disks when there is nothng reference the new device files.

  1. Record HBA info using fcmsutil
  2. Record details if any LUN being used for swap? - there are no swap files on any SAN LUNs
    1. swapinfo -a
  3. Get current disk info before starting
    1. ioscan –kfnC disk > /tmp/SANmove/currdiskinfo.out
  4. Backup strings within /etc/lvmtab file
    1. cp –p /etc/lvmtab /tmp/SANmove/lvmtab_bk
  5. Save directory listing of /dev/vg01, vg03, vg05, vg07 in case permissions need to be recreated after new device is available.
  6. Save volume group info
  7.                 vgdisplay –v vg01 > /tmp/SANMove/vg01.out
  8.                 vgdisplay –v vg03 > /tmp/SANmove/vg03.out
  9.                 vgdisplay –v vg05 > /tmp/SANmove/vg05.out
  10.                 vgdisplay –v vg07 > /tmp/SANMove/vg07.out
  11. stop the application and database
  12. Perform a cold backup to tape
  13. unmount the file systems
  14. Record the minor number of disks for later use
    1. ll /dev/vg*/group > /tmp/SANmove/vg.group.out
  15. Deactivate old volume groups
    1. vgchange -a n vg01
    2. vgchange –a n vg03
    3. vgchange –a n vg05
    4. vgchange –a n vg07
  16. Export vg info for later use
    1. vgexport –s -p-v -m /tmp/SANmove/vgxx.map /dev/vg01
    2. vgexport –s -p -v -m /tmp/SANmove/vgxx.map /dev/vg03
    3. vgexport –s -p -v -m /tmp/SANmove/vgxx.map /dev/vg05
    4. vgexport –s -p -v -m /tmp/SANmove/vgxx.map /dev/vg07  -p Preview the actions to be taken but does not updated /etc/lvmtab pr /etc/lvmtab_p file or remove the device file.
  17. disconnect the old storage -customer will remove the old LUNs
  18. present the new storage disk(LUN) to server
  19. discover the disks
    1. insf -e
    2. ioscan –fn
  20. Remove old volume groups from lvmtab
    1. vgexport vg01
    2. vgexport vg03
    3. vgexport vg05
    4. vgexport vg07
  21. Remake volume group files
    1. mkdir /dev/vg01
    2. mkdir /cev/vg03
    3. mkdir /dev/vg05
    4. mkdir /dev/vg07
  22. Make group file with special minor numbers
    1. mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
    2. mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
    3. mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
    4. mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
  23. Check ownership/permissions on new dev files created in the steps above and amend if necessary - all appear to only belong to root:sys
  24. Import map files from previous setup - Do i need to include the new disk device names here, e.g.vgimport -m /tmp/SANmove/vg01.map -s -p /dev/vg01 /dev/disk/diskn ? 
    1. vgimport -m /tmp/SANmove/vg01.map –s –p /dev/vg01
    2. vgimport -m /tmp/SANmove/vg03.map –s –p /dev/vg03
    3. vgimport -m /tmp/SANMove/vg05.map –s –p /dev/vg05
    4. vgimport -m /tmp/SANmove/vg07.map –s –p /dev/vg07
  25. Activate volume groups
    1. vgchange -a y vg01
    2. vgchange -a y vg03
    3. vgchange -a y vg05
    4. vgchange -a y vg07
  26. if required run fsck
  27. mount all file system
  28. May need to run swapon –a to activate swap on any new LUN - there is no swap on any SAN LUN.

The system is a 2 node active passive cluster using Veritas Cluster Server.

There is also a DR server which woudl be connected to the same LUNs in the event of a DR failover

So all three servers need to have this procedure performed.

2 REPLIES
PSPrakash
HPE Pro

Re: Data being moved to new SAN

Hello 

Since the replication id performed from Storage Side, plan of action sounds good.

 

lufc
Occasional Contributor

Re: Data being moved to new SAN

Hi - would you have any comment to make on the vgimport commands?

Import map files from previous setup - Do i need to include the new disk device names here, e.g.vgimport -m /tmp/SANmove/vg01.map -s -p /dev/vg01 /dev/disk/diskn ? 

  1. vgimport -m /tmp/SANmove/vg01.map –s –p /dev/vg01
  2. vgimport -m /tmp/SANmove/vg03.map –s –p /dev/vg03
  3. vgimport -m /tmp/SANMove/vg05.map –s –p /dev/vg05
  4. vgimport -m /tmp/SANmove/vg07.map –s –p /dev/vg07

Thanks