RE: Exadata backups
- From: Gurmeet Goindi <gurmeet.goindi@xxxxxxxxxx>
- To: niall.litchfield@xxxxxxxxx
- Date: Wed, 6 Nov 2013 08:56:51 -0800 (PST)
Good point Niall - but once you move the copy to a different media you are
incurring additional storage cost.
The technical deep dive regarding validation will be available closer to
release date, that being said, the appliance does Oracle block level validation
when it receives the backup and also when it replicates the backup to a
different appliance or sends it to tape. In addition the appliance
periodically goes and validates all the backups on disk, again at an Oracle
block level and not on a mere storage checksum. Users can also query when was
the last time a backup was validated.
From: Niall Litchfield [mailto:niall.litchfield@xxxxxxxxx]
Sent: Wednesday, November 06, 2013 12:54 AM
To: Gurmeet Goindi
Cc: D'Hooge Freek; Guillermo Alan Bort; oracle-l@xxxxxxxxxxxxx; Andy Colvin;
mboligan@xxxxxxxxx; hansrajsao@xxxxxxxxx
Subject: RE: Exadata backups
In a somewhat sane backup strategy using incrementally updated copies, you'd
then transfer the copy to another medium. Recovery to a point in time before
your last copy would then be a multistep affair, but in most use cases you'd
want to think through the business implications of not recovering to a current
point in any case so I don't really see that as a huge drawback.
Is there a link to what the backup validation does (especially as you say
elsewhere you never send the same block twice so you better be real sure every
block sent makes it correctly so you don't corrupt your backup over time).
On Oct 30, 2013 10:06 PM, "Gurmeet Goindi" <HYPERLINK
"mailto:gurmeet.goindi@xxxxxxxxxx"gurmeet.goindi@xxxxxxxxxx> wrote:
I should have mentioned this in my previous email, thanks Job for pointing it
out.
Another key difference between DBLRA and incrementally updated backup strategy
is that with DBLRA you can restore to any point in time. For each incremental
DBLRA receives it creates a virtual full, so the user has the choice to restore
to any of these virtual full backups. Whereas in an incrementally updated
strategy the updated copy cannot be undone, hence it's not possible for the
user to restore to a point prior to the one represented by the updated copy.
-----Original Message-----
From: Gurmeet Goindi
Sent: Wednesday, October 30, 2013 9:36 AM
To: D'Hooge Freek
Cc: HYPERLINK "mailto:mboligan@xxxxxxxxx"mboligan@xxxxxxxxx; Andy Colvin;
Guillermo Alan Bort; HYPERLINK
"mailto:hansrajsao@xxxxxxxxx"hansrajsao@xxxxxxxxx; HYPERLINK
"mailto:oracle-l@xxxxxxxxxxxxx"oracle-l@xxxxxxxxxxxxx
Subject: RE: Exadata backups
Its different in the sense that the DB server doesn't has to get involved in
applying the incrementals. The Appliance does it for you, say you take a rman
level 1 backup, and then when you do an "rman list" you'll see a full backup
not an incremental.
In addition it also validates the backup, so you don't have to run "rman
validate" on the db server anymore.
Gurmeet Goindi | Principal Product Manager Oracle High Availability | Maximum
Availability Architecture
400 Oracle Parkway | Redwood Shores, CA 94065, USA | HYPERLINK
"tel:650.506.1277"650.506.1277 http://www.oracle.com/goto/availability
-----Original Message-----
From: D'Hooge Freek [mailto:HYPERLINK
"mailto:Freek.DHooge@xxxxxxxxx"Freek.DHooge@xxxxxxxxx]
Sent: Wednesday, October 30, 2013 8:42 AM
To: Gurmeet Goindi
Cc: HYPERLINK "mailto:mboligan@xxxxxxxxx"mboligan@xxxxxxxxx; Andy Colvin;
Guillermo Alan Bort; HYPERLINK
"mailto:hansrajsao@xxxxxxxxx"hansrajsao@xxxxxxxxx; HYPERLINK
"mailto:oracle-l@xxxxxxxxxxxxx"oracle-l@xxxxxxxxxxxxx
Subject: Re: Exadata backups
Is this different from the incrementally updating backups feature of rman or
just a more automated version of it?
--
Freek D'Hooge
Uptime
Oracle Database Administrator
email: HYPERLINK "mailto:freek.dhooge@xxxxxxxxx"freek.dhooge@xxxxxxxxx
tel HYPERLINK "tel:%2B32%2803%29%20451%2023%2082"+32(03) 451 23 82
http://www.uptime.be
disclaimer: HYPERLINK "http://www.uptime.be/disclaimer.html";
\nwww.uptime.be/disclaimer.html
On di, 2013-10-29 at 14:05 -0700, Gurmeet Goindi wrote:
> This OOW we announced the Oracle Database Backup Logging Recovery
> Appliance. Details about the appliance can be found HYPERLINK
> "http://www.oracle.com/us/corporate/features/database-backup-logging-r
> ecovery-appliance/index.html"here
>
>
> Among other features, the appliance ingests RMAN incremental backups to
> generate a full backup for that point in time. Other than the first full
> backup, with this appliance the user will never have to take a full backup
> again but will enjoy the benefits of a full backup. In this setting RMAN will
> never read or send a duplicate block to the appliance hence the impact to the
> DB server will be minimum, highly proportional to the amount of change bits.
>
>
>
>
>
>
>
> Gurmeet Goindi | Principal Product Manager
>
> Oracle High Availability | Maximum Availability Architecture
>
> 400 Oracle Parkway | Redwood Shores, CA 94065, USA | HYPERLINK
> "tel:650.506.1277"650.506.1277
>
> http://www.oracle.com/goto/availability
>
>
>
>
>
> -----Original Message-----
> From: mike boligan [mailto:HYPERLINK
> "mailto:mboligan@xxxxxxxxx"mboligan@xxxxxxxxx]
> Sent: Tuesday, October 29, 2013 12:33 PM
> To: Andy Colvin
> Cc: Guillermo Alan Bort; HYPERLINK
> "mailto:hansrajsao@xxxxxxxxx"hansrajsao@xxxxxxxxx; HYPERLINK
> "mailto:oracle-l@xxxxxxxxxxxxx"oracle-l@xxxxxxxxxxxxx
> Subject: Re: Exadata backups
>
>
>
> Andy/Ryaj,
>
> Thanks for clarifying that for me, very helpful.
>
>
>
> Mike
>
>
>
>
>
>
>
>
>
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts: