Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Default User Newsgroups: linux.debian.user Subject: Re: backing up backups Date: Wed, 13 Apr 2022 18:30:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-user-request@lists.debian.org Wed Apr 13 16:21:10 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.109 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOAM532HhdYpg1qu6FXJEs2uJFPpYRA7mxKgC782f+ZW9yB7Tpvpnwy0 GjVFY6aSaJuowi7Vr5Aezo0vOXqgn/12oOD0SxuBfx9D X-Google-SMTP-Source: ABdhPJwh9MW6OxY1pQDScU2AL+RNj8q1zbW9FByuEy981DHyKGBtG4hQ1comb6Mu6t6x/KuoJGIQcq1Et8JJrRdhZHc= X-Received: by 2002:a05:6638:14d5:b0:323:dca6:fe8a with SMTP id l21-20020a05663814d500b00323dca6fe8amr20534998jak.309.1649866852324; Wed, 13 Apr 2022 09:20:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a8db1005dc8b8f5d" X-Mailing-List: archive/latest/788064 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAMaNm6F8V2YAV_k2YzdmB_fyB_pc-kjPRN6vv6os7qRxgOpE1g@mail.gmail.com Approved: robomod@news.nic.it Lines: 290 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 13 Apr 2022 12:20:36 -0400 X-Original-Message-ID: X-Original-References: <06886474-9735-3612-7c06-0ea3f92bcc14@holgerdanske.com> Xref: csiph.com linux.debian.user:247206 --000000000000a8db1005dc8b8f5d Content-Type: text/plain; charset="UTF-8" On Wed, Apr 13, 2022 at 12:09 PM Default User wrote: > > > On Mon, Apr 11, 2022 at 12:03 PM David Christensen < > dpchrist@holgerdanske.com> wrote: > >> On 4/10/22 22:15, tomas@tuxteam.de wrote: >> > On Sun, Apr 10, 2022 at 09:44:59PM -0700, David Christensen wrote: >> >> On 4/10/22 19:58, Default User wrote: >> >>> Hello! >> >>> >> >>> My setup: >> >>> - single home x86-64 computer running Debian 11 Stable, up to date. >> >>> - one 4-Tb external usb hard drive to use as a backup device, labeled >> MSD1. >> >>> - another identical usb hard drive, labeled MSD2, to use as a copy of >> the >> >>> backups on MSD1. >> >>> - the computer and all storage devices are formatted ext4, not >> encrypted. >> >>> - two old Clonezilla disk images from when I installed Debian 11 last >> year >> >>> (probably irrelevant). >> >>> - Timeshift to daily back up system EXCEPT for data directories. >> >>> - Back in Time to daily back up data directories. >> >>> - Borgbackup to also daily back up data directories. >> >>> - Rsync to frequently backup any changed data between the daily Back >> in >> >>> Time and Borgbackup backups of data directories, using this command: >> >>> >> >>> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 >> --exclude-from >> >>> "/home/default/rsync_exclude_list.txt" /home >> >>> /media/default/MSD1/rsync_backups_of_host_home_directory_only >> >>> >> >>> Each type of backup is in a separate subdirectory on MSD1 (Timeshift, >> Back >> >>> in TIme, Rsync, etc.). >> >>> >> >>> It "seems" to work okay, BUT . . . >> >>> >> >>> Then I try to use rsync to make an identical copy of backup device >> MSD1 on >> >>> an absolutely identical 4-Tb external usb hard drive, >> >>> labeled MSD2, using this command: >> >>> >> >>> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 >> >>> /media/default/MSD1/ /media/default/MSD2 >> >> >> >> >> >> See 'man 1 rsync'. You have a slash at the end of SRC, but not at the >> end >> >> of DEST. I would add a slash after "MSD2": >> > >> > The only thing I find in rsync's man page about trailing slashes >> > in the `dest' argument would be relevant if MSD2 didn't exist (in >> > the OP's case it seems it does, no?) >> >> >> There are four combinations for rsync(1) SRC and DEST vs. trailing >> slashes. I use two -- trailing slashes on SRC and DEST for directories, >> and no trailing slashes on SRC and DEST for single files. The other two >> combinations may "work" under certain circumstances, but they have >> caused me grief in the past and I avoid them as a matter of habit. >> >> >> David >> >> > > Hey guys, sorry for just getting back with you now. > Unfortunately, I am just now recovering from a self-inflicted computer > disaster. > > While fighting with rsync, I did either: > > sudo rsync -aAXHSxvv --delete --info=progress2,stats2,name2 > /media/default/MSD1/ /media/default/MSD2 > or > sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 > /media/default/MSD1/ /media/default/MSD2/ > > Just one small problem: MSD2 was not connected to my computer! > (Don't say it . . . ) > > Instead of giving an error message, rsync just created a directory on my > computer called /media/defaultMSD2, and filled it up until my / partition > was full, and THEN my desktop environment (Cinnamon) popped up a > notification saying so. How thoughtful. > > The computer then would not reboot into the operating system. > > No problem, I say. I will just use Timeshift to restore from its backup of > a few hours earlier. > > But that did not work, even after deleting the extra directory, and trying > restores from multiple Timeshift backups. > > Anyway, I never could fix the problem. But I did take it as an opportunity > to "start over". I put in a new(er) SSD, and did a fresh install, replacing > Cinnamon with Gnome. Mistake - now I remember why I dislike Gnome, ever > since Gnome 3. Wish I had re-installed Cinnamon, but too late now, out of > time. For now I will just have to grit my teeth and live with it. > > [BTW, yes, I do have all of my data. Backfilling it into my new setup will > no doubt be an ongoing adventure.] > > Anyway, just a few notes about the rsync situation: > > 1) Having or not having a trailing / on the destination directory did not > seem to make any difference in the size of the copy made, or otherwise. > Nevertheless, I intend to heed the advice given to have a trailing / after > both source and destination, or neither, as appropriate. > > 2) Using or not using an "S" option with rsync did not seem to make any > difference, at least concerning the size of the copy made. > > 3) Yes, I really should check into using checksums to avoid "bot rot". > Good advice. > > Finally, Gnome sucks. (Did I mention that?) > > Thanks for the replies. > > Uh oh . . . I just realized, this was supposed to have been sent to debian-user@lists.debian,org - NOT directly to Daivd Christensen. Sorry for the mistake. (Gmail also sucks. At least as far as composing and sending email.) --000000000000a8db1005dc8b8f5d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Apr 13, 2022 at 12:09 PM Default User <<= a href=3D"mailto:hunguponcontent@gmail.com">hunguponcontent@gmail.com&g= t; wrote:

