Are the correct permissions assigned via the SMB mount?  Not sure I would use this method for the repo let alone over the internet.

Just to make sure that I get it right. Your hardened repository server is using a SMB share? If so, this won't work with immutability as the immutable flag is only available in Linux file systems.

Maybe your agent backups aren't immutable at all?

@Chris.ChilderhoseThanks,

“Are the correct permissions assigned via the SMB mount?”
Maybe, as it works for Windows Agent Backups, using the same exact hardened BR.
FWIW, been using that mount SMB share for over a month, tho non-hardened repo.

“Not sure I would use this method for the repo let alone over the internet.“
Good point, let me clarify.
The linux server and SMB share are in the same datacenter, never routed/exposed to internet

@regnor, Maybe your agent backups aren't immutable at all?

I think you are correct, and now that I am learning to look into the VBR .log file, i think i know what is going on.

Maybe this is a bug with VBR, as it explains what is going on.
Should I report it?

Windows Backup Agent shows success when it should fail in the same exact way as Hyper-V backup.

With Windows Agent Backups, the VBR console is falsely showing success.
In fact, as shown below, the corresponding log shows the same exact errors as with Hyper-V.

here is the console output showing success.

This is the VBR log file, showing the exact same errors as backup log for the Hyper-V.

and it has the exact same errors as the log from the Hyper-V backup.

>05.11.2023 14:47:03.181] <18> Info         �CProxyVcpInvoker] IProxyVcpInvoker] 'Transport.DoRpc' error: Inappropriate ioctl for device
i05.11.2023 14:47:03.181] <18> Info         Failed to set flags for file.
s05.11.2023 14:47:03.181] <18> Info         Failed to invoke rpc command
05.11.2023 14:47:03.181] <18> Error        Inappropriate ioctl for device (Veeam.Backup.Common.CCppComponentException)
o05.11.2023 14:47:03.181] <18> Error        Failed to set flags for file. (Veeam.Backup.Common.CCppComponentException)
u05.11.2023 14:47:03.181] <18> Error           in c++: Failed to execute method �0] for class �immurepolib::IImmutableRepoService].
c05.11.2023 14:47:03.181] <18> Error        Failed to invoke rpc command (Veeam.Backup.Common.CCppComponentException)
m05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.Common.CVcpInvoker.Invoke(CVcpStreamBase stream, String command, CVcpCommandArgs inArgs, Boolean noLog)
r05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.ProxyProvider.CVcpInvokerHolder.Invoke(String command, CVcpCommandArgs inArgs, Boolean noLog)
e05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.ProxyProvider.CProxyVcpInvoker.CallImpl(String methodName, CProxyInvokeInputArg inputArg, Boolean secureCall, Nullable`1 timeout)
t05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.ProxyProvider.CProxyVcpInvoker.Call(String methodName, CProxyInvokeInputArg inputArg)
c05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.ProxyProvider.CTransportService.ImmutabilityApplyLocks(Stringt] storageLinks, TimeSpan lockPeriod, String& error, Stringn]& notProcessedStorageLinks, Boolean finalize)
s05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.Core.CProxyTransport.ImmutabilityApplyLocks(String4] storageLinks, DateTimeUtc immutableTill, String& error, Stringe]& notProcessedStorageLinks)
s05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.RepositoryImmutability.CSetImmutabilityCommand.Execute(IImmutableRepositoryProxy proxy, IImmutabilityPeriodProvider periodProvider)
m05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityLockPeriodManager.SetImmutability(ISetImmutabilityCommand command, IImmutabilityPeriodProvider periodProvider)
b05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityStorageCommander.SetLock(Guid backupId, IReadOnlyCollection`1 storageIds, Boolean finalizeLocks)
.05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityStorageCommander.SetLock(SetImmutabilityLockRequest request)
05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.Core.CRepositoryImmutabilityProcessingAlgorithm.SetLock(IRepositoryImmutabilityValidator repositoryImmutabilityValidator, SetImmutabilityLockRequest setImmutabilityLockRequest)
I05.11.2023 14:47:03.181] <18> Error           at Veeam.Backup.Core.CRepositoryImmutabilityProcessingAlgorithm.SetLockSafe(IRepositoryImmutabilityValidator repositoryImmutabilityValidator, SetImmutabilityLockRequest setImmutabilityLockRequest)
s05.11.2023 14:47:03.196] <18> Error        Inappropriate ioctl for device (Veeam.Backup.Common.CCppComponentException)
L05.11.2023 14:47:03.196] <18> Error        Failed to set flags for file. (Veeam.Backup.Common.CCppComponentException)
c05.11.2023 14:47:03.196] <18> Error           in c++: Failed to execute method g0] for class �immurepolib::IImmutableRepoService].
e05.11.2023 14:47:03.196] <18> Error        Failed to invoke rpc command (Veeam.Backup.Common.CCppComponentException)
x05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.Common.CVcpInvoker.Invoke(CVcpStreamBase stream, String command, CVcpCommandArgs inArgs, Boolean noLog)
C05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.ProxyProvider.CVcpInvokerHolder.Invoke(String command, CVcpCommandArgs inArgs, Boolean noLog)
a05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.ProxyProvider.CProxyVcpInvoker.CallImpl(String methodName, CProxyInvokeInputArg inputArg, Boolean secureCall, Nullable`1 timeout)
s05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.ProxyProvider.CProxyVcpInvoker.Call(String methodName, CProxyInvokeInputArg inputArg)
05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.ProxyProvider.CTransportService.ImmutabilityApplyLocks(String�] storageLinks, TimeSpan lockPeriod, String& error, Stringt]& notProcessedStorageLinks, Boolean finalize)
.05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.Core.CProxyTransport.ImmutabilityApplyLocks(Stringy] storageLinks, DateTimeUtc immutableTill, String& error, Stringr]& notProcessedStorageLinks)
L05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.RepositoryImmutability.CSetImmutabilityCommand.Execute(IImmutableRepositoryProxy proxy, IImmutabilityPeriodProvider periodProvider)
i05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityLockPeriodManager.SetImmutability(ISetImmutabilityCommand command, IImmutabilityPeriodProvider periodProvider)
p05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityStorageCommander.SetLock(Guid backupId, IReadOnlyCollection`1 storageIds, Boolean finalizeLocks)
e05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.RepositoryImmutability.CImmutabilityStorageCommander.SetLock(SetImmutabilityLockRequest request)
m05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.Core.CRepositoryImmutabilityProcessingAlgorithm.SetLock(IRepositoryImmutabilityValidator repositoryImmutabilityValidator, SetImmutabilityLockRequest setImmutabilityLockRequest)
m05.11.2023 14:47:03.196] <18> Error           at Veeam.Backup.Core.CRepositoryImmutabilityProcessingAlgorithm.SetLockSafe(IRepositoryImmutabilityValidator repositoryImmutabilityValidator, SetImmutabilityLockRequest setImmutabilityLockRequest)

