With "disaster recovery" I mean solving the problem of current single point of failure that only the uploader node has access to the data. At present if you lose your node by a system crash, crime or any other reason you lose your data uploaded to the network...
Backing up the node is not trivial as the node data files change continuously and you can lose your data if you lose the latest revision of the node data (particularly the "current" revision of storage contracts with hosts).
Can you elaborate on this a little more? Why do "node data files change continuously" - is this because the schema definition of the files is altered with each Sia client release?
It obeys the limit for a while but periodically ignores it as if some features obey the limit but not others.
I set it to about half my bandwidth: maxupload=400000
About 2 minutes later nethogs reports siad upload as 800Kb/sec (my maximum bandwidth)
A few minutes later it's back down to 400K
This cycle repeats, which makes sia unusable because when it jumps up and hogs all my bandwidth, everything else on my network comes to a screeching halt.