I found out what happened...
I have a software installed on the server called MemCached. Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering. Basically, it speeds up how the data is produced from the server to the browser.
The problem. The config file that the forum software uses, I then program with the memcached databased to achieve the above. When I installed the test upgrade for combatptsd.org, being a different domain and contained within a completely different area of the server, because memcached was configured in its config file also, memcached became a link between two databases that could never physically have linked otherwise. This is how installing one forum in a test environment overwrote parts of the ptsdforum.org database, thus created the issue.
As I stated, I wasn't performing any type of maintenance or task on this forum, because when I do, I also do a then and there backup to ensure data isn't lost. Basically, a configuration on another domain intertwined itself with this forums database via an independent piece of software installed on the server, hence why I had to revert back to the last days database backup, hence the loss of 22 hrs data.
Basically, to use memcached on two forum residing on the same server, the use of a prefix must be used to uniquely identify each database memcached use so that the software doesn't attempt to intertwine databases again.
I know a lot of that sounds jiberish to many, though atleast I found out. A user on vbulletin called Cellarius actually identified the problem.