Create a backup
You can create a backup from a serverless index as follows.Describe a backup
You can view the details of a backup as follows.List backups for an index
You can list backups for a specific index as follows. Up to 100 backups are returned at a time by default, in sorted order (bitwise “C” collation). If thelimit parameter is set, up to that number of backups are returned instead. Whenever there are additional backups to return, the response also includes a pagination_token that you can use to get the next batch of backups. When the response does not include a pagination_token, there are no more backups to return.
List backups in a project
You can list backups for all indexes in a project as follows. Up to 100 backups are returned at a time by default, in sorted order (bitwise “C” collation). If thelimit parameter is set, up to that number of backups are returned instead. Whenever there are additional backups to return, the response also includes a pagination_token that you can use to get the next batch of backups. When the response does not include a pagination_token, there are no more backups to return.
Delete a backup
You can delete a backup as follows.Schedule automated backups
Scheduled backups require
X-Pinecone-API-Version: unstable.expire_after_days) that automatically deletes old backups, keeping storage costs predictable. Each index supports one active schedule at a time.
To create a backup schedule:
curl
"frequency": "weekly" or "monthly" as needed.
You can also list schedules, update a schedule (e.g., to pause it or change the frequency), delete a schedule, and view the backup history for a schedule.
Deleting a schedule does not delete any backups that were previously created by it. For more details, see Scheduled backups.