Skip to content

Update migrating-storage-node.md #78

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.

Sign up for GitHub

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

Merged
noctarius merged 3 commits into from
Jul 11, 2025
Merged

Update migrating-storage-node.md #78

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8e3db73
Update migrating-storage-node.md
schmidt-scaled Jul 11, 2025
16638ab
Update migrating-storage-node.md
noctarius Jul 11, 2025
d27a57d
Merge branch 'main' into schmidt-scaled-patch-2
noctarius Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions docs/maintenance-operations/migrating-storage-node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,9 @@ that doesn't require explicit maintenance windows or storage downtime.

## Storage Node Migration

Migrating a storage node is a three-step process. First, the new storage node will be pre-deployed, then the old node
will be restarted with the new node address, and finally, the new storage node will become the primary storage node.
Migrating a storage node is a three-step process. First, the new storage node will be pre-deployed, after that the old
storage node must be shutdown properly. It will be restarted (migrated) with the new storage node's storage node api address,
and finally, the new storage node will become the primary storage node.

!!! warning
Between each process step, it is required to wait for storage node migration tasks to complete. Otherwise, there
Expand All @@ -31,6 +32,15 @@ If the command finishes successfully, resume from the next section of this page.

### Restart Old Storage Node

!!! warning
Before migrating the storage node on a storage host, the ols storage node must be put in offline state.

If the storage node is not yet offline, it can be forced into offline state using the following command.

```bash title="Shutdown storage node on old instance"
{{ cliname }} storage-node shutdown <NODE_ID> --force
```

To start the migration process of logical volumes, the old storage node needs to be restarted with the new storage
node's API address.

Expand Down