if it takes a lot of resources then i don't know what i would ask for. but if the report doesn't tell me what it did all i can do is eyeball the result. That might not be very accurate depending on what was being put back.
Hmmm...
We could change restore to publish a cumulative result at the end:
Restored 1438093 files. Restored 32192234 MB of data. 4 files - A, B, C, D could not be restored. 63KB of data could not be restored to file "X" -- tape read error. 16 ACLs could not be set on ...
Would this be helpful? Anybody else have opinions on what they might like to see?
Printing out cumulative results shouldn't hurt performance, and thus is more attractive to a performance weenie like me.
And that way you wouldn't have to troll through the logs of a restore -- just look at the end.
I can file an RFE for this, if you'd like.
Stephen Manley DAM and NDMP Genie in a Bottle