1) Obviously if the root passwords have been changed, use the correct ones instead of the default 2) You don't have to specify just a client name, you can specify a domain path and it will assume all clients and subdomains from that point. 3) Only backups which do not exist on ServerA will be copied from ServerB, so a rollback will essentially be reversed if replication has run. 4) Of critical importance is the --restore flag, without which this process will not work
Do you want to send the data that is replicated in site2, back to the site 1?? That would be nice to know, it has never happend to me that case, but when you get it please let me know the procedure
In your command you tried replicating from /REPLICATE/clients to /teste
Make sure that we need to replicate the data from /REPLICATE/clients to /clients on source, we cannot use different domain
As far as --restore switch is concern , it assumes that the data needs to be replicate back from destination to source, for any error please paste the output of
Amol
2 Intern
•
207 Posts
2
August 13th, 2009 05:00
Replication Source: ServerA
Replication Target: ServerB
To push backups from ServerB BACK to ServerA, you must run a manual replication as follows:
nohup replicate --dstaddr=ServerA --dstid=root --dstpassword=8RttoTriz --hfsaddr=ServerB --id=root --password=8RttoTriz --restore --srcpath=/path/to/client --dstpath=/path/to/client --logfile=/home/admin/repl-restore.log 2>&1 &
A couple of notes:
1) Obviously if the root passwords have been changed, use the correct ones instead of the default
2) You don't have to specify just a client name, you can specify a domain path and it will assume all clients and subdomains from that point.
3) Only backups which do not exist on ServerA will be copied from ServerB, so a rollback will essentially be reversed if replication has run.
4) Of critical importance is the --restore flag, without which this process will not work
Message was edited by:
Amol Powar
OscarG1
2 Intern
•
137 Posts
0
August 12th, 2009 14:00
Hormigo
2 Intern
•
131 Posts
0
August 12th, 2009 15:00
I think it should be, because if not, this is a big problem.
Hormigo
2 Intern
•
131 Posts
0
August 13th, 2009 07:00
Dubts:
I don't understand the item 4. You could explain more this item.
Thanks!!!
OscarG1
2 Intern
•
137 Posts
0
August 13th, 2009 07:00
The item 4: I guess that means that it has to be the --restore flag in the command line to make it work. otherwhise it will not work.
Hormigo
2 Intern
•
131 Posts
0
August 13th, 2009 08:00
Hormigo
2 Intern
•
131 Posts
0
August 13th, 2009 12:00
I running in source and destination, nothing occurs.
Following:
nohup replicate --dstaddr=avamar01-01.lab-f9c.com.br --dstid=root --dstpassword=8RttoTriz --hfsaddr=avamar02-01.lab-f9c.com.br --id=root --password=8RttoTriz --restore --srcpath=/REPLICATE/clients/ --dstpath=/teste --logfile=/home/admin/repl-restore.log 2>&1 &
Source(the original files)= avamar01-01
replication = avamar02-01
Back data (replicate) from avamar02-01 to avamar01-01.
Could you help me?
Amol
2 Intern
•
207 Posts
1
August 13th, 2009 13:00
nohup replicate --dstaddr=avamar01-01.lab-f9c.com.br --dstid=root --dstpassword=8RttoTriz --hfsaddr=avamar02-01.lab-f9c.com.br --id=root --password=8RttoTriz --restore --srcpath=/REPLICATE/clients/ --dstpath=/clients --logfile=/home/admin/repl-restore.log 2>&1 &
In your command you tried replicating from /REPLICATE/clients to /teste
Make sure that we need to replicate the data from /REPLICATE/clients to /clients on source, we cannot use different domain
As far as --restore switch is concern , it assumes that the data needs to be replicate back from destination to source, for any error please paste the output of
/home/admin/repl-restore.log
Hormigo
2 Intern
•
131 Posts
0
August 20th, 2009 14:00
nohup replicate --dstaddr=avamar01-01.lab-f9c.com.br --dstid=root --dstpassword=8RttoTriz --hfsaddr=avamar02-01.lab-f9c.com.br --id=root --password=8RttoTriz --restore --srcpath=/REPLICATE/marge.lab-f9c.com.br --dstpath=/marge.lab-f9c.com.br --logfile=/home/admin/repl-restore.log 2>&1
Run in Destination SITE2 (avamar02-01).
The clients have be add in SITE1 (avamar01-01) again.
verify the log: /root/nohup.out.
f25
1 Rookie
•
16 Posts
0
April 18th, 2025 09:54
@Amol One more thing, on the newer Avamars, custom rules should be added to Avamar firewall.
1. To check: (on source) # telnet <target_Avamar> 27000
[If works, ok...]
2. If did not work:
Avamar: How to add or remove custom Avamar firewall rules with edit-firewall-rules.sh | Dell US
Add custom rule "outgoing" on source, "incoming" on target to 27000 on target.