![]() You might need to export your WordPress database for other scenarios as well, not just as a backup in case something goes bad. So, it’s critical to either back up your entire WordPress site, or, at the very least, back up your database. If something bad happens to your WordPress website – like getting hacked and losing your data – and you don’t have the database backed up, then your website is gone forever. It stores your content, users, settings, URLs, and more. That would simplify things.The database is the most important part of a WordPress website. One thing I want to try is creating a cPanel backup as root, and seeing if it will migrate into Virtualmin using the root password. ![]() (I changed it about seven years ago.) So he shouldn’t be a problem. He’s been a client for… I’d say 15 years off the top of my head, and he doesn’t even know the cPanel password. I also have another client who’s on his own cPanel server, which needs both the OS upgrade and a storage upgrade (unless we farm out the mail). A few of them do, but most of them just bother me to do the stuff they should be doing. Almost none of them ever actually log in to cPanel. If I don’t tell them, most of them probably won’t even notice. I’m actually thinking about spinning up a server and installing Virtualmin Pro on it, then migrating the cPanel clients a few at a time without telling them. I did have a problem restoring a database-driven Virtualmin site, but then I tried again a few days later and it worked. I’ve had no problems migrating database-driven cPanel sites. It probably would take less time than writing a script to do it. I can re-create the filters easily enough, I suppose. As with most things, cPanel has their own way of doing things rather than using a stock Procmail or Sieve method. That’s actually one of the things I’m trying to figure out how to convert and migrate. Those were live migrations, some database driven, others not.Īll of the cPanel sites I’ve tried migrating on my testing server have also been automatic, with the only exception being that the mail filters seem to disappear. Not that I remember how, mind you, but I did it somehow or another. I had one minor one due to the way cPanel divides Awstats records into SSL and non-SSL, which really only mattered for historical reasons but it was pretty easy to fix. I really haven’t had any serious problems moving sites from cPanel to Virtualmin. ![]() Likewise, there is another error with the migration of the email accounts, it does not migrate the passwords, nor does it connect the accounts with the corresponding mailboxes, but that would be the subject of another post. So at this moment I have to conclude that a cPanel → VM migration is not automatic and that it requires prior preparation. Many of the links mentioned or that I found had neither my OS version nor were they similar to my case: cPanel-> VM, but different script-> VM, VM-> VM, DB-> DB.I myself have had to make manual corrections for the migration to work as recommended in many posts.It is said that the problem is MySQL 8, if so, why doesn’t the documentation mention it? ( Virtualmin for cPanel Users | Virtualmin) as it implies that the process should run without problems.Let’s see, I’ve been using Google since its invention … and yes, I did some research before coming here and creating a new thread. If I had been given $ 0.01 for every smart answer I have received right now I would be a billionaire … ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |