Project Name: Proxmox Backup Cloud Extension
Project Lead: Rodney Wild
Company: A-Z Computer Solutions
We propose to increase the amount of stored data on the Sia network. At the moment there are a low number of big renters uploading data to the sia network. We propose to develop a cloud backup module for proxmox backup that would take proxmox backup data and hold a replication of it at an external service provider. This can be done directly via a local sia host or a satellite when that service is complete. Proxmox backup server is a great candidate for using sia because of its large data sets. Even a basic proxmox backup can be TBs in size and if freely adopted could put many petabytes of data onto the sia network. Backups out in the sia network add an extra level of redundancy to local backups should a disaster recovery scenario happen and allow businesses that use the PBC extension to have a greater level of recoverability from disaster situations. For example, if the business or data center where their primary backup data is housed burns down to the ground or gets flooded. When it comes to backups, we think it’s a good idea to have the original running host, an on-site backup, and a fairly recent off-site backup just in case something happens for business continuity purposes.
The project source code shall be maintained in a public repository located on Git Hub.
The project shall have the following milestones:
1 Month – 1, 1.1 & 1.2, 1.3: Setup a Proxmox VE environment, Build and deploy a test instance of PBS, Study the PBS contribution guidelines
2 Month – 1.4, 1.5: Study the PBS tape feature, Start Starting to Build the cloud backup feature
3 Month – 1.5: Continue Building the cloud backup feature
4 Month – 1.5 Finish Building the cloud backup feature
5 Month – 1.6: Start Building the sia renterd plugin
6 Month – 1.6: Finish Start Building the sia renterd plugin
7 Month – Beta Testing of Cloud Backup System and website development
8 Month – Release
Please note that the above milestones are based on times provided by the developer and adjusted by the project manager.
Non-adherence to Proxmox Backup Server’s (PBS) development guidelines could lead to non-acceptance of the cloud backup feature in PBS’s code repository, making the project maintenance-intensive.
The other rise would be the loss of a developer once the project is started and not being able to find another developer.
I am not a developer.
Impact of Identified Risks:
The first risk could substantially increase the project’s dependency on maintenance.
The code could be cloned and modified in a new repository and needs to be systematically updated to align with the ongoing changes in the original PBS code.
Having backup developers or redundant resources is essential to maintain project continuity in case of any resource unavailability. As I started the hiring process with an agency, I think that the risk is low. I also already have another developer That was identified via our testing evaluation process that was very close to the current developer that I can call on should this be required.
Monitoring and Managing Risks:
Continuous monitoring and managing of the identified risks are crucial.
Risk mitigation strategies should be revised as more information becomes available and project conditions evolve.
The project is requesting 80,000 USD, for the following 8 months. The spending can be itemized as follows:
70,000 USD shall constitute the developer’s salary, paid monthly or quarterly, at the discretion of the Foundation, at the beginning of each period. This person will be a hired position.
1,000 USD shall be used to pay for the project infrastructure (test servers and environment, subscriptions, etc.) for the duration of the project, paid upon completion of Phase 1.
2,000 USD shall be used for testing of the product (we plan to have a number of people do testing of the modules and will cover a small subsidy to cover the cost of people testing the product while it is in beta similar to the way the foundation has incentivized participation in the testnet).
7,000 USD paid to the project manager of the project to cover administrative and support costs
The progress of the development shall be reported on a monthly basis in the community Discord.
The project lead is kindly asking the Foundation to review this proposal. He is also encouraging the community to ask as many questions as needed to improve the clarity of the project scope and the expected outcome. Our goal is to increase the amount of data on the sia network and increase the level of redundancy of backups in the proxmox virtual environment and provide for disaster recovery.
Will all of your project’s code be open-source?
[Projects can use closed-source components, but can’t develop closed-source code. If any of your project’s code is closed-source, please describe what code and why.]
There is a possibility that there will be extra functionality developed via additional plugins for other cloud platforms. but these will be closed source and a premium feature. Sia will be the only open-source plugin developed for the cloud backup project.
Leave a link where the code will be accessible for review.
Do you agree to submit monthly progress reports?
[Progress reports must be submitted monthly here in the forum.]
I agree to share monthly updates in the forum and on Discord.
There is an attached document with quite a bit more detail than his provided here. Although the research project looked at the possibility of an S5 and Satellite it has been determined that S5 is not advanced enough at this time and Satellite could be handled with the current renterd plugin code. Documentation will however be included for the setup of a Satellite renterd.
Link to supporting documentation: Removed, see updated submission.