Networker

Re: [Networker] How to make unique save set names for Oracle backups?

2007-05-08 09:43:31
Subject: Re: [Networker] How to make unique save set names for Oracle backups?
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 8 May 2007 09:44:22 -0400
Ronny Egner wrote:
Davina Treiber schrieb:
George Sinclair wrote:
Hi,

Is is possible to create unique save set names with Oracle backups using
NMO and RMAN?

Our save set names are always the name of the rman script itself. For
example, when we run our level 1
backups, mminfo reports something like this:

vol001 client 05/07/07 257 KB full RMAN:/oracle/rman/level1_test.rcv vol001 client 05/07/07 9473 KB full RMAN:/oracle/rman/level1_test.rcv vol001 client 05/07/07 2561 KB full RMAN:/oracle/rman/level1_test.rcv vol001 client 05/07/07 83 MB full RMAN:/oracle/rman/level1_test.rcv vol001 client 05/07/07 8705 KB full RMAN:/oracle/rman/level1_test.rcv vol001 client 05/07/07 257 KB full RMAN:/oracle/rman/level1_test.rcv
vol001    client    05/07/07 290 KB       9  index:client

How do we change it so the save set names are unique?

You need to use the format command within the RMAN script.
Our RMAN scripts has the format string as well. But the
save set names are named like the rman script anyway:

yellow-eyed:~ # mminfo -a -v -r 'ssid,name,volume' | more
 ssid      name                           volume
3524087915 ASR:\                          AXM340L1
3624751195 C:\                            AXM340L1
3339538558 D:\                            AXM340L1
3238875286 E:\                            AXM340L1
3960295478 SYSTEM DB:\                    AXM340L1
4111290418 SYSTEM STATE:\                 AXM340L1
3389870202 ASR:\                          AXM340L1
3188543653 C:\                            AXM340L1
3842854971 SYSTEM DB:\                    AXM340L1
4027404341 SYSTEM STATE:\                 AXM340L1
3423424629 ASR:\                          AXM340L1
3373092986 C:\                            AXM340L1
3708637272 SYSTEM DB:\                    AXM340L1
4178399281 SYSTEM STATE:\                 AXM340L1
51204144   /                              AXM340L1
135090222  /boot                          AXM340L1
1745674415 /u01/sicherung/scripte/rman_evn10g_arch.scr AXM340L1
722265146  /u01/sicherung/scripte/rman_evn10g_arch.scr AXM340L1
705487941  /u01/sicherung/scripte/rman_evn10g_arch.scr AXM340L1
[...]
2014109632 /u01/sicherung/scripte/rman_arch920_arch.scr AXM340L1
1930223568 /u01/sicherung/scripte/rman_arch920_arch.scr AXM340L1
1896669141 /u01/sicherung/scripte/rman_arch920_arch.scr AXM340L1
1528292205 /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
1310188841 /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
924313485  /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
538438250  /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
270003190  /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
169340148  /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
85454374   /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
4246204207 /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1
3927437369 /u01/sicherung/scripte/rman_arch920_full.scr AXM340L1


But why do you want to change the save set names? You dont restore
them yourself. RMAN requests them from the networker server in
case of restore/recovery.

Why use the format command if the save set names are still being named according to the script name?
What is the format command accomplishing in that case?

I guess I'm still confused about why some people are able to get the format command to custom name the save sets, but some of us cannot? Why is it that everyone else whose responded to this post can get
it to work, but we try, and it never does?

The reason I'd like to control the save set names is because while RMAN is used to do the recovery, it would be nice to have more meaningful save set names, especially given that they all list with a level full regardless of the backup level. Having more unique names just makes things more intuitive when I'm running mminfo to look at things, which I periodically do. For example, I might want to check the 'ssflags' and 'clflags' values for completed backups in the last week. If everything has the same name it just makes it harder to analyze it. Moreover, in performing various backup/recover tests in Oracle, I need to know what the previous backups were that we ran. For example, we might run a full and then several incrementals and then try to recover from one of the older incrementals. I run mminfo to see what we did. This might cover a period of several days. It makes it harder to delineate all the information if the save sets all have the save names, especially given that they all
indicate level full.

George

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