| Previous | Next |
| STATUS_CTLOG_LOGFILE_SIZE_EXCEEDED_MAXSIZE | STATUS_CTLOG_INVALID_TRACKING_STATE |
STATUS_CTLOG_VHD_CHANGED_OFFLINE
An offline disk operation invalidated the tracked history
RCT assumes that every relevant write is observed relative to a known virtual-disk identity and baseline. Compaction, expansion, offline mounting, direct editing, conversion, or another out-of-band operation can change the VHDX without updating the active tracking log. The previous change identifiers can then no longer describe the disk accurately.
This is a consistency failure, not merely a notification that the disk file timestamp changed. Reusing the old identifier could omit blocks from an incremental backup. The safe recovery is to establish a fresh baseline after the offline operation and treat older tracking data as stale.
What to inspect
- Identify every operation performed while the VM or tracking stack was offline, including compact, resize, merge, mount, and conversion.
- Compare the VHDX identity, parent chain, file size, and modification time with the last successful backup record.
- Discard or retire the old tracking identifier according to the backup product workflow.
- Run a full consistency-preserving backup before resuming incremental change queries.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: QueryChangesVirtualDisk
- Microsoft: GET_VIRTUAL_DISK_INFO change-tracking state
- Microsoft: Hyper-V backup approaches
Looking for a different code? Search another status or error code.