Framp's Linux Tips and Tricks
Toggle Navigation
  • You are here:  
  • Home

Deutsch / English

  • German (DE)
  • English (US)

In order to provide you with the best online experience this website uses cookies. Delete cookies

In order to provide you with the best online experience this website uses cookies.

By using our website, you agree to our use of cookies. Learn more

I agree

Data protection

Data protection
 

This Privacy Policy clarifies the nature, scope and purpose of the processing of personal data (hereinafter referred to as "Data") within our online offering and the related websites, features and content, as well as external online presence, e.g. our social media profiles on. (collectively referred to as "online offer"). With regard to the terminology used, e.g. "Processing" or "Responsible", we refer to the definitions in Article 4 of the General Data Protection Regulation (GDPR).

 
Responsible

Peter Taube
Bismarckstrasse 13
71272 Renningen
Germany
e-mail address: contact @ linux-tips-and-tricks.de
Imprint: https://www.linux-tips-and-tricks.de/de/impressum

 
Types of processed data:

- usage data (e.g., websites visited, interest in content, access times).
- Meta / communication data (e.g., device information, IP addresses).

 
Purpose of processing

- Provision of the online offer, its functions and contents.
- Answering contact requests and communicating with users.
- Safety measures.
- Reach Measurement / Marketing


Used terms

"Personal data" means any information relating to an identified or identifiable natural person (hereinafter the "data subject"); a natural person is considered as identifiable, which can be identified directly or indirectly, in particular by means of assignment to an identifier such as a name, to an identification number, to location data, to an online identifier (eg cookie) or to one or more special features, that express the physical, physiological, genetic, mental, economic, cultural or social identity of this natural person.

"Processing" means any process performed with or without the aid of automated procedures or any such process associated with personal data. The term goes far and includes virtually every handling of data.

"Responsible person" means the natural or legal person, public authority, body or body that decides, alone or in concert with others, on the purposes and means of processing personal data.

 

Relevant legal bases

In accordance with Art. 13 GDPR, we inform you about the legal basis of our data processing. Unless the legal basis in the data protection declaration is mentioned, the following applies: The legal basis for obtaining consent is Article 6 (1) lit. a and Art. 7 DSGVO, the legal basis for the processing for the performance of our services and the execution of contractual measures as well as the response to inquiries is Art. 6 (1) lit. b DSGVO, the legal basis for processing in order to fulfill our legal obligations is Art. 6 (1) lit. c DSGVO, and the legal basis for processing in order to safeguard our legitimate interests is Article 6 (1) lit. f DSGVO. In the event that vital interests of the data subject or another natural person require the processing of personal data, Art. 6 para. 1 lit. d DSGVO as legal basis.

 
Safety measures

We ask you to inform yourself regularly about the content of our privacy policy. We will adjust the privacy policy as soon as the changes to the data processing we make require it. We will notify you as soon as the changes require your participation (eg consent) or other individual notification.

 
Collaboration with processors and third parties

If, in the context of our processing, we disclose data to other persons and companies (contract processors or third parties), transmit them to them or otherwise grant access to the data, this will only be done on the basis of a legal permission (eg if a transmission of the data to third parties, as required by payment service providers, pursuant to Art. 6 (1) (b) GDPR to fulfill the contract), you have consented to a legal obligation or based on our legitimate interests (eg the use of agents, webhosters, etc.).

If we commission third parties to process data on the basis of a so-called "contract processing contract", this is done on the basis of Art. 28 GDPR.

 
Transfers to third countries

If we process data in a third country (ie outside the European Union (EU) or the European Economic Area (EEA)) or in the context of the use of third party services or disclosure or transmission of data to third parties, this will only be done if it is to fulfill our (pre) contractual obligations, on the basis of your consent, on the basis of a legal obligation or on the basis of our legitimate interests. Subject to legal or contractual permissions, we process or have the data processed in a third country only in the presence of the special conditions of Art. 44 et seq. DSGVO. That the processing is e.g. on the basis of specific guarantees, such as the officially recognized level of data protection (eg for the US through the Privacy Shield) or compliance with officially recognized special contractual obligations (so-called "standard contractual clauses").

 

Rights of data subjects

You have the right to ask for confirmation as to whether the data in question is being processed and for information about this data as well as for further information and a copy of the data in accordance with Art. 15 GDPR.

You have accordingly. Art. 16 DSGVO the right to demand the completion of the data concerning you or the correction of the incorrect data concerning you.

In accordance with Art. 17 GDPR, they have the right to demand that the relevant data be deleted immediately or, alternatively, to require a restriction of the processing of data in accordance with Art. 18 GDPR.

You have the right to demand that the data relating to you, which you have provided to us, be obtained in accordance with Art. 20 GDPR and request their transmission to other persons responsible.

You have gem. Art. 77 DSGVO the right to file a complaint with the competent supervisory authority.

 
Withdrawal

You have the right to grant consent in accordance with. Art. 7 para. 3 DSGVO with effect for the future

 
Right to

You can object to the future processing of your data in accordance with Art. 21 GDPR at any time. The objection may in particular be made against processing for direct marketing purposes.

 
Cookies and right to object in direct mail

"Cookies" are small files that are stored on users' computers. Different information can be stored within the cookies. A cookie is primarily used to store the information about a user (or the device on which the cookie is stored) during or after his visit to an online offer. Temporary cookies, or "session cookies" or "transient cookies", are cookies that are deleted after a user leaves an online service and closes his browser. In such a cookie, e.g. the contents of a shopping cart are stored in an online store or a login jam. The term "permanent" or "persistent" refers to cookies that remain stored even after the browser has been closed. Thus, e.g. the login status will be saved if users visit it after several days. Likewise, in such a cookie the interests of the users can be stored, which are used for range measurement or marketing purposes. A "third-party cookie" refers to cookies that are offered by providers other than the person who manages the online offer (otherwise, if it is only their cookies, this is called "first-party cookies").

We can use temporary and permanent cookies and clarify this in the context of our privacy policy.

If users do not want cookies stored on their computer, they will be asked to disable the option in their browser's system settings. Saved cookies can be deleted in the system settings of the browser. The exclusion of cookies can lead to functional restrictions of this online offer.

A general contradiction to the use of cookies used for online marketing purposes can be found in a variety of services, especially in the case of tracking, via the US website http://www.aboutads.info/choices/ or the EU site http://www.youronlinechoices.com/ be explained. Furthermore, the storage of cookies can be achieved by switching them off in the settings of the browser. Please note that not all features of this online offer may be used.

 

Deletion of data

The data processed by us are deleted or limited in their processing in accordance with Articles 17 and 18 GDPR. Unless explicitly stated in this privacy policy, the data stored by us are deleted as soon as they are no longer required for their purpose and the deletion does not conflict with any statutory storage requirements. Unless the data is deleted because it is required for other and legitimate purposes, its processing will be restricted. That The data is blocked and not processed for other purposes. This applies, for example for data that must be kept for commercial or tax reasons.

According to legal requirements in Germany, the storage takes place in particular for 10 years according to §§ 147 Abs. 1 AO, 257 Abs. 1 Nr. 1 and 4, Abs. 4 HGB (books, records, management reports, accounting documents, trading books, relevant for taxation Documents, etc.) and 6 years in accordance with § 257 (1) no. 2 and 3, para. 4 HGB (commercial letters).

According to legal regulations in Austria the storage takes place especially for 7 years according to § 132 paragraph 1 BAO (accounting documents, receipts / invoices, accounts, receipts, business papers, statement of income and expenses, etc.), for 22 years in connection with real estate and for 10 years in the case of documents relating to electronically supplied services, telecommunications, broadcasting and television services provided to non-entrepreneurs in EU Member States and for which the Mini-One-Stop-Shop (MOSS) is used.

 
Hosting

The hosting services we use are for the purpose of providing the following services: infrastructure and platform services, computing capacity, storage and database services, security and technical maintenance services we use to operate this online service.

Here we, or our hosting provider, process inventory data, contact data, content data, contract data, usage data, meta and communication data of customers, interested parties and visitors to this online offer on the basis of our legitimate interests in an efficient and secure provision of this online offer acc. Art. 6 para. 1 lit. f DSGVO i.V.m. Art. 28 DSGVO (conclusion of contract processing contract).

 
Collection of access data and log files

We, or our hosting provider, collects on the basis of our legitimate interests within the meaning of Art. 6 para. 1 lit. f. DSGVO Data on every access to the server on which this service is located (so-called server log files). The access data includes name of the retrieved web page, file, date and time of retrieval, amount of data transferred, message about successful retrieval, browser type and version, the user's operating system, referrer URL (the previously visited page), IP address and the requesting provider ,

Logfile information is stored for security purposes (for example, to investigate abusive or fraudulent activities) for a maximum of 7 days and then deleted. Data whose further retention is required for evidential purposes shall be exempted from the cancellation until final clarification of the incident.

 

 
Comments and posts

If users leave comments or other contributions, their IP addresses may be based on our legitimate interests within the meaning of Art. 6 para. 1 lit. f. DSGVO be stored for 7 days. This is for our own safety, if someone leaves illegal content in comments and contributions (insults, prohibited political propaganda, etc.). In this case, we ourselves can be prosecuted for the comment or post and are therefore interested in the identity of the author.

Furthermore, we reserve the right, in accordance with our legitimate interests. Art. 6 para. 1 lit. f. DSGVO to process the information of users for the purpose of spam detection.

Range measurement with Matomo

As part of Matomo's range analysis, the following data is processed on the basis of our legitimate interests (ie interest in the analysis, optimization and economic operation of our online offer as defined in Art. 6 (1) lit. DSGVO): the type of browser you use and the browser version, the operating system you are using, your country of origin, the date and time of the server request, the number of visits, how long you have spent on the site, and the external links you have activated. The IP address of the users is anonymized before being saved.

Matomo uses cookies that are stored on users' computers and that allow an analysis of how users use our online offerings. In this case, pseudonymous usage profiles of the users can be created from the processed data. The cookies have a retention period of one week. The information generated by the cookie about your use of this website will only be stored on our server and will not be passed on to third parties.

Users can object to the anonymized data collection by the program Matomo at any time with effect for the future by clicking on the link below. In this case, a so-called opt-out cookie is stored in your browser, with the result that Matomo no longer collects session data. If users delete their cookies, however, this means that the opt-out cookie is also deleted and must therefore be reactivated by the users.

 

The logs with the data of the users will be deleted after 6 months at the latest.

 
Online presence in social media

We maintain online presence within social networks and platforms in order to communicate with customers, prospects and users active there and to inform them about our services. When calling the respective networks and platforms, the terms and conditions and the data processing guidelines apply to their respective operators.

Unless otherwise stated in our Privacy Policy, we process users' data as long as they communicate with us within social networks and platforms, e.g. Write posts on our online presence or send us messages.

 
Integration of services and contents of third parties

Based on our legitimate interests (ie interest in the analysis, optimization and economic operation of our online offer within the meaning of Art. 6 (1) lit. DSGVO), we make use of content or services offered by third-party providers in order to provide their content and services Services, such as Include videos or fonts (collectively referred to as "content").

This always presupposes that the third-party providers of this content perceive the IP address of the users, since they could not send the content to their browser without the IP address. The IP address is therefore required for the presentation of this content. We endeavor to use only content whose respective providers use the IP address solely for the delivery of the content. Third parties may also use so-called pixel tags (invisible graphics, also referred to as "web beacons") for statistical or marketing purposes. The "pixel tags" can be used to evaluate information such as visitor traffic on the pages of this website. The pseudonymous information may also be stored in cookies on the user's device and may include, but is not limited to, technical information about the browser and operating system, referring web pages, visit time, and other information regarding the use of our online offer.

 
Google ReCaptcha

We bind the function to detect bots, e.g. when entering into online forms ("ReCaptcha") of the provider Google LLC, 1600 Amphitheater Parkway, Mountain View, CA 94043, USA. Privacy Policy: https://www.google.com/policies/privacy/, opt-out: https://adssettings.google.com/authenticated.

 

Use of Facebook social plugins

Based on our legitimate interests (ie interest in the analysis, optimization and economic operation of our online offer within the meaning of Art. 6 (1) f. DSGVO) we use social plugins ("plugins") of the social network facebook.com, which operated by Facebook Ireland Ltd., 4 Grand Canal Square, Grand Canal Harbor, Dublin 2, Ireland ("Facebook"). The plugins can represent interaction elements or content (eg videos, graphics or text contributions) and can be recognized by one of the Facebook logos (white "f" on blue tile, the terms "Like", "Like" or a "thumbs up" sign ) or are marked with the addition "Facebook Social Plugin". The list and appearance of Facebook Social Plugins can be viewed here: https://developers.facebook.com/docs/plugins/.

