# Stopping replication

To stop replication of a database, connect to the master database using the `stopMaster=true` connection URL attribute.

The master sends the remaining log records that await shipment, and then sends a stop replication command to the slave. The slave then writes all logs to disk and shuts down the database. For example, for a database named `wombat`, you might specify the following connection URL:

    jdbc:derby:wombat;stopMaster=true

To stop replication on the slave system if the connection to the master is lost, use the `stopSlave=true` connection URL attribute.

See the Derby Reference Manual for details about these attributes.

You cannot resume replication after it has been stopped. You need to start replication over again from the beginning using the `startMaster=true` attribute, as described in Starting and running replication.

Parent topic: Replicating databases
Related concepts
Starting and running replication
Forcing a failover
Replication and security
Replication failure handling