Pretty easy to do in one command in unix. Im not sure what you use to 
identify your tapes, but what ever it is if its outputs just the tape 
ids then do something like this :-

# mydate="mm/dd/yyyy" export mydate
# for x in `<your command to produce tape id>`
 >do
 >echo "Changing tapes id [$x] to expire on $mydate
 >bpexpdate -m $x -d $mydate
 >done

This will then change all your tapes to expire on $mydate.

This can of course be scripted too

Hope it helps a little.

Thanks
Dave




>I don't have any experience with scripting, yet. Changing the retention
>on over 100 media is a very time consuming task to do manually. 
>
>-----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 Tim Berger
>Sent: Monday, February 14, 2005 8:40 PM
>To: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: Re: [Veritas-bu] Month End and Weekly Backup
>
>Please clarify "getting old".  What you're doing sounds like the most
>efficient way of getting the task accomplished (if it were automated).
> It would also minimize the chance of more than one level 0 happening
>within the approximate monthly time frame.
>
>If your weekly backups are done the "netbackup way" (eg. every 7 days
>on any day) it's a very resilient way of getting regular backups done,
>but that makes it harder to have another calendar based monthly
>schedule that doesn't take place immediately after the weekly.
>
>For example, host "foo" gets backed up on Jan 31st on the weekly
>schedule, then the monthly schedule with a window from Feb 1st to the
>7th says, it's time for a level 0. Somewhat of a waste, don't you
>think?
>
>I'm thinking a scriptable solution of adjusting the retention periods
>would minimize potential scheduling complications.  But maybe there's
>another reason why you've rulled that out. Can anyone think of a
>reason why this might be *bad*?
>
>On Thu, 10 Feb 2005 13:57:17 -0500, Zermeno, Brandon (Contractor)
><BZERMENO AT intersil DOT com> wrote:
>  
>
>> 
>> 
>>
>>What is the "best practice" on handling the Month end backups and the
>>    
>>
>weekly
>  
>
>>backups? What I mean is, I have Full Weekly's that are retained for 3
>>months, but I also have to squeeze in the Month Ends that are retained
>>    
>>
>for 1
>  
>
>>year. How are you dealing with this? I have about 70 policies with 7
>>    
>>
>master
>  
>
>>servers. We have a ton of apps that all require different settings. I
>>    
>>
>have
>  
>
>>just been going in and modifying the retention period of the weekly's
>>    
>>
>to 1
>  
>
>>year but this is getting old. I am thinking of doing inline copies to
>>    
>>
>a
>  
>
>>different pool. Any ideas. 
>>    
>>
>
>
>  
>