title: Creating ISO of current Garuda Setup - Issues & Assistance - Garuda Linux Forum
source: https://forum.garudalinux.org/t/creating-iso-of-current-garuda-setup/18186/10
author:
- "[[Garuda Linux Forum]]"
published: 2022-03-18
created: 2025-03-13
description: I want to create ISO file of my current Garuda Setup with all files, config, etc. So when I have to reinstall it sometimes in case of system brick (I often brick something by playing with different linux things and that …
tags:
- Backup
- Software
- Computer
- Help
If you want to clean this up a little, you can pass the -a
flag–it includes -rlptgoD
all with one flag. You don’t have D in yours but it can’t hurt I think (preserves device and special files). -v
is also incuded with --progress
.
This looks like an auto-mount value. I would recommend making a directory for the device and mounting it, to avoid getting a different value every time you plug it in.
If this is the name of a folder, I would suggest renaming it with an underscore or something to get the space out of it. You might be able to capture the path with quotes or escape the space with a backslash, but these little tricks sometimes do not work properly if you want to run rsync over SSH. That might not matter to you, but best practice is to avoid spaces.
If you are going to back up your whole system, there are certain folders Arch wiki recommends excluding:
The
--exclude
option causes files that match the given patterns to be excluded. The directories/dev
,/proc
,/sys
,/tmp
, and/run
are included in the above command, but the contents of those directories are excluded. This is because they are populated on boot, but the directories themselves are not created./lost+found
is filesystem-specific.
Honestly the Arch Wiki suggested full backup rsync is pretty good as-is. If you want to check out the article they explain why they’ve set it up this way also.
# rsync -aAXHv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / */path/to/backup*