Re: Cold backup versus hot backup.
- From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
- To: jack@xxxxxxxxxxxx
- Date: Tue, 14 Apr 2009 01:38:57 -0300
Well, actually I didn't write much of what I think as I wanted to see
different points of view.
Currently cold backups are failing due to lack of attention, and lack
of resources. Generally databases are in noarchivelog mode, which has
a few performance and space advantages, and the most critical dbs are
on oracle managed backups. We are talking about several thousand
databases on different server architectures, operating systems and
administration teams, so basically we have a huge database full of
information on backup architectures on each DC. My idea is to bring
them all to a stanrdard, and as far as i can see, the best standard
for this particular situation would be:
Full Hot Backup with RMAN (obviously dbs in archivelog mode)
many archivelog backups a day (to prevent archive FS from filling up
and freezing the DB).
automatic space monitoring of archivelog FS and when it reaches a
certain threshold launch an automated archlog backup.
define retention policies based on the DB role (prod, devel, test,
validation, etc).
Make exception policies where needed.
use a single backup subsystem (TSM/TDPO???)
have a single set of scripts, common to every server so any dba can
check and manage backups.
have a centralized RMAN catalog and generate backup status reports and
analyze backup growth trends.
avoid cold backups, as the require much more attention and it makes
centralization a lot harder.
thanks everyone for your replies, this is a really interesting topic.
Alan Bort
Oracle Certified Professional
On Mon, Apr 13, 2009 at 10:37 PM, Jack van Zanen <jack@xxxxxxxxxxxx> wrote:
> Hi
>
> The question was not about archivelog or not but merely hot or cold backups.
> The assumption was made by another poster that cold backup automatically
> implied noarchivelog, in which case your plusses are valid points, however
> this was not the original question.
>
> However with all things being equal and just the backup temperature
> difference I stand by my comments.
>
> Test and development are completely different beasts altogether as some may
> actually get away with just a weekly/daily schema export without data.
>
> This would make for entertaining discussion at future meets as I'm sure
> there will be several ideas on this :-)
>
>
>
> Jack
>
> 2009/4/14 Nuno Souto <dbvision@xxxxxxxxxxxx>
>>
>> Jack van Zanen wrote,on my timestamp of 14/04/2009 9:33 AM:
>>>
>>> What makes the implementation of hot backups so much more complex?
>>> RMAN>backup database;
>>> RMAN>Restore database;
>>> RMAN>Recover database;
>>> looks simple enough to me
>>>
>>
>>
>> plus:
>>
>> - manage the archive log file system so that even on the highest load
>> of an errant program it doesn't fill up and freeze the db.
>> - find enough space somewhere to keep the compressed archived logs
>> until the next backup and make sure it doesn't blow up under
>> the same conditions.
>> - make sure the archiver works fine and doesn't let the db freeze
>> while waiting for it.
>>
>> and I can think of a few details more, mostly relevant to development
>> and test dbs.
>> What do you reckon of this as a subject to talk about on a
>> future meetup?
>>
>> --
>> Cheers
>> Nuno Souto
>> in sunny Sydney, Australia
>> dbvision@xxxxxxxxxxxx
>> --
>> //www.freelists.org/webpage/oracle-l
>>
>>
>
>
>
> --
> Jack van Zanen
>
> -------------------------
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient. If you are not the intended recipient,
> please be aware that any disclosure, copying, distribution or use of this
> e-mail or any attachment is prohibited. If you have received this e-mail in
> error, please contact the sender and delete all copies.
> Thank you for your cooperation
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
