File Store Archives / Backups

The Enterprise File Fabric Archive/Backup feature enables the archiving of a public or private file store to a secondary public or private file store (or a different region / bucket of the primary file store).

It can be used to backup Google Drive files to Amazon S3 for example or to archive a local WebDav Server to RackSpace etc. The combinations are limited only by the file stores that are supported by the File Fabric.

The aim is to ensure high availability of data with two different data stores be they public or private.

For the purpose of this overview we'll assume an archive from Google Drive to the DropBox Cloud, but typically please note that we would recommend an archive/backup from a consumer file store object storage rather than a consumer file store to another consumer file store. The reason for this is the API throttling and limitations that can be triggered on consumer file stores

1. Log into an account either on the File Fabric SaaS service or an enterprise on-premises deployment  
   2. Navigate to the Admin Account DashBoard
   3. Choose to add a new Backup provider and choose DropBox

   2 Request DropBox access

The DropBox OAuth screen will appear an you can sign into DropBox and choose to authorise access

A resync (meta sync) of the primary file store (Google Drive in this example) will now commence and as files are validated or found this will precipitate each file being added to the newly nominated DropBox Backup that has just been added.

When the Archive completes the primary file store (Google Drive) files have been backed up / archived to the secondary data store (DropBox).

Any subsequent files that are uploaded direct to Google Drive using the File Fabric will also be instantly archived/backed up to DropBox. If any files that are uploaded direct to Google Drive (ie. not through the File Fabric) they will also be uploaded to DropBox when the File Fabric next discovers them (either on a refresh or a resync of the metadata).