How would this be any different than reading a file system
when write activity is taking place?  It doesn't matter
if it's the OS or Oracle managing the disk, block can and
will be split during a hot backup.

I think your sysadmins need to reconsider.

And if I'm all wet on this, someone will be sure to tell me. :)

Jared



On Friday 15 June 2001 12:37, Jenkins, Michael wrote:
> We have parallel server running on on a Sun Cluster 2.2 and we are looking
> for the easiest way to perform hot backups.  Now, I know that you have to
> use the "dd" command and skip the header at the beginning.  Everything I
> read on metalink indicates that you can use basically the same paradigm as
> a hot backup on cooked file systems.  But, the sysadmins here tell me that
> the raw device can't be backed up if there is any write activity on the
> data file that is currently being backed up.  Now we all know that contrary
> to popular belief there is write activity on a data file even when the
> tablespace is in backup mode.  Is "rman" or some other block-level backup
> utility the only way to get a reliable hot backup on raw devices?  Does
> anybody have any experience with hot backups that are made while the
> database still has active users logged in?
>
> I look forward to everyone's thought on this.
>
> Thanks.
>
> Michael L. Jenkins
> Oracle Certified DBA
> Nextel Communications
> Norcross, GA
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jared Still
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to