# Backup entire workspace? **URL:** \ **Category:** Ideas & Features\ **Created:** [March 5, 2020, 4:56pm UTC](https://community.fibery.io/t/backup-entire-workspace/595 "2020-03-05T16:56:07Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Luke\_VanderHart](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/luke_vanderhart/32/488_2.png) [@Luke\_VanderHart](https://community.fibery.io/u/Luke_VanderHart)\ **Post date:** [March 5, 2020, 4:56pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/1 "2020-03-05T16:56:08Z")
It would be great to have a way to back up or create a checkpoint not just of a single app, but all apps and all their data in my account. I am paranoid that someone might delete a type/field/app by mistake, resulting in unrecoverable data loss. ---
**Author:** ![Holger\_Winkelmann](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/holger_winkelmann/32/1524_2.png) [@Holger\_Winkelmann](https://community.fibery.io/u/Holger_Winkelmann)\ **Post date:** [March 11, 2021, 9:07pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/2 "2021-03-11T21:07:21Z")
HI, we had a similar discussion with @antoniokov the other day and I promised to send some material over. The actual idea was to give the Workspace some kind of AWS Credentials for a Customer Owned S3 bucket. The Whole Workspace will be copied over there including metadata as JSON/YAML what or similar as archive. In an unexpected event, anyone can recover the data as long they are well-structured. The inspiration was coming from backup, a Github Backup tool: > **[Sync GitHub repository backups to Amazon S3 - BackHub Features](https://www.backhub.co/features/sync-github-backups-to-amazon-s3)** > > BackHub allows you to connect an Amazon S3 bucket of your choice and get all your GitHub repository backups synced on a daily basis, including metadata. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 11, 2021, 11:24pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/3 "2021-03-11T23:24:23Z")
I think the original feature request relates more to ‘undelete’ (which is WIP according to fibery twitter) rather than disaster recovery, which seems closer to your proposal (also important of course). ---
**Author:** ![radek](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/radek/32/4249_2.png) [@radek](https://community.fibery.io/u/radek)\ **Post date:** [October 29, 2021, 7:49pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/4 "2021-10-29T19:49:45Z")
@Chr1sG Even though the original request is about the “undelete”, the whole-workspace backup feature is important for the teams relying on the know how captured in fibery. @Holger_Winkelmann Is there any progress on that? ---
**Author:** ![Quinn\_JH](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/quinn_jh/32/5296_2.png) [@Quinn\_JH](https://community.fibery.io/u/Quinn_JH)\ **Post date:** [April 20, 2023, 9:58pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/5 "2023-04-20T21:58:33Z")
Sorry to resurrect an old thread here, I’m interested in both un-delete and disaster recovery. I’ve been recommending Fibery to clients but through gritted teeth as we’ve had trouble with restoring deleted data. > [@Chr1sG](#): > > I think the original feature request relates more to ‘undelete’ (which is WIP according to fibery twitter) rather than disaster recovery(…) In our experience, doing un-delete is achievable with the (now released) audit and trash logs. However, un-deleting an entire database or large portion of a large connected DB still has issues. Specifically, restoring more than 200 linked entities from both trash log and audit log can result in errors ( discovered when we needed to restore ~800 from being wiped by an integration ) Of course there is ‘workspace settings’\>export all data which is okay for manual DR backups. What we really need is: - Trigger backups on a user-defined schedule - Store the backups in S3 / gdrive and let us delete/retain them - Export any other files or information beyond .csv and md (?) Ideally, if things were deleted/lost, we could run ‘full export’ of current space, restore the entire workspace to past backup point, use the recent ‘full export’ and .csv import to update any data in db’s missed in past backup point Seeing “CSV import 2.0” feature being tested is very encouraging for per-DB restore from ‘full export’! Anyone else doing disaster recovery planning with Fibery? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 21, 2023, 9:06am UTC](https://community.fibery.io/t/backup-entire-workspace/595/6 "2023-04-21T09:06:00Z")
> [@Quinn\_JH](#): > > un-deleting an entire database or large portion of a large connected DB still has issues. > Specifically, restoring more than 200 linked entities from both trash log and audit log can result in errors ( discovered when we needed to restore ~800 from being wiped by an integration ) Un-deleting large amounts of data (that had originally been added into the workspace over a period of time) is quite challenging, for similar reasons to why trying to merge multiple documents is challenging. Imagine you have a database with a history like this: Created db Added some fields Added entities A and B Added some relations Deleted B Changed some relations (from one-to-one to one-to-many) Added entities C and D Added some more fields Deleted entities A and C Added entity E Added more fields …and now you realise that you need to recover entity B. What should happen? What values should B take for all its fields? Now imagine that you have deleted hundreds of entities(!) Of course, if you realise that you need to restore something immediately after it has been deleted, the challenges aren’t so great, but what if a little time has passed and you/your colleagues have made changes in the mean time? Designing an undelete process to be sufficiently robust is not a trivial one. Fibery does maintain regular backups of user data for internal purposes, but it is not very scalable to maintain snapshots of every workspace at the various time intervals that would accommodate a restoration process. > [@Quinn\_JH](#): > > What we really need is: > > - Trigger backups on a user-defined schedule > - Store the backups in S3 / gdrive and let us delete/retain them It is theoretically possible that Fibery could offer the option for users to do a full workspace backup (databases, files, documents, in a non-human readable format (blob) which users could then choose to store in their own data centres, but so far, the work to develop this functionality (and the functionality to restore from a blob) would be significant, and would take resources away from other areas. At the moment, it’s just not high enough priority. ---
**Author:** ![tomp](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@tomp](https://community.fibery.io/u/tomp)\ **Post date:** [January 16, 2025, 8:36pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/7 "2025-01-16T20:36:44Z")
In terms of data security, having data backup automatically to an external source such as OneDrive, or even to receive an email with a download link every day or week. ---
**Author:** ![HDU](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/hdu/32/10752_2.png) [@HDU](https://community.fibery.io/u/HDU)\ **Post date:** [March 24, 2026, 10:37pm UTC](https://community.fibery.io/t/backup-entire-workspace/595/8 "2026-03-24T22:37:18Z")
This would be a really good feature, especailly for those who use Fibery in any business critical operations. Any advice from the Fibery team or anyone - who can share their backup strategy for their Fibery data? Daily back up of all data is required. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 25, 2026, 9:17am UTC](https://community.fibery.io/t/backup-entire-workspace/595/9 "2026-03-25T09:17:36Z")
Technically very hard problem. Close to 0 chances we will do it. However, we will work on better History and Undo for all-the-things this year.