No index was found

Hi Dennis,

Also this may be name resolution issue, Make sure that client FQDN and shortname are present in Networker server's hosts file, Also add all the possible aliases of the client in client resource in NMC. Then try all the network and connectivity commands to check that everything is going well, try the following from the backup server to client , and vice versa:

Ping ( shortname and FQDN)

nslookup (shortname and FQDN)

rpcinfo -p (shortname and FQDN )

Make sure that naming resolution and connectivity are correct.

Hope this helps you.

Thanks,

Ahmed Bahaa

Hi Dennis,

    Is the saveset you are trying to restore within the browse period? If the browse period has expired, then you need either do a saveset recovery or rebuild the indexes to perform a browsable recovery.

You can follow the below KB to perform a saveset recovery.

http://solutions.emc.com/EMCSolutionView.asp?id=esg57424&usertype=C

Regards,

Arun

What the error message/tech note seem to be suggesting is that the index was removed because it expired in the time period between you selecting the files for recovery and starting the restore process.  You can assess if that is reasonable if you know what the browse period is for that data but it would generally be fairly unlikely though not impossible!  It is more likely to be down to inconsistent name resolution.

If you want to restore the SQL database: You must use the "Networker User for SQL Server":

"C: \ Program Files \ Legato \ nsr \ bin \ nwmssql.exe"-s Networker_server

or

"C: \ Program Files \ EMC Networker \ nsr \ bin \ nwmssql.exe"-s Networker_server

So you must have the rights andministratora SQL database.

I'm using "NetWorker User for SQL Server" and yet I can not restore

It means index was not saved under that name.  Is it perhaps cluster in question?

Just for the record, this thread is being answered in the Comunity Forum for Spanish Speakers under the following thread:

no index was found

Thank you,

Carlos

Si, Carlos, Muchas Gracias.