Backup Configurations - Select ethernet device for remote backups
Open Discussion
As a WHM user and a server administrator I would like the ability to define what Ethernet device or IP Route is used for a remote backup destination, on a per-destination basis.
- Original request
- This information is shared privately in spoiler and not visible!
I like this idea 
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.
Thank you so much for your submission! What would be the motivator for having the ability to define this in WHM, from your perspective. The only use case I can think of is when you're using a non-public-facing ethernet device, but routing for that would be determined by the OS without any need to specifically define it, assuming the interfaces and routes are defined correctly.
Thank you so much for your submission! What would be the motivator for having the ability to define this in WHM, from your perspective. The only use case I can think of is when you're using a non-public-facing ethernet device, but routing for that would be determined by the OS without any need to specifically define it, assuming the interfaces and routes are defined correctly.
Hello, in my case I would use it just to make certain that the primary public facing device is never used for the backup FTP process.
Hello, in my case I would use it just to make certain that the primary public facing device is never used for the backup FTP process.
If your server has a private network on eth1 (for instance) and your backup path is to an IP on that private network then by virtue of the routing table on the server it wouldn't send traffic over eth0.
If your server has a private network on eth1 (for instance) and your backup path is to an IP on that private network then by virtue of the routing table on the server it wouldn't send traffic over eth0.
Why not just let routing take care of this. If you want your backup to go via eth1 instead of eth0, then route the traffic via that interface.
Why not just let routing take care of this. If you want your backup to go via eth1 instead of eth0, then route the traffic via that interface.
Replies have been locked on this page!