Have you tried adding the server to Veeam without SMB and going direct to it?  Just wondering if that would produce different results or not.

@Chris.Childerhose, again, thanks!

Have you tried adding the server to Veeam without SMB and going direct to it?  Just wondering if that would produce different results or not.

I am more than willing to test anything you wonder about. I have been learning so much in this forum.
but small brain not understanding exactly what you want me to try?

That i should install SAMBA on the linux server, create a SMB share, mount the share and test that for the hardened BR location?

No I mean adding the server directly to Veeam as a Linux Hardened repository.  If you do that will it produce a different result.

@asdffdsa6132 It could be a UI bug with the agent Jobs but in General immutability won't work in combination with SMB shares. Only disks/volumes with a Linux filesystem will be able to set the immutable flag. 

No I mean adding the server directly to Veeam as a Linux Hardened repository.  If you do that will it produce a different result.

I think i understand your confusion, sorry about that.
In this older topic, I did connect a SMB share on the internet to VBR as an network attached storage repo.
https://community.veeam.com/discussion-boards-66/license-question-can-use-smb-share-hosted-in-cloud-as-backup-repository-5931

I have since moved on from that tho it worked fine.

However, in https://community.veeam.com/discussion-boards-66/vm-non-instant-restore-works-vm-instant-restore-fails-5938 and now, in this topic, only use linux repo server directly connected to the VBR.

@regnorIt could be a UI bug with the agent Job

Yes, that is my point. Should I report it, what is the correct way to do that?

Sorry, a little too excited that I found a bug, if only a UI bug

@regnor, Thanks. the immutable flag is only available in Linux file systems.

The mounted SMB share supports `xattr`and Veeam sets`user.immutable.until`to be set correctly, 7 days from today

mount -t cifs -o gid=1000,uid=1000 -o credentials=~/.credentials //xxx.your-storagebox.de/xxx-sub2 /hard01
xattr -l /hard01/backups/ABJ_X:_FOLDER-_HARD01/192.168.62.233/'ABJ_X:_FOLDER-_HARD01 - 192.168.62.233D2023-11-05T115841_300A.vbk'
user.immutable.until: 2023-11-12 19:47:02

the problem is that Veeam .log does not list the flag it cannot set.
Is there another flag Veeam tries to set and that fails?

Besides the technical details, Veeam explicitly states that it requires block storage. NFS and SMB cannot be used:

• As the hardened repository requires the block storage, you cannot use the following storage types:
  • NFS share or a Linux machine with the mounted NFS volume
  • ⁠A Linux machine with the mounted SMB (CIFS) volume

https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_limitations.html?ver=120

Regarding the agent job not displaying a warning/error, it would be best to open a support case. Support will be able to confirm if it's a bug and forward it to development.

@regnor“ A Linux machine with the mounted SMB (CIFS) volume“

I did see that in the docs but since mounted SMB works for non-hardened repo, i tried hardened repo.

I do not use block copy, fast rclone, XFS, etc.
with hardened repo, despite the flag error, the backup is valid, health check works, restore works and even instant restore works.

https://helpcenter.veeam.com/docs/backup/hyperv/linux_server.html?ver=120
“You can add a Linux server with local, directly attached storage or mounted NFS as a backup repository. The storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), NFS share”

Interesting, that for non-hardened repo, the docs mention mounted NFS but not mounted SMB.
But as I have posted, for non-hardened repo, backups work, backup copy works, health checks work, veeam.validator works, instant restore works.

so far, no reason why mount SMB cannot be supported.

I will open a support case about the possible UI bug and a support case about using mounted SMB share.
I will update the forum about that.

Once again, thanks for the great forum and taking your time to help.