Question about NAS Repository Configuration with Multiple NAS IP Addresses

[matsusan]

I would like to confirm the supportability and best‑practice considerations for the following NAS repository configuration.

Scenario
- One NAS device has two different IP addresses.
- I plan to create two separate backup repositories, each using a different IP.
- Each repository points to a different, non‑nested folder on the same volume.
[Example]
One NAS has two IPs:
- 192.168.0.1 → Repository name: BKNAS01_0_E
- 192.168.10.1 → Repository name: BKNAS01_10_E
Each repository points to a different folder on the same volume:
- \\BKNAS01_0\E$\FRONT
- \\BKNAS01_10\E$\BACK

Documentation Review
I checked the following:
[Backup Repositories]
https://helpcenter.veeam.com/archive/ba ... itory.html
Notes mention:
- Do not configure multiple repositories pointing to the same location.
- Do not use nested paths.
Since my configuration uses different IPs and different non‑nested folders, I am unsure whether this still counts as “same location”.

[NFS Share]
https://helpcenter.veeam.com/archive/ba ... share.html
It states:
- NFS multipathing is not supported.

Questions
- Is this configuration supported?
- Is it recommended or not recommended?

[david.domask]

Hi matsusan,

These will be presented as NFS or SMB ( CIFS ) shares?

If you have multiple different and unique shares being exported from the same NAS device, will be fine. The main concern is that the two repositories must be kept completely separate like the User Guide tells, and looks like your plan will suffice.

As for recommended / not recommended, primary question is why do it with separate IPs? I would always opt for less networking when possible if both repositories will be added to the same backup server, but if you could share a bit more would be great.

[matsusan]

Hi David,

We are considering both NFS and SMB (CIFS) for this setup.

Regarding “your plan will suffice”, I’d like to confirm that the configuration is supported:
two repositories, each using a different IP address and a different non‑nested folder on a same volume.

The reason for separating the IPs is that we want certain backup jobs to run over different network segments.
By assigning each job to a repository created with a different NAS IP, we expect to control the network path used.

If there are any concerns with this approach, please let me know.

Thanks again.

[david.domask]

Hi matsusan,

Yes, it is supported as both will be treated as separate devices. The main concern is how the data is stored / presented via the shares on the back-end; for example, with my lab TrueNAS setup, we have multiple NFS shares coming from the same backing volume but under their own unique directories, so accessing one share does not expose any part of the other share.

As noted, the only concern is that this is a bit extra networking work, but if it's a requirement for your setup, then it will work. But again make sure that the two directories do not overlap in any way.