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
1816
2
Posted 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