Successful sessions show reason as blank which is ok. Failed sessions are only picking up the first entry which is sometimes helpful and other times useless. THis example is shown below. I really couldve used the Second error but the REST api only fives me the first error that states 'finalizing'
Error messages for backup and backup task sessions are written to Config DBs similarly in both EM and VBR, and information retrieved through REST API depends solely on what's written in the corresponding tables. For reason property the first error message is logged by design. We could, of course, bypass this and parse logs directly from xml log file, but it would significantly affect performance.
