Varying-Vagrant-Vagrants / VVV

An open source Vagrant configuration for developing with WordPress
https://varyingvagrantvagrants.org
MIT License
4.54k stars 848 forks source link

Q: database backup and restore #2611

Closed JairoJL closed 2 years ago

JairoJL commented 2 years ago

I am trying to update to new version of vagrant like from 2 to 3 but i read it requires like the update that removes everything. is there instructions on how to back up my sites cause i read you need to backup database but i cant find anywhere how and what the command to backup and then restore is i would really like to know! thanks in advance!

welcome[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/

VVV
VVV Slack Workspace
Join the VVV Slack Workspace
Mte90 commented 2 years ago

So you have an old VVV version or vagrant? I think that in VVV 2 there was already the backup script for the database and that on halt it was generating them.

Otherwsie you can do the old school way, open phpmyadmin and export manually the various databases.

JairoJL commented 2 years ago

So how do i import them back after updating to vvv 3? After the whole like removing it to update? Does it auto bring the database or do i have to go in phpadmin and import them?

Mte90 commented 2 years ago

After updating you need to do a provision so the DB will be created and import again in phpmyadmin.

I don't know what is the VVV version are you using, but consider that VVV has an automatic DB export on halt and on provision if the DB doesn't exists will import them.

JairoJL commented 2 years ago

when i try to update to new version and do get pull it gives me error that i cant connect to it image

tomjn commented 2 years ago

when i try to update to new version and do get pull it gives me error that i cant connect to it

@JairoJL we don't maintain git or github.com, so there's very little if anything at all that can be done from the VVV end to resolve this. It's likely an issue with your local git setup, such as a bad SSH key, firewall and security software, or a very very out of date copy of git

tomjn commented 2 years ago

As for the database, stop thinking of VVV as some special case that requires special steps to do this.

If you were moving a site from GoDaddy to WPEngine you would do exactly the same steps. Export the database, then take that export and import it. There are hundreds of ways to do this, plugins, scripts, tools, manual instructions, etc.

The only difference is that the server you're exporting from isn't miles away in a data centre, it's in front of you. If you need DB access details there's a copy of PHPMyAdmin and direct SQL client details in the VVV docs

JairoJL commented 2 years ago

okay thank you ive managed to get throught these things but my problem now is when i try provisioning it gives me this error image

JairoJL commented 2 years ago

and i tried searching it but i cant get anywhere with how to fix this

tomjn commented 2 years ago

Your screenshot cuts off most of the error but it’s something that was fixed in VVV 3.9, you need to use the latest stable or develop branches

On Sat, 11 Jun 2022 at 01:46, Titan @.***> wrote:

and i tried searching it but i cant get anywhere with how to fix this

— Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2611#issuecomment-1152785316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZZMNJH4WOFWZR43FSDVOPAU3ANCNFSM5YLTL4BQ . You are receiving this because you commented.Message ID: @.***>

tomjn commented 2 years ago

Closing this as there's been no response in several months. Feel free to reopen if you encounter this again though