-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.10.2 update question #25
Comments
one other thing, how do we restore a previous backed up database? thanks |
If you want permalinks for every match you would need to reimport. The restore tool hasn't been tested much and can only be used via command line, I just tested it however and it doesn't work atm. |
Ok turns out I was being stupid and forgot a step, after you create a backup you need to copy all the files from inside the .zip file and place them into the restore-from folder, then run node testrestore in the main directory, I forgot the restore-from bit and that's why it was spitting out loads of mysql errors as the backup was from an old version. Also note you can only restore the backup to the same version it was from, you can not restore for example v2.9.x to v.2.10.0, I've not got round to making the admin UI for restoring, and to be honest was surprised that it still works. |
after this update, should we reload all logs in order to get the new permalink hash for matches? how important is that?
thanks you one more time for you amazing work!
The text was updated successfully, but these errors were encountered: