Hi to all,
I have a problem with one Networker client, every minute it generates the following event in application log
Event Type: Information
The purpose of this client is a daily SQL database direct restore for testing, ther is no need for backup.
Networker Server 7.6 Fast Start - Windows 2003 Standard x86
Networker Client 7.6 Fast Start - Windows 2003 Standard x86
Both machine is a virtual on VMware.
Recently about two weeks ago I succesfully performed an upgrade from Networker 7.5 SP1 to Networker 7.6 server with all clients........ maybe this information help us to resolve this minor problem.
The backup environment may reach a bottleneck when hundreds of clients but only one Networker server to handle all the traffic.
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.
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?
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
Ja have only 10 clients.
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.
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.