Failed to initialize RemoteBDB.Cloud. Error=[BlockDBConfig.readConfig]

Data backup applications Ahsay
1

Issue ater upgrading to 8.3.0.20 Failed to initialize RemoteBDB.Cloud. Error=[BlockDBConfig.readConfig] unknown default path for creating new journal file config: 0, caused by [RuntimeException]

1 Like
2

Hi,

It seems that there is an issue with the index file. Could you run a Data Integrity Check with CRC enabled to check on the problem? For details on how to perform a “Data Integrity Check”, please refer to the following FAQ article “How do I ensure the data integrity of the files in my backup sets?” viewtopic.php?f=58&t=81

3

Nice one, thanks Umer.

Since we installed 8.3.0.30, it looks like the index files stored locally in.obm have been upgraded to SQLite. Any idea on the benefits of this and what it means?

Considering the upgrade caused the index corruption, I guess SQLite hasn’t fixed that constant bug?

4

Hi,

The problem is with the index on the destination. As you are using a pooled destination, can you advise how many cloud destination has been pooled?

Also, from the image we can see that CRC had not been enabled for the check. Could you run the check again with CRC enabled?

5

Here’s a detailed explanation to help you fix the issue:

Issue Description

The problem arises after upgrading to version 8.3.0.20, where there is a failure to initialise RemoteBDB.Cloud due to an unknown default path for creating a new journal file.

Suggested Solution

  1. Run a Data Integrity Check with CRC Enabled:
    • This step is crucial to identify any corruption or issues within the data files.
    • Ensure that CRC (Cyclic Redundancy Check) is enabled during this process to verify the integrity of the data.
  2. Upgrade Impact:
    • The index files have been upgraded to SQLite in version 8.3.0.30.
    • Despite this upgrade, the index corruption issue might persist, indicating that the root cause has not been fully addressed.

Additional Troubleshooting Steps

  1. Verify the Default Path:
    • Check the configuration settings to ensure that the default path for creating new journal files is correctly specified.
    • If the path is incorrect or undefined, update it to a valid directory.
  2. Check Pooled Cloud Destinations:
    • Ensure that the pooled cloud destinations are correctly configured.
    • Misconfiguration in cloud destinations can lead to initialisation failures.
  3. Enable Detailed Logging:
    • Enable detailed logging to capture more information about the error.
    • Review the logs to identify any specific errors or warnings that could provide more insight into the issue.
  4. Consult Documentation and Support:
    • Refer to the official documentation for any additional troubleshooting steps or updates related to this issue.
    • If the problem persists, contact the support team for further assistance.

Detailed Explanation

  1. Running a Data Integrity Check:
    • Navigate to the data integrity check tool in your application.
    • Enable CRC to ensure a thorough check.
    • Run the check and review the results for any errors or warnings.
  2. Verifying the Default Path:
    • Open the configuration file or settings menu.
    • Locate the setting for the default path for journal files.
    • Ensure it points to a valid directory with appropriate permissions.
  3. Checking Pooled Cloud Destinations:
    • Access the cloud settings in your application.
    • Verify that all cloud destinations are correctly configured and accessible.
    • Test the connection to each destination to ensure they are working properly.
  4. Enabling Detailed Logging:
    • Go to the logging settings in your application.
    • Increase the logging level to capture detailed information.
    • Reproduce the issue and review the logs for any specific errors.

You should be able to identify and resolve the issue with RemoteBDB.Cloud. If you encounter any difficulties, don’t hesitate to reach out for further assistance.