I'm not sure my messages are actually getting through, but I'll try.

>From what I understand about CLOPSETs the clients should re-read it each
time they start a backup, so you should not have to restart the
scheduler for them to pickup changes.  I never have anyway.

See Ya'
Howard


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Zoltan Forray/AC/VCU
> Sent: Friday, March 21, 2008 9:36 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Forcing excludes
> 
> Doing some reviews of volume contents, we see lots of folks putting
> their
> MP3 rips on volumes that are being backed-up (after all....we are a
> university).  Besides the legal implications, the amount of storage
> occupied by these files is probably sizable, considering we have over
> 500TB of backups in 4-TSM servers.
> 
> So, we are looking into the prospect of excluding MP3's, en-mass.
> 
> I realize I can create a CLOPSET statement to EXCLUDE "*:\...\*MP3"
> 
> Is there any way to force CLOPSET changes without having to have every
> node restart their scheduler service to pickup these changes?