Hi Goran,

The backup environment may reach a bottleneck when hundreds of clients but only one Networker server to handle all the traffic.

Resolution

1. Add 1 Storage node apart from just having the Networker server to handle all the backup

2. Create more save groups to handle clients schedule backup jobs.

Check if this fixes the issue.

Arun

Hi,

Do you mean that recover operations are successful but you are seeing this annoying message in the logs or do you mean that recover operations are failing? Do you see these messages when the recover is running or at other times also?

-Bobby

Hi,

has restore worked in the way you want before the update to 7.6? On target machine nothing changed, like IP addressses, routing or network in general? Firewalls have not been switched on perhaps?

Can you connect to NetWorker server using NetWorker User for SQL (GUI), and if not, what is the error message ?

First thank you all for your responds

@Arun Daniel

Ja have only 10 clients.

@coganb

Hmm, today I found unsuccessfull direct restore and I had to restart networker services on client because something freez my SQL server. There is a SQL job which is done every night to perform direct restore from production SQL.

After restarting services everything works fine, and my job finished while it manually restarted.

@mofo

Yes restore worked fine before and after migration but suddenly today I have a problem. Nothing changed, no firewall bitween this two machines, no network changes. This two machines are virtual on same ESX host on same virtual switch.

Hi Goran,

Please have a look on the KB article:esg59591. It might help you.

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

Pradeep