In Snap Creator 4.0 the CLI and Agent created this directory in /tmp. These are the libraries and are things that those binaries use. The directory is not removed as it is reused, so unless you delete it or it gets deleted by /tmp.
In Snap Creator 4.1 only the CLI will create this directory in /tmp as the Agent is now Java which does things differently.
What is the problem with this dir not being removed?
Ah yes the VMware plugin and other perl plugins unpack things to /tmp. As I said they arent deleted but rather re-used. If they arent there then they are unpacked.
There is no point in deleting them. In addition we are talking a few MBs. I still dont understand the concern? As I said every time a backup runs these libraries are used. We could unpack them under somewhere else but we chose /tmp since they are important only at runtime. This is not something we can change or will change in 4.1 but we can consider this in future. Again I would like to understand the problem this creates?
Disregard what I said about POST_NTAP_CMD that isnt a good idea if you have multiple jobs running then they could step on each other and cause backup failures since the data in /tmp is used at runtime.