Continuous Replication job stalls, leaving {importing] vm's. On host restart these clone will autostart with networking enabled
-
I had several reports from users that could not access fileshares. The server was up and responded to ping. But in AD there were duplicates of the Windows server. We found that an old Cont Repl job had left "garbage" VM's named {importing]. These VM's had everyting on (networking and AutoStart Enabled). We did not take notice ogf these(stopped) VM's until they auto-started after host-upgrade and restart.
Could there be a function in ContReplication jobs that turns off Auto-start right away when the cloned VM is created, in case the job stops AND the host late will reboot?
Usiong the latest patches (260117) for both xcp-ng and XenOrchestra (from sources)
Best regards Johan Uusijärvi
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đź’—
Register Login