Hosting and maintenance / backup and website security
Backup and security
A recovery plan based on the data that matters, copies in separate destinations and restoration checks, complemented by protection measures.
Useful safety copies when data need to be retrieved
We define backups for projects administered on SIDECUBE infrastructure: what to save, where to store and how to check restoration. Data recovery complements access protection and updates.
- Inventory dataWe identify the files, databases and configurations needed for recovery. External services shall be treated separately.
- Children in multiple locationsWe keep backups in multiple locations; the plan specifies the frequency, destinations and retention period, according to the pace of the data change.
- Restoration verifiedWe check the integrity of the backups and go through restoration scenarios in a suitable environment, without confusing the existence of the archive with functional recovery.
- Protection and recoveryBackup helps after data loss; permissions, updates and access control reduce the risk of incident.
What the service can include
Backup frequency, retention and recovery objectives are defined for each project. We do not assume instant recovery or zero data loss.
01Data inventory
02Backup program
03Destinations and storage
04Backup verification
05Test restoration
06Recovery procedure
Recovery requirements shall be established prior to the incident
- We are clarifying the amount of data and the changes that need to be protected.
- We're checking copies and dependencies for restoration.
- We document the responsible person and the recovery steps.
- We agree on the limits on acceptable data loss and the duration of recovery.
Recommended pages
Pages related to this type of service: technologies, fields of activity, guides and complementary services.
Frequently Asked Questions
Before we begin the project
Choice, stages and support for Backup and security.
01 / Service
Purpose and conditions
Backup enough for security?
No. Copies help to recover, and updates, permissions and access protection reduce the risk of incidents.
How often are copies made and how long are they kept?
The frequency and storage shall be determined by the volume and rhythm of the data change. Recovery requirements are specified in the project agreement.
02 / Preparation
take-over and access
How can an existing project be taken over?
We evaluate the platform, data and integration, then clarify compatibility, remedies and migration to SIDECUBE infrastructure. An initial audit can be delivered prior to the takeover decision; the full recurrent administration is done in our environment.
What information is needed for the estimation?
Platform and services used, data volume, important operations and known problems. We determine the works, access and responsibilities prior to intervention; passwords are not sent via public forms.
03 / Verification
Validation and limits
How do you check the result?
We are clarifying the amount of data and the changes that need to be protected. We're checking copies and dependencies for restoration. We document the responsible person and the recovery steps. We agree on the limits on acceptable data loss and the duration of recovery.
What conditions and costs need to be clarified?
Backup frequency, retention and recovery objectives are defined for each project. We do not assume instant recovery or zero data loss.