List all clients in a backup spec

[JJJ]

HI All

I am trying to do something (I would have imageined) would be quite simple,

List all clients based on backup spec, whether that exports to .txt or .csv etc,

Can anyone assist me here?

Thanks

[Sebastian.Koehler · Accepted solution]

Hi PDS_Support,

I would use omnirpt for this.

omnirpt -report host_statistics -timeframe 168 168 -datalist DATALIST

Regards,
Sebastian Koehler

[JJJ]

Perfect 

Thank you Sebastian

[Pullan]

Hello!

I'm trying to get a list of clients in each backup specification (all clients in MyBackup1, MyBackup2). When I tried to run your command (DP 9.09), I get the following error:

Cell Manager: blah.blah.com
Creation Date: 5/16/2018 10:21:45 AM

Client backup statistics not available.

[Sebastian.Koehler]

Hi @Pullan,

Please try the following command which works in my environment. The quotes are only needed, if the datalist names contain spaces.

omnirpt -report host_statistics -timeframe 168 168 -datalist "DATALIST1" "DATALIST2"

Regards,
Sebastian Koehler

[Gamut]

Although you already have a correct answer, my answer might suite others.

Please note that route via omnirpt -report host_statistics uses a timeframe. Depending on your needs, it is exactly what you want or subtly wrong. If you do not run backups often (or disabled the schedule), you won't get any client. Just set the timeframe to 1 1 and you will get "Client backup statistics not available."

If you want to know which clients will (tried to) be backed up __if__ a backup runs, you might want to try

    /opt/omni/bin/omnirpt -report dl_trees -tab

Although this will list all the clients for all the backup specifications, you can simply filter the output with your favorite tool..

Just another approach which workes in DP9 (but perhaps not in DP10): manually searching the backup specifications files (mine are in /etc/opt/omni/server/datalists and the subidrectories of /etc/opt/omni/server/barlists) is possible. I tend to use it when I can't find the appropriate CLI tool or when the correct CLI tool is too cumbersome or slow. A word of warning: parsing barlists is tedious and therefore error prone and should therefore be avoided.