BCDR Cloud API

BCDR Cloud API

· پراستفاده‌ترین #352

The backup and DR platform your agent can run without you

ذخیره‌سازیپشتیبانیDeveloperSecurityاتوماسیون

BCDR Cloud API is Saudi Arabia's cyber-defence and business-continuity platform, giving organisations structured control over backup orchestration, recovery testing, compliance reporting, and asset protection across hybrid and cloud environments. Connect it to Actionist and your agents can trigger backups on demand, monitor RPO drift in real time, initiate failover tests against recovery sites, acknowledge alerts before escalations fire, and generate audit-ready compliance reports — all without an engineer logging into the console. Whether you're protecting financial data for SAMA compliance or orchestrating quarterly DR drills, the agent handles the sequence while your team stays focused on outcomes.

میانگین زمان صرفه‌جویی‌شده
11 ساعت
برای هر نفر · در هر ماه
تقریبا 1 روز کاری برگشتی

کار دستی را حذف می‌کند. Automation eliminates manual backup monitoring, console-based alert acknowledgement, and the laborious collation of RTO/RPO evidence for monthly compliance reports.

زمان‌بندی

عامل BCDR Cloud API شما چه چیزهایی را خودکار اجرا می‌کند

یک هفته کارهای زمان‌بندی‌شده که عامل Actionist از طرف شما اجرا می‌کند.

28کارهای زمان‌بندی‌شده
7عامل‌های فعال
24/7همیشه روشن
عامل‌ها
چهارشنبهجمعه
چهارشنبه
پنجشنبه
جمعه
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
گردش‌کارهای چنداپلیکیشنی

BCDR Cloud API × همه اپلیکیشن‌های دیگر شما

اتوماسیون‌های سرتاسری که چند اپلیکیشن را به هم وصل می‌کنند؛ هرکدام یک خروجی واقعی کسب‌وکار.

6گردش‌کارها
9اپلیکیشن‌های درگیر
حدود 44 ساعتصرفه‌جویی در هفته
6نقش‌های پوشش‌داده‌شده
برای موفقیت مشتری
ویژه4 اپلیکیشن

Backup failure → customer incident, closed in minutes

When a customer-facing system backup fails and the RPO clock starts ticking, your agent reads the BCDR failure details, initiates a fresh on-demand backup, posts a real-time status thread to the customer success Slack channel, and blocks a recovery review slot on the CSM's calendar — all before the ticket is even raised. Customers stay informed, SLAs stay intact, and your team spends its energy on resolution rather than coordination.

حدود 11 ساعت

زمانی که تیم شما هر هفته و به‌صورت خودکار پس می‌گیرد

جریان کار
تریگر·When a BCDR backup failure alert fires for a customer-facing system
نتیجه
Trigger on-demand backup job to close RPO gapPost incident status thread to #customer-successBlock recovery review slot for CSM
برد اصلی
صرفه‌جویی در هر اجرا
حدود 1 ساعت
اجرا در هفته
~10×
SLA preserved without manual triage
اجرا توسطCustomer Support Agent
بازگشت سرمایه

صرفه‌جویی

چیزی که تیم شما پس می‌گیرد: کارهای دستی‌ای که حذف می‌شوند و ارزشی که ایجاد می‌شود.

بدون Actionist

کاری که امروز دستی انجام می‌دهید

با Actionist

