6 thoughts on “Smokis Notesblog: Performing on-line backup using the C API”

  1. Hi Mikkel!

    I only want to show, what the tools delivered by the C API can do, for the user. My interest was to get some backup tool for my test-environment, where TSM or other tools are not available…

    dbbackup is also a nice tool to make copies of active databases, for sure…

    So, I think your ideas goes far behind this 🙂 And thats perfect, thats why I’m blogging!

    Maybe you can give me a little description of the admin tool you have in mind? Maybe I (or we?) can build up something is this direction?!

    Cheers!
    Chris

  2. We should probably keep with proven tools such as Tivoli and Veritas for production environments but utilities like yours to make copies of live databases for testing or simply to solve a particular problem are always nice. I have a small utility that only changes replica id etc. but I have used it countless number of times.

  3. Yes! I’ve a replica ID tool, too 🙂

    I’m now had started, to create some small tool (EXE)!

    It should in the first step be able to make a copy of all databases and templates on the server or for a specified database.

    It should work like follows:

    To make a Full Backup of Data:
    load backup -F

    To make a Full Backup of a database:
    load backup -F -d test1.nsf

    (-F for Fullbackup, because more options maybe follows…)

    The database(s) will be copied to a directory, defined in the notes.ini (via BACKUP_DIRECTORY)

    You could also use it from the command-line!

    What do you think about this?

    The next steps are for the recovery of a fullbackup from the backup directory to the server directory, with following possibilities:

    * Replace exiting file
    * Place it there as “test1.bak”, if you want to recover only some documents

    This all should be quite simple!

    Do you have other or further ideas?

  4. It sounds nice. One thing which would be nice would be if the tool would allow you to change the replica id of the databases while/after “restoring”. I find this to be a big problem with existing solutions as you many times end up with two databases with the same replica id on the server which isn’t a good thing.

    I’m okay with the notes.ini path as long as there is a way to set the path from the command line as well.

  5. Ok!
    You want two additional options:
    * restore with new ID (that should be easy!)
    * define a backup/restore directory by commandline-parameter (should be easy, too)

    I’ll try to keep this in mind, please tell, if I’ll forget it 🙂

Comments are closed.