Using results of an EVSVR scan to run a repair in EVSVR

OK so here is the enhancement i'd like to see in Enterprise Vault.

Currently if you are in a dataloss situation where you are missing DVS/DVSSP/DVSCC files and cannot retrieve them from backup, you have to use EVSVR to perform the clean up.
However best practice is to run a report through EVSVR as opposed to going straight in and performing a repair.

Once the report is done and you determine the extent of the issue, you are then to run a repair, which will be the same as the previous report that you ran, except this time it goes ahead and deletes the database entries of the items it cannot find.

So the problem can be this

1. You start your EVSVR scan, which can take a LONG time to complete, say for instance 96 hours
2. You then read the report and determine there are a number of savesets missing, you then run a repair
3. Using the same date ranges as the report, it now takes another 96 hours to complete the repair
4. End result is it has taken 8 days to complete an EVSVR scan.

In those 8 days though so many things can happen
1. The storage goes offline so EVSVR thinks the savesets do not exist and deletes the entries
2. Server reboots so you have to start again etc

I believe the answer to this which makes things both safer AND faster is that when the report has complete, EVSVR can then read the report it generated and perform a repair based on that report.
For instance, you run a report that lists 100 savesets missing out of a total of 100,000 savesets, it then goes and specifically looks at those 100 savesets, makes sure that the items still do not exist and if that time they do not, it then deletes the database entries

This gives us the following benefits:
1. Its safer because the storage can't go offline, leading EVSVR to believe all the savesets are missing
2. Its quicker because its only looking at those 100 items
3. It uses less resources for less amount of time
4. It will make support cases within symantec go quicker because they're not waiting for the tool to complete

And the report/repair/speed/safety issues isn't something thats just confined to EVSVR, but has existed in the past with VSVerify and i think it makes logical sense to have it read off of results its previously generated

cheers

-Alex