tar backup exclude dir

[a323870]

Tar img non include dir /proc /lost+found /sys /dev /tmp /boot /run

I solved append /* at the end of --exclude

cmd="tar \
	$TAR_BACKUP_OPTIONS \
	$TAR_BACKUP_ADDITIONAL_OPTIONS \
	${zip} \
	${verbose} \
	-f $target \
	--warning=no-xdev \
	--numeric-owner \
	--exclude=\"$BACKUPPATH_PARAMETER/*\" \
	--exclude=\"$source/$log_file\" \
	--exclude='.gvfs' \
	--exclude=$devroot/proc/* \
	--exclude=$devroot/lost+found/* \
	--exclude=$devroot/sys/* \
	--exclude=$devroot/dev/* \
	--exclude=$devroot/tmp/* \
	--exclude=$devroot/boot/* \
	--exclude=$devroot/run/* \
	$EXCLUDE_LIST \
	$source"

[framps]

Hello @a323870 ,

you are right. Without /* the contents of these directories is not saved. But all these directories are recreated during Linux boot so there is no need to save them.

What's the reason you want to save these directories? If you have a strong argument for this I will add an additional option to raspiBackup in next release.

[a323870]

i test restore phase in a new sd card but at first boot raspberry don't create this dir. Manually create on new SD and boot is ok. Tank. Il giorno sab 19 gen 2019 alle ore 16:15 framp <notifications@github.com> ha scritto:

…

Hello @a323870 <https://github.com/a323870> , you are right. Without /* the contents of these directories is not saved. But all these directories are recreated during Linux boot so there is no need to save them. What's the reason you want to save these directories? If you have a strong argument for this I will add an additional option to raspiBackup in next release for this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AqDzbxFCa6L5Sdo_NGkKgkRIwOnorktjks5vEzadgaJpZM4aJJZ9> .

[framps]

Do you use the USB boot mode of your Raspberry and boot without any SD card?

[a323870]

No only sd card. Boot start, but end in error not found /dev /sys ecc.... Create folder manually mounted sd in another raspy. Reinsert sd and reboot first raspy its ok. Il giorno sab 19 gen 2019, 16:27 framp <notifications@github.com> ha scritto:

…

Do you use the USB boot mode of your Raspberry and boot without any SD card? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AqDzb3dV6OneQL9Lpj-_h7bGWsXOPhn8ks5vEzlQgaJpZM4aJJZ9> .

[framps]

Which OS do you use? Please provide the output of
cat /etc/os-release

[a323870]

a323870@raspberrypi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" a323870@raspberrypi ~ $ Standard raspbian. The problem is that this folder aren't create at first boot. I saved only the folder in tar image. Bye. Il giorno sab 19 gen 2019, 17:15 framp <notifications@github.com> ha scritto:

…

Which OS do you use? Please provide the output of cat /etc/os-release — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AqDzbx3BETgMJ1LriXGieGBmVzoKiBJPks5vE0SagaJpZM4aJJZ9> .

[framps]

Thank you very much for this information. I don't use tar backup on my Raspis but it's tested in the raspiBackup regression test and I'm wondering why this issue doesn't pop up there.

I have to investigate this further now.

[a323870]

If it can bu usful : In older version (0,6,3,2) tar cmd was cmd="tar \ $TAR_BACKUP_OPTIONS \ $TAR_BACKUP_ADDITIONAL_OPTIONS \ ${zip} \ ${verbose} \ -f $target \ --one-file-system \ --warning=no-xdev \ --numeric-owner \ --exclude=\"$BACKUPPATH_PARAMETER/*\" \ --exclude=proc/* \ --exclude=lost+found/* \ --exclude=sys/* \ --exclude=dev/* \ --exclude=tmp/* \ --exclude=boot/* \ --exclude=run/* \ $EXCLUDE_LIST \ $source" in this case backup not save the content of the folder */proc */sys ecc... In my installation for example the contents of /usr/include/sys The new version is was correct referencing the absolute path with use of variable $devroot (default ="") that generate the string (example /proc) But has been omitted the /* at the end. In this case tar does not save the content (correct way) but not even the name of the folder. If you untar in a new sd, the lack of folder /dev /sys /proc ecc.... the do not allow booting. I hope i clarify the problem Il giorno sab 19 gen 2019 alle ore 17:31 framp <notifications@github.com> ha scritto:

…

Thank you very much for this information. I don't use tar backup on my Raspis but it's tested in the raspiBackup regression test and I'm wondering why this issue doesn't pop up there. I have to investigate on this further now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AqDzb70Av7nWzset3s9LNwP7TKSY5cyOks5vE0hRgaJpZM4aJJZ9> .

[framps]

If it can bu usful

Indeed 👍

[framps]

Thank you very much you reported this valid issue. 👍

I just fixed it and decided to make it a new release 0.6.4.2 so everybody using raspiBackup will get notified to upgrade.

Just execute raspiBackup.sh -U to get the latest release.