Why are my RollBack Rx snapshots shown in red/orange color
applies to RollBack Rx Pro and Server Edition v11 and later
Understanding Snapshot Indicators: What "Red Snapshots" Mean
When RollBack Rx Pro creates a snapshot, it captures the current state of your hard drive sector-by-sector. To ensure that this snapshot is as accurate as possible, the software must account for data currently being processed in your system's memory.
The Role of VSS in Snapshot Creation
Windows frequently stores active data in the System RAM or the Pagefile for high-speed access. This data has not yet been "committed" or written to the physical hard disk.
To maintain data integrity, RollBack Rx Pro communicates with the Windows Volume Shadow Copy Service (VSS) before finalizing a snapshot. This process "flushes" the memory cache, forcing any pending data to be written onto the hard drive so it can be included in the snapshot.
Why is my snapshot red?
A snapshot appears in red within the snapshot console if the VSS flush process was unsuccessful.
-
The Result: RollBack Rx Pro still completes the snapshot to ensure you have a recovery point, but it flags it as "red" to indicate the system may not have been in a completely consistent state at the moment of capture.
-
The Impact: In most cases, these are still fully functional, bootable snapshots. An occasional red snapshot is generally not a cause for alarm.
Troubleshooting Persistent Red Snapshots
If your system consistently generates red snapshots, it indicates that VSS is failing to communicate with the hardware or software properly.
Common Causes:
-
Software Conflicts: The most frequent cause is a conflict with third-party automated backup software (e.g., Acronis, Veeam, or Windows Backup) that is also attempting to utilize VSS at the same time.
-
VSS Service Errors: The Windows VSS framework itself may be stalled or corrupted.
-
High Disk I/O: Extreme disk activity during the snapshot window can occasionally cause the flush command to time out.
Next Steps
If you notice a consistent pattern of red snapshots, we recommend investigating your VSS logs or checking for overlapping backup schedules.
Need assistance? If you are unable to resolve VSS persistence issues, please submit a support ticket with your system logs for further investigation.
Take a new snapshot from there as this won’t require the VSS service. This should bypass the problem.