Synametrics Technologies

The RWP file I've created doesn't seem to get placed onto our test client after running the backup manually, nor does it seem to get placed onto the client when the backup is run automatically. I've created "C:\Syncrify\RansomwarePrevention\donotdelete.jpg" and ensured "donotdelete.jpg" name matches in the configuration on the Syncrify server.

The test computer we're running this on is set to backup:

C:\Users (all subcontent)

C:\CompanyName (all subcontent)

The file "donotdelete.jpg" does not appear in "C:\Users" or "C:\CompanyName" as expected. Can anyone shed light as to why this behavior isn't working as intended?

Mark,

Please look for errors in SyncrifyClientGUI.log file for details. I have a feeling you're running into some permission problems. Normally, Syncrify Client only needs READ-ONLY permission on folders to perform backups. Creating the bait file is the only time when Syncrify Client will need READ/WRITE permission on the top-level folder.

You would run into permission problems if the OS is denying WRITE permission to certain folders. In that case, you will have to copy this file manually and ensure the last modified date of the file does not change.

For anyone wondering, it boiled down to the file extension on the actual file being there twice. You can check this in the log file found by installation default at C:\Syncrify\logs\Syncrify.log

You'll be looking for a line similar to:

2019-12-25 05:25:14,341 ERROR handler.RansomwareHandler - Expected ransomware file was not found. Cannot send meta. File: RansomwarePrevention\<your_file_here>.ext (where ".ext" is the extension of your file)

in our case, we got the error on File: "RansomwarePrevention\do_not_delete.jpg" ... When we went to C:\Syncrify\RansomwarePrevention on our server, we realized the file was saved as "do_not_delete.jpg.jpg" ... Removing the extraneous extension solved the issue. Thank you to Syncrify's amazing support team for figuring this out for us so quickly.