• 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.

Data / Domain / Email Migration from Plesk 7.0.4 to 7.5.4

J

joinindia

Basic Pleskian
Hello,


I want to know any simple step by step instructions how to Migrate Data/Email/Domain/database/user id & passwords from Old Server which is working on
Plesk 7.0.4 + Linux Redhat ES3 to the New Server Plesk 7.5.4 + Linux Redhat ES4 ?
 
Originally posted by joinindia
Hello,


I want to know any simple step by step instructions how to Migrate Data/Email/Domain/database/user id & passwords from Old Server which is working on
Plesk 7.0.4 + Linux Redhat ES3 to the New Server Plesk 7.5.4 + Linux Redhat ES4 ?
Click to expand...

They are in official documentation
 
Plesk Migration Manager

Hello,

Any Comments/Problems/precaution using Plesk Migration Manager ?

Is it Safe to Migrate using Plesk Migration Manager?

I have followed below steps;

1. Upload migration agent. For Plesk it is /usr/local/psa/PMM/PleskX.pl somewhere on the source server.
2. Run it with --help option to get information how to use this script.
3. Then copy the files from ./pma directory from the source server to /usr/local/psa/PMM/archives on the

destination Plesk.
4. Copy PleskX.xml to /usr/local/psa/PMM/var on the destination server and rename it to dump.xml.

Confirm is it SAFE to use Step 5. for Final Migration to New Server ?

5. Then you can migrate data via Plesk on Server->Migration page in "Import mode".
 
Re: Plesk Migration Manager

Originally posted by joinindia
Hello,

Any Comments/Problems/precaution using Plesk Migration Manager ?

Is it Safe to Migrate using Plesk Migration Manager?

I have followed below steps;

1. Upload migration agent. For Plesk it is /usr/local/psa/PMM/PleskX.pl somewhere on the source server.
2. Run it with --help option to get information how to use this script.
3. Then copy the files from ./pma directory from the source server to /usr/local/psa/PMM/archives on the

destination Plesk.
4. Copy PleskX.xml to /usr/local/psa/PMM/var on the destination server and rename it to dump.xml.

Confirm is it SAFE to use Step 5. for Final Migration to New Server ?

5. Then you can migrate data via Plesk on Server->Migration page in "Import mode".
Click to expand...

AFAIK, there is no cases when something went wrong with final case: it only creates new objects, not touching existing.

And, you need not only PleskX.xml, but also other files in the directory: those which are archives with .tar.gz.aa and similar. They are need to be copied to /usr/local/psa/PMM/archives

Those files contain all content of your old server: httpdocs, mail, ftp content and so on.
 
Error in Plesk Migration

Hello,

I did the same way you mentioned, I tried doing 1 domain and got Error Report as below, Please Guide me how to Resolve these Errors.

---------------------------------------------------------------------------------------
Data migration from host localhost has been successfully completed.

DetailsCan not deploy web-content of domain Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.html.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/httpdocs'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy ssl-content of domain Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.shtml.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/httpsdocs'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy cgi-content of domain Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.cgi.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/cgi-bin'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy webstat content of domain Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.webstat.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/statistics/webstat'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy webstat content of domain Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.webstat-ssl.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/statistics/webstat-ssl'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy user private data of user onlinesms@Domain.Com
Execution of the following utility failed:
cat -- '//Domain.Com.private.tar.gz'.?? | tar xvfz - -C '/var/www/vhosts/Domain.Com/private'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Can not deploy mail content of admin@Domain.Com
Execution of the following utility failed:
cat -- '//admin@Domain.Com.mdir.tar.gz'.?? | tar xvfz - -C '/var/qmail/mailnames/Domain.Com/admin/Maildir'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Unable to unpack mail attachments for Domain.Com on domain admin@Domain.Com
Execution of the following utility failed:
cat -- '//admin@Domain.Com.attach.tar.gz'.?? | tar xvfz - -C '/usr/local/psa/tmp/Domain.Com/admin@Domain.Com'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Execution of '/usr/local/psa/bin/autoresponder.sh' '-a' '-mail' 'admin@Domain.Com' '-files'

'add:/usr/local/psa/tmp/Domain.Com/admin@Domain.Com/0' failed with the return code 1.
STDOUT:

