Many things could be happening.

How do you cleanup journal files? Purge after so many backups? Are your backup working?

You could look in a journal file and see what global data is causing the expansion.

If you have the system management portal you can look at journal data there too.

You might need to go to the application vendor to tell what data a global holds.

Will Cache and other older version docs be put on here?

Roger is correct. I wonder if the error is controllable though through the cpf.

The rules on global names - linked to the temporary doc location -

http://dreamymclean.intersystems.skytapdns.com:52773/csp/docbook/Doc.View.cls?KEY=GGBL_structure

You could try to compact and truncate.

Dmitry's idea will also work and be faster.

I think the WRC would be the only ones who could tell you what could be moved into CACHETEMP unless you found someone else  who they had told already.

If you just don't want to store so many journals you could just backup multiple times a day and do a journal purge.

Congratulations on using Ensemble to the point you have this problem.

Yes, the instances interconnect and share files.

Death to extents :)

I work in Unix where LVM and mount points would make this easy but it looks like Windows has mount points.

Windows mount point