Using after image logs, is it a valuable mean of centralizing db backup, as a "backup" solution.
I illustrate :
- backups are centralized but backups are still made on remote sites.
- centralized backups are used to secure backups.
- Day 1 : centralization of complete db backup
- Day 2 : centralization of after image log for Day 2
: AI log truncation
- Day 3 : centralization of AI log for Day 3
: AI log truncation
.../...
- Day n : db problem on remote site
: remote site tries to recover from its local backup (cartridge)
: remote site tries its 7 daily cartridge
: if Day n - 2 succeed in recovering
=> central site sends to remote site logs for Day n-2 and Day n-1
This way allows :
- to add security to backups
- with no remonte-central transfer overcharge
- with no data space overcharge on central site
Remark :
- we have 300 sites
- we have 3Gb DB on each site
- we have more or less 20000 daily transactions
Thanks for your eventually valuable feedback.
Best regards.
I illustrate :
- backups are centralized but backups are still made on remote sites.
- centralized backups are used to secure backups.
- Day 1 : centralization of complete db backup
- Day 2 : centralization of after image log for Day 2
: AI log truncation
- Day 3 : centralization of AI log for Day 3
: AI log truncation
.../...
- Day n : db problem on remote site
: remote site tries to recover from its local backup (cartridge)
: remote site tries its 7 daily cartridge
: if Day n - 2 succeed in recovering
=> central site sends to remote site logs for Day n-2 and Day n-1
This way allows :
- to add security to backups
- with no remonte-central transfer overcharge
- with no data space overcharge on central site
Remark :
- we have 300 sites
- we have 3Gb DB on each site
- we have more or less 20000 daily transactions
Thanks for your eventually valuable feedback.
Best regards.