3.2.4. Configuring Startup on Boot

The procedures in this section are designed for the pre-v6.x Multisite/Multimaster topology ONLY. Do NOT use these procedures with version 6.x Multisite Clusters.

For version 6.x Multisite Clustering, please refer to Deploying Composite Multimaster Clustering.

Because there are two different Continuent services running, each must be individually configured to startup on boot:

For the Tungsten Clustering service, use Section 4.3, “Configuring Startup on Boot”.
For the Tungsten Replicator service, a custom startup script must be created, otherwise the replicator will be unable to start as it has been configured in a different directory.
1. Create a link from the Tungsten Replicator service startup script in the operating system startup directory (/etc/init.d):
```
shell> sudo ln -s /opt/replicator/tungsten/tungsten-replicator/bin/replicator /etc/init.d/mmreplicator
```
2. Modify the APP_NAME variable within the startup script (/etc/init.d/mmreplicator) to mmreplicator:
```
APP_NAME="mmreplicator"
```
3. Update the operating system startup configuration to use the updated script.
  On Debian/Ubuntu:
```
shell> sudo update-rc.d mmreplicator defaults
```
  On RedHat/CentOS:
```
shell> sudo checkconfig --add mmreplicator
```

Prev	Up	Next
3.2.2.2. Install: Multisite/Multimaster Clusters using INI Configuration	Home	3.2.5. Performing Schema Changes