Networker query returning odd information

The time format looks strange - i would prefer the english time stamp like:

   nsrmminfo -s    //

                   -q "client= ,level=full,savetime=01/01/2015"  //

                   -r "savetime(18),ssinsert(18),sscreate(18),sscomp(18),totalsize(15),level,name"

It could also be that the time conversion is wrong. You can rely on the UNIX time stamp but it is not available to all attributes.

mminfo only knows 'nsavetime'.

To compare the savetimes I would not rely on ssinsert as this may vary. I think if you re-add a save set through scanner, it will later display that timestamp.

If you tell us what you really want to achieve, we probably could provide a better solution or alternative.

Trying to calculate the amount of time it took to perform the backup, the size of the backup, to calculate the MB/sec throughput we are achieving on backups.

Additional information:

I have a few entries where the completion time is prior to the other recorded times.  They also appear for different dates/times.

Here is just one example

"nsavetime(15),savetime(18),ssinsert(18),sscreate(18),sscomp(18)"
      save time  date    time    ss inserted        ss created      ss completed
    1428056952 04/03/15 05:29:12 04/03/15 05:29:17 04/03/15 05:29:17 04/03/15 05:18:33

From the command reference guide on query and reporting

attribute name - value range- width - description
nsavetime - NA - 11 - The save time, printed as seconds since 00:00:00 GMT, Jan 1, 1970.
savetime - time - 9 - The save time (on the client).
sscomp - time - 9 - The save set’s completion time. This is the time the save set backup was completed.
sscreate - time - 9 - The creation time (on the server). If the client and server clocks are out of sync, this time may be different from the save time.
ssinsert - time - 9 - The save set’s insertion time. This is the time the save set was most recently introduced into the database (for example, by a backup or by running scanner(1m)).

It looks like a bug.  Did you verify timestamps in daemon.raw on server side for specific client?  Does this anomaly show up only for specific client(s) - like only OpenVMS ones?

I don't have access to the networker server - will send to our backup team so they can check the daemon.raw. On the VMS side the daemon.raw is barely logging anything.  Nothing really with detailed backups.

I was referring on daemon.raw on backup server.  Also, do you run mminfo on backup server or from the client?  Normally, I would not expect any difference, but if OpenVMS is involved I would verify that too.