Controlling when a backup happens on a node

Answered

Comments

4 comments

  • Official comment
    Geir Ove Grønmo

    Sesam subscriptions (not self-hosted) currently makes backups at a randomized time inside the 22:00-03:00 UTC time window. It is currently not possible to override this.

    What is the use-case for needing to control the backup time?

    Comment actions Permalink
  • Jon Bryndorf

    We have another database that needs to be in sync with the Sesam database and if we need to restore our  database we need to chose a backup that matches a Sesam backup that matches in time (down to minutes it must match) otherwise will we get some conflicts that are close to impossible to resolve.

    0
    Comment actions Permalink
  • Geir Ove Grønmo

    It sounds to me like that is a next-to-impossible approach to take. Is Sesam writing data to that database or is Sesam reading data from the database? What is the reason for the conflicts? Can't you have Sesam all the data a second time? It would be helpful if you could explain the use case in more detail.

    0
    Comment actions Permalink
  • Jon Bryndorf

    Thanks for your reply

    The use case is the following:

    From our system a request for information from a third party solution is send through Sesam. Sesam checks if the information already exist. If the information is not found the request is procced and the response is saved both in Sesam and in our local database

    If a crash happens and Sesam gets two hours ahead of our backup and the same request is send again then Sesam will say that the information exist but it does not in our system. This is these kind of conflicts we want to avoid.

    We can take a meeting to explain in further details.

    0
    Comment actions Permalink

Please sign in to leave a comment.