Non PVE backup at scale

[cyruspy]

Hello,

Much to my dismay, I've came across a heavy Windows usage environment, with not all running on PVE (yet?).

I would like to write a native Windows client, with proper signage and a msi installer to simplify its lifecycle.

Also, I believe we need a scheduler to centralize management of the backup jobs (when should it run, did it run?, did it fail?, execute pre/post scripts, etc), going machine by machine to schedule a push backup doesn't scale. This layer will take time to build but I feel it-s missing, and probably should belong to PBS/PDM.

Is something like this of interest to any other user?

 

[Supaman]

If you are looking for a project: there is currently no proxmox backup client for windows with the full feature set of the linux client. all aof the the existing windows clients do not have encryption support.

 

[cyruspy]

If you are looking for a project: there is currently no proxmox backup client for windows with the full feature set of the linux client. all aof the the existing windows clients do not have encryption support.

Oh, yes. The 1:1 CLI native client for Windows is in progress. The next challenge is to fund the usd 300 yearly certificate to make Smartscreen and SecureBoot happy (MSI installer + NBD kernel driver).

While thinking beyond that point is that I thought of follow up options:

A- small system bar menu for the users to execute backup/restore
B- full Windows front end like Nimbus Backup Client
C- A proper central orchestration

With a fleet management responsability, I would pretty much prefer C. Per NIST recommendation the client shouldn't be able to mess with its protection rules & jobs.

Gave it further thought last night, and comparing PBS to solutions like Commvault, probably it's a good approach to leave PBS as the "data mover or muscle" and create a separate brain/orchestration for jobs scheduling and compliance (like Commvault's Commserv vs Media Agent model).

For home users, A is probably a nice fallback.