Veeam VBR bucket not found

[acolada-gt]

I have tried to access the rustfs bucket from Veeam Backup in many ways. The connection is made through a NAS reverse proxy with rustfs installed in a docker container on the same NAS. No issues with Veeam for Office 365, only with Veeam VBR. I can connect using the default region and I can also select the bucket. But when trying to create or select the folder, the error is "bucket not found".

[loverustfs]

1. What's your version number?

2. What's the region?

3. Are you using path-style or virtual host-style mode?

Does Veeam have any more tips?

[acolada-gt]

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

[ederidder59]

Just to confirm, i have Rustfs installed on my TrueNAS 25.10.0.1, working great. I have the Free VEEAM Backup software running on a Windows Server 2025 as a VM in Vmware Workstation Pro 25H2. This is in a test environment. All works great, can even connect from VEEAM to the S3 bucket but then the same error" Cannot Browse the folder or create folder.

[ramap-spec]

I would advise against using S3 as a target for anything other than 365 backups with Veeam, I have many years experience with Veeam and have tested this before with minio, it is not designed for server backups, please use the XFS or REFS for backup repositories.

[ederidder59]

I wouldn't say that. I have about 60/70 new Enterprise deployments, only this year, with VEEAM B&R and Minio S3 bucket with file versioning and object locking ( some with Compliance mode as well ) having great performance wit this setup. Sizes between 200TB and 2PB+. Only reason i am looking at this amazing project is because what Minio is doing. First removing all features from the WebUI ( ok yes still available with CLI ) but it's clear they want to get rid of Community Edition. I also understand it's not a priority. Still i believe that having this capability would attract a lot of "Unhappy" Minio users

[acolada-gt]

I wouldn't say that. I have about 60/70 new Enterprise deployments, only this year, with VEEAM B&R and Minio S3 bucket with file versioning and object locking ( some with Compliance mode as well ) having great performance wit this setup. Sizes between 200TB and 2PB+. Only reason i am looking at this amazing project is because what Minio is doing. First removing all features from the WebUI ( ok yes still available with CLI ) but it's clear they want to get rid of Community Edition. I also understand it's not a priority. Still i believe that having this capability would attract a lot of "Unhappy" Minio users

You are absolutely correct. Veeam also recommends S3 and object storage for office 365 backups, since it supports multiple proxies and not limited to jet based repository. @ramap-spec I think is talking about Veeam Backup and replication server, as that one uses xfs and refs repositories. Different solutions or products, different repositories. Veeam backup also uses object storage in Amazon or Wasabi or in scale out repositories, along with refs or xfs. But i t has nothing to do with the issues reported here. It should be a simple solution to why the folders from the bucket cannot be browsed.

[loverustfs]

Thanks for the feedback regarding the Veeam integration.

We have noted the issue where browsing directories and buckets may fail or appear as non-existent within the Veeam interface. We plan to investigate this compatibility behavior to understand the root cause.

However, please be aware that this is currently a lower priority item on our roadmap compared to other core features, so it may take some time before we can dedicate resources to fix it. We appreciate your patience.

@ramap-spec @acolada-gt

[gabryp]

Hi, the same problem
https://www.reddit.com/r/Veeam/comments/1p7y4fw/comment/nr2nr5j/
Any workaround?
Thank you, RustFS is a great product!

[loverustfs]

Hi, the same problem
https://www.reddit.com/r/Veeam/comments/1p7y4fw/comment/nr2nr5j/
Any workaround?
Thank you, RustFS is a great product!

Thank you for reminding me. It is difficult to reproduce this bug.

We have found the reason.

#958

[loverustfs]

This bug has been fixed. #958

If a bug exists, submitting detailed information in the issue section will result in higher processing priority.

Users mostly ask questions in the discussion forum.

@acolada-gt @gabryp @ederidder59 @ramap-spec

[loverustfs]

A little update: we were just testing this new version and after deploy version 1.0.0-alpha.71, we can no longer access the console with our credentials. Has anyone else tried? Using Docker, by reverting to version 1.0.0-alpha.70, we’re able to access the console correctly again , same Docker Compose setup. Thanks a lot!

the console is only on port 9001 now. you cand edit the yaml file, or access the console using only that port.
@loverustfs The folder still cannot be browsed for me. After clicking the Folder button, the new error is now:
Failed to get S3 archive folders. There is no no node with specified name...
It opens a page with the bucket and I can click on New folder, but then it gives the same error

Thanks for all the support.

Ok, we'll handle it in #969 .

[gabryp]

@loverustfs On version 1.0.0-alpha.71 , setting the port to 9001, the console started working correctly again ! Thank you for this detail.
On the Veeam side, I can now proceed, but it reports that the bucket does not have the Object Lock feature. In reality, the bucket was created with this feature enabled, and its properties confirm it when checking from the console.

[acolada-gt]

@gabryp Did you create a folder in Veeam interface, or before hand? I still cannot browse the folders or create them. I am using region us-east-1. I receive that error when I click the Folder button and also when it opens, after I try to create a new folder.

For your problem, have you tried to create another bucket with UID 10001(rustfs user) as owner for the folder?

Update: I have tested with a bucket without object lock and version and it works fine to list and select/create the folder.
So it seems there is a problem with immutability or rather with version control, because I have also activated just version control and had the same error.

[acolada-gt]

Also found this: https://forums.veeam.com/object-storage-as-backup-target-f52/idrive-error-craeting-storage-t84152.html

[acolada-gt]

@gabryp forgot to mention...disable retention and it will work now ith version alpha.72. Veeam documentation requires that you disable retention. Only object lock and versioning is required.
"If you enable Object Lock and Versioning features on an S3 bucket, make sure that you do NOT enable the default retention option. Enabling lifecycle rules is not supported, and may result in backup and restore failures."

Right now there is an issue with versioning in version 72, you can check #969 where I have reported the issue.

[loverustfs]

#985

[acolada-gt]

is it also available as a docker image?
thank you very much for your commitment.

[loverustfs]

is it also available as a docker image?
thank you very much for your commitment.

Got it. I'll check with the team to see if we can push out another release this week.

[loverustfs]

is it also available as a docker image?
thank you very much for your commitment.

Alpha.72 has been released.

[gabryp]

@loverustfs I tried to update to Alpha.72, delete and recreate the Bucket with OBJ Lock, configure it on a Veeam Environment but Veeam report that OBJ lock is not enable
Also the mc command show "Object locking is not enabled" on my bucket

[loverustfs]

@gabryp ,

Let's fix the bug in the issue, thank you.
#1066 (comment)

[acolada-gt]

@gabryp Does it actually work with a bucket folder named Veeam? From what I know Veeam creates a folder in the bucket with the name Veeam and inside it it creates another 2 folders and only after that it creates a folder with the name you specify in the interface.
Try a name different than Veeam.

[gabryp]

@acolada-gt i tried to: delete bucket, stop docker, set permission on datastore to 10001:10001, start docker, recreate the bucket, configure Veeam repository, create a folder backups from Veeam wizard, the same error