> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/infrastructure/dashboard-actions/resolve-sprinto-check-for-enabling-backup-on-databases.md). # Resolve Sprinto Check for Enabling Backup on Databases Sprinto raises this check when a connected database does not have **automatic or periodic backups enabled**, or when Sprinto cannot detect the configured backup schedule.\ Backups are required by multiple compliance frameworks to ensure organisations can restore critical data in the event of a failure or attack. This article explains how to resolve the check for integrated databases and how to meet the requirement using workflow checks when a database is not integrated with Sprinto. *** ### **When Databases Are Not Integrated with Sprinto** If a database cannot be integrated, you can still meet the compliance requirement by completing the workflow check: **Database backup is done regularly** This workflow check activates on a set frequency and requires the assigned stakeholder to upload evidence of backup completion. Once evidence is added, the check status moves to **Passing**. *** ### **Purpose of This Control** Most security frameworks (SOC 2, ISO 27001, HIPAA, PCI DSS) require organisations to maintain periodic backups of production databases.\ A recent backup helps restore systems quickly after: * Accidental data deletion * Infrastructure failure * Ransomware or security incidents Sprinto validates that each in-scope database has an operational backup schedule in place. *** ## **How to Fix the Check** ### **1. For Integrated Databases** #### Step 1 - Locate the failing check 1. Log in to the **Sprinto Admin Portal**. 2. Open the **Tasks** dashboard. 3. Scroll to **Infrastructure checks** and select the failing backup check.\ You may also find database-specific checks under **Infra Systems**. #### Step 2 - Enable or update backups in the database platform Log in to the relevant cloud provider or database console and configure automatic backups. Reference documentation for commonly integrated databases: * **Azure Cosmos DB**\ * **DigitalOcean DB**\ * **MongoDB Atlas**\ * **GCP Cloud SQL**\ * **Amazon EFS**\ * **Amazon Redshift**\ * **Amazon RDS**\ Once backups are enabled, Sprinto will automatically detect the change during the next monitor evaluation and update the status to **Passing**. *** ### **Workarounds (When Automated Backup Cannot Be Enabled)** If automated backup is temporarily not possible, you may: #### **Option 1 - Mark the check as a special case** Use this when the exception is justified and documented. You can: * Specify the reason * Attach supporting evidence * Set the exception period (temporary or permanent) Refer to:\ **How to mark a Sprinto check as a special case**\ #### **Option 2 - Upload external evidence** Upload a recent backup screenshot or export confirming that: * Automatic backups are running, or * Manual backups are taken on a regular schedule This will set the check to **Passing**. *** ## **2. For Workflow Checks (Non-Integrated Databases)** #### Step 1 - Access the workflow check 1. Log in to the Sprinto dashboard and navigate to **Monitoring**. 2. Go to the **Workflow Checks** tab.
3. Select **Database backup is done regularly**. This check may also appear in **Infrastructure workflow checks**. #### Step 2 - Upload backup evidence 1. Click **Upload evidence**.
1. Add the backup file or shareable link.\ Examples: * Screenshot of backup settings * Log or timestamp of the latest backup 2. Enter the **evidence recording date**. 3. Click **Save**.
The check will then reflect a **Passing** status. You may also edit: * Title * Description * Assigned user * Frequency of the check *** ## **Support** If you require assistance enabling backups or resolving related monitor issues, contact Sprinto Support. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinto.com/data-library/infrastructure/dashboard-actions/resolve-sprinto-check-for-enabling-backup-on-databases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.