- Run the following line, you should see the old grid name and the new grid name:
root@host:~/#: avmgr getl --path=/MC_SYSTEM
1 Request succeeded
1 OLDGRIDNAME.domain location: hex number pswd: hex number
1 NEWGRIDNAME.domain location: hex number pswd: hex number
- Next create avagent.cmd in /usr/local/avamar/var/
root@host:~/#: vi /usr/local/avamar/var/avagent.cmd
- Enter the following two lines and save:
--hostname=OLDGRIDNAME.domain
--mcsaddr=CURRENTIPADDRESS (not old one)
- Restart the Avamar Client Agent:
root@host:~/#: service avagent restart
- You should see the following
avagent Info: Stopping Avamar Client Agent (avagent)...
avagent Info: Client Agent stopped.
avagent Info <5008>: Logging to /usr/local/avamar/var/avagent.log
avagent Info <5174>: - Reading /usr/local/avamar/var/avagent.cmd
avagent Info <5417>: daemonized as process id 52585
avagent Info: Client Agent started.
- Once the service has restarted, go into Avamar Administrator, Policies and select the domain your grid is in. You should see your new grid name and old one. Make sure neither of them are disabled and replication will start working.
- For those interested in seeing what is in the log for the stuck job:<logdir ack="no" errdesc="Message intended for Client '04012b6ed263497e84e7b3f0a96300d6fd12989f' received incorrectly at agent on NEWGRIDNAME:1.1.1.1(e433961fb4975d1aa2ce635993242f2"21083161d) currently registered to 'newprod'" pidnum="1008" targetCid="" browsetimeout="10" maxelems="-1" file="MOD-1352394809289" supportbundle="false" sync="fg" cmd="getworklog" cid="04012b600d6fd129d26349789fee84e7b3f0a963" errno="6207" showd