I'd need to know a lot more about your Vault and SLP configuration to say why 
Vault's failing to pick your duplicated media. If you shoot me the output of 
nbstl -L and your vault.xml (maybe pass it through the following Perl script 
first to make it easier to sanitize any of your employer's private information 
if you need to) privately, I'll be happy to take a look.

---8<---
#!/usr/bin/perl -w

use strict;
use XML::Simple;
use Data::Dumper;

my $data = XMLin("-");

$Data::Dumper::Indent = 1;
$Data::Dumper::Maxdepth = 0;

print Dumper($data);
--->8---

I wasn't suggesting that vaulting originals rather than duplicates would fix 
the problem you're describing (you can't, actually, vault true originals: your 
originals are on a VTL), just that it's theoretically a better way to go 
because it exposes media failures sooner (but not enough better that I've 
bothered to go change the setup in any environment I've walked into).

--
gabriel rosenkoetter
Radian Group Inc, Senior Systems Engineer
gabriel.rosenkoet...@radian.biz, 215 231 1556

From: Clooney, David [mailto:david.cloo...@bankofamerica.com]
Sent: Thursday, March 05, 2009 4:00 AM
To: Rosenkoetter, Gabriel; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] NBU 6.5.3 Vault Query

Thanks Gabriel

This is what I have tried.

The Vault is setup for the correct volume group and pools, the criteria to be 
met are all "backups", all policies etc etc in the last 8 days. Duplication is 
skipped as this is taken care of in the SLP, catalog backup skipped for the 
purpose of testing. As I am in implementation I continuously duplicate to this 
volume group so there are definitely valid image copies that meet the criteria.

However the vault runs successfully however finds no images. From your mail 
below are you suggesting promote the duplicate copy to primary ? and in turn 
the vault will then meet its criteria?

Thanks in advance

David Clooney
From: Rosenkoetter, Gabriel [mailto:gabriel.rosenkoet...@radian.biz]
Sent: 04 March 2009 21:54
To: Clooney, David; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NBU 6.5.3 Vault Query

No, Vault can certainly send duplicates off site. In fact, prior to the advent 
of SLPs, most people duplicated images within Vault and sent those off site. 
(I've always theoretically preferred to send my originals off-site and promote 
my duplicates to be short on-site retention, which Vault can also do, but I've 
never walked into an environment already set up that way.) Just create the 
Vault within the robot where the duplicates are and specify the appropriate 
limitations (probably by volume pool in your case), skip the duplication step, 
perform the catalog backup (really, please, perform the catalog backup), and 
eject and generate reports.

--
gabriel rosenkoetter
Radian Group Inc, Senior Systems Engineer
gabriel.rosenkoet...@radian.biz, 215 231 1556

From: Clooney, David [mailto:david.cloo...@bankofamerica.com]
Sent: Wednesday, March 04, 2009 12:56 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NBU 6.5.3 Vault Query

Hi All

Am I correct in saying that vault can only vault backups and not duplications?

I.e. I am busy implementing a VTL(with NDMP functionality) and utilising NBU 
Lifecycle management polices.

As the VTL is equipped with NDMP Version 4 we are able to zone in physical 
drives on the backend of the VTL and pretty much setup NDMP STU's to write to 
these physical devices. The reason for this approach is that when we duplicate 
an image from a VTL volume to a physical volume the VTL becomes the data mover.

I now want to setup a process on the volume group that the physical backend 
volumes reside in, however these volumes are filled with duplications and not 
backups.

I am guessing , as new to vault,  that you cannot vault duplicated images?

Any suggestions would be helpful.

Regards

David Clooney
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of 
cksteh...@pepco.com
Sent: 04 March 2009 16:54
To: VERITAS-BU@mailman.eng.auburn.edu
Cc: VERITAS-BU@mailman.eng.auburn.edu; veritas-bu-boun...@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Upgrading media server from 5.0.5 to 6.5.2


Hi Pranav

I suggest you read the Symantec documentation

Check out this document
http://seer.entsupport.symantec.com/docs/290141.htm

Carl



----------------------------------
Carl Stehman
Distributed Services
Pepcoholdings, Inc.
701 Ninth St NW
Washington DC 20068
202-331-6619
------------------------------------

Pranav <netbackup-fo...@backupcentral.com>
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu

03/04/2009 11:30 AM
Please respond to
VERITAS-BU@mailman.eng.auburn.edu


To

VERITAS-BU@mailman.eng.auburn.edu

cc

Subject

[Veritas-bu]  Upgrading media server from 5.0.5 to 6.5.2








Hi,

We are planning to upgrade our media server from 5.0.5 to6.5.2
Please provide the necessary steps that we should follow while doing this and 
also looking for a solution to check media inconsistency.

We are also planning to attach a lto4 library with this.
So ,does this library can read lto2 tapes if we need to restore something.

Thanks!

Pranav

+----------------------------------------------------------------------
|This was sent by pranav_vent...@hotmail.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



This Email message and any attachment may contain information that is 
proprietary, legally privileged, confidential and/or subject to copyright 
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is 
intended solely for the use of the person(s) to which it is addressed. If you 
are not an intended recipient, or the employee or agent responsible for 
delivery of this Email to the intended recipient(s), you are hereby notified 
that any dissemination, distribution or copying of this Email is strictly 
prohibited. If you have received this message in error, please immediately 
notify the sender and permanently delete this Email and any copies. PHI 
policies expressly prohibit employees from making defamatory or offensive 
statements and infringing any copyright or any other legal right by Email 
communication. PHI will not accept any liability in respect of such 
communications.

________________________________
Notice to recipient:
The information in this internet e-mail and any attachments is confidential and 
may be privileged. It is intended solely for the addressee. If you are not the 
intended addressee please notify the sender immediately by telephone. If you 
are not the intended recipient, any disclosure, copying, distribution or any 
action taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful.

When addressed to external clients any opinions or advice contained in this 
internet e-mail are subject to the terms and conditions expressed in any 
applicable governing terms of business or client engagement letter issued by 
the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., 
London Branch and Banc of America Securities Limited are authorised and 
regulated by the Financial Services Authority.  For all U.K. corporate 
disclosures, please refer to 
www.bankofamerica.com/ukcompanies<http://www.bankofamerica.com/ukcompanies>
________________________________
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to