Audit question about node schedule and retention

[Raakin]

I have been given an audit question about backup retention. It was asked to List the nodes backed up, how often they are backed up and the retention for the nodes.

Straight forward question. I have easily listed the nodes and associated schedule but I am finding it is a bit more complex than I originally thought to gather the retention.

If all nodes used the standard MC I could easily list it but with the option in the dsm.opt/sys a node could have several retention policies set to it. Perhaps I am missing something so simple I just don't see it.

Is there a way to determine the retention policy of a given node from the server side so I do not have to go to every node and view the policy information?

Any advice or recommendations are welcome.

[fuzzballer]

I think might be what you are after. Seems to satify our auditors.
q co
q co t=a

[Raakin]

I figured there was something sooooo simple I just couldn't see it.
Thanks

[Raakin]

Well, actually, it is a start... but it does not associate the retention policy with the node like I thought when I first glanced at it.

As I mentioned there is a possibility of several retentions for one node depending on the business needs. This does a fine job listing the retention policies but not the associated nodes.

It may be good enough, knowing what I know now for better management of my TSM environment.

[sergimartin]

I have the same problem as you, I'm going crazy looking at documentation, and for now, the only way I see, is to go to every single node and list the inc.exc file.
Does anyone have an answer for that question? You will be a lifesaver!!

[vija]

select distinct class_name from backups where node_name='NODE_NAME'


This select will list you mgmt class which are being used by node name, So from this mgmt you can easily get retention for perticular nodes.

VJy

[sergimartin]

thank you, that's what I need.