NetApp Storage Integration and LUN Protection

[wilkins44]

Way back in the v7 days, we ran across something that suggested that a Windows proxy could try and initialize a LUN on the SAN and rewrite it. Back then, we had a SAN that Veeam wasn't able to integrate with, so storage snapshots weren't an option. Our proxy was setup in direct SAN mode with failover to network mode disabled. Now we’ve got a NetApp FAS8040 as our SAN, a Cisco UCS C220 proxy with direct san access, and storage snapshots enabled.

Is this still a risk due to the NetApp/Veeam integration? If it is, what can be done to mitigate this risk?

I've found a few things in the v8 documentation that addresses this, but nothing in v9 (unless I missed it).

[foggy]

Hi Jay, actually there is/never was an actual risk, since Veeam B&R automatically sets SAN policy to offline mode (or disables automount, if required) during installation of the proxy server, thus preventing disks from being initialized. To be 100% sure, you can check by running 'diskpart' command in the proxy command line and then typing 'san'.