- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Data being moved to new SAN
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
07-11-2018 07:08 AM
07-11-2018 07:08 AM
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.
- Record HBA info using fcmsutil
- Record details if any LUN being used for swap? - there are no swap files on any SAN LUNs
- swapinfo -a
- Get current disk info before starting
- ioscan –kfnC disk > /tmp/SANmove/currdiskinfo.out
- Backup strings within /etc/lvmtab file
- cp –p /etc/lvmtab /tmp/SANmove/lvmtab_bk
- Save directory listing of /dev/vg01, vg03, vg05, vg07 in case permissions need to be recreated after new device is available.
- Save volume group info
- vgdisplay –v vg01 > /tmp/SANMove/vg01.out
- vgdisplay –v vg03 > /tmp/SANmove/vg03.out
- vgdisplay –v vg05 > /tmp/SANmove/vg05.out
- vgdisplay –v vg07 > /tmp/SANMove/vg07.out
- stop the application and database
- Perform a cold backup to tape
- unmount the file systems
- Record the minor number of disks for later use
- ll /dev/vg*/group > /tmp/SANmove/vg.group.out
- Deactivate old volume groups
- vgchange -a n vg01
- vgchange –a n vg03
- vgchange –a n vg05
- vgchange –a n vg07
- Export vg info for later use
- vgexport –s -p-v -m /tmp/SANmove/vgxx.map /dev/vg01
- vgexport –s -p -v -m /tmp/SANmove/vgxx.map /dev/vg03
- vgexport –s -p -v -m /tmp/SANmove/vgxx.map /dev/vg05
- 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.
- disconnect the old storage -customer will remove the old LUNs
- present the new storage disk(LUN) to server
- discover the disks
- insf -e
- ioscan –fn
- Remove old volume groups from lvmtab
- vgexport vg01
- vgexport vg03
- vgexport vg05
- vgexport vg07
- Remake volume group files
- mkdir /dev/vg01
- mkdir /cev/vg03
- mkdir /dev/vg05
- mkdir /dev/vg07
- Make group file with special minor numbers
- mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
- mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
- mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
- mknod /dev/vg01/group c 64 0x0x0000 - Using numbers recorded earlier
- Check ownership/permissions on new dev files created in the steps above and amend if necessary - all appear to only belong to root:sys
- 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 ?
- vgimport -m /tmp/SANmove/vg01.map –s –p /dev/vg01
- vgimport -m /tmp/SANmove/vg03.map –s –p /dev/vg03
- vgimport -m /tmp/SANMove/vg05.map –s –p /dev/vg05
- vgimport -m /tmp/SANmove/vg07.map –s –p /dev/vg07
- Activate volume groups
- vgchange -a y vg01
- vgchange -a y vg03
- vgchange -a y vg05
- vgchange -a y vg07
- if required run fsck
- mount all file system
- 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2018 01:39 AM
07-13-2018 01:39 AM
Re: Data being moved to new SAN
Hello
Since the replication id performed from Storage Side, plan of action sounds good.
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2018 02:56 AM
07-13-2018 02:56 AM
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 ?
- vgimport -m /tmp/SANmove/vg01.map –s –p /dev/vg01
- vgimport -m /tmp/SANmove/vg03.map –s –p /dev/vg03
- vgimport -m /tmp/SANMove/vg05.map –s –p /dev/vg05
- vgimport -m /tmp/SANmove/vg07.map –s –p /dev/vg07
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 02:54 PM
07-26-2018 02:54 PM
Re: Data being moved to new SAN
if you are moving the data on the same server , you can use pvmove command . It automatically update LVM infor aftert all extents are moved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2018 03:05 AM
07-27-2018 03:05 AM
Re: Data being moved to new SAN
Hi, thanks for the response but as in original post the Customer is going to use OpenReplicator to move the data from old LUNs to new LUNs. Thsi is within the SAN so I am not sure if pvmove would be applicable.