کاری که عامل شما برایتان اجرا می‌کند

  • Sales
    19 دقیقه در هفته
    DR proof assembly

    Sales engineers manually pull RTO/RPO data and recent test results from the BCDR console to answer prospect questions — typically a 30-minute cross-team ask.

    عامل Sales
    ۰ دقیقه
    Agent builds the proof pack

    Agent pulls the latest RTO/RPO report and failover test history the moment a prospect asks — technical evidence ready in under 2 minutes.

  • Marketing
    14 دقیقه در هفته
    Case study data chase

    Marketing waits days for engineering to provide recovery test results and uptime metrics needed for customer case studies and reference materials.

    عامل Marketing
    ۰ دقیقه
    Agent extracts the metrics

    When a customer reference is approved, agent pulls failover test results and compliance report data and opens a pre-filled case study draft automatically.

  • Customer Support
    19 دقیقه در هفته
    Backup failure triage

    Support engineers manually check the BCDR console for error details, then compose status updates for customers while the clock runs on the RPO window.

    عامل Customer Support
    ۰ دقیقه
    Agent triages and notifies instantly

    Agent reads failure details, triggers a recovery backup, and posts a status update to the customer success channel — all within 90 seconds of the alert firing.

  • Human Resources
    8 دقیقه در هفته
    Offboarding data retention check

    HR manually confirms with IT that departing employees' system data is backed up before account deactivation — a step that often falls through the cracks.

    عامل Human Resources
    ۰ دقیقه
    Agent verifies coverage on exit

    When an offboarding ticket is raised, agent checks whether the employee's systems have active BCDR policies and flags any gaps before account deactivation proceeds.

  • Finance
    14 دقیقه در هفته
    Monthly compliance evidence pull

    Finance teams manually request RTO/RPO data from IT each month, wait for the report, and format it for the audit evidence folder — a recurring 14-minute cycle.

    عامل Finance
    ۰ دقیقه
    Agent files evidence automatically

    On the first of each month, agent generates the compliance report, validates RTO/RPO against contracted targets, and commits it to the audit evidence repository.

  • Operations
    30 دقیقه در هفته
    New-asset protection enrolment

    Ops engineers manually enrol each new server or VM into BCDR policies after provisioning — a step that is routinely delayed by days during high-velocity deployment cycles.

    عامل Operations
    ۰ دقیقه
    Agent protects on provision

    When a new asset appears in the inventory sheet, agent immediately adds it to the correct protection plan and logs the policy assignment — zero unprotected gap.

  • Legal
    6 دقیقه در هفته
    DR compliance attestation prep

    Legal manually gathers BCDR compliance evidence to support data protection attestations for contracts and regulatory filings — typically a 6-minute hunt across multiple systems.

    عامل Legal
    ۰ دقیقه
    Agent prepares the attestation pack

    When a contract compliance request arrives, agent generates the relevant compliance report and formats it for the legal team's filing template immediately.

+ صدها اتوماسیون دیگر BCDR Cloud API
میانگین ماهانه
11 ساعت / نفر / ماه
میانگین ماهانه
11 ساعت / نفر / ماه
محاسبه‌گر

محاسبه کنید تیم شما چه چیزی ذخیره می‌کند

اندازه تیم
10 نفر
نرخ ساعتی
20 دلار / ساعت
ساعت ذخیره‌شده / هفته
28
ساعت ذخیره‌شده / سال
1,400
بازگشت سالانه
$28,000

بر اساس الگوی رایج استفاده تیمی از BCDR Cloud API: کارهای قابل مشاهده به‌علاوه چند اتوماسیون دیگر که عامل اجرا می‌کند: حدود2.8 ساعت / نفر / هفته کار اداری خودکار می‌شود.

اتصال

چطور BCDR Cloud API را به Actionist وصل کنید

روش اتصالی را انتخاب کنید که با محیط کاری شما سازگار است.

The fastest path to BCDR Cloud API. Install the Datto BCDR MCP server and your agent reaches backup jobs, recovery points, assets, and alerts through a permissioned token handshake — no direct API wiring required.

1
Open the Apps tab

Find BCDR Cloud API in the Apps library and click Connect. MCP is selected by default.

2
Authorise in BCDR Cloud API

Enter your BCDR tenant URL and API token when prompted. The MCP server uses these to authenticate against your BCDR Cloud instance — your credentials are stored encrypted and never leave your environment.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

اکشن‌ها

16 اکشن که عامل شما می‌تواند اجرا کند

عملیات خواندن و نوشتنی که برای عامل Actionist شما در دسترس است.

تریگرها

7 رویداد که عامل شما می‌تواند به آن واکنش نشان دهد

رویدادهایی که عامل شما زیر نظر می‌گیرد و در پاسخ به آن‌ها اکشن اجرا می‌کند.

