This post is more than 5 years old
10 Posts
0
626
March 11th, 2015 13:00
Scheduled clone reporting
Hi All,
We're fairly new to the Networker world and have just started to perform monthly scheduled clones to an LTO tape library. We'd like to report on the tapes which were used each month and the save sets included on each tape. This would assist the local staff so that they can pull the necessary tapes and send them off-site for safekeeping.
The only place I've found in the GUI with data including clients, save sets, and tape (or volume) is in Media > Save Sets. Is there any other way of obtaining this data? Ideally, we would have a report in NMC, but I didn't see anything that included the tape bar code label. I also understand that there are command line tools available that might be of use for this.
Has anyone else been faced with a similar situation? Can anyone lend advice on how this data can be automated with a script?
..If it matters, we're running Networker v8.2.0.1 on Win 2008 R2.
Any help is much appreciated!
Thanks.
bingo.1
2.4K Posts
0
March 11th, 2015 23:00
mminfo is the command you want to use. I personally find the volume report useful. Example:
mminfo -q "family=tape,savetime>=01/01/2015,savetime<02/01/2015" -r "client,name,level,savetime,ssid,sumsize,ssflags,volume" -ocnt -xc, > ss_tape_report_yyyy_mm.txt
Ready to to be imported to an Excel spreadsheet.
Of course you can modify the command using the appropriate mminfo options.
IMHO, the save set information is not really required as you have the admin GUI or mminfo for that purpose.
If you set the "location" field in the media db you can also run this report:
mminfo -q "location=safe,savetime>=01/01/2015,savetime<02/01/2015" -r "volume" > tapes_yyyy_mm.txt
ble1
2 Intern
•
14.3K Posts
1
March 11th, 2015 13:00
You can use mminfo command to run queries and reports (CLI).
crazyrov
4 Operator
•
1.3K Posts
1
March 11th, 2015 23:00
Use the mminfo to query the volume or saveset details for the respective volume pool. Eg :
mminfo -avot -q pool=xyz
jpanei
10 Posts
0
March 12th, 2015 10:00
Thanks all, for your suggestions and examples with the mminfo command. I think we'll be able to get the information that we need with minimal effort!