> > if you can do it, you should take that database off line, rename it,
> > back it up with garbage collection disabled, restore it, and,
> > assuming all has gone well, rename it back and put it on line.
>
> Just curious, why the rename steps? They seem superfluous to me.
>
> -Kevin

to ensure noone is connecting/connected to database while restore is being
done.

backup/restore when you want to test restore
1. backup
2. restore to alternate filename
3. all OK - delete restore, archive backup

backup/restore when you want to use the rebuilt restore
1. shutdown database (only OK if users don't all connect via SYSDBA user)
2. stop server - rename real file to alternate name - this absolutelt stops
further transacation starting on the db which will not be visible to the
backup transaction.
3. start server
4. backup alternate name file to alternate name .fbk file
5. restore to alternate2 .fdb file
6. all ok, rename alternate2 file to real filename
people start connecting

Alan