<@U04UQ68083H> when creating backups for ory netwo...
# ory-copilot
b
@chilly-king-10285 when creating backups for ory network data, is the anything useful to backup besides identities, permissions, and oauth clients?
c
A message from kapa.ai
When creating backups for Ory Network data, the most critical items to back up are indeed identities, permissions, and OAuth clients. These represent the core user, access, and authorization data in your system. Beyond these, the knowledge sources suggest a few additional items you may want to consider: - Identity Schemas: If you use custom identity schemas, backing these up is important to ensure you can recreate your identity structure and validation rules. You can version and export these schemas from the Ory Network console or configuration files, and they are essential for restoring the correct user data structure in a disaster recovery scenario [Manage Ory Network configuration in git](https://www.ory.sh/docs/guides/gitops#identity-schema). - Configuration: Project and system configuration (such as settings for flows, hooks, and integrations) should be backed up, as these define how your Ory services behave. Configuration can be exported and versioned [Manage Ory Network configuration in git](https://www.ory.sh/docs/guides/gitops#identity-schema). - Organizations and Workspaces: If you use Ory’s organization or workspace features, consider backing up this data as well, since it defines your multi-tenancy and team structures [ory list organizations](https://www.ory.sh/docs/cli/ory-list-organizations), [ory list workspaces](https://www.ory.sh/docs/cli/ory-list-workspaces). Other operational data (like sessions, access tokens, and logs) is generally not considered personal data and is globally replicated for availability, so it may not be as critical to back up for disaster recovery, but you should assess your own requirements [Personal data location and homing](https://www.ory.sh/docs/security-compliance/personal-data-location). In summary, besides identities, permissions, and OAuth clients, you should also consider backing up identity schemas and configuration. If you use advanced features like organizations or workspaces, include those as well. If you have specific compliance or operational needs, review your backup strategy accordingly.