Difference between revisions of "PSA migration"
| Line 18: | Line 18: | ||
1 New Plesk Server | 1 New Plesk Server | ||
| − | + | ||
'''Step 1) Back up the system''' | '''Step 1) Back up the system''' | ||
| Line 34: | Line 34: | ||
Mailman will send out notifications to everyone when you migrate, block this short term with firewall rules: | Mailman will send out notifications to everyone when you migrate, block this short term with firewall rules: | ||
| − | iptables -I OUTPUT -p tcp --dport 25 -j DROP | + | iptables -I OUTPUT -p tcp --dport 25 -j DROP |
| + | iptables -I OUTPUT -p tcp --dport 465 -j DROP | ||
| + | |||
Revision as of 13:09, 4 June 2007
Abstract:
Safely migrating Plesk, in the event of an ISP change, hardware or OS upgrade involves the use of multiple systems. This procedure applies to you if:
You are running an End of Lifed (EOL) unsupported operating system like RH9, FC1, FC2, FC3, FC4 or FC5
You need to upgrade hardware
You are moving to a different hosting company
You have a badly laid out file system
Prereqs:
1 Plesk Server
1 New Plesk Server
Step 1) Back up the system
Step X) Plesk Restore
Task 1) Prep
/usr/local/psa/bin/pleskrestore --create-map backup -map map
Task 2) Restore
/usr/local/psa/bin/pleskrestore --restore backup -level all -map map
Step X) Surpress email notifications from mailman
Mailman will send out notifications to everyone when you migrate, block this short term with firewall rules:
iptables -I OUTPUT -p tcp --dport 25 -j DROP iptables -I OUTPUT -p tcp --dport 465 -j DROP
Step X) Testing Checklists
mailing lists
webmail
Web
websites (test for php issues, register_globals)
DNS
did all domains transfer?
