| Previous | Next |
| STATUS_VHD_METADATA_FULL | STATUS_VHD_CHANGE_TRACKING_DISABLED |
STATUS_VHD_INVALID_CHANGE_TRACKING_ID
STATUS_VHD_INVALID_CHANGE_TRACKING_ID concerns resilient change tracking (RCT) used to ask a virtual disk for changed ranges relative to a tracking baseline. The supplied identifier does not name a valid baseline for that request.
It differs from STATUS_VHD_CHANGE_TRACKING_DISABLED, where tracking is not enabled at all, and from STATUS_VHD_MISSING_CHANGE_TRACKING_INFORMATION, where a tracking context may be recognized but required delta information is unavailable. The identifier is not a guest filesystem snapshot label.
Correlate the request with its baseline
- Record the VHD path, tracking identifier, backup or replication job instance and the exact API call that failed.
- Confirm that the identifier was produced for the same virtual disk and the intended lifecycle of that disk.
- Do not invent a replacement identifier; restarting incremental processing may require a supported full-baseline operation.
References
Looking for a different code? Search another status or error code.