Pop!_OS (Linux)
Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.
Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.
Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.
Links
Guides
Hardware
Recommended
- !system76@lemmy.world
- !linux@lemmy.ml
- !opensource@lemmy.ml
- !linux@programming.dev
- !linux_gaming@lemmy.world
- !linux_gaming@lemmy.ml
- !selfhosted@lemmy.world
- !rust@programming.dev
- programming.dev
- fosstodon.org (Mastodon)
- !redox@lemmy.world
Community Rules
Follow the Code of Conduct
All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct
Be helpful
Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.
Critique should be constructive
We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.
This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.
Don't post malicious "advice"
It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.
Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.
No personal attacks
Posts making a personal attack on any user will not be tolerated.
No hate speech
Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.
view the rest of the comments
The real problem here is that you are not trusting the backup tool you selected. You are right to be paranoid of course....I am. Testing the backups is something we all should do on a schedule.
You don't want to restore the entire image for fear it won't work, and currently have no other option to test it.
Leap of faith with your untested restore is not adviseable either.
Ugh. Either you need to find another machine with enough space to teat the restore 1st, disconnect the drive and mount,.... Don't know how you could proceed otherwise.
Thank you. Of the folks who have engaged me over the past few years trying to find an adequate backup system, you're the first to tell me that I'm indeed not missing anything and that this cannot be made to work the way I'm expecting. I find that comforting.
Now I have a way to move forward: to back up a 1 TB drive, I can partition a 2 TB drive in half, back up to an image on one, restore that image to the other, chroot, and check that that worked.
Wasteful, but workable.
Thank you.
You're welcome. Like many, I dumpster dive for a lot of my equip. If you van getcyohr hands on almost any other machine with large enough drive, that would be good enough to test your clonezilla restore.
On my daily driver, I use nextcloud for document/photo sync so that I immediately have 2 copies. Then a weekly backup to external storage 1 time per week of my home folder.
Remember to test the backups every so often. Make sure you keep a copy of data offsite too(fire,theft,etc)
And its morbid, but I left instructions for my kids on how to gain access to backups in case I'm gone so they can keep pics and bids from my stash.
Oh yes, I tried testing my Clonezilla restore on an older laptop, but after logging in, the keyboard and trackpad stopped working. I wondered if that was a hardware incompatibility problem, since the keyboard and trackpad worked fine at the greeter screen. 🤷
Indeed, I have a lot of redundancy for critical documents, including a restic backup to Blackblaze and many many git repositories. What I don't have is the "Get back to work quickly when the internal drive dies" that SuperDuper gave me on my Mac. That's the missing piece I'd like.
And, as you noticed, since I was struggling with testing the Clonezilla backup, I couldn't possibly trust it. Now, at least, I have a plan.
And yes, I have onsite backups, offsite backups, and a succession plan.