{% extends "documentation/base.html" %}

{% block doc_content %}
<h1>Cove Data Protection</h1>

<p class="lead">
  Integrate N-able Cove backup accounts into Backupchecks using the Cove API.
</p>

<div class="doc-callout doc-callout-info">
  <strong>Scope:</strong><br>
  Cove integration is API-based (not email-based). Accounts are staged first, then linked to jobs.
</div>

<h2>How the Cove Flow Works</h2>

<ol>
  <li>Cove import reads account statistics from the Cove API.</li>
  <li>Accounts are upserted into the Cove staging table.</li>
  <li>Unlinked accounts appear on <strong>Cove Accounts</strong>.</li>
  <li>Operator links account to an existing job or creates a new job.</li>
  <li>After linking, an immediate import runs so new Cove runs appear right away.</li>
</ol>

<h2>Open Cove Accounts</h2>

<ol>
  <li>Open <a href="{{ url_for('main.cove_accounts') }}"><strong>Cove Accounts</strong></a>.</li>
  <li>Review <strong>unmatched</strong> accounts first.</li>
  <li>Link each account to a job (create or existing).</li>
</ol>

<h2>Settings and Operations</h2>

<ul>
  <li>Configure Cove under <strong>Settings → Integrations</strong>.</li>
  <li>Use <strong>Test connection</strong> to validate credentials and partner access.</li>
  <li>Use <strong>Run import now</strong> for manual sync.</li>
  <li>Background import runs on configured interval when enabled.</li>
</ul>

<h2>Run Visibility</h2>

<ul>
  <li>Cove runs are stored as API runs (<code>source_type = cove_api</code>).</li>
  <li>Cove run details are visible in Job Detail and Run Checks with a Cove summary panel (no mail section is shown for Cove runs).</li>
  <li>No mail message is required for Cove runs.</li>
  <li>Historical backfill can create runs from Cove 28-day colorbar data.</li>
  <li>
    <strong>Same-day duplicate suppression:</strong> once the first <em>complete success</em>
    run for a Cove job/day is recorded (status <code>Success</code> with at least one persisted
    object and all object statuses equal to <code>Success</code>), all newer Cove runs on that
    same local day are hidden in Run Checks — regardless of whether they are
    <code>Success</code>, <code>Warning</code>, or <code>Failed/Error</code>. Sort order in the modal
    stays newest → oldest.
  </li>
</ul>

<h2>Workstation Offline Handling</h2>

<p>
  Cove workstation devices are commonly powered off outside business hours, which used to
  produce false-positive missed-run alerts. Two mechanisms reduce this noise:
</p>

<h3>Schedule-based missed runs are skipped (always on)</h3>
<ul>
  <li>
    For jobs with <code>backup_software = "Cove Data Protection"</code> and
    <code>backup_type = "Workstation"</code>, the missed-run generator is disabled.
    No synthetic <code>Missed</code> rows are created when a workstation is off during a
    scheduled slot.
  </li>
  <li>
    Cove <em>Server</em> and <em>Microsoft 365</em> jobs keep the regular schedule-based
    missed-run logic.
  </li>
  <li>
    Real Cove statuses (<code>Failed</code>, <code>Warning</code>, <code>Not started</code>)
    continue to surface via the normal import flow, so genuine problems still get reported.
  </li>
</ul>

<h3>Colorbar-based offline detection (optional toggle)</h3>
<p>
  Configure under <strong>Settings → Integrations → Cove → Workstation offline detection</strong>.
</p>
<ul>
  <li><strong>Enable colorbar-based offline detection</strong> — off by default.</li>
  <li><strong>Warning after N inactive days</strong> — default 7 (range 1–28).</li>
  <li><strong>Error after N inactive days</strong> — default 14 (range 1–28).</li>
</ul>
<p>
  When enabled, every Cove import cycle checks each linked workstation's 28-day colorbar
  (<code>D09F08</code>) and counts the consecutive trailing days with status <code>0</code>
  (no backup activity). If the streak crosses the warning or error threshold, a single synthetic
  <code>JobRun</code> is upserted for that account so the alert appears in Run Checks. The same
  row is reused across cycles, so it escalates Warning → Error in place and is removed
  automatically once activity resumes. Runs that have already been reviewed in Run Checks are
  never mutated or removed, so acknowledged alerts do not reappear.
</p>

<h2>Troubleshooting</h2>

<ul>
  <li>If <strong>Cove Accounts</strong> is empty, run a manual import and check credentials.</li>
  <li>If a linked account shows no runs, verify link target job and import logs.</li>
  <li>If statuses look outdated, run <strong>Run import now</strong> and refresh Run Checks/Job Detail.</li>
</ul>

<h2>See Also</h2>

<ul>
  <li><a href="{{ url_for('documentation.page', section='backup-review', page='run-checks-modal') }}">Run Checks Modal</a></li>
  <li><a href="{{ url_for('documentation.page', section='customers-jobs', page='approved-jobs') }}">Approved Jobs</a></li>
</ul>
{% endblock %}