ioBroker.backitup
ioBroker.backitup copied to clipboard
simatec
Backupfiles from Dropbox are not shown for restore
My BackItUp adapter is configured to upload backup files into my Dropbox - this works fine. It's also configured to keep the last 5 Backups.
But if I want to select a backup for restore I can't see the latest backups, just 5 old ones. At the moment there are 9 backup files instead of 5.
iobroker_2022_09_28-02_00_13_backupiobroker.tar.gz iobroker_2022_10_01-02_00_10_backupiobroker.tar.gz iobroker_2022_10_04-02_00_10_backupiobroker.tar.gz iobroker_2022_10_07-02_00_10_backupiobroker.tar.gz iobroker_2022_10_10-02_00_10_backupiobroker.tar.gz iobroker_2022_10_13-02_00_10_backupiobroker.tar.gz iobroker_2022_10_17-18_00_12_backupiobroker.tar.gz iobroker_2022_10_19-02_00_10_backupiobroker.tar.gz iobroker_2022_10_19-07_10_45_backupiobroker.tar.gz
In debug mode there are following messages in log file:
2022-10-19 16:34:29.597 - info: backitup.0 (463496) Loglevel changed from "warn" to "debug"
2022-10-19 16:34:46.384 - debug: backitup.0 (463496) telegram-instance: telegram.0
2022-10-19 16:34:51.339 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:34:51.340 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:34:51.341 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.545 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.545 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.546 - debug: backitup.0 (463496) Backup list cannot be read ...
I need a few more details. The error is not reproducible for me.
On my test systems, all backups can be read from Dropbox.
Sorry, I don't have more information due to poor debug logging of BackItUp.
But I noticed that a newer backup gets displayed when I delete an older one.
Maybe the problem gets solved if all available backups are displayed, regardless howmany the adapter is configured to keep.
What bad debug logging?
Do not understand the statement. I need more info, screenshots etc.
All my test systems show all backups from dropbox and this is the first time I've heard this message from you.
What names do your backups have and what else is in the directories?
Please more info
poor != bad (just to say) Sorry if this was a misunderstanding.
Okay, even if I don't really have more information I will try to explain a little bit more. I got that issue described in the first post and was able to solve this by deleting all backups and start from beginning.
But I'm able to reproduce it (it's a little bit different from above).
Now at this moment I have a Dropbox folder which contains only backups made with BackItUp adapter (22 files).
This is a screenshot from Dropbox web ui:
You can count 7 ioBroker backups.
Next screenshot is from BackItUp:
You can count 3 ioBroker backups.
This is what BackItUp writes into log:
What else can I provide to help?
Ich kann deinen Fehler leider nicht nachstellen.
Prüfe mal, ob eventuell Dateien in der dropbox beschädigt sind. Was auch noch zu empfehlen ist, dass man Unterordner für die Backups anlegt. Also sprich, iobroker und Homematic trennen.
Dies kannst du in Backitup einstellen
Another option would also be to renew your token. You can do this in the Backitup menu.
ich hänge mich mal mit dran bei mir besteht das gleiche Problem.
kann es damit zusammenhängen das ioBroker im Docker läuft?
Backups erstellen und in der DB speichern funktioniertaber super.
wenn ich auf Sicherungen abrufen klicke passiert gar nix
Instanz steht auf Debug aber im log wird nach dem start nur das angezeigt:
einstellungen im Drobox Tab:
Token ist neu von heute
Ich kann das Problem nicht nachstellen. Habe auch auf der Testumgebung einen neuen Token geholt und ich kann im Config Menü und über den Backitup Tab die Backups holen. Was mir aufgefallen ist, bei dir stehen die Default Verzeichnisse in der Config. Eigentlich sind das Platzhalter. Stimmen die denn mit deinen Dropbox-Pfaden überein?
Verzeichnisse passen
Kann es denn mit der Installation in Docker zu tun haben?
Zeige mal im Pfad /opt/iobroker/node_modules/iobroker.backitup die Ausgabe von folgenden Befehl
npm ls
`root@ioBrokerTWS:/opt/iobroker# cd node_modules/iobroker.backitup root@ioBrokerTWS:/opt/iobroker/node_modules/iobroker.backitup# npm ls [email protected] (github:simatec/ioBroker.backitup#67543045504cee442132f7d0b7cab5c8685fd307) /opt/iobroker/node_modules/iobroker.backitup ├── UNMET DEPENDENCY @googleapis/drive@^4.0.0 ├─┬ @iobroker/[email protected] │ └─┬ @types/[email protected] │ └── UNMET DEPENDENCY @types/node@* ├─┬ [email protected] │ ├── [email protected] │ ├─┬ [email protected] │ │ ├── UNMET DEPENDENCY asynckit@^0.4.0 │ │ ├── UNMET DEPENDENCY combined-stream@^1.0.8 │ │ └── UNMET DEPENDENCY mime-types@^2.1.12 │ └── UNMET DEPENDENCY proxy-from-env@^1.1.0 ├── UNMET DEPENDENCY dropbox-v2-api@^2.5.6 ├─┬ [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ └── [email protected] │ │ └── [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├─┬ [email protected] │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── UNMET DEPENDENCY content-type@~1.0.4 │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── [email protected] deduped │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── [email protected] deduped │ │ ├── UNMET DEPENDENCY [email protected] │ │ ├── UNMET DEPENDENCY type-is@~1.6.18 │ │ └── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY content-type@~1.0.4 │ ├── [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── [email protected] │ ├── UNMET DEPENDENCY encodeurl@~1.0.2 │ ├── UNMET DEPENDENCY escape-html@~1.0.3 │ ├── UNMET DEPENDENCY etag@~1.8.1 │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY methods@~1.1.2 │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY parseurl@~1.3.3 │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY proxy-addr@~2.0.7 │ ├─┬ [email protected] │ │ └── UNMET DEPENDENCY side-channel@^1.0.4 │ ├── UNMET DEPENDENCY range-parser@~1.2.1 │ ├── [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY [email protected] │ ├── UNMET DEPENDENCY type-is@~1.6.18 │ ├── UNMET DEPENDENCY [email protected] │ └── UNMET DEPENDENCY vary@~1.1.2 ├─┬ [email protected] │ ├── UNMET DEPENDENCY graceful-fs@^4.2.0 │ ├── UNMET DEPENDENCY jsonfile@^6.0.1 │ └── UNMET DEPENDENCY universalify@^2.0.0 ├── UNMET DEPENDENCY ftp@^0.3.10 ├── UNMET DEPENDENCY google-auth-library@^8.6.0 ├── UNMET DEPENDENCY node-schedule@^2.1.0 ├── UNMET DEPENDENCY node-wol@^0.1.1 ├── UNMET DEPENDENCY request@^2.88.2 ├── UNMET DEPENDENCY tar-fs@^2.1.1 └── UNMET DEPENDENCY webdav@^4.11.0
npm ERR! missing: @googleapis/drive@^4.0.0, required by [email protected] npm ERR! missing: dropbox-v2-api@^2.5.6, required by [email protected] npm ERR! missing: ftp@^0.3.10, required by [email protected] npm ERR! missing: google-auth-library@^8.6.0, required by [email protected] npm ERR! missing: node-schedule@^2.1.0, required by [email protected] npm ERR! missing: node-wol@^0.1.1, required by [email protected] npm ERR! missing: request@^2.88.2, required by [email protected] npm ERR! missing: tar-fs@^2.1.1, required by [email protected] npm ERR! missing: webdav@^4.11.0, required by [email protected] npm ERR! missing: @types/node@*, required by @types/[email protected] npm ERR! missing: proxy-from-env@^1.1.0, required by [email protected] npm ERR! missing: asynckit@^0.4.0, required by [email protected] npm ERR! missing: combined-stream@^1.0.8, required by [email protected] npm ERR! missing: mime-types@^2.1.12, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: content-type@~1.0.4, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: encodeurl@~1.0.2, required by [email protected] npm ERR! missing: escape-html@~1.0.3, required by [email protected] npm ERR! missing: etag@~1.8.1, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: methods@~1.1.2, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: parseurl@~1.3.3, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: proxy-addr@~2.0.7, required by [email protected] npm ERR! missing: range-parser@~1.2.1, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: type-is@~1.6.18, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: vary@~1.1.2, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: content-type@~1.0.4, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: type-is@~1.6.18, required by [email protected] npm ERR! missing: [email protected], required by [email protected] npm ERR! missing: side-channel@^1.0.4, required by [email protected] npm ERR! missing: graceful-fs@^4.2.0, required by [email protected] npm ERR! missing: jsonfile@^6.0.1, required by [email protected] npm ERR! missing: universalify@^2.0.0, required by [email protected] root@ioBrokerTWS:/opt/iobroker/node_modules/iobroker.backitup# ^C`
Kannst du die Backups Lokal abrufen? Prüfe dort mal bitte die rechte der Backups, die unter /opt/iobroker/backups liegen
ls -lah /opt/iobroker/backups
Lass mal den iob fix laufen und beobachte dann mal die nächsten Backups.
Werden denn in Backitup die lokalen Backups gelistet?
wenn ich auf Sicherungen Abrufen clicke
kommt das fenster und es passsiert nix auch nach 30min nicht
bei lokal das selbe spiel
Ich gehe davon aus, dass deine Rechte nicht korrekt sind. Was hast du denn für eine Container Version laufen? Da schonmal ein Update des Containers gemacht?
Sorry hatte bis jetzt keine Zeit zum nachschauen:
Update vom Container hab ich noch nicht gemacht.
Hast du den iobroker fix laufen lassen? Passen deine Pfade alle?
prüfe die nochmal und speichere die Settings von Backitup.
Unbedingt den Fixer laufen lassen. Update von Backitup durchführen.
Alle Settings nochmal prüfen.
Wenn alles nicht hilft, sichere die Settings von Backitup, entferne ihn in den Instanzen und im Tab Adapter.
Installiere ihn nach einem Neustart des Containers neu und spiele die Settings zurück.