I understand...If your files are lost... you are going to have issues (a prime reason to do a full file and DB backup regularly).
Your files (unless you are using R2 or similar) also consist of any images, avatars, logos, attachments, etc. that have been uploaded and add-ons that were installed.
You can upload the XF files again, then manually install all the add-ons (by extracting and placing them in the appropriate directory) and then importing your DB again... but as for getting back to where you were, without a backup of all the files... you are pretty much toasted. You will have missing images in posts if they were attached, no users will have their avatars and such.
Not cleanly (nor easily) as you had to get those in via an import and XF does it's "magic" on the vB stuff as it imports (renames them to XF structure, creates the necessary linked data, etc).How can I partially restore attachments and avatars?
/data
and your internal_data
(this may not be needed) should get your old image attachments back but you will still be missing many (a years worth).via the config file should suffice.How do I disable all installed plugins? Is it done through the configuration file or via MySQL?
$config['enableListeners'] = false;
You can disable through MySQL, I’ve done it with some bad or buggy addons that caused errors on the admin CP.I understand...
I have a file system backup from a year ago before migrating from vBulletin. + XF mysql.
How can I partially restore attachments and avatars?
What changes occur with avatars and attachments in the process? Can I replicate them manually?
How do I disable all installed plugins? Is it done through the configuration file or via MySQL?
It will be functional... just a LOT of work to try to replace images... and a lot of "dead" attachments that will have to be cleaned up.You’ll have to deal with missing avatars and attachments after, but I think majority of the forum will be functional.
I plan it this way:
I'm setting up a clean forum with a 2023 database.
On another server, I'm initiating the conversion from VB 2022 to "XF 2022".
And copy attachments and avatars from "XF 2022" to XF 2023
I'm sorry, I didn't understand.If you have the database, upload it online, install a new forum and import the forum as a new firum
I want to install the same set of plugins on an empty forum that I had before. This way, after connecting the new database, the plugin files will already be in the system. How can I see in the MySQL database which plugins and their versions were installed before the crash?If it were me, I'd:
1. Copy the old Xenforo to a temporary location on the host.
2. Install the newest Xenforo database you have.
3. With a freshly installed empty Xenforo, import the database from step 2, using the attachment/avatar file locations from step 1. Retain content ids when importing.
4. You'll end up with a working Xenforo that has the same URLs as before, with attachments and avatars except for those from the past year.
If the old drive is still available, I've rescued data from Linux file systems before. This includes one case where a hacker had deleted all the database files. Most were recoverable, and thankfully those lost were small tables not required to rebuild a new Xenforo installation.
The forum was running on a virtual server image. Due to an unexpected server reboot, possibly caused by a power outage, a failure occurred. There was no way to recover the image (and its copy) using any means.The more important question is how was the data lost from a drive failure, did your host not have backups?
If your host was a "responsible" host.. they should have been regularly imaging their VM's and when they had a hardware failure, they should have restored from that.... sounds more like an "oh ****, we lost the drives, time to burn the VM setup back out and then have all our users start over from scratch".Due to an unexpected server reboot, possibly caused by a power outage, a failure occurred. There was no way to recover the image (and its copy) using any means.
I am buying a server on Hetzner without administration, and I am responsible for the administration myself.If your host was a "responsible" host.. they should have been regularly imaging their VM's and when they had a hardware failure, they should have restored from that.... sounds more like an "oh ****, we lost the drives, time to burn the VM setup back out and then have all our users start over from scratch".
Even when I was running ProxMox on my own dedicated server, I was smart enough to back up the VM's for the eventual "oh crap" scenario.... and that was 1/2 a decade ago.
I run on Hetzner currently on a 4vCPU/8GB/160GB shared instance.I am buying a server on Hetzner without administration, and I am responsible for the administration myself.
The backup scheme was taken from here "Backup VM without downtime"
https://b14esh.com/virtualization/kvm/backup-vm-qemu-kvm-libvirt.html.
However, it turned out to have significant shortcomings
The files were corrupted. After converting from qcow2 to raw, it was possible to partially access the file system. However, only a very small portion of the files could be retrieved...
In addition to what I described above, I do everything exactly the same as you. Thanks to this, I still have the file system for 2022 and a new database left. I forgot to specify the new address of the forum in rsyncI run on Hetzner currently on a 4vCPU/8GB/160GB shared instance.
I have ZERO issues with my backup process. I have a script that runs daily via CRON that dumps the DB and backs it all up... then I have another process on my local Mac desktop that uses Transmit to pull the files in from the server. I then also have a process that uses rsynch to synchronize to another server I have access to via the internet.
I use the same script for several different sites.. it dumps the DB into the local vhost location, then backs up those physical files... then transmits them.. then deletes the server based SQL dump (but not the server based backup). I keep 14 days of backups avaialble.
That's why I use two different destination locations and method of deliverability... and update them on any server move immediately.I forgot to specify the new address of the forum in rsync
We use essential cookies to make this site work, and optional cookies to enhance your experience.