Thank you for contacting Veeam Technical Support! My name is Viktoriia and I'll handle your case opened with us.
This is an expected behavior in update 2, we implemented caching which increases RAM requirements for the target agent. If this is enabled, Backup Copy job target agent will hold a lock on target files even if the session is idle and, accordingly, you can't eject the drive.
To get rid of this issue please implement the following registry value:
Implement it on each proxy or repository in your Veeam infrastructure here:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\
Restart Veeam Backup Service on Veeam server is obligatory.
Users browsing this forum: No registered users and 15 guests