Skip to main content
Question

Error Code: [17:90] Issue with FS backup (11.28.44)

  • June 24, 2024
  • 1 reply
  • 87 views

Forum|alt.badge.img+2

The error sates:

 

Error Code: [17:90]
Description: The following subclient content [C:\LOTS\Backup\LOTS.zip: error(2: The system cannot find the file specified.) ,C:\LOTS\Certs: error(2: The system cannot find the file specified.) ,C:\LOTS\OrderBackups: error(2: The system cannot find the file specified.) ,C:\LOTS\PersonFiles: error(2: The system cannot find the file specified.) ,C:\LOTS\Photos: error(2: The system cannot find the file specified.) ,C:\Program Files (x86)\MedAdvisor\MedAdvisorService\spsc.sqlite: error(3: The system cannot find the path specified.) ,C:\Program Files (x86)\MedAdvisor\MedAdvisorService\spsc.sqlite-shm: error(3: The system cannot find the path specified.) ,C:\Program Files (x86)\MedAdvisor\MedAdvisorService\spsc.sqlite-wal: error(3: The system cannot find the path specified.) ,C:\WebstercareMMS\Access: error(3: The system cannot find the path specified.)] could not be scanned. If content under these paths was backed up at some point in the past, it might not get deleted from media as this could be a temporary issue. Please revie

 

But the files are backed up. And able to restore.

Is there an explanation for this?  Shall I ignore this kind of error?

 

Appreciate it.

Thanks,

 

1 reply

Forum|alt.badge.img+11

Hi RicM,

this is a typical error which happens if the file was there during the scan phase and has been deleted meanwhile when the later backup phase of the job tries to read the file.

So, it might be that the failed files are included in a previous backup and can be restored from there transparently, but I don’t think it is in the latest backup that threw these errors.

In case it is really in that specific job, then please open a ticket with our Support to analize in detail as this is not expected behaviour.


Reply


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