Facebook is certified under the Privacy Shield Agreement, which provides a guarantee to comply with European privacy legislation (https://www.privacyshield.gov/participant?id=a2zt0000000GnywAAC&status=Active).

When a user invokes a feature of this online offering that includes such a plugin, their device establishes a direct connection to the Facebook servers. The content of the plugin is transmitted by Facebook directly to the device of the user and incorporated by him into the online offer. In the process, user profiles can be created from the processed data. We therefore have no influence on the amount of data that Facebook collects with the help of this plugin and therefore informs the users according to our knowledge.

By integrating the plugins, Facebook receives the information that a user has accessed the corresponding page of the online offer. If the user is logged in to Facebook, Facebook can assign the visit to his Facebook account. If users interact with the plugins, for example, press the Like button or leave a comment, the information is transmitted from your device directly to Facebook and stored there. If a user is not a member of Facebook, there is still the possibility that Facebook will find out and save their IP address. According to Facebook, only an anonymous IP address is stored in Germany.

The purpose and scope of the data collection and the further processing and use of the data by Facebook, as well as the related rights and setting options for protecting the privacy of users, can be found in Facebook's privacy policy: https://www.facebook.com/about/privacy/ ,

If a user is a Facebook member and does not want Facebook to collect data about him via this online offer and link it to his member data stored on Facebook, he must log out of Facebook and delete his cookies before using our online offer. Other settings and inconsistencies regarding the use of data for advertising purposes are possible within the Facebook profile settings: https://www.facebook.com/settings?tab=ads or via the US-American site http://www.aboutads.info / choices / or the EU page http://www.youronlinechoices.com/. The settings are platform independent, i. they are adopted for all devices, such as desktop computers or mobile devices.

 

Google Adsense

This website uses Google Adsense, a web advertising service of Google Inc., USA ('' Google ''). Google Adsense uses so-called 'cookies' (text files) which are stored on your computer and which allows you to analyze the use of the website by you. Google Adsense also uses so-called 'web beacons' (small invisible graphics) to gather information. By using the web beacon, simple actions such as visitor traffic on the website can be recorded and collected. The information generated by the cookie and / or web beacon about your use of this website (including your IP address) will be transmitted to and stored by Google on servers in the United States. Google will use this information to evaluate your use of the website in terms of advertising, to compile reports on website activity and advertisements for website operators, and to provide other services related to website activity and internet usage. Google may also transfer this information to third parties if required by law or as far as third parties process this data on behalf of Google. Google will in no case associate your IP address with other Google data. You can prevent the storage of cookies on your hard disk and the display of web beacons by selecting 'Do not accept cookies' in your browser settings (In MS Internet Explorer under '' Tools> Internet Options> Privacy> Settings '' in Firefox under '' Tools> Settings> Privacy> Cookies ''); however, please note that in this case you may not be able to use all features of this website to the fullest extent. By using this website, you consent to the processing of data about you by Google in the manner and for the purposes set out above.

 

Created witht Datenschutz-Generator.de of RA Dr. Thomas Schwenke and translated from German into English with Google Translate

 

New pages

  • raspiBackup Snapshots
  • raspiBackupDialog - a convenient helper script for raspiBackup
  • raspiBackup - Ubuntu support

Most visited

  • raspiBackup - Create regularly and unattended backups of your running Raspberries
  • Welcome
  • raspiBackup - Installation and configuration in 5 minutes

raspiBackup - Manual restore of a tgz backup

Details
Category: raspiBackup
Created: 14 October 2017
Last Updated: 25 January 2023
Hits: 55
  • restore
  • raspiBackup
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Read more: raspiBackup - Manual restore of a tgz backup Add new comment Hits: 55

The backup directory created by raspiBackup contains all information required to restore this backup also manually with standard Linux tools. The following page describes how to restore a normal tgz backup.

raspiBackup - Create regularly and unattended backups of your running Raspberries

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 18 June 2013
Last Updated: 10 January 2023
Hits: 180481
  • backup
  • raspberry
  • raspiBackup

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
Read more: raspiBackup - Create regularly and unattended backups of your running Raspberries 203 comments Hits: 180481

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

 

Raspberry Compute Module 4 (CM4) setup guide on eMMC and NVMe

Details
Category: Raspberry
Created: 12 June 2022
Last Updated: 03 January 2023
Hits: 3509
  • raspberry
  • CM4
  • compute module

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
Read more: Raspberry Compute Module 4 (CM4) setup guide on eMMC and NVMe Add new comment Hits: 3509

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

CM4Parts

Hynix NVMe, CM4 and Waveshare Mini Base Board A (from top to bottom)

 

 

Parts assembled

 

CM4

 

raspiBackup - FAQ

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 01 December 2015
Last Updated: 28 December 2022
Hits: 30543
  • raspberry
  • raspiBackup

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive
Read more: raspiBackup - FAQ 41 comments Hits: 30543

Frequent asked questions about raspiBackup. Every new user of raspiBackup should read all questions and answers.

raspiBackup - Support for Raspberry Compute Module 4 and NVMe

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 11 June 2022
Last Updated: 12 December 2022
Hits: 2521
  • raspiBackup
  • CM4
  • compute model
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Read more: raspiBackup - Support for Raspberry Compute Module 4 and NVMe Add new comment Hits: 2521

I just got a CM4 donated with 1GB main memory, 32GB eMMC and 128 GB NVMe. Thank you very much to the donator!

CM4 was already supported by raspiBackup but only running from a SD card, eMMC or USB boot. It's already possible to use NVMe when it's provided in an USB plug because it's exposed as a normal disk as /dev/sdx but there was no way to have NVMe plugged in in the PCI lane exposed as /dev/nvme.  Now I fortunately was able to add  this support to raspiBackup. This support is available now in release 0.6.8.

 CM4Parts

raspiBackup - Invocation syntax and options

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 18 June 2013
Last Updated: 11 December 2022
Hits: 541
  • backup
  • raspberry
  • raspiBackup
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Add new comment Hits: 541

Invocationsyntax and -options

raspiBackup has to be invoked as user root or with sudo. The invocation syntax is

raspiBackup.sh Option1 Option2 Option3 ... backupdirectory 
and starting with Release 0.6.6 you can omit the extension .sh
 

raspiBackup Option1 Option2 Option3 ... backupdirectory

 
There are a lot of options available to customize the backup process. The most important parameters are marked in red. Some options require addition parameters as -k 3 or -m 1.

All default options can be overwritten in a configuration file /usr/local/etc/raspiBackup.conf. A sample configuration file which has the standard options defined can be downloaded here.

All options which turn something on or off can be controlled by a trailing + or -. Example: Option -z and option -z+ turn on the backupcompression. Option -z- turns off the backupcompression and ignores the definition DEFAULT_ZIP_BACKUP in the configuration file. That way it's possible to turn off options in the commandline even they are turned on in the configuration file.

In addition to /usr/local/etc/raspiBackup.conf other config files are read if they exist. They are included in following sequence and overide the previous option settings. Last but not least the invocation options overide all previously defined options in the configuration files.

Priority Filename
5  /usr/local/etc/raspiBackup.conf
4 ~/.raspiBackup.conf
3 $(pwd)/.raspiBackup.conf
2 -f <configFile>
1  Invocation options

 

Options theme sorted

  • Options, which configure the backup
    • -k : number of backups to keep
    • -t : Type of backup (dd, tar, rsync)
    • -P : Partitionorientierted backup mode
    • -z: Compression of backup for dd or tar
    • -u: Add additional pathes to explude from backup
    • -T: Define the partitions to backup for partition oriented mode
    • -M: Create a snapshot
  • Options, which configure  the messages and logs
    • -m: Details of messages
    • -L: Location to store the execution log
    • -l: Enable debug mode
    • -G: Message language (English or German)
    • -A: Send the execution log in the notification email
    • -v: Log all messages from backup tools used to create the backup
  • Options, which configure the notification email
    • -e: eMailAdress which receives the notification email
    • -s: eMailClientProgram which is used to send the notification email
    • -E: Optional parameters for emailClientprograms
    • -F: Simulates a backup run. useful to quickly test the eMail notification
  • Options,  which update, restore and distribute raspiBackup
    • -U: Update of raspiBackup with the lates version and saves the current version
    • -n: Enable notification when a new raspiBackup version is available
    • -V: Restore a previous raspiBackup version
    • -y: Distribute current raspiBackup on local hosts via scp
  • Options, which start and stop services and run plugins before and after backup processing
    • -o: Commands which stop services before the backup
    • -a: Commands which start services after the backup
    • -N: Defines plugins to invoke before and after backup processing
  • Miscellaneous options
    • -b: Blocksize which will be used for dd backup
    • -D: Additional optional dd options

 

Options alphabetical sorted

Parameter Function Default Option can be set in installer Option in configuration file
-a

Commands to start services stopped before the backup. Example "service xbmc start" (Attention: There are leading and trailing double quotes). This option is mandatory together with option -o.

Multiple commands have to be separated by && . As an alternative use a wrapperscript (See below). The commands should have the inverse sequence as the commands used for the  -o parameter.

Example:

-a "service nfs-kernel-server start && service samba start"

If there are no services to stop use a colon ":" as parameter.

See also FAQ#1 and FAQ#18

Note: 

All commands are executed as root. There is no sudo required.

None yes

DEFAULT_STARTSERVICES

-b Blocksize used in the dd command 1MB no

DEFAULT_DD_BLOCKSIZE

-B

Boot partition will be save with tar instead of dd

Note: This option has no function if partition oriented mode is used and option -P is used or DEFAULT_PARTITIONBASED_BACKUP=1 is defined in the configuration file.

No no

DEFAULT_TAR_BOOT_PARTITION_ENABLED

--coloring  Starting with version 0.6.5 messages can be colorized. Possible parms C for console and/or M for eMail. See also option --eMailColoring if you use the postfix eMailClient. CM no

DEFAULT_COLORING

 -D Addition invocation parameters for dd command (e.G.. "conv=notrunc,noerror,sync")  None no

DEFAULT_DD_PARMS

--dynamic

Mount

Starting with version 0.6.6 the specified mount point or partition will be mounted during startup and umounted at the end. If it's already mounted it's not umounted at the end. The mount point has to be defined in /etc/fstab. The option argument can either be the mount point (e.g. /backup) or the backup partition name (e.g. /dev/sdb1).  None no

DEFAULT_DYNAMIC_MOUNT

 -e email address which will get a notification eMail  None yes

DEFAULT_EMAIL

-E

Optional additional parameters which are passed in the eMail call. For sendEmail use "-f sender.mail@senderdomain -s smtp-server:587 -xu username -xp password".

Attention: The parameters for -E have to have a leading and trailing double quote ". It's  useful to use parameter -F to speed up the test of the email notification function

Attention: If option -l 1 is used the password will be logged in the log file. Masquerade the password before sending the log to somebody.

None no

DEFAULT_EMAIL_PARMS

--eMail

Coloring

Default is to use the subject header in eMails to control eMail coloring because that's the way used by most of the emailCients. If postfix is used then parameter OPTION has to be used because postfix uses a dedicated option to control email coloring.
SUBJECT no

DEFAULT_EMAIL_COLORING

-f Configuration file which is includes last. See here for all configuration files and their precedence. No no  
-F Fake backup. This option is useful when raspiBackup is initially tested. The time consuming backup is not started but all the parameters are checked and an email is sent. No no  
-g This option enables a progress bar during backup and restore. For a tar backup there is no progress bar available.   no  
-G Define language of messages. Possible messages are DE (German) and EN (English). Volunteers to translate the messages into another languages are welcome.  Please contact me for details.

System language

If the system language is not supported EN (English) is used.

yes

DEFAULT_LANGUAGE

 -h  Help  No no  

--ignore

Additional

Partitions

Starting with version 0.6.5 raspiBackup allows to have more than two partitions on the SD card when tar or rsync backup is used. But only the first two partitions, /boot and / are saved and restored. Attention: All other paritions are not saved. No no

DEFAULT_IGNORE_ADDITIONAL_PARTITIONS

 -k

Number of backups to keep for all backup types if not overridden by following option. If you use the default you keep 3 dd, 3 tar and 3 rsync backups.

Note: This option is ignored when intelligent rotaion strategy is used.

 3 yes

DEFAULT_KEEPBACKUPS

--keep_<type>

Starting with version 0.6.4.3: Number of backups to keep for the specific backup type.

<type> can be any backup type, eg dd, ddz, tar, tgz or rsync

Note: These options are ignored when intelligent rotaion strategy is used.

Parameter for option -k no

DEFAULT_KEEPBACKUPS_{DD|DDZ|TAR|TGZ|RSYNC}

 -l

Log level defines whether a debug log will be created:

- off  -> No debug log

- debug -> Create debug log

Attention:  Logfile may contain sensitive data in some situations (E.g. external static IP addresses, eMailAddresses, passwords for mount commands or eMail server ...). The debug logs are stored in the backup location. In case the backup fails and the backup directory will be cleaned up the debug log is saved in the home directory of the caller first.

 on no

DEFAULT_LOG_LEVEL

-L

Defines the log target for raspiBackup.log

varlog: Target is /var/log/raspiBackup.log

backup: Log will be stored in created backup

current: Use current directory

<filename>:  Write log into <filename>. In addition the messages are written into a .msg file.

backup no

DEFAULT_LOG_OUTPUT

-m

Message details:

- minimal -> Write important messages only

- detailed -> Write a lot of messages to show the progress

minimal yes

DEFAULT_MSG_LEVEL

-M

This option allows to create raspiBackup snapshots which are not included in the backup recycle process. In addition the passed text is appended to the backup directory name. See also this page for details about snapshots.

Note: raspiBackup snapshots are normal backups with special properties but no real snapshots like LVM or btrf snapshots

Note: These backup directories are not included in the backup recycle process and have to be deleted manually.

  no  
-n Notify if there is a newer version of raspiBackup available Yes no

DEFAULT_NOTIFY_UPDATE

-N Activation of plugins to activate custom code. See this page for details which also offers three sample plugins which report the CPU temperature and the memory utilization before and after the backup run. None no

DEFAULT_EXTENSIONS

--notify

Start

Starting with version 0.6.5 it's possible to get an eMail or Telegram notification when raspiBackup starts. Default is to send an eMail or notification only when raspiBackup finishes. No no

DEFAULT_NOTIFY_START

-o

Commands to stop services before the backup. Example "service smb stop" (Attention: There are leading and trailing double quotes). This option is mandatory together with option -a.

Multiple commands have to be separated by && . As an alternative use a wrapperscript (See below). The commands should have the inverse sequences as the commands used for the  -a parameter

Example:

-o "service samba stop && service nfs-kernel-server stop"

If there are no services to stop use a colon ":" as parameter.

See also FAQ#1 and FAQ#18 

Note: 

All commands are executed as root. There is no sudo required.

None yes

DEFAULT_STOPSERVICES

-P Enable partitionoriented mode which allows to save more than the first two partitions which are saved in the normal mode. Use parameter -T to define which partitions should be saved. off yes

DEFAULT_PARTITIONBASED_BACKUP

--reboot

System

Starting with release 0.6.7 this option initiates a reboot when the backup run finished. This way all services are restarted again. Arguments passed with option -a will be ignored because of this.

Note: If option -F is used no reboot will be executed.

off no

DEFAULT_REBOOT_SYSTEM

-s

email program to use to sent the notification eMail  {mail|sendEmail|ssmtp|msmtp}. Use mail also for postfix and nullmailer and install mailtools. For sendEmail use also parameter -E to pass mandatory parameters (See parameter -E description for details)

Other eMailClients can be used via an eMailPlugin Then mailext has to passed as the parameter. See this page for details about the eMailPlugin.

mail no

DEFAULT_MAILPROGRAM

-S An update with option -U is executed even the versions are identical. A local betaversion and a local normal version will be replaced with the latest code level. It's primarily used to update a local beta version to the latest code level. off no  

--smart

Recycle

Starting with version 0.6.5 this option enables the intelligent rotationstrategy. For details see here. This also disables all --keep options and they don't have to be disabled by setting them to 0. off yes

DEFAULT_SMART_RECYCLE

--smart

Recycle

Dryrun

Starting with version 0.6.5 this option enables or disables the test mode of the intelligent rotationstrategy on. For details see here.

yes no

DEFAULT_SMART_RECYCLE_DRYRUN

--smart

Recycle

Options

Starting with version 0.6.5 this option defines the intelligent rotationstrategy parameters. For details see here. "7 4 12 1" yes

DEFAULT_SMART_RECYCLE_OPTIONS

--system

status

A list of running services and open files is reported in the debug logfile.   no  
-t

Backup type which can be dd, tar or rsync. rsync uses hardlinks if the backupfilesystem is an ext3/ext4 partition 

Attention:  rsync should not be used with NTFS formatted Backuppartitions because cannot store the access rights of an ext3/4 filesystem correctly. Therefore the access rights cannot be restored correctly on an ext3/4 filesystem and the restored image is unusable. In addition hardlinks are supported only on ext3/4 filesystems in order to minimze disk space usage.

See details of the backuptypes. An external root filesystem will be saved if tar or rsync backup is used and option -P is not selected. Parameter -z can be used in addition to zip the backups to reduce the backup size.

Note: dd backup can be controlled by configuration parameter DEFAULT_DD_BACKUP_SAVE_USED_PARTITIONS_ONLY which saves backuptime and -space. For details of the parameter see bottom of table.

dd yes

DEFAULT_BACKUPTYPE

-T

If the partitionoriented backupmode is selected with option -P this parameter can be used to define which partitions should be saved. Example: -T "1 2 5" saves the first two partitions and the fifth partition. * saves all partitions. 

* until release 0.6.5.1

"1 2" starting with release 0.6.6

yes

DEFAULT_PARTITIONS_TO_BACKUP 

--telegram

Token

--telegram

ChatID

--telegram

Notifications

Starting with version 0.6.5 Telegram notifications are supported. You have to configure the token and chatid. Notifications option can be S for success and/or F for failure. With "M" raspiBackup messages are attached in a file.. With "m" raspiBackup messages are sent too. Any of these options can be combined. Example: "SFM" or "Sm". Options "M" and "m" cannot be used together.

No

 

no

DEFAULT_TELEGRAM_TOKEN

DEFAULT_TELEGRAM_CHATID
DEFAULT_TELEGRAM_NOTIFICATIONS

--timestamps This option can be used to prefix all messages with a timestamp. No no

DEFAULT_TIMESTAMPS

-u
Extension of the excludelist for a backup to exlude special files and directories.
 

Attention: Parameters have to follow the syntax of the backuptool used. Otherwise the backup will fail. Example for rsync or tar:

"--exclude=/backup/* --exclude=/rsnapshot/* --exclude=/www-data*/*" 

Note the enclosing double quotes!

Additional information about the syntax is available on the man pages of the backup tools used.

Following directories are not saved:
Backuppath used in invocation, /proc/* , /lost+found/* , /sys/* , /dev/* , /tmp/*, /boot/*, /run/* , /proc/* , /lost+found/* , /sys/* , /dev/* , /tmp/* , /boot/* , /run/*
In addition all mounted directories from external devices which are not mounted on / are not saved. It's only the boot parition /dev/mmcblk0p1 and the root partition /dev/mmcblk0p2 or the external root filesystem on /dev/sda1 which is saved.
 
Note for partitionoriented backup mode:
 
If option -P is used the directories mentioned above are exluded in all partition backups.
 
rsync:
   */directory/* - Excludes directory on all partitions
   mmcblk0p2/verzeichnis/* - Excludes directory on partition mmcblk0p2
 
tar:
   directory/* - Excludes directory on all partitions
 
None no

DEFAULT_EXCLUDE_LIST

--unsupported

Environment

Starting with release 0.6.7  this option allows to start raspiBackup also on unsupported environments. For details read this article. off no  
-U

Upgrades the current raspiBackup version with the latest available version. The previous one will be saved as raspiBackup.sh.n.m where n and m are the versionnumbers of raspiBackup.

Attention: Read this page and understand which changes and new functions will become available before upgrading.

See also option -S which forces an update with the latest version even the versions are identical.

No no  
--updateUUIDs Starting with release 0.6.4.4: A restore will create partitions with the same UUIDs and PARTUUIDs of the original system. This option will create new UUIDs and PARTUUIDs on the restored partitions. No no

DEFAULT_UPDATE_UUIDS

-v Verbose mode of the backup tools tar and rsync. This option is useful during initial manual backup tests in order to see the backup progress. No no

DEFAULT_VERBOSE

-V Presents a list of existing previous version and allows to select one of the version to restore. The actual version will be saved and can be restored later on. See also parameter -U. (Available with Release 0.6) No no  
--version

Display the version information of raspiBackup in following format:

Version: 0.6.3.2 CommitSHA: 8fbcd1a CommitDate: 2018-02-19 CommitTime: 19:18:31

That way it's possible to query the current version information in a programmatic way.

No no  
-y This option starts the deployment of the actual script to hosts which are defined in the configuration file. Access has to be possible without password and requires the keys to be copied into authorized_keys . That way you can quickly deploy a new script version on multiple hosts. No no

DEFAULT_DEPLOYMENT_HOSTS

-z Use gzip with dd or tar backup to reduce the backup size No yes

DEFAULT_ZIP_BACKUP

 

An eMail will be sent only in case of backup failure Note: If raspiBackup crashes because of unexpected reasons it may happen there is no eMail send even the backup failed.

You use this option on your own risk.

No no

DEFAULT_MAIL_ON_ERROR_ONLY

 

Backupoptions used by rsync backup.

You use this option on your own risk.

--delete -aHAx no

DEFAULT_RSYNC_BACKUP_OPTIONS

  Backupoptions used by tarbackup. You use this option on your own risk. -cpi no

DEFAULT_TAR_BACKUP_OPTIONS

 

Additional backupoptions used by rsync backup.

You use this option on your own risk.

  no

DEFAULT_RSYNC_BACKUP_ADDITIONAL_OPTIONS

 

Additional backupoptions used by rsync backup.

You use this option on your own risk.

  no

DEFAULT_TAR_BACKUP_ADDITIONAL_OPTIONS

  Bootpartition backups use hardlinks to minimze the backupspace because bootpartitions don't change often. Note: Ssupport of hardlinks on the backupspace required (ext3/ext4 filesystem) No no

DEFAULT_LINK_

BOOTPARTITIONFILES

 

dd backup only saves the space used by defined partitions. That way a backup of a 32 GB SD card with a 8GB partition only needs 8GB. The root partition in general uses the the whole SD card and has to be resized with gparted or resize2fs first appropriately.

See also FAQ#16

No no

DEFAULT_DD_BACKUP_SAVE_USED_PARTITIONS_ONLY

  This option is used to append the log to the eMail -a no

DEFAULT_APPEND_LOG_OPTION

  Define the sender eMail for ssmtp and msmtp. root@$(hostname) no

DEFAULT_SENDER_EMAIL

 

Backup restore test reminder Intervall (Unit: Months)

6 no

DEFAULT_RESTORE_REMINDER_INTERVAL

  Number of reminders to execute a backup restore test 3 no

DEFAULT_RESTORE_REMINDER_REPEAT

  Starting with version 0.6.4.3: Defined commands are executes before and after backup creation and before stopping and after starting system services (options -a and -o) No no

DEFAULT_BEFORE_STOPSERVICES

DEFAULT_AFTER_STARTSERVICES

  Starting with version 0.6.7 you can define a pre and post exit which is executed when a backup is restored. The syntax is identical to the extsion format for backups. Empty no

DEFAULT_RESTORE_EXTENSIONS

   Starting with version 0.6.7 you can redefine the color codes used for emails and console. The first pair defines the colors for warnings and the second pair the colors for errors. The first element of the pair is the HTML color code The second element defined the VT100 color code. ("#FF8000 33" "#FF0000 31")
 
 no

 DEFAULT_RESTORE_EXTENSIONS

 

Starting with version 0.6.8 you can sent notifications to pushover.

You have to register on https://pushover.net/ first and have to create an application.

PUSHOVER_USER is the Pushover User Key.

PUSHOVER_TOKEN is the API Token Key for you application.

Notifications option can be S for success and/or F for failure. With "M" raspiBackup messages are attached in a file.. With "m" raspiBackup messages are sent too. Any of these options can be combined. Example: "SFM" or "S"F.

Priorities are the Pushover priorities.

Sounds are the Pushover sounds.

  no

DEFAULT_PUSHOVER_TOKEN

DEFAULT_PUSHOVER_USER

DEFAULT_PUSHOVER_NOTIFICATIONS

DEFAULT_PUSHOVER_SOUND_SUCCESS

DEFAULT_PUSHOVER_SOUND_FAILURE

DEFAULT_PUSHOVER_PRIORITY_SUCCESS

DEFAULT_PUSHOVER_PRIORITY_FAILURE

 

Starting with version 0.6.8 you can sent notifications to slack.

Notifications option can be S for success and/or F for failure. With "M" raspiBackup messages are attached in a file.. With "m" raspiBackup messages are sent too. Any of these options can be combined. Example: "SFM" or "S"F.

  no DEFAULT_SLACK_WEBHOOK_URL
DEFAULT_SLACK_NOTIFICATIONS
 
Note: Options in the config file which are set to yes or no have to be set as 0 for no and 1 for yes.
 
All options for the restore of a backup are described here.
 

raspiBackup - Supported hardware and software

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 04 February 2022
Last Updated: 21 November 2022
Hits: 2651
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
Add new comment Hits: 2651

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 hardware with different Linux distributions. 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. 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:  German (DE) 
Created: 02 March 2014
Last Updated: 20 November 2022
Hits: 30077
  • backup
  • raspberry
  • restore
  • raspiBackup

User Rating: 3 / 5

Star ActiveStar ActiveStar ActiveStar InactiveStar Inactive
Read more: raspiBackup - How to restore your backup 74 comments Hits: 30077

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!
 

How to test the CPU temperature of my Raspberry and check whether the CPU speed was throttled ?

Details
Category: Raspberry
Also available:  German (DE) 
Created: 24 July 2019
Last Updated: 22 October 2022
Hits: 3694
  • raspberry

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
Read more: How to test the CPU temperature of my Raspberry and check whether the CPU speed was throttled ? Add new comment Hits: 3694

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 - Used all over the world

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 24 August 2019
Last Updated: 25 August 2022
Hits: 3937
  • raspiBackup

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive
Add new comment Hits: 3937

raspiBackup is used in a lot of countries all over the world  (as of 08/2022)

Countries: 63

AE United Arab Emirates

AL Albania

AR Argentina

AT Austria

AU Australia 

BA Bosnia and Herzegovina

BE Belgium

BG Bulgaria

BN Brunei

BR Brasila

CA Canada

CH Suisse

CL Chile

CN China

CY Cyprus

CZ Czech Republic

DE Germany

DK Denmark

DZ Algeria

EE Estonia

ES Spain

EU Europe

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

KR South Corea

LB Lebanon

LT Lithuania

LU Luxemburg

MD Moldovia

MT Malta

MX Mexico

MY Malaysia

NL Netherlands

NO Norway

NZ New Zealand

PA Panama

PL Poland

PT Portugal

RO Romania

RS Serbia

RU Russia Any access rejected since 2/24/2022

SE Sweden

SG Singapore

SI Slovenia

SK Slovakia

TH Thailand

TR Turkey

TW Taiwan

UA Ukraine

US United States of Amerika

ZA Zaire

 

 

raspiBackup - Use pishrink to reduce dd backups to a minimum size

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 09 August 2019
Last Updated: 08 August 2022
Hits: 6427
  • raspberry
  • raspiBackup
  • pishrink

User Rating: 3 / 5

Star ActiveStar ActiveStar ActiveStar InactiveStar Inactive
Read more: raspiBackup - Use pishrink to reduce dd backups to a minimum size 5 comments Hits: 6427

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 - How do hardlinks work with rsync

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 18 May 2020
Last Updated: 08 August 2022
Hits: 4975
  • rsync
  • raspiBackup
  • hardlinks

User Rating: 4 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Inactive
Read more: raspiBackup - How do hardlinks work with rsync Add new comment Hits: 4975

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.

raspiBackup - Configuration update when upgrading to a new version

Details
Category: raspiBackup
Also available:  German (DE) 
Created: 07 April 2020
Last Updated: 08 August 2022
Hits: 3425
  • raspiBackup

User Rating: 1 / 5

Star ActiveStar InactiveStar InactiveStar InactiveStar Inactive
Add new comment Hits: 3425

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.

  1. bash - Nice way to enhance and prettify execution trace enabled with -x
  2. Erfahrungen beim Umzug von Fritz!Box 7390 zu Fritz!Box 7590
  3. Protect Raspberry Pi against internet attacks and disable attacks into the local network with a firewall using iptables

Page 1 of 2

  • 1
  • 2

Mainmenu

  • Home
  • Text search
  • Welcome
  • File downloads
  • Contact

raspiBackup

  • Features
  • Introductionary video
  • User guide
  • Installation
  • Invocation and options
  • FAQ
  • Errormessages
  • Restore
  • Snapshots
  • Donations
  • Configuration examples
  • Smart recycle
  • Synology

Website

  • Database
  • Joomla
  • Networking
  • Programming
  • Raspberry
  • raspiBackup
  • Security
  • Server
  • VMware
  • Miscellaneous

Impressum
Datenschutzerklärung

Back to Top

© 2023 Framp's Linux Tips and Tricks