Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[martin]

Danke.
Habe jetzt versucht das letzte Backup einzuspielen.

Hier aber jetzt Probleme mit denen ich nicht klar komme.

root@iobroker:/# iobroker stop
root@iobroker:/# iobroker restore 0
host.iobroker Using backup file total_2019_11_25-02_00_10_backupiobroker.tar.gz
host.iobroker Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
iobroker controller daemon is not running
host.iobroker OK.
(node:4959) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json'
    at Object.openSync (fs.js:443:3)
    at Object.readFileSync (fs.js:343:35)
    at BackupRestore.restoreAfterStop (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:566:23)
    at Daemon.daemon.on (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:846:22)
    at Daemon.emit (events.js:203:15)
    at Daemon._kill (/opt/iobroker/node_modules/daemonize2/lib/daemonize.js:246:14)
    at Daemon.stop (/opt/iobroker/node_modules/daemonize2/lib/daemonize.js:185:17)
    at tar.extract.err (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:848:20)
(node:4959) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:4959) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
root@iobroker:/#

[FredF]

@martin
Ich bin mir nicht sicher, aber muß ioBroker vorher gestoppt werden?

[martin]

Wenn er läuft kommt die Meldung, dass man ihn stoppen soll.

[FredF]

@martin
Das gemacht

You need to re-login before doing anything else on the console!

[martin]

Ja, ich mache nach jedem Schritt ein Reboot.

root@iobroker:~# iobroker upgrade self
Host    "iobroker"       is up to date.

[FredF]

@martin Dann probier doch mal das fixer script drüber laufen zu lassen.

curl -sL https://iobroker.net/fix.sh | bash -

[martin]

Habe jetzt alles (Debian + Iobroker) neu aufgesetzt.

root@iobroker:~# iobroker restore 0
host.iobroker Using backup file total_2019_11_25-02_00_10_backupiobroker.tar.gz
host.iobroker Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
iobroker controller daemon is not running

Dann das Fixer-Script laufen lassen (erfolgreich) und nochmal restore.

root@iobroker:~# iobroker restore 0
host.iobroker Using backup file total_2019_11_25-02_00_10_backupiobroker.tar.gz
host.iobroker Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
iobroker controller daemon is not running
host.iobroker OK.
root@iobroker:~#

Ich habe von der gecrashten Festplatte den /opt/iobroker Ordner kopieren können.
Kann ich den einfach per FTP drüber bügeln?

[martin]

Habe es jetzt mal mit "backitup" versucht.

======================
Log Backitup Restore:
======================

[DEBUG] [iobroker] Start ioBroker Restore ...
[ERROR] [iobroker] host.iobroker Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
[DEBUG] [iobroker] iobroker controller daemon is not running
[DEBUG] [iobroker] host.iobroker OK.
[DEBUG] [iobroker] ioBroker Restore completed successfully
[EXIT] 9 **** Restore completed successfully!! ****

The log can be closed ...

[martin]

Und nach iobroker upgrade self das hier:

root@iobroker:/opt/iobroker# iobroker restore 0
host.iobroker Using backup file iobroker_2020_02_18-19_14_04_backupiobroker.tar.gz
host.iobroker Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
iobroker controller daemon is not running
host.iobroker OK.
(node:1151) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json'
    at Object.openSync (fs.js:439:3)
    at Object.readFileSync (fs.js:344:35)
    at BackupRestore.restoreAfterStop (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:566:23)
    at Daemon.daemon.on (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:846:22)
    at Daemon.emit (events.js:194:15)
    at Daemon._kill (/opt/iobroker/node_modules/daemonize2/lib/daemonize.js:246:14)
    at Daemon.stop (/opt/iobroker/node_modules/daemonize2/lib/daemonize.js:185:17)
    at tar.extract.err (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:848:20)
(node:1151) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1151) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
root@iobroker:/opt/iobroker#

[martin]

Lösung:

du legst dein Backup in den Ordner /opt/iobroker und führst folgenden Befehl in diesem Ordner aus:

iobroker stop
cd /opt/iobroker
sudo tar -xzvf Backupname.tar.gz -C /opt/iobroker
iobroker start

Jetzt läuft alles zumindest mal wieder und meine Daten sind da.
Werde die nächsten Tage mal ein Standard-Backup erstellen das ich dann hoffentlich in eine saubere Neuinstallation per "Restore" einspielen kann.