Impaired Cloud Extensions
A Cloud Extension with an Impaired status functions differently depending on whether only one or both of its Cloud Edge nodes have failed:
- If only one of the Cloud Edge nodes fails, most operations remain available, but write throughput decreases.
- If both Cloud Edge nodes fail, VMs relying on that Cloud Extension will no
longer have access to storage and will fail.
Additionally, the Cloud Extension can no longer run
new VMs in the cloud. In this case, you can either:
- Force running VMs to move back to their source environment.
- If the VM is fully cached, run the Prepare to Detach operation.
- Stop VMs.
A Cloud Extension can also be Impaired if the Migrate for Compute Engine Backend or the Migrate for Compute Engine Manager fail. In this case, a limited set of actions are available.
Cloud Extensions can be impaired due to:
- Incomplete deployment or initial failed health checks. This is most likely due to improperly configured networks or permissions. After fixing the underlying causes, repair the Cloud Extension. Repairing the cloud extension attempts to recreate the missing components, run relevant health checks, or both. If the repair succeeds, the Cloud Extension is Active.
- A VM health issue. Stopping and starting the Cloud Extension might fix this issue after affected VMs restart on a healthy host.
Avoiding data loss
When one Cloud Edge node fails, the Cloud Extension enters a fail-safe mode. To avoid data loss, all data are written to the Cloud Extension's object store on Cloud Storage, which reduces the Cloud Extension performance.
For more information, see Monitoring Cloud Extensions.