Your IP address: 192.168.1.77 Servername or IP: 192.168.1.23 (192.168.1.23) m23 version and patch level: 23.1 rock (101712) Server status

» m23 project page   » m23 forum   » Commercial support   » m23 training  
god (Log out)


Server backup

Encrypt and upload backup

File storage service

Run server backup now



cron time base

cron time base



Add cron entry

Start minute (0-59)

Repeat ever N hours (1-23)

Show and print documentation for server restoration from backup.


Help: Server backup

This dialog will help you to create automatic backups of your m23 server at given points in time. The backups are containing the rescue data to restore the m23 server, the configuration of the operating system and the list of the installed packages. It is possible to restore the m23 server to the last saved sate with these files after a data loss or other damage. The backuped data can be stored on an external server in the network or uploaded to the internet and are encrypted via GPG before the upload, to make your data confidential.

This dialog for storing, encrypting and uploading consists of two parts.

  1. Encrypt and upload backup: This part deals with the encryption of the backups and copying them on an external storage.
  2. cron settings: Here you can specify the parameters for the cron daemon to determine the points of time for the automatic backup process.



Encrypt and upload backup

Here you need to enter the required access information for the chosen external storage and the GPG key for encrypting the backup data.

Hint for the GPG keys

Click on "Manage GPG keys", if the desired GPG key for encrypting the data cannot be found in the list.

  1. Choose the type of storing service at "File storage service". The following services are supported by m23:

    • -: This option stores the backups on the hard disk of the m23 server only. You should use this alternative, if you really do not want to use an external storage server. It is NOT possible to restore the m23 server in case of data loss e.g. caused by a head crash in the harddisk of the m23 server. The backups are stored on the m23 server in the directory /m23/root-only/serverBackups/ and can be copied manually to an external storage.
    • scp: Secure Copy allows to copy data to any computer that is reachable by the network and that is running the SSH daemon. This option is the method of choice, if you own an SSH server that is capable of storing the backup files. To add this server to your standard backup cycle is saving your m23 server in an optimal way.
    • share-online.biz: The m23 server will upload the encrypted backup data to a so-called file hosting service, if you choose this option. This may be an option for you, if don't own a server for storing the m23 server backups. Your backup data is safe due to the GPG encryption before the upload. The upload of your backup data may take some time.

  2. Click on "Change" after you made your decision.
  3. Depending on the choice of the external storage you need to give additional access information for the external storage.

    • scp

      To use "Secure Copy" you are required to enter the following values:

      • User: This is the user name the m23 server needs to connect to the SCP server and to copy the files to it.
      • SCP server: Enter the IP or the name of the SCP server accessible by the m23 server.
      • SCP store directory: The directory on the SCP server where to place the backup files. You should use full path names here.
      • GPG key: Choose the GPG key for encrypting the backups before copying.

      Hint

      You need to make sure that the SCP server can be reached by the root account of the m23 server. Add the contents of the file /root/.ssh/id_dsa.pub on the m23 server to the file ~/.ssh/authorized_keys on the SCP server owned by the user given above to ensure this. You can use the tool ssh-copy-id for the key exchange too: ssh-copy-id -i /root/.ssh/id_dsa.pub benutzer@SCP-Server.

  4. Finally, click on "Save" (independent of the chosen method).



cron settings

The cron daemon executes recurrent jobs at defined points in time and these can be defined with the dialog elements. Points in time for the current job are shown in a table under the heading "cron entries", if there are any. Waiting jobs are marked with a white dot and running jobs with an orange dot.

Step by step: Adding a new job

  1. Choose the time base you want to schedule the job for at "cron time base" first.
  2. Now click on "Change" to adjust the next dialog elements.
  3. You need to insert different values dependent on your previous choice:

    • Hourly: The job will be executed every hour or every N'th hour at the given minute.

      • Start minute: The minute the job will be started.
      • Repeat ever N hours: The interval between the runs in hours. (E.g. 2: execute every two hours).

    • Dayly: The job will be executed every day at the given time.

      • Start minute: The minute the job will be started.
      • Start hour: The hour the job will be started.

    • Weekly: The job will be started on a given day of week at a given time.

      • Start minute: The minute the job will be started.
      • Start hour: The hour the job will be started.
      • Day of week: The day of week the job will be started.

  4. Click on "Add" to add the job finally.

Deletion of jobs

Choose the entry from the list under "cron entries" and click on "Delete".