Skip to main content
commvault.com commvault.com
Solved

Could not get SIDB folders error on cluster drive

  • October 25, 2022
  • 3 replies
  • 557 views
G
Byte
Forum|alt.badge.img+10

I am backing up a cluster, but each cluster drive has its own subclient

All the other drives on their own subclient are backing up fine.

There are 2 errors I see.

  1. Process(72) - Could not get SIDB folders; cannot exclude SIDB folders from this backup
  1. ERROR CODE [17:49]: Failed to further divide the collect files. Possible reasons: nonexistent path/file, hardware problems or full disk.

The job for the cluster subclient run for over 30 hours before failing.

The check readiness indicates there is no error on the sublient,

Anyone have ideas on what logs I should look at the find the root cause.

Best answer by gary mcneely

SOLVED:

the reason for this particular failure was the drive the job results folder resides on is FULL.

View original
Did this answer your question?

3 replies

G
Vaulter
Forum|alt.badge.img+11
  • GseibakVaulter
  • Vaulter
  • 118 replies
  • October 25, 2022

Hi Gary ,  

 

Great name BTW :)

 

is it hung on the scan phase of the job?

 

check the output of command “vssadmin list writers” 

you may just have to reboot that client to clear it up.

Gary Seibak - TAM Commvault
Mike Struening
1 person likes this
  • Mike Struening
    Mike Struening
C
Vaulter
Forum|alt.badge.img+14

Hello @gary mcneely 

The errors indicate some issue with the DDB. Can you confirm:

  • The DDB partitions are reporting online in the GUI?
  • The DDB drive on the Media Agent is connected and online
  • The DDB Files exist in the location they are supposed to be on the drive
  • You can check clBackup.log & SIDBEngine.log on the Media Agent for further errors
  • Confirm AV exclusions are in place - https://documentation.commvault.com/11.23/expert/8665_recommended_antivirus_exclusions_for_windows.html
  • Confirm if you have a log on the Media Agent called “DLPAlerts.log” and if so, when was the most recent update to the log?

Thank you,
Collin

G
Byte
Forum|alt.badge.img+10
  • gary mcneely
  • Author
  • Byte
  • 39 replies
  • Answer
  • November 9, 2022

SOLVED:

the reason for this particular failure was the drive the job results folder resides on is FULL.

Mike Struening
G
C
3 people like this
  • Mike Struening
    Mike Struening
  • G
    Gseibak
  • C
    Collin Harper

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings