Bobcares

DirectAdmin to DirectAdmin migration – How to do it

by | Nov 3, 2021

Wondering how to perform DirectAdmin to DirectAdmin migration? We can help you.

As part of our Server Management Services, we assist our customers with several cPanel queries.

Today, let us see how our Support techs proceed to perform it.

 

How to perform DirectAdmin to DirectAdmin migration?

Today, let us see the steps followed by our Support Techs for the migratin.

Step 1:

Firstly, DirectAdmin needs to install on the new server.

For licenses with support, open a ticket to request a free temporary migration license.

For licenses out of support please purchase a license at your own expense, and cancel it when the migration is finished.

Once the migration is complete, request removal of the new license and then put the new server IP address into your original license.

Then it can done in your Client Account Area.

Step 2:

For each IP that you are using on the old server, you’ll need to add new IP’s to the new server.

Then, plan out which IP’s will match up.

Then, go to Admin Panel -> IP Manager on the new server, and add all of the IP’s.

You can change the IP assignment of the user when doing the transfer.

Eg: If they are currently on an owned IP address, it’s quite easy to transfer everyone to a shared IP address.

So If you don’t have as many IP’s, that’s not a problem.

Similarly, you can add users to owned IP’s if they were shared on the old server.

Step 3:

For each Admin/Reseller account on the old system, they will have to be create through DA the usual way on the new system.

If the User backup files of the Reseller/Admin were just restored, their account would be created as a user.

This is why their account needs to be first created.

Once each Reseller/Admin are created, go to Admin Panel -> IP Manager and assign each one whichever IP’s they’ll need to be using.

Step 4:

On the old server, for each Admin/Reseller, login as them, and go to their Reseller Panel -> Manage User Backups.

Select all accounts, and make a local backup of those accounts.

We recommend doing a local backup and then transferring the files over to the new server by hand.

You can try to use the ftp feature to upload to the same Admin Reseller on the new server, but you’ll have to make sure the firewalls are setup correctly first.

When uploading the backup files to the new server, place them in /home/reseller/user_backups.

Where reseller is the name of the admin/reseller who owns those accounts (including his own personal file).

Make sure that the user_backups directory is owned by that admin/reseller and that the backup files in that directory are chmod to 755.

The newer alternative for the Reseller Level Backups is Admin Level -> Admin Backups/Transfers.

Then, restore the Admins and Resellers first.

Step 5:

On the new server, for each Admin/Reseller.

Firstly, login and go to Reseller Panel -> Manage User backups. For all accounts shown in the list, restore them.

If you are assigning different users to different IP addresses, you’ll have to do 1 restore per IP with which ever user(s) you are restoring.

Eg: if 5 users are going to 1 shared IP, select those 5 users, select the shared IP and restore them.

If you are restoring 1 user to his own shared IP, he’ll have to restore by himself without any other users.

Repeat the restore process for all users until complete.

When restoring Admin/Reseller user accounts, the IP selection doesn’t matter as their user account is already create.

Step 6:

Finally, the restore process for Reseller Level settings will have to copy manually.

To copy the Reseller’s pacakges over, copy the contents of /usr/local/directadmin/data/users/reseller/packages/* and /usr/local/directadmin/data/users/reseller/packages.list over to the new server with the same settings.

The reseller will also have to setup any nameserver settings again.

Then, make sure that the default nameservers are set in the Reseller Panel -> Nameservers before restoring the users.

[Stuck in between? We’d be glad to assist you]

Conclusion

In short, today we saw steps followed by our Support Techs to perform DirectAdmin to DirectAdmin migration.

 

 

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF