UNSOLVED
AA
ahmed.aboutabl
23 Posts
0
1168
November 20th, 2012 04:00
Root-to-Root Migration client issue
Dear All, I have a problem after making a siccsesfull root - to- root migration between two Avamar single nodes. I can see all the source clients on the destination server also all policies and Administration configuration was shown. BUT whe I run a backup or restore it is hangen and nothing happens. the source server name is ABC.com ip 172.16.5.114 destination server name is XYZ.com ip 172.16.5.209. I tried to re-register one of the clients to the new server but it failed ttelling me that action is not permited, also I have VMware proxy machines when I tried to reconfigure them it didn't work also. did anyone faced this issue before. Regard, Ahmed Salah
ionthegeek
2 Intern
•
2049 Posts
373
0
Posted November 20th, 2012 06:00
If a client is registered in the root domain (/), replication does not preserve the client's CID. This is by design to avoid issues with the CIDs for the system accounts (MC_BACKUPS, EM_BACKUPS and AVI_BACKUPS) if, against best practice, replication is changed form root-to-root to root-to-REPLICATE or vice-versa. It is recommended not to activate clients directly into the root domain for this reason. One of the side effects is that clients replicated during root-to-root replication will have a CID mismatch between the GSAN User Accounting System and the Avamar Administrator Server Database (MCS Database).
If there are clients activated in the root domain, please open a service request for assistance in correcting the CID mismatch.
There are instructions on how to change the name of a server in the Changing the Name and IP Addressing of Avamar Systems Avamar 4.x or Later Technical Note.
ahmed.aboutabl
23 Posts
373
0
Posted November 20th, 2012 05:00
I need to rename the destination Server with the same name as the source server, but I don't know how, anyone can help ? Thanks