Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cloudbackup [2018_10_26 12:59] – [5 Backup/Archive Completed] jimcloudbackup [2024_02_28 01:03] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ====== File Store Archives / Backups ====== ====== File Store Archives / Backups ======
  
 +Access Anywhere 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 Access Anywhere.\\ \\ The aim is to ensure high availability of data with two different data stores be they public or private.\\ \\ *Please ensure a backup provider is chosen that is not subject to throttling or rate limiting else the backup provider will not be able to perform as required.* \\ \\ 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
  
-\\ \\ 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 Add a Archive / Backup File Store ===== ===== 1 Add a Archive / Backup File Store =====
- 
  
  
 {{ :dropbox_gdrive_backup_updated.png?400 |}} {{ :dropbox_gdrive_backup_updated.png?400 |}}
  
-1. Log into an account either on [[https://storagemadeeasy.com|the File Fabric SaaS service]] or [[https://storagemadeeasy.com/ownFileserver/|an enterprise on-premises deployment]]  \\ 2. Navigate to the Admin Account DashBoard \\ 3. Choose to add a new Backup provider and choose DropBox +1. Log into an admin account  
-===== 2 Request DropBox access =====+ 
 +2. Navigate to the Admin Account DashBoard 
 + 
 +3. Choose to add a new Backup provider and choose Dropbox 
 + 
 + 
 +===== 2 Request Dropbox access =====
  
  
Line 21: Line 26:
  
  
-===== 3 Authorise DropBox access =====+===== 3 Authorise Dropbox access =====
  
  
Line 27: Line 32:
 {{:/cloudbackup:steps:sme_3_authorise_dropbox_ac.png}} {{:/cloudbackup:steps:sme_3_authorise_dropbox_ac.png}}
  
-The DropBox OAuth screen will appear an you can sign into DropBox and choose to authorise access+The Dropbox OAuth screen will appear and you can sign into Dropbox and choose to authorise access
  
  
Line 33: Line 38:
  
  
-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.+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.
  
  
Line 40: Line 45:
  
  
-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). +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 directly to Google Drive using Access Anywhere will also be instantly archived/backed up to Dropbox. If any files are uploaded directly to Google Drive (ie. not through Access Anywhere) they will also be uploaded to Dropbox when Access Anywhere next discovers them (either on a refresh or a resync of the metadata). 
  
 ===== 6 Additional Backup/Archive Settings ===== ===== 6 Additional Backup/Archive Settings =====
Line 64: Line 69:
 If the primary file store is down when trying to access a file the backup/archive file store will be used to retrieve the file providing business continuity in the event of an outage. If the primary file store is down when trying to access a file the backup/archive file store will be used to retrieve the file providing business continuity in the event of an outage.
  
-===== 9 Summary ===== 
  
-Although we used Google Drive to DropBox as an example this is equally applicable to any of the [[https://storagemadeeasy.com/cloud_list/|60+ file stores]] that the File Fabric supports, including private file stores to public file stores or vice-versa.\\ \\+