When using the Offload scanner policies to configure primary and backup OSS servers. running the command line 'mvadm status' will reflect the setting.
When using the SVA Manager to assign the servers, I see a different result. The primary server shows active, but the secondary server shows "NONE:9053 [Not Configured]." Is this expected? And does this mean that if the SVA manager goes down it will not be able to transfer to a secondary scan server? I also notice that all servers will go to one assigned OSS server at the moment...is there a way to balance the load better or do you simply have to wait till the client load hits the maximum threshold?
This is correct.
So when the OSS goes down, Client will contact SVA manager again and get the new OSS details.
Load balancing is carried out by SVA manager. The SVA manager decides which OSS to assign based on load.