Skip to main content

Keeping Disk Usage Low

Generally, we recommend using Cleanup Policies and the Admin - Compact blob store task to keep disk usage low. However, this page details several other items for when policies are not enough.


If Cleanup Policies are not meeting your needs, you may need to use the existing tasks. See the FAQ section of Cleanup Policies for more about what Cleanup Policies cover and what needs Tasks used instead.


Like Cleanup, these tasks soft delete and the Admin - Compact blob storetask is needed after to actually free your disk space.

For More Complex Cleanup Scenarios

For scenarios the policies and tasks don't cover with their provided variables, we suggest using the REST API to find and delete what you need via REST call.

For example, if you'd like to delete all components named alpha, you can perform the following curl to identify them:

curl -X GET "http://localhost:8081/service/rest/v1/search?name=alpha" -H "accept: application/json"

Depending on your results, you can then call individual deletes or design a script to remove them all. Example of what a delete curl might look like:

curl -X DELETE "http://localhost:8081/service/rest/v1/components/bWF2ZW4tcmVsZWFzZXM6ODg0OTFjZDFkMTg1ZGQxMzgwYjA3YWQzNDAwOGVmNTc" -H "accept: application/json"

Examining Blobstore Space Usage

If you would like more insight into how blobstore space is being consumed to make better informed configuration decisions, you can run groovy scripts either from the command line or from within NXRM using the Execute Script task. This Knowledge Base article provides samples to get you started.

Totally Out of Space / Seeing Errors?

If you are currently out of disk space, there are a couple of other Knowledge Base articles you can look at to free up space urgently and get the system up and running:

What to Do When the Database is Out of Disk Space

What to Do When the Blob Store is Out of Disk Space