Skip to content

Commit 96a63b4

Browse files
authored
Clean up syntax (docker#8881)
1 parent 57bffe0 commit 96a63b4

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

ee/dtr/admin/configure/external-storage/storage-backend-migration.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -26,27 +26,26 @@ Docker recommends the following steps for your storage backend and metadata migr
2626

2727
5. With DTR restored from your backup and your storage data migrated to your new backend, garbage collect any dangling blobs using the following API request:
2828

29-
```bash
30-
curl -u <username>:$TOKEN -X POST "https://<dtr-url>/api/v0/jobs" -H "accept: application/json" -H "content-type: application/json" -d "{ \"action": \"onlinegc_blobs\" }"
31-
```
32-
On success, you should get a `202 Accepted` response with a job `id` and other related details.
33-
34-
This ensures any blobs which are not referenced in your previously created backup get destroyed.
29+
```bash
30+
curl -u <username>:$TOKEN -X POST "https://<dtr-url>/api/v0/jobs" -H "accept: application/json" -H "content-type: application/json" -d "{ \"action": \"onlinegc_blobs\" }"
31+
```
32+
33+
On success, you should get a `202 Accepted` response with a job `id` and other related details. This ensures any blobs which are not referenced in your previously created backup get destroyed.
3534
3635
### Alternative option for data migration
3736
38-
- If you have a long maintenance window, you can skip some steps from above and do the following:
37+
If you have a long maintenance window, you can skip some steps from above and do the following:
3938
40-
1. Put DTR in "read-only" mode using the following API request:
39+
1. Put DTR in "read-only" mode using the following API request:
4140
42-
```bash
43-
curl -u <username>:$TOKEN -X POST "https://<dtr-url>/api/v0/meta/settings" -H "accept: application/json" -H "content-type: application/json" -d "{ \"readOnlyRegistry\": true }"
44-
```
45-
On success, you should get a `202 Accepted` response.
41+
```bash
42+
curl -u <username>:$TOKEN -X POST "https://<dtr-url>/api/v0/meta/settings" -H "accept: application/json" -H "content-type: application/json" -d "{ \"readOnlyRegistry\": true }"
43+
```
44+
On success, you should get a `202 Accepted` response.
4645
47-
2. Migrate the contents of your current storage backend to the new one you are switching to. For example, upload your current storage data to your new NFS server.
46+
2. Migrate the contents of your current storage backend to the new one you are switching to. For example, upload your current storage data to your new NFS server.
4847
49-
3. [Reconfigure DTR](/reference/dtr/2.6/cli/reconfigure) while specifying the `--storage-migrated` flag to preserve your existing tags.
48+
3. [Reconfigure DTR](/reference/dtr/2.6/cli/reconfigure) while specifying the `--storage-migrated` flag to preserve your existing tags.
5049
5150
5251
## DTR 2.6.0-2.6.4 and DTR 2.5 (with experimental garbage collection)

0 commit comments

Comments
 (0)