Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[RESOLVED] Restore with timeshift

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

[RESOLVED] Restore with timeshift

#1 Post by ticojohn »

I have, for quite some time, been using Grsync to back up my /home directory and I have recently begun using timeshift to backup my system(s). I have what may sound like a dumb question. Can I restore a backup from timeshift to a mounted system? I would assume not, and timeshift may prevent such action if it is not allowed. I am not sure why, if the system is functioning correctly, that I would want to restore to a mounted system but just want to know as it might save me some grief in the future. My desktop has three drives, each with Bullseye installed, so I should always have an operational system from which I can invoke timeshift.

EDIT: After using timeshift, admittedly for a short time, I decided I don't like timeshift as well as Grsync. One thing that bothers me a little is that there does not appear to be a simulate mode. I like that feature in Grsync and find it handy. So I am going to purge timeshift and just use Grsync. Not having a cron job taking care of backups doesn't bother me as I have a weekly routine of backing up things. So the original question is now moot. Post is now marked as RESOLVED.
I am not irrational, I'm just quantum probabilistic.

User avatar
bester69
Posts: 2072
Joined: 2015-04-02 13:15
Has thanked: 24 times
Been thanked: 14 times

Re: [RESOLVED] Restore with timeshift

#2 Post by bester69 »

ticojohn wrote: 2021-08-22 20:24 I have, for quite some time, been using Grsync to back up my /home directory and I have recently begun using timeshift to backup my system(s). I have what may sound like a dumb question. Can I restore a backup from timeshift to a mounted system? I would assume not, and timeshift may prevent such action if it is not allowed. I am not sure why, if the system is functioning correctly, that I would want to restore to a mounted system but just want to know as it might save me some grief in the future. My desktop has three drives, each with Bullseye installed, so I should always have an operational system from which I can invoke timeshift.

EDIT: After using timeshift, admittedly for a short time, I decided I don't like timeshift as well as Grsync. One thing that bothers me a little is that there does not appear to be a simulate mode. I like that feature in Grsync and find it handy. So I am going to purge timeshift and just use Grsync. Not having a cron job taking care of backups doesn't bother me as I have a weekly routine of backing up things. So the original question is now moot. Post is now marked as RESOLVED.
BTRFS + snapper-gui; Timeshift is overrated, better to use snapper-gui+btrfs
and forget headches for ever

Image

Image

Here, you can see all snapshots Ive right now of system, home, and DATA subvolumes:
Four years usinbg btrfs filesystem snapshots, there is no way back..

