Hello All
We have VEEAM for VMware vSphere with Block Storage and are using the Storage
Integration feature.
In the documentation there is written, that we have to open the tcp port 3260 (iSCSI)
between VEEAM proxies and Storage system.
Why exactly is this port needed? What does VEEAM proxies communicate over this port?
Regards
pd
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Apr 02, 2024 9:34 am
- Full Name: Patrik Blocher
- Contact:
-
- VP, Product Management
- Posts: 7145
- Liked: 1532 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam Storage Integration
Patrik, I am making some assumptions here, so please correct me.
You are using a FibreChannel Storage system under VMware and wonder why you need to open iSCSI for the Storage Integration.
Our Veeam background scans and backup from storage snapshot tries to use iSCSI first before it falls back to fibre channel.
The reason for this is that the iSCSI stack is way faster for temporary mounts (rescan) and so there is less delay in the processing for waiting until windows/linux stops to worry about the "lost" drive when we unmount it from Proxy.
If you want to use FibreChannel only processing there is no need for iSCSI connections.
You are using a FibreChannel Storage system under VMware and wonder why you need to open iSCSI for the Storage Integration.
Our Veeam background scans and backup from storage snapshot tries to use iSCSI first before it falls back to fibre channel.
The reason for this is that the iSCSI stack is way faster for temporary mounts (rescan) and so there is less delay in the processing for waiting until windows/linux stops to worry about the "lost" drive when we unmount it from Proxy.
If you want to use FibreChannel only processing there is no need for iSCSI connections.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Apr 02, 2024 9:34 am
- Full Name: Patrik Blocher
- Contact:
Re: Veeam Storage Integration
Hi Andreas
Yes, your assumptions is correct. So you are saying, that, when we are using FC storage only we don't need
this ports open?
But when VEEAM unmounts the drive, Windows will faster find out (rescan over iSCSI) that the mounted drive
is gone, instead waiting until Windows stops worrying? So opening this ports make sense even if we only use FC
storage?
Regards
Pd
Yes, your assumptions is correct. So you are saying, that, when we are using FC storage only we don't need
this ports open?
But when VEEAM unmounts the drive, Windows will faster find out (rescan over iSCSI) that the mounted drive
is gone, instead waiting until Windows stops worrying? So opening this ports make sense even if we only use FC
storage?
Regards
Pd
-
- VP, Product Management
- Posts: 7145
- Liked: 1532 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam Storage Integration
At the storage integration wizard, you can select which protocolls we will use. If iSCSI and FC are enabled, then we try iSCSI first and then fallback to FC.
If iSCSI is possible then we do "rescanns" and "backup from storage snapshot" over iSCSI as the handling of many snapshots and volumes are faster. Usually FC has a 30 seconds or higher timeout, which means at larger scale (many snapshots/volumes) this can slow down processing then. Everything is fine with a FC only processing. If you face a too long rescan window or backup from storage snapshot window, then you can react and consider more proxy server or the additional usage of iSCSI just for the proxy server.
If iSCSI is possible then we do "rescanns" and "backup from storage snapshot" over iSCSI as the handling of many snapshots and volumes are faster. Usually FC has a 30 seconds or higher timeout, which means at larger scale (many snapshots/volumes) this can slow down processing then. Everything is fine with a FC only processing. If you face a too long rescan window or backup from storage snapshot window, then you can react and consider more proxy server or the additional usage of iSCSI just for the proxy server.
Who is online
Users browsing this forum: Baidu [Spider] and 31 guests