{"id":4666,"date":"2026-06-14T19:31:06","date_gmt":"2026-06-14T19:31:06","guid":{"rendered":"https:\/\/cloudsave.app\/?p=4666"},"modified":"2026-06-15T15:10:51","modified_gmt":"2026-06-15T15:10:51","slug":"den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer","status":"publish","type":"post","link":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/","title":{"rendered":"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer"},"content":{"rendered":"

I den h\u00f8jrisikofyldte verden af databaseadministration og site reliability engineering findes der et velkendt aksiom: Schr\u00f6dingers backup<\/em>. Tilstanden af enhver backup er ukendt, indtil du fors\u00f8ger at gendanne den. Indtil det \u00f8jeblik eksisterer den i en kvantetilstand, hvor den er b\u00e5de perfekt brugbar og fuldst\u00e6ndig korrupt.<\/p>\n

For DevOps-ingeni\u00f8rer og DBA’er er det det ultimative mareridt at opdage, at en kritisk databasebackup er korrupt under en aktiv h\u00e6ndelse. Det forvandler en rutinem\u00e6ssig gendannelsesoperation til en katastrofal begivenhed med datatab. Denne “tavse morder” af dataintegritet g\u00e5r ofte ubem\u00e6rket hen, fordi backup-jobs ofte rapporterer en succesfuld Exit Code 0<\/code>, selv n\u00e5r den underliggende nyttelast er kompromitteret.<\/p>\n

I denne omfattende guide vil vi dissekere anatomien af backup-korruption, udforske databasespecifikke valideringsteknikker og demonstrere, hvordan man bygger automatiserede, skudsikre gendannelses-pipelines til produktionsmilj\u00f8er.<\/p>\n

Anatomien af backup-korruption<\/h2>\n

For at opdage korruption skal du f\u00f8rst forst\u00e5, hvordan den opst\u00e5r. Backup-korruption falder generelt i to kategorier: fysisk (infrastrukturniveau) og logisk (applikationsniveau).<\/p>\n

Fysisk korruption<\/h3>\n

Fysisk korruption opst\u00e5r, n\u00e5r de faktiske bits p\u00e5 lagringsmediet \u00e6ndres. Dette kan ske under l\u00e6seprocessen fra kildedisken, under netv\u00e6rkstransport eller ved hvile p\u00e5 m\u00e5llageret.
\n* Bit Rot:<\/strong> Gradvis nedbrydning af lagringsmedier kan vende bits lydl\u00f8st.
\n* Transportfejl:<\/strong> Selvom TCP har checksums, er de notorisk svage (16-bit). Milj\u00f8er med h\u00f8j gennemstr\u00f8mning kan opleve tavs datakorruption over netv\u00e6rket, som TCP ikke fanger.
\n* Fejl i storage-controller:<\/strong> Hardwarefejl i RAID-controllere eller SAN-fabrics kan skrive skraldedata, mens de rapporterer succes til operativsystemet.<\/p>\n

Logisk korruption<\/h3>\n

Logisk korruption er uden tvivl farligere, fordi selve backup-filen er intakt, men dataene indeni er \u00f8delagte.
\n* Garbage In, Garbage Out (GIGO):<\/strong> Hvis din live-database har et korrupt indeks eller en beskadiget side, kan dit backup-v\u00e6rkt\u00f8j trofast kopiere den korrupte side. Backup-jobbet lykkes, men gendannelsen vil fejle eller resultere i en \u00f8delagt database.
\n* Ufuldst\u00e6ndige transaktioner:<\/strong> Snapshots p\u00e5 filsystemniveau taget uden korrekt at fryse database-I\/O (f.eks. ved ikke at bruge FLUSH TABLES WITH READ LOCK<\/code> i MySQL) resulterer i beskadigede sider og uigenkaldelige tilstande.<\/p>\n

Proaktiv detektering: Checksums og kryptografisk hashing<\/h2>\n

Den f\u00f8rste forsvarslinje mod fysisk korruption er kryptografisk validering. Det er utilstr\u00e6kkeligt at stole p\u00e5 filst\u00f8rrelser eller \u00e6ndringsdatoer.<\/p>\n

Aktivering af checksums p\u00e5 databaseniveau<\/h3>\n

Moderne relationelle databasestyringssystemer (RDBMS) underst\u00f8tter checksums p\u00e5 sideniveau. N\u00e5r det er aktiveret, beregner databasen en checksum for hver side, f\u00f8r den skrives til disken. N\u00e5r siden l\u00e6ses (enten af en foresp\u00f8rgsel eller en backup-proces), verificeres checksummen.<\/p>\n

For PostgreSQL<\/strong> kan du aktivere datachecksums under klyngeinitialisering:<\/p>\n

# Initialiser en ny PostgreSQL-klynge med checksums aktiveret\ninitdb --data-checksums -D \/var\/lib\/postgresql\/data\n<\/code><\/pre>\n
Bem\u00e6rk: Hvis du har en eksisterende PostgreSQL-klynge, kan du bruge pg_checksums<\/code>-v\u00e6rkt\u00f8jet til at aktivere dem offline.<\/em><\/p>\n
For Microsoft SQL Server<\/strong> skal du sikre dig, at PAGE_VERIFY<\/code> er sat til CHECKSUM<\/code> (standard i moderne versioner, men v\u00e6rd at verificere p\u00e5 \u00e6ldre systemer):<\/p>\n
ALTER DATABASE [ProductionDB] SET PAGE_VERIFY CHECKSUM;\nGO\n<\/code><\/pre>\n
Validering af backups ved hvile<\/h3>\n
N\u00e5r backuppen lander p\u00e5 dit lagringsm\u00e5l, skal dens integritet verificeres kryptografisk. Enterprise backup-platforme som CloudSave beregner og verificerer automatisk SHA-256 hashes af backup-blokke under transport og ved hvile. Hvis du administrerer brugerdefinerede scripts, skal du implementere dette manuelt:<\/p>\n
# Generer SHA-256 hash efter backup-oprettelse\nsha256sum prod_db_backup.tar.gz > prod_db_backup.tar.gz.sha256\n\n# Verificer hashen p\u00e5 storage-serveren\nsha256sum -c prod_db_backup.tar.gz.sha256\n<\/code><\/pre>\n
Databasespecifikke valideringsteknikker<\/h2>\n
Forskellige database-motorer tilbyder indbyggede v\u00e6rkt\u00f8jer til at verificere integriteten af deres backup-artefakter.<\/p>\n
PostgreSQL: pg_verifybackup<\/code><\/h3>\n
Introduceret i PostgreSQL 13, er pg_verifybackup<\/code> en game-changer for fysiske backups taget med pg_basebackup<\/code>. Den l\u00e6ser backup_manifest<\/code>-filen, der genereres under backuppen, og verificerer, at alle filer er til stede, og at deres checksums stemmer overens.<\/p>\n
# K\u00f8r verifikation mod et fysisk base backup-bibliotek\npg_verifybackup \/mnt\/backups\/postgres\/base_backup_20231025\/\n<\/code><\/pre>\n
Hvis en enkelt bit er vendt i nogen af datafilerne, vil pg_verifybackup<\/code> kaste en fatal fejl, hvilket g\u00f8r det muligt for dine overv\u00e5gningssystemer at advare DBA-teamet med det samme.<\/p>\n
Microsoft SQL Server: RESTORE VERIFYONLY<\/code><\/h3>\n
SQL Server tilbyder en indbygget kommando til at verificere den fysiske integritet af en backup-fil uden faktisk at gendanne den. Den tjekker backup-headere og validerer side-checksums (hvis de var aktiveret under backuppen).<\/p>\n
RESTORE VERIFYONLY \nFROM DISK = 'Z:BackupsProdDB_Full.bak' \nWITH CHECKSUM;\n<\/code><\/pre>\n
Advarsel:<\/strong> RESTORE VERIFYONLY<\/code> bekr\u00e6fter kun, at backup-filen er l\u00e6sbar, og at fysiske checksums stemmer overens. Den garanterer ikke<\/em> logisk integritet. For at sikre logisk integritet skal du udf\u00f8re en fuld gendannelse og k\u00f8re DBCC CHECKDB<\/code>.<\/p>\n
MySQL \/ InnoDB: Percona XtraBackup<\/h3>\n
For MySQL-milj\u00f8er h\u00e5ndteres fysiske backups ofte af Percona XtraBackup. Backup-processen best\u00e5r i at kopiere filer, men backuppen er ikke konsistent, f\u00f8r transaktionsloggene (redo logs) er anvendt. --prepare<\/code>-fasen fungerer som et indbygget integritetstjek.<\/p>\n
# Forberedelse af backuppen anvender redo logs. \n# Hvis backuppen er korrupt, vil dette trin fejle.\nxtrabackup --prepare --target-dir=\/data\/backups\/mysql\/\n<\/code><\/pre>\n
Guldstandarden: Automatiseret gendannelsestest<\/h2>\n
Checksums og verifikationskommandoer er n\u00f8dvendige, men de er ikke tilstr\u00e6kkelige. Den eneste m\u00e5de at bevise, at en backup er brugbar, er at gendanne den. I moderne DevOps-milj\u00f8er skal denne proces v\u00e6re fuldt automatiseret.<\/p>\n
Ved at behandle backups som kode kan du bygge en CI\/CD-pipeline til dine databasegendannelser. Denne pipeline b\u00f8r klarg\u00f8re flygtig infrastruktur, udf\u00f8re gendannelsen, k\u00f8re valideringsforesp\u00f8rgsler og nedbryde milj\u00f8et igen.<\/p>\n
Opbygning af en automatiseret gendannelses-pipeline<\/h3>\n
Herunder er et eksempel p\u00e5 et Bash-script, der kunne udl\u00f8ses dagligt af et cron-job eller en CI-runner (som GitLab CI eller GitHub Actions) for at validere et logisk PostgreSQL-dump.<\/p>\n
#!\/bin\/bash\nset -e\n\nBACKUP_FILE="\/mnt\/storage\/prod_db_latest.dump"\nDB_NAME="prod_db"\nCONTAINER_NAME="pg_restore_test"\n\necho "[INFO] Starter automatiseret gendannelsestest..."\n\n# 1. Start en flygtig PostgreSQL-container\ndocker run --name $CONTAINER_NAME \n  -e POSTGRES_PASSWORD=testpass \n  -d postgres:15\n\n# Vent p\u00e5 at PostgreSQL er klar\necho "[INFO] Venter p\u00e5 at databasen initialiseres..."\nuntil docker exec $CONTAINER_NAME pg_isready -U postgres; do\n  sleep 2\ndone\n\n# 2. Opret m\u00e5ldatabasen\ndocker exec $CONTAINER_NAME psql -U postgres -c "CREATE DATABASE $DB_NAME;"\n\n# 3. Udf\u00f8r gendannelsen\necho "[INFO] Gendanner backup..."\ndocker cp $BACKUP_FILE $CONTAINER_NAME:\/tmp\/backup.dump\ndocker exec $CONTAINER_NAME pg_restore -U postgres -d $DB_NAME -1 \/tmp\/backup.dump\n\n# 4. K\u00f8r logiske valideringsforesp\u00f8rgsler\necho "[INFO] K\u00f8rer valideringsforesp\u00f8rgsler..."\n# Tjek om brugertabellen har mere end 10.000 poster\nUSER_COUNT=$(docker exec $CONTAINER_NAME psql -U postgres -d $DB_NAME -t -c "SELECT COUNT(*) FROM users;")\n\nif [ "$USER_COUNT" -lt 10000 ]; then\n    echo "[ERROR] Logisk validering fejlede. Forventede >10000 brugere, fandt $USER_COUNT"\n    # Udl\u00f8s PagerDuty \/ Slack-advarsel her\n    exit 1\nelse\n    echo "[SUCCESS] Logisk validering best\u00e5et. Antal brugere: $USER_COUNT"\nfi\n\n# 5. Nedbryd flygtigt milj\u00f8\necho "[INFO] Rydder op..."\ndocker rm -f $CONTAINER_NAME\n\necho "[INFO] Automatiseret gendannelsestest fuldf\u00f8rt med succes."\n<\/code><\/pre>\n
Hvad b\u00f8r du validere?<\/h3>\n
N\u00e5r du udf\u00f8rer automatiseret gendannelsestest, skal du ikke bare tjekke, om databasen starter. K\u00f8r applikationsspecifikke valideringsforesp\u00f8rgsler:
\n1.  R\u00e6kkeantal:<\/strong> S\u00f8rg for, at kernetabeller har det forventede antal r\u00e6kker (f.eks. b\u00f8r users<\/code>-tabellen ikke v\u00e6re tom).
\n2.  Nylige data:<\/strong> Foresp\u00f8rg efter poster oprettet inden for de sidste 24 timer for at sikre, at backuppen ikke er for\u00e6ldet.
\n3.  Referentiel integritet:<\/strong> K\u00f8r scripts for at tjekke for for\u00e6ldrel\u00f8se fremmedn\u00f8gler, hvilket indikerer logisk korruption.<\/p>\n
Overv\u00e5gning og alarmering ved backup-anomalier<\/h2>\n
At opdage korruption, f\u00f8r katastrofen indtr\u00e6ffer, kr\u00e6ver robust observerbarhed. Udover bin\u00e6re succes\/fejl-tilstande b\u00f8r du overv\u00e5ge metadataene for dine backup-jobs for at opdage anomalier.<\/p>\n
Heuristisk overv\u00e5gning<\/h3>\n
Integrer dine backup-metadata i Prometheus og visualiser dem med Grafana. Ops\u00e6t alarmer for f\u00f8lgende heuristikker:
\n*   Pludselige fald i st\u00f8rrelse:<\/strong> Hvis din daglige backup konsekvent er 500 GB, og dagens backup er 50 MB, kan jobbet v\u00e6re fuldf\u00f8rt med succes (Exit Code 0), men det har sandsynligvis kun taget backup af et tomt skema.
\n*   Varighedsanomalier:<\/strong> Hvis en backup, der normalt tager 2 timer, f\u00e6rdigg\u00f8res p\u00e5 5 minutter, er noget blevet sprunget over. Omvendt, hvis det tager 10 timer, kan du have disk-I\/O-nedbrydning, der kan f\u00f8re til korruption.
\n*   Akkumulering af WAL\/arkiv-logs:<\/strong> Hvis din database genererer Write-Ahead Logs (WAL), men backup-systemet ikke arkiverer dem hurtigt nok, risikerer du et hul i din Point-in-Time Recovery (PITR)-k\u00e6de.<\/p>\n
Implementering af 3-2-1-reglen med integritetstjek<\/h2>\n
Den industristandardiserede 3-2-1-backupregel (3 kopier af data, 2 forskellige medier, 1 offsite) er kun effektiv, hvis alle kopier er verificeret.<\/p>\n
Det er her, udnyttelsen af en enterprise-l\u00f8sning som CloudSave drastisk reducerer de operationelle omkostninger. I stedet for at skrive og vedligeholde komplekse bash-scripts for hver database-node, integreres CloudSave direkte med din infrastruktur for at automatisere 3-2-1-livscyklussen. Den tilbyder uforanderlig lagring \u2013 beskyttelse mod ransomware \u2013 og har indbyggede, automatiserede tidsplaner for gendannelsesverificering. CloudSave kan automatisk starte isolerede sandbox-milj\u00f8er, mounte backuppen, k\u00f8re dine brugerdefinerede SQL-valideringsscripts og rapportere sundhedsstatus tilbage til dit centrale dashboard.<\/p>\n
Konklusion<\/h2>\n
Korrupte databasebackups er en tavs morder, der kan \u00f8del\u00e6gge virksomheder. At stole udelukkende p\u00e5 Exit Code 0<\/code> fra et backup-script er et farligt sats.<\/p>\n
For virkelig at beskytte dine produktionsmilj\u00f8er skal du vedtage en “defense-in-depth”-strategi:
\n1.  Aktiv\u00e9r checksums p\u00e5 sideniveau i din database-motor.
\n2.  Brug indbyggede verifikationsv\u00e6rkt\u00f8jer (pg_verifybackup<\/code>, RESTORE VERIFYONLY<\/code>) umiddelbart efter backup-oprettelse.
\n3.  Overv\u00e5g backup-metadata (st\u00f8rrelse, varighed) for heuristiske anomalier.
\n4.  Implementer automatiseret, flygtig gendannelsestest som en del af din daglige operationelle pipeline.<\/p>\n
Ved at skifte fra en passiv “fire and forget”-backupmentalitet til en aktiv “kontinuerlig gendannelsesvalidering”-model sikrer du, at n\u00e5r katastrofen uundg\u00e5eligt indtr\u00e6ffer, er dine data klar, p\u00e5lidelige og fuldt gendannelige.<\/p>\n","protected":false},"excerpt":{"rendered":"
** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Detect Corrupted Database Backups Before Disaster","rank_math_description":"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.","rank_math_focus_keyword":"corrupted database backups","footnotes":""},"categories":[391],"tags":[3326,3327,3328,392,899,2136,3329],"class_list":["post-4666","post","type-post","status-publish","format-standard","hentry","category-database-backup","tag-backup-testing","tag-corrupted-backups","tag-data-integrity","tag-data-loss-prevention","tag-database-administration","tag-devops","tag-restore-testing"],"yoast_head":"\nDetect Corrupted Database Backups Before Disaster<\/title>\n<meta name=\"description\" content=\"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/\" \/>\n<meta property=\"og:locale\" content=\"da_DK\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer\" \/>\n<meta property=\"og:description\" content=\"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/\" \/>\n<meta property=\"og:site_name\" content=\"CloudSave\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-14T19:31:06+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-15T15:10:51+00:00\" \/>\n<meta name=\"author\" content=\"shervinrv\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Skrevet af\" \/>\n\t<meta name=\"twitter:data1\" content=\"shervinrv\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimeret l\u00e6setid\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutter\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/\"},\"author\":{\"name\":\"shervinrv\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"headline\":\"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer\",\"datePublished\":\"2026-06-14T19:31:06+00:00\",\"dateModified\":\"2026-06-15T15:10:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/\"},\"wordCount\":1271,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"keywords\":[\"backup testing\",\"corrupted backups\",\"data integrity\",\"data loss prevention\",\"Database Administration\",\"devops\",\"restore testing\"],\"articleSection\":[\"Database Backup\"],\"inLanguage\":\"da-DK\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/\",\"name\":\"Detect Corrupted Database Backups Before Disaster\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#website\"},\"datePublished\":\"2026-06-14T19:31:06+00:00\",\"dateModified\":\"2026-06-15T15:10:51+00:00\",\"description\":\"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/#breadcrumb\"},\"inLanguage\":\"da-DK\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#website\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/\",\"name\":\"CloudSave\",\"description\":\"CloudSave\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"da-DK\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/#\\\/schema\\\/person\\\/286beefe68281d868e87f46603a7ae4d\",\"name\":\"shervinrv\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"da-DK\",\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"url\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"contentUrl\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\",\"width\":859,\"height\":150,\"caption\":\"shervinrv\"},\"logo\":{\"@id\":\"https:\\\/\\\/cloudsave.app\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/Logo_Name-2.png\"},\"sameAs\":[\"http:\\\/\\\/cloudsave.app\"],\"url\":\"https:\\\/\\\/cloudsave.app\\\/da\\\/knowledge-base\\\/author\\\/shervinrv\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Detect Corrupted Database Backups Before Disaster","description":"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/","og_locale":"da_DK","og_type":"article","og_title":"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer","og_description":"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.","og_url":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/","og_site_name":"CloudSave","article_published_time":"2026-06-14T19:31:06+00:00","article_modified_time":"2026-06-15T15:10:51+00:00","author":"shervinrv","twitter_card":"summary_large_image","twitter_misc":{"Skrevet af":"shervinrv","Estimeret l\u00e6setid":"8 minutter"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/#article","isPartOf":{"@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/"},"author":{"name":"shervinrv","@id":"https:\/\/cloudsave.app\/da\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"headline":"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer","datePublished":"2026-06-14T19:31:06+00:00","dateModified":"2026-06-15T15:10:51+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/"},"wordCount":1271,"publisher":{"@id":"https:\/\/cloudsave.app\/da\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"keywords":["backup testing","corrupted backups","data integrity","data loss prevention","Database Administration","devops","restore testing"],"articleSection":["Database Backup"],"inLanguage":"da-DK"},{"@type":"WebPage","@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/","url":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/","name":"Detect Corrupted Database Backups Before Disaster","isPartOf":{"@id":"https:\/\/cloudsave.app\/da\/#website"},"datePublished":"2026-06-14T19:31:06+00:00","dateModified":"2026-06-15T15:10:51+00:00","description":"** Discover how DevOps engineers and DBAs can detect corrupted database backups before disaster strikes. Learn advanced techniques for PostgreSQL, SQL Server, and MySQL, including automated restore testing and checksum validation.","breadcrumb":{"@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/#breadcrumb"},"inLanguage":"da-DK","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cloudsave.app\/da\/knowledge-base\/den-tavse-dr%c3%a6ber-s%c3%a5dan-opdager-du-korrupte-database-backups-f%c3%b8r-katastrofen-indtr%c3%a6ffer\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudsave.app\/da\/"},{"@type":"ListItem","position":2,"name":"Den tavse dr\u00e6ber: S\u00e5dan opdager du korrupte database-backups, f\u00f8r katastrofen indtr\u00e6ffer"}]},{"@type":"WebSite","@id":"https:\/\/cloudsave.app\/da\/#website","url":"https:\/\/cloudsave.app\/da\/","name":"CloudSave","description":"CloudSave","publisher":{"@id":"https:\/\/cloudsave.app\/da\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudsave.app\/da\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"da-DK"},{"@type":["Person","Organization"],"@id":"https:\/\/cloudsave.app\/da\/#\/schema\/person\/286beefe68281d868e87f46603a7ae4d","name":"shervinrv","image":{"@type":"ImageObject","inLanguage":"da-DK","@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","url":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","contentUrl":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png","width":859,"height":150,"caption":"shervinrv"},"logo":{"@id":"https:\/\/cloudsave.app\/wp-content\/uploads\/2026\/02\/Logo_Name-2.png"},"sameAs":["http:\/\/cloudsave.app"],"url":"https:\/\/cloudsave.app\/da\/knowledge-base\/author\/shervinrv\/"}]}},"_links":{"self":[{"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/posts\/4666","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/comments?post=4666"}],"version-history":[{"count":2,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/posts\/4666\/revisions"}],"predecessor-version":[{"id":5732,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/posts\/4666\/revisions\/5732"}],"wp:attachment":[{"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/media?parent=4666"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/categories?post=4666"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudsave.app\/da\/wp-json\/wp\/v2\/tags?post=4666"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}