[opensuse] Question on "backintime" - user experience needed.
I tried to set up a "back-in-time" installation for my friend. She is running opensuse Leap 42.3 currently. I did attach a usb3.0 disc to the machine. On it, I have the backup, created manually the first time in superusermode. Now, first the setting to do incremental backups automatically when branched the disc fails (seems a permission problem). I think it has to run as superuser. Question: If I set it up in a GUI session in root, does this work also when the system starts normally or do I have to set up in CLI via a startup script? Does anybody has a similar setup? The program should do a differential backup of all /home users, no matter which one is logged in, preferentially. It should of course honor the settings of the rest of preferences. Currently I had the issue that, when I do not activate checksum, it does run through with "nothing to do". So I think back in time needs checksum to be activated. I do not want to have "full rsync compatiblility" because I wish the backups to be read only. Is it possible that leap attributes a different path to an external usb3 disc although it has not been unplugged? In case this is so, is it possible to force it to give it a static path? P.s. I will not be able to put your advice into practice at once, but I am gathering input now, so that, when I will have occasion, I can try to set it up this time. Thank you in advance. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-26-18 08:28]:
I tried to set up a "back-in-time" installation for my friend. She is running opensuse Leap 42.3 currently. I did attach a usb3.0 disc to the machine. On it, I have the backup, created manually the first time in superusermode.
and now root "owns" the backup and must be used to do operations note: if you setup backintime with <user>, then there are problems backing up files which <user> doesn't have proper permissions, which is NOT a problem if you are *only* backing up <user>'s files.
Now, first the setting to do incremental backups automatically when branched the disc fails (seems a permission problem). I think it has to run as superuser.
yes
Question: If I set it up in a GUI session in root, does this work also when the system starts normally or do I have to set up in CLI via a startup script? Does anybody has a similar setup?
I have been using backintime for several years. it writes a crontab entry and survives reboots (option under "Expert Options") in the gui.
The program should do a differential backup of all /home users, no matter which one is logged in, preferentially.
if setup as root, not as a <user>.
It should of course honor the settings of the rest of preferences.
yes
Currently I had the issue that, when I do not activate checksum, it does run through with "nothing to do". So I think back in time needs checksum to be activated.
I don't know, don't have checksum activated.
I do not want to have "full rsync compatiblility" because I wish the backups to be read only.
they are "read only" on my system w/o "full ...".
Is it possible that leap attributes a different path to an external usb3 disc although it has not been unplugged?
don't know, haven't tried, not applicable to my system. I backup to rotating rust.
In case this is so, is it possible to force it to give it a static path?
assign a "label" to mount the usb device
P.s. I will not be able to put your advice into practice at once, but I am gathering input now, so that, when I will have occasion, I can try to set it up this time. Thank you in advance.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 26 novembre 2018 14:51:29 CET, Patrick Shanahan ha scritto:
* stakanov <stakanov@eclipso.eu> [11-26-18 08:28]:
I tried to set up a "back-in-time" installation for my friend. She is running opensuse Leap 42.3 currently. I did attach a usb3.0 disc to the machine. On it, I have the backup, created manually the first time in superusermode.
and now root "owns" the backup and must be used to do operations
note: if you setup backintime with <user>, then there are problems backing up files which <user> doesn't have proper permissions, which is NOT a problem if you are *only* backing up <user>'s files.
Now, first the setting to do incremental backups automatically when branched the disc fails (seems a permission problem). I think it has to run as superuser.
yes
Question: If I set it up in a GUI session in root, does this work also when the system starts normally or do I have to set up in CLI via a startup script? Does anybody has a similar setup?
I have been using backintime for several years. it writes a crontab entry and survives reboots (option under "Expert Options") in the gui.
The program should do a differential backup of all /home users, no matter which one is logged in, preferentially.
if setup as root, not as a <user>.
It should of course honor the settings of the rest of preferences.
yes
Currently I had the issue that, when I do not activate checksum, it does run through with "nothing to do". So I think back in time needs checksum to be activated.
I don't know, don't have checksum activated.
I do not want to have "full rsync compatiblility" because I wish the backups to be read only.
they are "read only" on my system w/o "full ...".
Is it possible that leap attributes a different path to an external usb3 disc although it has not been unplugged?
don't know, haven't tried, not applicable to my system. I backup to rotating rust.
In case this is so, is it possible to force it to give it a static path?
assign a "label" to mount the usb device
P.s. I will not be able to put your advice into practice at once, but I am gathering input now, so that, when I will have occasion, I can try to set it up this time. Thank you in advance. Thank you very much, especially for the tip with the label! The issue with the choice of usb is btw (though I do understand the convenience of "rotating rust") that, before she does some adventurous and non reversible actions on her system, I can tell her to take off the usb first, so, whatever may "happen" it will not destroy everything, but in the worst case a working backup of the /home remains. For you it may sound overprotective...but by experience I assure you, it is not ;-)
I still have to understand why the superusermode does require on my system a checksum, while on yours not. Maybe it is the changing name of the usb support the culprit. Anyway, great input. I will try to setup a similar situation here, just to gather some experience. Regards. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* stakanov <stakanov@eclipso.eu> [11-26-18 20:20]:
In data lunedì 26 novembre 2018 14:51:29 CET, Patrick Shanahan ha scritto:
* stakanov <stakanov@eclipso.eu> [11-26-18 08:28]:
I tried to set up a "back-in-time" installation for my friend. She is running opensuse Leap 42.3 currently. I did attach a usb3.0 disc to the machine. On it, I have the backup, created manually the first time in superusermode.
and now root "owns" the backup and must be used to do operations
note: if you setup backintime with <user>, then there are problems backing up files which <user> doesn't have proper permissions, which is NOT a problem if you are *only* backing up <user>'s files.
Now, first the setting to do incremental backups automatically when branched the disc fails (seems a permission problem). I think it has to run as superuser.
yes
Question: If I set it up in a GUI session in root, does this work also when the system starts normally or do I have to set up in CLI via a startup script? Does anybody has a similar setup?
I have been using backintime for several years. it writes a crontab entry and survives reboots (option under "Expert Options") in the gui.
The program should do a differential backup of all /home users, no matter which one is logged in, preferentially.
if setup as root, not as a <user>.
It should of course honor the settings of the rest of preferences.
yes
Currently I had the issue that, when I do not activate checksum, it does run through with "nothing to do". So I think back in time needs checksum to be activated.
I don't know, don't have checksum activated.
I do not want to have "full rsync compatiblility" because I wish the backups to be read only.
they are "read only" on my system w/o "full ...".
Is it possible that leap attributes a different path to an external usb3 disc although it has not been unplugged?
don't know, haven't tried, not applicable to my system. I backup to rotating rust.
In case this is so, is it possible to force it to give it a static path?
assign a "label" to mount the usb device
P.s. I will not be able to put your advice into practice at once, but I am gathering input now, so that, when I will have occasion, I can try to set it up this time. Thank you in advance. Thank you very much, especially for the tip with the label! The issue with the choice of usb is btw (though I do understand the convenience of "rotating rust") that, before she does some adventurous and non reversible actions on her system, I can tell her to take off the usb first, so, whatever may "happen" it will not destroy everything, but in the worst case a working backup of the /home remains. For you it may sound overprotective...but by experience I assure you, it is not ;-)
I still have to understand why the superusermode does require on my system a checksum, while on yours not. Maybe it is the changing name of the usb support the culprit.
settings -> options uncheck "Use checksum ...." check "Check for changes...."
Anyway, great input. I will try to setup a similar situation here, just to gather some experience.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 26 Nov 2018 14:26:29 +0100 stakanov <stakanov@eclipso.eu> wrote:
I do not want to have "full rsync compatiblility" because I wish the backups to be read only.
IMHO a better way to arrange that is to use a script as the cron job for the backup. In the script, start by mounting the backup, then run the actual backup, then dismount (umount) the backup. That way, the backups are extremely unlikely to be accidently corrupted or encrypted by ransomware or rm -rf * or whatever, and they still serve their purpose as a true backup with all permissions intact. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 26/11/2018 à 17:59, Dave Howorth a écrit :
That way, the backups are extremely unlikely to be accidently corrupted or encrypted by ransomware or rm -rf * or whatever, and they still serve their purpose as a true backup with all permissions intact.
yes, and when restoring, mount read only jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 26 novembre 2018 18:15:56 CET, jdd@dodin.org ha scritto:
Le 26/11/2018 à 17:59, Dave Howorth a écrit :
That way, the backups are extremely unlikely to be accidently corrupted or encrypted by ransomware or rm -rf * or whatever, and they still serve their purpose as a true backup with all permissions intact.
yes, and when restoring, mount read only
jdd
so I would then mount not automatically? I will have to set this in the partition manager to be durable,and survive reboot, right? Then the script will mount and subsequently umount at every system session. Finally: what would happen if, not wanting it, the user would shut down the machine while still running a backup. Would that incremental backup be simply aborted or would this cause potential havoc? How to approach this situation in a safe mode, could be e.g. to delay the shutdown with a message on the screen, as the system is on a APC UPS, so it would be safe against accidental power interruption. We speak about a potential PEBKAC problem to be clear. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 26/11/2018 à 18:36, stakanov a écrit :
yes, and when restoring, mount read only
partition manager to be durable,and survive reboot, right?
usually you don't have to restore so often :-) but... if you want to have the file at always at hand, mount read only in fstab and remount rw only to do the backup
machine while still running a backup. Would that incremental backup be simply aborted or would this cause potential havoc?
if you use rsync, this wont have any bad effect, with simple copy paste the result in unpredicable
potential PEBKAC problem to be clear.
rsync is the solution, and is built with this in mind. I always use rsync through ssh (I have sshd running on most machines). I didn't follow all the thread, but don't see why you don't want to use it. setting the backup in a cron job and forget it if the host is always available. any backup depends of what one exactly wants. Take time to think about it before any move :-) some tracks: http://dodin.org/wiki/pmwiki.php?n=Doc.CompleteBackup jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
and, just in case the subject is really a back in time, think of virtual machine with non persistent storage or simply snapshots jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* jdd@dodin.org <jdd@dodin.org> [11-26-18 13:34]:
Le 26/11/2018 à 18:36, stakanov a écrit :
yes, and when restoring, mount read only
partition manager to be durable,and survive reboot, right?
usually you don't have to restore so often :-)
but... if you want to have the file at always at hand, mount read only in fstab and remount rw only to do the backup
machine while still running a backup. Would that incremental backup be simply aborted or would this cause potential havoc?
if you use rsync, this wont have any bad effect, with simple copy paste the result in unpredicable
potential PEBKAC problem to be clear.
rsync is the solution, and is built with this in mind. I always use rsync through ssh (I have sshd running on most machines). I didn't follow all the thread, but don't see why you don't want to use it.
setting the backup in a cron job and forget it if the host is always available.
any backup depends of what one exactly wants. Take time to think about it before any move :-)
some tracks:
backintime uses rsync. I haven't tried but I would bet it will survive a reboot interruption. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 26 novembre 2018 20:09:52 CET, Patrick Shanahan ha scritto:
* jdd@dodin.org <jdd@dodin.org> [11-26-18 13:34]:
Le 26/11/2018 à 18:36, stakanov a écrit :
yes, and when restoring, mount read only
partition manager to be durable,and survive reboot, right?
usually you don't have to restore
so often :-)
but... if you want to have the file at always at hand, mount read only in fstab and remount rw only to do the backup
machine while still running a backup. Would that incremental backup be simply aborted or would this cause potential havoc?
if you use rsync, this wont have any bad effect, with simple copy paste the result in unpredicable
potential PEBKAC problem to be clear.
rsync is the solution, and is built with this in mind. I always use rsync through ssh (I have sshd running on most machines). I didn't follow all the thread, but don't see why you don't want to use it.
setting the backup in a cron job and forget it if the host is always available.
any backup depends of what one exactly wants. Take time to think about it before any move :-)
some tracks:
http://dodin.org/wiki/pmwiki.php?n=Doc.CompleteBackup @ backintime uses rsync. I haven't tried but I would bet it will survive a reboot interruption. Thanks to all of you. I will try and will give feedback, at times, when desperate, I will come back here whining for help. :-p
Hope all will go well. Oh, @jdd: the issue is that the person in question has no NAS, on the other hand wants an easy but regular solution for backing up / home. A system restore would be quite easy as she has opted (or me for her) for btrfs on that system. But the anxiety is to have redundancy of documents, pics etc. That is the reason why I do not use things like ssh but a locally attached usb drive. and yes, Patrick is absolutely right, it has rsync build in and has the possibility to do full rsync protocol but then with the drawback of loosing the advantage of read only backups (which I prefer). Anyway thank you all. Regards. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Dave Howorth -
jdd＠dodin.org -
Patrick Shanahan -
stakanov