• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Corrupt dump.xml file causing migration failure

K

kkaos

Guest
Hello,

I have been unable to perform a migration from a Linux Plesk 8.1 server without complete failure. I noticed that the dump.xml file that's being created on this server during the migration contains numerous weird ^@ characters, mainly in the limit values (i.e. <limit_name="disk_space">). There are way too many of these characters for me to vi into the file and remove manually; neither the sed tool nor the search utility in vi can find these characters (i.e. searching for ^@ in vi doesn't work) in order to perform an automated replace.

How can I either fix this or work around? I appreciate any guidance offered.

Thanks,


Sean
 
Faris,

Thanks for you response; however, I tried using single quotes and double quotes, but sed won't find the ^@ characters.
 
Back
Top