VirtualServer shuts down with “running elsewhere” – duplicated virtualserver_unique_identifier after snapshot import

Hello everyone,

I’m running two separate TeamSpeak 3 servers on two different VMs (different IPs, different licenses, clean installations).

On the second server I:

  • installed TS3 from scratch
  • imported a server snapshot exported from the first server using YATQA (to reuse channels/groups as a base)

Both servers can start correctly, but after ~1 hour the virtual server on one of them shuts down with:

virtual server id X is running elsewhere, shutting down!

After some investigation I found that:

  • both virtual servers have the same virtualserver_unique_identifier
  • licenses are different
  • IPs and machines are different
  • no files or databases were copied manually, only snapshot import

So it seems that importing a full server snapshot also clones the virtual server identity, and the accounting/licensing check later detects the same VS running in two places.

I understand that the correct solution is probably:

  • create a fresh virtual server
  • avoid full server snapshot
  • migrate only channels / permissions (partial import)

However, before rebuilding everything, I wanted to ask:

  • Is there an official or supported way to regenerate a virtualserver_unique_identifier?
  • Is partial import (channels + permissions) the only recommended way to clone a server layout?
  • Is this behavior expected / documented for full server snapshots?

Any confirmation or best practice advice would be appreciated.

Thanks in advance.

We do not support any manually modification of the virtual server ID


This behavior is expected since the snapshot is a “full”[1] backup of the server it will restore the virtual server ID.

The most optimal way to handle this would be to use use YaTQA and export the Channel tree as well as Server Groups and do the rest by hand.


  1. not including uploaded files etc. ↩︎

3 Likes