linux-0xkw:/home/daka # kdesu backintime
kdesu(16056)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
KCrash: Application 'kdesu' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/root/.kde4/socket-linux-0xkw.site/kdeinit4__0
Warning: connect() failed: : Connection refused
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
drkonqi(16057)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
linux-0xkw:/home/daka #
I would have never known if you had not told me. Thank you for your help.
Do you agree that this “backintime” is the best solution for me to create incremental backups once per week that I will save to an external USB hdd that is formatted as NTFS?
it is quite possible that someone else wrote those applications and the backintime author doesn’t know about them, that’s the beauty of open source a lot of people can compliment your work.
but that directory is your entire Linux system including external hard drives and the internet, only back-up your home dir/partition (or parts of it)
so try again but only do it for **/home **there is little point in backing up everything else.
Nothing wrong with it thee are several backup programs. I suggest that you go to yast software management and check the box search in description and search for backup. You will get a whole bunch to look at.
Personally I format the USB stick as ext4 (no journel) and use Luckybackup, which uses rsync to backup. This way it is a proper Linux FS and once the first backup is done it is very fast only writing changes.
There is something to be said for incremental it acts a time machine so you can go back to the main if needed. But restore can be a pain since you have to go to the original backup first then move through.
For me a simple backup is good. I will start doing multiple rotating versions to allow for failure of backup media. USBs are dirt cheap
Basically I want to backup a “known good configuration” of the entire system to quickly recover the entire system from a disaster. Basically I am trying to create an enterprise image for disaster recovery.
No need for :shame:. Every one of us had to learn from scratch some time. And remind, these forums ae the place to ask, to ask for further clarification and to ask more. That is what they are for.
This is a very worthwhile action, but somewhat different than what is intended with Back in Time. The main requirement for disaster recovery is having the image on separate media, and a bootable medium that runs a system to restore it. When the primary hard drives dies, something else must boot the system and execute recovery.
I use Back in Time to do nightly backups of select, important files that are revised frequently.
If you’re looking for an alternative, I can highly recommend extundelete (as the name implies, it only runs on ext file systems) http://extundelete.sourceforge.net/
As expected,
Once you set it up, it will automatically make a backup of any files that are changed.
Although there is no GUI, it’s very simple to setup and run, you just follow the questions you’re prompted and it runs.
When I last looked at it, it only supported one disk. It wouldn’t access any other disks, so everything you want protected has to be on the primary disk (whatever partitions).
That looks good. I will create an image with CloneZilla and then use one of the other tools (probably luckybackup) to run more specific backups every 3 days (incremental). And every 3 months I will make a new CloneZilla image and purge the old one.
