Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › Procedure for Restoring From a BFC Mnesia Backup

Procedure for Restoring From a BFC Mnesia Backup

Here's the procedure for restoring from a mnesia backup (the backup from /opt/bfc/Mnesia.bfc/backup/). This should not be necessary unless you're unable to recover from the replica database.

1. Verify that new BFC server has the same backbone and external Ips that the original had and setup the /replica in the same location as well.
2. Install the BFC with the same BFC version that was running before, but don't do any configuration post install (you can, but we'll overwrite it when db_restore is run)
3. Set up the download directory for the bfc in the same location as the old install, and containing the same applogic versions that existed on the previous install
4. Make sure you have the 3.5 version of the db_restore script in /opt/bfc/bin. If you're running 3.1, attached is the 3.5 version (there's actually two files, both of which should be placed in /opt/bfc/bin – "db_restore" is the shell script that invokes "erestore")
5. Switch to the bfcadmin user: "su – bfcadmin"
6. Run the db_restore script and give it the full path to the backup from the previous install, e.g.: /opt/bfc/bin/db_restore /<path>/backup_YYYY.M.D_H.M.S.MS.bz2. The main reason to have the 3.5 version of db_restore is that the 3.1 version just automatically grabs the latest backup and doesn't let you specify the one you want, so again you want that 3.5 version.

One important caveat: This backup is a snapshot from a point in time (that is now a couple of months ago for this BFC). In theory it shouldn't be that far off as they couldn't have done anything to their grids while the BFC was down, but just a heads up. Again, the replica is really the thing we want to do restores/recoveries from. The backups in /opt/bfc/Mnesia.bfc/backup/ are really there for situations like this one where we didn't have a replica.

Scripts:

db_restore

erestore