That’s cutting it close. Would be better if you can free up additional space, just to be safe.
During the process, the -wal file will grow to the size of the bloated db file, so you need enough room for both. If it is also the boot drive, then you’ll need whatever working room the OS needs.
Once the process is finished, the db file will be back to normal and the -wal file will still be bloated. Stop Plex Media Server and the -wal file should go away. When you re-start PMS, the -wal file will return at its normal size.
I do not know of a way to tell when the weekly database optimization will run.
That’s the advantage of using WebTools-NG - you get to say when it starts.
Plex has not backed up the db since May 21.
The bloat problem started with the 1.41.7 beta releases, so whenever you loaded one of the affected releases is when the bloat began.
Given the dates, the problem was probably bad enough by May 24 that the backup failed.