مهارت‌ها

مهارت‌هایی که با BCDR Cloud API خوب کار می‌کنند

مهارت‌های قابل استفاده مجدد عامل که کنار این اپلیکیشن مفید هستند.

هنوز مهارت جفت‌شده‌ای آماده نشده است. این اپلیکیشن را به عامل خود اضافه کنید تا گزینه‌های مناسب را کشف کنید.
سرورهای MCP

سرورهای MCP سازگار با BCDR Cloud API

Actionist را به سرورهای MCP ساخته‌شده برای این اپلیکیشن یا پیرامون آن وصل کنید.

Datto BCDR
رسمی

MCP server exposing Datto BCDR appliances, agents, recovery points, screenshots, and alerts as tools your agent can call directly.

پرسش‌ها

پرسش‌ها درباره BCDR Cloud API + Actionist

How do I connect BCDR Cloud API to Actionist?
The recommended path is MCP: open the Apps tab, find BCDR Cloud API, click Connect, enter your BCDR tenant URL and API token, and Actionist runs a read-only verification call. If MCP is not available in your environment, use the API Token method — generate a token in your BCDR portal under Settings → API Access with backup, asset, report, and alert scopes, then paste it into Actionist.
Which BCDR actions can the agent take without my approval?
The agent can read freely — listing assets, fetching backup status, pulling RTO/RPO reports, and listing alerts — with no human confirmation needed. Write operations such as triggering backup jobs, initiating failover tests, restoring assets, and acknowledging alerts only run when you've explicitly given the agent that instruction or configured an approval-free automation. You control the scope at connection time via the API token scopes you grant.
Can the agent accidentally overwrite production data during a restore?
No. BCDR Cloud API's restore operations require you to specify the target destination explicitly — the agent cannot restore to an arbitrary location. Actionist surfaces the target in the action confirmation step before executing. For additional safety, configure restore actions as approval-required in Actionist's permission settings so a human confirms the destination before the agent proceeds.
How does the agent handle backup failures for critical systems?
When a backup failure trigger fires, the agent reads the error details (error code, affected asset, consecutive failure count) and routes the response based on severity rules you configure. For tier-1 systems the default path is: open an incident, acknowledge the alert to stop escalation paging, trigger an on-demand backup to close the RPO gap, and notify the on-call engineer. All of this happens within 90 seconds of the failure signal — before a human would typically see the alert.
What happens if the agent triggers a backup during a maintenance window?
BCDR Cloud API's scheduled policies respect maintenance windows defined in your BCDR tenant configuration. On-demand backups triggered by the agent do not automatically honour those windows — they execute immediately. If you want the agent to skip maintenance windows, add a condition to your automation that checks for active maintenance flags (via a Notion or calendar lookup) before calling Trigger backup job.
Can the agent generate compliance reports for specific regulatory frameworks?
The Generate compliance report action creates a point-in-time report covering backup coverage, policy adherence, and missed backup windows for assets you scope to it. It does not automatically map to named frameworks like ISO 27001 or SAMA requirements out of the box. However, you can configure the agent to filter the report to the relevant asset groups (e.g. all finance-system VMs) and attach it to a pre-formatted framework template stored in Google Drive or Notion.
How do I prevent the agent from triggering too many failover tests and consuming DR capacity?
Add a rate-limit condition to any automation that calls Initiate failover test — for example, check the List failover tests result to confirm no test for the same asset completed in the past 7 days before proceeding. For batch DR drills, sequence the tests explicitly rather than triggering them all in parallel, so recovery site capacity is not exhausted by simultaneous restores. BCDR Cloud API returns an error if a test conflicts with a live restore; the agent surfaces that error for you to handle.
Can I disconnect BCDR Cloud API without losing my automation history?
Yes. Disconnecting BCDR Cloud API removes the agent's ability to make new calls to your BCDR tenant, but it does not delete any automation run history, compliance report files already generated, or data stored in other connected apps (Google Sheets, Notion, etc.). Reconnecting restores full functionality. Rotate your API token before disconnecting if the token was shared with other systems.