# File Storage ## Methodology > [!important] The 3-2-1 Backup Strategy > > - At least 3 copies. > - At least 2 media. > - At least 1 of them must be offsite. ## Platform ```mermaid stateDiagram-v2 direction TB state device <<join>> state backup <<join>> state extraction <<join>> state iCloud { state "Documents" as i Obsidian forScore Lightroom Photos } state "OneDrive" as o state "Baidu Netdisk" as b state "Zotero" as z [*] --> device : Device device --> i : Project Files device --> forScore : Sheets device --> Photos : Phone Camera device --> Lightroom : Camera Lightroom --> Photos : Export Photos --> Lightroom : Color device --> z : Literature i --> o : Archive device --> o : Replayer Media device --> b : Large Media iCloud --> backup o --> backup backup --> b : Full Size Backup b --> b : Online Unzip b --> extraction o --> extraction extraction --> i : Extraction ``` [[cloud-storage]] - [[icloud|iCloud]] -- 200GiB - Center of file storage system. - For frequently used working/syncing files. - [[onedrive|OneDrive]] -- 1TiB - Comes with Microsoft 365 - Relayer files and archived project files. - Baidu Netdisk -- 14TiB, $40/yr - Media and full-size backup. - Online unzipping makes it suitable for backup. User [Mover](https://app.mover.io/) to migrate files between accounts! ## Organization - Let's start with what we have: - Tag - Metadata, including filename - Folders - File content - How do we find files: - Descend the file trees. - Spotlight search. - Pinned items. - General rules to follow - Limit hierarchy levels. Deep directories easily confuse users. - Comment and tag metadata. - Naming conventions, see [[filename]] for detailed disucssions. ## Methodology - [[para|PARA System]] - [[johnny-decimal|Johnny Decimal System]] - ACCESS - Flat structure -- used widely in [[backlink]] note taking systems.