Unsolved
This post is more than 5 years old
51 Posts
0
1847
October 24th, 2012 03:00
Move failed when moving clients between single nodes
I have new node where I would like to move clients from old node. I have added old node to Enterprise Manager (6.1.0-402, since you cannot add 6.1 node to EM 6.0) and I'm trying to move clients to new node from EM Client Manager.
Whatever I do (replicate backups or not, delete from source or not) it ends up to failure:
"Move Failed. Client software could not be contacted."
I've tried this with pageable and non-pageable clients, no difference.
Old node is 6.0.1.66 and new node is 6.1.0-402, but this doesn't work even between two 6.1.0-402 nodes. There is no firewall between nodes. We're not replicating anything between nodes.
Any ideas where to look for resolution, logs or am I just missing something relevant?
0 events found


niko.virta
51 Posts
0
October 25th, 2012 04:00
If you mean what is the state in EM Client Manager -> View Log -> Management Log, yes the state is pending.
First Description is that "Move Failed. Client scheduled for 24 retries. Invitation failed - Client software could not be contacted." with status code 22271. Then the next ones are just Invitation failed - Client software could not be contacted." with status code 22271.
Haven't touched to acm.properties to speed up the retry attempts yet. Any idea where I could get more detailed logging about this?
5.0 Admin Guide lists some possible reasons for this code (dropped from 6.0/6.1 AG):
- The hostname does not exist on the network
- Avamar server cannot communicate with the invited computer
- Avamar client software is not installed on the invited computer
First one makes me wonder should this work with non-pageable clients at all, second & third one should be OK if the client is online and working.
Sandeep_Sinha
307 Posts
0
October 25th, 2012 04:00
Hello,
After the client move failure, what's the client state on the source grid, is it changed to pending ?
Sandeep_Sinha
307 Posts
0
October 26th, 2012 05:00
Please open a Service Request with Avamar support to get this investigated