If you’re seeing “tag is unavailable” errors when attempting to protect a VM using vSphere tags or “QueryAllCategoryInfos failed. There was no endpoint listening at https://vcenteraddress/lookupservice/sdk that could accept the message” error when editing the backup job.Continue reading
Tags are a great way to manage and organise resources across a vSphere environment, with tags we can sort and group VMs together based on any criteria we wish. Veeam can even leverage these “groups of VMs” in many different ways.
For example, Veeam Disaster Recovery Orchestrator leverages tags for orchestration plans and to make sure VMs are restored to the right place with tag-based recovery locations.
Veeam ONE Business View can automatically create and assign tags to VMs based on any desired criteria with its categorization engine, this is on top of VeeamONEs capability to run reports based on tags. I’ve previously written about Veeam ONE Business View which can be found here.
Veeam Backup & Replication (VBR) also can utilise tags for any job. By simply adding tags as the source object to the job, VBR will protect any VMs with that same tag, this can be especially time-saving if VMs are frequently being provisioned. Another benefit of tags is that, unlike folders and resource pools, VMs can be assigned multiple tags.
Let’s take a look at how we could group a selection of 8 VMs into various different backup jobs using tags.Continue reading
So working on a Veeam project recently and noticed I couldn’t add vSphere tags to any jobs. Now I won’t go into the benefits of using vSphere tags in this post, I’ll leave that up to this excellent write-up by Luca Dell’Oca which can be found here.
So checking the usual culprits and researching online I found someone with a similar issue on the Veeam forums here but I still couldn’t resolve the issue. I checked vCenters FQDN IP address which was set correctly and that I could indeed query vSphere tags from vCenter using PowerCLI without any problems. I bounced the Veeam B&R server, checked event logs and eventually ran out of ideas to try.