Overview
Service type | Scenario | Included in standard service (contract) | Counts against contractual limit / SLA limit | What this means for you |
|---|---|---|---|---|
Refresh | Refresh of a target environment with a current snapshot from PROD, including filestore | Yes – a limited number of Refreshes per target environment is included in the itdesign Clarity SaaS Hosting Service Agreement | Yes – each such Refresh is counted against the SLA limit for the target environment | You can refresh (for example) TEST from PROD within your included quota. Each Refresh uses part of your contractually included number of Refreshes for that environment. |
Refresh (as part of an upgrade) | Refresh that is performed as part of an upgrade | Yes – performed as part of the upgrade within the service | No – explicitly not counted against the SLA limit | When we upgrade your environment, any Refreshes required for the upgrade do not reduce your contractual Refresh quota. |
Refresh using nightly or manually created backup | Refresh where the source is the nightly backup or a manually created backup instead of a live PROD snapshot | Yes – listed as a special case included in the standard service | Yes – counted against the SLA limit | You can request a Refresh from a backup (nightly or manual). It is part of the standard service, but it consumes from your contractual Refresh limit. |
Restore using nightly backup | Restore of an environment using the nightly backup (database only, no filestore) | Yes – explicitly stated as part of the standard service | Yes – counted against the SLA limit | You can reset an environment to the state of the last nightly backup as part of your contract. Each such Restore counts towards your contractual SLA limit. |
Restore using Point‑in‑Time Recovery (PITR) | Restore using PITR with up to 7 days restoration window and minute‑level precision | No – not part of the standard service and performed manually upon request only | No – it is outside the standard service and therefore not part of the included SLA / Refresh‑Restore limit | For special cases where you need to restore to an exact point in time (within the last 7 days), PITR is available on request but is not covered by your standard contract or included quota. |
Refresh
A Refresh transfers data (file system and database) from a source environment to a target environment (for example, source: PROD, target: TEST). A snapshot of the source data is taken at the time the refresh starts. This snapshot represents the exact data state at that moment.
A Refresh can be scheduled at any time. If the scheduled time is outside the service hours (Monday to Friday, 09:00–17:00), the process is executed unattended. In this case, the snapshot is created automatically at the scheduled time and used for the refresh. To ensure that specific data is included, all required data must be fully available in the source environment before the scheduled start time.
During a Refresh, the source system remains available at all times. The target system is not available during the process.
Restore
A restore allows you to reset a database to a previous state while remaining within the same environment (for example, TEST to TEST). The filestore is excluded from this process, ensuring that only the database itself is reverted. This provides a controlled and reliable way to return to a defined point in time, helping to resolve issues, validate changes, or restore a stable baseline without impacting other environments.
To support different use cases and requirements, there are two restore variants available.
- Restore Using the Nightly Backup
This restore variant uses the latest available nightly backup within the same environment. It is part of the standard service and counted against the SLA limit. All executions are tracked and contribute to the defined SLA usage. - Restore Using Point-in-Time Recovery (PITR)
Our Clarity SaaS backup supports Point-in-Time Recovery with a restoration window of up to 7 days. PITR allows restoring the database to a specific point in time with minute-level precision. This variant is not part of the standard service and is performed manually upon request only.
Restore Within the Standard Service
- Restores using the nightly backup are part of the standard service and are counted against the SLA limit
- Restores using PITR are not part of the standard service and are available only manually upon request
During a Restore, the target system is not available. The system is overwritten with the selected data state. The duration of the process depends on the data volume and the performance class of the database and cannot be determined precisely. A Restore is carried out exclusively during service hours.
