Troubleshooting guide

Use the message shown on the page and the job details to identify where the failure occurred before changing the configuration. Changing several settings at once makes the cause harder to isolate.

Recommended sequence

1. Record the product version, time, page, and complete error message.
2. Open the related job or resource and identify the failed step and affected scope.
3. Confirm that the relevant Agent, Proxy, or Data Gateway is online.
4. Validate the backup source, target storage, or model-service connection separately.
5. Change one condition at a time, then repeat the original action.

Choose a scenario

Account accessConsole or sign-in unavailableCheck the console address, sign-in method, account state, and browser access.Installation and connectivityInstallation failed or a node is offlineCheck system prerequisites, the installation command, component state, and control-plane connectivity.Data protectionBackup, repository, or restore failedCheck folder permissions, object storage, NAS, Proxy storage access, snapshots, and the restore destination.InsightsData Gateway or AI Copilot unavailableCheck models, snapshot scope, the Public or Private Data Gateway, and data-preparation status.

Before opening an issue

After confirming that the problem is reproducible, search GitHub Issues for an existing report. When opening a new issue, include the product version, operating system, steps to reproduce the problem, and the complete error message. Attach only the relevant, sanitized logs needed for investigation.