Please add database backup step during upgrade storage node. I see a lot of SNO have issues when storagenodes upgrade to the new versions. In most cases database is corrupted, and have possibility to recovery from backup is very ipmortant
Jul 11 2019
Enter a subject
Log in / Sign up
Identify yourself with your email address
You won't be notified about changes to this idea.
Hash SNO errors. If the hash is unique, send the error to storj. Storj stores hash. Future SNOs check storj to see if it is known issue and whether SNO should be concerned about said issue
Use the given email address from the docker run command to send monthly reports with detailed information about your node (payout + surge payouts + held amount, storage, traffic, reputation, uptime, possible improvements and an overall score for example) and notify users when their node goes offline (without a third party service)
Allow for a storage node to perform planned maintenance
Use more threads when generating keys for a new node.
Email notification in case the node goes OFFLINE
Storage node with proxy ( i.e. without portforwding need)
A possible solution for SNO data loss/drive failure protection (in comments)
If every one could storj storage node's reputation easily. Then the nodes' quality could be impoved precisely.
Multi-HD setup for a single node
Remote api monitoring of node statistics and status