Windows, Linux and macOS according to supported version and product;
Windows, Linux and macOS according to supported version and product;
Structure tenants, agents, storage, encryption, retention, alerts and restores without turning multicloud flexibility into operational fragmentation.
Multitenant management, selected storage, policies and tested recovery.

MSP360 Managed Backup lets organizations, users, endpoints and plans be administered from a console. The multitenant hierarchy must reflect isolation, delegation and support; global templates receive controlled exceptions by workload and customer. Roles, MFA where available, offboarding, an administrative audit trail and protection of storage credentials are part of the architecture. Add Solution documents who changes policies, accesses keys, performs restores and approves deletions.
Commercial coverage does not replace the compatibility matrix. Operating system, application-aware processing, VSS, permissions, APIs and restore granularity are checked before design.
Windows, Linux and macOS according to supported version and product;
files, volumes and system images according to edition;
VMware and Hyper-V with specific integrations and requirements;
Microsoft SQL Server and supported applications with validated consistency;
Microsoft 365 and Google Workspace through dedicated offerings, under the applicable scope and license.
MSP360 can work with supported cloud storage providers and local destinations, depending on the product. Using a customer-owned storage account broadens cost and residency options, but the customer remains responsible for the account, keys, lifecycle, capacity, egress and provider support. Immutability depends on the backend, backup mode and supported configuration. Object Lock, versioning or provider retention must not be generalized. The period, deletion authority and credential recovery must be tested.
Plans define source, frequency, destination, compression, encryption, retention and notifications. Different policies serve mobile endpoints, servers, databases and VMs. Bandwidth limits and windows reduce impact but can compromise RPO when daily volume exceeds transfer capacity. Sizing considers protected volume, change rate, full and incremental backups, retention, growth, multiple destinations and restore time. Deduplication or compression is never assumed to deliver a fixed ratio.
Encryption in transit and at rest depends on the product, destination and configuration. When a customer-controlled password or key protects backups, losing it can make recovery impossible. Custody, rotation, emergency access and escrow belong in the runbook. The console, endpoints and storage account form different trust domains. A single administrative credential must not silently control all of them.
Restoration can involve files, volumes, images or supported workloads. Bare-metal recovery and restoration to different hardware or environments depend on drivers, boot, licenses, networking and the application. Add Solution tests the entire path, not just reading the object from storage. Recovery workflow:
Define loss events, workloads, dependencies, RPO, RTO and retention.
Size the management plane, agents or proxies, networking, storage and isolation.
Apply policies by criticality, window, destination and administrative authority.
Test consistency, restoration, destination capacity and owner acceptance.
Monitor recovery points, failures, capacity, changes and evidence.
Protected SaaS services, objects, APIs, retention and licensing vary by offering. Offboarded users, discovery of new accounts, administrative permissions, residency and search must be defined. Native SaaS retention and independent backup address different events.
The console must highlight endpoints without backups, the age of the latest recovery point, recurring failures, offline agents, capacity and overdue tests. Alerts are routed by tenant, severity and time; a report without an accountable response queue does not constitute operations. RMM and Remote Desktop are adjacent products and must not be assumed to be included or to replace backup monitoring. Remote access requires its own authorization and auditing.
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
Testar consistência, restore, capacidade do destino e aceite do owner.
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
Licensing can vary by product, device, workload, user, storage or contracted plan. Cloud storage, API operations, egress, retention and recovery compute may be charged by the selected provider. Features of Managed Backup, standalone Backup, Microsoft 365, Google Workspace, RMM and Connect are not treated as a universal package. Compatibility, lifecycle and support are confirmed in current documentation. MSP360 support, the storage provider and Add Solution each have their own scope.
Answers for MSP360 protection, recovery and operational decisions.
It depends on the offering. Many designs use separately selected and contracted storage; the account, consumption, egress and support must be confirmed.
No. The backend, backup mode, configuration and administrative authority determine the available control.
No. Criticality, volume, connectivity, retention, system and contract require templates with controlled exceptions.
This must not be assumed. It is a specific offering with its own scope.
No. Hardware, drivers, boot, licenses, networking, dependencies and application consistency must be validated.
No. They can be integrated, but coverage, alerts and responsibilities are different.
tenant and workload assessment;
multitenant architecture and delegation;
agents, policies, storage and keys;
Microsoft 365 and Google Workspace within their own scopes;
sizing, bandwidth and capacity planning;
restores, evidence and runbooks;
alerts, reports and ongoing operational support.
Connect tenants, storage, policies, keys, alerts and tests to each customer’s actual commitments.