A user is defined as one personalized email address (for example, name@yourcompany.com) whose cloud account is synced, backed up, or migrated. Even if this user uses multiple cloud apps (Dropbox, Salesforce, etc.), we still count it as one user. In the case of Egnyte, one Egnyte power user is equal to one cloudHQ license.

To back up the Egnyte Shared folder and your Egnyte has 18 power users, you will need 18 cloudHQ Backup and Sync licenses.

Yes, you can backup Egnyte to Office 365 SharePoint document library. To setup a backup just create one-way backup sync pair from Egnyte Shared folder to Office 365 SharePoint document library folder. To start the wizard just go here: https://www.cloudhq.net/backup/egnyte/office365_sharepoint

The following cloud storage providers are compatible for use as a destination in a cloudHQ backup operation:

1. Dropbox
2. Google Drive
3. Google Shared Drives
4. Box
5. Office 365 Sharepoint Document Libraries
6. Office 365 OneDrive
7. Amazon S3

You can find a shortcut to the cloudHQ dashboard for backing up data from Egnyte to Amazon S3 at cloudHQ: Egnyte to Amazon S3 Backup.

When you enable “archive files before they are deleted or modified,” cloudHQ protects your data in real time. Every change is backed up right away, so nothing is lost.

When a file is deleted, removed, or renamed, cloudHQ saves the previous version in cloudHQ_archive folders. This folder will be created after initial data transfer finishes and you made a first change on the Egnyte side.

Let’s say your sync pair is:

Egnyte (admin)/Shared   -> Amazon S3/backup_bucket

Now assume the file Shared/ClientTemplates/Contract_template.docx is modified in Egnyte. As soon as the file changes, cloudHQ will:

– Create a folder named cloudHQ_archive under Amazon S3/backup_bucket.
– Create date/time subfolders for when the change happened:

Amazon S3/backup_bucket/cloudHQ_archive/2016/Jun 2016/01 Jun 2016 (wed)/2016-06-01T17_58_55

– Archive the old version from its live location:

Amazon S3/backup_bucket/Shared/ClientTemplates/Contract_template.docx

to the archive folder:

Amazon S3/backup_bucket/cloudHQ_archive/2016/Jun 2016/01 Jun 2016 (wed)/2016-06-01T17_58_55/Shared/ClientTemplates/

The archived file will be:

Amazon S3/backup_bucket/cloudHQ_archive/2016/Jun 2016/01 Jun 2016 (wed)/2016-06-01T17_58_55/Shared/ClientTemplates/Contract_template.docx

– Copy the updated file from:

Egnyte (admin)/Shared/ClientTemplates/Contract_template.docx

to:

Amazon S3/backup_bucket/Shared/ClientTemplates/Contract_template.docx

End result:
– The latest version (current backup) is at:

Amazon S3/backup_bucket/Shared/ClientTemplates/Contract_template.docx

– The previous version is at:

Amazon S3/backup_bucket/cloudHQ_archive/2016/Jun 2016/01 Jun 2016 (wed)/2016-06-01T17_58_55/Shared/ClientTemplates/Contract_template.docx

No, not directly. cloudHQ does not have a “quiet hours” or “off-peak window” setting. You cannot say *”sync every 10 minutes except 9 AM–5 PM.”* What you can do — using the “Adjust the granularity of your sync or backup process” option in the sync pair settings:

This option is a dropdown in the sync pair’s settings page that controls how often the sync runs (the “granularity”). Choices range from “check and sync every 1 minute” all the way up to “check and sync every 1 month”. Lower granularity = fewer, less frequent runs = fewer API calls.

Using it to approximate off-peak behavior:

• Pick a lower granularity (e.g. “every 1 hour” instead of “every 10 minutes”) – reduces the total volume and rate of API calls across the day.
• If you choose a granularity of “24 hours, 7 days, or 1 month”, an additional “Starting at” picker appears below the dropdown — you can set the exact hour, timezone, and day of week/month. So a once-a-day Egnyte sync can be set to run at, say, 2 AM Pacific.

Bottom line: there’s no way to block out specific hours, but you can push the whole sync into off-peak time if you’re willing to sync only once a day (or less often).

Egnyte sync pairs default to every 10 minutes. You can change this in the sync’s settings to anything from 1 minute up to 1 month.

Yes. When the sync frequency is “24 hours or longer” (daily, weekly, monthly), the UI lets you pick:

• the start hour (with AM/PM),
• the timezone,
• for weekly syncs: the day of the week,
• for monthly syncs: the day of the month

For frequencies shorter than 24 hours (e.g. every 10 minutes, every hour) you cannot pin a start time — the sync runs continuously on that cadence.

Scheduling won’t move calls to off-peak hours, but reducing the granularity (running the sync less often) will reduce burst impact. The sync pair settings page shows a notice for Egnyte users specifically, right under the granularity dropdown:
Egnyte is limiting API calls, so please adjust the granularity of your sync or backup process. If you need to reduce the number of Egnyte API calls, you can decrease the granularity of your sync or backup process. If you need real-time sync (which will cause higher usage of Egnyte API calls), you can increase the granularity of your sync or backup process.

Yes, automatically — separate from the schedule. cloudHQ throttles outgoing Egnyte API calls. You don’t configure this — it runs in the background to keep cloudHQ from blowing through Egnyte’s quota.

Yes, indirectly. Each sync pair has its own frequency setting. So if you have a “Critical Docs” sync pair and an “Archive” sync pair, you can configure one to run every 10 minutes and the other to run daily at 2 AM. There’s no per-subfolder schedule within a single sync pair.

Not as a built-in feature. You’d have to either:

• Set the sync to a long enough frequency that it effectively only runs once a day at the start hour you choose, or
• Manually pause/resume the sync pair around business hours.
There is no scheduled pause/resume window.

1 month. The frequency selector goes from every 1 minute up to once per month, with intermediate options (5 min, 10 min, 30 min, 1 hour, 6 hours, daily, weekly, monthly).