Configure and validate backups for monday.com

Set up and validate backups for monday.com.

Service provider configurations

Before onboarding monday.com backups, service providers must complete the following configurations:

  • Prepare a MediaAgent to receive data via S3 protocol
  • Add an access node
  • Create a workload resource pool for SaaS applications

For instructions, see Configure SaaS applications for service providers.

Onboard monday.com

Onboard a monday.com instance to begin protecting your monday.com data. During onboarding, you connect to monday.com, choose the content to protect, assign a backup plan, and create the backup configuration.

Start the configuration

  1. From the Command Center navigation pane, go to Protect > SaaS Applications.

  2. Click Add SaaS Application.

  3. Select monday.com, and then click Next.

Specify credentials

Cloud App Connection Details

  • In the Name field, provide a display name for this monday.com backup configuration.

Configure Credential

  • In the Password field, paste your monday.com Personal API Token.

To generate a Personal API Token, sign in to monday.com, click your profile icon, select Developers, open My Access Tokens, and copy the token. For details, see Configure permissions for monday.com protection.

Choose the backup content

  • Click the pencil (edit) icon next to Content.

  • Choose either: select the workspaces shown in the browse tree, or define rules to select content for the subclient.

Workspaces are the top-level browseable objects. You can select all workspaces to back up the entire account, or select specific workspaces to scope backup to those workspaces and all boards within them.

Select a backup plan

  • Select an existing backup plan, or click + to create a new one.

  • After you create a backup plan, you can select it when you onboard additional monday.com instances.

Important

Use any backup plan whose Primary Copy MediaAgents have the CVS3Service package installed.

Review summary

  • Review the instance name, plan name, schedule, and backup content.

  • Click Submit.

Run a backup

  1. From the Command Center navigation pane, go to Protect > SaaS Applications.

  2. For the application that you want to back up, click the action button action_button, and then click Back up now to run a Full backup.

  3. Monitor job progress in the Jobs view.

Backup performance depends on the amount of data, the number of workspaces and boards, and monday.com API rate limits. Commvault uses a complexity-budget system to manage API rate limits automatically.

Validate the backup

Verify the configuration

After you assign the backup plan, confirm that:

  • The monday.com instance appears in the SaaS Applications list with the name you provided during onboarding.

  • The browse tree populates with your workspaces, folders, and boards.

Confirm that the backup completed successfully

  1. From the Command Center navigation pane, go to Monitor > Jobs.

  2. Locate the completed backup job.

  3. Verify that the job status is Completed.

  4. Check the job details to confirm:

    • The number of objects backed up matches the expected count of workspaces, folders, and boards.

    • The storage used is reasonable for the amount of data in your monday.com account.

    • The job duration is within expected limits based on your account size and API rate limits.

Test a restore

  1. From the Jobs view, select the completed backup job.

  2. Click Restore.

  3. Select one or more boards to restore.

  4. Confirm that the restore destination is set to Isolated workspace mode. Commvault creates a fresh workspace with the name "Restored from backup — YYYY-MM-DD" and rebuilds all folders and boards inside it.

  5. Click Submit.

  6. Verify that the restore completes with status Completed and that the data matches the original.

For complete restore procedures, see Restore monday.com data.

Common causes of failures and what to check first

Configuration and permission issues

Authentication failure

  • Check that the Personal API Token is correctly copied into the Commvault credential field without extra spaces or characters.

  • Verify that the token has not been revoked in the monday.com Developer Center.

  • Confirm that the account associated with the token has access to the workspaces and boards you want to back up.

  • Ensure that the account plan supports API access. Free plans may have limited API access.

Missing permissions

  • Verify that the Personal API Token has the required scopes: me:read and boards:read for backup, and me:write, boards:read, and boards:write for restore.

Network connectivity failure

  • Confirm that the access node can reach api.monday.com on port 443.

  • If you use a Commvault-managed access node, allowlist the access node IP address in your network firewall.

Backup job failures

Rate limit exceeded

  • monday.com uses a complexity-budget system for API rate limits. If the backup job encounters a rate limit, Commvault automatically retries with exponential backoff.

  • If rate limit errors persist, schedule backups during off-peak hours to reduce API load.

Empty browse tree

  • Verify that the account associated with the token has access to at least one workspace.

  • Check that the workspace is not archived or deleted in monday.com.

Restore failures

User or team not found

  • Users are matched by email and teams are matched by name on the target account. If a user or team is not found during restore, Commvault logs a warning and continues with the restore.

  • After restore, verify that board owners and sharing settings are correct, and reconfigure them manually if needed.

Cross-board column unlinked

  • board_relation, dependency, and mirror columns that reference boards outside the backup scope are created but left unlinked.

  • To restore cross-board column linkage, include all referenced boards in the same backup and restore operation.

×

Loading...