Multiple Services Fail to Start After vSZ Reboot

Summary

The customer noticed that many services were in an offline state and not functioning properly after starting the vSZ.

Question

vSZ services are not starting properly and repeated reboot attempts have not resolved the issue. What could be the cause and what are the recommended recovery steps?

Customer Environment

vSZ-H R6.1.2p5 KVM

Root Cause

Upon investigation, it was confirmed that this vSZ instance was newly built by restoring a KVM hypervisor backup taken from another physical server. Ruckus does not recommend or support migrating or rebuilding vSZ systems using hypervisor?level backup or snapshot mechanisms. As a result, this unsupported restoration method caused service initialization failures, leaving multiple vSZ services in an offline state.

Resolution

To resolve the issue, the affected vSZ instance must be rebuilt using a supported method.
A new vSZ instance should be deployed on the target physical server and the system should be restored using the vSZ Cluster Backup and Restore feature.
Migration or recovery using hypervisor?level backup mechanisms, such as KVM backups or snapshots, must not be used as this method is not supported by Ruckus and can cause service startup failures.
After restoring the cluster backup on the newly deployed vSZ, verify that all services are running properly and confirm proper system operation.

Article Number:
000015272

Updated:
April 23, 2026 06:49 PM (29 days ago)

Tags:

Votes:
0

This article is:
helpful
not helpful