Storage Expiry is not enabled by default, and if configured, will run in the background based on a preset scheduled. If not disabled before any EVSVR investigations, the following behaviors can be seen:

Scenario 1:
Storage Expiry runs and expires all items in a Collection, the RefCount in the Collection table will have a residual value of 1 (this is by design)

Before the collection is removed:

1. A DatabaseLinkages in  verify mode at this stage would highlight this as an inconsistency
   

   	Collection RefCount: 1, VS DB Saveset record count: 0

2. A DatabaseLinkages in Repair mode would set the RefCount to 0
3. A DeleteSurplusReference in Verify mode would highlight this as an inconsistency
4. A DeleteSurplusReference in Repair Mode would fail and terminate asking to run DatabaseLinkages in Repair Mode

Scenario 2:

Storage Expiry is running and the process is placed in backup mode for an EVSVR run:

1. A DatabaseLinkages in Repair mode would repair any inconsistencies between the RefCount and actual Saveset Count
   

   	2012-08-08 16:44:05              Collection Reference Counts do not match. VS DB	TotalCount: 217, VS DB RefCount: 146, VS DB Saveset record count: 149, FP DB SISPart and Converted Content record count: 0
   	2012-08-08 16:44:05              Repaired collection record - Reference Count set to 149 

2. A DeleteSurplusReference in Repair Mode would fail and terminate asking to run DatabaseLinkages in Repair Mode

Disable Storage Expiry during the whole duration of the EVSVR investigations.