Skip to main content
NetApp Knowledge Base

Existing ISCSI LUNs are not visible on new Veeam proxy server

  1. Last updated
  2. Save as PDF
Views:
375
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
SAN
Last Updated:

Applies to

  • Ontap
  • ISCSI LUN
  • Veeam Proxy server with Windows v2019
  • EMC datastore

Issue

  • Existing LUNs were mapped to old Veeam Proxy server with windows v2019.
  • The LUNs from each volume were clubbed as single disk on host side and these disks were reporting as basic disks instead of dynamic disks.
  • New Veeam proxy server was created as there were some issues with old server and new server has same configuration, same IP and SAM IQN as old Veeam proxy server.
  • Since its same IQN for new server the existing LUNs on NetApp side must be visible on new Veeam proxy server but they weren't.
  • ISCSI initiator portal on new server was showing as connected for target LIFs.
  • New LUNs created on NetApp and mapped to the same Igroup were visible on both old & new server.
  • Old Veeam Proxy server was using Microsoft Storage Space Device and Spaces for existing disks on windows side as opposed to using iSCSI.

Existing ISCSI LUNs are not visible on new Veeam proxy server clipboard_e60c800bab6487133cf4ba0e006f48a41.png

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.