- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Expanding HP SimpliVity from 1Node to 2Node Cluste...
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
Forums
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
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
Wednesday - last edited yesterday by support_s
Wednesday - last edited yesterday by support_s
Expanding HP SimpliVity from 1Node to 2Node Cluster (without xml)
Hi All
Due to a cyber security issue, we lost the complete HP SimpliVity Cluster, but were able to recover all data. So this is not an issue.
But in order to get the environment up and running again, i was only deploying one node, the other node was used to recover the data.
So, now we do have a 1Node Cluster which is working. I need to expand this now to 2Nodes in order to get everything working again as it should be.
As far as I understand: just start the deployment manager and load the config.xml (if it would have been saved), and then start the deployment of the second machine, BUT I do not have the config.xml. anymore.
now my questions: is it somehow possible to read out the xml now from the current node? and use it for later deployment
or deploy somehow the second note?
or what should I do?
Thanks for any hint
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
yesterday
Re: Expanding HP SimpliVity from 1Node to 2Node Cluster (without xml)
Hello @jdacircle
Without the original config.xml file, the process can be a bit complex.
According to my understanding, HPE SimpliVity may not provide a supported method to extract the original config.xml from a deployed node. Once the deployment is complete, the XML may not be stored in a retrievable format. You'll need to manually recreate the configuration by gathering details from the existing node using CLI commands or vCenter.
If you fail in recreating the original config.xml, you may need to deploy the second node manually.
Before you start deploying, ensure the new node matches the versions of the existing node. (Eg: firmware, ESXi, OmniStack versions).
When you start the deployment manager, it may ask for config.xml, and since you don't have it, you might need to manually input the cluster settings during the deployment process.
Since you are dealing with a SimpliVity cluster recovery, I strongly recommend reaching out to HPE SimpliVity support as they may have the tools and expertise to guide you through the process safely.
Regards,
Sanika.
If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.
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]
