Skip to main content
  • EN

Hi Community.  I have an Azure storage account I am no longer using as a repository for VBAz policies.  I was going to delete the account until I noticed there are three containers named “veeamdeployer<random>”, and each container contains the same 3 files: veeamDeploymentdll.dll, veeamDeploymentSvc.exe, and veeamNetworkRedirector.exe.  Does anyone know if these containers and files are needed now that I’m well beyond deployment into Azure?  Thank you.

Those files are part of the Veeam Installer service that is used to deploy components from the VBR server.  If you are no longer using them you can delete them.

Thanks Chris for the very quick reply.  We deployed our VBA outside of the VBR and we use the VBA web UI to do our Azure VM backups.  I’m not sure what we did with VBR that was a “deploy” into Azure, other than  there was some early testing within VBR by another team member restoring an on-prem VMWare VM backup into Azure.  Maybe that process created those containers and files on that storage account? 

I need to remove this storage account.  I don’t find anywhere within VBR or VBA how relocate the veeamdeployer containers.  I assume they’re transient and VBR will simply request a new storage account to use for its veeamdeployer containers if at some point we do a VBR “deploy” into Azure.

Thanks Chris for the very quick reply.  We deployed our VBA outside of the VBR and we use the VBA web UI to do our Azure VM backups.  I’m not sure what we did with VBR that was a “deploy” into Azure, other than  there was some early testing within VBR by another team member restoring an on-prem VMWare VM backup into Azure.  Maybe that process created those containers and files on that storage account? 

I need to remove this storage account.  I don’t find anywhere within VBR or VBA how relocate the veeamdeployer containers.  I assume they’re transient and VBR will simply request a new storage account to use for its veeamdeployer containers if at some point we do a VBR “deploy” into Azure.

Yeah more than likely that process created them.  You can just remove them and then more than likley will have them deployed when adding a new storage account.

Comment


Terms & Conditions