I would like to inform you about the planned migration of your shared hosting account to a new hosting environment. This concerns the domain xx***********. The migration will start on: 29-10-2009 during business hours.
Due to a problem with the restoration of the backup on the newermachine, we did not succeed in the transfer of your domain. So for now it will stay on the 'older' webshared enviroment. Are you OK with us to give it another run tomorrow? Please indicate a No in case this is inconvinient to you, if there is noanswer we assume that there is not a problem and we will work on thetransder again tomorrow.
Dear Customer, The transfer of your webpackage to one of our new shared hosting servershas been completed.
Now my Oscommerce site is down: Parse error: syntax error, unexpected ';' in /vhosts/xxx***********/httpdocs/catalog/index.php on line 314
I checked line 314 of index.php does not have ';' My site admin side is working.
I Foolishly entrusted a server migration to seeksadmin recently... however they seem unable to provide the required level of support to complete this task... Up to now the average response time per query is between 12 to 24 hours... amazing as we have paid for one hour response package.
We have a small window of opportunity to complete a seemless migration tonight... but again seeksadmin are nowhere to be seen...
We have coordinated with our datacentre and informed our customers that the move will take place tonight, however seeksadmin are either asleep or just can't be bothered to respond... which leaves us with no other option than to try and locate an alternative support company to assist with this migration...
All accounts are copied... it is just a case of hardening the server and installing third party softwares, ensuring all data is up to date and addressing any issues which may arise...
Can anyone suggest a tech/support company who can help out at short notice? Migration will start at CET 01:00 and needs to be completed during the night before my users come back online in the morning...
I migrated my server on friday, and I changed the IP address of my DNS. There are still a few customers accessing the old server. What can I do? Is it possible to flush some persistent DNS cache somewhere?
I have recently migrated to new server with Plesk 12. There was a webalizer even I used to have awstat. So I installed awstat and changed it in the settings. But every day when I synchronized the abonnement it changed alone back to Webalizer ... which I dont want
When I tried to deactivate or deinstall Webalizer in plesk using the update manager, I got an error:
"Some errors occured during installation."
Solved, changed settings in Customer Service Plan and synchronized...
I just signed up for dedicated server at Softlayer with cPanel, mySQL and CentOS. I'm moving a site that is on a VPS with WHM. I know that cPanel has a transfer site feature.
I was considering hiring a service to migrate my site and to harden my server. Is this necessary or should I simply move it via cPanel? Things are tight and I don't want to incur an unnecessary cost if I don't have to. I defer to the members here at WHT for your recommendations.
I have a new Server (CentOS Linux 7.1.1503) and will migrate the Data from my old Server (Ubuntu 14.04 LTS) with the Migration Manager. Both Servers running with Plesk 12.0.18
After i entered the Server-IP and the Login-Data for the old Server i became this Error on the new Server:
Fehler: launchpad error (Error code = 2): == STDERR ==================== Cannot request remote agent status using command line /var/cache/20150518173107557/PleskX.pl: UNIVERSAL->import is deprecated and will be removed in a future perl at (eval 25) line 3. UNIVERSAL->import is deprecated and will be removed in a future perl at IPC/Run.pm line 1060. UNIVERSAL->import is deprecated and will be removed in a future perl at IPC/Run/IO.pm line 78. UNIVERSAL->import is deprecated and will be removed in a future perl at IPC/Run/Timer.pm line 161. Died at AgentConfig.pm line 23. ==============================Click to expand...
I have upgraded to a new server and need to move all domains, users, and most important all email accounts to the new server.
Both servers run Plesk 11.0.9 on CentOS. The migration manager works great, no problems with that.
After migrating, I change my DNS settings at an external DNS provider to the new IP. The problem is, DNS changes take time. I then get emails on the old server and on the new server until DNS information is spread.
I was searching for a way to let the old server forward to the new one, but changes for specific domains in plesks DNS system (MX record) on the old server did not work. The mails still arrived at the old server.
What can i do? Can I uncheck "Activate mail service on domain" and will all emails be rejected until DNS points to the new server? Or will that lead to bounces?
After a server migration, some critical Plesk settings were not copied across, even though the option to backup/restore panel configuration was used. e.g.
skeleton (vhosts.skel folder) php.ini (Program Files (x86)ParallelsPleskAdditionalPleskPHP5* folder) Default site (vhostsdefault folder) health config (Program Files (x86)ParallelsPleskadminconfcustom-health-config.xml) Additional Administrator accounts
Is there a way to get these things to backup and restore that I am doing wrong?
Are there other important settings/data that I have missed from that list? I am still paying to keep the old server in case I discover something else!
Using Plesk Backup & Restore for disaster recovery will lose these settings unless they take extra steps. e.g. I now have a simple batch file that copies these files to a private folder on one of the domains before the daily backup kicks in.
I'm migrating from Plesk 9.5 to 11 and I'm getting the following on my Transfer Pre-Check from within the Migration Manager."The destination DNS server does not support networks in the Transfer Restrictions Template, but some subscriptions have networks in DNS transfer restrictions. The records with network IP addresses in the DNS transfer restrictions will not be restored."
I've gone to Server, DNS Settings, Transfer Restriction Template and added the new server's IP to the list of allowed networks to no avail. I also couldn't find any documentation on what the cause might be.
We are migrating an existing multi-site Windows2003/IIS6 web hosting system with
CFusion8 MS Access backend databases SQL2000 backend databases http and https site access
Windows2012 R2/IIS8.5 with CFusion10 MS Access backend databases (not updated) SQL2014 databases http and https site access
On the new system we are looking to add Plesk12 to give users easier management of their own websites.I am about to install the trail version of Plesk12 WebHOST.I have the following questions:
1. Can we use the plesk migration tool to move the websites from the old IIS6 to the new IIS8.5 server? 2. If not, am I right to think we would migrate from IIS6 to IIS8.5 manually and then import these websites into Plesk12 from the new server? 3. Can I migrate the existing websites piecemeal over onto the new server and into the Plesk control panel at the same time as creating brand new websites under the control panel? 4. Once Plesk is installed on the new IIS server is there a KB article on how to add all these existing websites to Plesk - I could not find one. 5. Is the local windows administrator account used for the install used to run any services?
We have 2 servers SQL, Web & SM 4.x each with and have about 40 sites and we wish to migrate them to Virtual sever for the ease of management & some cost saving. We are thinking of taking good configuration box with Win2k8 server and planning to run VMs over Hyper-V.
I've been getting frustrated with my hosting provider, and after doing application development and sysadmin for a while now, I'm ready to have a go at doing it all myself on a VM. I plan on migrating my site to the new server and when everything is set up, pointing my domain to the new name servers...
My question is - what's the best order to do things to minimize downtime? Can I set up email, MySQL, Apache, DNS etc before I have the domain pointing at the new server, while still being able to test adequately? Would I just set up the services and test them using the IP, then once I'm happy with everything, setup DNS, point domain at new nameservers, then change all configs to use the domain name rather than the IP? In theory if it email etc works with the IP, then the name server change shouldn't matter because it will resolve to the IP...