You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/current/v25.3/take-and-restore-locality-aware-backups.md
-41Lines changed: 0 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,47 +191,6 @@ To restore from a specific backup, use [`RESTORE FROM {subdirectory} IN ...`]({%
191
191
When [restoring from an incremental locality-aware backup]({% link {{ page.version.version }}/take-and-restore-locality-aware-backups.md %}#restore-from-an-incremental-locality-aware-backup), you need to include **every** locality ever used, even if it was only used once.
192
192
{{site.data.alerts.end}}
193
193
194
-
## Manually restore zone configurations from a locality-aware backup
195
-
196
-
During a [locality-aware restore](#restore-from-a-locality-aware-backup), some data may be temporarily located on another node before it is eventually relocated to the appropriate node. To avoid this, you need to manually restore [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) first:
197
-
198
-
Once the locality-aware restore has started, [pause the restore]({% link {{ page.version.version }}/pause-job.md %}):
199
-
200
-
{% include_cached copy-clipboard.html %}
201
-
~~~sql
202
-
PAUSE JOB 27536791415282;
203
-
~~~
204
-
205
-
The `system.zones` table stores your cluster's [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}), which will prevent the data from rebalancing. To restore them, you must restore the `system.zones` table into a new database because you cannot drop the existing `system.zones` table:
0 commit comments