Could some kind soul possibly provide me with a simple walkthrough for starting up Fathom Replication? We're in the middle of an office move and sadly our replication target lost a volume in the midst of the move and it had to be recreated. Rather frustratingly it's the database volume that's gone.
I'm assuming that I should create new dbs from the most recent backups? And then set them up as replication targets? This is the one eventuality I'm poorly prepared for, typically!
I am assuming the db.repl.properties files are still intact and that the PROD DB is online. I am also assuming that you did NOT disable replication on the source side.
Source:
probkup online src src.bkp -REPLTargetCreation
scp src.bkp target:/tmp
Target:
prorest tgt /tmp/src.bkp
proutil tgt -C enablesitereplication target
<start the DB with all the normal params>
dsrutil tgt -C monitor -> select agent
Source:
dsrutil src -C restart server
dsrutil src -C monitor -> select server
IF the rpserver was still running, then instead of the restart server do:
dsrutl src -C connectagent agent1
Thanks Paul. I will give it a go.
Unfortunately the server has died completely and I'm having to reconfigure a spare. I've copied the properties folder over to the new box, but when I try to start the db as per your instructions I get errors. I've copied the log file...
Sun Apr 20 16:11:46 2014
[2014/04/20@16:11:46.613+0100] P-3360 T-2184 I REPLENB : (451) EnableSiteReplication session begin for inencoadmin on CON:.
[2014/04/20@16:11:46.613+0100] P-3360 T-2184 I REPLENB : (7129) Usr 0 set name to NETWORKS\inencoadmin.
[2014/04/20@16:11:46.628+0100] P-3360 T-2184 I REPLENB : (10351) Replication (target) is now enabled for database secure.
[2014/04/20@16:11:46.628+0100] P-3360 T-2184 I REPLENB : (334) EnableSiteReplication session end.
Sun Apr 20 16:15:26 2014
[2014/04/20@16:15:26.645+0100] P-3568 T-3532 I BROKER 0: (10356) Access to database secure not allowed. The database is enabled for site replication but either replication is not running, or this process is not authorized to open a replication enabled database.
Sun Apr 20 16:16:02 2014
[2014/04/20@16:16:02.368+0100] P-2908 T-3416 I : (451) Replication Status session begin for SYSTEM on batch.
[2014/04/20@16:16:02.373+0100] P-2908 T-3416 I : (7129) Usr 0 set name to NT AUTHORITY\SYSTEM.
[2014/04/20@16:16:02.407+0100] P-2908 T-3416 I : (334) Replication Status session end.
Sun Apr 20 16:16:02 2014
[2014/04/20@16:16:02.469+0100] P-3480 T-2352 I : (451) Replication Status session begin for SYSTEM on batch.
[2014/04/20@16:16:02.474+0100] P-3480 T-2352 I : (7129) Usr 0 set name to NT AUTHORITY\SYSTEM.
[2014/04/20@16:16:02.501+0100] P-3480 T-2352 I : (334) Replication Status session end.
Sun Apr 20 16:16:02 2014
[2014/04/20@16:16:02.621+0100] P-2452 T-636 I : (451) Replication Status session begin for SYSTEM on batch.
[2014/04/20@16:16:02.625+0100] P-2452 T-636 I : (7129) Usr 0 set name to NT AUTHORITY\SYSTEM.
[2014/04/20@16:16:02.629+0100] P-2452 T-636 I : (334) Replication Status session end.
Sun Apr 20 16:16:02 2014
[2014/04/20@16:16:02.805+0100] P-3508 T-2428 I BROKER 0: (10356) Access to database f:\database\secure\secure not allowed. The database is enabled for site replication but either replication is not running, or this process is not authorized to open a replication enabled database.
[2014/04/20@16:16:49.651+0100] P-764 T-2112 I RPLU (1423) There is no server for database F:\DATABASE\SECURE\secure.
[2014/04/20@16:16:49.653+0100] P-764 T-2112 I REPL : (10429) The user failed to connect to database F:\DATABASE\SECURE\secure with error -1 in rpDB_OpenDatabase.
[2014/04/20@16:16:49.653+0100] P-764 T-2112 I REPL : (10717) The Fathom Replication Utility cannot connect to database F:\DATABASE\SECURE\secure.
Any ideas please?
I think it may be because we don't have the db.repl.properties files. Bugger.
I've got the properties from the server. Will that help?
Yes it will help though it may not be 100% correct. We like to keep the source and target repl.properties the same but often they are not.
I think you're close. It looks like the db is a target. You need to start it with -DBService replagent.
Thanks Paul. Once I've got that sorted there's only 5 others to go... lol
When I try and restart the replication server on the src I'm now getting
"Cannot connect to replication shared memory. Satus = -1".
In the db log file:
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (10507) The Fathom Replication Server has successfully connected to the Fathom Replication Agent agent1 on host 192.168.125.228.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (11251) The Replication Server successfully connected to all of its configured Agents.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (11703) It appears the Target Database f:\database\secure\secure has been restored since the last time Replication was run. Replication to this Agent agent1 cannot continue.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (10440) Either the Fathom Replication Agent agent1 has been incorrectly configured or the target database f:\database\secure\secure has been improperly sourced.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (11696) The Agent agent1 cannot be properly configured and is being terminated.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (10700) The Fathom Replication Agent agent1 is being terminated.
[2014/04/20@21:04:21.457+0100] P-9064 T-11444 I RPLS 47: (10504) Unexpected error -129 returned to function rpSRV_ServerLoop.
[2014/04/20@21:04:23.463+0100] P-9064 T-11444 I RPLS 47: (10505) The Fathom Replication Server is ending.
Looks like you need to re-init the target. Probably safest to disable replication on the src and start over. No need to stop the prod db. Are you using the AI archiver?
Src:
dsrutil src -C disablesitereplication target
rfutil src -C aimage list
Make sure there are a couple of empty extents afyer the buay
proutil src -C enablesitereplication source
probkup online src src.bkp -REPLTargetCreation
Then reuse my procedure from above.
Yeah we are. Will give that a go in the morning.
That is awesome Paul! reinitialising has done the trick. I have the first db happy.
Unbelievable! I have all 6 databases replicating like a dream now. Thanks so much for your help Paul.