A couple suggested solutions we've used are...

1.  Use NTBackup to backup System State to disk file (from the "old" v3.7
days, to support multiple versions of registry, et. al.) -- using
pre-schedule command and batch file to run weekly;

2. Use the explicit DOMAIN option to suppress system objects for daily
backups, then use a separate schedule command on weekends to get weekly
system state backups;

3. Use default DOMAIN, with "include.systemobject ALL sysobj_class" to
control management class -- setting up shorter version count (7) and/or
retention (10 days) than most file-served data... similar to dba standards,
where we want a corruption is discovered in less than a week;  for this
mode, I'd recommend a weekly version that gets archived, for weekly
granularity,,, but don't see how that can be done -- so, an alternative is
to play with the frequency parameter, secondary node, nothing really
palatable... so ended up with just daily backups kept for 7 days, up to 15
versions (to allow for admin. folks needing manual system-state backups
before and after doing maintenance).

All the while, separate management class assigned to system state backups
(regardless of the method) to assign different version-count/retention
parameters.

Don France
Technical Architect -- Tivoli Certified Consultant
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)