Re: Backing up a Development instance

On Mon, 23 Feb 1998 17:49:21 -0600, "John P. Higgins" <jh33378nospam_at_deere.com> wrote: Hi,

backing up only the control files is worthless since they only contain information about the datafiles the db is made up and so on. Issue a 'ALTER DATABASE BACKUP CONTROLFILE TO TRACE; ' to see what inside there. If you don't want to backup the whole datafiles of the dev env, keep in mind that a lot of work of your dev crew is in this env and think of exporting the dev db and backing up the export dump. Thus all stored procs etc. will be backed up.

>Remember that the developers do their production on the development
>databases! It's true that the business impact is less (smaller
>audience), so a longer interval between backups is justified. But I
>think you should also use archiving to protect their work between
>backups.
>
>Neal Nachtigall wrote:
>>
>> I know about the various ways for backing up an Oracle instance
>> (hot,cold,etc.), but was wondering about what should be backed up.
>>
>> For production instances it is pretty straight forward, you back up
>> everything: datafiles,control files, archive logs, yada yada yada, but my
>> question is as far as a development instance in which you are are mostly
>> interested in maintaining the data dictionary wouldn't it be good enough to
>> just backup the control files (and probably datafiles periodically so don't
>> have to reload test data). Then master instances probably want to backup
>> more again, but in both cases probably don't need to do archive logging or
>> hot backups other then for testing recovery, do you??
>>
>> Are there any guidelines regarding this?
>>
>> Thanks,
>> --
>> No wonder nobody comes here--it's too crowded. -Yogi Berra
>>
>> Neal L. Nachtigall
>> Neal.Nachtigall_at_lodgenet.com

--

Regards

Matthias Gresz    :-)

GreMa_at_T-online.de