Try to run the following command:

mminfo -r"client, name, totalsize" -q"ssflags=I"

I thought "i" was for in-progress savesets.

That's the point. Active save sets are actually "in progress" ones, so you can see active sessions this way...

I was referring to "i" vs "I".

Thanks

The command is not valid because the ssflags is only valid for reports.

D:\win32app\nsr\bin>mminfo -r"client, name, totalsize" -q"ssflags=i"
mminfo: constraint `ssflags' is only valid for reports
usage: mminfo [-avV] [-o order] [-s server] [-x exportspec] [report] [query] [volname...]

: [ -m | -p | -B | -S | -X | -r reportspec ]
: [-c client] [-N name] [-t time] [-q queryspec]

You can grep (findstr in Windows world) incomplete flag for given column (not sure how to do that in Win32 world). Not sure if mminfo -av -q incomplete -r would give you what you are after, but you can give it a try.

This command almost returns the information, but the totalsize is not updatede until the saveset i complete.

D:\win32app\nsr\bin>mminfo -v -r"client,name,totalsize,ssflags" -q"incomplete" | find "viI"
nas2.dst.local E:\Fkontor 0 viI
srvlov3.dstlov.local D:\FM\NSM 0 viI
srvlov3.dstlov.local D:\MB 0 viI
srvnas4.dst.local E:\sasdata\sasdata\S5003 0 viI
srvnas4.dst.local F:\FseData\Grunddata 0 viI

If sumfiles is used the command returns information per volume, but the active volume is 0 KB

D:\win32app\nsr\bin>mminfo -v -r"client,name,sumsize,volume,ssflags" -q"incomplete" | find "viI"
nas2.dst.local E:\Fkontor 132 GB DS0092L2 viI
nas2.dst.local E:\Fkontor 55 GB DS0095L2 viI
nas2.dst.local E:\Fkontor 66 GB DS0097L2 viI
nas2.dst.local E:\Fkontor 83 GB DS0100L2 viI
nas2.dst.local E:\Fkontor 99 GB DS0109L2 viI
nas2.dst.local E:\Fkontor 282 GB DS0116L2 viI
nas2.dst.local E:\Fkontor 314 GB DS0117L2 viI
nas2.dst.local E:\Fkontor 498 GB DS0118L2 viI
srvnas4.dst.local E:\sasdata\sasdata\S5003 659 GB DS0119L2 viI
srvnas4.dst.local F:\FseData\Grunddata 270 GB DS0119L2 viI
nas2.dst.local E:\Fkontor 109 GB DS0121L2 viI
nas2.dst.local E:\Fkontor 107 GB DS0122L2 viI
nas2.dst.local E:\Fkontor 239 GB DS0123L2 viI
srvnas4.dst.local E:\sasdata\sasdata\S5003 0 KB DS0194L2 viI
srvnas4.dst.local F:\FseData\Grunddata 0 KB DS0194L2 viI
srvlov3.dstlov.local D:\MB 42 GB DS0399L2 viI
srvlov3.dstlov.local D:\FM\NSM 13 GB DS0399L2 viI
nas2.dst.local E:\Fkontor 0 KB DS0405L2 viI
srvlov3.dstlov.local D:\FM\NSM 0 KB DS0416L2 viI
srvlov3.dstlov.local D:\MB 0 KB DS0416L2 viI

Well, you can't know how much you will backup until backup is still running. It's a problem of logic as totalsize will be displayed for ssid and until ssid is not finished total size is uknown. As far as I know there is such thing as current size. Didn't try, but I think same applies to sumsize.

hmmm, how about extracting the group information from nsradmin as follows

nsradmin> show name;start time;completion;work list;completion
nsradmin> print type: nsr group; name: GroupName


this will show you the output from the specific group with what has completed, the sizes, completion, level etc and also what is still outstanding "worklist"

I believe the problem is that Bo is looking for method how to see size of incomplete (in-progress) saveset and not completed one. That makes sense only for full backups or/and when level/increental backups are consistent in change/size per day basis. The only way to get that is to parse it from daemon.log and calculate it. I didn´t try, but it sounds like nsradmin will also give you completed savesets reports (as opposed to currently running ones).