Soteria Cloud KB
Soteria Cloud KB
Breadcrumbs

40.70 — Data Sources, Storage and Backup Targets

40.70 — Data Sources, Storage and Backup Targets

Publication status: Current official Acronis offering
Baseline verified: 21 August 2026
Content model: Original Soteria Cloud operational summary with canonical Acronis sources; no vendor article body is reproduced.

Purpose and portfolio position

Operational coverage for data sources, storage and backup targets.

This page establishes a controlled starting point for sales qualification, solution design, deployment, operations and support. It does not override the customer's agreement, the current Soteria Cloud service catalogue, Acronis licensing policy, the product support matrix or product lifecycle information.

Capability scope

  • disks and volumes.

  • files and folders.

  • system state.

  • ESXi configuration.

  • NAS.

  • network shares.

  • SAN.

  • tape.

  • local storage.

  • Acronis-hosted storage.

  • partner-hosted storage.

  • Amazon S3.

  • Microsoft Azure.

  • supported S3-compatible targets.

Soteria Cloud delivery boundary

  • Confirm whether Soteria Cloud offers this item, whether it is enabled for the relevant partner/customer tenant and who owns first-line and escalated support.

  • Confirm the exact commercial package, metric, quota, exclusions and dependencies before quoting or enabling it.

  • Do not claim South African data residency, Teraco hosting, geo-redundancy or local service operation unless the exact workload, tenant and service design have been verified.

  • Keep vendor capability, Soteria service design, reseller responsibility and end-customer responsibility explicit.

Qualification and design checks

  • source ownership.

  • protocol and credentials.

  • capacity and retention.

  • immutability.

  • encryption.

  • connectivity and throughput.

  • provider lifecycle and egress.

  • representative restore test.

  • Identify data classification, privacy, compliance, retention and audit requirements before enabling access or protection.

  • Define success criteria, test evidence, monitoring ownership and the support/escalation path.

Enablement checklist

  1. Confirm the current Acronis name, release status, lifecycle state and canonical documentation.

  2. Confirm the customer or tenant, workload scope, administrator roles and least-privilege access.

  3. Confirm licensing, offering items, quotas, dependencies, price-list mapping and customer approval.

  4. Document architecture, network, identity, storage, data-location and integration dependencies.

  5. Configure a bounded pilot or representative workload before broad rollout.

  6. Validate the expected protection, management, security or recovery outcome and retain evidence.

  7. Establish alerting, operational review, change control, support ownership and an exit/rollback path.

Operating model

  • Maintain the workload inventory and dependency map.

  • Monitor the controls that contribute to the stated business outcome.

  • Test representative failure, response and recovery scenarios.

  • Record gaps that sit outside Acronis capability or the contracted Soteria service.

  • Review the design when workloads, versions, identity, networks or objectives change.

Troubleshooting path

  1. Confirm whether the problem is entitlement, configuration, connectivity, compatibility, capacity, identity or an active vendor incident.

  2. Capture the exact error, timestamp, activity or incident identifier, tenant, workload, version and recent change.

  3. Check service status, release notes, lifecycle and the current compatibility documentation.

  4. Reproduce safely at the narrowest scope; do not disable protection broadly to prove a hypothesis.

  5. Escalate with logs, screenshots, topology, expected versus actual result and business impact.

Minimum escalation evidence

  • Customer, tenant and affected workload identifiers.

  • Product/service name, edition, version, agent or component build.

  • Policy, plan, offering item and relevant role assignments.

  • Exact timestamps, activity/incident IDs, errors and recent changes.

  • Logs or reports collected through the approved support procedure.

  • Business impact, urgency, workaround and required outcome.

Important limitation

Support varies by product generation, edition, agent and version. Validate current documentation before implementation.

Official source

Governance

  • Owner: Soteria Cloud Knowledge Base governance owner

  • KB-ID: SCKB-AW-4070

  • Review baseline: 21 August 2026

  • Review trigger: Acronis release, licensing, lifecycle or Soteria service-catalogue change