Quoting VirusPil: Quote:
But then we would (perhaps) lose the possibility of restoring a specific (older) point. For database applications you want transaction backups. Once a quarter, for example, the complete database file is backed up and all of the transaction files deleted. Once a month would be a level 1 backup, where all of the transaction files since the last level 0 are backed but not deleted. Each week, a level 2 backup is done of all the transaction files from the last level 1. Then, all of the other days during the week a level 3 backup would be done of all the transaction files since the last level 2. You can get back to any particular day by restoring the most recent level 0, then level 1, then level 2 and lastly the level 3 of the day of the week you want to go back to. Since you are dealing with transaction files, you get all changes to the database. This requires that DVDP create transaction files each time it is exited and has the ability to restore transaction files. If DVDP only created single transaction files each time DVDP is run, in a quarter there could be a potential 90 files to restore. If DVDP appended to an existing transaction file, then the backups would delete the file it just backup up, or move it to a different location so that DVDP will create a new transaction file.. I think you get the picture on how it would work. There are many variables to work out. |