PowerShell vs GUI Behavior for NAS Backup Objects (NetApp SVM / Share Path Differences)

[appleoddity]

Subject: PowerShell vs GUI Behavior for NAS Backup Objects (NetApp SVM / Share Path Differences)

Hi all,

I'm running into a disconnect between what the Veeam GUI allows and what I can accomplish via PowerShell when working with NetApp NAS filers.

Environment / Context

- NetApp storage systems are added to Veeam as NAS Filers
- In the GUI, I can create a NAS backup job and add:
- - Entire NAS Filer
- - Specific SVM
- - Specific share under an SVM

The GUI represents these paths as:

Code: Select all

<netapphost>
<netapphost>\<svm>
<netapphost>\<svm>:\<share_name>

What I See in PowerShell

When querying an existing job:

Code: Select all

Get-VBRUnstructuredBackupJob

The BackupObject array correctly reflects the Path as:
- Host: <netapphost>
- SVM: <netapphost>\<svm>
- Share: <netapphost>\<svm>:\<share_name>

Creating Objects via PowerShell

To add objects, I must use:
- New-VBRNASBackupJobObject
- Then pass that into:
Add-VBRNASBackupJob

Example – Entire NAS Filer (Works as Expected)

Code: Select all

New-VBRNASBackupJobObject -SanEntity (Get-NetAppHost -Name <netapphost>)

Example – File Share (Problematic)

Code: Select all

New-VBRNASBackupJobObject -Server (Get-VBRUnstructuredServer -Name <netapphost>\<svm>:\<share_name>)

Issue #1 – Path Translation

The resulting object has its Path converted to:

Code: Select all

\\<IP Address>\<share_name>

This carries through into:

Code: Select all

Get-VBRUnstructuredBackupJob

However, in the GUI, it still displays as:

Code: Select all

<netapphost>\<svm>:\<share_name>

Issue #2 – Missing SVM-Level Object Creation

I cannot find any way in PowerShell to create an object representing:

Code: Select all

<netapphost>\<svm>

There does not appear to be a combination of:
- -SanEntity
- -Server + -Path

that allows adding an SVM the same way the GUI does.

Questions

1) How can I create an SVM-level backup object via PowerShell?
(Equivalent to adding <netapphost>\<svm> in the GUI)

2) How can I add a share via PowerShell so that the path remains:

Code: Select all

<netapphost>\<svm>:\<share_name>

instead of being converted to:

Code: Select all

\\<IP Address>\<share_name>

Concern

Functionally, the jobs appear to run the same. However, it's concerning that:
- The underlying job configuration differs
- The Path value is inconsistent depending on whether the object is added via GUI vs PowerShell

This makes automation feel unreliable or at least opaque.

Any insight into how to properly align PowerShell behavior with the GUI would be greatly appreciated.

Thanks!