Skip to main content
Druva Documentation

Troubleshoot Could not add storage. The data folder for storage is not accessible or is not a directory error

 

Problem description

This article explains the troubleshooting steps to resolve the below error message:

Could not add storage. The data folder for storage is not accessible or is not a directory

clipboard_e1657565970deef92a619e0ee9c4deadf.png

This error appears while adding a storage to an inSync On-Premise environment. This error is mostly seen if the Data component of the Storage is on a NAS location.

Cause

There could be several causes for this error. Following is the list of most common reasons for this error:

  • The storage registration failed or had some issues during the registration process.
  • The NAS location is not accessible or incorrect service account credentials are being used.
  • Any handle of the antivirus or other 3rd party applications are not allowing the inSync processes to come up in the Task Manager.
  • Parameters such as IP, Port, Hostname, Service, User, and so on in the configuration file of the Storage node are incorrect or are being changed due to an handle of any other 3rd party application.

Resolution

  1. Make sure that the NAS Location is accessible from the Storage node.
    If it is accessible, make sure that you have the right to perform Read/Write operations on the location. (Create a test .txt file, and add some text, and save the file. Try to delete the file. If you are able to successfully delete the file, you have the required rights.)
  2. Make sure that the service account credentials are correct.
  3. Try to re-register the storage node in the inSync Management Console once using the Registration key from the Druva inSync Storage Node application.
  4. Make sure that the Log On as Service window for Druva Storage Node service in services.msc has the latest credentials for the service account.
  5. Check and verify the service account permissions for the below locations. We need Full Control of the service account for the following locations:
    1. C:\Programdata\Druva
    2. C:\ProgramFiles\Druva
    3. C:\Windows\Temp
  6. In the task manager, check if all the related inSync processes are up and running. Make sure that there is no process that although keeps up and running, but then crashes. List of all the required processes:
    1. inSyncBynamo.exe
    2. inSyncNodeMaster.exe
    3. inSyncNodeMasterCfg.exe
    4. inSyncNodeMasterSVC.exe
    5. inSyncStorageMaster.exe
    6. inSyncWorker.exe
      The count of the inSyncBynamo.exe and the inSyncWorker.exe process could be based on the number of storages associated with this storage.
  7. In the inSync Management console, click the name of Storage Node and under Storage Node Server Credentials, check if it says: Node Not Reachable and if Yes, proceed to the next step.
  8. Make sure that the below values are correct in the Storage Node Configuration Window (the application on the storage node after installing the msi).
    1. IP Address/FQDN
    2. Backup/Sync Port
    3. User Web Access Port

You need to stop the Druva inSync Storage Node service and kill all the inSync processes running in the Task Manager before making any changes to the cfg file. Also, please verify the changes made for the cfg file.

 

  1. Make sure that the ports being used in the configuration file of Storage Node (inSyncServerStorage.cfg) are correct (Backup/sync port and web panel port). Check the following parameters:
    1. SERVERS
    2. SYNC_PORT
    3. EDGESERVER_PORT=8015
  2. Make sure that the Hostname and IPs being used in the configuration file of Storage Node (inSyncServerStorage.cfg) are correct (Backup/sync port and web panel port). Check the following parameters:
    1. MDM_HOST
    2. SERVERS
    3. WR_IP
    4. UA_IP
  3. Make sure that the 'CLOUD_KEY' parameter that's being used in the configuration file of the Storage Node (inSyncServerStorage.cfg) is correct (Backup/sync port and web panel port). You can compare the same from in the master server's configuration file (inSyncServer.cfg ). If it's different, you can copy-paste the file from master server's cfg to the Storage Node's cfg.
  4. Make sure that value for below parameters are correct:  
    1. SERVICE_PASSWORD (Note service_password is an encrypted value.)
      Example: QlpoOTFBWSZTWbGEO0gAAASPgEA4IYCFACAQEYAgACIQaY1HlCmAAB3MxKoBElfF3JFOFCQsYQ7SAA==
      (Passwords this long is usually encrypted for service account, or else, the password for local account is also encrypted but are of lot less characters.
    2. SERVICE_USER
      (It should be a service account. If it is LOCALSYSTEM, that means the service account credentials did not get implemented in the cfg file.)
  5. Make sure there is no other process/application/service trying to put a handle on inSync processes and suppressing them or not allowing them to launch by using handle.exe or Microsoft Process Monitor tool.
  6. Make sure that the Antivirus Exclusions for both Master server and Storage node are in place as per the recommendations in the Antivirus recommendations for inSync article.

Verification

Once done, all the inSync processes should come up and should be visible in the Task manager and you should be able to add storage without any issues.

  • Was this article helpful?