As a Server Administrator, I want the ability to clone a cPanel server to a new setup, so that deployment of new servers is simplified and quicker.
Cloning should include:
Cloning should explicitly exclude:
This is a feature that has been migrated over from the cPanel Forums. All previous comments and discussions concerning this feature can be located at:http://forums.cpanel.net/f145/clone-server-configuration-144297.html
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
I like this idea 
This is available in cPanel & WHM version 56. You can read about it here:
https://documentation.cpanel.net/display/ALD/Transfer+Tool#TransferTool-ServiceConfigurations
Comments are now locked, but if you require any assistance you can open a ticket with our support team, email me (benny@cpanel.net) or ask me on twitter (@cpaneldev).
This is available in cPanel & WHM version 56. You can read about it here:
https://documentation.cpanel.net/display/ALD/Transfer+Tool#TransferTool-ServiceConfigurations
Comments are now locked, but if you require any assistance you can open a ticket with our support team, email me (benny@cpanel.net) or ask me on twitter (@cpaneldev).
This would be awesome, something like cluster-settings where you add the key from the servers that you want to be equally setup and also this way you avoid mistakes or forgetting to enable/disable something.
This would be awesome, something like cluster-settings where you add the key from the servers that you want to be equally setup and also this way you avoid mistakes or forgetting to enable/disable something.
This is currently do-able in sort of a manual fashion but the issue is that with each revision of cPanel, the files that store this various information change so much that you have to test and make sure it's working each time you run it on a new version.
I believe the ability to deploy to 11.30 where you could automate configuration, and then run /scripts/upcp was designed to help with this - but an ability to deploy a 'template' of a server would be great.
Something that is probably seen as a separate request, is if cPanel stored all of it's data in a centralized location (i.e. /usr/local/cpanel for example) versus all over the file system as it does now - this feature request would be much easier to make as you wouldn't need to know what files are handled where all over the file system to make a template.
This is currently do-able in sort of a manual fashion but the issue is that with each revision of cPanel, the files that store this various information change so much that you have to test and make sure it's working each time you run it on a new version.
I believe the ability to deploy to 11.30 where you could automate configuration, and then run /scripts/upcp was designed to help with this - but an ability to deploy a 'template' of a server would be great.
Something that is probably seen as a separate request, is if cPanel stored all of it's data in a centralized location (i.e. /usr/local/cpanel for example) versus all over the file system as it does now - this feature request would be much easier to make as you wouldn't need to know what files are handled where all over the file system to make a template.
This would be great, would be nice to see a CLI script for it as well.
This would be great, would be nice to see a CLI script for it as well.
it` will be easyer then like now to copy config files ...
it` will be easyer then like now to copy config files ...
This would be great.
This would be great.
I would love to have this feature! ;-)
I would love to have this feature! ;-)
This would save us many hours for each new server that is setup. This would be great to see.
This would save us many hours for each new server that is setup. This would be great to see.
second that
second that
Is there any way of gauging what the current progress is on actually implementing this AWESOME feature request?
Is there any way of gauging what the current progress is on actually implementing this AWESOME feature request?
A ready to clone configs zip based on specific version of OS and cPanel coul be run on every system/cPanel update. A script to import, check, deploy would make the work and warnings.
A ready to clone configs zip based on specific version of OS and cPanel coul be run on every system/cPanel update. A script to import, check, deploy would make the work and warnings.
mega future! Waiting very very
mega future! Waiting very very
How about just a simple "export settings" feature?
(And of course, a corresponding "import settings" utility...)
For version compatability, just check to make sure that export/import servers are the same version, and do not allow import if not.
How about just a simple "export settings" feature?
(And of course, a corresponding "import settings" utility...)
For version compatability, just check to make sure that export/import servers are the same version, and do not allow import if not.
is just "ok" so long as it does not require download and upload of
configuration files to/from the admin's PC then back to the desired server. The idea is to keep this
communication between the servers.
Also it's not been mentioned here (unless its been forked into 2 separate feature requests), but in the original feature request for this, part of this system was to be so that settings can be replicated to other servers in real
time, not just during setup.
For example, say I want to update the contact email address on the main server and have that same setting replicated to all of the servers configured in the "settings cluster." I don't want to manually import or export in any
fashion because that would actually take longer than logging into WHM
and just changing it in tweak settings on every server.
is just "ok" so long as it does not require download and upload of
configuration files to/from the admin's PC then back to the desired server. The idea is to keep this
communication between the servers.
Also it's not been mentioned here (unless its been forked into 2 separate feature requests), but in the original feature request for this, part of this system was to be so that settings can be replicated to other servers in real
time, not just during setup.
For example, say I want to update the contact email address on the main server and have that same setting replicated to all of the servers configured in the "settings cluster." I don't want to manually import or export in any
fashion because that would actually take longer than logging into WHM
and just changing it in tweak settings on every server.
If they add an export/import configuration capabilty into the WHM api.. then it would be a very simple matter to automate this from any server.
Want your server to sync configuration to/from another server? Easy. Just setup a simple api call and run it via cron.
Want to setup a new server using config from another server? Easy. Just click the "get config from server" button, enter the desired server and api authentication details, and poof! Done.
Best of both worlds if they do import/export using an API.
If they add an export/import configuration capabilty into the WHM api.. then it would be a very simple matter to automate this from any server.
Want your server to sync configuration to/from another server? Easy. Just setup a simple api call and run it via cron.
Want to setup a new server using config from another server? Easy. Just click the "get config from server" button, enter the desired server and api authentication details, and poof! Done.
Best of both worlds if they do import/export using an API.
Can we get an e.t.a. from the devs please?
Can we get an e.t.a. from the devs please?
is much better use the time of Employees in make other features, like security, more tools for email, antispam or integration with IPv6
is much better use the time of Employees in make other features, like security, more tools for email, antispam or integration with IPv6
se the time of Employees in make other features, like security, more tools for email, antispam or integration with IPv6
se the time of Employees in make other features, like security, more tools for email, antispam or integration with IPv6
Ye we all want it. Be a good feature. Shave a few hours off when deploying new servers.
Ye we all want it. Be a good feature. Shave a few hours off when deploying new servers.
clone - export - ... or a BACKUP/RESTORE?
This SHOULD be a feature.
clone - export - ... or a BACKUP/RESTORE?
This SHOULD be a feature.
Would this be the same as allowing mutliple users for one cpanel, to allow a user with limited access?
Would this be the same as allowing mutliple users for one cpanel, to allow a user with limited access?
If this is too big of a feature, then starting with multiple Cpanel users for each account that can be limited to access would solve the problem.
If this is too big of a feature, then starting with multiple Cpanel users for each account that can be limited to access would solve the problem.
From experience we have upgraded for almost a decade and I can tell you that recently found a Apache bug that was a setting from 3 servers ago and didn't work with the current server.
My suggestion is to NOT copy the files that do the setting but sorta Pre-fill the settings on the new server and let it set itself up fresh with all you settings in place.
I would at first go one step at a time. Have the servers talk to each other and place a "COPY SETTINGS FROM" feature on each WHM page. Would be faster than it is today and would give a baby step to prevent copying bad/old configurations.
From experience we have upgraded for almost a decade and I can tell you that recently found a Apache bug that was a setting from 3 servers ago and didn't work with the current server.
My suggestion is to NOT copy the files that do the setting but sorta Pre-fill the settings on the new server and let it set itself up fresh with all you settings in place.
I would at first go one step at a time. Have the servers talk to each other and place a "COPY SETTINGS FROM" feature on each WHM page. Would be faster than it is today and would give a baby step to prevent copying bad/old configurations.
Yes... This option will be great to clone cpanel... Otherwise... we are doing it manually.
Yes... This option will be great to clone cpanel... Otherwise... we are doing it manually.
but for time being isnt there any manual way to do this? I want to migrate all DNS zones also to new server along with all sites and other settings.
but for time being isnt there any manual way to do this? I want to migrate all DNS zones also to new server along with all sites and other settings.
If this is too big of a feature, then starting with multiple Cpanel
users for each account that can be limited to access would solve the
problem.
My suggestion is to NOT copy the files that do the setting but sorta
Pre-fill the settings on the new server and let it set itself up fresh
with all you settings in place.
If this is too big of a feature, then starting with multiple Cpanel
users for each account that can be limited to access would solve the
problem.
My suggestion is to NOT copy the files that do the setting but sorta
Pre-fill the settings on the new server and let it set itself up fresh
with all you settings in place.
Some of this functionality can already be accomplished with cpconftool. We will be improving this tool and providing additional modules for this system in the future.
Some of this functionality can already be accomplished with cpconftool. We will be improving this tool and providing additional modules for this system in the future.
Personally I'd like to see EasyApache and PHP settings, Nameserver selection and IMAP/POP server selection included as well.
Personally I'd like to see EasyApache and PHP settings, Nameserver selection and IMAP/POP server selection included as well.
That's awesome Nick, we are super happy to see some progress here. looks like exim and tweak settings are the first modules which have been deployed.
What kind of feedback are you specifically requesting from us? More module suggestions, testing or something else?
That's awesome Nick, we are super happy to see some progress here. looks like exim and tweak settings are the first modules which have been deployed.
What kind of feedback are you specifically requesting from us? More module suggestions, testing or something else?
I second this. I've already missed several tweaks and config options when deployong cpanel servers and having to setup everything again with every new server it's honestly ANNOYING. You can spend easily one full afternoon in setting up things. Multiply that if you need to enable several servers. It's a pain in the *** :(
I second this. I've already missed several tweaks and config options when deployong cpanel servers and having to setup everything again with every new server it's honestly ANNOYING. You can spend easily one full afternoon in setting up things. Multiply that if you need to enable several servers. It's a pain in the *** :(
I'm pretty sure that using the same cluster capabilities of the DNS's it's possible to maintain a cpconftool like feature in sync with all the others.
I'm pretty sure that using the same cluster capabilities of the DNS's it's possible to maintain a cpconftool like feature in sync with all the others.
I would be fantastic an import export of configuration...
I would be fantastic an import export of configuration...
It would be of great help. An addition would be that such changes to be forwarded to clustered server, like if I enable something in Tweak Settings, it should be enabled on all servers in cluster.
It would be of great help. An addition would be that such changes to be forwarded to clustered server, like if I enable something in Tweak Settings, it should be enabled on all servers in cluster.
Have used one of my precious votes to support this feature request. Would save me a lot of time.
Have used one of my precious votes to support this feature request. Would save me a lot of time.
Same
tool (import/export accounts) should be very useful in WHN not only on cPanel!
Sometimes new servers/providers are extremely necessary and re-setup a new server
with same accounts, e-mails and etc... is frustrating sometimes. We as an
technician loses a lots of time setting up this things.
Same
tool (import/export accounts) should be very useful in WHN not only on cPanel!
Sometimes new servers/providers are extremely necessary and re-setup a new server
with same accounts, e-mails and etc... is frustrating sometimes. We as an
technician loses a lots of time setting up this things.
Very much looking forward to the replies on this.
Very much looking forward to the replies on this.
This is such a needed feature that I often wonder why it is not there already.
Each migration or server hardware upgrade would result in us saving hours upon hours of work and painstakingly check things manually.
+1 for this indeed!
This is such a needed feature that I often wonder why it is not there already.
Each migration or server hardware upgrade would result in us saving hours upon hours of work and painstakingly check things manually.
+1 for this indeed!
We think that the ability to Download a configuration file and be able to upload it on other cPanel server would be very useful specially with case like our where we keep very similar setup on each server,
We think that the ability to Download a configuration file and be able to upload it on other cPanel server would be very useful specially with case like our where we keep very similar setup on each server,
It is a good idea and can save time everytime we setup a new server.
It is a good idea and can save time everytime we setup a new server.
+1 Add Branding to the list. We should be able to select transfer/install multiple styles to another server with one click. Not one at time as are currently the case. A fashion similiar to package an account transfers would be nice. A well laid out interface with every custom setting in the same section, allowing us to select multiple/all custom settings would be better. Honestly a premier control panel should already be better in this regard.
+1 Add Branding to the list. We should be able to select transfer/install multiple styles to another server with one click. Not one at time as are currently the case. A fashion similiar to package an account transfers would be nice. A well laid out interface with every custom setting in the same section, allowing us to select multiple/all custom settings would be better. Honestly a premier control panel should already be better in this regard.
This would save time for server admins in setting up new servers.
Have some something like EasyApache but have stored profiles of configurations on a main server so that it only be like a few clicks on the server with going through every setting in WHM which is time consuming.
This would save time for server admins in setting up new servers.
Have some something like EasyApache but have stored profiles of configurations on a main server so that it only be like a few clicks on the server with going through every setting in WHM which is time consuming.
This feature is a must to deploy multiple comparable servers, and it could even serve as a server config comparison tool between machines (like test servers and productions / or even between production servers). With a side by site config comparison.
It should be considered that if this script or configuration should ever exist, that it is a secure way to copy configuration without bringing in problems from a compromised system. If this is done, reloading a new fresh server and moving accounts would take out SO much pain.
+1 to this initiative! :)
This feature is a must to deploy multiple comparable servers, and it could even serve as a server config comparison tool between machines (like test servers and productions / or even between production servers). With a side by site config comparison.
It should be considered that if this script or configuration should ever exist, that it is a secure way to copy configuration without bringing in problems from a compromised system. If this is done, reloading a new fresh server and moving accounts would take out SO much pain.
+1 to this initiative! :)
I suggest combining this feature with "Centralized Server Management"
http://features.cpanel.net/responses/as-a-hosting-provider-i-want-centralized-server-management-so-that-i-can-control-many-servers-from-one-main-server
The idea is: after connecting the slave server to the master server, the admin can with a click clone the configuration to the newly added slave server.
I suggest combining this feature with "Centralized Server Management"
http://features.cpanel.net/responses/as-a-hosting-provider-i-want-centralized-server-management-so-that-i-can-control-many-servers-from-one-main-server
The idea is: after connecting the slave server to the master server, the admin can with a click clone the configuration to the newly added slave server.
I too would be very keen for this feature to be added. I'm going to need to do a migration in a couple of months from a server with quite a few sites that will not work on the latest versions of php etc.
I too would be very keen for this feature to be added. I'm going to need to do a migration in a couple of months from a server with quite a few sites that will not work on the latest versions of php etc.
I too would welcome this feature. It's especially welcome to those not using ESXi free too as we can't migrate/move vm's easily, so it would be helpful to be able to set up a new server with the cpanel centos disk iso, import configurations, then transfer accounts.
This would save a huge amount of time too if a server failed as at the moment it can take a large amount of time to set up WHM/cpanel on a new server before accounts can be imported from remote backup servers.
If we had the option to export all settings, then we could do that weekly, infact if the settings could be saved as part of the nightly backup to a remote server that would be the most perfect solution, I've always wondered why WHM/cpanel configuration is not backed up as it's as important as the accounts.
I too would welcome this feature. It's especially welcome to those not using ESXi free too as we can't migrate/move vm's easily, so it would be helpful to be able to set up a new server with the cpanel centos disk iso, import configurations, then transfer accounts.
This would save a huge amount of time too if a server failed as at the moment it can take a large amount of time to set up WHM/cpanel on a new server before accounts can be imported from remote backup servers.
If we had the option to export all settings, then we could do that weekly, infact if the settings could be saved as part of the nightly backup to a remote server that would be the most perfect solution, I've always wondered why WHM/cpanel configuration is not backed up as it's as important as the accounts.
I tried the mentioned method (partially) to do a clone setup but I ran into very serious and bad problems. many apache/php configuration has set they was never on the other server and I've been forced to (double) check/change every single setting. Waiting for the full (and working) implementation of this feature.
Thanks!
I tried the mentioned method (partially) to do a clone setup but I ran into very serious and bad problems. many apache/php configuration has set they was never on the other server and I've been forced to (double) check/change every single setting. Waiting for the full (and working) implementation of this feature.
Thanks!
I would like a flag that you could use to specify the path in which the file is saved.
I would like a flag that you could use to specify the path in which the file is saved.
Any news about this feature ? I need to clone my primary HD and I would use this.
Any news about this feature ? I need to clone my primary HD and I would use this.
central server management that can be cloned / synced is what everyone wants. Can serve as a hot-backup and allow for growth / migration. would help hosting companies and end users.
central server management that can be cloned / synced is what everyone wants. Can serve as a hot-backup and allow for growth / migration. would help hosting companies and end users.
This would be great, would make adding servers to our hosting business easier!
This would be great, would make adding servers to our hosting business easier!
is configuration clustering the same thing with this ????
is configuration clustering the same thing with this ????
i think it is, they have buit the system required to do this but now need to implement all the configs that need to be backed up. From what I've understood, much like the IPv6 implimentation they will be adding to it with every new version of cpanel to gradually turn it into a complete feature.
i think it is, they have buit the system required to do this but now need to implement all the configs that need to be backed up. From what I've understood, much like the IPv6 implimentation they will be adding to it with every new version of cpanel to gradually turn it into a complete feature.
We think that the ability to Download a configuration file and be able
to upload it on other cPanel server would be very useful specially with
case like our where we keep very similar setup on each server,
We think that the ability to Download a configuration file and be able
to upload it on other cPanel server would be very useful specially with
case like our where we keep very similar setup on each server,
i dont think its gonna happen for the next 2 years,
development seems to go very very slow here....
i dont think its gonna happen for the next 2 years,
development seems to go very very slow here....
this is a really important must-have feautre. +1
this is a really important must-have feautre. +1
This feature is unnecessary and a waste of cPanel development resources. We already accomplish this utilizing other tools. You can do the same by making use of something like Puppet, Chef, Ansible etc. Utilize templates for each configuration file to replace specific lines with server specific settings (hostname, nameservers etc). You can have it deploy once or even have it maintain the configurations and check it every hour. This strategy also has the advantage of maintaining files outside of cPanel control. One such example is making sure certain packages are installed.
This feature is unnecessary and a waste of cPanel development resources. We already accomplish this utilizing other tools. You can do the same by making use of something like Puppet, Chef, Ansible etc. Utilize templates for each configuration file to replace specific lines with server specific settings (hostname, nameservers etc). You can have it deploy once or even have it maintain the configurations and check it every hour. This strategy also has the advantage of maintaining files outside of cPanel control. One such example is making sure certain packages are installed.
Complete restore options would be perfect... Moving servers should not take days to set everything up. Done with a click of a mouse or a couple ssh line commands. Like the idea...
Complete restore options would be perfect... Moving servers should not take days to set everything up. Done with a click of a mouse or a couple ssh line commands. Like the idea...
I don't get it, the highest voted request on the site and it is not even in planned stage, let alone in progress? Come on cPanel, give your users what they are asking for.
I don't get it, the highest voted request on the site and it is not even in planned stage, let alone in progress? Come on cPanel, give your users what they are asking for.
Agreed.. We intentionally hold off on server refreshes due to this. It's a PITA to setup a new server to mirror the settings you had before so that your environment remains stable for customers!
Agreed.. We intentionally hold off on server refreshes due to this. It's a PITA to setup a new server to mirror the settings you had before so that your environment remains stable for customers!
I agree 100%, it's BADLY BADLY needed. Server migrations are always a pain without this feature! C'mon guys... :-)
I agree 100%, it's BADLY BADLY needed. Server migrations are always a pain without this feature! C'mon guys... :-)
I thought that configuration cluster was going to be designed for such feature.
I thought that configuration cluster was going to be designed for such feature.
-- Duplicate Post Deleted --
-- Duplicate Post Deleted --
great that you highlight cpconftool but please be clear what is/is not supported. If you have a step by step guide or partial scrip that would help too.
great that you highlight cpconftool but please be clear what is/is not supported. If you have a step by step guide or partial scrip that would help too.
Yeah, the doc on that script is non-existent or we would try to use it.
Yeah, the doc on that script is non-existent or we would try to use it.
For all those referring to the "cpconftool", while it has no documentation the CLI arguments are pretty clear. Right now it doesn't do a great deal though. All it will do presently is back up your exim configuration and the "tweak settings" configuration page in cPanel. It looks as if it's designed to be modular so we can hopefully expect some additions to this in the future.
The point of this comment though is that right now if you're expecting it to be somewhat useful in cloning a server configuration, it's really not.
For all those referring to the "cpconftool", while it has no documentation the CLI arguments are pretty clear. Right now it doesn't do a great deal though. All it will do presently is back up your exim configuration and the "tweak settings" configuration page in cPanel. It looks as if it's designed to be modular so we can hopefully expect some additions to this in the future.
The point of this comment though is that right now if you're expecting it to be somewhat useful in cloning a server configuration, it's really not.
great that you highlight cpconftool but please be clear what is/is not supported. If you have a step by step guide or partial scrip that would help too.
great that you highlight cpconftool but please be clear what is/is not supported. If you have a step by step guide or partial scrip that would help too.
Why do you keep repeating the same message?
Why do you keep repeating the same message?
may be clone server without emails but with email accounts
for a migration to new server at minimum time
may be clone server without emails but with email accounts
for a migration to new server at minimum time
may be clone server without emails but with email accounts
for a migration to new server at minimum time
may be clone server without emails but with email accounts
for a migration to new server at minimum time
Great to see this get a status update. Lets keep things moving forward, folks :)
Great to see this get a status update. Lets keep things moving forward, folks :)
Great to see this get a status update. Lets keep things moving forward, folks :)
Great to see this get a status update. Lets keep things moving forward, folks :)
I'm confused - what exactly has changed? Status = Open Discussion?
I'm confused - what exactly has changed? Status = Open Discussion?
This could be especially helpful to allow migrations from CentOS6 to CentOS7 . Not sure if we need yet another feature request though ... idea would be to scan system for modification from base, package and selectively install on new system, identifying or flagging incompatibilities between systems. This would be a sensible migration approach to get a new server running and switch.
This could be especially helpful to allow migrations from CentOS6 to CentOS7 . Not sure if we need yet another feature request though ... idea would be to scan system for modification from base, package and selectively install on new system, identifying or flagging incompatibilities between systems. This would be a sensible migration approach to get a new server running and switch.
Another reason this is particularly important is that most config management tools that can look at changes made to a base distribution might try to replicate things that either cpanel needs to manage (etc. httpd.conf). Any guide to migrate packages, etc. would be helpful so we can create parity on a newly migrated system (esp upgrade from centos6 to centor7)
Another reason this is particularly important is that most config management tools that can look at changes made to a base distribution might try to replicate things that either cpanel needs to manage (etc. httpd.conf). Any guide to migrate packages, etc. would be helpful so we can create parity on a newly migrated system (esp upgrade from centos6 to centor7)
+1 this should be a mandatory feature. I'm about to move away from my Cent OS / cPanel setup with Host Gator, to Azure with Windows, as this kind of upgrade is an area that isn't largely an issue in that platform (certainly in theory - yet to know the practice!). I'm tired of the banner saying I should upgrade to Cent OS 6 asap every time I log in to WHM, when you provide no mechanism to do this, and HostGator want to charge me $75 for the privilege! Thanks :-)
+1 this should be a mandatory feature. I'm about to move away from my Cent OS / cPanel setup with Host Gator, to Azure with Windows, as this kind of upgrade is an area that isn't largely an issue in that platform (certainly in theory - yet to know the practice!). I'm tired of the banner saying I should upgrade to Cent OS 6 asap every time I log in to WHM, when you provide no mechanism to do this, and HostGator want to charge me $75 for the privilege! Thanks :-)
This seems like one of the most requested cpanel items. I want it to help me upgrade to a new CentOS 7 server. I'm sure there are many use cases. Full automation may be hard but PLEASE help by providing some tutorials to capture all the config on one machine, relative to a pure cpanel server and migrate to a new machine. RPMs, /etc config, etc. Many people are "stuck" on a server and want to migrate / rebuild.
This seems like one of the most requested cpanel items. I want it to help me upgrade to a new CentOS 7 server. I'm sure there are many use cases. Full automation may be hard but PLEASE help by providing some tutorials to capture all the config on one machine, relative to a pure cpanel server and migrate to a new machine. RPMs, /etc config, etc. Many people are "stuck" on a server and want to migrate / rebuild.
I think cPanel has understood the need of these functions hence they introduced "Configuration Cluster" but unfortunatly I don't see a lot of movement on the "Add ...... to Configuration Cluster" topics :(
Any update cPanel Team ?
I think cPanel has understood the need of these functions hence they introduced "Configuration Cluster" but unfortunatly I don't see a lot of movement on the "Add ...... to Configuration Cluster" topics :(
Any update cPanel Team ?
Wow, Status changed to Planned... Love to see this feature is starting its engines :)
Wow, Status changed to Planned... Love to see this feature is starting its engines :)
We are in the early stages of planning this feature. I will update this feature request as the planning continues and we have more information that we can share.
Our primary objective is to extend the transfer tool to perform configuration setting migrations (cpanel.config, easyapache profiles, exim configurations, etc). We plan on first building a framework for solving this problem and then adding different subsystems (f.ex. cpanel.config, exim, apache..) to the migration process iteratively over the next few months.
I do not know what sort of impact this will have on backups or a CLI utility at this time. I do feel that these are improvements that can offer quite a bit of value to our users. I cannot imagine a scenario where we will not eventually iterate to some sort of improvement in that direction.
We are in the early stages of planning this feature. I will update this feature request as the planning continues and we have more information that we can share.
Our primary objective is to extend the transfer tool to perform configuration setting migrations (cpanel.config, easyapache profiles, exim configurations, etc). We plan on first building a framework for solving this problem and then adding different subsystems (f.ex. cpanel.config, exim, apache..) to the migration process iteratively over the next few months.
I do not know what sort of impact this will have on backups or a CLI utility at this time. I do feel that these are improvements that can offer quite a bit of value to our users. I cannot imagine a scenario where we will not eventually iterate to some sort of improvement in that direction.
I can't promise that we will be able to migrate every single thing on a server. for example, our current plugin architecture has no consideration for migration in it, it would have to be changed to do a migration in any sane way.
As we plan this feature I'd like to ask everyone who is watching this thread:
What are the most important parts of the server to migrate? What's the most critical? What's the most painful?
I can't promise that we will be able to migrate every single thing on a server. for example, our current plugin architecture has no consideration for migration in it, it would have to be changed to do a migration in any sane way.
As we plan this feature I'd like to ask everyone who is watching this thread:
What are the most important parts of the server to migrate? What's the most critical? What's the most painful?
Of most improtance for me is everything to do with apache.
Versions options, modules... etc.
Of most improtance for me is everything to do with apache.
Versions options, modules... etc.
I've been able to bash script almost everything with migrating from one cpanel server to another. Some of the things that I have not been able to reliably script, or may not want to script, are:
- tweak settings
- exim configuration (i don't really want to just overwrite the file.)
- statistics software configuration
- Password Strength Configuration
- host service ssl
- cpanel branding
- csf configuration (whitelist and blacklist i've got, but custom configurations such as ports need to be done manually.
In addition, I would also like to point out that a CLI script (like cpconftool) is useful for server restores as well, not just server migrations. I currently use the cponftool in my script and it does a good job of catching some of this stuff.
The issue, I understand, is that we cannot account for all of the ways that someone is going to customize a server. Especially if those customizations are made outside of cpanel.
I've been able to bash script almost everything with migrating from one cpanel server to another. Some of the things that I have not been able to reliably script, or may not want to script, are:
- tweak settings
- exim configuration (i don't really want to just overwrite the file.)
- statistics software configuration
- Password Strength Configuration
- host service ssl
- cpanel branding
- csf configuration (whitelist and blacklist i've got, but custom configurations such as ports need to be done manually.
In addition, I would also like to point out that a CLI script (like cpconftool) is useful for server restores as well, not just server migrations. I currently use the cponftool in my script and it does a good job of catching some of this stuff.
The issue, I understand, is that we cannot account for all of the ways that someone is going to customize a server. Especially if those customizations are made outside of cpanel.
Basic CPanel & WHM Setup
Configure CPanel Cron Jobs
Statistics Software ConfigTweak Settings
Update Preferences
Everything under Support tab
Everything under Server Contacts tab
Packages, if possible, and Feature Manager
Basic CPanel & WHM Setup
Configure CPanel Cron Jobs
Statistics Software ConfigTweak Settings
Update Preferences
Everything under Support tab
Everything under Server Contacts tab
Packages, if possible, and Feature Manager
Why not work on automation documentation instead just like Odin did with Plesk, and then let sysadmin/devops deploy & manage servers with their own tools?(Ansible,puppet,Chef, Etc...)
Why not work on automation documentation instead just like Odin did with Plesk, and then let sysadmin/devops deploy & manage servers with their own tools?(Ansible,puppet,Chef, Etc...)
The "small" things that you have to configure everytime it's a pain in the arse, such apache (easyapache [!]), tweaks, exim, default templates,php config,packages&features(+LVE settings <- will be awesome!!).
@Jacob: for csf stuff it's so easy to copy the specific files with scp -r or simply pack the files and unpack on new server.
The "small" things that you have to configure everytime it's a pain in the arse, such apache (easyapache [!]), tweaks, exim, default templates,php config,packages&features(+LVE settings <- will be awesome!!).
@Jacob: for csf stuff it's so easy to copy the specific files with scp -r or simply pack the files and unpack on new server.
I suggest adding a "Clone cPanel server" page in WHM. This page should enable you to specify the remote server to clone to (if possible, otherwise figure out how to give us an archive file to transfer over manually). It should default to cloning every possible (this is up to cPanel's dev team) thing. Then have an 'Advanced' drop down menu that lists every group of objects (e.g. packages, features, and each section of WHM, such as (>> denotes child pages):
Server Configuration >> Basic cPanel & WHM Setup
Server Configuration >> Tweak Settings
Service Configuration >> Apache Configuration
etc.
Being able to clone these settings from our most up to date server would save a ton of time.
I suggest adding a "Clone cPanel server" page in WHM. This page should enable you to specify the remote server to clone to (if possible, otherwise figure out how to give us an archive file to transfer over manually). It should default to cloning every possible (this is up to cPanel's dev team) thing. Then have an 'Advanced' drop down menu that lists every group of objects (e.g. packages, features, and each section of WHM, such as (>> denotes child pages):
Server Configuration >> Basic cPanel & WHM Setup
Server Configuration >> Tweak Settings
Service Configuration >> Apache Configuration
etc.
Being able to clone these settings from our most up to date server would save a ton of time.
Now that we are a few months into development of this feature I can discuss a bit about where we are, what we are doing and where it is heading.
In 11.56 we have extended the transfer tool with a new set of options called "Service Migrations". This same functionality is accessible through the CLI via a tool called "cpconftool". Initially we are offering the ability to migrate the following items (some items may not make the cut in a few weeks from now):
Apache
EA3 profiles, optmods & rawopts
EA4 profiles
template files
/var/cpanel/conf/apache/ and it's contents
Exim
/etc/exim.conf and along list of things
cPanel
cpanel.config
/etc/wwwacct.conf
touch files associated with those two areas
global paper_lantern customization
/etc/stats.conf (statistics software configuration)
MySQL
Update the server to the version that the source had (no downgrades)
/etc/my.cnf
New backup system
Transports
Global backup configuration
This is of course a first iteration towards this feature, we intend on extending this feature with further capabilities. I would love to hear what items the people in this thread feel are the highest value.
Now that we are a few months into development of this feature I can discuss a bit about where we are, what we are doing and where it is heading.
In 11.56 we have extended the transfer tool with a new set of options called "Service Migrations". This same functionality is accessible through the CLI via a tool called "cpconftool". Initially we are offering the ability to migrate the following items (some items may not make the cut in a few weeks from now):
Apache
EA3 profiles, optmods & rawopts
EA4 profiles
template files
/var/cpanel/conf/apache/ and it's contents
Exim
/etc/exim.conf and along list of things
cPanel
cpanel.config
/etc/wwwacct.conf
touch files associated with those two areas
global paper_lantern customization
/etc/stats.conf (statistics software configuration)
MySQL
Update the server to the version that the source had (no downgrades)
/etc/my.cnf
New backup system
Transports
Global backup configuration
This is of course a first iteration towards this feature, we intend on extending this feature with further capabilities. I would love to hear what items the people in this thread feel are the highest value.
This sounds great. I think our primary use and upvote on the feature request was to be able to "move" cpanel user accounts to other servers. This would include email data, added DNS records and mysql and file structure.
This sounds great. I think our primary use and upvote on the feature request was to be able to "move" cpanel user accounts to other servers. This would include email data, added DNS records and mysql and file structure.
While this will be great when I want to start up a new server so I don't have to go page by page to compare settings after tweaking a system for several years, there is another use I can see.
I have a 32 bit system now and will need to move it to 64 bit in the future. Since there is no direct upgrade path anything that can help move the accounts and the server configuration to reducing the downtime is appreciated.
Oh...and if it could detect additional PHP modules that were installed and clone that as well, that would be great.
While this will be great when I want to start up a new server so I don't have to go page by page to compare settings after tweaking a system for several years, there is another use I can see.
I have a 32 bit system now and will need to move it to 64 bit in the future. Since there is no direct upgrade path anything that can help move the accounts and the server configuration to reducing the downtime is appreciated.
Oh...and if it could detect additional PHP modules that were installed and clone that as well, that would be great.
I would love to see these:
Tweak Settings
Exim Configuration
Feature Lists
Packages
Statistics Software Configuration
Update Preferences
Even if we have setup these automatically today, it would be great to have it in WHM.
I would love to see these:
Tweak Settings
Exim Configuration
Feature Lists
Packages
Statistics Software Configuration
Update Preferences
Even if we have setup these automatically today, it would be great to have it in WHM.
Look at the way digital ocean approaches this. They don't automate everything....they provide step by step tutorials....in fact they pay people to write them. Cpanel Has a very unique environment and this would be a great strategy for something like this.
Look at the way digital ocean approaches this. They don't automate everything....they provide step by step tutorials....in fact they pay people to write them. Cpanel Has a very unique environment and this would be a great strategy for something like this.
Look at the way digital ocean approaches this. They don't automate everything....they provide step by step tutorials....in fact they pay people to write them. Cpanel Has a very unique environment and this would be a great strategy for something like this.
Look at the way digital ocean approaches this. They don't automate everything....they provide step by step tutorials....in fact they pay people to write them. Cpanel Has a very unique environment and this would be a great strategy for something like this.
I need to set password automatic on backup file that moved on remote server.
I need to set password automatic on backup file that moved on remote server.
First thanks for asking. I am relatively New to this side of cpanel..long time admin going out on his own...
I would just simply say it should be I want to "clone" this Gold copy or Gold server to another blank or OS installed box. I would pretty much want the generic stuff to be able to change Like IP, Hostname, root passwd, All in a menu asking what they should be. The option to move or not move accounts would be essential IMHO. Think of it as provisioning a new server from a gold copy. The use of making a gold copy image would be great to.. I would assume some are doing this with tools outside of Cpanel now. Anyway that's my 2 cents.
First thanks for asking. I am relatively New to this side of cpanel..long time admin going out on his own...
I would just simply say it should be I want to "clone" this Gold copy or Gold server to another blank or OS installed box. I would pretty much want the generic stuff to be able to change Like IP, Hostname, root passwd, All in a menu asking what they should be. The option to move or not move accounts would be essential IMHO. Think of it as provisioning a new server from a gold copy. The use of making a gold copy image would be great to.. I would assume some are doing this with tools outside of Cpanel now. Anyway that's my 2 cents.
It'd still be nice to see this all in a cPanel Master server though, so configurations can easily be pushed out to groups of servers (tags on servers would be best) :)
It'd still be nice to see this all in a cPanel Master server though, so configurations can easily be pushed out to groups of servers (tags on servers would be best) :)
I what version will be available?
I what version will be available?
So will this facilitate a server migration + config + packages in centos 6 to centos7? The idea is to do a basic install on target then run migration or do you start with migration on a pure centos target host?
So will this facilitate a server migration + config + packages in centos 6 to centos7? The idea is to do a basic install on target then run migration or do you start with migration on a pure centos target host?
This is available in cPanel & WHM version 56. You can read about it here:
https://documentation.cpanel.net/display/ALD/Transfer+Tool#TransferTool-ServiceConfigurations
Comments are now locked, but if you require any assistance you can open a ticket with our support team, email me (benny@cpanel.net) or ask me on twitter (@cpaneldev).
This is available in cPanel & WHM version 56. You can read about it here:
https://documentation.cpanel.net/display/ALD/Transfer+Tool#TransferTool-ServiceConfigurations
Comments are now locked, but if you require any assistance you can open a ticket with our support team, email me (benny@cpanel.net) or ask me on twitter (@cpaneldev).
Replies have been locked on this page!