Issues Exporting Existing LUNs to New ESXi Host
Posted: Thu Sep 08, 2022 1:06 pm
Hello,
I’m new to 3PAR, taking over the system from an employee who is long gone. I have 2 existing ESXi hosts that already have 5 LUNS exported to them separately, there were no Virtual Volume Sets or Host Sets in use.
I created a Virtual Volume Set and added the 5 LUNs used by vSphere. I then created a Host Set and added the two existing ESXi hosts as well as one new one (I will be adding three more but am using one of the new servers to test and document the build for the other three new hosts).
However, when I try to export the Virtual Volume Set to the Host Set I created I get the following warning:
1. Virtual Volume Set VMWare_Volume_Set is already exported. Unless this volume is being exported to a clustered environment, creation of multiple exports could lead to data corruption. To avoid accidental creation of multiple exports, consider setting the virtual volume policy to restrict export to a single host.
2. Host [New Host Name] in Host Set ESXi_Hosts has no active paths. Template will be created but no active VLUNs will be created.
While my ESXi hosts are not in a vSphere cluster, we do want the hosts to all see the same storage. Can I safely ignore warning #1 or do I need to unexport the virtual volumes before exporting them to the new Host Set. If I do have to unexport the LUNs from the existing hosts, I am assuming that I will need downtime as the LUNs will temporarily be invisible to the hosts.
I’m also not sure of warning #2. I have successfully added the new host in the 3PAR Management Console and added it to the Host Set and am simply trying to export the existing LUNs used by vSphere to this new host.
Am I doing anything wrong? Again, I’m new to managing the 3PAR and have to rely on the experts here on the 3PAR user group because our 7400c is no longer under support.
Thanks in advance!
I’m new to 3PAR, taking over the system from an employee who is long gone. I have 2 existing ESXi hosts that already have 5 LUNS exported to them separately, there were no Virtual Volume Sets or Host Sets in use.
I created a Virtual Volume Set and added the 5 LUNs used by vSphere. I then created a Host Set and added the two existing ESXi hosts as well as one new one (I will be adding three more but am using one of the new servers to test and document the build for the other three new hosts).
However, when I try to export the Virtual Volume Set to the Host Set I created I get the following warning:
1. Virtual Volume Set VMWare_Volume_Set is already exported. Unless this volume is being exported to a clustered environment, creation of multiple exports could lead to data corruption. To avoid accidental creation of multiple exports, consider setting the virtual volume policy to restrict export to a single host.
2. Host [New Host Name] in Host Set ESXi_Hosts has no active paths. Template will be created but no active VLUNs will be created.
While my ESXi hosts are not in a vSphere cluster, we do want the hosts to all see the same storage. Can I safely ignore warning #1 or do I need to unexport the virtual volumes before exporting them to the new Host Set. If I do have to unexport the LUNs from the existing hosts, I am assuming that I will need downtime as the LUNs will temporarily be invisible to the hosts.
I’m also not sure of warning #2. I have successfully added the new host in the 3PAR Management Console and added it to the Host Set and am simply trying to export the existing LUNs used by vSphere to this new host.
Am I doing anything wrong? Again, I’m new to managing the 3PAR and have to rely on the experts here on the 3PAR user group because our 7400c is no longer under support.
Thanks in advance!