Data BackupPublished on · Author: WSV Redaktion· Reviewed on

Backup in a German Data Center: What SMEs Should Check Before the First Upload

A German data center is a good start, but not proof of data protection on its own. This checklist shows what to clarify before the first upload: operator and sub-processors, data processing agreement, encryption and keys, deletion, recovery and how costs scale with data volume.

A woman and a man review data on a laptop together in a data centre, next to server racks with network cables.

Image: AI-generated

Your data is stored in Germany, so data protection is taken care of? It is not quite that simple. A backup in a German data center is a good start: the copy is physically separate from your office, and for the storage itself the data does not leave the European Economic Area. What the location does not tell you is who runs the service, who works in the background, who holds the key and how quickly you get your data back in an emergency. This checklist helps you clarify exactly that before the first upload. It also shows how costs build up with data volume.

Who is it for? Management, office administration and IT in SMEs who are choosing or reviewing an online backup. The outcome: Questions for the provider and the documents you should have afterwards. Brief orientation, not legal advice; clarify individual questions with your data protection officer.

An example: "It's all in Germany anyway"

Imagine a fictional tax advisory firm with twelve employees. Until now, the office manager takes the backups home on a USB drive every evening; an online backup is to replace this. The cheapest offer advertises a "data center in Germany", and the firm is ready to sign.

A second look reveals gaps. The data processing agreement (DPA) is only a general reference in the terms and conditions, and there is no list of sub-processors. The backup software comes from a group whose parent company is outside the EU, and its support partly works from there. And the provider manages the key.

The firm requests a complete DPA including the sub-processors. With its data protection officer, it clarifies the additional rules for professionals bound by confidentiality. It sets up encryption with its own key, which is stored in the emergency plan.

The lesson: the location was the first of seven checkpoints, not the last.

Backup in a German data center: What the location guarantees and what it doesn't

The location brings two real advantages: physical separation, because a fire or break-in at the office does not affect the copy in the data center, and storage within the EEA. For the storage itself, there is therefore no transfer to a third country.

Brief orientation, not legal advice. "GDPR-compliant", however, describes the entire processing, not the building. Under Article 5(2) of the General Data Protection Regulation, you must be able to demonstrate compliance, and according to the German Data Protection Conference, engaging a service provider does not relieve you of this overall responsibility.

Conversely, a provider outside the EU is not automatically prohibited: the GDPR allows it if the additional conditions of Articles 44 et seq. are met. A German location is therefore a sensible risk decision, but not a legal requirement.

Topic Covered by location? What you also need
Physical separation Yes Local copy for fast restores
Storage within the EEA Yes –
Contract (DPA) No DPA under Art. 28 GDPR
Sub-processors No List and change notices
Third-country access No Group and support check
Encryption No Before upload, own key
Retention, deletion No Retention periods, deletion plan
Recovery No Timed restore test

The checklist: seven steps before the first upload

The steps follow the order in which you review an offer: first who and where, then contract and access, and finally keys and recovery.

1. Have the location and operator named in writing

"German data center" is a category, not an address. Have the data center, location and operator named, plus the location of any second copy. In its IT-Grundschutz module CON.3, Germany's Federal Office for Information Security (BSI) recommends regulating, among other things, the storage location, availability, authentication methods and encryption in the contract for online backups.

Three companies can be behind one offer: the maker of the backup software, the data center operator and the service provider who supports you. The BSI names the risks: attacks on the provider can also affect your data, and unfavourable contract terms can delay backups in an emergency.

2. Check the data processing agreement and sub-processors

Brief orientation, not legal advice. If your backup contains personal data, such as customer, staff or email data, the provider is generally a processor. In its Short Paper No. 13, the German Data Protection Conference explicitly lists outsourcing backup storage as a typical case, as well as cloud storage where the operator does not need access to the content.

Under Article 28 GDPR, this requires a contract, in writing or in electronic form. Among other things, it covers your instructions, including on third-country transfers, confidentiality, the security measures under Article 32, evidence of compliance, and deletion or return of data at the end of the contract.

The provider may only use sub-processors with your prior authorisation, either specific or general. With a general authorisation, it must inform you of every intended change, and you can object. It must pass its obligations on to sub-processors and remains liable to you for them. According to the Data Protection Conference, remote maintenance and support with possible access to data also count as processing on your behalf.

For professionals bound by confidentiality, such as law firms and medical practices, the Data Protection Conference points out that the conditions of section 203(3) and (4) of the German Criminal Code also apply. More on this in our guide on liability and reporting obligations for data loss.

3. Parent companies and remote access: What the CLOUD Act has to do with it

Brief orientation, not legal advice. The US CLOUD Act established in 18 U.S.C. § 2713 that communication and cloud providers subject to US law must preserve or disclose data in their possession, custody or control when ordered to by authorities or courts, regardless of whether the data is located inside or outside the United States. Besides the location, it therefore matters which group the provider, software maker and operator belong to.

In its Guidelines 05/2021, the European Data Protection Board (EDPB) describes exactly this case: a processor in the EU whose parent company is in a third country. Storage in the EU is not a third-country transfer. But if the processor hands over data at the request of a third-country authority, that would be one. The EDPB therefore advises assessing these circumstances before engaging the processor. Remote access from a third country, for example for support, also counts as a transfer according to the EDPB.

