Veritas-bu

Re: [Veritas-bu] RMAN, Veritas - Correlating Media ID after tape vaulted

2009-09-24 16:55:55
Subject: Re: [Veritas-bu] RMAN, Veritas - Correlating Media ID after tape vaulted
From: william.d.brown AT gsk DOT com
To: "veritas-bu AT mailman.eng.auburn DOT edu" <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Thu, 24 Sep 2009 21:52:26 +0100
I think our problem is that although I agree that what you say works, we 
don't keep an onsite copy of the backup.  So while if a restore is 
initiated from RMAN, NetBackup will work out where the primary backup 
image is, in our case that will just cause an operator request to get the 
tape and load it, as it is offsite.  Current practice by the DBAs has been 
to get the picking list from RMAN, have the tapes recalled and loaded, and 
only start the restore when they know the tapes are in the library.

So I guess what they are after is being able to use RMAN to generate the 
picking list.  It sounds as if running the RMAN 'crosscheck' after the 
duplication (or when preparing for a restore) may fixup the RMAN catalog. 
However I think I'm going to have the test that.

Of course I'd rather we had an onsite copy, but that is not yet on offer.

William D L Brown


veritas-bu-bounces AT mailman.eng.auburn DOT edu wrote on 24/09/2009 21:38:34:

> Running 6.5.3.1 on Solaris Master/Media servers.
> We backup to a VTL, and duplicate to tape using SLP - we have had no
> issues restoring from either VTL or tape.
> RMAN asks NetBackup for the image, and as long as NetBackup knows 
> where it is, (i.e. where is primary copy) it restores fine.
> >
> >Message: 5
> >Date: Thu, 24 Sep 2009 11:20:32 +0100
> >From: william.d.brown AT gsk DOT com
> >Subject: Re: [Veritas-bu] RMAN, Veritas - Correlating Media ID 
> after tape vaulted
> >To: veritas-bu AT mailman.eng.auburn DOT edu
> >Message-ID: <OF762F90E2.37580156-ON8025763B.0036C8BE-8025763B.
> 0038D059 AT gsk DOT com>
> >Content-Type: text/plain; charset=iso-8859-1
> >
> >On a similar track, has anyone experience of using staging disk 
> (not DSSU) with lifecycle policies with RMAN?
> >
> > The question I'm trying to answer (about to test) is that if the 
> backup phase of the SLP is to a disk STU, the backint will report to
> RMAN where the backup has landed on disk.
> >
> >The duplication stage then puts that onto a tape, but RMAN will not
> be told (I assume) what the media ID is.
> >
> >If a restore was requested from the agent, that I suspect is fine 
> as NetBackup will look in the catalog for where the primary copy is,
> and then pop up an operator request for the tape (that assumes that 
> [a] we expired the disk image and [b] the tape is offsite).
> >
> >Our current practice is not to submit the restore request until we 
> know the media are loaded, and the list of media to request to be 
> brought back to site comes from the RMAN catalog.
> >
> >We suspect that is going to stop working.  Has anyone seen this 
> problem, solved this problem, or found a way to avoid it?
> >
> >William D L Brown
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 


-----------------------------------------------------------
This e-mail was sent by GlaxoSmithKline Services Unlimited 
(registered in England and Wales No. 1047315), which is a 
member of the GlaxoSmithKline group of companies. The 
registered address of GlaxoSmithKline Services Unlimited 
is 980 Great West Road, Brentford, Middlesex TW8 9GS.
-----------------------------------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>