After upgrading TDP for exchange to latest version 8.1.14, backup doesn't work anymore. If parameter DIRMC is set on a TDP node and not exists in the domain, then backup fails.

Attempting to perform a Tivoli Storage FlashCopy Manager
backup of the SQL Server may fail with an RC=189.
A trace shows that the failure is occurring when the
Remote Agent is initialized:
07/18/2011 16:39:59.364 [002296] [3476] : iccuval.cpp
 (463): Exiting iccuUnPackIdentifyResp()
07/18/2011 16:39:59.364 [002296] [3476] : client2client.cpp
 (2240): Exit C2CContactAgent() - Remote Agent responded with
  rc=189
The problem is seen when the DIRMC value specified within the
DSMAgent (Remote Agent service) options file (dsm.opt) is set
to a Mgmtclass that is not within the Policy Set for the Node
that is being used for the FlashCopy Manager backup.

Add the TESTFLAG IGNOREDIRMC to dsm.opt from baclient folder

ANS1025E (RC137)  Session rejected: Authentication failure
ACO5060E A IBM Spectrum Protect API error has occurred.

Suppress the folder

C:\ProgramData\Tivoli\TSM\....

And authenticate the nodes

tsm backup success, but nothing is backup

when using tdp command line, VSS writer for exhange is offline:

c:> tdpexcc query exchange
...
DB1 online
...
VSS writer: offline

If the Windows Backup tool was used to backup the Exchange DAG, as part of setting up the Windows Backup tool the following registry value must be created to work in a database availability group (DAG) .

HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters. 
DWORD value : EnableVSSWriter
Value: 0 

Microsoft documentation used to enable Windows Backup feature states that the Microsoft Exchange Replication server VSS writer must be disabled for correct operation. However, to use Backup Exec after having run a Windows Backup, the registry key “HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters\EnableVSSWriter” must be re-enabled by setting the value to 1 (default), and the Microsoft Exchange Replication service must be restarted to enable the 'Microsoft Exchange Replica Writer' again.

To create the trace flag, issue the “/TRACEFILE” and “/TRACEFLAGS” command-line options with the following example command:

TDPEXCC BACKUP SG1 FULL /TRACEFILE=DPTRACE.TXT /TRACEFLAG=SERVICE

Enable tracing with the DP/Exchange dsm.opt file and the “TRACEFILE” and “TRACEFLAGS” keywords. The following text is an example of the entry in the DP/Exchange dsm.opt file:

TRACEFILETRACEFLAGAPITRACE.TXT
SERVICE

Enable tracing with the dsmagent (baclient) dsm.opt file and the “TRACEFILE” and “TRACEFLAGS” keywords. The following text is an example of the entry in the dsmagent (baclient) dsm.opt file:

TRACEFILE AGTTRACE.TXT
TRACEFLAG SERVICE PID TID ENTER ALL_VSS SBRM RESTORE

The trace flag, in this instance, is ALL_VSS (you might need different traceflags, depending on the circumstance).

Event logging is the only extra tracing that can be turned on. Complete these steps to modify the level of event logging for the Exchange Store Writer:

1. Open the Exchange Management Console.
2. Find the server object.
3. Right-click the server on which you want to increase the logging level
and click Properties or Manage Diagnostic Logging Properties, depending on the Exchange version.
4. Click the Diagnostics Logging tab.
5. Expand the MSExchangeIS node in the Services pane and click System.
6. Click Exchange writer in the Categories pane and select the logging level.
7. Click Apply and then OK to close the Properties dialog box.