Veritas-bu

[Veritas-bu] VTL images to tape

2006-08-23 08:31:32
Subject: [Veritas-bu] VTL images to tape
From: Greg.Hindle at constellation.com (Hindle, Greg)
Date: Wed, 23 Aug 2006 08:31:32 -0400
I am talking about enterprise vault add on for netbackup. It has been
around for a few years now. Its not well meshed with netbackup (yet). 



Greg

-----Original Message-----
From: Rob Worman (home) [mailto:rob at worman.org] 
Sent: Tuesday, August 22, 2006 10:59 PM
To: Hindle, Greg
Cc: Darren Dunham; Veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] VTL images to tape

I'm sorry Greg, but I'm still not 100% clear which "vault" product you
are talking about in your complaints that duplication from VTL --> real
tape isn't possible.

Can you confirm that you're talking about "Enterprise Vault", the
relatively new-to-NetBackup Exchange-specific product, only runs on
windows, etc?

As more and more "EV" users start posting to this group, we're going to
have lots of confusing conversations like this... :-(

thanks
rob

On Aug 22, 2006, at 2:13 PM, Hindle, Greg wrote:

> Good questions that they cannot answer. Enterprise vault was and is 
> not part of netbackup per se. It was written outside of netbackup and 
> then "connected" to netbackup. But vault does run outside of netbackup

> to a point. So just because netbackup can see the VTL as a tape it 
> does not mean that vault will see it the same way. If fact there any 
> many things about vault that I don't like and it is frustrating that 
> the 2 products don't "talk" to each other 100%. If anyone that uses 
> vault knows that if you put tapes in your robot and run an inventory, 
> netbackup knows about the tape being added back into the robot but 
> vault does not know that the tape was put back in the robot. You have 
> to tell vault manually that it was moved back or vault ignores the 
> tape, thinking it is still in the offsite storage area. We had to 
> write a script to work around this issue as we had over 100 tapes in 
> our L700 that should be vaulted out but were not, because vault still 
> thought they were in offsite storage. This is frustrating. I am hoping

> in a future release that they integrate vault more with netbackup to 
> fix issues like this.
>
>
>
> Greg
>
> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Darren

> Dunham
> Sent: Tuesday, August 22, 2006 2:32 PM
> To: Veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] VTL images to tape
>
>>
>> Are you using enterprise vault to get your images off from the VTL to

>> tape? This is what I am referring to. There is an option in 
>> enterprise
>
>> vault that says vault the images and du0liacte them to tape. This 
>> option does not work if you are trying to vault from the VTL.
>
> I don't normally use vault, so I'm not sure of the mechanisms here.
>
> What does vault require here that a normal restore does not?  Why 
> would netbackup even know that it's a VTL and not a physical library.
>
> -- 
> Darren Dunham                                           
> ddunham at taos.com
> Senior Technical Consultant         TAOS            
> http://www.taos.com/
> Got some Dr Pepper?                           San Francisco, CA bay 
> area
>          < This line left intentionally blank to confuse you. > 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>>> This e-mail and any attachments are confidential, may contain 
>>>> legal, professional or other privileged information, and are 
>>>> intended solely for the addressee.  If you are not the intended 
>>>> recipient, do not use the information in this e-mail in any way, 
>>>> delete this e-mail and notify the sender. CEG-IP1
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>


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