Networker

Re: [Networker] RMAN backups levels and Networker Media database levels

2007-05-04 11:50:59
Subject: Re: [Networker] RMAN backups levels and Networker Media database levels
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 4 May 2007 11:49:11 -0400
Yes, but wouldn't NetWorker still report the same save set names from mminfo? In other words, wouldn't the save set names reported by mminfo still be the name
of the rman script itself? This is the case for us.

George

Faidherbe, Thierry wrote:
What I usually try to do, configuring a backup with RMAN,
is to change default Oracle Rman streams names (format field
in rman backup command).

I usually set to backup ....
 format "<hostname>_%d_<level>_<type>_%s.%p" ...

being :
<hostname>, the dbase server,
%d, the Oracle SID,
<level>, the oracle rman backup from oracle (eg Full, Lvl1,....)
<type>, df for datafile, cf for controlfile, ar for archive, sp for
spfile ....
%s.%p, increment number making the rman file unique.

I also sometime add _<backupdate> in format because if you  recreate the
db and open resetlog, you will get a new incarnation number of your DB
and increment will reset to 0 (causing duplicate rman file in indexes)

So, seeing DF+CF+SP, you can "group/retrieve" your rman backup cycles,
seeing AR, you know it is oracle archivelogs.
seeing level full/diff, you can better see dependency using name and
not saveset level.

Work like a charm.

HTH,

TH


Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
 *******    h      *******   1 Rue de l'aeronef/Luchtschipstraat
 ******    h        ******   1140 Bruxelles/Brussel/Brussels
***** hhhh pppp ***** ***** h h p p ***** 100/102 Blv de la Woluwe/Woluwedal
 *****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
 ******      p      ******   BELGIUM
******* p ******* ********* ********* Phone : +32 (0)2 / 729.85.42 Mobile : +32 (0)498/ 94.60.85 Fax : +32 (0)2 / 729.88.30 I N V E N T Email/MSN : thierry.faidherbe(at)hp.com
                             Internet  : http://www.hp.com/
Enterprise number 0402.220.594 - RPM/RPR Brussels
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of George Sinclair
Sent: vendredi 4 mai 2007 16:40
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] RMAN backups levels and Networker Media
database levels

We always see level fulls reported regardless of the level we run. However, the sizes are what we would expect
for an incremental. The other thing we notice, though, is that NetWorker

only reports the rman script name
as the save set name, so all the save sets have the same name. We're running Oracle 10g with NW 7.2.2 and
NMO 4.2. Behavior could be different in later NW releases?

We've tested recovering these incrementals by first restoring the previous full and then the desired incremental. We run one full (level 0) per week and a level 1 cumulative incremental five days per week. One day is a skip. We use a one month policy on the Oracle side and a 5 week browse policy on the NetWorker side.
George

Allan, Kevin wrote:
We are currently testing the use of incremental Oracle RMAN backups
but
we have noticed that the level recorded by Networker is always full.

This causes us concern as the logic inside Networker for protecting
incremental backups to ensure your browse and retention polices are
meant will not work.
Test Scenario:
In our test configuration we setup one full followed by six
incremental
backups per week, with a 14 day browse/retention. we ran the first
week
of backups okay and the intentionally broke the next full and ran the
other six incremental without a problem.
We therefore had a scenario where we had 12 incremental backups
reliant
on a single full (RMAN view), but in Networker there were no recorded
dependences as all savesets were marked as FULL. Once ran the next
full
week of the cycle we therefore lost the first full, as it had expired
but this also meant all twelve incremental backups were left useless.
The end result being we only had a recovery window of one week.

Day of Week                     S M T W T F S   S M T W T F S    S M T W
T F S

Networker Level         F F F F F F F   X F F F F F F    F F F F
F F F
X=Failure

RMAN Level                      0 1 1 1 1 1 1   X 1 1 1 1 1 1    0 1 1 1
1 1 1 X=Failure
We are running Networker 7.2.2, Oracle 10.2.0 and NMO 4.2 on a Solaris
9
server.

I would appreciate your comments/views.

We have looked at using the NSR_RETENTION_DISABLED=TRUE, this would
move
the media management control to the RMAN Catalog and may have it's own
headache.

Regards
Kevin

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145       | Voice: (301) 713-3284 x210
1315 East West Highway        | Fax:   (301) 713-3301
Silver Spring, MD 20910-3282  | Web Site:  http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER