In order to find the point at which you want to advance your restored backup, use the program agtool recover to show you all the recovery points. When you specify -newuuid, the restored backup has a new uuid and the original uuid is now in a file, parent-uuid, since the parent uuid will be needed by the agtool recover program to find the old commits to add to this database.
#POINT INTIME RECOVERY ARCHIVE#
Since this is a common operation when doing point-in-time recovery, the agtool archive option -recover will set both -newuuid and -nocommit. % agtool archive -newuuid restore dbname db.backup The agtool agaph-backup program can change the uuid for a database it is restoring. If your purpose in doing point-in-time recovery is to bring the database to a certain state and then make use in a way where you'll be making new commits, then you should change the uuid of the database so that the transaction logs for this recovered database do not get confused with the transaction logs for the original database. That program, along with most other command-line AllegroGraph programs, have been folded into the single agtool program.) New UUID (In earlier releases there was an agraph-recover program. See the agtool general command utility document for information on the agtool program. It is as if you did a backup after every commit. You can use the recover utility of the agtool program to advance the state of the restored database forward to any later commit that was done to the original (and perhaps still running) database. You may want to see what it looked like a few hours or a few days later. If you restore the database backup you can view the state of the database as it was when the backup was done. Meanwhile the original database continues to be used and further commits are done and written to the transaction log. You can make a backup of a database (even while it's running) and you then have a copy of the database at a certain point in time. The content of Allegrograph database is the result of a sequence of commits, each commit being recorded in a transaction log as well as in other database files.
0 kommentar(er)
