#22

thx refi64 … my system files … isn’t that enough? i need only “my” flatpaks, layered packages, settings of the layered packages, containers (in the future) & home files. possibly not possible at present, but not impossible.

edit: well, i’ve calmed down again. the world isn’t perfect (as far as this mozilla/google - attitude is concerned). there will be some changes. i can wait. on the subject: done. i flattened the silverblue image on the ssd over windows and after the installation i had access to my second hard drive (the previous version) and all its files. flatpaks and chromium had to be installed again. sb on the 2nd hard drive deleted afterwards. rpm-ostree upgrade worked without a workaround this time and the system now boots noticeably faster. auto-updates are set. ready to learn & ready for the future (… without ff & co. - again).

#23

Are you meaning the rpm-ostree? There are ways to refer to your previous meta-data of ostree installs that you can use to get back to a particular state of the OS, external to the Flatpak setup or user data.
First, in a terminal type rpm-ostree status. This will get the commits you have, namely your current and previous. What you are interested in here is the name of your remote, in my case the result looks like below, clipped for brevity

Screenshot%20from%202019-02-25%2009-47-39
Screenshot from 2019-02-25 09-47-39.png1355×156 12.7 KB

The name of my remote is fedora-workstation:fedora/29/x86_64/silverblue. Using that name in the following command will allow me to “look back” at my previous ostree commits
sudo ostree pull --commit-metadata-only fedora-workstation:fedora/29/x86_64/silverblue --depth=5 five commits. You can make the command option --depth=-1 to go back to the beginning, a lot of info. From there you would deploy a particular commit you were interested in.

#24

wow, thx jakfrost.

yes, i meant rpm-ostree. and yes, i have already “rolled” back and forth & pinned a deployment for security reasons if something goes wrong with my newbie-experiments. also my re-installation a few days ago on the ssd was without problems.

but before this migration i was wondering if it is possible to save a deployment resp. metadata (i.e. the installed flatpaks) on a stick, to upload this data/deployment to the fresh re-installation later. so i wouldn’t have had to re-install the flatpaks (+ settings) and layered package (+ settings) again. a “little” backup (on a stick, not in a “cloud” or whatever), based on the structure of the os itself, without 3rd party tools.

but unfortunately that is technically not possible, i was told here. which is not bad. it was just a thought of mine.

anyway, " … pull --commit-metadata-only …" was completely new to me and is extremely helpful for the future - thank you for that!

#25

If someone manages to Flatpak package Vorta then you will have what you’re hoping for!

1 Like
#26

flatpak create-usb Could be the answer for backing up your flatpaks. I haven’t tried it as of yet but definitely will in the future. I don’t know if you have to do them individually or whether you can bulk create-usb. It looks like you can specify an app/runtime or just the user or the default of the system.

#27

FWIW just to be clear, this does not back up any app data (e.g. stuff in ~/.var), which would have to be backed up separately.

As a side note, IMO that’s where the complications of trying to take advantage of deployments for backups arise, since you still need some more traditional tooling to handle the actual, err, user data. (I’ve had some ideas on modernizing this in an OSTree-/atomic-style way for a long time but haven’t gotten around to it yet.)

#28

yep & thx again jakefrost,

this is exactly the reason why i asked this question at this point in the first place. flatpak -help gave me (on my first day with f29 silverblue) exactly this output: “create-usb -> put applications or runtimes onto removable media”. but i just quickly overread it (i had more important things to do at this point). still something unconsciously stuck. now that you mention that, it’s clear again why i’m asking at all.
so, it is possible. if only sometime in the future. that’s ok. i honestly don’t have the courage to try this option yet.

but even that is not satisfying, because layered packages & containers should also be able to be stored offline on a stick - in this way. firstly, because offline - capacities (against this “cloud madness” known from ms & co.) have to be promoted:

empowering the next billion with ostree, flatpak, ndn, … [edit: but imho not the “cloud” - see r. stallman about this dangerous construct + smartphones/mobile-phones are only a threat in these days; therefore the “monolith” in this video only represents the nsa & co. - these are also facts]

… and secondly because 3rd party applications are imho not a “solution”. there should be the possibility to perform secure offline (mini) backups via the os (architecture) itself (if possible and if this does not violate security aspects).

and i still think that ostree would be suitable for it, even though i can’t come up with a technical solution because i learned something else (unfortunately in this context).

maybe, some ideas (refi) in “modernizing this in an ostree/atomic-style way”, are the future too (just like “flatpak create-usb”). you are all intelligent, passionate people, lightyears ahead of most of the other linux distros. i have no doubt that you will find a solution to this backup - problem (and i perceive it as a problem, also as a security - problem). at least as far as flatpaks alone are concerned, maybe i will play with it (i can always roll back).

thx. and still no problem with sb on my system. it is stable like granit.

uhh: ostree create-usb & flatpak create-usb (e.g. “system”: flatpak create-usb --help ). but a little too cyrptical for me.

#29

I understand that @refi64, it does allow for the backup of the flatpak installation on the system from what I could tell in the help for the flatpak command. That is part of the answer in this case since there is no one stop solution for this problem as of now. Indeed, even if Deja-Dup was working correctly as a flatpak, it still wouldn’t back up the layering and flatpak installations. The layering, ostree, and flatpak states should be able to be captured in metadata I would think since this is the Git of OS’s.

#30

I hope it is helpful, what you are asking for in Silverblue has been asked by others and will continue to be the case until a solution is derived. flatpak create-usb With no options I think will create a usb of your flatpak installations, but I don’t think I have a usb thumb drive large enough for what I have installed. I browsed the app directories with tree, they’re huge. That’s why I think saving the metadata of the ostree state with the layering information, and the metadata of the flatpak’s installed, along with the user data (traditional backup) is the only way to achieve what you are asking. On a side note, but related, I have forgone traditional backups on my personal system for some time, read years. I use the file-roller (Archive Manager) or simply tar.gz the files I want backed up and store them onto an external HDD, the caveat being I have to be organized up front. Git is also another useful tool in this regard, again up front organization is required.

#31

Oh yeah I wasn’t disagreeing, just wanted to make sure it was entirely clear to anyone else stumbling upon this thread in the future.

#32

True, the conversation tends to meander. I didn’t take offense in any case, my skin’s pretty thick. I come from a large family, lot’s of siblings and cousins, and friends with too much time and well developed senses of humor.

1 Like
#33

Is this available as a Flatpak or would layering be required?

#37

Can an admin please split this browser discussion into a new topic? It has nothing to do with Silverblue backups…

#38

Hi all, please keep this thread on topic to the thread title. If you want to keep the conversation about browsers going, please start a new thread. Thanks!

#39

Instead of hiding off-topic posts, can’t you split them into a new thread? (Discourse offers such a feature, I have seen it used elsewhere…)

#41

@rugk It might be done with a plugin. I don’t see an obvious way for me to split the posts into a new thread as of now. Maybe @sanja knows a way.

#43

Also if you like deja-dup it is now working on silverblue with the latest release.

#44

@jakfrost & co. : i tested endless os for a while. the only function i found imho useful was the straightforward gui - option to load each flatpak onto an usb-stick (even if it didn’t work lol). i’m sure silverblue/gnome can do it in future. sry that i was o.t. & angry (happy with iridium for fedora; i’m free to choose on sb).

#45

All good then,

Cheers!

#46

BTW as for backing up flatpaks I found this useful blog post:

Unfortunately, that user experience there is not really nice… :smile: