| Previous | Next |
| STATUS_CTLOG_TRACKING_NOT_INITIALIZED | STATUS_CTLOG_VHD_CHANGED_OFFLINE |
STATUS_CTLOG_LOGFILE_SIZE_EXCEEDED_MAXSIZE
The RCT log exhausted its allowed capacity
Hyper-V change tracking persists metadata beside the virtual disk so changes survive service restarts and host failures. This status means the tracking file grew beyond the limit accepted by the implementation. Continued writes cannot be represented reliably in the existing log, so an incremental chain based on it is no longer trustworthy.
A burst of writes, a long interval without establishing a new backup baseline, replication delay, or storage problems that prevent normal log rollover can all contribute. Simply enlarging the VHDX does not repair the tracking history because the limit belongs to the tracking metadata, not to guest free space.
What to inspect
- Correlate the event with backup, replication, checkpoint, and Hyper-V VMMS logs.
- Record the sizes and timestamps of the associated .rct and .mrt files before changing anything.
- Determine whether the product supports resetting RCT and forcing a new full or synthetic-full baseline.
- Check host storage latency and free space so rollover or reference-point creation can complete.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Hyper-V backup approaches
- Microsoft: antivirus exclusions for Hyper-V hosts
- Microsoft: QueryChangesVirtualDisk
Looking for a different code? Search another status or error code.