PostgreSQL 数据库案例
postgresql数据库恢复 PG数据库无法启动恢复 postgresql数据库损坏修复
postgresql数据库恢复 PG数据库无法启动恢复 postgresql数据库损坏修复
客户名称 保密
数据类型 postgresql 11.2
数据容量 50 GB
故障类型 服务器异常断电导致数据库损坏无法启动,启动PG服务报错.
2022-07-04 16:48:45.655 HKT [23532] LOG: database system was interrupted; last known up at 2022-07-04 09:45:56 HKT
2022-07-04 16:50:06.316 HKT [23532] LOG: database system was not properly shut down; automatic recovery in progress
2022-07-04 16:50:06.323 HKT [23532] LOG: redo starts at 4E/A8C32EF8
2022-07-04 16:50:06.323 HKT [23532] LOG: invalid record length at 4E/A8C32F30: wanted 24, got 0
2022-07-04 16:50:06.323 HKT [23532] LOG: redo done at 4E/A8C32EF8
2022-07-04 16:50:11.845 HKT [29376] LOG: database system is ready to accept connections
2022-07-04 16:52:11.840 HKT [29376] LOG: could not open file "postmaster.pid": No such file or directory
2022-07-04 16:52:11.840 HKT [29376] LOG: performing immediate shutdown because data directory lock file is invalid
2022-07-04 16:52:11.841 HKT [29376] LOG: received immediate shutdown request
2022-07-04 16:52:11.841 HKT [29376] LOG: could not open file "postmaster.pid": No such file or directory
2022-07-04 16:52:11.842 HKT [29028] WARNING: terminating connection because of crash of another server process
2022-07-04 16:52:11.842 HKT [29028] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2022-07-04 16:52:11.842 HKT [29028] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2022-07-04 16:52:11.875 HKT [29376] LOG: database system is shut down
修复结果 手动修正损坏的的事务 重新启动PG服务, 顺利启动后 做备份导出,还原到客户新库完成恢复。完整度100%.
客户满意 是
耗费工时 1 小时
深圳极佳数据救援中心友情提醒:重要数据一定要勤备份,遇到数据丢失 数据损坏 等问题,要第一时间联系专业人士。
对于各类主流数据库,我们可以做最底层的数据恢复及数据修复,对于数据库的某些特定故障我们保证数据库100%原模原样恢复,
无论多大的数据库都立等可取。