The backup should include all databases owned by the user, assuming you chose to backup the databases. I don’t know of any reason it wouldn’t…we’d need to see errors, probably. I kinda assume something went wrong during the backup, and if so, there’d be some kind of error.
Are you sure the missing database is owned by the domain owner, though?
This isn’t about how WordPress works, it’s about how VMin and also Virtual Server Transfer ignores any database other than the one it initially created.
Also, using your favourite tool doesn’t also move things like Users, emails etc to another server all in one go, just Wordpress - which I can also do quite happily with eg Duplicator and probably a few other tools.
Virtualmin is an amazing tool for making server admin so easy, I am simply offering my observations that may allow it to be improved, and hopefully with enough details to make my observations useful.
That seems wrong. A database created as part of an Install Script is also owned by the domain owner user by default, and should be associated with the domain…so, if you can’t see it in the “Edit Databases” page, something happened to disassociate it, and that explains why it is not included in the backup.
If you can see it in the Edit Databases page, then we’re still in the dark about why it isn’t in the backup.
Then it’s been disassociated from the domain. Obviously Virtualmin won’t backup databases that don’t belong to the domain (that’d be a huge security concern).
You want to use the Import tab in Edit Databases for the domain to bring it back in (I’m noticing that’s a poorly named tab…there are two meanings for “import” when it comes to databases, and I can see how it might not be obvious that import in this context would mean “make an existing database owned by this domain”).
On the backup form you can choose which features to backup.