Hi J�rg, > What would be the best practice to make a snapshot of a > database instance, so that it can be restored to exactly > the same state it had when the snapshot was taken?
Either a complete backup for migration or a complete backup and relevant log information (log devspace or log backups). If a complete backup for migration is used only, you have to reinstall the database (and thereby throwing the log on the logdevspace away) and restore that backup. After the restart, the database will contain exactly the state written to the backup. With a complete backup (recovery/migration) and the relevant log information (log devspace or log backup), you can restore to any point in time after the complete backup. Which one of those is better, depends on your situation. > When I made a backup and restored it later on, new rows that > had been added > after the backup was made were still there. I would like this > new data to be > discarded instead. By just restoring the complete backup the still available log information from the logdevspace was used for the restart, so all committed transaction after the backup were repeated with the help of the log information. This is what you would also normally expect, if restoring a database with an non damaged log devspace. > Maybe it is necessary to clean the database before > restoring the backup? What would be the easiest way to do that? If you want only the state of the backup, reinstall the database using that backup (DBMGUI->Install, use the same database name and select restore instead of install, when asked for, restore the backup as normal). Best regards, Tilo Heinrich SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
