Restore headeronly during differential backup

Hello,

We are using Litespeed in combination with TSM, and I am testing Litespeed 7.1 Fast Compression at the moment.

I noticed that TSM responds to a restore headeronly during a differential backup. I suppose this is to get the details about the current backupset. But since our organisation needs justification for each restore activity I have some questions about this restore headeronly:

1) Is this typical SQL Server or Litespeed behaviour?

2) Can I avoid this to take place on TSM? If yes, how can it be avoided?

Thanks,

Patrick