Ive never lost anything again neither resintalled the system again since BTRFS... this damn thing never get corrupted in my experience.. Im rolling back system and home five to 10 times every week in order to undo things or installations. dont waste a second and re-install over btrfs :o
ID 258 gen 23940 top level 5 path PARABORRAR/@cache
ID 259 gen 32541 top level 5 path @log
ID 278 gen 2072 top level 5 path PARABORRAR/data/snapshot
ID 284 gen 32541 top level 5 path MIDATA
ID 290 gen 23952 top level 5 path PARABORRAR/cache.del
ID 291 gen 32506 top level 418 path home/.snapshots
ID 298 gen 31985 top level 520 path rootsys/.snapshots
ID 300 gen 4828 top level 298 path rootsys/.snapshots/1/snapshot
ID 301 gen 32404 top level 284 path MIDATA/.snapshots
ID 304 gen 4901 top level 301 path MIDATA/.snapshots/2/snapshot
ID 315 gen 5898 top level 298 path rootsys/.snapshots/2/snapshot
ID 316 gen 5986 top level 298 path rootsys/.snapshots/3/snapshot
ID 318 gen 10088 top level 298 path rootsys/.snapshots/4/snapshot
ID 325 gen 7407 top level 298 path rootsys/.snapshots/5/snapshot
ID 329 gen 21323 top level 5 path PARABORRAR/@
ID 332 gen 13219 top level 298 path rootsys/.snapshots/6/snapshot
ID 335 gen 15844 top level 298 path rootsys/.snapshots/7/snapshot
ID 338 gen 16068 top level 298 path rootsys/.snapshots/8/snapshot
ID 339 gen 16195 top level 301 path MIDATA/.snapshots/15/snapshot
ID 342 gen 16637 top level 298 path rootsys/.snapshots/9/snapshot
ID 345 gen 16775 top level 298 path rootsys/.snapshots/10/snapshot
ID 346 gen 16798 top level 298 path rootsys/.snapshots/11/snapshot
ID 350 gen 17712 top level 298 path rootsys/.snapshots/12/snapshot
ID 359 gen 18682 top level 298 path rootsys/.snapshots/13/snapshot
ID 367 gen 19081 top level 298 path rootsys/.snapshots/14/snapshot
ID 369 gen 19204 top level 298 path rootsys/.snapshots/15/snapshot
ID 377 gen 19938 top level 301 path MIDATA/.snapshots/37/snapshot
ID 380 gen 20330 top level 298 path rootsys/.snapshots/16/snapshot
ID 388 gen 21334 top level 298 path rootsys/.snapshots/17/snapshot
ID 389 gen 21341 top level 298 path rootsys/.snapshots/18/snapshot
ID 390 gen 21358 top level 298 path rootsys/.snapshots/19/snapshot
ID 396 gen 23835 top level 298 path rootsys/.snapshots/20/snapshot
ID 416 gen 30681 top level 5 path del/rootsys-2021-08-27_06:49:31.log
ID 418 gen 32541 top level 5 path home
ID 421 gen 23942 top level 5 path PARABORRAR/cachevar
ID 422 gen 32541 top level 5 path cache
ID 423 gen 23970 top level 298 path rootsys/.snapshots/21/snapshot
ID 424 gen 24128 top level 298 path rootsys/.snapshots/22/snapshot
ID 425 gen 24628 top level 301 path MIDATA/.snapshots/54/snapshot
ID 426 gen 24804 top level 298 path rootsys/.snapshots/23/snapshot
ID 427 gen 24871 top level 298 path rootsys/.snapshots/24/snapshot
ID 429 gen 25182 top level 298 path rootsys/.snapshots/25/snapshot
ID 434 gen 25466 top level 298 path rootsys/.snapshots/26/snapshot
ID 441 gen 25836 top level 298 path rootsys/.snapshots/27/snapshot
ID 445 gen 26454 top level 298 path rootsys/.snapshots/28/snapshot
ID 447 gen 27180 top level 298 path rootsys/.snapshots/29/snapshot
ID 452 gen 27480 top level 301 path MIDATA/.snapshots/70/snapshot
ID 453 gen 27619 top level 298 path rootsys/.snapshots/30/snapshot
ID 459 gen 27985 top level 298 path rootsys/.snapshots/31/snapshot
ID 472 gen 28595 top level 298 path rootsys/.snapshots/32/snapshot
ID 482 gen 29234 top level 298 path rootsys/.snapshots/33/snapshot
ID 486 gen 30862 top level 298 path rootsys/.snapshots/34/snapshot
ID 489 gen 29673 top level 301 path MIDATA/.snapshots/90/snapshot
ID 495 gen 30522 top level 301 path MIDATA/.snapshots/95/snapshot
ID 496 gen 30868 top level 5 path del/rootsys-2021-08-27_07:49:40.log
ID 497 gen 30724 top level 301 path MIDATA/.snapshots/96/snapshot
ID 506 gen 31690 top level 5 path del/rootsys-2021-08-27_23:19:53.log
ID 507 gen 30907 top level 301 path MIDATA/.snapshots/97/snapshot
ID 508 gen 30967 top level 301 path MIDATA/.snapshots/98/snapshot
ID 509 gen 30996 top level 301 path MIDATA/.snapshots/99/snapshot
ID 510 gen 31016 top level 298 path rootsys/.snapshots/35/snapshot
ID 512 gen 31183 top level 298 path rootsys/.snapshots/36/snapshot
ID 513 gen 31217 top level 298 path rootsys/.snapshots/37/snapshot
ID 514 gen 31223 top level 301 path MIDATA/.snapshots/100/snapshot
ID 515 gen 31228 top level 301 path MIDATA/.snapshots/101/snapshot
ID 516 gen 31685 top level 298 path rootsys/.snapshots/38/snapshot
ID 517 gen 31403 top level 301 path MIDATA/.snapshots/102/snapshot
ID 518 gen 31501 top level 301 path MIDATA/.snapshots/103/snapshot
ID 519 gen 31616 top level 301 path MIDATA/.snapshots/104/snapshot
ID 520 gen 32537 top level 5 path rootsys
ID 521 gen 31700 top level 298 path rootsys/.snapshots/39/snapshot
ID 522 gen 31832 top level 298 path rootsys/.snapshots/40/snapshot
ID 525 gen 31985 top level 298 path rootsys/.snapshots/41/snapshot
ID 526 gen 31999 top level 301 path MIDATA/.snapshots/105/snapshot
ID 527 gen 32124 top level 301 path MIDATA/.snapshots/106/snapshot
ID 529 gen 32195 top level 301 path MIDATA/.snapshots/107/snapshot
ID 530 gen 32404 top level 301 path MIDATA/.snapshots/108/snapshot
ID 532 gen 32506 top level 291 path home/.snapshots/1/snapshot
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...

