Seems to me that webmin backup is really that good. In virtualmin you can use backup and restore to migrate a site. Virtualmin restore seems to recreate the sites rather than just doing a file replace. If you backup all of webmin and then restore it on a new vps what it does is screw up the new vps. For starters etc\network\interfaces will set new vps ip address to same as the old which is NOT what you want. Also, if virtualmin has recreated the site then the UIDs are different and a lot of webmin saved files have specific UIDs in then which again will screw things up.
So really webmin backup is of no use to migrate, and given that virtualmin restore will change UID it doesn't work as webmin/virtualmin site backup either. That just leaves plain old backup every file method, but for vps where you might need to move to another vps if the current vps goes to the wall, that's not a viable strategy either.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems to me that webmin backup is really that good. In virtualmin you can use backup and restore to migrate a site. Virtualmin restore seems to recreate the sites rather than just doing a file replace. If you backup all of webmin and then restore it on a new vps what it does is screw up the new vps. For starters etc\network\interfaces will set new vps ip address to same as the old which is NOT what you want. Also, if virtualmin has recreated the site then the UIDs are different and a lot of webmin saved files have specific UIDs in then which again will screw things up.
So really webmin backup is of no use to migrate, and given that virtualmin restore will change UID it doesn't work as webmin/virtualmin site backup either. That just leaves plain old backup every file method, but for vps where you might need to move to another vps if the current vps goes to the wall, that's not a viable strategy either.