I installed Vestaccp on my VPS (CentOS 6.9) and it was working perfectly.
Today, by mistake I installed VestaCP again on the same server because I was thinking I was installing on my different VPS. Therefore I installed VestaCP twice on the server.
As a result, all of my websites running on my old vestaCP went down and I'm not even able to get their database dump coz everything is written by new installation.
New VestaCP placed files and database of old vestacp installation on following locations those I can copy easily but I can't use those databases anymore
Old VestaCP current path[Files of websites]:
/root/vst_install_backups/1526175423/home/web/
Old VestaCP Database current path:
/root/vst_install_backups/1526175423/mysql/mysql_datadir
Currently I can't even get database dump of my old vestacp because of new installation.
Please guide me how can I database dump of my old working websites so I can use them to rum my websites back.
Looking for kind response.
I'm sorry that I couldn't ask you any questions, I do not yet have the ability to comment.
Now, if you've created your databases one by one in VestaCP (not clicked on the phpmyadmin link) you may be in luck.
I.e. not on http://EXAMPLE.COM/phpmyadmin/, but rather at https://EXAMPLE.COM:8083/list/db/.
If you SSH into your VPS and do a ls /backup do you have any files there?
Mine reports the following:
admin.2018-05-17_05-12-25.tar
admin.2018-05-18_05-12-31.tar
admin.2018-05-19_05-12-38.tar
These are the default backups that Vesta runs every day. They include database dumps that are GZipped and safe to import into a clean load.
The downside to these backups is that it will only keep 3 at once (unless you tell it otherwise), and personally, I think daily is too frequently for full backups.
If you'd like to change the amount of backups that it keeps, head to Packages > Default > Edit. Scroll down near the bottom of the page and you're looking for "Backups". Bear in mind the more backups you let sit there, the less disk space you'll have. And if you run out of disk space, usually your mysql-server is the first to spit the dummy, as it cannot write any temp files.
One thing I am unclear about is if Vesta has a retention policy, and if so, how long it holds on to them. Because my webserver running Vesta has been up since April 2017, and my last 3 backups are 17th, 18th, and 19th of May.
