Multiple ISCSI mounts across proxies and b&r server

[adam.costello]

Veeam team,
I have come across an issue, and wanted to understand it a bit more. Here is the scenario:
1. Single B&R server with 2 ISCSI mounts from a Nimble block only array
2. SOBR configuration with 2 ISCSI mounts (same mounts as above) with data locality as the configuration
3. 3 Proxy servers with 2 ISCSI mounts (same mounts as above)

Is this a supported configuration? I would think you would want the data to be written from the proxy servers across the array, as scale is needed or required instead of a single repository server with a single interface to handle all of that workload.

Thoughts?

[Mildur]

Hi Adam

Are you trying to mount the same iSCSI LUN (your Backup Target) to multiple windows server at the same time?

That is definitely not a good choice. The different windows machines are not talking to each other. If two machines are trying to write data to the same iscsi lun at the same time, it can lead to data corruption.
Connecting the same iscsi lun to multiple machines is only supported when all connected machines are talking to each other and have knowledge, which one is writing to which block on the LUN. That is not the case with veeam repos and proxys.

[rennerstefan]

Hi Adam,

as Fabian already wrote the configuration should be changed in a way that only the repository server has access to the LUNs you want to use as your backup destination.
If you want to scale you can either scale the repo server (more CPU, RAM and interfaces) or by adding additional repository server.
You can also a proxy be a repo server at the same time.
But you should never mount the same LUN to different servers the same time unless the servers are cluster servers and with that make sure that only one server accesses data at the same time.
But that is nothing you would use to scale a Veeam environment.

As written above you should really change it as you may have data corruption soon which my make your backups useless. At least if we understand correctly what you explained.

Thanks

[chris.childerhose]

If you are trying to mount the iSCSI volumes to your Proxy server to do Storage Integration backups with Nimble then you should be mounting the LUNs that contain your VMs and not your repository volumes connected to your VBR server as you have noted with the SOBR. That is typically how it is done with Nimble as I used to configure this in a previous job and it required the NCM - Nimble Connection Manager be installed on your Proxy server for making the connection to the iSCSI volumes as it also turns off - automount.

[adam.costello]

This has been resolved by utilizing a repository server. Thank you all.