RE: NetApp (was utl_file

From: Satar Naghshineh <Satar.Naghshineh_at_irvine.mellesgriot.com>
Date: Mon, 4 Dec 2000 15:32:15 -0800
Message-Id: <10700.123598@fatcity.com>

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------_=_NextPart_001_01C05E4A.704753F0
Content-Type: text/plain

NetApp is suggesting that the DBA doesn't have to backup the RBS, TEMP and INDEX tablespace. The "logic" behind that assumption is that one could easily re-create those tablespaces rather than backing them up everytime. The Snapshot utility is generally pushed/prostituted in business environments (like in VLDB) in which backups must be fast and take up less space.

Regards,
Satar

PS My suggestions/comments are the result of the voices of my head only, and do not represent NetApp Corp.

> -----Original Message-----
> From: Suzy Vordos [SMTP:lvordos_at_datsit.com]
> Sent: Monday, December 04, 2000 10:11 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: NetApp (was utl_file_dir)
>
>
> Still working on the backup strategy and haven't tried a snapshot
> restore yet. But, for the database files, you do need to put the
> tablespaces in backup mode before taking a snapshot. I mention this
> because of the impression I got from talking to different people from
> NetApp.
>
> I was told that because snapshots are a read-only image of blocks on the
> volume, you could simply schedule snapshots and restore from them at any
> time. No mention of putting tablespaces in backup mode, or the impacts
> of snaprestore on the database.
>
> Okay, the snapshot feature is pretty slick, but in my mind that doesn't
> change basic Oracle backup and recovery concepts. Hot backups require
> the tablespaces be in backup mode, cold backups require the database be
> down. Why would NetApp snapshots make this any different??
>
> The backup strategy I'm implementing follows
> http://www.netapp.com/tech_library/3049.html, which explains the
> tablespaces are put in backup mode, snapshot taken, tablespaces out of
> backup mode. Although it does puzzle me why they suggest certain
> tablespaces can be excluded, seems that would make recovery a little
> more challenging.
>
> I'd be interested in hearing about the backup strategies other people
> are using for database on a NetApp filer.
>
>
>

------_=_NextPart_001_01C05E4A.704753F0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =

charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2650.12">

<TITLE>RE: NetApp (was utl_file_dir)</TITLE>
</HEAD>
<BODY>

NetApp is suggesting = that the DBA doesn't have to backup the RBS, TEMP and INDEX tablespace. = The "logic" behind that assumption is that one could easily = re-create those tablespaces rather than backing them up everytime. The = Snapshot utility is generally pushed/prostituted in business = environments (like in VLDB) in which backups must be fast and take up = less space.

Regards, Satar

PS My = suggestions/comments are the result of the voices of my head only, and = do not represent NetApp Corp.

</P>
<UL>
<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From:&nbsp;&nbsp;</FONT></B> <FONT =

SIZE=3D1 FACE=3D"Arial">Suzy Vordos [SMTP:lvordos_at_datsit.com] Sent:   Monday, December 04, 2000 10:11 PM To:     Multiple recipients of list ORACLE-L Subject:       =

</B> <FONT SIZE=3D1 FACE=3D"Arial">Re: NetApp (was utl_file_dir)</FONT>
</P>
<BR>

Still working on the backup strategy = and haven't tried a snapshot
 restore yet.  But, for the = database files, you do need to put the tablespaces in backup mode before = taking a snapshot.   I mention this because of the impression I got from = talking to different people from
 NetApp.

I was told that because snapshots are = a read-only image of blocks on the volume, you could simply schedule = snapshots and restore from them at any time.  No mention of putting = tablespaces in backup mode, or the impacts of snaprestore on the = database.

Okay, the snapshot feature is pretty = slick, but in my mind that doesn't change basic Oracle backup and = recovery concepts.  Hot backups require the tablespaces be in backup mode, = cold backups require the database be down.  Why would NetApp = snapshots make this any different??

The backup strategy I'm implementing = follows
 <A = HREF=3D"http://www.netapp.com/tech_library/3049.html" = TARGET=3D"_blank">http://www.netapp.com/tech_library/3049.html</A></FONT= >, which explains the tablespaces are put in backup mode, = snapshot taken, tablespaces out of backup mode.  Although it does = puzzle me why they suggest certain tablespaces can be excluded, seems = that would make recovery a little more challenging.

I'd be interested in hearing about the = backup strategies other people
 are using for database on a NetApp = Received on Mon Dec 04 2000 - 17:32:15 CST