The blobcollector endpoint provides the possibility to suspend the deletion of unused blobs at runtime. This is a required step for the backup of custom blob stores, as described in the section "Backup Strategy" of the Content Server Manual. Alternatively, blob deletion can be suspended with configuration property sql.store.collector.suspend but that requires a restart of the Content Server.

Endpoint properties. 

management.endpoint.blobcollector.access=unrestricted

Endpoint URL. 

http://localhost:8081/actuator/blobcollector

When requested using a GET HTTP request, the endpoint will respond with the current state of the blob collector. It returns true for the key "suspend", if blob deletion is currently suspended or was requested to suspend.

Response. 

{
  "suspend": false
}

To suspend blob deletion, send a POST request with "suspend": true to the endpoint:

Suspend blob deletion. 

curl -X POST -H "Content-Type: application/json" \
     -d '{"suspend": true}' \
     http://localhost:8081/actuator/blobcollector

To resume blob deletion, send a POST request with "suspend": false to the endpoint:

Resume blob deletion. 

curl -X POST -H "Content-Type: application/json" \
     -d '{"suspend": false}' \
     http://localhost:8081/actuator/blobcollector