A backup system where the admin can see the backup state of all backed clients. It should also run on low resources servers and on Synology NAS. It is similar to "Active Backup" from Synology, but can be run on any Java supported operating system and NAS models, which are currently not supported by Synology.
The server is a very lightweight container.
It provides an HTML5 GUI where the client(for windows, linux, mac) for the machine is provided from where the HTML5 is visitided.
Every user from every machine can visit the servers HTML site, download the client and begin a backup. But a regisration is necessary that only this user is able to start a recovery using the backupd data.
The backup admin can visit an admin area where he can see
- the backup clients
- the last time when each client contacted the server
- the timestamp when the last file was backed up
- the file structure of the backed up files, including the size
- encryption of backed up data
- optimized network usage
- performant backup
- keep history of files
- A Synology package even for ones with low resources
- recovery of all files
- reocvery of single files or directories
- reocvery to the defined timestamp
I would describe the current state alpha. I need setup and run it on my machines to get an impression how stable and how efficient it runs.
When it is sufficient I'll would create the first beta release, which can be used already, but I would expect that problems occur.
Finnally, when those problems are solved, I will create the first stable release.
- Users who are familar with computers can allready run the server and the client.
- Backup works already
- Installation/Configuration descpription
- Recovery
- Security
- Client state feedback to the user in the toolbar
- Automatic client installation
- comfortable client configuration within a GUI
- comfortable server configuration
- client configuration on the server which sends the update to the client
- automatic client update
- manage that some of reported errors are ignored
I was getting frustrated by the performancd of the server application. The file upload was realy very slow. Furthermore the code gets confusing. Therefor I started reimplementing the server backand. What I plan to do(or did already) is to
- migrate from Spring to Quarkus
- provide a native image at least for raspberry
- separated the one server backup service to a file upload and and a backup command
- reimplement with DDD, CQRS and Event-Sourcing
I started on a new branch an will merge back when the migration is finished