How to test raspiBackupAndClone.sh manually?

[begunfx]

I followed the directions to setup raspiBackupAndClone.sh here: https://www.linux-tips-and-tricks.de/en/raspibackupcategorye/685-how-to-create-a-clone-with-raspibackup

I wanted to be able to manually execute a backup to test that it is working. I already have a properly formatted backup of RaspiBackup on my external microSD card and have several raspiBackups on my server. I'm using the default backup options (using rsync).

I can confirm that the drive exists:

Disk /dev/sda: 238.3 GiB, 255869321216 bytes, 499744768 sectors
/dev/sda1          8192   1056767   1048576   512M  c W95 FAT32 (LBA)
/dev/sda2       1056768 499744767 498688000 237.8G 83 Linux

I tried executing a new backup using the following:
sudo raspiBackupAndClone.sh /dev/sda -m detailed -g

I also tried:
sudo raspiBackupAndClone.sh /dev/sda

One thing I noticed in the tutorial is that we are supposed to use "partition oriented mode" when creating a backup, but the default for raspiBackup is only two partitions - which I have currently. Will this cause any issues or is there any reason why I should enable partition oriented mode when using this wrapper?

Getting the following error:
??? RBK0344E: No mounted boot parition detected

I'm sure I'm doing something wrong...

[framps]

You have to use the partition oriented backup because option -00 is only available in this mode.#

Looks like I have to create a fix for the typo 😆

[begunfx]

Okay. I created a backup using the -P option and restored that backup to the card.

Then I tried to run:
sudo raspiBackupAndClone.sh /dev/sda -P -m detailed -g

But I'm still getting an error:

raspiBackupAndClone.sh v0.2.1, $/$ - 
--- Creating backup and restore backup afterwards to /dev/sda ...
--- RBK0009I: ServiceVault2: raspiBackup.sh V0.7.0.2 - 2025-03-29 (3a9ab26) started at Thu 17 Apr 21:40:27 PDT 2025
--- RBK0116I: Using config file /usr/local/etc/raspiBackup.conf
??? RBK0344E: No mounted boot parition detected
--- RBK0033I: Please wait until cleanup has finished
--- RBK0320I: Removing incomplete backup. This may take some time. Please be patient
??? RBK0005E: Backup failed. Check previous error messages for details
--- RBK0010I: ServiceVault2: raspiBackup.sh V0.7.0.2 - 2025-03-29 (3a9ab26) stopped at Thu 17 Apr 21:40:28 PDT 2025 with rc 121
--- RBK0167I: Sending email
--- RBK0283I: Pushover notified
--- RBK0026I: Debug logfile saved in /home/begun/raspiBackup.log

So, even running a regular backup I'm getting this error.

If I reboot my pi then I can run the regular backup without issue.

This is what my steps look like:

1. Format microSD card - fat32 using disk Utility on Mac
2. Plug in my microSD card into the Pi using a USB reader
3. Execute a backup to my server using the following: sudo raspiBackup -P -t rsync -m detailed -g
4. Restore the backup to the microSD card using the following: sudo raspiBackup -d /dev/sda <backupDirectory>
5. Run another backup to the microSD card using: sudo raspiBackup -P -t rsync -m detailed -g
6. Getting error...

I can safely rule out the power supply as the issue since I'm now using official raspberry pi power plugs.

[framps]

1. Format microSD card - fat32 using disk Utility on Mac

You don't need to format the SD card. That's done by raspiBackup during restore.

4. Restore the backup to the microSD card using the following: sudo raspiBackup -d /dev/sda <backupDirectory>

You have to use raspiBackupAndClone.sh now all the time you want to create a manual backup. I updated the article on my website to make this clearer.

[begunfx]

To clarify: I'm getting the same error even if I use:
sudo raspiBackupAndClone.sh /dev/sda -P -t rsync -m detailed -g

[begunfx]

Note this is the output of: lsblk

begun@ServiceVault2:~ $ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    1 238.3G  0 disk 
├─sda1        8:1    1   512M  0 part 
└─sda2        8:2    1 237.8G  0 part 
mmcblk0     179:0    0 238.3G  0 disk 
├─mmcblk0p1 179:1    0   512M  0 part 
└─mmcblk0p2 179:2    0 237.8G  0 part /

As you can see the sd card "sda" is listed

[framps]

I see. You unfortunately have to be patient the next 4 weeks because I don't have access to a Raspberry and cannot check what's going on. This script is brand new and you're the guinea pig 😉

[begunfx]

Ah, okay. Didn't realize it was that new. The good news is my scheduled backup via the service ran successfully - so I can rule out any issues with the sdcard and mounting. One point to note though. Nothing in the log states that the backup was sync'd to the external sdCard or that raspiBackupAndClone was executed post backup. Might be good to include those in the log so we know that the sync part also ran successfully.

Here's my full log for your reference:

