Topic
This article lists the NinjaOne Device Backup Verification codes, their meanings, and potential causes.
Environment
NinjaOne Device Backup
Description
NinjaOne Device Backup Verification will display a code in the results for any unsuccessful verification. Refer to the following chart for descriptions of each code and its potential causes.
| Code | Status | Cause |
|---|---|---|
| 1 | Generic failure | NinjaOne cannot determine the cause of the verification failure. |
| 2 | Microsoft Windows update detected | A Microsoft Windows update was underway, so verification could not be completed. |
| 3 | Chkdsk on startup detected | Boot verify will not run when a chkdsk is in progress |
| 4 | Bad VM layout - Ninja Developer assistance needed | Manually initiated backup jobs may cause this status. Boot verification is designed to run on scheduled jobs. |
| 5 | Timeout | The virtualization ran for 60 minutes without displaying the login screen. |
| 6 | Hypervisor Exited | The hypervisor exited for an unknown reason. No disk activity on the virtual machine may result in this code. |
| 7 | Reset loop detected | A reboot loop on the machine was detected. |
| 8 | Job failed | The backup job we attempted to verify was in a failed state. |
| 9 | Disk space | There was not enough disk space on the hypervisor to virtualize the job. |
Additional Resources
For more information about boot verification, refer to: NinjaOne Device Backup: Boot Verification.