=
On Mon= , Apr 11, 2022 at 12:03 PM David Christensen <dpchrist@holgerdanske.com> wrot= e:
On 4/10/22 22= :15, tomas@tuxteam.de= wrote:
> On Sun, Apr 10, 2022 at 09:44:59PM -0700, David Christensen wrote:
>> On 4/10/22 19:58, Default User wrote:
>>> Hello!
>>>
>>> My setup:
>>> - single home x86-64 computer running Debian 11 Stable, up to = date.
>>> - one 4-Tb external usb hard drive to use as a backup device, = labeled MSD1.
>>> - another identical usb hard drive, labeled MSD2, to use as a = copy of the
>>> backups on MSD1.
>>> - the computer and all storage devices are formatted ext4, not= encrypted.
>>> - two old Clonezilla disk images from when I installed Debian = 11 last year
>>> (probably irrelevant).
>>> - Timeshift to daily back up system EXCEPT for data directorie= s.
>>> - Back in Time to daily back up data directories.
>>> - Borgbackup to also daily back up data directories.
>>> - Rsync to frequently backup any changed data between the dail= y Back in
>>> Time and Borgbackup backups of data directories, using this co= mmand:
>>>
>>> sudo rsync -aAXHxvv --delete --info=3Dprogress2,stats2,name2 -= -exclude-from
>>> "/home/default/rsync_exclude_list.txt" /home
>>> /media/default/MSD1/rsync_backups_of_host_home_directory_only<= br> >>>
>>> Each type of backup is in a separate subdirectory on MSD1 (Tim= eshift, Back
>>> in TIme, Rsync, etc.).
>>>
>>> It "seems" to work okay, BUT . . .
>>>
>>> Then I try to use rsync to make an identical copy of backup de= vice MSD1 on
>>> an absolutely identical 4-Tb external usb hard drive,
>>> labeled MSD2, using this command:
>>>
>>> sudo rsync -aAXHxvv --delete --info=3Dprogress2,stats2,name2 >>> /media/default/MSD1/ /media/default/MSD2
>>
>>
>> See 'man 1 rsync'.=C2=A0 You have a slash at the end of SR= C, but not at the end
>> of DEST.=C2=A0 I would add a slash after "MSD2":
>
> The only thing I find in rsync's man page about trailing slashes > in the `dest' argument would be relevant if MSD2 didn't exist = (in
> the OP's case it seems it does, no?)


