Retain
Retention periods defined around your operations. Keep what you need for as long as you need it.
Backup and continuity
Don’t let one mistake erase your company’s work.
We protect your data with retention, separate backups and recovery tests.
Assess my backups
Protect
Separate copies, encryption and least-privilege access controls, according to the solution.
Recover
Regular recovery tests and clear processes to resume operations with confidence.
Microsoft 365
Microsoft Purview
Retention policies and labelsWe apply policies and labels to retain information for the period your organization defines.
Google Workspace
Google Vault
Retention rulesWe define rules to retain data from users and supported Google Workspace services.
The data that drives your business.
Consistent backups according to version and database engine, retention and application-level tests.
Connecting and protecting what matters.Saint
Profit Plus
SAP Business One
Other systems
How we back up Saint, Profit Plus and SAP Business One
We review each installation’s version, engine and dependencies. For SQL Server, we combine full, differential and transaction-log backups as appropriate to the recovery model; for SAP HANA, we use compatible platform mechanisms. We include required files and configuration, and validate restoration with the application, not just the backup file.
Shared documents. Recoverable versions.
- Previous Versions and VSS: recovery points according to server configuration.
- Separate backups: a copy outside primary storage.
- Access control: we verify files, permissions and access after restoration.
Snapshots do not replace backups. They help with changes or deletions; a separate copy protects against storage failures.
3 copies · 2 types of storage · 1 offsite
3 copiesOriginal + 2 backups
2 storage typesDifferent media or technologies
1 offsiteSeparate from the primary site
Isolated or immutable copies according to the environment.
ISO/IEC 27001 certification
Defined backups. Tested recovery.
ISO/IEC 27002:2022 · Control 8.13: information backup.
Example: retention periods defined around your operations
Daily
For rapidly changing data and daily operations.
Weekly
For tracking and business cycles.
Monthly
For historical records and audit requirements.
Periods are tailored to your needs, capacity and internal policies.
How we recover
Request
Confirm scope and priority.
Locate
Find the appropriate version.
Restore
Restore and verify integrity.
Validate
Confirm access and functionality.
Frequently asked questions
What happens if something is deleted by mistake?
We review the deletion time and available versions or backups. We isolate the destination when needed, restore a copy and validate the data with your team. Recovery depends on a retained, usable recovery point.
Can I recover earlier versions?
Yes, when versioning, retention policies or backups preserve them. We define the included data and test recovery before it is needed.
How often do you test recovery?
Frequency is agreed according to criticality, changes and recovery objectives. We document what was restored, how long it took and any required adjustments.
Where are my backups stored?
We can combine local, offsite and cloud storage. We define location, access, encryption and separation from the primary environment, including isolated or immutable copies where supported.
Can I choose retention periods?
Yes. We align them with business needs, available storage and applicable requirements. Daily, weekly and monthly generations are an example, not a universal requirement.
Does Microsoft or Google retention replace a backup?
They serve different purposes. Purview and Vault retain information within their policy scope and supported services. For operational restores and an independent copy, we assess backup tools, licensing and specific tests.
Let’s assess your backup strategy.
Let’s define what to retain, where to protect it and how to recover it to strengthen your business continuity.