While there may be no absolute "standard", there _are_ good
ideas ("exclude.fs /afs", for example, on AFS clients, and
"exclude.fs /proc").  There's no way I can expect random users
(e.g. faculty members who can barely log on) to make reasonable
decisions about what to back up, so I'll have to do the bulk of
the work for them.  And, since each machine is indihvidually
owned and operated, there's no rigid definition of filespaces,
either, nor (generally) is there anyone around who might be
remotely considered a sysadmin.

So - I can make these up myself, but I'd appreciate seeing what
others had come up with.  Would "adsm.org" be interested in
archiving what I come up with?

Pat Wilson
paw AT dartmouth DOT edu

>  There is no standard for what you should or should not backup.  The default
>  should be exclude * ( everything ) and then take a serious look at what
>  should be included.  This approach would eliminate all the unnecessary
>  files, and force the SA to choose what is important enough to be on ADSM,
>  MHO.
>
>  Anthony Jones
>  Koch Industries, Inc.
>  Platform Technologist
>  316-828-2432
>
>  > -----Original Message-----
>  > From: Pat Wilson [SMTP:paw AT NORTHSTAR.DARTMOUTH DOT EDU]
>  > Sent: Wednesday, November 11, 1998 8:53 AM
>  > To:   ADSM-L AT VM.MARIST DOT EDU
>  > Subject:      "standard" include/exclude files?
>  >
>  > Is there a set, somewhere, of "standard" include/exclude files?
>  > For example, you probably want to exclude /etc/objrepos from AIX
>  > backups, and /proc from OSes that have that...
>  >
>  > Thanks.
>  >
>  > Pat Wilson
>  > paw AT dartmouth DOT edu