Complete backup set
We coordinate the data directory or object storage, database, configuration, custom apps, themes, secrets and keys needed to recover.
Nextcloud resilience
A backup matters only when it can restore coherent data and service.
We design Nextcloud continuity around the impact on work. Data, database, configuration, apps and keys are protected as one system, and the recovery path is tested against agreed RPO and RTO objectives.
Measurable continuity
Backup, redundancy and high availability solve different problems.
Redundancy can keep a service running when a component fails, but it can also replicate deletion, malicious encryption or application error. Backup preserves earlier states but does not itself reduce the time needed to rebuild an environment. High availability shortens certain outages while increasing operational cost and complexity.
We first establish which interruptions are acceptable and how much data may be lost. We then build a coherent set of copies, automation, monitoring, dependencies and runbooks. Exercises measure real timings and expose missing credentials, unrecoverable keys or steps that existed only on paper.
Continuity design
Protect the complete service, not just the files folder.
Frequency, retention and isolation are selected according to criticality and threat model.
Segregated, protected copies
We separate credentials and destinations from the operating domain, applying encryption, retention and modification protection where specified.
Recovery exercises
We restore into a controlled environment, check integrity and access, and record duration, issues and corrective action.
End-to-end monitoring
We monitor availability, queues, errors, certificates, capacity, databases, storage and job success without mistaking a successful job for a valid backup.
Proportionate redundancy
We consider redundant components and highly available designs only when risk, RTO and budget justify their complexity.
Runbooks and communication
We define escalation, decision authority, alternative channels, recovery criteria and evidence collection during an incident.
Resilience lifecycle
Objectives are tested, not assumed.
Continuity evolves with volumes, dependencies, apps and the importance of the service.
- Control 01
Define impact, RPO and RTO
We connect time and tolerable data loss to business processes, distinguishing failure, error and attack scenarios.
- Control 02
Design copies and dependencies
We define frequency, retention, destinations, keys, bandwidth and the order in which components are rebuilt.
- Control 03
Exercise recovery
We conduct bounded exercises, measure the result and verify data, authentication, apps and integrations.
- Control 04
Correct and repeat
We update runbooks and architecture after exercises, incidents, growth or significant platform changes.
Evidence of recoverability
“Backup completed” does not mean “service recoverable”.
A job can finish without every component, without usable keys or without enough recovery capacity. We therefore distinguish copy status, integrity checking and full exercises, recording the date, scope, duration and deviations for each test.
Frequently asked questions
Clear answers before we define the scope.
01How often is Nextcloud backed up?
Frequency follows the RPO: how much activity the organisation can accept losing in a defined scenario. Databases, files and configuration can need different schedules but must be recoverable to a coherent state. The specific plan is documented in the service.
02What is the difference between RPO and RTO?
RPO is the maximum period of data the organisation aims to avoid losing; RTO is the target time to restore the service. They are agreed objectives for defined scenarios, not implicit guarantees attached to any installation.
03Do backups protect against ransomware and deletion?
They can reduce the impact when copies are separated, protected by different credentials, retained long enough and checked before recovery. An attacker with access to the same administrative domain may otherwise damage the backups too.
04Are high availability and backup the same?
No. High availability aims to continue service through certain failures; backup allows return to an earlier state. A critical design may need both, together with monitoring, procedures and prepared people.
Nextcloud is a registered trademark of Nextcloud GmbH. Nebulas Software provides independent consulting, development and managed services; available functions depend on the agreed edition, apps and architecture.
Continuity plan
Measure what Nextcloud must recover and how quickly.
Share volumes, growth, dependencies and the impact of downtime, and we will turn priorities into a testable plan.
Define your RPO and RTO