Browselist saveset within Notes backup.

Are they going to the same pool as well?

No, there are going to different pools: Week, Month, Year

Check pool setting and make sure that pool where you do not get browselist does not have store index entries unchecked. If unchecked, no index is saved thus no browsing (usually used for cloning pools as they share index from source - leading to some interesting problems when you scan such tape on new system).

browselist should contain list of data backed up. Question is why you don't have browselist for some of them.

Yes this is good question. I have no idea. For backups which are running during a week (regular full online backups and logs backups) i can see those *browselist savesets but for backups which are running during weekend there is NO such saveset during backup. The only different between those weekdays backups and weekends backups is retention/browse policy (weekend backups are kept for a longer time - month or year, when weekdays backups are kept for one week).

So, that's not a problem then. Check in applogs if you have module log and if inside you see any failure or anything that would remotely suggest why browselist is not being generated for you.

Unfortunately there is no information about any failure. What is also interesting the backup of Lotus Logs goes to the same pool as the weekend backup goes to - Month, for the log backup *browselist saveset is generated and is backed up (I can see it thru mminfo) but the online weekend full backup (which goes to the same pool) does not have this saveset.

One question, when you say client GUI I assume you are referring to Lotus Notes client GUI, right? Can you browse missing data with nsrinfo using -n notes switch?

Yes, by GUI I mean Lotus Notes Client GUI.

And to answer to your second part of the question: Yes I can see the details (nsrinfo) of the backup made durind weekends to Month/year pool.

I think you will need to engage support for closer look. I know that browselist might not be created if during the backup directory is renamed (at least that has been reported), but somehow I doubt you hit this problem each time. I assume having setup in higher debug should give us or support more clue about what is going on there.