Re: [Veritas-bu] RMAN crosscheck
On Wed, May 19, 2010 at 1:16 PM, David McMullin david.mcmul...@cbc-companies.com wrote: NOTE THIS PART! but this list is incomplete if an image spans several media. I haven't experienced that myself. If that were true, RMAN would be unable to restore. Having used RMAN/NetBackup to do many restores, that statement seems incorrect to me. One thing that I have seen is that if the tape has been vaulted, the media ID changes and RMAN no longer knows the correct media to ask for. When that happen, I have to supply a date range to our Backup Admin, and he requests the right tapes to restore to the time period. As re-cataloging NetBackup tapes back into the RMAN repository is nearly impossible, I never expire anything from RMAN. That way when an old tape is put back into NBU, RMAN still has the correct names to request. I guess it is possible to re-catalog NBU tapes back into RMAN, it just isn't documented by Oracle. Here's an undocumented CATALOG command you may find interesting: http://erpondb.blogspot.com/2008/09/catalog-rman-backuppieces.html Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN crosscheck
On Mon, May 17, 2010 at 9:38 AM, Lightner, Jeff jlight...@water.com wrote: That’s unfortunate. It seems that there ought to be a way to have RMAN rebuild its catalog from NBU much the same the way that NBU can recover images into its catalog from NBU expired but not yet overwritten tapes. It apparently can be done, though it requires some manual intervention: http://erpondb.blogspot.com/2008/09/catalog-rman-backuppieces.html Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN crosscheck
On Tue, May 25, 2010 at 4:54 PM, Dean dean.de...@gmail.com wrote: Are you sure RMAN actually knows about the tape an image is on? If it does, that is just silly. It should just ask for a backupid, then NBU will give it the correct tape, regardless of whether it's a duped or vault copy or whatever. I've always been sure that that's the way it worked (Although, I'm not a DBA and don't know that much about RMAN). I think you're right, it just keeps the Media ID. It's been a few months since I have looked closely at it. Regarding vaulted tapes: RMAN will not know that a tape has been vaulted, so it will have the wrong media ID for requesting the tape. If the tapes are restored into the NBU catalog, RMAN will then ask for the correct backup pieces by name. This not an issue with RMAN, as the API has that capability, at least according to the docs. It just has not been implemented by Veritas. This would bear further investigation, as that situation may have changed since I last looked into it. Does RMAN also track disk STUs? I know in our environment, we write all our Oracle archive log backups to a DSSU, then they get moved out to tape and deleted from the DSSU within a day or so. We restore regularly (to development), and it always works fine, regardless of whether the archive log backups are still on disk or have been moved to tape. Does that mean RMAN is aware of the destage process? I highly doubt it. There is a way for RMAN in later version to track backups that are staged to disk and then backed up on to tape. I have never used it, and don't know any details about it. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Restoring RMAN files
On Fri, Mar 12, 2010 at 9:19 PM, awiggins netbackup-fo...@backupcentral.com wrote: Is there any way to restore RMAN files as standard files using bprestore? I've been told you can but I get the error below when I try: What is it you are actually trying to accomplish? Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN, Veritas - Correlating Media ID after tape vaulted
That's what we're doing now, but it seems rather kludgy to me.
It should be possible to exactly correlate the Media ID's.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
On Wed, Sep 23, 2009 at 5:43 AM, Jeff Lightner jlight...@water.com wrote:
Since you know the completion time and elapsed time from the RMAN output
you could figure it out by doing:
bpimmedia -L -policy policy -d 06/14/2009 017:00:00 -e 04/27/2008
18:30:00
The end time (-e) is the one shown for completion (padded a little) and the
start time (-d) is subtracting the hour and three minutes from that end
time (and padding a little). This will show you the backup IDs and the
image 1 and image 2 data. The image 2 data is the vaulted tapes. This
would show you only the image 2 tapes if the image 1 tapes had already
expired. Some people keep a longer retention on offsite than on site.
--
*From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto:
veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Jared Still
*Sent:* Tuesday, September 22, 2009 7:12 PM
*To:* veritas-bu@mailman.eng.auburn.edu
*Subject:* [Veritas-bu] RMAN, Veritas - Correlating Media ID after tape
vaulted
When determining which tapes to recall from offsite, RMAN provides the
RESTORE DATABASE PREVIEW RECALL syntax to identify the needed tapes.
Here's an example:
RMAN RUN
2 {
3 set until time to_date('06/17/2009 08:00:00','mm/dd/ hh24:mi:ss');
4 restore database preview recall;
5 }
executing command: SET until clause
Starting restore at 09/22/2009 11:15:21
...
List of Backup Sets
===
BS Key Type LV Size Device Type Elapsed Time Completion Time
--- -- -- --- ---
2070190 Incr 0 89.78G SBT_TAPE01:03:42 06/14/2009 18:20:43
BP Key: 2070201 Status: AVAILABLE Compressed: NO Tag:
TAG20090614T180051
Handle: PRD_T20090614_db_s21827_p1_t689536853 Media: 002774
List of Datafiles in backup set 2070190
File LV Type Ckp SCNCkp TimeName
-- -- ---
24 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA10\BTABD_60\BTABD.DATA60
37 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA2\SOURCED_1\SOURCED.DATA1
48 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA13\ES700I_1\ES700I.DATA1
Notice the Media ID of 002774. So far, so good.
The problem occurs when working with media that has been vaulted.
What occurs then is the the images on 002774 are copied to a new tape with
a different Media ID.
Let's say in this case the vaulted tape has a Media ID of 003500
So tape 003500 goes offsite, and tape 002774 is put back in the scratch
pool and reused.
At this point the RECALL PREVIEW is reporting the incorrect Media ID,
because
RMAN has no knowledge of the tape vaulting.
This brings up some questions I have not been able to find answers to.
1) What NBU command can be used to correlate the old Media ID to the new
Media ID?
I have examined and tried bpimmedia, bpimagelist and vmquery. No joy.
2) I believe the (unpublished) RMAN SBT API has routines to allow the media
ID to be updated in the catalog in the event a tape is copied to a new one
which
is moved offsite. Does anyone know where the docs are regarding this ( I
have
looked), and if Veritas makes use of it. I have looked at the CROSSCHECK
and
CHANGE RMAN commands, but didn't see anything relevant.
That doesn't mean it wasn't there however, I just could have missed it.
The whole point of this post is to learn how to use the information
provided by
RMAN to request the correct tapes to be returned from offsite, given a date
and time to restore to.
Please don't suggest requesting a date range of tapes. We are already doing
that, and it is crude and time consuming.
Thanks,
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
*Please consider our environment before printing this e-mail or
attachments.*
--
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you
have received this electronic transmission in error, please reply
immediately to the sender that you have received the message in error, and
delete it. Thank you.
--
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http
Re: [Veritas-bu] RMAN, Veritas - Correlating Media ID after tape vaulted
On Wed, Sep 23, 2009 at 9:49 AM, Jeff Lightner jlight...@water.com wrote: If you’re saying RMAN isn’t that good at keeping track of things I’d have to say I agree but that’s something the Oracle folks should address. Oracle has provision in the RMAN API to update the RMAN repository when media ID's are changed due to vaulting. I've seen it addressed somewhere in the docs, can't haven't been able to find it again. As the API is published only to partners, there's no API documentation for me to go look this up. It's up to Veritas to actually implement this in the Oracle MML. :) Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NetBackup Training
We were planning to have some onsite training from Symantec, but they managed to price themselves right out of the market. Does anyone here have some references for good onsite NetBackup training? This would be for NetBackup 6.5, mixed Windows/Linux environment, predominantly Windows however. All the usual suspects are present: SAN, DFS, SQL Server, Oracle, misc other things. TIA Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN, Veritas - Correlating Media ID after tape vaulted
When determining which tapes to recall from offsite, RMAN provides the
RESTORE DATABASE PREVIEW RECALL syntax to identify the needed tapes.
Here's an example:
RMAN RUN
2 {
3 set until time to_date('06/17/2009 08:00:00','mm/dd/ hh24:mi:ss');
4 restore database preview recall;
5 }
executing command: SET until clause
Starting restore at 09/22/2009 11:15:21
...
List of Backup Sets
===
BS Key Type LV Size Device Type Elapsed Time Completion Time
--- -- -- --- ---
2070190 Incr 0 89.78G SBT_TAPE01:03:42 06/14/2009 18:20:43
BP Key: 2070201 Status: AVAILABLE Compressed: NO Tag:
TAG20090614T180051
Handle: PRD_T20090614_db_s21827_p1_t689536853 Media: 002774
List of Datafiles in backup set 2070190
File LV Type Ckp SCNCkp TimeName
-- -- ---
24 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA10\BTABD_60\BTABD.DATA60
37 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA2\SOURCED_1\SOURCED.DATA1
48 0 Incr 7113842263 06/14/2009 18:00:59
S:\ORACLE\PRD\SAPDATA13\ES700I_1\ES700I.DATA1
Notice the Media ID of 002774. So far, so good.
The problem occurs when working with media that has been vaulted.
What occurs then is the the images on 002774 are copied to a new tape with a
different Media ID.
Let's say in this case the vaulted tape has a Media ID of 003500
So tape 003500 goes offsite, and tape 002774 is put back in the scratch pool
and reused.
At this point the RECALL PREVIEW is reporting the incorrect Media ID,
because
RMAN has no knowledge of the tape vaulting.
This brings up some questions I have not been able to find answers to.
1) What NBU command can be used to correlate the old Media ID to the new
Media ID?
I have examined and tried bpimmedia, bpimagelist and vmquery. No joy.
2) I believe the (unpublished) RMAN SBT API has routines to allow the media
ID to be updated in the catalog in the event a tape is copied to a new one
which
is moved offsite. Does anyone know where the docs are regarding this ( I
have
looked), and if Veritas makes use of it. I have looked at the CROSSCHECK and
CHANGE RMAN commands, but didn't see anything relevant.
That doesn't mean it wasn't there however, I just could have missed it.
The whole point of this post is to learn how to use the information provided
by
RMAN to request the correct tapes to be returned from offsite, given a date
and time to restore to.
Please don't suggest requesting a date range of tapes. We are already doing
that, and it is crude and time consuming.
Thanks,
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] DR data restores not writing all data
Speaking solely for myself, there isn't really a lot of information here to go on. How were the backups made? Are they RMAN backups, or something else? How was the restore done? Have you examined restore logs? etc... Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist On Thu, Sep 17, 2009 at 12:02 PM, JBrownell netbackup-fo...@backupcentral.com wrote: Just getting ready to engage Symantec support on this one but thought I would see if anyone else has had this issue before. We run NetBackup 6.5.4 and just completed our DR test and had many issues. The one that concerns us most is when we selected all required datasets and executed the restore the job would run and seem to indicate all was fine. We would get a 0 exit code and the amount recovered would seem to be about right from NetBackup point of view. When the users went to validate the server they would indicate that significant amounts of data would be missing randomly throughout the recovery. Sometimes rerunning the job would return the data, sometimes not. All seemed to be going well at the start of our test when we were recovering windows SQL data but once we began restoring UNIX Oracle data it seemed to all fall apart. ( Sounds like it should not matter but that was the observation.) At home we never experience anything like this and have always been able to successfully restore all data on the first pass. Any insight or similar experiences would be greatly appreciated. Thanks. +-- |This was sent by jim_brown...@conseco.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up multiple Oracle db's from a single host
On Thu, Apr 30, 2009 at 2:23 PM, nellis netbackup-fo...@backupcentral.comwrote: I'd like to ask everyone; what works best for those of you backing up multiple Oracle db's from a single host. I have several Oracle 10g servers I backup. Each has anywhere from 1 to 20 db instances. I use a single policy and a common path script name to backup the Oracle servers. This for me keeps the number of policies I have to manage down to a minimum. This highlights a long standing shortcoming of NBU - the inability to manually backup only one of the backup selection in policy directly from the admin console. Is there a venue for requesting enhancements for NBU? Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup Oracle Script for Window Systems
On Wed, Apr 22, 2009 at 5:55 AM, Todd Jackxon netbackup.i...@gmail.comwrote: Hello Everyone Is there anyone out there running Oracle on a Windows box? If so can you explain how you are running your script on the client side for Backups? Our setup on windows uses a config file (CMD script) to set some env variables, and then run the backup. If you only have one db on Windows to backup, you could just use the wizard on the client to generate a template. The template will then be on the master server, and you will reference the template as a backup selection. Fairly simple to setup. Not as flexible as scripting, but with one database on windows, you probably don't want to spend a lot of time on it. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN and Netbackup timeout issues
On Wed, Mar 11, 2009 at 9:27 AM, Jared Still jkst...@gmail.com wrote: On Thu, Mar 5, 2009 at 7:56 AM, Roy McMorran mcmor...@mdibl.org wrote: You should probably enable block change tracking. This allows Oracle to track changes to the database so that RMAN does not scan the database looking for changes to the database for incremental backups, but just reads the BCT file and backs up the blocks pointed to. It is very fast, and timeouts should no longer be an issue. For the benefit of anyone reading this thread after the fact, Roy reported that use Block Change Tracking reduced the incremental backup time from 4-6 hours to 15 minutes. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN to backup big empty DB
On Sat, Mar 14, 2009 at 8:48 AM, Dennis Peacock netbackup-fo...@backupcentral.com wrote: On your master/media server, you may want to check and see if you have the following tuning parameters in /usr/openv/netbackup/db/config: NUMBER_DATA_BUFFERS SIZE_DATA_BUFFERS SIZE_DATA_BUFFERS_RESTORE ... Maybe, but there's little point in tweaking knobs when you don't know why the system is slow. Diagnosis first to find the problems, then fix the problems, if they can be fixed. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN and Netbackup timeout issues
On Thu, Mar 5, 2009 at 7:56 AM, Roy McMorran mcmor...@mdibl.org wrote: Hi all, The nightly incremental backups are failing. They run for about 3 hours, then fail with a 41 error. Then retry, run for about 3 hours and then error 41 again. Then the job fails with an error 6. This is a large database and (at times) very static. I surmise that the incremental backup is indeed running for 3 hours without finding any changed blocks to write to tape, thus triggering the timeout. And indeed the weekly full backup always runs to completion without any problem (takes about 7 hours). You should probably enable block change tracking. This allows Oracle to track changes to the database so that RMAN does not scan the database looking for changes to the database for incremental backups, but just reads the BCT file and backs up the blocks pointed to. It is very fast, and timeouts should no longer be an issue. Here's how to check if it is enabled: select status from v$block_change_tracking; Here's an example of enabling it: alter database enable block change tracking using file '/u01/oradata/ts10/dbf/ts10/bctf01.dbf' reuse / The file will not be of benefit until after the next full backup. http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmbckba.htm#sthref937 http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_1004.htm#sthref3774 Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN to backup big empty DB
On Fri, Feb 27, 2009 at 3:26 AM, LDi netbackup-fo...@backupcentral.comwrote: Hi, Could someone help us determine what to expect with this situation : - Backup server : SERVER_A - DB server : SERVER_B (as StorageNode or MediaServer with 4 SAN Drives attached, see below) - DB server : PA_RISC HP-UX 11.11 (HP 9000 rp7410) - Oracle 10g R2 DB : 3,6TB - Real amount of datas : 50GB - RMan allocating 3 channels (SBT) - RMan MAXSETSIZE 128G - RMan MAXPIECESIZE 128G - RMan FILESPERSET 32 - Drives : 3 emulated LTO3 (VTL Quantum PVX 2TB/H) At the moment, the backup process lasts 4.5 hours (only 8 to 10GB/H throughput) ! Is it something normal, do you have any suggestions ? There are 3 major elements to consider: * how fast can data be read from the source system? * how fast can data be written on the target system? * how fast can data be transferred from source to target? You can easily run some simple benchmarks to test each of these. If none of those reveal a bottleneck, you need to consider some other things obviously. :) For instance, what is RMAN doing during all this time? Are you looking at the IO read rate on Oracle? If it seems very fast, then it seems likely that RMAN is scanning much more than the 50G of data you have. Has this source database ever held 3TB of data? The point of this question is really Where are the high water marks in the datafiles? RMAN will scan to the high water mark - it doesn't matter how much data is actually in the database. If the HWM has been set so high in the datafiles by previous data that the total value of all HWMs in the files is 3TB, then RMAN will scan 3TB of files. Following is a script you can run to determine where the HWM is set. Please post the results of this script back to this thread. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist set linesize 200 col file_name format a50 head 'FILE NAME' col file_size format 999,999,999,999 head 'FILE SIZE|BYTES' col shrink_size format 999,999,999,999 head 'SHRINK TO|SIZE BYTES' col tablespace_name format a15 head 'TABLESPACE' col bytes_saved format 999,999,999,999 head 'BYTES SAVED' col max_block_id format 9 head 'MAX BLOCK ID' break on tablespace_name skip 1 break on report compute sum of bytes_saved on tablespace_name compute sum of bytes_saved on report compute sum of file_size on tablespace_name compute sum of file_size on report compute sum of shrink_size on tablespace_name compute sum of shrink_size on report with maxext as ( select file_id, max(block_id) max_block_id from dba_free_space group by file_id ), shrink as ( select t.tablespace_name , f.file_id , f.file_name , m.max_block_id , f.blocks * t.block_size file_size , case when ((nvl(m.max_block_id,f.blocks+1)-1) * t.block_size) = (128*1024) then(nvl(m.max_block_id,f.blocks+1)-1) * t.block_size else 128*1024 end shrink_size from maxext m , dba_data_files f , dba_tablespaces t where m.file_id(+) = f.file_id and t.tablespace_name = f.tablespace_name and t.contents = 'PERMANENT' ) select s.tablespace_name , s.file_id , s.max_block_id , s.file_name , s.file_size , s.shrink_size , (s.file_size - s.shrink_size) bytes_saved from shrink s order by tablespace_name, file_id / ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Intermittent ORA-19511 with Oracle RMAN
A little environmental info: client: RedHat Linux ES 4 Net Backup 5.1 MP5 Oracle 9.2.0.6 Master and Media Server: Windows 2003 Server SP1 NetBackup 6.0 MP7 Intermittently I am seeing the following errors on 2 nearly identical linux servers when backing up some Oracle databases. channel ORA_SBT_TAPE_1: starting piece 1 at 11-FEB-09 RMAN-00571: === RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === RMAN-00571: === RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 02/11/2009 05:17:57 ORA-19506: failed to create sequential file, name=PROD_T20090211_db_s6095_p1_t678518252, parms= ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: socket open failed I've searched the Veritas support site and googled for this, without finding anything useful. There are some recommendations from veritas to check name resolution. (Server names and IP addresses edited) # ./bpclntcmd -pn expecting response from server MEDIA_SERVER orhrprd01.radisys.com orhrprd01 10.1.100.68 64800 # # ./bpclntcmd -hn rsysnbu host rsysnbu: rsysnbu.radisys.com at 192.168.1.10 (0x) checkhname: aliases: # # ./bpclntcmd -hn 192.168.1.10 host 192.168.1.10: 192.168.1.10 at 192.168.1.10(0xXXX) checkhname: aliases: This error occurred on one server this morning. The time previous to that was two weeks ago. Any ideas on what this may be? Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN - Duplicate Database with Veritas to new server
Earlier this year I was asking about Duplicate Database problems with
NetBackup and Oracle.
Here's the thread from the Oracle-L list. I think I asked on this list as
well.
http://www.freelists.org/archives/oracle-l/05-2007/msg00324.html
Well, it's back, and this time with a solution.
It seems I've spent a lot of time lately chasing down NetBackup
idiosyncrasies.
This is NetBackup 5.1 MP5 on Windows 2003.
If interested, read the referenced thread, it isn't very long.
Here's the solution.
This does NOT work:
RUN
{
allocate auxiliary channel C1 device type 'sbt'
parms=ENV=(NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu);
allocate auxiliary channel C2 device type 'sbt'
parms=ENV=(NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu);
set until time to_date('08/07/2007 06:08:00','mm/dd/ hh24:mi:ss');
DUPLICATE TARGET DATABASE TO ORCL;
}
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of Duplicate Db command at 08/07/2007 13:41:22
RMAN-03015: error occurred in stored script Memory Script
ORA-19507: failed to retrieve sequential file,
handle=APP_T20070806_db_s1075_p1_t629896012, parms=
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Backup file APP_T20070806_db_s1075_p1_t629896012 not found in NetBackup
catalog
RMAN **end-of-file**
This however, DOES work:
RUN
{
allocate auxiliary channel C1 device type 'sbt';
allocate auxiliary channel C2 device type 'sbt';
send
NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu;
set until time to_date('08/07/2007 06:08:00','mm/dd/ hh24:mi:ss');
DUPLICATE TARGET DATABASE TO ORCL;
}
Setting up the parameters with the ALLOCATE CHANNEL command does not work
with DUPLICATE
DATABASE and NetBackup.
Using the SEND command to set the parameters does work.
This is a problem that has been reported in the past on MetaLink, and I
thought Veritas had it fixed, as
it does work now for making backups and with automatic channels.
Apparently they missed a spot.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN - Duplicate Database with Veritas to new server
On 5/16/07, ryeddu [EMAIL PROTECTED] wrote: Did you make the modification son the Netbackup Master server, for an alternate (destsination) client to see the Source client. There is and altnames directory created on the master server. I see I missed this message earlier. Thanks, already familiar with altnames, that wasn't the problem. Never did get the DUPLICATE to work, though a restore did work. Strange. I've done this before, but I have found strange problems before with NBU and RMAN. -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN - Duplicate Database with Veritas to new server
So I'm trying to run a duplicate database with RMAN
and having some trouble getting it to work.
Platform:
(Target Database)
Node A: PRD
RH Linux 4
Oracle 9.2.0.6
Veritas client 5.1
Oracle owner: oraprod
(Auxiliary Instance)
Node B: DEV
RH Linux 4
Oracle 9.2.0.6
Veritas client 5.1
Oracle owner: oradev
Veritas Master Server: Windows 2003, Veritas 5.1 MP5
Here is what is not working:
Login to RMAN:
$ORACLE_HOME/bin/rman target nbu/[EMAIL PROTECTED] auxiliary / nocatalog
Run duplicate script:
The ENV variables are set to the values used when the backup was created on
Node A.
run {
allocate auxiliary channel clone_db_2 device type 'sbt'
parms=ENV=(NB_ORA_CLIENT=PRD,NB_ORA_POLICY=ORA_PRD_full,NB_ORA_SERV=nbu_server,NB_ORA_SCHED=Daily-Full);
set newname for datafile 1 to
'/u01/oracle/dev/devdata/dbf/prod_system_01.dbf';
...
set newname for datafile 46 to
'/u01/oracle/dev/devdata/dbf/sysdba01.dbf';
set until time to_date('05/05/2007 12:00:00','mm/dd/
hh24:mi:ss');
DUPLICATE TARGET DATABASE TO DEV
LOGFILE
GROUP 1
...
SIZE 20M;
}
The syntax of the script is fine - no parsing errors occur.
Unnecessary bits have been edited out for conciseness.
Output:
connected to target database: PROD (DBID=15620415)
using target database controlfile instead of recovery catalog
connected to auxiliary database: DEV (not mounted)
RMAN
RMAN
RMAN run {
2
3
4
5
6 allocate auxiliary channel clone_db_2 device type 'sbt'
7
parms=ENV=(NB_ORA_CLIENT=PRD,NB_ORA_POLICY=ORA_PRD_full,NB_ORA_SERV=nbu_server,NB_ORA_SCHED=Daily-Full);
8
9 set newname for datafile 1 to
'/u01/oracle/dev/devdata/dbf/prod_system_01.dbf';
...
54 set newname for datafile 46 to
'/u01/oracle/dev/devdata/dbf/sysdba01.dbf';
55
56 set until time to_date('05/05/2007 12:00:00','mm/dd/
hh24:mi:ss');
57
58 DUPLICATE TARGET DATABASE TO DEV
59 LOGFILE
60GROUP 1
61 (
...
74 ) SIZE 20M;
75
76 }
allocated channel: clone_db_2
channel clone_db_2: sid=11 devtype=SBT_TAPE
channel clone_db_2: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET NEWNAME
...
executing command: SET until clause
Starting Duplicate Db at 08-MAY-07
printing stored script: Memory Script
{
set until scn 2000109207;
set newname for datafile 1 to
/u01/oracle/dev/devdata/dbf/prod_system_01.dbf;
set newname for datafile 2 to
...
/u01/oracle/dev/devdata/dbf/noetix_views_01.dbf;
set newname for datafile 46 to
/u01/oracle/dev/devdata/dbf/sysdba01.dbf;
restore
check readonly
clone database
;
}
executing script: Memory Script
executing command: SET until clause
...
executing command: SET NEWNAME
Starting restore at 08-MAY-07
channel clone_db_2: starting datafile backupset restore
channel clone_db_2: specifying datafile(s) to restore from backup set
restoring datafile 1 to /u01/oracle/dev/devdata/dbf/prod_system_01.dbf
...
restoring datafile 00046 to /u01/oracle/dev/devdata/dbf/sysdba01.dbf
released channel: clone_db_2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of Duplicate Db command at 05/08/2007 14:52:13
RMAN-03015: error occurred in stored script Memory Script
ORA-19507: failed to retrieve sequential file,
handle=bk_PROD_u77igrh59_s1255_p1_t621659305, parms=
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Backup file bk_PROD_u77igrh59_s1255_p1_t621659305 not found in
NetBackup catalog
RMAN
RMAN **end-of-file**
This problem seems to be an evironment or permissions problem.
The auxiliary node can browse the backups from the target node via
the netbackup command 'bplist', so the netbackup backup catalog
is visible for backups from other nodes.
The file that is shown as not found in the backup catalog is indeed
there, and can be seen as per previous comments about bplist.
A straight restore of the DEV database was initiated to ensure that
the communications from Node B to the NetBackup server were
functioning properly.
Running the job from Node A ( owner of the backup files) gets
the same results.
I have successfully run done similar database duplicate jobs,
the difference being that the duplicate database was on the
same node.
Several notes on MetaLink, Veritas support site, and googling
have yielded a number of things to check, but no help.
So, if you have some insights into this issue, please feel free to share.
Thanks,
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN recovery from tape with automatic channels
Whilst trying to simplify our restore procedures by using automatic channels
to configure RMAN for tape, I have run into the following problem.
A simple restore and recover operations fails because RMAN is opening
a disk channel rather than a tape channel.
RMAN run {
2 #allocate channel ch1 type 'sbt';
3 restore database;
4 recover database;
5 alter database open;
6 }
Starting restore at 20-MAR-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=13 devtype=DISK
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of restore command at 03/20/2007 12:05:59
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 10
...
RMAN-06100: no channel to restore a backup or copy of datafile 1
RMAN
RMAN
RMAN **end-of-file**
RMAN show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 5 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; #
default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXOPENFILES 8;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORA92\DATABASE\SNCFTL01.ORA';
# default
RMAN
As you can see, SBT_TAPE is set as the automatic channel.
The script works as expected if the 'allocate channel' line is uncommented.
Backups via the automatic channel work fine.
Environment:
Oracle 9.2.0.7
No Recovery catalog
Veritas NetBackup 5.1 MP5
Windows Server 2003 SP1
Has anyone here run into this?
Or know a possible solution?
I know there are some issues with NBU 5.1 and RMAN, so I guess
this could be another one.
I have searched MetaLink and googled veritas.com - not much help.
Thanks,
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Interesting Error with NBU 5.1MP5 and Oracle
Though no errors were raised, there is definitely an error condition.The server is 5.1 MP5 on Windows 2003 Enterprise Server.The client is RH Linux ES 4, Oracle 9.2.0.6 with the NBU
5.1 MP5 client.While investigating some backup issues, I found the following interestingcondition in a log file. Though the template seen in the log clearly shows that database DB01 is to be backed up, database DB02 was the one that was
actually backed up.This has been verified with bplist, and the fact that the controlfile autobackfilename inludes the DBID from DB01. Both databases are on the sameserver, but the passwords for the NBU account is different on each. It appears
as if the NBU software is picking up the wrong database and password fromit's own data. Losing track of pointers.Also, both databases have backups scheduled at the same time.Interesting, no?
I've opened a support case for this, but just wondered if anyone elsehas ever seen anything like this.-- Jared StillCertifiable Oracle DBA and Part Time Perl Evangelist
Log File - abbreviated for space.INF - Begin progress logging for process: (19550)
INF - Using policy ORA_ordb02_full to perform a server directed Standard backup.INF - Starting Oracle Recovery Manager.
INF - Using: /u01/app/oracle/product/9.2.0/apps9i/bin/rman
INF - Connection info: target 'nbu/[EMAIL PROTECTED]' nocatalogINF - Start of Recovery Manager input.
INF - # -
INF - # RMAN command sectionINF - # -
INF - RUN {INF - ALLOCATE CHANNEL ch00
INF - TYPE 'SBT_TAPE';INF - SEND 'NB_ORA_CLIENT=ordb02,NB_ORA_SERV=rsysnbu,NB_ORA_POLICY=ORA_ordb02_agile_full,NB_ORA_PC_SCHED=Full';
INF - BACKUP
INF - INCREMENTAL LEVEL=0INF - FORMAT 'bk_%d_u%u_s%s_p%p_t%t'
INF - DATABASE;INF - RELEASE CHANNEL ch00;
INF - # Backup Archived LogsINF - sql 'alter system archive log current';
...INF - }
INF - End of Recovery Manager input.
INF - Start of Recovery Manager output.INF - Recovery Manager: Release 9.2.0.6.0 - 64bit Production
INF - connected to target database: DB02 (DBID=2182868868)INF - using target database controlfile instead of recovery catalog
INF - allocated channel: ch00
INF - channel ch00: starting incremental level 0 datafile backupsetINF - input datafile fno=00018 name=/u01/oradata/DB02/perfstat01.dbf
INF - input datafile fno=2 name=/u01/oradata/DB02/undotbs01.dbf
INF - input datafile fno=1 name=/u01/oradata/DB02/system01.dbf
INF - input datafile fno=7 name=/u01/oradata/DB02/xdb01.dbfINF - input datafile fno=3 name=/u01/oradata/DB02/drsys01.dbf
INF - input datafile fno=6 name=/u01/oradata/DB02/users01.dbf
INF - input datafile fno=4 name=/u01/oradata/DB02/indx01.dbfINF - input datafile fno=5 name=/u01/oradata/DB02/tools01.dbf
INF - piece handle=bk_DB02_ulvhu9u3c_s703_p1_t602208364 comment=API Version 2.0,MMS Version
5.0.0.0INF - channel ch00: backup set complete, elapsed time: 00:10:06
INF - Starting Control File and SPFILE Autobackup at 27-SEP-06INF - piece handle=c-2182868868-20060927-00 comment=API Version
2.0,MMS Version 5.0.0.0INF - Finished Control File and SPFILE Autobackup at 27-SEP-06
INF - released channel: ch00
...INF - archive log filename=/u01/oradata/DB02/archive/DB02_0001_001867.arc recid=1860 stamp=602146512
INF - archive log filename=/u01/oradata/DB02/archive/DB02_0001_001875.arc recid=1868 stamp=602209040
INF - archive log filename=/u01/oradata/DB02/archive/DB02_0001_001876.arc recid=1869 stamp=602209041INF - Starting Control File and SPFILE Autobackup at 27-SEP-06
INF - piece handle=c-2182868868-20060927-01 comment=API Version 2.0,MMS Version 5.0.0.0
INF - Finished Control File and SPFILE Autobackup at 27-SEP-06
INF - piece handle=bk_DB02_um5hu9utm_s709_p1_t602209206 comment=API Version 2.0,MMS Version 5.0.0.0
INF - End of Recovery Manager output.INF - End Oracle Recovery Manager.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Oracle database restore
This chapter of the docs may help:http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1008564 On 7/27/06, Julio Duarte de Assis Dezan [EMAIL PROTECTED] wrote: Guys,I don't have experience with oracle restoration. I just used the DB agent for disaster recovery restore when I was testing, runing a customised database_restore.sh script with my DB variables.Now I want to know if is possible to restore this database in another machine, that has the same hardware and directore structure and also the same instance name. Is it possible just chnaging the script and other points to say to my servers that this one is that one that I backuped up the DB? How can I set a different time frame for restore, instead the last backup restore that I think is pre configured... ???I tried to change the parameters that the script send to RMAN using set until time 'Jul 17 2006 23:00:00'; but it didn`t work.. The oracle DB is running on Solaris 9 for both servers (production and test).Anyone can help me?Thanks,Julio___Veritas-bu maillist- Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Jared StillCertifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
