exchange 2016 is running out of space

@Edward: You are welcome, thank you for sharing us the valuable knowledge :)

I hope you will have more in future, not only Exchange but also other products, such as Sharepoint,...

@DP230, I am working on a few things which i hopefully can publish soon. Sharing is caring :-)

I don't know, how can I find out?

I figured out the problem, just not sure how to fix it.   So for some reason, my logs are not be truncated, since March of this year, everyday, another log file is added, and when I do my exhange backups, whether using Arcserve or the Windows backup, as I did both, the logs are not truncated.
I checked the vssadmin writers, and the exchange writer is not there.  i have restarted the server and even made a registry change, but still doesn't work, the exchange writer is not there.

Any idea's how I can get the exchange writer installed?

Thanks guys for your help.

@Dan: you need to restart service Exchange Replication or restart server to bring back the vss exchange writer

Did you miss any configuration in Backup server, so that the log cannot be truncated?

DP320
I have restarted the server numerous times, the service does not come back.  I tried Arcserve and the built in Windows backup server, so both missconfigured is rare.  I even had Arcserve support log into my PC and tried different things, and the tech said it's MS's fault, as there's no Exchange writer.

You would have to recreate the Writer. you can also use vsstester script from here:

https://blogs.technet.microsoft.com/exchange/2016/07/28/vsstester-script-updated-troubleshoot-exchange-2013-2010-and-2016-database-backups/

Also if the writer is missing and you have not set these Registry  entries you should

https://vox.veritas.com/t5/Backup-Recovery-Community-Blog/vssadmin-Microsoft-Exchange-Writer-is-Missing/ba-p/779343

if it is there and still nothing, please check application event viewer and look for vss errors warnings or something which indicates an issue. If these is still nothing, you may want to disable backup and check if the writer appears, sometimes it is missing due to a third party app.

Also if nothing else helps enable circular logging for the database. this will temporary save you some space.

So I had already tried the registry fix, but that didn't work, did numerous server restarts, and still didn't work.

run the vsstester script and if you get things created, then you should contact support of the backup tool:

https://blogs.technet.microsoft.com/exchange/2016/07/28/vsstester-script-updated-troubleshoot-exchange-2013-2010-and-2016-database-backups/

do you know if it can be run in production, will it take down any services, etc....