Problem
Salesforce records backed up by Druva sometimes appear in snapshots much later than their LastModifiedDate suggests, causing administrators to question backup timing and completeness.
Explanation
This occurs because Druva relies on SystemModstamp for backups, while users typically see LastModifiedDate. Salesforce's internal processes can update SystemModstamp independently of user edits (which update LastModifiedDate), leading to a difference in these timestamps. Druva correctly captures the record change based on the later SystemModstamp.
Example
Record State - LastModifiedDate = March 10th (User edit)
System Update - An internal process updates SystemModstamp to April 20th (LastModifiedDate unchanged).
Admin View - Sees March 10th in Salesforce.
Druva Backup - Correctly uses SystemModstamp, backing up the record in the April 20th/21st snapshot.
Likely Causes for SystemModstamp > LastModifiedDate -
Apex Triggers - Performing secondary system updates on records after the initial user save.
Flows / Process Builder - Automated flows executing subsequent record updates after the user action.
Roll-Up Summary Fields - System updating parent records when child records change, triggering recalculations.
Background Apex Jobs - Updates made to records by scheduled or batch Apex processes running internally.
Field History Archiving - Internal system processes touching records during historical data archival.
Salesforce Maintenance - Record modifications resulting from Salesforce release updates or internal system upkeep.
Feature Enablement/Packages - Background jobs updating records when certain features are enabled or due to managed package logic.
NOTE - This list covers common scenarios, but other reasons may exist. It is recommended to validate specific occurrences with Salesforce Support for confirmation or further investigation.
Why Druva Uses SystemModstamp -
Druva intentionally uses SystemModstamp to identify records for backup because it is the most accurate timestamp, reflecting all modifications, including both direct user edits and internal Salesforce system processes. Unlike LastModifiedDate, which can miss system-only updates, SystemModstamp ensures every change is captured. This approach is essential for maintaining data integrity and providing complete, reliable incremental backups, guaranteeing no modifications are overlooked.
Recommended action -
You can run the below Query in their Developer Console to validate this difference, and if any such difference in these timestamps is found, you should contact SFDC support from your end to get the RCA -
SELECT Id, Name, SystemModstamp,LastModifiedDate,CreatedDate FROM <object name> where ID = '<id of the record>'
This query effectively highlights records where the SystemModstamp is more recent than the LastModifiedDate. You can engage Salesforce Support with these specific instances is the correct next step, as Salesforce should have the internal logs and visibility to understand the exact processes causing these updates.