Re: backup strategy

Well, as a general rule I backup/secure my databases using not only a tape system but also Oracle's EXP (export) utility. The export utility is relatively common, in the shops that I have been in.

The ability to import (IMP) a specific schema is handy and quicker to use vs restoring a tablespace where the users objects are stored. Now keep in mind, a seperate tablespace (tbs) would be better than placing objects in a tbs with other objects not belonging to that user (for obvious reasons). Recovery of that tbs would require taking it offline which could affect more users than just the schema your concerned about.

So the long and the short ... if this is an on the fly process .. I would export before/after your process. It depends on your requirements. Sounds like you maybe deleting or truncating or dropping objects .. so if you need to go back to a process time (mins, hours, days) .. just create your exports w/a time-date stamp.

-Mike

Audun Jensen wrote in message ...
>Hi,
>we have an application currently running on MS SQL Server, and now we want
>to support Oracle as well.
>This application create SQL server databases "on the fly", on oracle it
>will create schemas "on the fly". These schemas will consist of a
>customer's project. An instance can contain "thousands" of schemas.
>
>I'm wondering what approach to take regarding backup/recovery. I read that
>physical backups contains physical units like datafiles, tablespaces etc.
>There is also a logical type that uses exp/imp on user leve.
>Which one is most common? Why?
>
>Should the schemas created on the fly put it's objects on a separate
>tablespace? In that case the physical backup strategy could be used, and a
>customer's project could easily recovered. If so, the instance will contain
>thousands of tablespaces (among with thousands of users with approx. 50
>tables each). How will Oracle handle this?
>
>Anyone who could give some advices?
>
>AJ
Received on Fri Feb 23 2001 - 16:17:36 CST