It's unclear from the documentation at what point a copycluster or backup is consistent.
For a backup, the documentation states "This type of backup provides a consistent image of the database at the time the backup occurred.", but if a backup takes 1.5 hours, is that the start or end of the backup or copycluster ?
In some databases (Oracle) it's at the end, and others (Informix) it's at the start.
Does vbr put a hold on file deletions while it's running in order that all files that are present at the start are still present at the end and are not missed while copycluster'ing or backing up ?
Question
Copycluster and backup consistency
+2
+2The backup process snapshots the catalog at the start of the backup transaction, so that is the point of consistency.
+2Thanks Bryan, and for the last question, does vbr put a hold on file deletions while it's running in order that all files that are present at the start are still present at the end and are not missed while copycluster'ing or backing up ?
+2There is transaction isolation during vbr: Internal task "Database Snapshot" holds a catalog lock while backup runs, which would block deletes during backup. Deletes and purges would not commit until after backup in this case.
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
