Prior to issuing a copy or append command on source, it is required to start the launcher on target. This solution delves on question as to whether the launcher needs to be started on target every a copy or append command is issued on source.
When a copy or append is issued from source, a process named sp_sync_svr is launched on source. This happens due to action of issuing the command. On the target a launcher daemon (named sp_sync_launcher) needs to be running for the launching of the client process named sp_sync_clt. For this purpose, the launcher is started once on target and subsequently any number of times a copy or append command can be issued on source so long as the launcher daemon is running on target. Once started, the launcher will keep running even if Shareplex is shutdown on target. When the launcher is stopped by user after all copy commands have been run, it will need to be started prior to running any copy command from source. So it is ok to stop it if there is no more copy commands to be issued or it can be left in running state as deemed necessary for future copy commands.
The following command will start launcher (issued on target sp_ctrl):
The following command will stop launcher:
See Shareplex Reference Guide for details on command syntax.