|Subject||Re: [ib-support] gbak restore corruption|
> I think the order is something like:<etc>
Thanks heaps for that.
It looks to me like I should be able to setup a backup process so that
it runs the first 5 steps. Then it can just store the extra metadata
On restore I run the same 5 steps and then apply the stored metadata
in the order you suggested.
I can locate the backup database on a compressed volume to reduce
space. And if I ever need to move to a different platform there is a
good chance that gbak will not have problems with the backup database
(since it does not have all the confusing constraints installed) and
so I can move the backup database using gbak and then restore on the
Seems good to me, although there is still one outstanding question...
One of the reasons for using gbak is to reset version numbers on the
metadata. Will the application of alter table commands to add
computed fields, constraints etc impact this? That is; do I get a
version number increment for each and every computed field and
constaint added - perhaps I can minimise this by attempting to add all
such changes in a single alter table command.