- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- windows boot from SAN upgrade basic MPIO to full M...
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
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
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
тАО02-16-2009 09:10 AM
тАО02-16-2009 09:10 AM
I will soon be migrating all of the data to an EVA8100 using Continuous Access.
I have viewed the HP MPIO Full Featured DSM EVA4x00/6x00/8x00 family of Disk Arrays 3.01.00 Installation and Reference guide which describes upgrade steps for HP MPIO of a stand alone and clustered systems However, there was no procedures listed if you boot Windows from SAN.
Can anyone tell me the best practice I should follow to move my Windows boot from SAN blades to my new EVA?
I was thinking I would perform the following steps.
shut down Windows blade
unzone blade from EVA5000
zone blade for EVA8100
Command View EVA EVA8100, present vdisks to blade
boot up blade
upgrade MPIO
thanks in advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 10:19 AM
тАО02-16-2009 10:19 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
I would first configure a singe-path access to the EVA-5000 (make sure you hit the controller that owns the virtual disk). Then un-install the basic MPIO and reboot.
Replicate the disk to the EVA8100 and boot single-path from the 8100. Install the full-featured MPIO and MMC plugin. Configure the remaining paths and do a reboot to be sure all paths are recognized fine and everything works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 10:31 AM
тАО02-16-2009 10:31 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
the san design guide p.192 lists windows supported windows multipathin coexistence matrix:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf?jumpid=reg_R1002_USEN
from that you can see that the mpio basic for the eva 3k/5k (3110) can coexist with mpio ff for eva 4k/6k/8k (e.g. 6110) and thus giving you the opportunity to nicely CA migrate all relevant VDISKS to new EVA and then shut down the server and do the CA failover to the new EVA (the failover means that roles of the primary and secondary VDISKs swap and then you can try to boot the servers now from Active/Active EVA...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 10:46 AM
тАО02-16-2009 10:46 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
If it is document number AA-RW86Z-TE (January 26, 2009), then page 192 contains the HP-UX matrix. This thread is about Windows and if I am reading the Windows matrix on page 214 correctly, there is NO coexistence.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 11:04 AM
тАО02-16-2009 11:04 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
the page number is different (214), but i see it as supported :-) with 4k/6k/8k (minimum XCS6110) and not supported with 3k/5k (VCS4x), so I will check it...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 11:19 AM
тАО02-16-2009 11:19 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
the following coexistences are supported:
MPIO FF for EVA 4k/6k/8k coexistence on the same server :
a) Secure Path, YES
b) HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx, YES
c) HP MPIO Full Featured DSM for MSA1000/1500
(Active-Active), YES
d) HP MPIO basic failover for EVA arrays, YES
e) HP MPIO basic failover for XP arrays, No
f) MS DSM, Yes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 11:24 AM
тАО02-16-2009 11:24 AM
Re: windows boot from SAN upgrade basic MPIO to full MPIO
So with both basic and full able to coexist in Windows at the same time, I should be able to:
Shutdown my blades
Perform the CA failover
Rezone and update Command View for the eva8100
Boot up the blades
Upgrade MPIO and reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 11:32 AM
тАО02-16-2009 11:32 AM
Solution1. Add new host/eva8100 zones, update Command View for the eva8100
(online no downtime)
2. install the MPIO FF (coexistence with the MPIO basic)
(online no downtime)
3. Shutdown my blades
(short downtime)
4. Perform the CA failover
(several minutes of downtime)
5. Boot up the blades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2009 11:39 AM
тАО02-16-2009 11:39 AM