- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Rename Nimble volume and VMWare datastore
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
10-29-2015 08:31 AM
10-29-2015 08:31 AM
We want to re-name several volumes/datastores in our virtual environment. We're using a Fiber Channel Nimble array (not iSCSI) and are running on VMWare v 5.0
Is this as simple as just renaming the volume on the Nimble array, and then renaming the datastore within vCenter? I've read where you can run into issues with iSCSI due to the volume name being imbedded in the datastore path/icn, but was not sure if this applies to Fiber Channel implementations or not. I suspect no, but thought I would double check.
Also, what impact does the rename have (if any) on replication?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-10-2015 03:42 AM
11-10-2015 03:42 AM
SolutionHi Dan
I just tried this in a lab running on a FC connected array (vSphere 6). When you rename the volume you will get this message:
As per the message it will take the volume offline, rename it, then bring it back online. This process is very quick (split second) and so the VMs/ESX hosts may survive this short timeout. If you want to be extra sure though I'd recommend planning a maintenance window if you can take downtime on the VMs.
Once the volume is renamed the next replication update will update the downstream volume to the same name.
The renaming of the datastore doesn't cause any downtime.
It worked in my lab, but as above you may want to test first or plan a maintenance window to guarantee no impact.
Jason
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP