Server, VPS and infrastructure backup
suXus inventories systems, data, applications and dependencies required for recovery, then selects backup methods, schedules and checks appropriate to the environment. A successful job notification is a starting point, rather than proof that the complete service is recoverable.
Off-site backup
A copy outside the primary environment can reduce risks arising from a site or platform incident. suXus uses Iron Mountain for relevant infrastructure, off-site backup and continuity facilities. Storage and access arrangements are documented for each service.
Recovery points and retention periods
Recovery points determine the moments to which data can be restored. Retention periods reflect business needs, data volume, risk, legal agreements and available capacity. Default settings are not silently treated as business decisions.
Recovery objectives and tests
suXus discusses acceptable data loss and downtime for each process, and the technical dependencies affecting them. Recovery procedures are tested periodically or after relevant changes. Tests record what was recovered, how long it took and which exceptions remain open.
Monitoring and follow-up
Backup jobs, storage capacity and relevant errors are monitored within the agreed management boundary. Alerts have an owner, priority and next action. Changes to servers, data locations and applications must be incorporated into protection promptly.
Failover and continuity arrangements
Continuity involves more than a copy of data. Compute capacity, networking, identity, applications, people, communication and decisions may also be needed. suXus documents existing failover facilities, when they are used and which components fall outside the service.
Separate service: Microsoft Cloud Protection
Protection by suXus covers Microsoft 365 Backup, Microsoft Entra ID backup, Azure Backup, ransomware recovery and cloud governance. This cloud service has its own recovery and governance decisions and is not combined with traditional infrastructure backup.
Responsibilities
Responsibilities
suXus documents which systems and data are covered, who reports changes, who follows up alerts, who can request recovery and who accepts operation after recovery. Dependencies involving customers, suppliers and connections are made explicit.
Outcomes
Outcomes
A protection matrix, agreed recovery points and retention periods, monitoring, recovery procedures and reports of completed recovery tests. Failover and continuity are included only where concrete agreements and facilities exist.
Frequently asked questions
Is off-site backup the same as failover?
No. Off-site storage protects a copy against risks at the primary location. Failover also requires systems, access, connectivity, procedures and tested responsibilities.
Does this page cover Microsoft 365 Backup?
No. Microsoft 365 Backup, Microsoft Entra ID backup, Azure Backup, ransomware recovery and cloud governance remain part of Protection by suXus.