There are four combinations for rsync(1) SRC and DEST vs. trailing
slashes.=C2=A0 I use two -- trailing slashes on SRC and DEST for directorie= s,
and no trailing slashes on SRC and DEST for single files.=C2=A0 The other t= wo
combinations may "work" under certain circumstances, but they hav= e
caused me grief in the past and I avoid them as a matter of habit.


David



Hey guys, sorry for just getting back with you now.
Unfortunately, I am just now recovering from a self-in= flicted computer disaster.

While fighting with rsync, I did either:<= /div>

sudo rsync -aAXHSxvv --delete --info=3Dprogress2,stats2,name2 /media/defa= ult/MSD1/ /media/default/MSD2
or
<= div style=3D"font-size:small">sudo rsync -aAXHxvv --delete --info=3Dprogres= s2,stats2,name2 /media/default/MSD1/ /media/default/MSD2/

Just one smal= l problem: MSD2 was not connected to my computer!
(Don't say it . . .=C2=A0 )

Instead of giving an error= message, rsync just created a directory on my computer called /media/defau= ltMSD2, and filled it up until my / partition was full, and THEN my desktop= environment (Cinnamon) popped up a notification saying so.=C2=A0 How thoug= htful.

The computer then would not reboot into the operating system.=

No problem, I say. I will just use Timeshift to restore from its backup = of a few hours earlier.

=
But that did not work, even after deleting t= he extra directory, and trying restores from multiple Timeshift backups.

Anyway, I never could fix the problem. But I did take it as an opportu= nity to "start over". I put in a new(er) SSD, and did a fresh ins= tall, replacing Cinnamon with Gnome. Mistake - now I remember why I dislike= Gnome, ever since Gnome 3. Wish I had re-installed Cinnamon, but too late = now, out of time. For now I will just have to grit my teeth and live with i= t.

[BTW, yes, I do have all of my data. Backfilling it into my new se= tup will no doubt be an ongoing adventure.]

Anyway, just a few notes abou= t the rsync situation:

1) Having or not having a trailing / on the destin= ation directory did not seem to make any difference in the size of the copy= made, or otherwise. Nevertheless, I intend to heed the advice given to hav= e a trailing / after both source and destination, or neither, as appropriat= e.

2) Using or not using an "S" option with rsync did not = seem to make any difference, at least concerning the size of the copy made.=

3) Yes, I really should check into using checksums to avoid "b= ot rot". Good advice.

Finally, Gnome sucks.=C2=A0 (Did I mentio= n that?)

Thanks for the replies.

=
=C2=A0

Uh oh . . .

I just realized, this was supposed to have been sent to = debian-user@lists.debian,org - NOT directly to Daivd Christensen.

Sorry for the mistake.
<= div style=3D"font-size:small" class=3D"gmail_default">
(Gmail also sucks. At least as= far as composing and sending email.)

--000000000000a8db1005dc8b8f5d--