Recipes are labels that define the state of data by which the backup must be performed, as defined by the Application Admin. Recipes are the backup definition criteria for the data state upon backup execution, for example, application consistent, crash consistent, and so on.
Recipes are the first component of the application backup definition. Key considerations include:
- Databases: Database protection is a complex process, ranging from quiescing to log truncation as part of replica management. Thus, database protection frequently requires customization, using multiple recipes applied across different time periods based on business needs.
- Consistency groups: Components of an application may have I/O consistency, especially when generating crash-consistent backups,
- Snapshots vs. backups: Depending on the business needs, administrators may leverage snapshots or require the data copies in an alternate location, either using a standard CLI tool (such as a mysqldump for MySQL) or utilize a backup agent.
- Access to external datastores for protection and the sequence of resource backups, as relevant.
To define your Kubernetes Application Group and prepare for application data backup, you must first define the Application Group detail and the associated backup recipes. You can define one or more recipes for each Application Group, and each recipe is unique to that application.
For more information, see Recipe Definition.