Loading...
Loading...
When attempting to deploy or test a worker VM, the operation fails with the following errors: Failed to deploy the worker VM: Cannot access a closed Stream. Worker <VM Name> test failed: Cannot access a closed Stream. This may also occur after an upgrade, when the existing worker VM is recreated and the redeployment fails.
This issue occurs because the storage that Veeam Backup & Replication is configured to use for worker VM deployment does not provide the ISO image and Snippets content types. During deployment, the worker image is written to the ISO image directory of that storage, and the worker's cloud-init configuration is written to its snippets directory. By default, Veeam Backup & Replication uses the Proxmox VE local storage, which on a default installation carries both content types. This storage is separate from the storage where the worker VM's disks are mounted, so selecting a different storage for worker VMs does not remove the requirement.
A worker VM can only be deployed to a host that provides file-level storage with the ISO image and Snippets content types enabled. The storage must also support snapshots. LVM storage that uses the Snapshots as Volume Chains (SAVC) mechanism cannot be used for worker files. If the default local storage was disabled unintentionally, enable it on the affected Proxmox VE nodes, then test each existing worker VM before a job is run. If the default storage cannot be used in the environment, configure an alternative as described below.
Veeam Backup & Replication User Guide > Proxmox Virtual Environment > Considerations and Limitations Veeam Backup & Replication User Guide > Proxmox Virtual Environment > System Requirements Proxmox VE Documentation > Directory Backend Proxmox VE Wiki > Storage
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.