I'll likely be of little assistance on that front. I haven't looked at
networker a great deal. We're currently using RMAN's retention, as it's what
we're most familiar with.
One thing I will mention; backup retention can be deceptively simple. I want
to know I can trust it.
One key feature I'm not sure networker could compete with is RMAN's option of
redundancy rather than age. If our last few full backups have silently failed
for whatever reason, I'd rather not get rid of my last good backup of a data
file, simply because it's old.
On May 5, 2016, at 8:00 AM, Jeff Thomas <dbmangler@xxxxxxxxx> wrote:
Thanks for the replies. Which retention policy are you using, in
Networker, or in RMAN?
On Wed, May 4, 2016 at 12:36 PM, Adric Norris <landstander668@xxxxxxxxx
<mailto:landstander668@xxxxxxxxx>> wrote:
On Wed, May 4, 2016 at 11:28 AM, Ryan January <rjanuary@xxxxxxxxx
<mailto:rjanuary@xxxxxxxxx>> wrote:
As an aside, I'd note we've had a very difficult time with overrunning DD's
streams capacity after the last OS upgrade. Historically it's been a good
product, but recent issues have left a sour taste in my mouth. That's an
ongoing battle with EMC that has me longing for Oracle's urgency of Sev 3
support :/
To clarify slightly (Ryan's colleague here), he was referring to a Datadomain
OS upgrade... not something on the database server side.
--
"In the beginning the Universe was created. This has made a lot of people
very angry and been widely regarded as a bad move." -Douglas Adams
