@dan_ce , there are basically three (maybe four ) databases/locations that contain what you need,
A) Voicemail and recordings , are all in /var/spool/asterisk/* and /etc/asterisk/voicemail.conf
B) The current state of the machine , CF’s DND’s etc in /var/lib/asterisk/astdb-sqlite3
C) Most of the rest in the mysql/mariadb databases ‘asterisk’ and ‘asteriskcdrdb’
D) any customization you did in /etc/asterisk/*.conf , sorry you are on your own here
If you can reconstruct exactly what you had when it broke, then with asterisk and mysql stopped, you quite likely could restore the asterisk’s sqlite3 database and the /var/lib/mysql/asterisk* directory structures to the new machine if they are ‘un-corrupted’. If needed, repairing the mysql databases is usually quite easy. A broken sqlite3 data base is best recovered by just deleting it and letting Asterisk rebuild it, that sometimes needs a little attention to each ‘endpoint’ to re-sync it’s state with FreePBX’s database view which can’t do the CF/DND kinda stuff cos it’s dynamic.
As to wasting your time, I offer a counter argument,
Raspberry Pi 4 estimated cost of power per month is 30cents
Cost of 2G pI4 with case and psu plus SD approx $70
Learning how to not write logs to the SD = $0 + 20 minutes.
Break-even point Hardware vs. a VM with backups , about 1 year.
Residual value after that year, Vultr/DO = $0, PI hardware invested in including knowledge gained = $70 * 0.9 (ok, add depreciation ) + lots .
QED , You are neither wasting time nor money, you are gaining lots of ‘value added’ stuff. Many folks (myself included) have PI 2’s running for years under sinks and in broom closets without a problem,. almost all failures are either writing logs to the SD , so don’t, or losing power unexpectedly, a $15 usb power bank makes a very effective UPS for PI’s for that one.
Of course ‘off hardware’ backups are highly recommended also.