Why is a session still seen after the related objects have expired?

To have an answer to this question, it is important to understand that in the Data Protector Internal Database (IDB) everything is based on media. As long as the medium is there, related objects will be there and even the session report will stay. What will be removed when the objects are expiring is basically the catalogs. All other info (e.g. object details or session reports) is very small compared to the catalogs. So the biggest part is deleted at expiration time. Keeping the session listed makes it easy to import catalogs again if required.

It is possible to "Remove Session" in the IDB context of the GUI. All this is doing is actually flagging the session not to be displayed anymore. So the GUI will not list it anymore and also "omnidb -session"  won't list it. BUT if the sessionID is known then details can still be retrieved by running "omnidb -session <SessionID>" or even "omnidb -session <SessionID> -detail". The report however will not be retrievable anymore.

The way to have everything removed from the IDB is by exporting the medium. This will delete the medium and everything linked to it. In case of a null device this will be the only way to have it all removed. In case of a tape device, this will normally happen when the tape is overwritten. In case of a B2D medium, it will happen when the slot and medium is getting deleted during daily maintenance or by using "omnimm -delete_unprotected_media".

If you found this post useful then please make sure you are logged on and give it a “Like”.
You may be interested in some of my other Support Tips too: Support Tips listed per category.