No, not clustered. This just started recently and even to some backups that were fine before. I recently added some clients but don't think it has anything to do with this (maybe?)

Could be some sort of corruption with names or IPs... I would check those first.

Your index doesn't get updated correctly under its own name... is that cluster perhaps?

Check if index is going to the full name for the client instead of the short one (if it was configured this way). Check also if someone added any alias to this client.

To me it sounds like it is the media database that has some kind of problem since the CFI isn't needed to determine previous level of backups. That is recorded in the media db. So try to check the media db and see if that helps.

Forgive me, it's been awhile since I have had to do that. What is the command? Is it the nsrck command? Should Networker be up or down to run it?

I didn't add any aliases but somehow they automagically showed up in the client setup. They all appear to be going to the proper index files looking at the index instances. It appears that the backup is not looking in the right place, how can I check that?

Use nsrinfo. nsrinfo from server will show you what is in index (newest entries first).

When you find to which index the data is being saved, you can use save -c to force it to the correct client ,if even adding the aliases to the client resource don't fix the issue.

I ran the nsrinfo on the different clients and they appear to be there from today and the days before yet I still get the message. Any ideas what to look for next?

Actually, nsrinfo is not good idea because:
- you get message for index backup
- index backup is not browsable thus you can't verify it with nsrinfo

So, what is left is that somewhere in media db there is a problem how this is saved (eg. shortname vs. long name of backup server). Right now this error would indicate that you do not have issues with browsable recoveries of your clients, but in DR situation you would probably have issues with nsrck -L7 step. So, I think problem is on server side and server client. Have this opened with support - they will probably be in position to connect to you and verify this quickly and run whatever it is required to fix it.

It is fixed, long story short: We had a DNS server go down which was apparently used for all the client info. When we added hosts = local, bind to netsvc.conf to force the server to look at the hosts file first it was apparently looking for the wrong server name (long name instead of short). I changed the order in the hosts file and now everything is working right.