Issue/Introduction

Source and classification

• Source: Customer Support site case.
• Classification: Host scheduling or deployment prerequisites during Worker creation.
• Confirmation basis: On June 11, 2026, a site reported Worker creation failing with the technical literal 没有有效的主机使用. On August 11, the group recommended preferring a static IP because DHCP address-acquisition timeout might fail Worker creation.
• Internal tracking: No specific Jira.

Issue metadata

• Issue ID: None.
• Component/product: ZSphere and Veeam Worker.
• Status: General checks are available; the original case's unique cause and final result were not recorded.
• Priority/severity: General; blocks Worker creation and dependent backup/recovery.
• Affected version: Not provided.
• First fixed version: None.
• Confirmation date: June 11, 2026.
• Last updated: September 4, 2026.

Problem description

When creating a Worker after Veeam integrates with ZSphere, the platform selects an eligible host and prepares compute, storage, and network resources. If no candidate satisfies scheduling or required network, addressing, or storage is unavailable, creation can fail because no valid host is available.

The original site text was:

What can cause Worker creation to fail? The error says that no valid host is available.

This means no host passed pre-creation availability filtering, but does not identify the failed condition. Inspect task details, host state, capacity, storage, and Worker network configuration.

Symptoms

• Worker creation fails immediately.
• The page or task details show a message similar to:

  没有有效的主机可用

Or:

  没有有效的主机使用

• The Worker VM is not created or does not finish initialization.
• With DHCP, address acquisition might time out later in creation.
• Ordinary VMs might still run; this does not prove every host meets Worker prerequisites.

Site screenshot

Impact

• A new Veeam Worker cannot be created.
• Dependent backup, recovery, or data transfer cannot continue.
• Existing healthy Workers are usually unaffected directly.
• There is no evidence of damage to existing backup or business VM data.

Environment

• Product: ZSphere and Veeam integration.
• Product line: ZVF.
• Component: Veeam Worker creation and host scheduling.
• Version: Not provided.
• Trigger: No host simultaneously meets availability, compute, storage reachability, and network conditions, or later network initialization fails.

Possible causes

This symptom can be caused by one or more of the following conditions:

• All candidates are in maintenance, disconnected, disabled, unschedulable, or excluded by deployment constraints.
• Candidate compute resources or accessible storage do not meet Worker requirements.
• Worker network, IP pool, or VLAN is unavailable; DHCP can also time out later.

Resolution

1. Inspect detailed task errors

1. Find the Worker creation task in ZSphere Task Center.
2. Record full error code/message, candidate filtering, and failure time.
3. Identify the stage at which the failure occurs:

• Before host selection or scheduling.
• During Worker VM creation.
• During Worker OS startup or network initialization.
• During Worker package installation or initialization.

4. If details name insufficient resources, network, or storage, follow that specific error instead of only the outer no-valid-host message.

2. Check candidate-host state

Check the cluster and hosts on which the Worker is planned for deployment:

1. Hosts must be connected, enabled, and schedulable.
2. Hosts must not be in maintenance, disconnected, disabled, or abnormal.
3. At least one host in the cluster must meet Worker requirements.
4. Confirm host/cluster/deployment constraints do not exclude all hosts.
5. After host recovery, wait for resource and capacity refresh before retrying.

3. Check compute resources

1. Check available CPU and memory against Worker specifications.
2. Check resource reservation, overcommit limits, and other scheduling constraints.
3. Confirm resource tags, affinity rules, or host policies do not filter all hosts.
4. If necessary, test a smaller supported Worker specification; do not operate long-term below product requirements.

4. Check storage availability

1. Confirm the primary storage for the Worker system disk is connected and enabled.
2. Confirm it is attached to the candidate cluster with enough capacity.
3. Confirm backup storage containing the image/template is available and candidates can access the image path.
4. If only some hosts reach destination storage, they must also meet compute and network conditions.
5. Restore abnormal storage first; do not bypass scheduling by forcing a host.

5. Check the Worker network

1. Confirm the network is attached to the candidate cluster.
2. Confirm L2, L3, and IP-pool status.
3. Confirm sufficient IP addresses and correct gateway, subnet mask, and DNS.
4. Confirm reachability to ZSphere management, Veeam, and other required services.
5. Check physical NIC, VLAN, and switch configuration on candidates.

6. Prefer a static IP

Group experience recommends a static IP. Slow DHCP, an exhausted pool, or missing replies can time out Worker creation.

Procedure:

1. Select an unused static IP on the Worker network.
2. Enter correct subnet mask, gateway, and DNS.
3. Confirm the IP is unused.
4. Recreate the Worker with the static IP.
5. After boot, verify reachability to ZSphere management and Veeam.

7. Verify recovery

1. Recreate the Worker and confirm host selection.
2. Confirm the Worker VM is created and starts.
3. Confirm expected IP and management-network communication.
4. Wait for initialization and Available in Veeam.
5. Run a small backup or recovery test.

8. Collect information if unresolved

If the message still reports that no valid host is available after these checks, collect the following information and contact engineering:

• Exact ZSphere, API Proxy, and Veeam versions.
• Complete Worker creation steps and configuration.
• Complete error details from Task Center.
• Worker specification, target cluster, and allowed host scope.
• Connection, enabled, and maintenance state of every candidate host.
• Available CPU and memory of the candidate hosts.
• Primary storage, backup storage, and image state.
• L2 network, L3 network, IP pool, and VLAN information used by the Worker.
• Whether static IP or DHCP was used and the corresponding address-acquisition result.
• Management node and Veeam task logs near the creation failure time.

Additional information

Precautions

• No valid host is a scheduling result, not proof that a host is powered off or physically failed.
• Online hosts might still fail Worker compute, storage, or network conditions.
• Do not modify the database, bypass scheduling, or force an abnormal host to create a candidate.
• Static IP can reduce DHCP-timeout failures but does not resolve every no-valid-host case.
• Deleting packages and remaining at initialization during Worker creation is a separate issue; wait for command retry and shut down from the UI at the specified screen. Do not merge its cause with host filtering.
• Repeatedly deleting and recreating the Worker before saving task details and logs is not recommended because it can overwrite site evidence.

Fix status

• Current status: Troubleshooting and workaround available.
• General fix: There is no evidence that a single product defect causes this message in every case.
• Network workaround: Prefer static IP to avoid DHCP response errors/timeouts.
• Fixed version: None.
• Related patch/fix package: None.

Related information

• Original issue date: June 11, 2026.
• Static-IP recommendation date: August 11, 2026.
• Source group: veeam &Commvault使用说明.
• Recommended images: Error screenshot showing 没有有效的主机使用 and a screenshot of the static-IP configuration page.