Been using DirectAdmin for years now, and always used the process described here to migrate users to newer servers as older servers got retired. I don't like endlessly upgrading DirectAdmin servers through new Debian releases, CustomBuilds etc - I prefer migrating them empty when EOL to a newer server.
But that article, from 2008, describes a cumbersome process which could easily be automated. Since server migrations always have a DirectAdmin server at both ends, it would be easy to have a separate server transfer screen at admin/reseller level (or included in existing backup/transfer screens) automatically performing:
I currently have a Debian 6 DirectAdmin server with PHP 5.3 entering end of life, and I'd estimate the described feature would save me over 80% in workload on the final migrations.
As a bonus feature, I would LOVE (caps and bold intended) to be able to automate this automation via the remote API, so our internal systems, integrated with our own DNS system (we don't use DirectAdmin's DNS facilities as we require more redundancy) can automatically:
But that article, from 2008, describes a cumbersome process which could easily be automated. Since server migrations always have a DirectAdmin server at both ends, it would be easy to have a separate server transfer screen at admin/reseller level (or included in existing backup/transfer screens) automatically performing:
- Backup at first location
- FTP transfer to second location
- Restore at second location
- Cleanup of backup files
I currently have a Debian 6 DirectAdmin server with PHP 5.3 entering end of life, and I'd estimate the described feature would save me over 80% in workload on the final migrations.
As a bonus feature, I would LOVE (caps and bold intended) to be able to automate this automation via the remote API, so our internal systems, integrated with our own DNS system (we don't use DirectAdmin's DNS facilities as we require more redundancy) can automatically:
- Download list of domains from user on server A
- Verify we have control over all of them, and determine longest TTL
- Set all TTLs to lowest value, and sleep until longest TTL has expired
- Transfer account from A to B
- Set all external DNS records to new IP and raise TTL
- Delete original user a week later unless intervened