Closed killmasta93 closed 1 year ago
Hello
Can you create a fresh domain in the KVM?
According with this may be something with the CPU model that is configured, I don't use KVM so can't tell. Please let me know if you have any progress.
Hi @diegogslomp , Correct i created another fresh DC docker on another VM how would i transfer the files? or which folders contains the samba info? to maybe try to migrate Thank you
Try the rsync that you did here and update the interface inside smb.conf file.
hi @diegogslomp thank you so much for the reply it seems in the host that is working it has these folders
bin bind-dns etc include lib libexec private sbin share var
while on the host that has the CPU differnt it has these folders
bin bind-dns etc include lib lib64 libexec private sbin share shares var
it seems that it created the lib64 folder
i ran the setups
created docker on the host i want to be migrated then stop the container
then rsync from the old host folder samba to the new host
and restart the container and same issue with the CPU
Hello
Try to rsync only the etc, private, var
folders from /usr/local/samba
. If it fails you can
Join the old dc and sync the new one if you have connection between them, like the dc2,3,4 from the docker-compose.yml
Another alternative is to create a samba-tool domain backup
file and restore to the new one, but in this case the name of the new one should be different from the old one, more info here
Let me know if you have any progress
Hi finally got it working i did the samba tool domain backup
Hi @diegogslomp Hope all is well, Currently im migrating another docker container to another host the issue is that on the current host i have a different CPU while on the other host i have KVM when i migrate i see the logs
i tried creating another container in the KVM host then copy the private lib and libexec to that container but no luck
Thank yu=ou