Re: Hot backup question
- From: Subodh Deshpande <deshpande.subodh@xxxxxxxxx>
- To: daniel.fink@xxxxxxxxxxxxxx
- Date: Sat, 25 Sep 2010 15:54:51 +0530
And Daniel, how to overcome this, its again related to sizing it
seems..thanks..subodh
On 25 September 2010 05:26, Daniel W. Fink <daniel.fink@xxxxxxxxxxxxxx>wrote:
> Data is still being written to the datafiles while the tablespace is in
> hotbackup mode. The main change is that the redo written for any table/index
> in a tablespace in hot backup mode is not just the redo vector, but the
> whole block. This prevents split blocks causing unrecoverability. The impact
> is primarily seen in increased i/o (both in redo and the backup process)
> competing for system resources.
>
>
>
> On 09/24/2010 04:49 PM, Blanchard, William G wrote:
>
> Having spent all of my time using RMAN for backup/recovery, I find myself
> at a disadvantage when it comes to hot/cold backups. My questions is, what
> is the impact on users during a hot backup? My guess is that either the DB
> Writer doesn’t write to the tablespace while it’s in backup mode but resumes
> writing when the tablespace is taken out of hot backup mode. Can anyone
> clear up my confusion?
>
>
>
>
>
> Thank you,
>
>
>
> WGB
> _____________
>
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.
> _____________
>
>
--
==============================
DO NOT FORGET TO SMILE TODAY
==============================
Other related posts:
