Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

The actual final raspxbmc version of February 2nd 2013 works perfect compared to the previous code drops. I have a Hama MCE remote control and it now works perfectly. Even the mouse pad works fine out of the box. Unfortunately the Context menu doesn't work - at least that's what I thought and read in the net. I spent hours to find a way to get this fixed and finally detected the file /opt/xbmc-bcm/xbmc-bin/share/xbmc/system/keymaps/hama_mce.xml on my pi and detected that contextmenu function is already mapped to a key on my hama MCE. But I didn't expect this key to be the contextmenu key.

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Raspberry PI owners should make sure access to their Pi from the internet is secure. It's possiblet o use ssh tunneling but the most secure and universal method is to use OpenVPN. That way all ports on Pi can be accessed from a remote client via the internet in a secure way. The following article describes how to install and configure OpenVPN on Pi and how to install and configure an OpenVPN client to access your Pi from the internet on a secure way. This configuration uses the simple variant which only allows one client at a time to connect and is suffient in most cases. The client configuration description covers Linux and Windows7.

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Create .xbmc/userdata/keymaps/mouse.xml to hold the following mouse mappings which will switch the mouse buttons:
 
<keymap>   
   <global>
      <mouse>
         <rightclick>leftclick</rightclick>
         <leftclick>rightclick</leftclick>
      </mouse>
   </global>
</keymap>
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Die folgende Datei .xbmc/userdata/keymaps/mouse.xml muss erstellt werden und den folgenden Inhalt bekommen:
 
<keymap>   
   <global>
      <mouse>
         <rightclick>leftclick</rightclick>
         <leftclick>rightclick</leftclick>
      </mouse>
   </global>
</keymap>
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

cron usually runs on Linux per default. Unfortunately my script didn't run which I added to the crontab on raspxbmc.  That's because cron is not enabled on raspbxbmc per default. The following link explains in detail how to activate cron on xbmc.  Then everything works like a charme.

 
 
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

It's possible to add custom code which is executed before and after the backup process via two script extensions. They are useful if modification of the backup script is required to extent the script capabilities and will be lost and thus have to be merged again and again every time when raspiBackup will be updated.

Three sample plugins are available and can be used as templates for new plugins. The first three report the CPU temperature, memory utilization and backup partition usage pre and post a backup run. The last one is called at the end of the backup and can be used to execute different actions depending on the success or failure of raspiBackup.

If you create your own plugin please share it with the community and announce it's availability in a comment. If there is any function missing for the plugin please write a comment and I'll check whether it's possible to provide the missing function.

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

raspiBackup creates a backup which contains all required information to restore a backup manually. User Micha wanted to restore a backup manually and kindly documented the steps in detail in a comment in German. I transleted his comments into English:

 

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

Following pages describe different usage scenarios and configurations. They should help to find the right usage configuration out of the various configuration options of raspiBackup. Later on these usage scenarios can be customized further. An overview of all option is available here. The different ways to restore a backup are described here.

All configurations which don't use a dd backup save an external rootfilesystem together with the SD boot partition. If the USB bootmode is used and no SD card is used any more the whole rootpartition is also saved.

 

Usage scenarios described:

1a. A Windows user wants to backup his Raspberry and restore it with windisk32imager on Windows.

1b. A Windows user has a 32GB SD card but uses only 12GB and 12GB should be saved only.

1c. A Windows user wants to use pishrink to create a minimal backup image.

2. Raspberry should be saved very fast. Backuppartition is a nfs mounted EXT4 partition which is provided by a Synology.

3. Raspberry should be saved on a Samba mounted filesystem, which is provided by a Windows box.

4. A snapshot should be saved because there are some major changes planned and it should be possible to revert quickly.

5. A USB boot system backup should include an additional partition.

6. Raspberry should be saved on a local USB stick or a local USB disk.

 

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive

Users of raspiBackup in the world (Status 01/2024)

Countries: 70

 

User Rating: 2 / 5

Star ActiveStar ActiveStar InactiveStar InactiveStar Inactive

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
 

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive

A lot of time people ask how the rsync backup type works and how hardlinks are used. Following article describes what happens when files are created and deleted on the file system in the backup process and how hardlinks are used.

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive

Depending on the backup method used in raspiBackup you should choose the right filesystem on your backup partition. Following table lists the different filesystems per backup method.

impossible: not possible, restricted: limited, possible: possible, plus: suggested

 

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

I noticed there are a lot of raspiBackup users who use dd as backup method. In particular users which work primarily on Windows  use dd because they can restore a dd backup on Windows with win32diskimager or equivilent tools. There is a certain risk with dd which doesn't exist with tar of rasync. That's why I suggest better to use tar or rsync .

 

Subcategories