Paul,

Are you defining a "command" type schedule?
Does the schedule identify the correct
batch file that runs the proper "excdsmc" command
to accomplish the backup?

If "files" are getting backed up, it probably means
that you associated the particular node to a
selective or incremental schedule and not a
"command" type schedule.

If you issue a "QUERY SCHEDULE F=D" on your TSM server,
you should get something like this:


            Policy Domain Name: STANDARD
                 Schedule Name: EXCFULL
                   Description: Daily Exchange Full Backup
                        Action: Command
                       Options:
                       Objects: G:\EXCFULL.BAT
                      Priority: 2
               Start Date/Time: 10/19/1999 07:37:17
                      Duration: 2 Hour(s)
                        Period: 1 Day(s)
                   Day of Week: Any
                    Expiration:
Last Update by (administrator): HOOBLER
         Last Update Date/Time: 10/19/1999 07:37:17
              Managing profile:


"G:\EXCFULL.BAT" is my batch file that runs the
"excdsmc" command for doing my backups.

Does this help?  If not, look in the latest version of
the Tivoli Data Protection for Microsoft Exchange
Server User's Guide. Appendix C gives you exact details
on the steps that you must do to set up the TSM base client
scheduler to perform scheduled DIR and IS backups.

If you don't have a copy, look here:

    http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm#agents

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


Paul Dowie <DOWIE AT CLEAR.CO DOT NZ> on 07/11/2000 04:45:11 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Exchange Scheduling Problems




Hi,

I don't get any errors, just that it backs up the NT file system and not
the
Exchange DS & IS.

Circular logging is disabled and I have all options at the client end, just
the OS390 doesn't seem to schedule the correct data.

thanks
Paul