Hi folks, As a server admin we’ve to handle multiple servers with control panel and without it. DirectAdmin is also one among the popular control panel in the web-hosting industry with its default port 2222. Most of all server admins will be familiar with cPanel migration, here I’m explaining the detailed steps for DirectAdmin to DirectAdmin migration.
It’s also very easy. As in cPanel transfer tool there’s no such option to do DirectAdmin to DirectAdmin migration. This can be achieved by following the steps given below. For simplicity I’ll give you step by step instructions:
Step 1: Skip home directory from backup
Log into your source server via SSH and with your favorite editor say vi or nano, take /usr/local/directadmin/conf/directadmin.conf. Set/add skip_domains_in_backups=1 in it. This will prevent copying Home directory while taking backups.
# grep skip_domains_in_backups /usr/local/directadmin/conf/directadmin.conf
skip_domains_in_backups=1
Step 2: Creating backup on source server
Access source server’s DirectAdmin panel. Navigate to Admin tools >> Admin Backup/Transfer. Select all users (if you need to migrate all users or else select the user you need) and then click on “now” to take the backup at that instant. By default the backups will be copied to the location /home/admin/admin_backups locally (which means on the source server itself). Then select all the data to be copied and then click on submit.
All the backups will create in the location /home/admin/admin_backups of the source server.
Simple way to configure DirectAdmin Backup
DirectAdmin Backup Manager : Where you can manage your DirectAdmin account backup painlessly!!
It’s an awesome plugin developed by ModMaster. By using DirectAdmin Backup Manager plugin, your backup and restore works should be pain less. Everyone can manage this plugin simply. Read more..
Step 3: Syncing backup to destination server
Now we need to copy the backups from the source server to destination server. For that we can use rsync command. Here’s a sample command. You can use according to your preference.
P.S Run rsync on screen
# rsync -avz --progress -e ssh /home/admin/admin_backups/ root@destination_server_ip:/home/admin/admin_backups/
This will copy all the backups over to your destination server’s /home/admin/admin_backups/ location.
Step 4: Restoring backup
Now access your destination server’s DirectAdmin panel.
>> Navigate to Admin tools >> Admin Backup/Transfer.
>> “From Where” select local /home/admin/admin_backups
>> “Select IP” Use the IP from the list and select the shared IP of the server or if you need to use a dedicated IP, use the one that you prefer.
>> Select the backup files
>> Click on submit.
All your selected backups will restore to the new server. Monitor the restoration process using ps (about ps command usage) or top (more about top command).
Step 5: Rsync the home folders.
When the restoration completes, we can proceed with the rsync of home folders. Here’s an example command to be executed from the source server:
# rsync -avz --progress -e ssh /home/ root@destination_server_ip:/home/
That’s it!!
Important log file paths for Directadmin server
DirectAdmin is one of the commonly using web hosting control panels available now. It is an easy to use control panel.
It is an extremely efficient control panel that uses the bare minimum of system resources.
This makes DirectAdmin ideal for systems ranging from low-end VPS units to heavily-loaded dedicated servers.
It is a completely stand-alone control panel. Administrators are free to upgrade/downgrade services, libraries, etc. without fear of breaking the control panel.
Please remember about set_permissions.sh script
Why not just send all backup with FTP to the destination server, and restore them there with the new IP?
sometime it gives error during such transfer, rsync is a good option
will this backup emails also?
thanks for the explanation
Hello
After I followed it, I can do it. But I have a doubt that Why all moved domains Not showing the number on the reseller’s name
Thank you
I use directslave for dns clustering, after restoring was completed dns record in directslave was not updated to destination_server_ip.