We will deploy physical servers acting as proxies to perform SAN based backup. I know about The Ugly you can be confronted with, the physical proxy resignaturing your disk in case of wrong settings, big change of loosing your vm environment. The things to take care of in order to not make this happen: if possible mount luns read only, disabling automount on the proxy, disk management snap-in disablement and restrict local admin access to the proxy (obviously backup-admins only).
If I implement these things, am I cool then? If anybody has other things to mention please do so..
-
- Expert
- Posts: 235
- Liked: 37 times
- Joined: Aug 06, 2013 10:40 am
- Full Name: Peter Jansen
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Securing repository proxy for use with san access
In fact no additional steps are required. Corruption could be caused by disk initialization only. To effectively avoid automatic mount and initialization of VMFS volumes in Windows 7/2008 and later, SAN Policy should be set to Offline. Starting from v6.1 Veeam B&R automatically sets SAN Policy to Offline (and disables automount in older releases) during installation, thus preventing disks from being initialized. As far as disks are seen as offline in Disk Management, you are safe.
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 49 guests