Message-Id: <10700.123598@fatcity.com> From: Satar Naghshineh Date: Mon, 4 Dec 2000 15:32:15 -0800 Subject: RE: NetApp (was utl_file_dir) 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@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 RE: NetApp (was utl_file_dir)

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.