If a client backup is reported in the activity monitor as "Timed Out - Start" it doesn't necessarily mean that the client isn't working properly or that it needs restarting.
The Avamar server may have been too busy servicing other client backups and didn't reach this client before its backup schedule ended.
Make sure the backup isn't scheduled to run during the maintenance window when backup session capacity is limited to 2 per data node and check that there are enough nodes to service all clients.
The likelihood of seeing "Timed out - start" failures will increase if you have relatively few data nodes but have lots of clients which take a significant amount of time to perform backups (therefore hogging the limited session availability).
we are getting exactly the same error (3 years on I know), with Avamar client 6.1.101-87 on Solaris 10. Again, agent starts, requests work, and sleeps, then the grid just changes from 'waiting on client' to 'TimedOut-Response' - the client has never started off the job.
truss-ing the avamar client process shows a lot of ETIME error messages:
Zhou
1 Rookie
•
53 Posts
0
May 22nd, 2009 14:00
2. run /etc/init.d/avagent stop; /etc/init.d/avagent start
Randeep_Singh
1 Rookie
•
74 Posts
0
May 22nd, 2009 21:00
Serg_Shu
4 Posts
0
July 21st, 2011 02:00
I have same problem. How I can solve it?
Avamar Exorcist
462 Posts
0
July 21st, 2011 02:00
If a client backup is reported in the activity monitor as "Timed Out - Start" it doesn't necessarily mean that the client isn't working properly or that it needs restarting.
The Avamar server may have been too busy servicing other client backups and didn't reach this client before its backup schedule ended.
Make sure the backup isn't scheduled to run during the maintenance window when backup session capacity is limited to 2 per data node and check that there are enough nodes to service all clients.
The likelihood of seeing "Timed out - start" failures will increase if you have relatively few data nodes but have lots of clients which take a significant amount of time to perform backups (therefore hogging the limited session availability).
Serg_Shu
4 Posts
0
July 21st, 2011 05:00
First I try to restart Solaris client (V880). In logs lot of lines end with:
Avamar is my backup server.
When I start backup manualy in Solaris client log is
2011-07-21 15:18:55 avagent Info <5962>: Wake up message received
2011-07-21 15:18:55 avagent Info <7151>: first work request delay finished.
2011-07-21 15:18:55 avagent Info <5964>: Requesting work from avamar
2011-07-21 15:18:55 avagent Info <5962>: Wake up message received
ralpmat
1 Message
0
March 7th, 2014 09:00
Hi Sergey,
we are getting exactly the same error (3 years on I know), with Avamar client 6.1.101-87 on Solaris 10. Again, agent starts, requests work, and sleeps, then the grid just changes from 'waiting on client' to 'TimedOut-Response' - the client has never started off the job.
truss-ing the avamar client process shows a lot of ETIME error messages:
Did you ever find a resolution to this?
Thanks,
Matt
Gontse_Len
1 Rookie
•
11 Posts
0
March 28th, 2014 05:00
Ix if the solution I have only works for Exchange DAGs. If it was Exchange DAGs you would have to restart the DAGs Service on DAG's (cluster) manager