N-Able is a popular backup and recovery software used by many organizations to ensure their data is safe and recoverable in the event of an unexpected loss. However, like any other software, it can encounter errors that can disrupt the backup process. One such error is the “The tag present in the reparse point buffer is invalid. (4393)” error. This error can occur when doing an N-Able Cove Data Protection backup and can be frustrating to deal with. In this article, we will explore the steps to fix this error.
Step 1: Check for Corrupt Files
The “The tag present in the reparse point buffer is invalid. (4393)” error can occur due to corrupt files. I have found that it is mostly files that are in OneDrive. Use the CHKDSK utility to check for any corrupt files on the backup source drive. CHKDSK is a Windows utility that checks for errors on a disk and can fix them if necessary. To use CHKDSK, follow these steps:
- Open the Command Prompt as an administrator.
- Type “chkdsk C: /r /f” and press Enter. (C: would be the drive letter the error occurred on)
- CHKDSK will ask if the scan should be scheduled on the next restart, type “Y”.
- Restart the computer and let the scan complete.
- Rerun the backup.
Step 2: Disable Reparse Points
Another cause of this error is reparse points. Reparse points are a feature in Windows that allows files to be tagged with metadata that can be used by applications. However, if the reparse point is invalid, it can cause the “The tag present in the reparse point buffer is invalid. (4393)” error. To disable reparse points, follow these steps:
- Open the Command Prompt as an administrator.
- Type “fsutil behavior set disablelastaccess 1” and press Enter.
- Type “fsutil behavior set disablelastaccess 0” and press Enter.
In conclusion, the “The tag present in the reparse point buffer is invalid. (4393)” error can be frustrating to deal with when doing an N-Able Cove backup. However, by following the above steps, you can easily resolve the error and ensure that your backup process is smooth and hassle-free. Remember to check for corrupt files and disable reparse points to fix the error.