Backup Egnyte: FAQ (Frequently Asked Questions)

How does cloudHQ counts number of license?

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.

Can I backup Egnyte to Office 365 SharePoint?

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

Which cloud storage services can be used as target for cloudHQ backup?

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

Where I might find a shortcut or a simplified guide for backing up data from Egnyte to 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.

How does Egnyte backup work? How does cloudHQ ensure real-time data protection?

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

—

Tagged: