New pages
Most visited
raspiBackup has a new logo
- Details
- Category: raspiBackup
-
Also available:
- Hits: 18
raspiBackup - FAQ
- Details
- Category: raspiBackup
-
Also available:
- Hits: 34192
User Rating: 4 / 5
Frequent asked questions about raspiBackup. Every new user of raspiBackup should read all questions and answers.
raspiBackup - Supported hardware and software
- Details
- Category: raspiBackup
-
Also available:
- Hits: 3995
raspiBackup - Supported hardware and software
raspiBackup is supported with RaspbianOS and Raspberry hardware only. Ubuntu on Raspberry will be supported in next release. There is a beta available already. But raspiBackup can also be used successfully on different Raspberry compatible hardware with different Linux distributions. But note raspiBackup requires the /boot and /root partition used in RaspbianOS.
Just test raspiBackup on your environment and be happy if it works. But if it fails or you get error messages there is no support. You may create an issue in github and append the debug log and I will check whether the issue is minor an can be fixed easily. But in any case the environment is unsupported.
Given the fact raspiBackup is maintained and supported for free
1) It's too expensive for me to buy all possible hardware required for tests
2) it's too expensive for me to setup and execute all test combinations
3) it's to expensive for me to execute all tests every time a new release will be published.
There exists a small script in github which tests whether the present environment is supported by raspiBackup. (see here)
raspiBackup - How to restore your backup
- Details
- Category: raspiBackup
-
Also available:
- Hits: 34088
User Rating: 3 / 5
With raspiBackup you can create regular backups of your Raspberry. In addition you can restore a backup to any SD card. A new partition table is created on the target SD card and the backup data is restored on the partitions. If an external root filesystem was saved with raspiBackup this filesystem will also be restored to an external device.
Recently I got issues in github because restore failed. It's strictly recommended to restore your backup with the same OS the backup was created with. You're free to use another Linux release but this may the restore to fail because of different versions of the Linux tools which are usedto backup and restore the backup. In particular it's because of an incompatible change in sfdisk in Bullseye. Just use the OS the backup was created to restore the backup!
raspiBackup - Create regularly and unattended backups of your running Raspberry
- Details
- Category: raspiBackup
-
Also available:
- Hits: 195602
User Rating: 5 / 5
raspiBackup helps to create backups of a running Raspberry with no shutdown or manual intervention which means your can save or clone your SD card during normal operation. An exported root partition will be saved too. Important services will be stopped just before starting the backup and are started again when the backup finished. Any device which can be mounted on Linux can be used as backupspace (USB disk, USB stick, nfs, samba, sshfs, ...). The backup image can be created with dd, tar or rsync using hardlinks. Restore is possible on Windows or Linux. Source Raspbian may have been installed on SD card only or the boot partition may be on SD card and the root partition on an external USB device like USB SSD or USB stick. Raspbian installed on an USB device only using USB boot mode is also supported
sshuttle: packet_write_wait: Connection to port 22: Broken pipe
- Details
- Category: Networking
- Hits: 102
I just had to tunnel inside a VPN to be able to connect to my home network. I tried OpenVPN and Wireguard but had issues to get it working. Therefore I decided to use ssh tunneling inside the existing VPN. There is a nice too called sshuttle available which easily allows to tunnel any requests through ssh.
raspiBackup - Used all over the world
- Details
- Category: raspiBackup
-
Also available:
- Hits: 4539
User Rating: 4 / 5
raspiBackup is used in a lot of countries all over the world already (Status 07/2023)
Countries: 65
AE United Arab Emirates
AM Armenia
AR Argentina 
AT Austria 
AU Australia 
BE Belgium 
BG Bulgaria 
BN Brunei
BR Brasila 
CA Canada 
CH Suisse 
CL Chile
CM Camerun
CN China 
CO Colombia
CY Cyprus
CZ Czech Republic 
DE Germany 
DK Denmark 
EE Estonia
ES Spain 
FI Finland 
FR France 
GB United Kingdom 
GH Ghana
GR Greece 
HK Honkong
HR Croatia
HU Hungury 
ID Indonesia 
IE Irland 
IL Israel 
IN India 
IR Iran
IT Italy 
JP Japan 
KE Kenya
KR South Corea
LI Liechtenstein
LT Lithuania
LU Luxemburg 
LV Latvia
MT Malta
MX Mexico
MY Malaysia
NG Nigeria
NL Netherlands 
NO Norway 
NZ New Zealand 
PA Panama
PH Philippines
PL Poland 
PT Portugal 
RO Romania 
SE Sweden 
SG Singapore
SI Slovenia
SK Slovakia
TH Thailand 
TR Turkey 
TW Taiwan 
UA Ukraine 
US United States of Amerika 
VN Vietnam
ZA Zaire
PiShrink is just a hack
- Details
- Category: Raspberry
-
Also available:
- Hits: 849
PiShrink is a useful tool to compress backups created with win32diskimager and other windows tools as a full backup to reduce them to a minimum size.
It's a hack and works a lot of time. Unfortunatey there are a lot of situations you get an ugly error message which are created because of missing checks in the code.
raspiBackup - How do hardlinks work with rsync
- Details
- Category: raspiBackup
-
Also available:
- Hits: 5989
User Rating: 4 / 5
A lot of time people ask how rsync backup type works and how hardlinks are used. Following article describes when files are created and deleted on the file system Dateien and when hardlinks are used.
Raspberry Compute Module 4 (CM4) setup guide on eMMC and NVMe
- Details
- Category: Raspberry
- Hits: 6882
User Rating: 5 / 5
I recently got a compute module 4 (CM4) donated to add support for NVMe in raspiBackup (See here for details). I'm used to use a Raspberry but never used a CM4 before so I had to ramp up on CM4 first. The following page describes how I managed to get a RaspbianOS (Buster) up and running on the CM4 and to boot from NVMe.
My CM4 specs: 1GB main memory, 32GB eMMC and 128GB NVMe from Hynix, no WiFi and a Waveshare Mini Base Board A (CM4-IO-BASE-A)
Parts
Hynix NVMe, CM4 and Waveshare Mini Base Board A (from top to bottom)
Parts assembled
How to test the CPU temperature of my Raspberry and check whether the CPU speed was throttled ?
- Details
- Category: Raspberry
-
Also available:
- Hits: 4340
User Rating: 5 / 5
We now have a new Raspberry4 gibt, which in contrast to the previous versions becomes quite hot. So everybody is interested in the effectiveness of either passive or active cooling and whether this cooling suppresses CPU throtteling.
I wrote a small script check_throttled.sh which reads the current throttling states of the Raspberry with vcgencmd get_throttled and if throtteling happens or already happend the meaning of the throttling bits is reported.
raspiBackup - Use pishrink to reduce dd backups to a minimum size
- Details
- Category: raspiBackup
-
Also available:
- Hits: 7480
User Rating: 3 / 5
pishrink is a useful tool to reduce the size of dd images to it's minimum. When the image is booted the image expands the root partition to it's possible maximum size. You can shrink an image created by raspiBackup by using the helper script raspiBackupWrapper.sh. Following paragraph describes in detail how to configure raspiBackup to shrink dd backup images with pishrink.
raspiBackup - Configuration update when upgrading to a new version
- Details
- Category: raspiBackup
-
Also available:
- Hits: 4046
User Rating: 1 / 5
Whenever an upgrade to a new version of raspiBackup is executed it's tested whether the new version has new configuration options. If there are new configuration options used the local configuration file will be merged into a new file with the new configuration file while upgrading raspiBackup. Following page describes in detail what's going on during a configuration update.
Note
If a version less than 0.6.5 is upgraded the configuration file merge has to be started manually after upgrading. Following command will start the configuration update:
sudo raspiBackup.sh --updateConfig
When the two configuration files are merged raspiBackup writes various information messages. Following messages are written when upgrading raspiBackup from v0.6.4.3 to v0.6.5:
--- RBK0241I: Merging current configuration v0.1.3 with new configuration v0.1.4 into /usr/local/etc/raspiBackup.conf.merged.
--- RBK0248I: Added option DEFAULT_SMART_RECYCLE=0.
--- RBK0248I: Added option DEFAULT_SMART_RECYCLE_DRYRUN=1.
--- RBK0248I: Added option DEFAULT_SMART_RECYCLE_OPTIONS="7 4 12 1".
--- RBK0248I: Added option DEFAULT_TELEGRAM_TOKEN="".
--- RBK0248I: Added option DEFAULT_TELEGRAM_CHATID="".
--- RBK0248I: Added option DEFAULT_TELEGRAM_NOTIFICATIONS="F".
--- RBK0248I: Added option DEFAULT_NOTIFY_START=0.
--- RBK0248I: Added option DEFAULT_COLORING="CM".
--- RBK0243I: Configuration merge finished successfullly but not activated.
!!! RBK0245W: Backup current configuration in /usr/local/etc/raspiBackup.conf.bak and activate updated configuration? y/N
Configuration file
/usr/local/etc/raspiBackup.conf.merged
will be created and receive the merged configuration files /usr/local/etc/raspiBackup.conf with the new configuration . RBK248 lists which changes are applied. Finally you have to answer the question whether you want to activate the merged configuration file. The existing configuration file will be saved in /usr/local/etc/raspiBackup.conf.bak. Do you answer with yes the configuration update is finished and you get following messages
--- RBK0240I: Saving current configuration /usr/local/etc/raspiBackup.conf to /usr/local/etc/raspiBackup.conf.bak.
--- RBK0244I: Merged configuration /usr/local/etc/raspiBackup.conf.merged copied to /usr/local/etc/raspiBackup.conf and activated.
That's the easiest way to activate the merged configuration file and you're done quickly.
But you also can answer no and the merged configuration file will not be activated. You get following message:
--- RBK0247I: Now review /usr/local/etc/raspiBackup.conf.merged and copy the configuration file to /usr/local/etc/raspiBackup.conf to finish the configuration update.
The new options in the merged configuration file can easily be identified:
# Smart recycle
# >>>>> NEW OPTION added in config version "0.1.4" <<<<<
DEFAULT_SMART_RECYCLE=0
# Smart recycle dryrun
# >>>>> NEW OPTION added in config version "0.1.4" <<<<<
DEFAULT_SMART_RECYCLE_DRYRUN=1
# Smart recycle parameters (daily, weekly, monthly and yearly)
# >>>>> NEW OPTION added in config version "0.1.4" <<<<<
DEFAULT_SMART_RECYCLE_OPTIONS="7 4 12 1"
Now use your editor and check /usr/local/etc/raspiBackup.conf.merged and change the contents if needed. Finally copy the merged configuration file to /usr/local/etc/raspiBackup.conf to activate the new configuration file.
Finally execute as usual whenever you upgraded raspiBackup a backup/restore cycle and test whether everything still works as before.
raspiBackup supports usage of different configuration files. The automatic configuration update is only done for /usr/local/etc/raspiBackup.conf. All other configuration files have to be updated manually. Just copy the lines marked as new configuration lines into the other configuration files.
Page 1 of 2