- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Connecting new host to MSA 2050 without loosing da...
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
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
тАО11-13-2019 02:55 AM
тАО11-13-2019 02:55 AM
Connecting new host to MSA 2050 without loosing data.
I have an HP MSA 2050 storage that is already configured on one host via FC interface and I am using it on Redhat servers with Ext4 partition formatting done on the MSA partitions.
But, as per my new requirements, I need to connect my another server to same HP MSA 2050 in order to access the partitions on both servers simultaneously.
Is it possible to connect a new server (new host) to the MSA 2050 without losing my partitions format & data?
I had read somewhere that adding new host requires re-configuration of LUN & indeed the disk partitions. Just want a confirmation whether is it safe to add new host without losing any partition format & data?
Any help is appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-13-2019 02:01 PM
тАО11-13-2019 02:01 PM
Re: Connecting new host to MSA 2050 without loosing data.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2019 06:52 AM
тАО11-14-2019 06:52 AM
Re: Connecting new host to MSA 2050 without loosing data.
Yes you need Install and configure High-Availability Cluster setup for your Server Operating System in order to access same MSA volume from both servers otherwise data corruption will happen.
You can check below links to get idea and contact your Solution Consultant or OS support to Install and configure two node Cluster system,
https://www.learnitguide.net/2016/02/configure-high-availability-linux-cluster.html
https://www.tecmint.com/cman-multi-node-cluster-setup-in-linux/
https://www.golinuxcloud.com/ste-by-step-configure-high-availability-cluster-centos-7/
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*************************************************************************
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
