> ## Documentation Index > Fetch the complete documentation index at: https://cockroachlabs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # CREATE SCHEDULE FOR BACKUP export const InternalLink = ({version, path = "", children, ...props}) => { let detectedVersion = version || "stable"; if (typeof window !== 'undefined' && !version) { const match = window.location.pathname.match(/\/docs\/([^/]+)/); if (match) { detectedVersion = match[1]; } } const normalizedPath = path.startsWith("/") ? path.slice(1) : path; return {children} ; }; The `CREATE SCHEDULE FOR BACKUP` statement creates a schedule for periodic backups. For more information about creating, managing, monitoring, and restoring from a scheduled backup, see Manage a Backup Schedule. ## Required privileges Starting in v22.2, CockroachDB introduces a new system-level privilege model that provides finer control over a user's privilege to work with the database, including taking backups. There is continued support for the [legacy privilege model](#required-privileges-using-the-legacy-privilege-model) for backups in v22.2, however it **will be removed** in a future release of CockroachDB. We recommend implementing the new privilege model that follows in this section for all new and existing backups. You can grant the `BACKUP` privilege to a user or role depending on the type of backup: | Backup | Privilege | | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Cluster | Grant a user the `BACKUP`system-level privilege. For example, `GRANT SYSTEM BACKUP TO user;`. | | Database | Grant a user the `BACKUP` privilege on the target database. For example, `GRANT BACKUP ON DATABASE test\_db TO user;`. | | Table | Grant a user the `BACKUP` privilege at the table level. This gives the user the privilege to back up the schema and all user-defined types that are associated with the table. For example, `GRANT BACKUP ON TABLE test\_db.table TO user;`. | The listed privileges do not cascade to objects lower in the schema tree. For example, if you are granted database-level `BACKUP` privileges, this does not give you the privilege to back up a table. If you need the `BACKUP` privilege on a database to apply to all newly created tables in that database, use `DEFAULT PRIVILEGES`. You can add `BACKUP` to the user or role's default privileges with `ALTER DEFAULT PRIVILEGES`. You can grant the `BACKUP` privilege to a user or role **without** the `SELECT` privilege on a table. As a result, these users will be able to take backups, but they will not be able to run a `SELECT` query on that data directly. However, these users could still read this data indirectly, by restoring it from any backups they produce. Members of the `admin` role can run all three types of backups (cluster, database, and table) without the need to grant a specific `BACKUP` privilege. However, we recommend using the `BACKUP` privilege model to create users or roles and grant them `BACKUP` privileges as necessary for stronger access control. ### Privileges for managing a backup job To manage a backup job with `PAUSE JOB`, `RESUME JOB`, or `CANCEL JOB`, users must have at least one of the following: * Be a member of the `admin` role. * The `CONTROLJOB` role option. To view a backup job with `SHOW JOB`, users must have at least one of the following: * The `VIEWJOB` privilege, which allows you to view all jobs (including `admin` -owned jobs). * Be a member of the `admin` role. * The `CONTROLJOB` role option. See `GRANT` for detail on granting privileges to a role or user. ## Required privileges using the legacy privilege model The following details the legacy privilege model that CockroachDB supports in v22.2 and earlier. Support for this privilege model will be removed in a future release of CockroachDB: * Full cluster backups can only be run by members of the `admin` role. By default, the `root` user belongs to the `admin` role. * For all other backups, the user must have read access on all objects being backed up. Database backups require `CONNECT` privileges, and table backups require `SELECT` privileges. Backups of user-defined schemas, or backups containing user-defined types, require `USAGE` privileges. See the [Required privileges](#required-privileges) section for the updated privilege model. ## Destination privileges You can grant a user the `EXTERNALIOIMPLICITACCESS` system-level privilege. Either the `EXTERNALIOIMPLICITACCESS` system-level privilege or the `admin` role is required for the following scenarios: * Interacting with a cloud storage resource using `IMPLICIT` authentication. * Using a [custom endpoint](https://docs.aws.amazon.com/sdk-for-go/api/aws/endpoints) on S3. * Using the `cockroach nodelocal upload` command. No special privilege is required for: * Interacting with an Amazon S3 and Google Cloud Storage resource using `SPECIFIED` credentials. Azure Storage is always `SPECIFIED` by default. * Using Userfile storage. We recommend using cloud storage. You also need to ensure that the permissions at your storage destination are configured for the operation. See Storage Permissions for a list of the necessary permissions that each bulk operation requires. ## Synopsis ```text theme={"theme":{"light":"catppuccin-mocha","dark":"catppuccin-mocha"}} CREATE SCHEDULE [IF NOT EXISTS]