Challenge
After upgrading 3PAR firmware you may encounter an all jobs failing and/or 3PAR rescans failing with an inability to communicate to the 3PAR device.Manual communication can be performed via PowerShell with the following:
http://xwiki.support2.veeam.local/bin/view/Main/Internal%20Technical%20Docs/Veeam%20Backup%20and%20Replication/Storage%20Integration/How-to-test-connectivity-to-3PAR-%28API%29/
Yes, I know this is our internal wiki, we should perhaps ask the creator if this is something we can publish externally for manual testing as this is an easy tool to test communication and is how this issue was isolated/resolved.
To review the logs for this issue you can find the location, log, and example below for comparison.
Log Location:
C:\ProgramData\Veeam\Backup and Replication\Backup\SanRescan
Log Name:
Util.SanRescan.Name.log
Example:
[29.08.2018 11:50:46] <01> Error [Hpe3PAR] Generate Hp3PAR exception. ErrorCode: '1', Description: 'internal server error', Reference: '<null>'.
[29.08.2018 11:50:46] <01> Error Failed to call web service methods. RetryCount: '1'. MaxRetryCount: '3'.
[29.08.2018 11:50:46] <01> Error Exception has been thrown by the target of an invocation.