Hello,
I just finished my “new” TNS backup server - installation went smooth with 25.10.0 and everything worked.
Then I started to replicate the encrypted datasets from my TNS-Filserver to the TNS-Backup (datasets also encrypted), afterwards I unlocked the datasets with the key. I can access the files via SMB on my W11 workstation.
BUT
If I want to move or delete a file, or folder from the TNS-Backup I get the following error message “The disk is write protected. Remove the write protection or use another disk”.
The SMB user has FULL CONTROL.
Are there any limitations inherited from the replication, or any thoughts how be able to have full control via SMB about TNS-Fileserver (works) and also TNS-Backup (only read access right now)?
By default data that is replicated is read only set at the dataset level.
This is by design as if you change data on the backup system it will be wiped out at next replication.
Assuming you do not plan on replicating anymore and you have severed the tie then you can simply set the parent zfs dataset to readonly=off and you should be good to go.
I didn’t know, but it makes sense !
I’m rebuilding the storage pool and therefore need to get all the data from TNS-Fileserver to build a new pool.
1 Like
Everything set-up and it works 
I had to calculate the “optimal” special small blocks size for the sVDEV (I choose 8k).
I just started to copy the data from my Windows 11 Workstation to the SMB shares, but when trying to copy large amounts of data at once, e.g. 1TB, Windows tells me that there is not enough space… BUT I was able to copy chunks of up to 650GB at once.
Is there any specific limit or config on the TNS side, which prevents copying these large amounts of data?
