Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !
WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure. Join the pilot program today!
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
Most likely these are some kind of temporary data, or a cache, or huge logs. You need to find the reason for this. Believe me, it is very difficult to do this in the scope of clairvoyance in the format of a forum discussion.
The comment made by @IgorG is right: it is hard to make a guess if sufficient information is absent.
Nevertheless, it is very likely that you have a number of backup processes that consume a lot of disk space.
This could (but not necessarily will) explain the problem you face.
One can specify a threshold of disk space at which Plesk will not start with backups.
For instance, just go to "Tools & Settings > Backup Manager" and
- make sure that you have specificied an appropriate (relatively high) value at "Start the backup only if your server has the specified amount of free disk space"
- make sure that you have checked the "Start the backup only if your server has the sufficient amount of free disk space" checkbox
and also note that issues with backup processes are often associated with high CPU usage: keep check of the CPU usage!
In addition, have a look at all cache or temporary files and directories: just start with inspection of /tmp, /var/tmp, /opt/psa/tmp and /var/lib/psa/dumps.