TSM: ANR8985E The drive xxx in library xxx is using an encryption method that is incompatible with the current server settings.

I have faced confusing error message:

ANR8985E The drive xxx in library xxx is using an encryption method that is incompatible with the current server settings.

The root case of error was that I defined device class explicitly with parameter DRIVEEncryption and value OFF.
There was impact even I did not use encryption on library and its drives.

Drive was encryption capable but not enabled on library:
[root@tsm1 ITDT]# ./itdt -f /dev/IBMtape0 encryption
Getting drive encryption settings...
Encryption settings:

  Drive Encryption Capable... Yes
  Encryption Method.......... Library
  Encryption State........... NA
Exit with code: 0


So I changed DRIVEEncryption to ALLOW (default) even I did not use encryption and error message disappeared and volume got mounted...

define devclass IBMTAPE01WORM LIBRary=IBMTAPE01 DEVTYPE=LTO FORMAT=ULTRIUM8C WORM=YES MOUNTLimit=DRIVES DRIVEEncryption=ALLOW LBProtect=READWrite

TSM: Replicate Node fails with ANR9999D_2930690409 and rc=1120

I have had a problem when running replicate node between two TSM / Spectrum Protect servers, replication failed with nothing saying error message ANR9999D_2930690409 and rc=1120.

02/12/2019 12:30:47     ANR9999D_2930690409 SmReplServerSession(smrepl.c:2609) Thread<1537>: Replication session 246 for TSM on Linux/x86_64 failed, rc=1120 (SESSION: 246)
02/12/2019 12:30:47     ANR9999D Thread<1537> issued message 9999 from: (SESSION: 246)

Root cause was missing archive copy group on target server, wow, one may think that this could be common configuration mistake when configuring replication, but IBM doesn't think so when showing message which You can not understand :)

You can compare and validate policies on source and replication servers by command:

VALIDATE REPLPOLICY TARGET_TSM_SERVER_NAME

TSM: ANS0338E An invalid operation was attempted on a node on target server with replication

Error message "ANS0338E An invalid operation was attempted on a node" can be related to state of node on TSM server - node can be replicated to target server and has to be removed from replication by command "remove replnode nodename".