You could use a pre-schedule job (bpstart_notify.<policyname>) on the client
and actively create an ../netbackup/include.<policyname> file, then keep the
policy's filelist the same.

HTH - Mark



-----Original Message-----
From: Justin C. Lloyd [mailto:justin.lloyd AT mci DOT com]
Sent: Thursday, January 22, 2004 12:12 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Dynamic policies


We have a data directory where data from multiple sources is
divided up into subdirectories based on the date and the
data's source, something like /data/$YYYYMMDD/$SOURCE.  (Each
day's data will be about 30 GB.)

Every morning we would like to do a full backup of the
previous day's data from all sources.  Once a day's data is
written to disk, it never changes, so a full (plus a Vault
copy) is all we would have in backups for each day, i.e., no
incrementals for the /data filesystem.  So for each day
YYYYMMDD I would need a new policy with the line

/data/${YYYYMMDD - 1}/*

in the policy's file list.

I obviuosly would not want to hand-create hundreds of policies.
This leads me to two possible solutions:

1. Create a unique policy for every day.  A cron job could
run a script to generate, say, a month of policies in advance.
(Perl could handle the $date - 1 easily.)  I would also want
to periodically delete old policies.

2. Have just one policy whose file list is updated daily by
cron.

Number 2 is much more to my liking.  That being said, does
this sound more difficult than it needs to be?

Justin


-- 
Justin C. Lloyd
Unix System Administrator
MCI System Technology Solutions
Office 703.886.3219 Vnet 806.3219 Fax 703.886.0132
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu