My apologies if this has already been asked before. I did a brief board search and couldn’t find the answer and I’ve already checked out the documentation on v-restore-user without finding the results. Is it possible to migrate all of the domains/email/dns/databases and settings from the admin to a non-privileged user account or do you have to recreate it all? Thank you in advance.
As Eris said… you can restore to ‘admin’ and then change owner of the domain/db with those commands. In old VestaCP, you could trick the restore to a new user by renaming backup file ‘admin_backupxxx’ to ‘newuser_backupxxx’ and then restore it to new user’s name directory with v-restore-user.
Also pay attention to any custom templates you might be using here for additional configs.
You can also use
v-restore-user newuser admin.xxxxx.tar
Fantastic, thank you both very much. Beforehand I searched the board and checked out the docs on the v-restore-user CLI command because I was already aware of it and didn’t find it, but after you said that, I went back and searched on the documentation page and found this. 
It was right freaking there. Apparently I didn’t search hard enough, so again, I apologize for the redundancy and appreciate your patience.
Using the restore approach, the only issues I have noticed so far are that any database user credentials on any websites that are prefixed by the old username will need updated, which is obvious, and that none of the symlinks for the ssl certs on any of my mail domains worked. All mail domains with SSL enabled receive the series of messages below, which I don’t believe is the intended action of the restore script.
chmod: cannot access '/usr/local/hestia/data/users/userx/ssl/mail.domain.com.*': No such file or directory
cp: cannot stat '/usr/local/hestia/data/users/userx/ssl/mail.domain.com.crt': No such file or directory
cp: cannot stat '/usr/local/hestia/data/users/userx/ssl/mail.domain.com.key': No such file or directory
cp: cannot stat '/usr/local/hestia/data/users/userx/ssl/mail.domain.com.pem': No such file or directory
chmod: cannot access '/home/userx/conf/mail/domain.com/ssl/*': No such file or directory
chown: cannot access '/home/userx/conf/mail/domain.com/ssl/*': No such file or directory
chmod: cannot operate on dangling symlink '/usr/local/hestia/ssl/mail/mail.domain.com.crt'
chmod: cannot operate on dangling symlink '/usr/local/hestia/ssl/mail/mail.domain.com.key'If you use v-restore-user, take a look at the crontab of the new user. If its migrated the admin crontab to the new user it will be creating lots of errors. You’ll probably need to remove all the crontab entries for the new user.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.