STDERR:
Can't add file "/usr/local/psa/tmp/Domain.Com/admin@Domain.Com/0" to attachments repository: Can't read the file.


Execution of '/usr/local/psa/bin/spamassassin.sh' '--update' 'admin@Domain.Com' '-status' 'true' '-hits' '3' '-action'

'mark' '-modify-subj' 'true' '-modify-subj-text' '****SPAM****' failed with the return code 1.
STDOUT:

STDERR:
Unable update spam assassin setting for mail name "admin@Domain.Com": SpamAssassin is not supported by the license key


Can not deploy mail content of info@Domain.Com
Execution of the following utility failed:
cat -- '//info@Domain.Com.mdir.tar.gz'.?? | tar xvfz - -C '/var/qmail/mailnames/Domain.Com/info/Maildir'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Unable to unpack mail attachments for Domain.Com on domain info@Domain.Com
Execution of the following utility failed:
cat -- '//info@Domain.Com.attach.tar.gz'.?? | tar xvfz - -C '/usr/local/psa/tmp/Domain.Com/info@Domain.Com'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Execution of '/usr/local/psa/bin/autoresponder.sh' '-a' '-mail' 'info@Domain.Com' '-files'

'add:/usr/local/psa/tmp/Domain.Com/info@Domain.Com/0' failed with the return code 1.
STDOUT:

STDERR:
Can't add file "/usr/local/psa/tmp/Domain.Com/info@Domain.Com/0" to attachments repository: Can't read the file.


Can not deploy mail content of support@Domain.Com
Execution of the following utility failed:
cat -- '//support@Domain.Com.mdir.tar.gz'.?? | tar xvfz - -C '/var/qmail/mailnames/Domain.Com/support/Maildir'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Unable to unpack mail attachments for Domain.Com on domain support@Domain.Com
Execution of the following utility failed:
cat -- '//support@Domain.Com.attach.tar.gz'.?? | tar xvfz - -C '/usr/local/psa/tmp/Domain.Com/support@Domain.Com'
The return code was

The output on STDOUT was:


The output on STDERR was:
2

Execution of '/usr/local/psa/bin/autoresponder.sh' '-a' '-mail' 'support@Domain.Com' '-files'

'add:/usr/local/psa/tmp/Domain.Com/support@Domain.Com/0' failed with the return code 1.
STDOUT:

STDERR:
Can't add file "/usr/local/psa/tmp/Domain.Com/support@Domain.Com/0" to attachments repository: Can't read the file.


Execution of '/usr/local/psa/bin/spamassassin.sh' '--update' 'support@Domain.Com' '-status' 'true' '-hits' '3' '-action'

'mark' '-modify-subj' 'true' '-modify-subj-text' '****SPAM****' failed with the return code 1.
STDOUT:

STDERR:
Unable update spam assassin setting for mail name "support@Domain.Com": SpamAssassin is not supported by the license key


Execution of '/usr/local/psa/bin/dns.sh' '--add' 'Domain.Com' '-cname' 'ftp' '-canonical' 'Domain.Com.' failed with the

return code 1.
STDOUT:

STDERR:
Unable add record in DNS server: Unable to insert new DNS record: Unable to resolve the canonical name Domain.Com.


Execution of '/usr/local/psa/bin/dns.sh' '--add' 'Domain.Com' '-cname' 'www' '-canonical' 'Domain.Com.' failed with the

return code 1.
STDOUT:

STDERR:
Unable add record in DNS server: Unable to insert new DNS record: Unable to resolve the canonical name Domain.Com.


---------------------------------------------------------------------------------------

Kindly instruct how to resolve step by step the above Errors.
 
You must log in or register to reply here.

Similar threads

S
Resolved Error migrating tool
Replies
6
Views
614
SalvadorS
S
B
Question Migration data from Horde to SOGo extension
Replies
4
Views
757
bit
B
M
Resolved SSH type seems disallowed on migration from WHM to Plesk
Replies
1
Views
217
MHC_1
M
K
Question Plesk Migrator
Replies
5
Views
953
scsa20
scsa20
S
Issue Migration Error: from Obsidian 18.0.34 Update #2 to Obsidian 18.0.66
Replies
2
Views
603
Vladimir C.
V
Back
Top