Well, Marc, if you're stuck between the rock and the political hard place,
you could create 2 nodes.

node
node_hybrid

Create two schedulers.  Use two different optfiles with two different
inclexcl lists.  Or put the nodes in seperate domains so they can use
different default mgmtclasses.  Make the schedule for node_hybrid run a
normal incremental backup on the first of every month.  It's copygroup
should be something like....

Policy    Policy    Mgmt      Copy      Versions Versions   Retain  Retain
Domain    Set Name  Class     Group         Data     Data    Extra    Only
Name                Name      Name        Exists  Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
HYBRID    ACTIVE    MONTHLY   STANDARD        12       12      365     365
HYBRID    ACTIVE    MONTHLY   STANDARD        12       12      365     365

You may want to set the frequency to 28, or some such, just in case someone
accidentally tries to kick off a mid-month backup under the hybrid node
name.  This way only new stuff or stuff that gets changed during the last
month will get backed up.  Granted, that approximately doubles that node's
occupancy, and increases backup processing and network utilization and
whatnot once a month, but it'll be better than keeping 12 copies of
everything and a lot less effort, processing overhead, and database overhead
than most archive scenarios.

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail