The information drives both business and country

ERP Backup #Discovery - My writing is different....✍️

In September–October 2024, I implemented incremental backup strategies on our ERP server while studying Macrium Reflect concepts.

🔍 During this exercise, I discovered that daily overwriting of incremental backups in a database-driven ERP system caused historical data to resurface.

Overwrite Backup= Full + Differential + Incremental
Make sure it increases from 8674kb to 16345kb.

Result or outcome of this process: it reviews
-Balances Account
-Balances Stock
-Sales order cancellation/ Deleted sales order
-Missing stock item
-Deleted Receipt

Things I used in unravelling it...
Overwritten Backup - Explained already...
Resurface hidden things and balanced data.

Screenshot to notice changes
Constant follow up of total sales order
Changes in the Net flow and Net profit.

Any little changes above shows the data has been tampered with.

This happens because databases don’t just add new data — they constantly reorganize, re-index, and touch old blocks. At the block level, backups treat this as “new changes,” pulling old history forward into each backup set.
You still one key 🗝️ chat me up.
Via Whatsapp: https://wa.me/8169115247

📌 Key takeaway: For ERP and financial systems, a hybrid strategy works best — combining database-native backups (for consistency) with full/differential image backups (for disaster recovery).