Marie SWE
Posts: 241
Joined: 2021-04-06 22:14
Location: Sweden / Linköping
Has thanked: 7 times
Been thanked: 9 times

Re: [RESOLVED] Restore with timeshift

#3 Post by Marie SWE »

Hi @bester69 :)
interesting... is it easy to set up? and is the restore process easy?
Why make things complicated in life, if you can make it easier for yourself... Do it. ;o)
You only have one life, so make the most of it and enjoy it while you can.

User avatar
bester69
Posts: 2072
Joined: 2015-04-02 13:15
Has thanked: 24 times
Been thanked: 14 times

Re: [RESOLVED] Restore with timeshift

#4 Post by bester69 »

Marie SWE wrote: 2021-08-28 02:26 Hi @bester69 :)
interesting... is it easy to set up? and is the restore process easy?

Installation

sudo apt install snapper snapper-gui

snapper is a daemon that takes snapshots that you can configure throught gui, it works like a kind of daily crontab by taking automatically snapshots, so yout dont need to be worry


restoring manually a snapshot
yes. very easy...as easy to take a snapshot and reboot; just like this.:

for system

(by default, installation usually names @ to subvolume folder / partition; i prefer to use "rootsys" name)
sudo mount -t btrfs /dev/sda1 /mnt && cd /mnt
sudo mv @ @.del
sudo btrfs subvolume snaphot @.del/.snapshots/34/snpahot @
sudo mv @.del/.snapshots @/ (move snapper .snapshots folder within new active snapshot)
sudo reboot

after reboot
sudo btrfs subvolume delete @.del


for home

sudo mount -t btrfs /dev/sda1 /mnt && cd /mnt
sudo mv home home.del
sudo btrfs subvolume home.del/.snapshots/12/snapshot home
sudo mv home.del/.snapshots home/ (move snapper .snapshots folder within new active snapshot)

after reboot
sudo btrfs subvolume delete home.del

You can also create a subvolume or folder and put in there all dropped subvolumes named with datetime just in case you made an error and needed back to those snapshots; just like this.:
ID 496 gen 30868 top level 5 path del/rootsys-2021-08-27_07:49:40.log
ID 497 gen 30724 top level 301 path MIDATA/.snapshots/96/snapshot
ID 506 gen 31690 top level 5 path del/rootsys-2021-08-27_23:19:53.log
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: [RESOLVED] Restore with timeshift

#5 Post by ticojohn »

Thanks for the replies. I find Grsync to be easy to use, so I will stick with that.
I am not irrational, I'm just quantum probabilistic.

Marie SWE
Posts: 241
Joined: 2021-04-06 22:14
Location: Sweden / Linköping
Has thanked: 7 times
Been thanked: 9 times

Re: [RESOLVED] Restore with timeshift

#6 Post by Marie SWE »

bester69 wrote: 2021-08-28 11:33
Marie SWE wrote: 2021-08-28 02:26 Hi @bester69 :)
interesting... is it easy to set up? and is the restore process easy?

