The other way is to create a copy of existing data and update the data-path in the Trainz Settings on the Install tab.
--- Copy TRS19 Plus/SP4 and call it TRS22 Beta.
--- Replicate the data folder. Call it TRS22_TEST
--- Update the copied program. I recommend using the Patch installer directly rather than using the updater through the Launcher.
--- Choose TRS19 Plus Beta as the source.
--- Install, and repeat the same again for the second part.
--- Start up TRS22.
--- At the Launcher, click on Trainz Settings.
--- Click on Install tab.
--- Click on the three dots on the right. (...)
--- Browse to TRS22_TEST
--- Click on it.
--- Click Select.
In the Internet tab, your login will populate since it's picking up your login information from your TRS19 database
Your program will run a quick "updating translations", or something like that and will want to restart.
--- Restart as required.
The program will now run a DBR. This process can take a very long time if you have a lot of data. The progress bar will appear to be hung during the checking faulty assets stage. It is not stuck, it's a known bug with the progress bar showing one value, but the process is not completed.
Once done, check in Content Manage to ensure your content is intact, and most importantly check for faulty assets. If there are any faulty assets, select them, right-click choose View errors and warnings. Most of the errors should disappear, and if there are any remaining, you need to delete, replace, or repair the faulty content.
With this replicated setup, you can now compare operations between your TRS19 and TRS22. This is very helpful when problems appear unique to TRS22, but may have existed before but went unnoticed, or not.