The GDPR counters this: under Article 48, demands for disclosure by courts and authorities of third countries are only recognised if they are based on an international agreement, such as a mutual legal assistance treaty. A provider subject to both legal systems can therefore find itself in a conflict.

So ask in writing about group affiliation and support locations, and keep the key yourself wherever possible (step 5).

4. Read the evidence correctly: C5 attestation and ISO 27001

According to the BSI's C5 FAQ (accessed in October 2026), there is no certificate for C5, but an attestation by auditors. It covers 3 to 12 months retrospectively and is usually repeated every year. Pay attention to:

  • Type 2: It also tests the effectiveness of the controls over a period, whereas Type 1 only covers a specific date.
  • Qualifications: An attestation can also be qualified. As the customer, you evaluate the report yourself.
  • Scope: The attestation only applies to the audited services and regions. C5 explicitly asks for data location and place of jurisdiction.

For ISO 27001, check the scope: does the certificate cover your service or only one site?

5. Define encryption and key control

Encrypt before the upload, in transit and at rest; the BSI recommends regulating encryption in the contract. Just as important is who can decrypt.

In its Recommendations 01/2020, the EDPB considers encryption for backups in third countries an effective supplementary measure only if, among other things, strong encryption is applied before the data is transferred and the keys are under the sole control of the company or an entity entrusted by it within the EEA. Our interpretation, not legal advice: This standard also fits a German data center with group ties abroad. Someone who only holds encrypted data and no key cannot hand over anything readable.

The downside: a lost key makes the backup worthless. The BSI therefore recommends backing up keys separately and checking that encrypted backups can still be restored after a long time. Store the key in your IT emergency plan, with at least two authorised people. The backup console also needs sign-in with a second factor.

6. Regulate retention, deletion and the end of the contract

Brief orientation, not legal advice. Under Article 5(1)(e) GDPR, personal data may only be stored for as long as necessary for the purpose. Set retention periods for each type of data.

It gets difficult when someone requests erasure of their data (Article 17). According to an EDPB report from 2026, depending on the technical settings and risks, it may not always be advisable to modify backups after the fact. In that case, organisations should keep track of erasure requests and apply them again after a restore. At the same time, the BSI requires that backups cannot be overwritten, whether deliberately or accidentally.

For the end of the contract, Article 28(3)(g) GDPR provides that the provider deletes or returns the data at your choice. Ask for a deadline and a confirmation. Incidentally, a backup is not an archive; what applies to invoices and receipts is explained in our guide on GoBD-compliant archiving.

7. Calculate and test recovery

According to the BSI, the backup system and network connection should be designed so that the permitted backup and recovery times are not exceeded. So work out the restore time in advance:

Data volume at 100 Mbit/s at 500 Mbit/s
500 GB approx. 11 hrs approx. 2.2 hrs
1 TB approx. 22 hrs approx. 4.4 hrs
2 TB approx. 44 hrs approx. 9 hrs

Theoretical values with the connection fully utilised, without overhead, compression or rebuilding. Only a restore test shows the real values.

The first full backup also takes time, because it transfers the entire data set. For fast restores, a local copy is usually part of the setup, while the data center holds the copy for disasters. How the two work together is shown in our 3-2-1-1-0 backup strategy.

Test recovery regularly and time it. The BSI requires regular tests, and Article 32 GDPR requires the ability to restore data in a timely manner and its regular review. You can estimate what an hour of downtime costs with our downtime cost calculator.

What does a data center backup cost? The logic by data volume

Costs depend mainly on three factors: the storage used, the number of servers backed up and the retention period. The longer you keep backup versions and the more your data changes, the more storage they use.

How to check an offer:

  1. Data volume: How much storage do your backups use, including retained versions, and how fast is the data set growing?
  2. Price: What is a flat fee, and what is billed per server or unit of storage? Multiply the expected storage by the price per unit, add the fixed components and extrapolate over the minimum term.
  3. Additional costs: Do restores cost extra, are there travel costs?

A fictional example: A plumbing supplies wholesaler with 40 employees wants to back up its merchandise management server to a data center as well. Management assumes that after an outage "everything will be back in an hour or two". IT does the maths with assumed values: around 1.5 TB of backup data and a 100 Mbit/s connection. In purely arithmetical terms, the transfer back alone takes a good 33 hours, without overhead and without rebuilding the server. In addition, backups are to be kept for twelve months, and each retained version uses additional storage.

The solution: a local copy for a fast restart, the data center for disasters, retention periods per data type and a timed restore test. The lesson: data volume determines both price and restart time. Both belong on the table before the contract is signed.

For comparison, the list prices of our online backup for servers, as stated on the product page (valid from 16 August 2026): "Online backup – €110.00/month per server" with "Max. 1,000 GB (1 TB) of storage including monitoring of the backup by your IT service provider"; "Additional 100 GB of storage – from €7.00/month". Minimum term 12 months, payment annually in advance, plus any travel costs; all prices net, plus statutory VAT. Before setup, we clarify your servers, applications, data and required storage.

