These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Server backup issue on the new forum.
Web Hosting and Cloud Computing Control Panels
Howdy,
Yeah, the particular backup format that's configured by default wants to be able to include the home directory data.
To get around that, you could always select a different backup format. When setting up your scheduled backup, in the Destination and Format section, you could choose "One file per server (old format)" rather than using the default "One file per server" in the "Backup Format" section.
-Eric
Hi Eric, I had tried that but
"Backup failed : The option to transfer each server after it is backed up can only be used with new-format backups"
Edited: stupid me: I unchecked that option to transfer (I had marked it because of ssh option to backup file)
Howdy,
Great, sounds like you got that working! Yeah, I do something similar since I prefer to use rsync to backup my files as well :-)
-Eric
Eric, A second file is created: virtualmin.tar.gz Do I have to do something with it?
That file contains your Virtualmin settings and configurations. For example, all the Server Templates and Backup Schedules would be included in that.
If you're migrating from one server to another, you'd want to restore that archive as part of the migration procedure (unless you were hoping to start from scratch on your configuration).
-Eric
So, do I have to restore it one time like my first VS restore?
You'd restore that anytime you want to transfer all the Virtualmin settings from your old server to your new one (overwriting your existing settings on the new server).
You wouldn't want to do that after you've made any customizations, or they'd be overwritten.
-Eric
Nice!
1) "Warning - the following features were enabled in one or more of the domains in the backup, but are not enabled on this system : Plugin virtualmin-signup"
Can you please help me how to add this plugin?
Isn't it an old fashoned setting? I remember virtualmin-signup in three or more years ago.
2) Anyway, I cannot restore because of "A unix user named ** already exists" I had backed up users and groups id>=500 and restored them in the new server. I remember last move that id# were not the same after virtualmin restore and that affected files owned by uid numbers instead of names. Is there another way to avoid this? (I can delete the user, remember the id #, let Virtualmin make its job and then change assigned id#)
Regarding the large folder in the home directory. Did you try to exclude the folder with "Administrations Options->Excluded Directories->Directories under home to skip"? May be this works?
Fine! Thanks! This is a good option to exclude certain dirs. The backup options only allows to exclude all files. Both are good for me.
You are welcome.
Howdy,
1) "Warning - the following features were enabled in one or more of the domains in the backup, but are not enabled on this system : Plugin virtualmin-signup"
That's actually a Virtualmin add-on module that may have been added into your system in the past. One or more of your domains may have used that at some point, and now Virtualmin is expecting to see the module installed and enabled now.
That's an easy fix though -- if you're using Ubuntu/Debian, you can run "apt-get install webmin-virtualmin-signup". If you're using CentOS, you can run "yum install wbm-virtualmin-signup".
-Eric