No update will make this go away. Mistake has been done at early stage. I would suggest to scan older data under name of bogus client.

Did you check with support. They would have some process for this. They had helped us with mminfo etc when we had two client ID's for the same client.

It looks like you have 2 clients for the same machine. One with the short name another with the FQDN. While restoring, try using recover -c cy-bkp01.domain.com You should be able to restore the backups using this.

As far as making sure that you have only one client, you might need to delete the client resource where no index entries are getting stored. If you look at the index size you should get an idea of which one you need to delete. Once you delete the client resource, say the one with the short name, add the short name as an alias for the client resource with the FQDN.

I think the problem here is more complex as we are talking about backup server which has two hostids - right? If not, if that would be a client, then it would be easy to fix it.

You are right. Does look like the backup server. If it is the backup server, contacting support would be the best bet.

Unfortunately you have right Hrvoje, our problem is the Backup Server with two host IDs. The mistake was happened, obviously during the NetWorker update from 7.3 to 7.4 and now we would like to get it away before we go to 7.4.3 or 7.5.
What did you mean exactly as you said/ suggest ¿to scan older data under name of bogus client?¿

Did you try to do a recover -c cy-bkp01.domain.com I had a similar problem once and I was able to recover data using the old backup server / client resource name. In terms of merging the index entries for the two different client ids, it's a little more complicated. I got the exact steps from support that time around and it was tricky even with the instructions. Would suggest a backup of your /nsr directory with networker services down before you attempt any merging.

It really depends how much data you have prior to upgrade which should still be recoverable. If that amount is not that big (and I would assume it is not by guessing that would be just monthend backup) then I would create new clientname using old hostid first (you must create bogus entry in hosts table). Then you scan old data. -c as Hari said might do the trick and ssid restore might also work (if data is recoverable). It would be interesting to see what caused this; recently I have seen same thing upon update from 7.4SP2 to 7.5. Few tests showed that this does not happen when nsrauth is disabled (no idea why).

Update to my earlier post..does nsradmin show server having two id's?

I see that you have a full bootstrap backup. Maybe you can use mmrecov to recover old media DB?

Does nsradmin show the client having two clientids?

Regarding scan of old data,
well the company is using Legato Backup software since 2001 and amount of saved data is really big, (if we are take only the monthend backup ¿ 3 -5 LTO tapes/month it will be more than 100 LTO 1 tapes,.and in real we are having much , much more important data and actually all data that are saved should be also recoverable, even if their retention has expired, so that with scanning of all old tapes is almost impossible at the moment)

for recover ¿c option

When I try to run recover -c following message occurs:

User@cy-bkp01:/>recover
39584:recover: No files have been backed up for this client. No index was found on the server for the path / on this client.
User@cy-bkp01:/>


User@cy-bkp01:/>recover -c cy-bkp01.domain.com
39584:recover: No files have been backed up for this client. No index was found on the server for the path / on this client.
User@cy-bkp01:/>

-------------
ps.
The Service Request to our Support is going to be opened still today¿

how can I check it with nsradmin?

You can't - you can see that with mminfo or from NW GUI if you check details for client (which will show current hostid being used).

I personally would not trust LTO1 to keep my data safa for that log and besides I would count only data that is recoverable. Obviously you could have two server setups; one with older state and and one with current one and switch those depending which restore date you need. Not the best solution, but after all this time you do not have many options left.

nsradmin -i client_info.txt

where client_into.txt has...

-----------------
. type: nsr client

show name;comment;group;schedule;browse policy;retention policy;save set;group;schedule;backup command;application information;Aliases;Scheduled backup;networker version;ndmp;parallelism;remote access;storage nodes;client id;

print
-------------

This will show you all details of a client or server..a sample of my listing..

Current query set
name: prd-tapesrv2;
client id: \
25bec060-00000004-3ffc535a-3ffc5359-00010000-ac11645f;
-------------

etc..

Indeed, I stand corrected. For online nsradmin queries you can see clientid (I've been doing too many of those offline queries lately).