Installation

sudo apt install snapper snapper-gui

snapper is a daemon that takes snapshots that you can configure throught gui, it works like a kind of daily crontab by taking automatically snapshots, so yout dont need to be worry


restoring manually a snapshot
yes. very easy...as easy to take a snapshot and reboot; just like this.:

for system

(by default, installation usually names @ to subvolume folder / partition; i prefer to use "rootsys" name)
sudo mount -t btrfs /dev/sda1 /mnt && cd /mnt
sudo mv @ @.del
sudo btrfs subvolume snaphot @.del/.snapshots/34/snpahot @
sudo mv @.del/.snapshots @/ (move snapper .snapshots folder within new active snapshot)
sudo reboot

after reboot
sudo btrfs subvolume delete @.del


for home

sudo mount -t btrfs /dev/sda1 /mnt && cd /mnt
sudo mv home home.del
sudo btrfs subvolume home.del/.snapshots/12/snapshot home
sudo mv home.del/.snapshots home/ (move snapper .snapshots folder within new active snapshot)

after reboot
sudo btrfs subvolume delete home.del

You can also create a subvolume or folder and put in there all dropped subvolumes named with datetime just in case you made an error and needed back to those snapshots; just like this.:
ID 496 gen 30868 top level 5 path del/rootsys-2021-08-27_07:49:40.log
ID 497 gen 30724 top level 301 path MIDATA/.snapshots/96/snapshot
ID 506 gen 31690 top level 5 path del/rootsys-2021-08-27_23:19:53.log
okay, so it isn't just a GUI solution, you still need terminal commands..
Then I think I will stay with Timeshift for a while longer. :wink:
Why make things complicated in life, if you can make it easier for yourself... Do it. ;o)
You only have one life, so make the most of it and enjoy it while you can.

User avatar
bester69
Posts: 2072
Joined: 2015-04-02 13:15
Has thanked: 24 times
Been thanked: 14 times

Re: [RESOLVED] Restore with timeshift

#7 Post by bester69 »

ticojohn wrote: 2021-08-28 13:12 Thanks for the replies. I find Grsync to be easy to use, so I will stick with that.
Btrfs is very easy to learn and very funny to play with

>> sudo btrfs subvolume create mydatapdf (Create subvolume Partition)
>> sudo btrfs subvolume snapshot mydatapdf Snapshotofmydatepdf (Create a snapshot subvolume Partition)
>> sudo btrfs subvolume delete mydatapdf (Delete a whole subvolume)
>> sudo mount -t btrfs -o subvol=mydatapdf /dev/sda1 /mnt (Mount a subvolume by namesubvolume id)
>> sudo btrfs send -v mydatapdf | sudo btrfs receive mydatadestdatapdf (send and receive a subvolume between different partitions, equivalent to dd but with subvolumes)

Just with that, you learnt btrfs and can start using it :D
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: [RESOLVED] Restore with timeshift

#8 Post by ticojohn »

bester69 wrote: 2021-08-29 17:55
ticojohn wrote: 2021-08-28 13:12 Thanks for the replies. I find Grsync to be easy to use, so I will stick with that.
Btrfs is very easy to learn and very funny to play with

>> sudo btrfs subvolume create mydatapdf (Create subvolume Partition)
>> sudo btrfs subvolume snapshot mydatapdf Snapshotofmydatepdf (Create a snapshot subvolume Partition)
>> sudo btrfs subvolume delete mydatapdf (Delete a whole subvolume)
>> sudo mount -t btrfs -o subvol=mydatapdf /dev/sda1 /mnt (Mount a subvolume by namesubvolume id)
>> sudo btrfs send -v mydatapdf | sudo btrfs receive mydatadestdatapdf (send and receive a subvolume between different partitions, equivalent to dd but with subvolumes)

Just with that, you learnt btrfs and can start using it :D
Yeah, right. Grsync is graphical and waaayyyyy easier than using CLI. But you can have it your way, I'll it do my way.
I am not irrational, I'm just quantum probabilistic.

Post Reply