El Belgicano
-----------------
Laptop: 5 years old Asus M6N (ATI9600/9700 graphics, 512Mb RAM, Intel Mobile 1.66GHz, 60Gb HDD) running 10.04-Lucid Lynx pretty nicely.
Ok so I was using this tar method for a while and had had some success with it, until not to long ago when I had to restore it because I was making some changes to my setup and for some reason it didn't work properly. wouldn't completely boot or log me in. it just kept dropping me down to the command line. The only cause that I could think of was that I was restoring to a different HDD but I changed the necessary UUID in fstab and the grub.cfg to the new HDD but still no success. In the end I just grit my teeth and started from scratch.
But I'm wondering now could it possibly have been caused from using the system at the time of backup?
Ubuntu 16.04 / Linux 18
“To mess up a Linux box, you need to work at it; to mess up your Windows
box, you just need to work on it”.
El Belgicano
-----------------
Laptop: 5 years old Asus M6N (ATI9600/9700 graphics, 512Mb RAM, Intel Mobile 1.66GHz, 60Gb HDD) running 10.04-Lucid Lynx pretty nicely.
i dont know if this has been mentioned before, but i use a USB external drive, and therefore I also exclude the /media folder since otherwise it would backup that drive as well...
The following is the script that I ran.
To restore it I manually ran the above changed to to the extraction equivalent.Code:#Back up the root drive. zenity --info --title="System Backup" --text='System back up of the root directory begun!' | tar -cvpjf /home/jonny/.BackUps/backup_root-desktop.tar.bz2 --exclude=/proc --exclude=/lost+found --exclude=/mnt --exclude=/sys --exclude=/home --exclude=/media / | cat > /home/jonny/.BackUps/Root_Backup_Log.txt zenity --info --title="System Backup" --text='System back up of the home directory begun!' | tar -cvpjf /home/jonny/.BackUps/backup_home-desktop.tar.bz2 --exclude=/home/jonny/.BackUps --exclude=/shared --exclude=/*/Videos /home | cat > /home/jonny/.BackUps/Home_Backup_Log.txt #Display a message to incate that the backup has finished. zenity --info --title="System Backup" --text='System back up has completed!'
I tried both extracting over a fresh install and to a blank formatted partition. I also tried running the "sudo update-grub".
I am right in saying that using the it is fine to use the system while running tar aren't I?
Ubuntu 16.04 / Linux 18
“To mess up a Linux box, you need to work at it; to mess up your Windows
box, you just need to work on it”.
I think you should tar with "sudo", don't you see something referring to this being a problem in your log?
For your question, think about this: "you don't tie your shoes while walking do you? your heart is beating, you're breathing, but you're not walking." Same goes for the backup process on a "running" system.
El Belgicano
-----------------
Laptop: 5 years old Asus M6N (ATI9600/9700 graphics, 512Mb RAM, Intel Mobile 1.66GHz, 60Gb HDD) running 10.04-Lucid Lynx pretty nicely.
El Belgicano
-----------------
Laptop: 5 years old Asus M6N (ATI9600/9700 graphics, 512Mb RAM, Intel Mobile 1.66GHz, 60Gb HDD) running 10.04-Lucid Lynx pretty nicely.
thankyou for your guide. i'm newbie for linux..
syahmei.blogspot.com
Hi,
Thank you so much for this tutorial.
I've read on www.ubuntu-fr that using "sudo su" wasn't much wise ; I cannot say that I've understood why. They seem to imply that using "sudo -i" or "sudo -s" was preferable. So, what should we do?
Thank you for the answer.
_____________________
I'm on Ubuntu 10.10, gnome.
Bookmarks