-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update backup integration docs to reflect current SW #36684
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,25 +11,25 @@ ha_codeowners: | |
ha_iot_class: Calculated | ||
ha_integration_type: system | ||
related: | ||
- docs: /installation/#advanced-installation-methods | ||
title: Home Assistant installation methods | ||
- docs: /common-tasks/general/#backups | ||
title: Backups | ||
- docs: /getting-started/onboarding/ | ||
title: Recover from backup during onboarding | ||
- docs: /docs/configuration/ | ||
title: Configuration file | ||
- docs: /common-tasks/os/#restoring-a-backup | ||
title: Home Assistant Operating System- Restoring a backup | ||
- docs: /more-info/backup-emergency-kit/ | ||
title: backup emergency kit | ||
--- | ||
|
||
The **Backup** {% term integration %} is used for {% term "Home Assistant Core" %} and {% term "Home Assistant Container" %} installations to create and download backups. This backup file can be used if you migrate to {% term "Home Assistant Operating System" %}. | ||
The **Backup** {% term integration %} is used by all [installation types](/installation/#advanced-installation-methods) to create and restore backups. | ||
|
||
Note: If you use {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %} installation, this page is not for you. Instead, refer to the documentation on using the [built-in back up](/common-tasks/general/#backups). | ||
To learn how to create and restore a backup, refer to the backup section under [common tasks](/common-tasks/general/#backups). | ||
|
||
## Actions | ||
|
||
The **Backup** integration exposes an action that can be used to automate the backup | ||
process. | ||
|
||
However, it is no longer needed to create your own automation. Follow these steps to [set up an automatic backup from the UI](/common-tasks/general/#setting-up-an-automatic-backup-process). | ||
|
||
### Action {% my developer_call_service service="backup.create" %} | ||
|
||
The {% my developer_call_service service="backup.create" %} action can be used | ||
|
@@ -61,20 +61,4 @@ automation: | |
## Restoring a backup | ||
Backups created via the **Backup** integration are in a subdirectory `backups`, located in your [configuration directory](/docs/configuration/#editing-configurationyaml). | ||
The {% term "Home Assistant Container" %} installation typically mounts this directory via `docker-compose.yml` or `docker run` to a directory of your choice. | ||
|
||
The steps on recovering from a backup depend on the installation type and use case. Follow one of these steps: | ||
|
||
1. If you use {% term "Home Assistant Operating System" %} or {% term "Home Assistant Supervised" %}: | ||
- Follow the steps described in [Restoring a backup](/common-tasks/os/#restoring-a-backup). | ||
2. If you use a {% term "Home Assistant Core" %} or {% term "Home Assistant Container" %} installation: | ||
- A Home Assistant backup is just a tar file of the [configuration directory](/docs/configuration/#editing-configurationyaml), plus some metadata. | ||
- To manually restore a backup, use the following command: | ||
|
||
```shell | ||
tar -xOf <backup_tar_file> "./homeassistant.tar.gz" | tar --strip-components=1 -zxf - -C <restore_directory> | ||
``` | ||
|
||
3. If you migrate from a {% term "Home Assistant Core" %} or {% term "Home Assistant Container" %} installation to {% term "Home Assistant Operating System" %}: | ||
- You can use these backup files during [onboarding](/getting-started/onboarding/) to recover your installation from backup. | ||
To restore a backup, follow the steps described in [Restoring a backup](/common-tasks/os/#restoring-a-backup). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion Consider using a more general restoration guide link The current link points to OS-specific restoration documentation ( Consider updating to point to a more general restoration guide: -To restore a backup, follow the steps described in [Restoring a backup](/common-tasks/os/#restoring-a-backup).
+To restore a backup, follow the steps described in [Restoring a backup](/common-tasks/general/#restoring-a-backup).
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
The link to automatic backup setup is incorrect
The documentation refers to
/common-tasks/general/#setting-up-an-automatic-backup-process
, but the actual content is included fromsource/_includes/common-tasks/backups.md
and the correct anchor is#setting-up-an-automatic-backup-process
. The link should be updated to point to the correct location.source/_integrations/backup.markdown
to:/common-tasks/backups/#setting-up-an-automatic-backup-process
🔗 Analysis chain
Excellent guidance on preferred backup method!
The update appropriately directs users to the UI-based setup while maintaining YAML documentation for advanced users.
Let's verify the UI setup link is valid:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 67
Script:
Length of output: 489
Script:
Length of output: 171
Script:
Length of output: 176
Script:
Length of output: 14263