Context
A backup dashboard can be green while the business still cannot restore its application. A useful cloud support arrangement for teams around the Mediterranean begins with the data needed to deliver a service, the acceptable recovery point and the people who can authorize restoration. Countries and local business calendars differ; select the actual customer location when agreeing a maintenance or recovery exercise.
The UK National Cyber Security Centre recommends making and testing backups. The right technical design depends on the application, storage and business requirements rather than the country name alone.
Plan the support handover
The following are examples of named local time zones for scheduling a customer contact or change window. They are not a promise of a local office, a local-language service or coverage in every location. Some countries span multiple zones; confirm the actual city, date, daylight-saving rules and agreed support hours with the customer.
| Country or market | Example IANA time zone |
|---|---|
| Spain | Europe/Madrid |
| Portugal | Europe/Lisbon |
| Italy | Europe/Rome |
| Greece | Europe/Athens |
| Cyprus | Asia/Nicosia |
| Malta | Europe/Malta |
| Croatia | Europe/Zagreb |
| Slovenia | Europe/Ljubljana |
| San Marino | Europe/San_Marino |
| Türkiye | Europe/Istanbul |
IANA time-zone guidance explains why civil-time rules can change. Save a UTC timestamp as well as the named local zone for every approved maintenance window.
Map the complete recovery set
List the database, uploaded files, encryption keys, application configuration, DNS and identity dependencies. Record the source account and region, backup location, owner and retention. A database snapshot without the corresponding encryption key or application secrets may be unusable during a real incident.
Separate the recovery point objective—how much data loss the business can tolerate—from the recovery time objective—how long restoration may take. Both need agreement with the application owner.
Run an isolated restore exercise
Choose a non-production destination and a representative recovery point. Restore the data and application configuration, then check a meaningful business transaction. Measure elapsed time, identify manual steps and confirm whether the person on call can obtain the necessary permissions without using a shared root account.
Treat customer data carefully in the test environment. Where possible use synthetic or appropriately protected records; arrange deletion and access expiry after the exercise.
Act on evidence, not the backup badge
Record the date of the test, source and destination, checks performed, exceptions and the recovery owner. Investigate a failed or partial restore before changing the retention schedule. Keep a protected copy of the runbook accessible when the primary cloud account or ticketing system is unavailable, and review the plan after an architecture change.
Source and support scope
Primary technical reference. Verify current applicability and provider documentation for your own environment. Clouvenix can discuss the agreed scope through backup and disaster recovery; support hours, coverage, response targets, languages and costs are agreed for each engagement.