Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter ioBroker.backitup v3.1.x

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Test Adapter ioBroker.backitup v3.1.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • simatec
      simatec Developer Most Active @DK43 last edited by

      @dk43 Ich pushe gerade die v2.5.11 auf Github, wo ich versucht habe den Fehler mal zu fixen.
      Kannst du das bitte direkt in deiner Installation testen?

      DK43 1 Reply Last reply Reply Quote 0
      • DK43
        DK43 @simatec last edited by

        @simatec

        beim installieren

        $ iobroker url https://github.com/simatec/ioBroker.backitup.git --host iobroker-pi --debug
        
        install simatec/ioBroker.backitup#7449f768b8a58f5a996f2b504f07d9cff2cf61b6
        
        host.iobroker-pi Adapter "system.adapter.backitup.0" is stopped.
        
        npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
        
        up to date, audited 702 packages in 8s
        
        51 packages are looking for funding run `npm fund` for details
        
        
        upload [19] backitup.admin C:/Users/FujitsuSmartHome/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml
        
        upload [12] backitup.admin C:/Users/FujitsuSmartHome/node_modules/iobroker.backitup/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
        
        upload [1] backitup.admin C:/Users/FujitsuSmartHome/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript
        
        host.iobroker-pi Adapter "system.adapter.backitup.0" is started
        
        Process exited with code 0
        

        und debug unmittelbar nach dem restore

        2023-01-18 10:03:51.477 - info: admin.0 (4576) ==> Connected system.user.admin from ::1
        2023-01-18 10:03:52.001 - debug: backitup.0 (6468) telegram-instance:
        2023-01-18 10:03:54.155 - debug: backitup.0 (6468) Backup list be read ...
        2023-01-18 10:03:58.573 - info: admin.0 (4576) <== Disconnect system.user.admin from ::1
        2023-01-18 10:04:04.714 - info: host.iobroker-pi stopInstance system.adapter.backitup.0 (force=false, process=true)
        2023-01-18 10:04:04.717 - info: host.iobroker-pi stopInstance system.adapter.backitup.0 send kill signal
        2023-01-18 10:04:04.716 - info: backitup.0 (6468) Got terminate signal TERMINATE_YOURSELF
        2023-01-18 10:04:04.717 - info: backitup.0 (6468) cleaned everything up...
        2023-01-18 10:04:04.718 - info: backitup.0 (6468) terminating
        2023-01-18 10:04:04.719 - debug: backitup.0 (6468) Plugin sentry destroyed
        2023-01-18 10:04:04.721 - info: backitup.0 (6468) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2023-01-18 10:04:05.273 - info: host.iobroker-pi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2023-01-18 10:04:07.749 - info: host.iobroker-pi instance system.adapter.backitup.0 started with pid 6824
        2023-01-18 10:04:08.937 - debug: backitup.0 (6824) Redis Objects: Use Redis connection: 127.0.0.1:9001
        2023-01-18 10:04:08.963 - debug: backitup.0 (6824) Objects client ready ... initialize now
        2023-01-18 10:04:08.964 - debug: backitup.0 (6824) Objects create System PubSub Client
        2023-01-18 10:04:08.965 - debug: backitup.0 (6824) Objects create User PubSub Client
        2023-01-18 10:04:08.977 - debug: backitup.0 (6824) Objects client initialize lua scripts
        2023-01-18 10:04:08.983 - debug: backitup.0 (6824) Objects connected to redis: 127.0.0.1:9001
        2023-01-18 10:04:08.996 - debug: backitup.0 (6824) Redis States: Use Redis connection: 127.0.0.1:9000
        2023-01-18 10:04:09.001 - debug: backitup.0 (6824) States create System PubSub Client
        2023-01-18 10:04:09.002 - debug: backitup.0 (6824) States create User PubSub Client
        2023-01-18 10:04:09.008 - debug: backitup.0 (6824) States connected to redis: 127.0.0.1:9000
        2023-01-18 10:04:09.025 - debug: backitup.0 (6824) Plugin sentry Initialize Plugin (enabled=true)
        2023-01-18 10:04:09.322 - info: backitup.0 (6824) starting. Version 2.5.10 (non-npm: simatec/ioBroker.backitup#7449f768b8a58f5a996f2b504f07d9cff2cf61b6) in C:/Users/FujitsuSmartHome/node_modules/iobroker.backitup, node: v16.15.1, js-controller: 4.0.24
        2023-01-18 10:04:09.336 - debug: backitup.0 (6824) Backitup has recognized a win32 system
        2023-01-18 10:04:09.409 - info: backitup.0 (6824) [iobroker] backup was activated at 01:30 every 1 day(s)
        2023-01-18 10:04:09.469 - debug: backitup.0 (6824) [iobroker] 10 30 01 */1 * *
        2023-01-18 10:04:10.374 - error: backitup.0 (6824) Dropbox: "expired_access_token/..."
        2023-01-18 10:04:10.375 - error: backitup.0 (6824) Dropbox: "expired_access_token/..."
        2023-01-18 10:04:13.989 - debug: backitup.0 (6824) detect backup file 1 from googledrive: iobroker_2023_01_04-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.990 - debug: backitup.0 (6824) detect backup file 2 from googledrive: iobroker_2022_12_30-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.990 - debug: backitup.0 (6824) detect backup file 3 from googledrive: iobroker_2022_12_28-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.991 - debug: backitup.0 (6824) detect backup file 4 from googledrive: iobroker_2022_12_25-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.991 - debug: backitup.0 (6824) detect backup file 5 from googledrive: iobroker_2022_12_24-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.991 - debug: backitup.0 (6824) detect backup file 6 from googledrive: iobroker_2022_12_23-17_59_32_backupiobroker.tar.gz
        2023-01-18 10:04:13.991 - debug: backitup.0 (6824) detect backup file 7 from googledrive: iobroker_2022_12_23-17_54_33_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 8 from googledrive: iobroker_2022_12_23-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 9 from googledrive: iobroker_2022_12_21-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 10 from googledrive: iobroker_2022_12_20-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 11 from googledrive: iobroker_2022_12_19-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 12 from googledrive: iobroker_2022_12_18-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.992 - debug: backitup.0 (6824) detect backup file 13 from googledrive: iobroker_2022_12_17-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.993 - debug: backitup.0 (6824) detect backup file 14 from googledrive: iobroker_2022_12_13-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.993 - debug: backitup.0 (6824) detect backup file 15 from googledrive: iobroker_2022_12_12-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.993 - debug: backitup.0 (6824) detect backup file 16 from googledrive: iobroker_2022_12_08-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.993 - debug: backitup.0 (6824) detect backup file 17 from googledrive: iobroker_2022_12_07-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.993 - debug: backitup.0 (6824) detect backup file 18 from googledrive: iobroker_2022_12_03-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.994 - debug: backitup.0 (6824) detect backup file 19 from googledrive: iobroker_2022_12_02-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.994 - debug: backitup.0 (6824) detect backup file 20 from googledrive: iobroker_2022_12_01-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:13.995 - debug: backitup.0 (6824) detect last backup file: iobroker_2023_01_04-01_30_10_backupiobroker.tar.gz
        2023-01-18 10:04:15.253 - info: admin.0 (4576) ==> Connected system.user.admin from ::1
        2023-01-18 10:04:15.806 - debug: backitup.0 (6824) telegram-instance:
        2023-01-18 10:04:17.463 - debug: backitup.0 (6824) Backup list be read ...
        2023-01-18 10:04:26.589 - debug: backitup.0 (6824) set chmod for "C:/Users/FujitsuSmartHome/backups" successfully
        2023-01-18 10:04:33.978 - info: admin.0 (4576) <== Disconnect system.user.admin from ::1
        2023-01-18 10:04:43.975 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
        2023-01-18 10:04:43.980 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2023-01-18 10:04:43.981 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
        2023-01-18 10:04:43.981 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
        2023-01-18 10:04:46.108 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
        2023-01-18 10:04:48.452 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
        2023-01-18 10:04:48.457 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2023-01-18 10:04:48.457 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
        2023-01-18 10:04:48.458 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
        2023-01-18 10:04:50.598 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
        2023-01-18 10:04:53.233 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
        2023-01-18 10:04:53.238 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2023-01-18 10:04:53.239 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
        2023-01-18 10:04:53.239 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
        2023-01-18 10:04:55.362 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
        

        komischerweise wird mir noch die v2.5.10 angezeigt.

        simatec 2 Replies Last reply Reply Quote 0
        • simatec
          simatec Developer Most Active @DK43 last edited by

          @dk43 Kann es sein, dass dein altes System nicht up2date war?
          Zeige mal bitte die Ausgabe von iobroker status

          DK43 1 Reply Last reply Reply Quote 0
          • simatec
            simatec Developer Most Active @DK43 last edited by

            @dk43 sagte in Test Adapter ioBroker.backitup v2.5.x:

            komischerweise wird mir noch die v2.5.10 angezeigt.

            Warte mal noch kurz, der push läuft noch

            1 Reply Last reply Reply Quote 0
            • DK43
              DK43 @simatec last edited by

              @simatec sagte in Test Adapter ioBroker.backitup v2.5.x:

              @dk43 Kann es sein, dass dein altes System nicht up2date war?
              Zeige mal bitte die Ausgabe von iobroker status

              C:\Users\FujitsuSmartHome>iobroker status
              iobroker is running on this host.
              
              
              Objects type: jsonl
              States  type: jsonl
              

              auf dem raspi siehts genauso aus bis auf

              iobroker@iobroker-pi:~  $  iobroker status
              
              simatec 1 Reply Last reply Reply Quote 0
              • simatec
                simatec Developer Most Active @DK43 last edited by

                @dk43 Und was lief auf deinem alten System? auch die jsonl als Object und File DB?

                DK43 1 Reply Last reply Reply Quote 0
                • DK43
                  DK43 @simatec last edited by DK43

                  @simatec

                  Richtig. Also auf dem Raspi 3b+ mit 2GB RAM

                  so siehts aus wenn ich mit der Wiederherstellung starte
                  9038ad68-c2b4-4215-92c6-59acccc7293f-image.png

                  und bleibt auch so.

                  2023-01-18 10:50:14.294 - info: admin.0 (4576) ==> Connected system.user.admin from ::1
                  2023-01-18 10:50:14.807 - debug: backitup.0 (5032) telegram-instance:
                  2023-01-18 10:50:19.539 - info: admin.0 (4576) <== Disconnect system.user.admin from ::1
                  2023-01-18 10:50:31.094 - info: admin.0 (4576) ==> Connected system.user.admin from ::1
                  2023-01-18 10:50:33.628 - debug: backitup.0 (5032) Backup list be read ...
                  2023-01-18 10:50:39.519 - debug: backitup.0 (5032) set chmod for "C:/Users/FujitsuSmartHome/backups" successfully
                  2023-01-18 10:50:46.897 - info: admin.0 (4576) <== Disconnect system.user.admin from ::1
                  2023-01-18 10:50:56.674 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
                  2023-01-18 10:50:56.678 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2023-01-18 10:50:56.678 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
                  2023-01-18 10:50:56.679 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
                  2023-01-18 10:50:58.799 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
                  2023-01-18 10:51:01.115 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
                  2023-01-18 10:51:01.119 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2023-01-18 10:51:01.119 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
                  2023-01-18 10:51:01.120 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
                  2023-01-18 10:51:03.236 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
                  2023-01-18 10:51:05.766 - info: host.iobroker-pi iobroker.js-controller version 4.0.24 js-controller starting
                  2023-01-18 10:51:05.771 - info: host.iobroker-pi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2023-01-18 10:51:05.771 - info: host.iobroker-pi hostname: iobroker-pi, node: v16.15.1
                  2023-01-18 10:51:05.772 - info: host.iobroker-pi ip addresses: 2003:c9:1706:5500:d92d:a5dd:dbba:a5a4 2003:c9:1706:5500:a1ce:ec6f:1b0a:7bbd fe80::d92d:a5dd:dbba:a5a4 192.168.178.75
                  2023-01-18 10:51:07.903 - error: host.iobroker-pi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "C:\Users\FujitsuSmartHome\iobroker-data\objects.jsonl"!
                  

                  simatec 1 Reply Last reply Reply Quote 0
                  • simatec
                    simatec Developer Most Active @DK43 last edited by

                    @dk43 Dann installiere mal über Github, mache danach zur Sicherheit einen Upload und zeige mir danach mal den Inhalt von C:\iobroker\iobroker-data\backitup

                    DK43 1 Reply Last reply Reply Quote 0
                    • DK43
                      DK43 @simatec last edited by

                      @simatec

                      0553b121-152e-4f14-b38a-ddd7e2c0d612-image.png

                      simatec 1 Reply Last reply Reply Quote 0
                      • simatec
                        simatec Developer Most Active @DK43 last edited by

                        @dk43 Zeige mal den Inhalt von der external.bat und der stopIOB.bat

                        DK43 1 Reply Last reply Reply Quote 0
                        • DK43
                          DK43 @simatec last edited by

                          @simatec

                          external.bat

                          cd "C:\Users\FujitsuSmartHome"
                          call iobroker stop
                          timeout /T 10
                          if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                          redis-server --service-stop
                          )
                          if exist "C:/Users/FujitsuSmartHome/iobroker-data/backitup/.redis.info" (
                          cd "C:\Users\FujitsuSmartHome\node_modules\iobroker.backitup\lib"
                          ) else (
                          cd "C:/Users/FujitsuSmartHome/iobroker-data/backitup"
                          )
                          node restore.js
                          

                          stop.bat

                          start "" "C:\Users\FujitsuSmartHome\iobroker-data\backitup\external.bat"
                          
                          simatec 1 Reply Last reply Reply Quote 0
                          • simatec
                            simatec Developer Most Active @DK43 last edited by

                            @dk43 Mache mein ein Doppelklick auf die stopIOB.bat und poste mal die Ausgabe

                            DK43 1 Reply Last reply Reply Quote 0
                            • DK43
                              DK43 @simatec last edited by

                              @simatec

                              =============================
                              Running Admin shell
                              =============================
                              
                              **************************************
                              Invoking UAC for Privilege Escalation
                              **************************************
                              
                              Waiting for  0 seconds, press a key to continue ...
                              [DEBUG] [iobroker] Start ioBroker Restore ...
                              [ERROR] [iobroker] Stop iobroker first!
                              [DEBUG] [iobroker] ioBroker Restore completed successfully
                              [EXIT] 99
                              
                              C:\Users\FujitsuSmartHome\iobroker-data\backitup>
                              
                              simatec 1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active @DK43 last edited by

                                @dk43 sagte in Test Adapter ioBroker.backitup v2.5.x:

                                Waiting for 0 seconds, press a key to continue ...

                                Hast du bei Aufruf gewartet oder oder den Timeout abgebrochen?
                                Da musst du beim Aufruf warten, damit sich iobroker erstmal beenden kann

                                DK43 1 Reply Last reply Reply Quote 0
                                • DK43
                                  DK43 @simatec last edited by

                                  @simatec

                                  Ich habe es so laufen lassen. Also keine Eingabe

                                  simatec 1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active @DK43 last edited by simatec

                                    @dk43
                                    Ändere mal bitte den Inhalt von der external.bat wie folgt ab und versuche es nochmal

                                    cd "C:\Users\FujitsuSmartHome"
                                    iobroker stop
                                    timeout /T 15
                                    if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                    redis-server --service-stop
                                    )
                                    if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                    cd "C:\Users\FujitsuSmartHome\node_modules\iobroker.backitup\lib"
                                    ) else (
                                    cd "C:\Users\FujitsuSmartHome\iobroker-data\backitup"
                                    )
                                    node restore.js
                                    
                                    DK43 1 Reply Last reply Reply Quote 0
                                    • DK43
                                      DK43 @simatec last edited by

                                      @simatec

                                      hab den inhalt der external.bat geändert.

                                      Daraufhin in den Backitup adapter --> Wiederherstellen --> Sicherungsquelle lokal --> Sicherung abrufen und die Wiederherstellung gestartet.

                                      Es erscheint wieder "localhost refused to connect". ( bei chrome oder einem anderen Browser würde denke ich mal jetzt was anderes stehen).

                                      Habe dann direkt die stopIOB.bat gestartet und folgendes wurde geöffnet.

                                      =============================
                                      Running Admin shell
                                      =============================
                                      
                                      **************************************
                                      Invoking UAC for Privilege Escalation
                                      **************************************
                                      
                                      C:\Users\FujitsuSmartHome>
                                      

                                      Mehr auch nicht.

                                      simatec 1 Reply Last reply Reply Quote 0
                                      • simatec
                                        simatec Developer Most Active @DK43 last edited by

                                        @dk43
                                        dann versuche nochmal bitte mit einem call vorm iobroker stop
                                        Sorry, hab kein Windows zum testen laufen und muss dich mal etwas ausnutzen 😊

                                        cd "C:\Users\FujitsuSmartHome"
                                        call iobroker stop
                                        timeout /T 15
                                        if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                        redis-server --service-stop
                                        )
                                        if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                        cd "C:\Users\FujitsuSmartHome\node_modules\iobroker.backitup\lib"
                                        ) else (
                                        cd "C:\Users\FujitsuSmartHome\iobroker-data\backitup"
                                        )
                                        node restore.js
                                        
                                        DK43 1 Reply Last reply Reply Quote 0
                                        • DK43
                                          DK43 @simatec last edited by

                                          @simatec

                                          Überhaupt kein Ding. Bin dir sehr dankbar dafür dass du dir die Zeit nimmst.

                                          Was kann ich unter call verstehen?

                                          simatec 1 Reply Last reply Reply Quote 0
                                          • simatec
                                            simatec Developer Most Active @DK43 last edited by simatec

                                            @dk43 Du muss nur den Inhalt komplett in die external.bat packen

                                            cd "C:\Users\FujitsuSmartHome"
                                            call iobroker stop
                                            timeout /T 15
                                            if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                            redis-server --service-stop
                                            )
                                            if exist "C:\Users\FujitsuSmartHome\iobroker-data\backitup\.redis.info" (
                                            cd "C:\Users\FujitsuSmartHome\node_modules\iobroker.backitup\lib"
                                            ) else (
                                            cd "C:\Users\FujitsuSmartHome\iobroker-data\backitup"
                                            )
                                            node restore.js
                                            

                                            Da gibt es dann auch diese Zeile

                                            call iobroker stop
                                            
                                            DK43 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            612
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            backitup backitup backup ccu history mysql redis restore restore backup
                                            168
                                            2711
                                            1861777
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo