Hi
We have two servers connected directly to a HP MSA2052 SAN using ISCSI
One volume holds our VMs and belongs to the Failover clustered storage, the Failover of VMs works smoothly between nodes.
We have another volume on the SAN that is mapped to one of the nodes that we want to test Windows backup on. The Disk mounts successfully within the windows environment to drive letter H. (Initially the second volume was also added to clustered storage, but windows server backup was unable to run as the back up of Drive C also contained the Clustered Storage volume).
Windows server backup can successfully backup and restore within the Server OS GUI.
We want the ability to be able to restore the windows backup from the recovery console if needs be.
The server nics are all static as shown in the attachment. The SAN has a clustered IP address on the 192.168.1.* network.
Once booted into the recovery console we can assign IP Addresses via netsh to the 192.168.1.* subnet and one of the 17.16. subnets and can successfully ping the respective IP on the SAN.
What we don’t know how to do is see the volume on the SAN that was mapped to the server as the H Drive, which contains the Windows backup image.
![Server SAN connectivity drawing.]()
We have two servers connected directly to a HP MSA2052 SAN using ISCSI
One volume holds our VMs and belongs to the Failover clustered storage, the Failover of VMs works smoothly between nodes.
We have another volume on the SAN that is mapped to one of the nodes that we want to test Windows backup on. The Disk mounts successfully within the windows environment to drive letter H. (Initially the second volume was also added to clustered storage, but windows server backup was unable to run as the back up of Drive C also contained the Clustered Storage volume).
Windows server backup can successfully backup and restore within the Server OS GUI.
We want the ability to be able to restore the windows backup from the recovery console if needs be.
The server nics are all static as shown in the attachment. The SAN has a clustered IP address on the 192.168.1.* network.
Once booted into the recovery console we can assign IP Addresses via netsh to the 192.168.1.* subnet and one of the 17.16. subnets and can successfully ping the respective IP on the SAN.
What we don’t know how to do is see the volume on the SAN that was mapped to the server as the H Drive, which contains the Windows backup image.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 11 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.