I have a problem
First my old hosting uses CWP panel and when I got a new hosting uses cPanel and WHM.
I did a full backup from CWP panel
And when I try to restore either from cPanel or WHM via cpmove I got error and I don’t know to to migrate from my old host to a new host
Note: my old host has application of e-commerce Opencart with MySQL database
It’s my first time to migrate from my old hosting to the new hosting and I did research through web and YouTube without any luck to fix my problem.
Thank you all.
Restoring through WHM cpmove
Restoring through cPanel
Related
A client has a live website with data and he just want to upgrade the website design, without effecting the live data. He asked me to build website on a local server or a a different instance on same hosting and then shift that design to the live instance.
With Odoo you can build the website as an own extensions and build all the content / design part with the xml/qweb templates. So yes, you build up the extension and then just upload this extension on the server and install it there.
I currently have a dedicated server running the following:
Apache/2.2.32
WHM/CPanel 11.44.3 (build 5)
MySQL Server version: 5.5.40-cll
Because of a security with the version of Cpanel I am told by my hosting company that Cpanel requires an update. The issue they have is because the current Cpanel is version 11.44.3 they can not update to the latest version.
Question, has anyone else had this issue and if so what was if any the resolution.
Many thanks in advance for your time
The hosting company are telling me that the only way around this issue is to have a completely new server configured with all the latest Apache, WHM/CPanel.
This of course would require all the scripts for our web site been transferred to the new server.
You have too old version and to avoid possible issues and downtime, it is recommended to setup and new server with CentOS 7 and latest cPanel and then migrate account one by one. This will allow you to check your websites one by one as you migrate. You should be able to generate full account backup and then you can restore it on a new server.
There is possibility to upgrade the version on your existing server but it is possible that it may cause other issues and you may face lots of issues and downtime.
We have plesk hosting account now we want to migrate to cpanel,approx 5gb mail data in plesk account how to direct transfer Email data from plesk to cpanel.
You can migrate whole account through cPanel migration tool
OR
You can submit migration requesto to cPanel support team. They will help you on this. Here are the some useful information about this.
https://documentation.cpanel.net/display/CKB/cPanel+Migration+Services+and+Guides
Does anyone know of any reputable online service that can do WHM/Cpanel to WHM/Cpanel migrations from one host to another. Currently the new host I am using does not support transfer feature with WHM.
I cannot do a backup and upload via FTP since the data amounts to about 25GB and I have a 1Mbps connection. That would take ages to download and then upload.
Kindly help
I used a high speed VPS service from DigitalOcean and set up an Ubuntu Virtual Machine. From there, did a backup of my cpanel accounts and downloaded them onto the VM. Uploaded the files to my new host. It took me less than 4 hours to transfer 25GB!!
Cpanel/WHM does provides whm to whm migration, which you can use. as you have mention you have whm to whm migration whichmeans you should be owning the VPS or dedicated. Most of the companies now a days offers Free data migration services which you can use.
This will not only save your time but money too as creating the VPS just to download and upload the data on new server is not affordable.
You can connect WHM to WHM backup transfer using backup utility at whm as shown below :
Home »
Transfers »
Copy an Account From Another Server With an Account Password
I suggest you to use whm panel transfer tool option because it will reduce time,bandwidth usage.
Follow the below steps
1.Login into new server WHM panel
2.open a transfer tool option
Transfer tool :
Remote server ip address:Existing server ip
Remote SSH port:Existing server SSH port no
Authentication Login:
Select Root option (default)
Authentication method
Password:Existing server password
4.Click Fetch Account List
5.After existing server account list and package list will be displayed
6.Select account which you want to migrate and complete the process.
I had a SharePoint server, now i want to move this from one machine to another machine.
This is what i did for the migration.
I have just installed sharepoint server in my new machine and i have removed the Sharepoint_config and wss_content databased from the new server. and i have restored both the databases from the old server. Then i tried to run the Central Admin and i got Unable to connect to content database error.
Is replacing the DB is wrong. is there any other way to migrate SP server from one machine to another. I have tried my taking Farm backup and restore i had many problem with that. so i feel replacing DB would be better for me. any suggestions please?
Move SharePoint between servers is a huge effort.
Data in databases are very depends on the SharePoint install and its environments. So, I suggest just re-install the SharePoint on the new server, and then restore site collection backups to the new install.
Install SharePoint Server on the new server machine
Backup site collections from the old server, follow this guide: http://technet.microsoft.com/en-us/library/cc263441(v=office.12).aspx
Create Web Applications on the new server
Restore site collections from the prev. backups, follow this guide: http://technet.microsoft.com/en-us/library/cc262087(v=office.12).aspx
Be aware, if you have farm level customize solutions (developed by Visual Studio) or css files deployed in the LAYOUT folder, don't forget to re-deploy them on the new server.
I guess this question is too old and my answer will not help topicstarter... However, I was looking to refresh my own knowledge on this topic and I feel it will be useful to share it here.
This solution is not good for every SharePoint deployments, of course, it's just a general idea.
And I don't think it suits production environments well... but if you are brave and foolish as myself, you can do it there as well, with some additional precautions like backups and so on.
Here are prerequisites:
SharePoint was initially installed in Farm mode (not in Single Server mode)
Both old and new servers are in the same domain
You know Farm Passphrase used for initial installation
Old server is still intact and accessible from the new server
Steps to do
Skip steps 2-6 if you don't want to move databases to new location
Install SharePoint on the new server and join to existing farm. See
https://technet.microsoft.com/en-us/library/cc261752.aspx for details on joining procedure.
Ensure that the SharePoint is read-only. You can just shut down MS SQL DBEngine service if it's ok for your users.
Install MSSQL Server on the new server or other location you want. Remember, that it's not a good idea to keep SharePoint and MSSQL on the same server if it's not a demo/dev environment
Move all SharePoint databases to the new MSSQL Server. You can simply copy all DB files and attach it to the new SQL, or go full backup and restore way.
Important: Create an SQL client alias on the new server with cliconfg tool. See blogs.msdn.com/b/priyo/archive/2013/09/13/sql-alias-for-sharepoint.aspx for details.
Use your old SQL instance name as alias name. E.g. if your old server had SQL installed alongside with SharePoint on SharePoint.mydomain.com, alias name should be "SharePoint.mydomain.com"
Set Server name for alias to the new SQL location. Something like "NewServer.mydomain.com"
Ensure that you specify correct port number for SQL connection or configure network for default dynamic port. It is not necessary only if you have local SQL server on the same machine.
Create identical SQL client alias on the old server (this is needed to correctly remove old server from farm)
Remove old server from the farm. See this technet article for details
Update DNS settings or whatever you use to point users to the new server.
That's it. Hope it will help someone