The github issues about this seem long dead.
This is probably the best place to track it:
And this is the Qubes issue for it:
So it seems long way off still. Is wyng stable enough already to reliably use it with CLI “at-your-own-risk”?
I see reports from users who happily use wyng, and also reports and
questions in the forum from people with issues. You could review these
yourself, and then decide whether to use is at your own risk. If all
that you want is the ability to get back your qube at a specific point
of time, wyng may serve your purpose.
I’ve said before that it doesnt provide any of the features that I want
in a backup. This is by design: it works at the volume level.
Want to find a file that you deleted some time in the last month or
year? Restore EVERY backup that you took, and look through the volumes
til you find it.
Want to find a specific version of that file you were working on? Again,
restore EVERY Wyng backup and check until you find it.
Note that if you have also added a large quantity of other data in the
meantime you have to restore ALL that data until you find the one
file you are looking for.
I believe that you also have to shutdown a qube before running Wyng on
it.
I focus on incremental backups of data (daily, hourly in some cases) and
use the Qubes backup only in specific cases.
I see. How would I do automatic backups of data in every qube though? I would have to attach some external drive to all qubes one by one which breaks isolation?
I use a disposable and attach the private volume as explained in the docs
Backup that data. If the qube is running then I attach ro the snap
volume, and mount it ro, to access the data.
This is readily automated in a batch file. Remember to attach ro and
mount ro.
This allows me to back up data from important qubes on an hourly basis,
and other qubes at set interval, and access data easily for restore. The
backups are encrypted and can be moved offsite as needed.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.