Restore configuration
Not every problem requires a major solution. Before restoring an entire installation, it's worth looking at smaller steps: often it's enough to restore a single object or the object database from an hour ago.
Four levels
| Level | When | With which |
|---|---|---|
| A single object | A data point was accidentally changed or deleted. | Objects tab, Insert JSON |
| One instance | A configuration has been changed. | Delete and recreate the instance |
| The object database | After a crash, objects are lost or unusable. | The automatic backups in the data directory |
| The entire installation | Hardware change, defective card, failed update. | iobroker restore or BackItUp |
A single object
In the Objects tab, an object can be viewed and edited as JSON. Users who still have the previous version, for example from a backup or the clipboard, can paste it there.
The same thing works on the command line:
iobroker object get <id> --pretty
The output can be saved before any changes are made to an object. This is the cheapest way to protect yourself before tinkering with roles or rights.
One instance
If only the configuration of an instance has been changed and its original state is unknown, deleting and recreating it is usually faster than searching. However, the data points generated by the instance are lost in the process, along with their assignments to rooms and functions.
First, in the Objects tab, view the instance's namespace and note its contents. Recorded values inhistory ,influxdb orsql are not affected by this, they are located outside of it.
The automatic database backups
ioBroker automatically creates copies of the object database, independent of any backup adapter. These copies are located at:
/opt/iobroker/iobroker-data/backup-objects
After a crash with a corrupted database, this is the first place to check. The procedure for this, along with other startup problems, is described under ioBroker is no longer running .
Before any intervention iniobroker-data Stop ioBroker and copy the directory beforehand. A second failed attempt on already modified data is the most common way to create two problems from one.
The entire installation
There are two ways to do this, both of which require an existing backup:
iobroker stop
iobroker restore <Name oder Pfad der Sicherung>
iobroker start
Lists without parametersiobroker restore The existing backups are displayed. A more convenient method is via BackItUp in the Backup tab. Both methods are described under Data Backup .
The complete process for a newly set up system, including Redis and Homematic, is described step by step under Restore .
If there is no fuse
Then you have to rebuild everything. That's annoying, but rarely as bad as feared: the adapter list can be reconstructed from memory, and the devices will reappear during setup. What's lost are the finer details, such as scripts, visualizations, and the assignments to rooms and functions.
Therefore, the first step after rebuilding is always the same: setting up a data backup .