This post is more than 5 years old
10 Posts
0
2270
September 2nd, 2012 23:00
replication failure when moving client
We have a root to root replication between two nodes and mainly use AVAMAR for VMware environemnts via image based backups.
The nreplication entry is set to "complete" with some clients being excluded intentional.
Recently two of our VM were moved from TEST to PRODUCTION domain in AVAMAR (Administration -> Account Management -> select client -> Move)
The move process went flawless but the replication is now broken as the replication tries to find the VM entry on the remote AVAMAR node in the "new" domain while the replication entry is still in the "old" domain on the remote AVAMAR node.
To overcome the situation we had to move the clients back to the original domain on AVAMAR which is not real solution due to the incorrect server classification between test & production.
Any idea how we can fix the issue or what we did wrong?
Nikolaus
Sandeep_Sinha
307 Posts
0
September 4th, 2012 07:00
Hello,
Please edit the /usr/local/avamar/etc/repl_cron.cfg file and add --force-move on a separate line and then try to perform replication.
Sandeep_Sinha
307 Posts
0
September 3rd, 2012 06:00
Hello,
Can you please paste the error you received for replication when the VM clients were moved to PRODUCTION domain on the source Avamar, also which Avamar server version are you running ?
TheOneAndOnlyNi
10 Posts
0
September 3rd, 2012 09:00
Both nodes are on v6.0.1.66 and the issue is not moving the client to another domain (that works fine) but that the replication is broken once you move a client VM to another domain.
Below is an example from the replication logfile:
2012/09/03-07:43:45 avtar Info <5552>: Connecting to Avamar Server (bebruavamar)
2012/09/03-07:43:45 avtar Info <5554>: Connecting to one node in each datacenter
2012/09/03-07:43:45 avtar Info <5552>: Connecting to Avamar Server (esmadavamar.eur.ko.com)
2012/09/03-07:43:45 avtar Info <5554>: Connecting to one node in each datacenter
2012/09/03-07:43:45 avtar Info <5583>: Login User: "root", Domain: "default", Account: "/bebrui38.eur.ko.com/VirtualMachines/Prod/BEBRUA43_UomqGmsfWSZuNfhmaq9qHA"
2012/09/03-07:43:45 avtar Info <5580>: Logging in on connection 0 (server 0)
2012/09/03-07:43:45 avtar Info <5582>: Avamar Server login successful
2012/09/03-07:43:45 avtar Info <5583>: Login User: "repluser", Domain: "default", Account: "/REPLICATE/bebruavamar/bebrui38.eur.ko.com/VirtualMachines/Prod/BEBRUA43_UomqGmsfWSZuNfhmaq9qHA"
2012/09/03-07:43:45 avtar Info <5580>: Logging in on connection 0 (server 1)
2012/09/03-07:43:45 avtar Error <0000>: Login error 74: Account not found in the Avamar database
2012/09/03-07:43:45 avtar Error <10510>: Problem logging into Target Avamar server (1)
So basically when we move the host on the AVAMAR server from /VirtualMachines/Test to /VirtualMachines/Prod the next replication will fail as the client entry is only moved on the AVAMAR node performing the backup and not on the remote node.
Once we move the Client back to /Test domain all will work fine (see below):
2012/09/03-07:57:28 avtar Info <5583>: Login User: "root", Domain: "default", Account: "/bebrui38.eur.ko.com/VirtualMachines/Test/BEBRUA43_UomqGmsfWSZuNfhmaq9qHA"
2012/09/03-07:57:28 avtar Info <5580>: Logging in on connection 0 (server 0)
2012/09/03-07:57:28 avtar Info <5582>: Avamar Server login successful
2012/09/03-07:57:28 avtar Info <5583>: Login User: "repluser", Domain: "default", Account: "/REPLICATE/bebruavamar/bebrui38.eur.ko.com/VirtualMachines/Test/BEBRUA43_UomqGmsfWSZuNfhmaq9qHA"
2012/09/03-07:57:28 avtar Info <5580>: Logging in on connection 0 (server 1)
2012/09/03-07:57:28 avtar Info <5582>: Avamar Server login successful
2012/09/03-07:57:29 avtar Info <5550>: Successfully logged into Avamar Server
2012/09/03-07:57:29 avtar Info <5295>: Starting replicate at 2012-09-03 07:57:29 CEST as "admin" on "bebruavamar" (4 CPUs) [6.0.101-66]
Did we miss a step in moving the client on the replication host? Was under the impression that the information that a client has been moved will be transferred during next replication session.
Nikolaus
TheOneAndOnlyNi
10 Posts
0
September 4th, 2012 14:00
Thank you very much - problem solved by adding the line according to your recommendation!
Nikolaus