Forum

When you initiate the Rollback feature in Phire, objects that do not exist in the target at the time the baseline version is taken will be automatically deleted. The driver for the action Phire takes during a rollback (either copy or delete) depends on the state of the object in the target when the baseline backup is made.  If the object exists when the baseline is taken, then the action for the rollback is set to COPY. If the object does not exist when the baseline is taken, then the action for the rollback is set to DELETE.

You can view the action Phire will perform for each object when the rollback is initiated by looking at the baseline Version Set. From the CR, navigate to the “Objects” tab and click on the “View Version Set” icon below the CR Number. Click on the “Objects” link next to the Baseline backup from <TARGET>. For each object, the Action to be taken for the restore will be displayed.

One possible cause for the restore action to not be set to DELETE is if you perform multiple migrations to the same database. The rollback of the last migration will not result in the “new” objects to be deleted since those objects may not have existed when the first migration was done, however, they do exist when the last migration is performed. In this scenario, you can Restore the baseline backup taken prior to the first migration to delete the objects.