2020-06-23T05:55:52.5446075-04:00 Verbose SDW PID=[2996] TID=[12312] The SVM 'archive_svm' with User 'a1\admin.xxx' , UserGroupObjectType 'None' and Role 1 RoleObjectsShared True is not in the storage system cache.
2020-06-23T05:55:52.5446075-04:00 Verbose SDW PID=[2996] TID=[12312] The SVM is not in the storage systemId cache:
2020-06-23T05:56:13.5923927-04:00 Error SDW PID=[2996] TID=[12312] Cannot retrieve storage connection setting from SMS server.
The issue here is for some reason the SVM in question is not present in your plug-in host caching. Cache is built when you add the host and push plug-in packages. During 'discovery' operation, SC looks for the storage in plugin-host cache and if it doesnt find the respective SVM, it tries to fetch it from SC server host itself. From your logs the fetching operation too is failing. This is mostly beacuse the storage resolution is not working from your SQL nodes, hence missing from its cache.
Please make sure the svm name 'archive_svm' resolves and pings using name from both SQL Cluster nodes and retry .
Ex: ping -a <SVM IP> should return name 'archive_svm' from SC server as well all plugin host nodes.
To summarize , if SVM is added with short name or FQDN it has to be resolvable from both the server and the plug-in host.
Once you make the change, you can either try to restart the SMcore/Plug-in for windows services on the plug-in hosts or else, remove and re-add the host, if no restrictions.