--- RBK0009I: ServiceVault: raspiBackup.sh V0.7.0.2 - 2025-03-29 (3a9ab26) started at Sat 19 Apr 03:00:47 PDT 2025
--- RBK0116I: Using config file /usr/local/etc/raspiBackup.conf
--- RBK0031I: Checking whether a new version of raspiBackup.sh is available
--- RBK0151I: Using backuppath /backup with partition type nfs4
--- RBK0271I: Smart recycle strategy will be applied
--- RBK0008I: Stopping services: 'systemctl stop cron && systemctl stop cups-browsed && systemctl stop cups && systemctl stop docker'
--- RBK0267I: Extension raspiBackup_mem_pre.sh called
--- RBK0267I: Extension raspiBackup_temp_pre.sh called
--- RBK0267I: Extension raspiBackup_disk_pre.sh called
--- RBK0081I: Creating backup of type rsync in /backup/ServiceVault/ServiceVault@debian12-rsync-backup-20250419-030046
--- RBK0347I: Partition oriented backup of type rsync started for partitions 1 2
--- RBK0036I: Saving partition layout
--- RBK0045I: Creating backup of partition layout in /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/ServiceVault-backup.sfdisk
--- RBK0045I: Creating backup of partition layout in /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/ServiceVault-backup.blkid
--- RBK0045I: Creating backup of partition layout in /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/ServiceVault-backup.parted
--- RBK0045I: Creating backup of partition layout in /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/ServiceVault-backup.fdisk
--- RBK0046I: Creating backup of master boot record in /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/ServiceVault-backup.mbr
--- RBK0092I: Saving partition mmcblk0p1 (69.23 KiB/509.99 KiB)
--- RBK0133I: Using directory /backup/ServiceVault/ServiceVault@debian12-rsync-backup-20250417-210925/mmcblk0p1 for hardlinks
--- RBK0158I: Creating native rsync backup /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/mmcblk0p1
--- RBK0085I: Backup of type rsync started. Please be patient
--- RBK0112I: Partition mmcblk0p1 was saved
--- RBK0092I: Saving partition mmcblk0p2 (24.23 MiB/222.11 MiB)
--- RBK0133I: Using directory /backup/ServiceVault/ServiceVault@debian12-rsync-backup-20250417-210925/mmcblk0p2 for hardlinks
--- RBK0158I: Creating native rsync backup /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046/mmcblk0p2
--- RBK0085I: Backup of type rsync started. Please be patient
--- RBK0112I: Partition mmcblk0p2 was saved
--- RBK0078I: Backup time: 00:06:50
--- RBK0033I: Please wait until cleanup has finished
--- RBK0345I: Temporary backup directory /backup/ServiceVault/tmp/ServiceVault@debian12-rsync-backup-20250419-030046 moved to /backup/ServiceVault/ServiceVault@debian12-rsync-backup-20250419-030046
--- RBK0218I: Applying smart backup strategy. Daily:7 Weekly:4 Monthly:12 Yearly:1
--- RBK0219I: No backups will be smart recycled
--- RBK0267I: Extension raspiBackup_mem_post.sh called
--- RBK1001I: Memory usage pre backup - Used: 770 MB Free: 1624 MB
--- RBK1001I: Memory usage post backup - Used: 670 MB Free: 200 MB
--- RBK0267I: Extension raspiBackup_temp_post.sh called
--- RBK1000I: CPU temperature pre and post backup: 40.0'C - 42.2'C
--- RBK0267I: Extension raspiBackup_disk_post.sh called
--- RBK1001I: Disk usage pre backup: Used: 26.73 TiB Free: 37.65 TiB
--- RBK1002I: Disk usage post backup: Used: 26.75 TiB Free: 37.63 TiB
--- RBK1003I: Disk usage change: -18.52 GiB (0.00 %%)
--- RBK0007I: Starting services: 'systemctl start docker && systemctl start cups && systemctl start cups-browsed && systemctl start cron'
--- RBK0017I: Backup finished successfully
--- RBK0010I: ServiceVault: raspiBackup.sh V0.7.0.2 - 2025-03-29 (3a9ab26) stopped at Sat 19 Apr 03:07:47 PDT 2025 with rc 0
--- RBK0283I: Pushover notified
--- RBK0167I: Sending email

[framps]

Didn't realize it was that new.

raspiBackupAndClone uses a new feature of raspiBackup 0.7 - the option -00 which disables formatting of the restore device and rsync just synchronizes the updates.

One point to note though. Nothing in the log states that the backup was sync'd to the external sdCard or that raspiBackupAndClone was executed post backup. Might be good to include those in the log so we know that the sync part also ran successfully.

Thank you for your feedback. I agree with you. User processing feedback is required. Unfortunately it's not easy to implement. A restore does not create an eMail and thus you don't get any feedback of the restore other than a raspiBackup.msg file in /root.

Would it be acceptable by you to get two notifications? One for the backup and one for the restore? To concat both raspiBackup run messages into one eMail will require a lot of changes and development and test time I frankly don't want to spend.

[begunfx]

I think it would be perfectly acceptable to have two separate notifications for a backup and restore. In an ideal world one notification for the entire process would be the best route, but if to get to that it's a heavy lift, then I think two would be fine.

No worries on the delay to look at the manual restore/backup of raspiBackupAndClone. I'm just glad the service backup seems to be working. Feel free to reach out when you do have some time to look at it and I'd be happy to help debug. As always appreciate your efforts!

[framps]

I'm back home now and I didn't forget you 😃 But a lot of todos have accumulated. Please be patient with raspiBackupAndClone.

[begunfx]

Hi @framps. No worries. I was actually just thinking about reaching out. No problem. Reach out when you are ready!

[framps]

I just created an issue to track the changes I'm going to make in raspiBackup so notifications are sent if a backup finishes in the background.