Using SyncBackPro > Technical Reference

warning

Support for Egnyte is deprecated and may be removed in a future version of SyncBackPro.

Prior to March 2024, SyncBackPro connected to Egnyte using a special 2BrightSparks Key and Secret. A Key and Secret is like a username and password. It identified that it was SyncBackPro connecting to Egnyte. However, due to policy changes at Egnyte, software that uses Egnyte must supply their own credentials which you must retrieve from Egnyte.

Please contact Egnyte about getting an API Key and Secret. SyncBackPro is a public application that uses the Authorization Code method. During the application registration ensure that the application is marked as "Publicly Available Application":

egnyte-type

For the "Registered OAuth Redirect URI" you can use ours: https://www.2brightsparks.com/syncback/syncbackpro/egnyte.php

If during the authorization procedure (through SyncBackPro) you receive the following error then most likely you have registered the API Key as being Private:

{"errorMessage":"Incorrect request type GET for resource owner flow. Please check the documentation and try again."}

Once you have a Key and Secret you can use it in the Cloud Accounts so that you no longer need to enter it again.

IMPORTANT: The Egnyte plan you have limits how frequently SyncBackPro can call the Egnyte cloud service. If you are being throttled (receiving HTTP 429 errors) please contact Egnyte to increase your limits. State that you are using SyncBackPro and ask to increase the number of calls to the desired amount, and the reason it is needed, e.g. migration.

information

Note: files with an older modified date

Egnyte decides which version of a file is current by its modified date, not by the order in which versions were uploaded (see Egnyte's article on file versions). SyncBackPro uploads files with their real modified date. If the file already on Egnyte has a newer modified date than the file being uploaded, Egnyte stores the upload as an older, non-current version and keeps showing (and returning) the previous content. When this happens the profile run reports success, but the file is copied again on every later run because its date on Egnyte never matches the source, and restoring the file from Egnyte returns the newer content rather than what was just backed up.

This can happen when the source file is replaced by a copy with an older modified date (for example, an old copy restored from another backup, extracted from an archive, or copied from another computer with its date preserved), or when the file on Egnyte was changed later (in the Egnyte web interface, by another user or by another application) and SyncBackPro then overwrites it with the source file. To work around it, do one of the following:

1.Update the source file's modified date to now before the run, either by opening and saving it, or by running (Get-Item "C:\path\file.ext").LastWriteTime = Get-Date in PowerShell (replace the path with the path of your file).

2.Delete the file on Egnyte, then run the profile again.

3.In the Egnyte web interface, open the file's version history and restore the version you want. Egnyte gives a restored version the current time, so it becomes the current version.

For more details, see this knowledge base article.