Run the backup again and once completed issue below command on the backup server to see the status of the backed up data:

mminfo -avot -c client_name -t "2 day ago"

where client_name is the name of your solaris client.

Also you can see the logs in daemon.raw:

nsr_render_log /nsr/logs/daemon.raw | grep client_name

I had run a backup earlier and ran the commands below and "no matches found for the client"

I had watched the backup and data was written to tape and completed successfully. If you look at the index in NMC it shows the size s 734MB.

Can u share the output of command:
nsr_render_log /nsr/logs/daemon.raw | grep group_name

where group_name is the networker group resource for the effected client.

Also in the NMC details does it show the successfull data saveset beside index saveset ?

Hi,

I recently tried this and the negative result was a full backup of the client every day instead of an incr. The daemon log and GUI client details revealed nothing in my case. So maybe this can help:

If you run the backup in CLI:
savegrp -v -c

In the debug info you get a log pointed out:
/nsr/tmp/sg/group name/sso.client name

In my case the log said:
~Where:
ClientA - the client name defined
ClientB - the client the index was written to~

"sso.clientA" 11 lines, 866 characters
7198:savefs: path /var by default belongs to client ClientB and NOT client ClientA!
7200:savefs: Default client index for scheduled save will be that of ClientB.

...and the same for the remaining file systems

And looking at the client index entries for ClientB revealed data for ClientA.

So maybe thats what you see?

NB: My client belongs to a cluster=>index confusion (probably! Haven't had time to solve the issue)

Best regards
JGR

You may have a client id issue - have you at any time renamed the client?

Client IDs can be a pain in the ass. I just had to rename a whole bunch of clients using dummy hostnames which was rather painful. EMC should come up with an easier way to do this!

That was the issue, client was using another client id. I ran the backup in verbose and noticed once data was saved, it was saved under the other client. I was able to resolve the issue and seems to be okay.

Thanks