directories to backup

8 posts / 0 new
Last post
#1 Tue, 09/02/2014 - 13:24

directories to backup


I've tried the migrate method and got in a total mess. I now can't delete the virtual domains - DBI connect failed : Access denied for user 'root'@'localhost' (using password: YES)

webmin backup/restore doesn't seem to work and neither does virtualmin. Hence I think the easiest solution might be just to take /home and the appropriate configuration files (which is what webmin backup says it will do but doesn't as far as I can looking in the backup gz file).

So can you provide a list of directories to back/restore in order to migrate webmin/virtualmin and websites to a new OS with webmin/virtualmin installed (and pear etc.)

Tue, 09/02/2014 - 15:01


Hmm, normally the process of migrating from one server to another is pretty straight forward... the process is documented here in the migration documentation:

Are you seeing the error you described on the old system, or the new one? It sounds like you're just seeing an incorrect root MySQL password though. That can be corrected in Webmin -> Servers -> MySQL -> Module Config, and there you can set "Administration password".

Performing a manual migration would be fairly tricky, as you'd have to move not just /home, and the databases in /var/lib/mysql, but you'd also need to move all the users, DNS settings, Apache settings, and a variety of other things.

I'm curious though, what distro/version are you moving from and to?


Tue, 09/02/2014 - 15:30

I'm actually moving from the same distro to the same distro, ubuntu 14.04 32bit.

I wonder if it because I skipped out of webmin just after I had run the and then logged in to see if it was all correct. Maybe I need to go through the new setup first, just to setup a bare webmin before I restore.

It does look like there is no databases or login for databases.

I'll give a go tomorrow.

Wed, 09/03/2014 - 06:09

Right I've rebuild from a new distro (ubuntu 14.04), reinstalled everything and this time gone through the post installation setup. I've restored a webmin backup which still doesn't change the theme. I then restore virtualmin features which works except for ftp which fails (I don't have ftp setup on the original so maybe that is why). I then come to restore virtualmin sites and it then fails because the sites already exist having been installed by restoring the webmin backup.

So does the virtualmin include webmin backup? Or should I restore webmin after restoring virtualmin?

Wed, 09/03/2014 - 13:11


Well, the recommended way to perform a migration from one server to another is to use the instructions I linked to above.

If you first copy over the files using another method (such as a Webmin backup), that could cause the restore of your Virtual Servers to fail, as Virtualmin might think it's already hosting those domains.

If you have a Webmin backup you wish to restore, you could always try restoring it after performing the steps in the above migration documentation.

Webmin and Virtualmin settings shouldn't cause FTP not to start though. The most common cause of that is ProFTPd not being able to determine the IP address of your hostname... you'd want to make sure the name returned in the "hostname" command exists in /etc/hosts, and is associated with an IP address.


Thu, 09/04/2014 - 03:18

OK, so run through my build vps checklist again and built a clean vps with webmin/virtualmin installed for Run through the post setup. I changed etc/hosts on the current setup which wasn't right. Took a virtualmin backup as per migration instructions then restored that on new server. That ran off without any moans this time.

However, pointing my local hosts to the new IP so I can see my duplicated site this doesn't work. The database user is not found. I suspect this is because I'm not using the default user of domain_name and default data_base of domain name. I've created a new database base and a new database user (user in server->mysql database). I haven't restored webmin at this point BTW so that is I suspect the reason.

I've taken a webmin backup, all modules + server files. I've done this on the duplicate and the current. Then I've ungz'ed these on my PC and run cdiff over them to see what is the same and what is different. Some files are the same, some are different which is interesting.

It looks like the UID numbers have been recreated, so where I had on the old system, user=domain, UID=1000 on the new system this would be user=domain, UID=1002, for example. Also, when I look at the owner of the home directory on the old system this is group=domain[1000], owner=domain[1000] where as on the new it is group=domain[10003], owner=domain[1005]. This is a bit worrying that it will mess up when I copy webmin over the top and change UID numbers.

Thu, 09/04/2014 - 11:43

I was right to worry. Restoring webmin messed up my duplicate vps so that I could not even ssh in. I had to use console in my vps control panel to get in. At that point it was clear that an issue was the duplicate vps thought it had the same IP address as the current vps.

I think this is because webmin restore just saves a bunch of files and then over writes the current setup, including etc/network/interfaces.

Thu, 09/04/2014 - 14:15

Really there is no backup method. Virtualmin backup/restore is ok but that is just for virtualmin. There isn't a viable webmin backup and virtualmin restore will be incompatible with webmin restore since virtualmin's restore rebuilds the sites and users, changing the user IDs and some of webmin's backup files also have uids in them.

Topic locked