Veritas-bu

[Veritas-bu] bpduplicate using the -id switch

2001-07-27 11:38:33
Subject: [Veritas-bu] bpduplicate using the -id switch
From: leila AT anyloan DOT com (Leila Curic)
Date: Fri, 27 Jul 2001 08:38:33 -0700
Does anybody know how to configure nbmail.cmd file. I don't know what to put
instead of %3 where it should be file? What file do I put?
Thank you.
 Leila

-----Original Message-----
From: David A. Chapa [mailto:david AT xbpadm-commands DOT com]
Sent: Friday, July 27, 2001 7:56 AM
To: RYAN ANDERSON; kkadams AT mmm DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] bpduplicate using the -id switch


Yes, I actually do use the media id for the duplication, but its a very
selective process based on the schedule and client name.

bpVault used the bid (backupid), Brian found that to be faster (I still
disagree Brian... ;-), however, there are some caveats to using the bid
versus my method.  I don't have my documentation with me to look up those
caveats, but Brian (or Bryan C.) if you are listening...could you jump in?

I used to run into contention problems.  Where I had more than one stream
looking for the same piece of media.  I solved that by doing what I do(wah
ditty ditty dum ditty do...sorry...its called lack of sleep)...

So what I do is identify which images are candidates for duplication based
on some rules in my scripts.

First I call the client select script (dup_client_select).  My comments in
that script says that it orders the images by priority (not true, this is
where I hit the wall), based on a client's request, which didn't work
out...but I haven't changed my comment yet.

>From that I create FILEs that are named after the Media ID to be used in the
duplication, that have the Media ID, Schedule and class.  This little trick
completely eliminates the contention problem and you will get as much
throughput as you have drives and bandwidth.

My scripts look for a MEDIAID.todo file in the list, when it grabs it, it
renames it to MEDIAID.inprog.  I keep doing this until my max tasks variable
has been reached.

Therefore no other duplication process can possibly have the same request
queuing up.

If you want to use my scripts on your NT server, you will have to purchase
MKS Toolkit (http://www.mks.com) in order to get a korn shell.  I have
tested this and it works like a dream on NT/2000 as well.

sorry for my delay in returning this email, I've fallen way behind on my
reading.

If you have any more questions about my duplication scripts, please feel
free to contact me directly too.

847 514 7724 (cell phone)

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
Consulting Manager
DataStaff, Inc.
847 413 1144
http://www.consulting.datastaff.com
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of RYAN
ANDERSON
Sent: Wednesday, July 25, 2001 12:16 PM
To: kkadams AT mmm DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] bpduplicate using the -id switch


kkadams AT mmm DOT com wrote:
>
> ? regarding the bpduplicate command using -id mediaid
>
> The Administrator's guide states "If an original is fragmented between
different
> media ID's, Netbackup duplicates only the fragments that exist on the
specified
> Media ID"
>
> However, when I use the command the first tape that is selected is a
different
> media id than the one specified in the command. Which leads me to believe
that
> the documentation is incorrect.
>
> My goal is to streamline the duplication process so I do not end up with
tape
> contention. I'm not sure whether I should run duplications from an
imagelist or
> a list of tapes.
>
> David Chapa.... your script on the Advanced Netbackup scripting site uses
the
> -id switch. Have you had any problems with tape contention when
duplicating?
>
> PS... my environment is Netbackup 3.4 Datacenter, patch 341 on a Windows
2000
> Master server.
>
> Any input or suggestions are appreciated.

His script duplicates based on client, at least the version of it I
have.

Duplicating by client or class is the easiest. You can duplicate by
backupid also if you want that granularity. I'd avoid duplicating by
media id. Here's a simple way you could duplicate by backupid:

bpimagelist -hoursago 72 -st full -idonly | awk '{ print $8 }' | while
read bpimg do
        bpduplicate -backupid $bpimg -dstunit <storage unit> -v -dp <offsite
pool> -L /tmp/log.log
done

I'd try scripting it yourself, or use ones that do what you want, like
my 'nbduplicate' script (http://www.xbpadm-commands.com/) ;-)  You'd
have to convert these to Perl or batch though...


RCA
--
Ryan C. Anderson       | United Defense L.P.
ryan_anderson AT udlp DOT com | pager 952.235.9936
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

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