July 15, 2013 at 6:39 am #9338avd23Spectator
I searched for this but did not find any posts. Is there an easy way to back up all the settings I have set up and the database of members to move them to a new server. I have checked out PHP MY Admin but I have about 70 databases on the server and I do not see how to identify which one is for EMember. I also do not see any information about whether or not it contains all the settings for a move. I did find this link
but it does not describe whether all the settings are included in the database and how to identify the database. Any information is appreciated.
eStore v 6.9.3July 15, 2013 at 2:54 pm #56617wzpModerator
You don’t have 70 databases; you have one WordPress database, with 70 tables in it. That tells me you might have great difficulties following the procedures, outlined in the video.
Will the new server have the same domain name? If the new server will have the same domain, you might be able to “get away” with a wholesale backup and restore of the entire database.
Otherwise, unless you have hundreds of products and members, to justify the effort; I sense you may find it easier to simply redo your settings.
This article on how to move a WordPress blog to a new host might be helpful:July 16, 2013 at 5:49 am #56618avd23Spectator
I’m sorry, but you misunderstood. Within my CPanel I have 70 individual databases as I have a lot of wordpress sites in my account. What I was trying to indicate was what would be the easiest way to find the emember database without having to check all the databases.
I was hoping that EMember had a backup feature built into the software that would backup all the settings and all the members and allow me to download to a local server for safe keeping and to move the members.
Thanks for the link. It will be helpful.July 16, 2013 at 2:18 pm #56619wzpModerator
Each of your 70 WordPress sites has only one database. Within each database are many tables. Some tables are for WordPress itself, others are for the plugins. Copying just the tables from one database to another doesn’t always work. This thread illustrates that even after copying the eMember tables from one database to another, minor “tweaks,” in the form of table column editing, are often required.
If you are going to create many sites, perhaps you can do what large IT departments do; create a generic site image (directories and database), with all the settings the way you like them, and just load the generic image onto your servers.
On the other hand, if you are just trying to backup your sites, then making a backup of each entire database is the best approach.
- You must be logged in to reply to this topic.