CTGGI0002 No MongoDB instance have been found.
Explanation
The inventory finds only MongoDB instances that are running. Check that at least one MongoDB process is running on the application server before rerunning the inventory.
System action
User response
CTGGI0003 The MongoDB instance instance_name that was found is being examined.
Explanation
System action
User response
CTGGI0004 MongoDB instance discovered to be a member of replica set replica_set_name.
Explanation
System action
User response
CTGGI0005 Successfully retrieved members of the replica set.
Explanation
System action
User response
CTGGI0006 Examining MongoDB replica set member member_name.
Explanation
System action
User response
CTGGI0007 Starting the MongoDB instance backup operation.
Explanation
System action
User response
CTGGI0008 Database name: database_name.
Explanation
System action
User response
CTGGI0009 Backup destination: path_name.
Explanation
System action
User response
CTGGI0010 Backup timestamp is: timestamp.
Explanation
System action
User response
CTGGI0011 Finished MongoDB backup operation.
Explanation
System action
User response
CTGGI0012 Number of parallel streams for this backup operation: _number_parallel_streams.
Explanation
Specifying a number of parallel streams to speed up the backup operation.
System action
User response
CTGGI0013 Forcing a new base backup creates a full backup of the MongoDB database.
Explanation
System action
User response
CTGGI0014 The backup destination for the backup operation has been cleared of existing data in preparation for the new backup.
Explanation
System action
User response
CTGGI0015 The clean-up operation of the backup destination failed with an error message error.
Explanation
For details about the error, download the job command.log file.
System action
User response
CTGGI0016 Successfully completed the backup operation of the MongoDB instance.
Explanation
System action
User response
CTGGI0017 Backing up the MongoDB instance with database path database_path.
Explanation
System action
User response
CTGGI0018 Time elapsed: time seconds.
Explanation
System action
User response
CTGGI0019 MongoDB backup operation in progress.
Explanation
System action
User response
CTGGI0020 Starting MongoDB restore operation.
Explanation
System action
User response
CTGGI0021 The MongoDB restore operation cannot complete because the server information is missing.
Explanation
Information about the target MongoDB server is missing for the restore operation. Download the job log files and ensure that the input.json file includes the restore metadata attribute.
System action
User response
CTGGI0022 The MongoDB restore operation cannot complete because the server information is missing and the clean-up operation cannot complete.
Explanation
Download the job log files and ensure that the input.json file includes the restorecleanup metadata attribute.
System action
User response
CTGGI0023 The MongoDB restore operation cannot complete because the metadata for the clean-up information missing.
Explanation
Download the job log files and ensure that the input.json file includes the restorecleanup metadata attribute.
System action
User response
CTGGI0024 The MongoDB restore operation cannot complete because the MongoDB target server cannot shutdown.
Explanation
Download the job log files and ensure that the input.json file includes the restoreMetadata metadata attribute.
System action
User response
CTGGI0025 Database name: database_name.
Explanation
System action
User response
CTGGI0026 Source path for the restore operation: source_path.
Explanation
System action
User response
CTGGI0027 Starting MongoDB restore_type restore operation.
Explanation
Review details of whether this restore operation is a production or test restore operation.
System action
User response
CTGGI0028 Unable to find the process owner on the host from the backup named backup_name. Starting the MongoDB instance restore operation with the root user.
Explanation
The original owner of the mongod process that was backed up could not be found.
System action
User response
CTGGI0029 MongoDB restore operation finished successfully: instance=instance_name, database=database_name.
Explanation
System action
User response
CTGGI0030 Starting the MongoDB instance with the following command: startup_cmd
Explanation
Check the mongod process arguments such as the bind ip address, port, used configuration file, database path and log path.
System action
User response
CTGGI0031 MongoDB restore operation in progress.
Explanation
System action
User response
CTGGI0032 The MongoDB server name was shut down successfully.
Explanation
System action
User response
CTGGI0033 Starting command: cmd
Explanation
System action
User response
CTGGI0034 Generated the following MongoDB starting arguments: startup_cmd
Explanation
System action
User response
CTGGI0035 An error was encountered when listing the MongoDB connections.
Explanation
An error was encountered when the Python module netconnections attempted to retrieve the MongoDB port information. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0036 An error was encountered. The Python module netconnections was not found in the MongoDB application server folder.
Explanation
An error was encountered. The Python module netconnections was not found in the MongoDB application server folder.
System action
User response
CTGGI0037 The MongoDB inventory that was running is canceled.
Explanation
The MongoDB agent encountered an error during the inventory operation. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0038 Failed to connect the MongoDB instance name.
Explanation
Check that you entered the correct user ID and password, and that the mongod process is running.
System action
User response
CTGGI0039 Volume Group volume_group does not have enough free space to complete the action.
Explanation
Ensure that the volume group has enough free space for LVM snapshots during the backup operation. The volume group must have enough free space for the backup and inventory processes to run.
System action
User response
CTGGI0040 You have canceled the inventory operation.
Explanation
System action
User response
CTGGI0041 The primary member of the MongoDB replica set cannot be reached. The MongoDB admin command replSetGetConfig failed to run. Discovery of instance instance_name cannot continue due to invalid configuration.
Explanation
If you have enabled authentication for your MongoDB instance, check that the user was granted the clusterMonitor role.
System action
User response
CTGGI0042 Failed to dismiss the snapshot. Processing continuing.
Explanation
The LVM snapshot created during the backup could not be removed. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0043 Unable to run the backup for the instance because no matching MongoDB instance was found on this system.
Explanation
The MongoDB agent could not retrieve a running mongod the instance to backup. Ensure that then MongoDB instance was started correctly.
System action
User response
CTGGI0044 You have canceled the backup operation.
Explanation
System action
User response
CTGGI0045 The volume group of mount point mount_point has insufficient unallocated space for an LVM snapshot.
Explanation
Ensure that the volume group has enough free space for LVM snapshots during the backup.
System action
User response
CTGGI0046 The MongoDB could not find the command fsyncUnlock.
Explanation
The MongoDB instance was previously locked by executing the fssyncLock command. All pending write operations are flushed to disk and the entire mongod instance is locked to prevent additional writes until the lock is released by a corresponding fsyncUnlock command. The MongoDB agent could not find the command fsyncUnlock. Ensure that the command can be executed.
System action
User response
CTGGI0047 An error occurred when running fsynUnlock.
Explanation
The MongoDB instance was previously locked by executing the fssyncLock command. All pending write operations are flushed to disk and the entire mongod instance is locked to prevent additional writes until the lock is released by a corresponding fsyncUnlock command. The MongoDB agent could not find the command fsyncUnlock. Ensure that the command can be executed.
System action
User response
CTGGI0048 An error occurred when creating snapshot: name.
Explanation
The backup operation failed because the LVM snapshot could not be created. Check that there is not an existing volume group snapshot, and that there is enough space in the volume group for the backup operation. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0049 Backup failed because the path path_name could not be matched to a corresponding path at the target.
Explanation
Database paths for creating the snapshot must match. There was no matching snapshot found for a path. Download the job command.log and review it for further indications why the snapshot is missing. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0050 Error encountered during the incremental copying process.
Explanation
The Python module mongoincrementalcopy.pyc has failed to run successfully. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0051 Error occurred when making incremental changes to the backup copy.
Explanation
The Python module mongoincrementalcopy.pyc has failed to run successfully. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0052 An error occurred when creating the snapshot. Anything created in this operation will now be removed.
Explanation
Check if there is an existing snapshot of the volume group, and if there is enough space for the copy operation. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0053 You have canceled the restore operation successfully.
Explanation
System action
User response
CTGGI0054 The restore source restore_source chosen in the restore operation is not compatible with the recovery mode recovery_mode for this operation.
Explanation
Select a valid recovery mode.
System action
User response
CTGGI0055 The recovery mode recovery_mode is not valid for a restore operation with the target restore_destination
Explanation
System action
User response
CTGGI0056 You cannot restore data to the original location without the overwrite option selected.
Explanation
The MongoDB agent cannot overwrite existing data at the target because the overwrite option was not selected for this restore operation.
System action
User response
CTGGI0057 Restore type restore_type cannot be run for MongoDB.
Explanation
System action
User response
CTGGI0058 The recovered MongoDB instance cannot start because an existing MongoDB instance with pid process_id is already running in database_path.
Explanation
For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0059 Failed to shutdown server using MongoDB API due to error.
Explanation
The Python module pymongo used to create the API client has encountered errors. The shutdown command using the API client failed. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0060 Failed to shutdown MongoDB instance at connection.
Explanation
Check that the Python module shutdown is in the application agent folder. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0061 The command restorevalidate is not supported.
Explanation
System action
User response
CTGGI0062 The restore type restore_type and the source restore_source for the restore operation are incompatible. Check that the details of this restore operation and make the required changes.
Explanation
The fully qualified folder name of the MongoDB backup destination is not correct. The path must be correct to locate the source for the restore operation.
System action
User response
CTGGI0063 The restore type restore_type and the target destination for the restore operation are incompatible. Check the details of this restore operation and make the required changes.
Explanation
The fully qualified folder name of the MongoDB restore destination is not correct. The path must be correct to locate the destination for the restore operation.
System action
User response
CTGGI0064 The MongoDB server was shutdown before the restore cleanup command was issued.
Explanation
The MongoDb agent detected that the MongoDB server is not running.
System action
User response
CTGGI0065 Error in listing the MongoDB connections.
Explanation
Check that the Python module netconnections.pyc is in the MongoDB application agent folder. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0066 The Python module netconnections.pyc failed.
Explanation
Check that the Python module netconnections.pyc is in the MongoDB application agent folder. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0067 Error retrieving the MongoDB servers running on the host.
Explanation
The MongoDB agent was unable to query the running instances. Check that the Python module netconnections.pyc is in the MongoDB application agent folder. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0068 No address or host name and port was supplied for connecting to the MongoDB server.
Explanation
MongoDB instances are identified with a combination of hostname and port name. This information cannot be retrieved. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0069 Access denied. The Python module pymongo used to create the API client has encountered errors.
Explanation
If you have enabled authentication for the MongoDB instance, the user specified with credentials during host registration is used. Check that the user ID and password are correct, and check that the user has been granted the required roles for the MongoDB instance. For information about roles see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI0070 Failed to connect to the MongoDB server at address connection.
Explanation
MongoDB instances are identified with a combination of hostname and port name. This information cannot be retrieved. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0071 Unable to find the MongoDB server at host host_name port port_number.
Explanation
MongoDB instances are identified with a combination of hostname and port name. This MongoDB server is not reachable with the connection information provided. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0072 The option command_line_option was found in the MongoDB instance arguments but was not accepted during the restore operation when starting the MongoDB server.
Explanation
The option will be added to the MongoDB startup command that is used after restore operations.
System action
User response
CTGGI0073 Unable to find the volume mount point for file path path_name.
Explanation
The MongoDB agent could not retrieve the volume mount point file system type for the file path. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0074 Connection to MongoDB instance failed.
Explanation
MongoDB instances are identified with a combination of hostname and port name. When the MongoDB API was initialized an error occurred. For details about the issue and where it occurred, download the job command.log file.
System action
User response
CTGGI0075 Authentication failed.
Explanation
If you have enabled authentication for the MongoDB instance, the user specified with credentials during host registration is used. Check that the user ID and password are correct, and check that the user has been granted the required roles for the MongoDB instance. For information about roles see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI0076 You cannot backup MongoDB logs.
Explanation
The command logbackup is not supported.
System action
User response
CTGGI0077 Assigned user does not have access to the server_info command on the admin database.
Explanation
If you have enabled authentication for the MongoDB instance, the user specified with credentials during host registration is used. Check that the user ID and password are correct, and check that the user has been granted the required roles for the MongoDB instance. For information about roles see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI0078 Instance instance_name is a MongoDB sharded cluster which is not supported.
Explanation
Only MongoDB standalone instances and MongoDB ReplicaSets can be protected.
System action
User response
CTGGI0079 Instance instance_name has in-memory storage only which is not supported.
Explanation
The MongoDB agent supports only instances that write database files to disk.
System action
User response
CTGGI0080 Assigned user does not have access to getCmdLineOpts and serverStatus commands on the admin database.
Explanation
If you have enabled authentication for the MongoDB instance, the user specified with credentials during host registration is used. check that the user ID and password are correct, and check that the user has been granted the required roles for the MongoDB instance. For information about roles see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI0081 The volume group containing path_name does not have enough free space
Explanation
Ensure that the volume group has enough free space for LVM snapshots during the backup operation. For information about space requirements see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI0082 A MongoDB instance with more than a single LVM volume mount point cannot be protected.
Explanation
All MongoDB database files must be on a single LVM volume.
System action
User response
CTGGI0083 Retrieving information about the mount point of path_name has failed.
Explanation
The mount point could not be retrieved. Ensure that the path is correctly entered for this restore operation.
System action
User response
CTGGI0084 Unable to get information about the size of directory dir_name.
Explanation
The MongoDB agent could not retrieve the size of the database path correctly. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI0085 MongoDB server failed to start with command: startup_cmd
Explanation
The restored MongoDB instance could not be started after the restore operation. For details about the error and where it occurred, download the job command.log file. Fix the issues and retry the operation.
System action
User response
CTGGI0086 The specified restore target path path_name is invalid.
Explanation
The target path name that was specified in the restore wizard is not a valid path name. Valid path names have maximum of 4096 characters consisting of alphanumeric characters and the symbols . _ - /
System action
User response
CTGGI0087 The specified database name dbname is invalid.
Explanation
The database name that was specified in the restore wizard is not a valid MongoDB database name. Valid database names have 1 to 64 characters consisting of alphanumeric characters and the symbols . _ # -
System action
User response
CTGGI0088 The specified restore target path path_name must be empty or owned by user owner.
Explanation
The target path name that was specified in the restore wizard is not a valid restore target path because it is not empty and not owned by the right user. Change the owner of the target destination, and retry the operation.
System action
User response
CTGGI5001 Copied file argname1 / argname2 (argname3 %)
Explanation
System action
User response
CTGGI5002 Removing unrelated signature file file_name.
Explanation
System action
User response
CTGGI5003 Invalid header found for the signature file file_name. The file will be wiped.
Explanation
System action
User response
CTGGI5004 Validation of hashing algorithm failed.
Explanation
System action
User response
CTGGI5005 Incomplete signature header.
Explanation
System action
User response
CTGGI5006 Invalid signature header.
Explanation
System action
User response
CTGGI5007 Canceling copy operation on request.
Explanation
System action
User response
CTGGI5008 Argument chunk_size is below the limit of 1k: chunk_size.
Explanation
System action
User response
CTGGI5009 An error occurred when attempting to access file file_name.
Explanation
System action
User response
CTGGI5010 An error occurred then attempting to delete file file_name.
Explanation
System action
User response
CTGGI5011 Inconsistent signature file: signature_file_name.
Explanation
System action
User response
CTGGI5012 An error occurred while copying data from file argname1 to file argname2.
Explanation
For details about any errors and where they occurred, download the job command.log file.
System action
User response
CTGGI5013 An error was encountered because the num_workers argument cannot have a value of 0.
Explanation
System action
User response
CTGGI5014 When copying data from file argname2 to file argname3 the operating system reported an error: argname1.
Explanation
For details about any errors in the copying process and where they occurred, download the job command.log file.
System action
User response
CTGGI5015 When copying data from file argname1 to file argname2, the target machine has run out of available space.
Explanation
check that the capacity for backup storage on the dashboard. If there is not enough space, increase the capacity by adding disk storage. Retry the operation.
System action
User response
CTGGI5101 A backup operation is in progress.
Explanation
System action
User response
CTGGI5102 A restore operation is in progress.
Explanation
System action
User response
CTGGI5103 Snapshot size: snap_size
Explanation
System action
User response
CTGGI5104 Received unknown operation: operation_name
Explanation
System action
User response
CTGGI5105 An error occurred when creating the snapshot: exception
Explanation
The backup operation failed because the LVM snapshot could not be created. Check that there is not an existing volume group snapshot, and that there is enough space in the volume group for the backup operation. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5106 An error occurred when creating the snapshot: exception
Explanation
The creation, mounting, unmounting or removal of a LVM snapshot failed. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5107 An error occurred when creating the snapshot: exception
Explanation
The exception occurred during creation, mounting, unmounting or removal of a LVM snapshot failed. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5108 Failed to calculate the snapshot size for the mounted volume on mount point mount_point.
Explanation
The system command df ran into problems and could not determine the size of the snapshot. For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5109 Mounting of snapshot volume vol_name failed.
Explanation
Download the job command.log and review it for further indications of the failure.
System action
User response
CTGGI5110 Failed to unmount snapshot snapshot_name from mount point mount_point.
Explanation
Download the job command.log and review it for further indications of the failure.
System action
User response
CTGGI5111 Snapshot volume snapshot_name could not be mounted.
Explanation
For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5112 Snapshot volume vol_name has errors that cannot be recovered from.
Explanation
The snapshot could not be checked and repaired. For details about the errors and where they occur, download the job command.log file.
System action
User response
CTGGI5113 Failed to create snapshot for logical volume vol_name.
Explanation
Download the job command.log and review it for further indications of the failure.
System action
User response
CTGGI5114 Failed to enumerate existing logical volumes.
Explanation
For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5115 Failed to determine the file system path for the snapshot volume vol_name.
Explanation
For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5116 Failed to determine logical volume path from the mount point mount_point.
Explanation
For details about the error and where it occurred, download the job command.log file.
System action
User response
CTGGI5117 The mount point mount_point you specified is not a valid directory.
Explanation
Check the mount point of the database volumes are accurate existing directories.
System action
User response
CTGGI5118 Ensure you are running the application agent in a supported environment.
Explanation
For information about system requirements, see the Knowledge Centre:For information about space requirements see the IBM Knowledge Centre: https://www.ibm.com/support/knowledgecenter/SSNQFQ/landing/welcome_ssnqfq.html.
System action
User response
CTGGI5119 Command line 'cmdline has ended with exit code exitcode.
Explanation
The specified command ended with error. Console output is: 'stdout' Console error output is: 'stderr'
System action
User response
CTGGI5120 The target location path is not suitable for the operation as it is located on the root file system.
Explanation
The specified path is part of the root file system. Ensure that the path is located on a dedicated file system which is mounted to the root file system.
System action
User response
CTGGI5121 The target location mount_point does not have enough free space for the operation.
Explanation
The specified location has insufficient free space. The required capacity is {1} MB but the actual free space is {2} MB.