adsm.se

Tivoli Storage Manager use a Global Return Code to document the errors received during various operations. These return code are unique for Server and storage agent operations. Depending on the error condition, the GRC code can be logged to the server activity log along with an ANR message.

Tivoli Storage Manager Server V6 and V7

Example of an ANR message with GRC :


ANR1936E Replication of BACKUP data for file space fs1 on node NODE1 failed with reason: Reason code 1020.

In above example, the reason code 1020 translates to GRC_LOCK_CONFLIC

Below are a list of GRC codes can be received during node replication.

Return codes for replication only:

GRC_NO_REPL_WORK_FOUND                  2001
GRC_REPLICATION_UNAVAIL_SRC             2090
GRC_REPLICATION_UNAVAIL_TGT             2091
GRC_REPLICATION_NODE_DISABLED           2092
GRC_REPLICATION_RULE_DISABLED           2093
GRC_REPLICATION_FS_DISABLED             2094
GRC_REPLICATION_MODE_INCOMPAT           2095
GRC_OPERATION_IN_PROGRESS               2096
GRC_SKIP_REPL_FOR_PREVIEW               2097
GRC_SKIP_UPDATE_FOR_PREVIEW             2098
GRC_REPLICATION_TGT_SYNC_NODE_UNDEF     2099
GRC_REPL_NODE_READ_ONLY                 2100
GRC_REPL_SRV_DELETE_INPROGRESS          2101

Return codes common to all components:

GRC_NO_SPACE                            1001
GRC_NO_MEMORY                           1012
GRC_DEADLOCK_DETECTED                   1014
GRC_NO_LOG_SPACE                        1015
GRC_NO_DB_SPACE                         1016
GRC_DEADLOCK_EXISTS                     1018
GRC_CONDITIONAL_LOCK_FAILED             1019
GRC_LOCK_CONFLICT                       1020
GRC_LOCK_CONFLICT_RETRY                 1021
GRC_LOCK_NOT_GRANTED                    1022
GRC_LOCK_REQ_ABORTED                    1023
GRC_NO_THREAD                           1024
GRC_TXN_FAILED                          1030
GRC_TXN_ABORTED                         1031
GRC_RETRY_TXN                           1032
GRC_INSUFFICIENT_AUTHORITY              1040
GRC_CANCEL_PENDING                      1050
GRC_CANCEL_FAILED                       1051
GRC_CANCELED                            1052
GRC_SYNTAX_ERROR                        1060
GRC_INVALID_USE                         1061
GRC_NOT_PROCESSED                       1062
GRC_BUF_TOO_SMALL                       1063
GRC_OBJECT_NOT_FOUND                    1100
GRC_BITFILE_NOT_FOUND                   1101
GRC_VOLUME_NOT_FOUND                    1102
GRC_LIBRARY_NOT_FOUND                   1103
GRC_DRIVE_NOT_FOUND                     1104
GRC_PATH_NOT_FOUND                      1105
GRC_NODE_NOT_FOUND                      1106
GRC_FILESPACE_NOT_FOUND                 1107
GRC_VFS_NOT_FOUND                       1108
GRC_OBJSET_NOT_FOUND                    1109
GRC_DOMAIN_NOT_FOUND                    1110
GRC_POLICYSET_NOT_FOUND                 1111
GRC_MGMTCLASS_NOT_FOUND                 1112
GRC_COPYGROUP_NOT_FOUND                 1113
GRC_KEY_NOT_FOUND                       1114
GRC_TABLE_NOT_FOUND                     1115
GRC_ITEM_NOT_FOUND                      1116
GRC_SERVER_NOT_FOUND                    1117
GRC_ADMIN_NOT_FOUND                     1118
GRC_NODEGROUP_NOT_FOUND                 1119
GRC_POLICY_NOT_FOUND                    1120
GRC_NO_DEFAULT_MGMTCLASS                1121
GRC_NODE_NOT_IN_DOMAIN                  1122
GRC_STGPOOL_NOT_FOUND                   1123
GRC_SCRIPT_UNDEFINED                    1124
GRC_OPTSET_NOT_DEFINED                  1125
GRC_AUTHRULE_NOT_DEFINED                1126
GRC_VFS_MAPPING_EXISTS                  1127
GRC_SESSION_NOT_FOUND                   1128
GRC_CLASS_NOT_FOUND                     1129
GRC_CLASSNAME_NOT_DEFINED               1130
GRC_NO_DATAMOVER                        1131
GRC_DB_ALIAS_NOT_FOUND                  1132
GRC_DUPLICATE_OBJECT                    1200
GRC_KEY_EXISTS                          1202
GRC_ITEM_EXISTS                         1203
GRC_NODE_ALREADY_DEFINED                1204
GRC_ADMIN_ALREADY_DEFINED               1205
GRC_OPTSET_ALREADY_DEFINED              1206
GRC_NODEGROUP_ALREADY_DEFINED           1207
GRC_FS_ALREADY_DEFINED                  1208
GRC_AUTHRULE_ALREADY_DEFINED            1209
GRC_VFS_ALREADY_DEFINED                 1210
GRC_CLASSNAME_ALREADY_DEFINED           1211
GRC_VOLUME_ALREADY_DEFINED              1212
GRC_THREAD_ALREADY_RUNNING              1213
GRC_LDAP_ERROR                          1220
GRC_PASSWORD_TOO_SHORT                  1221
GRC_PASSWORD_TOO_YOUNG                  1222
GRC_PASSWORD_IN_HISTORY                 1223
GRC_PASSWORD_NOT_COMPLEX                1224
GRC_LOCKED_LDAP                         1225
GRC_PASSWORD_RESET                      1226

By default, reconciliation operations run every 20 minutes on the Derby database to delete metadata for backups that are no longer available. This action ensures that the Derby database remains synchronized with the Data Protection for VMware repository. When reconciliation runs, the VMCLI node connects to the Tivoli Storage Manager server.

The interval between reconciliation operations on the Derby database with Data Protection for VMware is specified by the VMCLI_RECON_INTERVAL_TSM parameter, which is one of the Data Protection for VMware command-line interface profile parameters. The default value for the parameter is 1200 seconds (20 minutes).

You can adjust the value of the parameter to reduce the frequency of connections made by the VMCLI node. For example, to have the VMCLI node connect to the Tivoli Storage Manager server once a day use the following parameter :

VMCLI_RECON_INTERVAL_TSM 86400


Note that the VMCLI node also establishes a connection to the Tivoli Storage Manager server when the Tivoli Storage Manager for VMware UI is started, regardless of the value set with the VMCLI_RECON_INTERVAL_TSM parameter.