I am using MSP360 Connect Free. Lately, I have been getting this message -
It then lists the files. I went to edit the Backup plan. In the choice for “Do not back up files of these types,” I put “Sparce” in the blank, but it didn’t work -
What are “sparce” files? How do I get rid of the error next time I back up?
K1ESE, John
It looks like you’re referring to MSP360 Backup, not MSP360 Connect Free (our remote desktop product). The warning in your screenshot is generated by MSP360 Backup.
I assume the product names were mixed up. Please confirm you are using MSP360 Backup
Also, could you confirm which operating system you’re backing up (Windows, Linux, or macOS)? Based on the warning, it may help explain why those files were skipped.
Yes, I am using MSP360 Backup, sorry for my confusion. I’m using Windows 11. After using MSP360 Backup successfully for months, this error has shown up in the last few days.
Grateful for help,
John K1ESE
First, there’s nothing critical with your backup right now. Your existing backups in the cloud are safe.
The first warning (1622) indicates that some files couldn’t be backed up because MSP360 Backup didn’t have permission to access them. The backup report should list those files so you can identify what was skipped. If the report doesn’t include them, we’ll need to review the backup logs.
The second message (1551) is informational rather than a warning. It indicates that MSP360 Backup skipped sparse files, as backing up sparse files isn’t currently supported. What’s unusual in your screenshot is that it only shows C: without any additional file details.
Overall, your backups should be fine. To investigate the warnings further, could you please share the backup logs with us?
To send logs directly from the MSP360 Backup agent, go to Tools > Diagnostic in the program menu. In the diagnostic window, fill in your email address, add a brief description of the issue, and click Send to automatically submit the logs to the support team
The logs have been sent. Thank you for your assurances that my data is safe.
Regards,
K1ESE John
Our support engineer updated the ticket with a suggested resolution. Let me know if anything else comes up
