Hello Indy,
An in‑place upgrade of a Domain Controller from Windows Server 2016 to 2019 is technically supported, but it carries risk and is not the recommended approach. Microsoft’s best practice is always to stand up a new DC, transfer FSMO roles, and demote the old one, but since you don’t have the storage capacity, you’ll need to prepare carefully. Before starting, ensure the 2016 DC is fully patched, run adprep /forestprep and adprep /domainprep from the 2019 media, and confirm replication health with dcdiag and repadmin /replsummary. Disable or remove any third‑party agents that hook into AD or the file system, as they often break upgrades. Make sure SYSVOL is healthy and using DFSR replication, not FRS, since FRS is deprecated and will block the upgrade. Finally, take a full system backup and snapshot if possible, because if the upgrade fails, rollback is the only recovery path. With those checks complete, you can proceed with the in‑place upgrade, but be aware that any corruption in AD or replication issues will be magnified during the process.
You can refer to this article: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers