Cool script for migrating cpanel servers
Pullsync is a cool migration script for cPanel servers.
Migrate a single cPanel account, from a user list, a domain list, or all users, to another cPanel server. Update/final syncs, too.
Shows updating status of parallel processes:
Bonus features:
The script will only run on cPanel servers, and will only migrate from cPanel servers, both of which must be RHEL variants (CloudLinux, AlmaLinux, CentOS, Oracle, Rocky, etc). You must have direct root-level SSH access available to both servers.
The script has been tested as far back as CentOS 4 for source, but newer features have not been fully verified against this. RHEL 7, 8, and 9 targets are supported (though RHEL 7 itself is beyond EOL and may not supported for much longer…)
The script also assumes that you have packaged and restored cPanel accounts and websites manually in the past, as, in essence, this is a bash script you downloaded from the internet, and you should treat it as such. It may fail, and you will have to pick up the pieces.
The script utilizes the following additional standalone systems, and may redistribute precompiled versions simply for ease of installation:
Pullsync is run from the TARGET of your migration as ROOT. You will also need ROOT SSH access to your source server.
Set up your userlist at /root/userlist.txt with space or newline separated cpanel usernames. If migrating all users, skip this step.
If you need to exclude files or databases, set up the appropriate files at /root/rsync_exclude.txt and /root/db_exclude.txt, otherwise you can skip this step, too.
Finally, download and execute the script AS ROOT:
wget -O /root/pullsync.sh https://raw.githubusercontent.com/ch604/pullsync/master/pullsync.sh && chmod 700 /root/pullsync.sh
bash /root/pullsync.sh
Pullsync will install its own prerequisites (jq, whois, parallel, etc) if needed, and download its supporting files from this repo. It will restart itself in screen if necessary, and present a user-friendly menu to proceed from there.
Pullsync writes its temporary files and logs to /home/temp/pullsync/, which is a symlink to a directory in /home/temp/ suffixed with the start time. Some important files to consider:
/pullsync.log #all script output is stored here/error.log #important errors are logged here/log/dbsync.log #this is the output from a mysql-only or final sync/log/*.${user}.log #each user's tasks are logged in these files, there is a looplog, a pkgacct, a restorepkg, and an rsync log.
The pullsync directory is stuffed with all kinds of other output as well, including /reply_url, a copy of the url with testing output, /dns.txt, a summary of DNS resolution, and /ticketnote.txt, a summary of the changes pullsync attempted to make. Additional files will be called out during the script that the technician performing the migration should pay attention to.
Copies of several key files from the source server are also copied into this directory for reference before, during, and after the migration, such as /etc/wwwacct.conf, /var/cpanel/users/, and /etc/ips, among others.
Finally, there is an eternal history file at /root/migration.log, showing what accounts were operated on at what times, and where you can get more details.
You already know how to migrate and can fix it, right? ….right?
Bugs or feature requests can be reported on this repository. If you have used pullsync, drop me a line! I’d like to know your experience with it!
