Ist mir zu viel.

Die Folge davon bei mir
54GB History Daten wegen gefühlt hunderter Flot Diagramme in Hochauflösung

Ich hatte gedacht, Grafana 10 könnte ich mir ja mal anschauen, wenn ich mein Balkonkraftwerk etwas monitoren will. Aber das ist ja komplett mit Kanonen auf Spatzen geschossen. >400MB nur für buntere Graphen und die Einarbeitungszeit in die beiden Dinger ist es mir dann doch nicht wert.

Mit so'm Grafikgedöns wie Dashboards hab ich mich noch nicht beschäftigt. Dann wird es wohl daran liegen.
Irgendwie wird mir das aber auch alles zu doof. Ist mir zu viel.
Ich beschränke mich dann wohl doch auf echarts.

Schwuppdiwupp, 400 MB mehr frei auf dem Datenträger....

The following packages will be REMOVED:
  grafana influxdb2
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 399 MB disk space will be freed.
Do you want to continue? [Y/n] Y

Aber im log keine Spur der beiden, nicht mal Fehlermeldungen.

Started iobroker ...
[DEBUG] [mount] - noserverino option: true
[DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups"
[DEBUG] [mount] - mount successfully completed
[DEBUG] [mount] - done
[DEBUG] [iobroker] - host.chet 7866 states saved

[DEBUG] [iobroker] - host.chet 9746 objects saved

[DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_06_19-19_40_36_chet_backupiobroker.tar.gz

[DEBUG] [iobroker] - This backup can only be restored with js-controller version up from 4.1

[DEBUG] [iobroker] - done
[DEBUG] [historyDB] - compress from historyDB started ...
[DEBUG] [historyDB] - Backup created: /opt/iobroker/backups/historyDB_2023_06_19-19_40_49_chet_backupiobroker.tar.gz
[DEBUG] [historyDB] - done
[DEBUG] [zigbee] - found zigbee database: zigbee.0
[DEBUG] [zigbee] - done
[DEBUG] [javascripts] - Created javascript_tmp directory: "/opt/iobroker/backups/tmpScripts"
[DEBUG] [javascripts] - found Script: dwd_uwz_nina_warnungen
[DEBUG] [javascripts] - found Script: lautstaerke_bad
[DEBUG] [javascripts] - found Script: lautstaerke_kueche
[DEBUG] [javascripts] - found Script: paketlieferungen
[DEBUG] [javascripts] - found Script: pakettruhe_offen
[DEBUG] [javascripts] - found Script: ps4_waker
[DEBUG] [javascripts] - found Script: sonnenaufgang
[DEBUG] [javascripts] - found Script: sonnenuntergang
[DEBUG] [javascripts] - found Script: speedtest
[DEBUG] [javascripts] - found Script: telefon_klingelt
[DEBUG] [javascripts] - found Script: treppenhaus_licht_ble
[DEBUG] [javascripts] - found Script: treppenhaus_licht_hub
[DEBUG] [javascripts] - found Script: tuerklingel_laeutet
[DEBUG] [javascripts] - found Script: vorhaenge-sonnenschutz
[DEBUG] [javascripts] - found Script: wohnung_verlassen
[DEBUG] [javascripts] - found Script: wohnungstuer_entriegelt
[DEBUG] [javascripts] - found Script: awtrix
[DEBUG] [javascripts] - found Script: zuhause_verlassen
[DEBUG] [javascripts] - Try deleting the Javascript tmp directory: "/opt/iobroker/backups/tmpScripts"
[DEBUG] [javascripts] - Javascript tmp directory "/opt/iobroker/backups/tmpScripts" successfully deleted
[DEBUG] [javascripts] - Backup created: /opt/iobroker/backups/javascripts_2023_06_19-19_40_50_chet_backupiobroker.tar.gz
[DEBUG] [javascripts] - done
[DEBUG] [cifs] - used copy path: /fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet
[DEBUG] [cifs] - done
[DEBUG] [googledrive] - Google Drive: Copy iobroker_2023_06_19-19_40_36_chet_backupiobroker.tar.gz...
[DEBUG] [googledrive] - Google Drive: Copy historyDB_2023_06_19-19_40_49_chet_backupiobroker.tar.gz...
[DEBUG] [googledrive] - Google Drive: Copy zigbee.0_2023_06_19-19_40_50_chet_backupiobroker.tar.gz...
[DEBUG] [googledrive] - Google Drive: Copy javascripts_2023_06_19-19_40_50_chet_backupiobroker.tar.gz...
[DEBUG] [googledrive] - done
[DEBUG] [clean] - No older backup files are deleted, because this backup was started manually
[DEBUG] [clean] - done
[DEBUG] [whatsapp] - done
[DEBUG] [historyHTML] - new history html values created
[DEBUG] [historyHTML] - done
[DEBUG] [historyJSON] - new history json values created
[DEBUG] [historyJSON] - done
[DEBUG] [umount] - mount activ, umount is started ...
[DEBUG] [umount] - umount successfully completed
[DEBUG] [umount] - done
[EXIT] 0

Was mach ich denn wo falsch?

danke für den Hinweis. Das ist die entscheidende Stelle in der Anleitung:

ioBroker.backitup löscht/ergänzt/überschreibt etc. aktuell kein Bucket mit identischem Namen beim Restore.

Musst du hier mal nachlesen:

https://github.com/simatec/ioBroker.backitup/wiki/Diverse-Anleitungen-für-ioBroker.backitup

danke werde es mal testen. Habe das Feld leer gelassen und es ist laut Backupit durch gelaufen.

Started iobroker ...
[DEBUG] [iobroker] - host.iobtest 2359 states saved

[DEBUG] [iobroker] - host.iobtest 2313 objects saved

[DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_06_18-21_06_13_backupiobroker.tar.gz

[DEBUG] [iobroker] - done
[DEBUG] [influxDB] - InfluxDB-Backup started ...
[DEBUG] [influxDB] - Start InfluxDB Backup ...
[DEBUG] [influxDB] - InfluxDB Backup tmp directory created 
[DEBUG] [influxDB] - Packed 171MB so far...
[DEBUG] [influxDB] - Packed 326MB so far...
[DEBUG] [influxDB] - Backup created: /opt/iobroker/backups/influxDB_2023_06_18-21_06_16_backupiobroker.tar.gz
[DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory: "/opt/iobroker/backups/influxDB_2023_06_18-21_06_16_backupiobroker"
[DEBUG] [influxDB] - InfluxDB tmp directory "/opt/iobroker/backups/influxDB_2023_06_18-21_06_16_backupiobroker" successfully deleted
[DEBUG] [influxDB] - InfluxDB-Backup for is finish
[DEBUG] [influxDB] - done
[DEBUG] [clean] - No older backup files are deleted, because this backup was started manually
[DEBUG] [clean] - done
[DEBUG] [historyHTML] - new history html values created
[DEBUG] [historyHTML] - done
[DEBUG] [historyJSON] - new history json values created
[DEBUG] [historyJSON] - done
[EXIT] 0

der Restore lief nicht durch, wollte die aktuelle DB einfach mal mit dem Backup überschreiben.

Started restore ...
[DEBUG] [influxDB] - Created tmp directory
[DEBUG] [influxDB] - Start infuxDB Restore ...
[DEBUG] [influxDB] - influxdb.0 is stopped
[ERROR] [influxDB] - 2023/06/18 21:11:39 INFO: Restoring bucket "ea25e11851af6754" as "ioBrokerBucket"
Error: failed to restore bucket "ioBrokerBucket": 422 Unprocessable Entity: bucket with name ioBrokerBucket already exists

[DEBUG] [influxDB] - Try deleting the InfluxDB tmp directory
[DEBUG] [influxDB] - InfluxDB tmp directory was successfully deleted
[DEBUG] [influxDB] - infuxDB Restore completed successfully
[EXIT] influxDB restore done
[DEBUG] [influxDB] - influxdb.0 started

muss für den Restore influx gestoppt werden?

Bei Verwendung von influxdb2 keiner.
Bzw. könnte dann da wohl /usr/bin/influx eingetragen werden.

welcher kommt den da rein?

Ich versuche gerade ein Backup für influxdb2 anzulegen. Aber irgendwas klemmt hier.

Moin,

mir ist nicht bekannt, dass das influxd ist, ich mache von Remote CLI immer mit influx.

 18:07:05  ✘  dp20eic@influxdb-v2-prod  ~ 
$ influx --help 
NAME:
   influx - Influx Client

USAGE:
   influx [command]

HINT: If you are looking for the InfluxQL shell from 1.x, run "influx v1 shell"

COMMANDS:
   version              Print the influx CLI version
   write                Write points to InfluxDB
   bucket               Bucket management commands
   completion           Generates completion scripts
   query                Execute a Flux query
   config               Config management commands
   org, organization    Organization management commands
   delete               Delete points from InfluxDB
   user                 User management commands
   task                 Task management commands
   telegrafs            List Telegraf configuration(s). Subcommands manage Telegraf configurations.
   dashboards           List Dashboard(s).
   export               Export existing resources as a template
   secret               Secret management commands
   v1                   InfluxDB v1 management commands
   auth, authorization  Authorization management commands
   apply                Apply a template to manage resources
   stacks               List stack(s) and associated templates. Subcommands manage stacks.
   template             Summarize the provided template
   bucket-schema        Bucket schema management commands
   scripts              Scripts management commands
   ping                 Check the InfluxDB /health endpoint
   setup                Setup instance with initial user, org, bucket
   backup               Backup database
   restore              Restores a backup directory to InfluxDB
   remote               Remote connection management commands
   replication          Replication stream management commands
   server-config        Display server config
   help, h              Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --help, -h  show help

VG
Bernd