If I understand the way archiving works, I don't think it uses the
include/exclude file at all.  My understanding is that 'archive' gets
everything in each of the filespaces it is told to look at. Am I
operating under a misconception?

 On Tue, 7 Dec 1999, Sanders, David
wrote:

// Thanks again Betsy for your followup;
//
// but I think that I'm confused by your response?  My belief is that running
// the archive function from the centralized schedule doesn't use the node's
// option file which is where the include/exclude list would be?  Am I to
// believe that there would be a common include/exclude list that could be used
// from the server end-of-the-pipe to blanket the archive request with pick and
// choose?  If so,, I'm missing that big time??
//
// Dave Sanders
// Sr. Technical Consultant
// MassMutual / The Blue Chip Company
// 1295 State St, E060, Springfield, MA 01111
// 413-744-5095
//
//
//
//
//
// -----Original Message-----
// From: Moir,Betsy [mailto:betsy.moir AT ABBOTT DOT COM]
// Sent: Tuesday, December 07, 1999 8:16 AM
// To: ADSM-L AT VM.MARIST DOT EDU
// Subject: Re: archive (gotta get it all)
//
//
// Instead of using the domain c: d: parameter or  the objects parameter in the
// schedule, have you tried adding the line INCLUDE *:\...\* at the top of the
// include/exclude list.  This would cause ADSM to backup everything on any
// locally attached drive, i.e. if they had only a c: drive it would only back
// that up, but if it had a c: and a d: drive it would back them both up.
//
//
//
//
// ADSM-L AT vm.marist DOT edu on 12/07/99 05:59:10 AM
// Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
// To: ADSM-L AT vm.marist DOT edu @ INTERNET
// cc:
// Subject: Re: archive (gotta get it all)
//
// Betsy, thanks for that suggestion.  But, I don't seem to be able to do this
// from my serve using the automated schedular.  I'm looking to do a generic
// backup for all platforms with a customized 1-time schedule.  I've seen
// references that say that to include "all stuff" you may have to create
// seperate schedules for each platform.  I was willing to do that but, I can't
// even get the Win95 one to "get it all".
//
// If I use "domain c: d:", that will work fine except for those workstations
// that don't have a "d" drive.  So it gets marked as failed and then will try
// to rerun and will redo the c: drive data over again.
//
// It looks like I will have to go thru the filespaces and have seperate
// schedules for those that have "c only" drives and another one for "c & d"?
//
// BTW: we do realize how much potential data we will be pumping over the
// network.  It's been raised as an issue and we are trying to determine how we
// can ask our clients to stop processing for the length of time that we need
// to do their quiesced backup.  Two opposing forces:  the client's need for
// processing their data as normal (maybe more so before the Y2K rollover) vs.
// the Insurance Commisioner request.
//
// Dave Sanders
// Sr. Technical Consultant
// MassMutual / The Blue Chip Company
// 1295 State St, E060, Springfield, MA 01111
// 413-744-5095
//
//
//
//
//
// -----Original Message-----
// From: Moir,Betsy [mailto:betsy.moir AT ABBOTT DOT COM]
// Sent: Monday, December 06, 1999 3:18 PM
// To: ADSM-L AT VM.MARIST DOT EDU
// Subject: archive (gotta get it all)
//
//
// I can help you with a couple of these things.
//
// We do a yearly archive on 10 CADD servers in our company.  They're NT
// servers
// and our ADSM server is on the VM mainframe.
//
// Because they're NT servers, we can run the archive as an NT service.  We use
// the DSMCUTIL command to create a separate NT service for the yearly backup.
// We created a separate management class for the yearly archives and at the
// top
// of all our EXCLUDE  statements in the options file we have an INCLUDE
// statement which reads:
//
// INCLUDE *:\...\* CEDCADY
//
// Keep in mind, though, that depending on how many machines you're backing up,
// this can be a huge amount of data going across your network at a possibly
// very busy time of year.  If your major concern is not losing data, I'd make
// the extra effort to get exclude statements in there for anything and
// everything you don't need to archive.
//
// where CEDCADY is the name of the management class for the yearly archive.
//
// If you're not backing up NT servers, then you'd have to initiate another
// scheduled session with ADSM or use whatever other scheduler you're using.
//
// Hope this helps
// ---------------------- Forwarded by Betsy Moir/LAKE/CHMS/ABBOTT on 12/06/99
// 02:04 PM ---------------------------
//
//
// Michael A Cernak
// 12/06/99 01:51 PM
// To: Betsy Moir/LAKE/CHMS/ABBOTT@ABBOTT
// cc:
// Subject: archive (gotta get it all)
//
// Betsy, do you think our experience with CED archives would help this guy?
// It
// also sounds like he doesn't comprehend the magnitude of the task due to
// volume of data.
// ---------------------- Forwarded by Michael A Cernak/LAKE/CHMS/ABBOTT on
// 99-12-06 01:49 PM ---------------------------
//
//
// ADSM-L AT vm.marist DOT edu on 99-12-05 06:45:40 AM
// Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
// To: ADSM-L AT vm.marist DOT edu @ INTERNET
// cc:
// Subject: archive (gotta get it all)
//
// We have been told that the Insurance Commisioner in our state (MA), has
// informed us insurance companies that we need to have "static backups of
// vital records" at the Y2K rollover.
//
// I'm trying to set up a special scheduled archive run for all participating
// client nodes (we are mainframe-based server).  I'm wondering if anyone has
// tried and true "objects" all-inclusive for a scheduled task that will get it
// all (  maybe  *:*   ?)
//
// I'm wondering what other companies are doing in this regards?
//
// Dave Sanders
// Sr. Technical Consultant
// MassMutual / The Blue Chip Company
// 1295 State St, E060, Springfield, MA 01111
// 413-744-5095
//

-
Best regards,
Best regards,
Brian

+-----------------------------------------------------------------------+
| Brian T. Huntley                         Systems and Network Engineer |
| Campus Information Services, Clarkson University                      |
| Ph/FAX: 315.268-2292/6570                                             |
| bth AT clarkson DOT edu                                 www.clarkson.edu/cis |
+-----------------------------------------------------------------------+
 UNIX *is* user friendly. It's just selective about who its friends are.
        PGP Public Key available. finger bth AT clarkson DOT edu