The checklist to copy

Enter the provider's answers and file the evidence; a tick without a document does not count.

Checkpoint Question for the provider Evidence
Location Which data center, which location? Stated in the contract
Second copy Where is a geo-redundant copy kept? Stated in the contract
Operator Who runs the software and the data center? Sub-processor list
DPA Is there a DPA under Art. 28? Concluded DPA
Changes How do I learn about new sub-processors? Clause in the DPA
Third country Parent company or support outside the EU? Written statement
Attestation C5 Type 2 or ISO 27001, what scope? Current report
Encryption Before upload, in transit, at rest? Technical description
Key Who can decrypt? Written arrangement
Access Strong sign-in to the console? Configuration
Retention How long, protected against overwriting? Retention plan
Contract end Return or deletion, deadline? Clause in the DPA
Restore Duration and cost of a restore? Restore test record
Costs What counts as data volume? Price sheet

These five documents you should have afterwards:

  • DPA with a list of sub-processors
  • Written details of the location and the second site
  • Current C5 report or ISO 27001 certificate with scope
  • Key arrangement and where it is stored in the emergency plan
  • Record of the first restore test with measured duration

Common mistakes

Accepting "GDPR-compliant" without checking. A typical case is an advertising claim replacing a look at the contract. Ask for the evidence.

Signing the DPA but never looking at the sub-processors. A typical case is a DPA whose annex listing the sub-processors nobody has read. That is exactly where it says who actually stores or supports your data.

Entrusting the key to a single person. Also typical: an external administrator encrypts properly with their own password but documents it nowhere. If the server fails and that person cannot be reached, the backups are complete but unreadable. Key control also means key responsibility.

Never timing the restore. A typical case is a green tick in the backup log but no timed restore. Only the test shows whether the restart time suits your business.

When outside help makes sense

Outside help pays off when nobody in-house has time for contract reviews, key management and restore tests. We look after more than 300 servers and more than 1,500 endpoints.

Our online backup is based on Acronis Cyber Cloud. The backups are transferred, encrypted, to a German data center every night, and our service technicians monitor the process. Ask us, as you would any other provider, about the location, operator and sub-processors before you sign. Have the data processing agreement and the list of sub-processors presented to you before the first backup runs. That applies to every provider. We agree retention individually: up to twelve months, longer on request. With our online backup, who can decrypt and restore data depends on the key and access management we set out in the quote.

Our Backup Check & Restore Test checks whether anything can really be restored from an existing backup: a test restore into a separate environment, followed by a report with prioritised recommendations. How much difference a separate backup makes in an emergency is shown by the anonymised cases from our customer support.

Frequently asked questions

Is a backup in a German data center automatically GDPR-compliant?

No, the location is only one building block. The GDPR additionally requires a data processing agreement, protective measures such as encryption and timely recoverability, and rules for retention and deletion. Your company remains responsible, even if a service provider stores the data.

What does the US CLOUD Act mean for backups stored in Germany?

The US CLOUD Act requires providers subject to US law to disclose requested data in their possession or control, regardless of where it is stored. The European Data Protection Board advises assessing such third-country laws before engaging a provider. As an effective supplementary measure for backups in third countries, it names, among other things, strong encryption before transfer with keys held solely by you or an entity within the EEA. Whether a specific provider is affected is something to clarify with your data protection officer.

Who should hold the key to an encrypted backup?

You decide this deliberately and record it in writing. If you keep the key yourself, the provider cannot read anything. But then it must be available in an emergency: the BSI warns that an encrypted backup is unusable without its key, and recommends backing up keys separately, for example in the IT emergency plan with two responsible people.

How much does a data center backup cost?

That depends mainly on the storage used, the number of servers and the retention period. Also check what counts as data volume, the minimum term and restore costs. According to the product page, our online backup costs €110.00 per month per server with a maximum of 1 TB of storage, and each additional 100 GB from €7.00 per month, all net with a 12-month minimum term.

How long does a restore from the data center take?

That depends mainly on the data volume and the connection. In purely arithmetical terms, 1 TB takes around 22 hours over a fully utilised 100 Mbit/s connection, without overhead. Only a restore test shows the real duration; for fast restores, a local copy is usually part of the setup.

Conclusion

The German data center provides physical separation and keeps storage within the EEA. The contract, sub-processors, third-country access, keys, deletion and recovery remain open until you have checked them. In the tax advisory firm from the example, that would have been enough: a complete DPA, its own key in the emergency plan and a timed restore test.

Would you like to move your server backup to a German data center and settle these points at the same time? Talk to us about our online backup.

Sources

Updated on

WhatsAppRequest adviceGet support

Get in touch

Privacy settings

We use cookies and other technologies on our website. Some of them are essential, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized ads and content or ad and content measurement.

There is no obligation to consent to the processing of your data in order to use this offer. You can withdraw or adjust your selection at any time under settings. Please note that due to individual settings, not all functions of the website may be available.

We use technically necessary storage for operating this website. Optional services (statistics, marketing, external media) are only loaded after your consent.

Privacy settings