Skip to content

Commit 383837e

Browse files
vnikolineak13
andauthored
Update articles/operator-nexus/troubleshoot-reboot-reimage-replace.md
Co-authored-by: Andrew Karandjeff <[email protected]>
1 parent 4cefab1 commit 383837e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-nexus/troubleshoot-reboot-reimage-replace.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Servers contain many physical components that can fail over time. It's important
177177
A hardware validation process is invoked to ensure the integrity of the physical host in advance of deploying the OS image. Like the reimage action, the Tenant data isn't modified during replacement.
178178

179179
> [!IMPORTANT]
180-
> When run with default options, the RAID controller is reset during BMM replace, wiping all data from the server's virtual disks. Baseboard Management Controller (BMC) virtual disk alerts triggered during BMM replace can be ignored unless there are other physical disk and/or RAID controllers alerts. Starting with the 2025-07-01 GA API version, use `replace` with `storage-policy="Preserve"` to retain virtual disk data.
180+
> When run with default options, the RAID controller is reset during BMM replace, wiping all data from the server's virtual disks. Baseboard Management Controller (BMC) virtual disk alerts triggered during BMM replace can be ignored unless there are other physical disk and/or RAID controllers alerts. Starting with the 2025-07-01 preview version of the NetworkCloud API, and generally available with the 2025-09-01 GA version, use `replace` with `storage-policy="Preserve"` to retain virtual disk data.
181181
182182
### Replace workflow
183183

0 commit comments

Comments
 (0)