- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- MSA 2050/2052 and ESX 5.5 using ISCSI ?
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
02-11-2020 01:48 AM
02-11-2020 01:48 AM
MSA 2050/2052 and ESX 5.5 using ISCSI ?
Hi All,
a simple question. Customer needs a migration strategy from a legacy ISCSI array supporting an ESXI 5.5U3 ingfrastructure. Was considering MSA 2050 or 2052 but support matrix shows ESXi 6.0 is the lowest supported (or at least tested) version. Assume if we were to deploy an MSA2050/2 using ISCSI to provide a new storage location that it should most likely work given it's just ISCSI. Appreciate the SPOCK reccomendations are what's been lab-tested. Just wanted to confirm there should be no major gotchas. Plan would be to re-use the MSA elsewhere once the 5.5 environment is decomissioned.. Existing ISCSI array is EOL and at capacity hence the need. Thanks,
- Tags:
- MSA ESX 5.5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2020 10:16 AM
02-11-2020 10:16 AM
Re: MSA 2050/2052 and ESX 5.5 using ISCSI ?
Hello,
A simple answer is that yes this "should" work but has not been tested or qualified by HPE. However, you should consider several things when migrating your data. With ESXi 6.0 virutal volumes are supported but not with ESXi 5.5. Likely that is also true on the storage side. You did not mention the older device, but likely it is a linear based storage device while the MSA2050 is virtual only. To take advantage of the array and the host OS your best bet would be to move to all virtual.
Just as a precaution - your new system has at least a warranty support contract available on it. If you are not in a supported configuration, your warranty options will be limited.
Without knowing your environement, my concerns would be compatability between your old storage and new. Can you VMotion the data over successfully? And if you can get your current data to the new MSA 2050, your next question to consider would be can you connect a newer ESXi OS version to the MSA 2050 with your data's file system intact? In other words are the OS versions compatable between VFMS5, VFMS6, etc?
You might want to consider future growth and how you want to implement this so you do not build yourself into a corner. It might make more sense to backup your data and start fresh so you have the ability to expand into newer OS and storage options as needed. Sometimes a little pain at the start saves you major heartache at the end.
Good luck!
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
I work for HPE