Skip to main content
Question

How to Backup one Database to several destinations as an on going process?

  • June 10, 2020
  • 1 reply
  • 3 views
mosheg
Forum|alt.badge.img+2
  • mosheg
  • Participating Frequently

We have a customer who wish to backup from DB1 to DB2 and in addition from DB1 to DB3.
They cannot implement a solution, with fork loading.
I assume copy cluster keep epoch for the incremental process.
1. Does it keep epoch per each copy cluster process (i.e. epoch1 for DB2 and epoch2 to DB3)?
2. Can they have a script which will copy DB1 to DB2 and then copy DB1 to DB3?
The plan is to continue the daily backup from DB1 to DB3 even when DB2 is disconnected.

    1 reply

    mosheg
    Forum|alt.badge.img+2
    • mosheg
    • Author
    • Participating Frequently
    • June 11, 2020

    Found that one copycluster.ini file, which contain 2 links for 2 DB servers worked.
    Customer activated single copycluster execution, coping one DB from cluster A to both clusters B and C.
    However, Vertica does not recommend concurrent backups. If you must run multiple backups concurrently, use separate backup and temp directories for each. Having separate backup directories detracts from the advantage of sharing data among historical backups.
    And for each backup activation with the same configuration file, vbr creates an additional backup and might remove the oldest backup.
    See: https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/AdministratorsGuide/BackupRestore/CreatingBackups.htm

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement