We replaced some hosts withing a cluster under vCenter. Apparently some replication jobs had referred to a specific host rather than the cluster, so now all attempts to refer to those jobs or replicas within Veeam fail, complaining they can't find that old hostid. The replicas are intact, but cannot be removed from the configuration or used normally by Veeam.
In the best scenario, Veeam would provide a means to replace old hostid entries with a valid entry of our choice, and the problem would be 100% cured.
In a livable scenario, Veeam woud provide a means to delete references to the missing host and remove associated replicas from the configuration, so we could recreate the jobs and seed them with the good replicas.
So far Veeam support seems to be stumped.
Case #07784059
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Sep 09, 2009 4:53 pm
- Full Name: Richard A Bollinger
- Contact:
Who is online
Users browsing this forum: Semrush [Bot] and 12 guests