CBMR to TSM backup Fails - ANS1357S Session rejected: Downlevel client code version

CBMR to TSM backup Fails - ANS1357S Session rejected: Downlevel client code version

When CBMR is used for an ordinary TSM backup with the BA Client. The CBMR node must only be used for CBMR. using the TSM BA Client to connect to the backup server, on the client being backed up, causes the ANS1357S error as seen in the logs:

ANS1357S Session rejected: Downlevel client code version
ANS8023E Unable to establish session with server.

Once this error occurs the node is contaminated cannot be used to backup or recover from any filespace within the node. To fix this you need to create a separate node for the sole use of CBMR.

Delete the contaminated node and re-create it.


The problem arise because CBMR backs up in a non-unicode mode. The BA Client backs up in a unicode mode. Once a filespace within a node has been written to from Windows, the whole Node becomes inaccessible to CBMR whether it is running on Windows or Unix platforms.

You may check the current state of the node by looking at the filespaces within it. Use the command q file f=d and look for the unicode state of each filespace.

Note: You could also get this error when doing a recovery if you addressed the recovery to the wrong TSM node. If you tried to recover from the node to which you normally backup with the BA Client, it would give you a Downlevel error.