Nas Filer to S3 - Problems with Repository Configuration

[HansMeiser]

Hello,

currently i do some tests with an S3 backend and storing data to S3.

I have two S3 Backup Repositories, one for performane and one for capacity. These both repos are bound together to a scale-out Repository. I have a job which is storing VMs to this backend, this is working for some weeks.
Now i want to do the next step and store unstructed data from my NAS Filer to S3. Unfortunately i cant choose the scale-out repository as backend for the file job. I assume scale-out repos have some limitations.
So i created a new S3 backup repo with same bucketname, but with different folder. Creating was accepted but it seems to be not really useable. The overview is missing data on free and used storage space.
When creating a new filejob it is possible to choose my new repo, but when clicking on "Next" i get the errormessage: "Multi bucket-repository is not supported as primary backup repository".

So what would be the best solution in my case?. Do i need a new bucket on my S3? Or was it a mistake to combine my two S3 Repos to a scale-out repo?
Iam not really familiar with S3 yet. I hope you can give me some clarity.

Thanks,
Hans

[Mildur]

Hi Hans

Unfortunately i cant choose the scale-out repository as backend for the file job. I assume scale-out repos have some limitations.

Correct, the SOBR Capacity Tier is not supported for File Backup jobs. Same for Object Storage in Performance Tier. This limitation is documented in the Help Center.

but when clicking on "Next" i get the errormessage: "Multi bucket-repository is not supported as primary backup repository".

Please create a new repository and ensure that the Multi-Bucket option is disabled during setup.



Best,
Fabian

[HansMeiser]

Hello Fabian,

i tried, but when choosing a folder the "automatic bucket creation" is auto-enabled and i cant disable it. What am I doing wrong?

1 year ago i testet with a self-hosted S3 with min.io on a local linux computer. https://www.min.io/
this repo is still available and i can choose it in job-creation. "automatic bucket creation" seems to be enabled too, but it is working as expected. Repository type is S3-integrated and icon is a big blue bucket. My new S3 repo has type S3-compatible, and icon is a smaller green bucket. Are there different types of S3 repos?

Thank you,
Hans

[Mildur]

You need to create a new folder. If you select an existing folder that was used with “automatic bucket creation,” this feature cannot be disabled.

MinIO supports our Smart Object Storage API, which provides additional capabilities such as automatic load balancing and available/free storage reporting.
That’s why it is displayed as S3-Integrated. S3 Object Storage instances that do not support the Smart Object Storage API are displayed as S3-Compatible.

“Automatic bucket creation” seems to be enabled too, but it is working as expected.

That’s unusual, since for Object Storage using the Smart Object Storage API, automatic bucket creation should be automatically disabled.

Best regards,
Fabian

[HansMeiser]

I think the problem is based on the two S3 backup repos which build my s3 SOBR.
The two S3 backup repos already use 2 different bucketnames but same foldername.
Repo1: Bucket: veeam-performance Foldername: Veeam
Repo2: Bucket: veeam-capacity Foldername: Veeam.
Both repos exist on same S3 Server, so it is already a multi-bucket repo and not usable for file-backups. This explains why i could not deactivate the "automatic bucket creation" while creating a new backup repo.
I could end the SOBR, but i assume the basic S3 repo is still not usable.

So the basic mistake is to have 1 S3 Storage with multiple buckets. It should be different S3 for performance, capacity and archive or same S3 but with only one bucket but different foldernames.
Can you confirm my assumption?

Thanks,
Hans

[Mildur]

“1 S3 Object Storage with multiple buckets” is perfectly fine.
Just create a third bucket for your NAS backups and disabling automatic bucket creation during "New Repository" process.
If that doesn't work, please contact our customer support team to investigate the issue.

Best regards,
Fabian

[HansMeiser]

Ok, i will try to find an admin who is able to create a new bucket and see what happens within veeam.
but iam slightly suprised by this suggestion, because i found this in S3 Limitations:
"You cannot use S3 compatible repositories with multiple buckets as a target repository for Unstructured Data Backup. This includes backup, archive, or secondary repositories."

I'll get back to you as soon as I have any news.

Thanks,
Hans

[Mildur]

Hi Hans,

Thanks — it seems the wording in our Help Center is a bit confusing.
When we refer to “S3-compatible repositories with multiple buckets,” we mean “repositories with automatic bucket creation enabled”.
I’ll reach out to our Help Center team to see if we can make it less confusing.

Best regards,
Fabian

[HansMeiser]

Hello,

we created a new bucket in our NetApp and i tried to configure it in Veeam. On the "bucket"-tab i disabled automatic bucket creation, but it enables itself again after choosing the folder. At this point it is not allowed to disable automatic bucket creation.
I try to use the new backup-repo, but within a file-job i get the same error-message: "Multi bucket-repository is not supported as primary backup repository"

Hmm, what to do now?

Thanks,
Hans

[Mildur]

Hi Hans

That’s unexpected. Could you please open a case and provide our support team with the logs?
Once done, kindly share your case number here.

Best,
Fabian

[HansMeiser]

Hello,

ahh, i got it working now. I had not only create a new bucket, i needed to create a new Folder within new bucket too. At this point "automatic bucket creation" remains disabled and i could create my filejob.

Thanks,
Hans

P.S. My Filejob is working with some smaller volumes, an other testvolume in size ~3T fails with:
04.12.2025 14:07:51 :: Error: Agent: Failed to process method {NasMaster.CreateBackupProcessor}: The system cannot find the path specified.

Will this never end?

[Mildur]

I’m glad to hear it’s working now.
For the error you mentioned, please contact our customer support team; as stated in our forum policy, this forum is not a technical support. It’s best to let our support team review the logs and investigate further.

Thank you,
Fabian