From Core to Scale | Cannot backup dataset to Backblaze

TrueNAS General
1

I imported my pool from Core to Scale.

I succesfully unlocked the “Documents” dataset

I cannot create a backup task to Backblaze because the dataset does not show in the dropdown. It was working fine in Core.

What’s wrong ?

image
image1022×441 14.5 KB

image
image426×701 14.7 KB

2

Maybe it’s a new safeguard that they designed to prevent cloud tasks being configured with unavailable paths if a dataset is locked?

You can probably override this by manually typing the path in the “Directory/Files” text field.

3

I just tried to no avail.

The dataset does not show in RSYNC tasks either

Here are the actual permissions.

image
image421×332 5.23 KB

The SMB share is working. From Windows, I can access the dataset, create and delete a file.

4

What was the error message?

5

Because the new system is in a construction phase and located in my study room rather than downstairs, I turned it off last night.

This morning, after reboot, I tried to replicate the problem to snapshot the screen and the problem is solved.

Conclusion:

  • System was turned on
  • Pool was inported
  • Dataset was unlocked
  • Dataset share was working perfectly but:
  • Dataset was nos avalaible for rsync or cloud backup task
  • System was rebooted
  • Dataset was now fully functionnal

Is this a bug that should be reported ?

6

It might be a bug or an oversight of a safeguard feature. The middleware might populate a list of “usable paths” for a cloud sync source. If the dataset is currently locked when this happens, its path might never be “available” until the next reboot or middleware restart.

7

At first I thought you were talking about ZFS. :wink: