Synology Drive Client 4.0.2 Issues

[midnight_Lightning]

One of my PC's stopped syncing after installing v 4.0.2 client - perhaps because it hadn't been used for several months? I left it to run and whilst it did sync some files, others were missing. Also lots of files with Red Crosses in the working directory.

I then found the same red crosses on other PC's although these appear to have synced correctly.

I uninstalled Drive from each PC, deleted the client Drive Folder, Rebooted, Download and re-Installed the client and set up the sync task from scratch.

All PC's appear to have synced correctly but the red crosses still appear in the working directory. The "Sign" directory has hundreds of folders/sub-folders with Red crosses.

The syncing appears to be working but the red crosses are freaking me out - I cant afford any issues?

Thoughts/Solutions?

 

[h_smith]

I use 4.02. Once the internal database for Synology Drive becomes corrupted, you cannot really trust it. On Windows, the files are stored here:

C:\Users\<User>\AppData\Local\SynologyDrive

The database for everything that has been backed up is stored here:

C:\Users\<User>\AppData\Local\SynologyDrive\data\db

The dilemma with Drive Client is that it does not perform any verification of your local files to ensure that they are indeed backed up on your NAS if you wipe out the database and re-setup the client. It only stores new file changes. This presents a hazardous situation if you believe that you are properly backed up, but you are not.

That being the case, If you are running with a corrupt Drive Client database for some period of time, you have no idea what is actually backed up on the NAS. The longer the corruption went undetected, the more missing files you will have on your NAS.

I looked around for a solution to this problem, a tool to verify what is actually backed up on the NAS, and for the most part, I found nothing that worked for me. This is especially true if you are dealing with terabytes of data and many files.

You would think that Drive Client would have your back, verifying local versus NAS files, but that doesn't exist (from my observation).

I wrote a utility to perform this verification (for Windows) but as of yet, I have not posted it online.