Strangely, I can create an initial task where I “Add New” and have it create a bucket. I supply it with a folder name as well. When I run the task, it works flawlessly.
Then I go in and create a second task and I want to reuse the new bucket but with a different folder name. However, when I create the new task, select my credentials, and click the bucket dropdown list, the bucket that was created in the first task is greyed out. Obviously I could “Add New” and create a second bucket, but that isn’t what I want.
My credentials are using the ones created by the TrueNAS application in the applications list and I gave it “Full Access” to the project (not what I want but I needed to eliminate permissions as an issue).
Is TrueCloud Backup only able to use each bucket for a single task?
Yes, one bucket per task or backup dataset.
Think of a bucket as equivalent to a dataset… they are free to create. The data is organized so that bucket is cleanly aligned… if you want to restore some buckets to another NAS you could.
If you want to delete a bucket and a specific backup, it can be done safely.
1 Like
Thanks for the reply!
Yeah I read that entire page and it wasn’t clear that was the case. I understand that buckets are free to create but having 60+ buckets for each backup is going to be unwieldy. I was hoping that I could do like I do with my cloud sync tasks and have a single bucket but use different folders within the bucket for each task. 
It’s also the case that it’s disabled if I create a bucket on Storj and then go into TrueNAS and try to select it. After re-reading that page for the 5th time, it looks like that isn’t supported and that only “Add New” is. Again, very unintuitive.
At the very least, I think it might be a better user experience when a disabled bucket is listed in the dropdown if it said next to the bucket name why it’s not able to be selected.
@Captain_Morgan The other thing that’s odd is that, if there’s supposed to be a bucket per task, then why is “Folder Name Required”? If the only thing that’s going to exist in that bucket is a single task?
If the datasets are all organized under a single dataset, then only one bucket is needed. Isn’t that the case for you?
That would be fine except that many of my datasets require different configuration options (number of snapshots kept, schedule, hooks, etc)
Also, there’s the fact that Storj only allows 100 buckets without paying for more. If I’m coming even remotely close to that limit as a personal user, it seems like “one bucket per task” is going to be a larger problem.
