Re:RE: NetApp (was utl_file

From: <dgoulet_at_vicr.com>
Date: Tue, 5 Dec 2000 09:31:41 -0500
Message-Id: <10701.123655@fatcity.com>

Satar,

To some degree that is Oracle's suggestion as well. BTW, you can add the online redo logs to that list. The rational is that temp should not have any permanent objects therefore easier to offline drop & rebuild without having to take the DB down. Likewise with RBS, although you do require some down time, but less than a restore. Indexes are questionable especially in a DSS environment, one needs to weigh the time required to restore the files from tape & recover vs. the time it takes to rebuild the indexes. Lets face facts, if it takes 8 hours to recover a lost index tablespace that is faster than an 18 hour rebuild process.

Dick Goulet

____________________Reply Separator____________________

Subject: RE: NetApp (was utl_file_dir) Author: Satar Naghshineh <Satar.Naghshineh_at_irvine.mellesgriot.com> Date: 12/4/2000 3:45 PM

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.
>
>
>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="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=1 FACE="Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=1 FACE="Arial">From:&nbsp;&nbsp;</FONT></B> <FONT SIZE=1

FACE="Arial">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

<BR><FONT SIZE=2 FACE="Arial">the tablespaces be in backup mode, cold backups
require the database be</FONT>
<BR><FONT SIZE=2 FACE="Arial">down.&nbsp; Why would NetApp snapshots make this

any different??

The backup strategy I'm implementing follows <A HREF="http://www.netapp.com/tech_library/3049.html" TARGET="_blank">http://www.netapp.com/tech_library/3049.html</A>, 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 Received on Tue Dec 05 2000 - 08:31:41 CST

Re:RE: NetApp (was utl_file_dir)