Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    Cold backup takes too long; old archive files not removed

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    We are a Hosted customer and had a new oracle cold backup process set up two weeks ago. The downtime (~9.5 hours) with the new method is much too long for us. Would a stop-and-copy be just as good and much faster? That was our cold backup method with our previous ILS, and it took about 15 minutes.

    Also, aleph isnt being automatically restarted after the backup -- I had to do so manually last Sunday and this morning. And we need to configure it to remove no longer needed backup files. This morning /exlibris had gotten to 92% (45G avail), with about 16G more expected from the cold backup, so I removed those older than the last cold backup. We now have two cold backups worth, but we're only at 86%, so I'll leave well enough alone.

    Resolution:
    This has been resolved by:

    1) Running a "Hot" backup on Sunday thus allowing the db server to be available throughout the day.
    2) Limiting the number of saved full db backups to 1 (saves space on disk)
    3) Running a data pump export on a weekly basis (on Saturday) giving us another recovery alternative (if needed).

    • Article last edited: 10/8/2013