Re: Exchange server backuped normal data

Mark,

I think you set up the schedule on the TSM Server incorrectly.
It needs to be a ACTION=COMMAND type schedule that calls a command
file that starts the Data Protection for Exchange backup.
For example:

    def sched mydomain my_schedule desc="Exchange Daily FULL Backup"
         action=command objects="c:\excfull.cmd" priority=2
         starttime=21:00 duration=15 duru=minutes period=1
         perunits=day dayofweek=any

For details, refer to the chapter in the User's Guide that
discusses how to set up automated scheduling.

As far as the "file" data that you backed up by mistake, if you
do not want it at all, you can us the "DELETE FILESPACE"
TSM Server command to remove the data from the server.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/18/2005
07:43:17 AM:

> Aloha,
>
> The Exchange Server backuped normal data and only normal data, it
> does not even touch the
> exchange Database.
> When i login the server and start the backup manually it works fine.
> ( i just sad this, to show
> that the normal installation is OK, i know that the schedule has not
> much in common with this)
>
> This is the output of the command q occ:
>
> SYSEXCHANGE     Bkup     SYS\Erste Speichergruppe        1
> AUTOLTO_POOL          15     11,481.66     11,481.6
> SYSEXCHANGE     Bkup     SYS\Erste Speichergruppe        1
> DBDATA                 5      3,708.89      3,708.89
> SYSEXCHANGE     Bkup     \\sys\c$               2     AUTOLTO_POOL
> 44,771      6,075.54      5,922.78
> SYSEXCHANGE     Bkup     \\sys\c$              2     DBDATA
> 146         22.73         22.73
> SYSEXCHANGE     Bkup     SYSTEM OBJECT               4
> AUTOLTO_POOL       2,074        199.55        199.55
> SYSEXCHANGE     Bkup     SYSTEM OBJECT               4     DBDATA
> 4,149        409.17        409.17
>
> How does it do this? The dsm.opt file likes like that and is
> associated with the right schedule.
>
> NODename          SYSexchange
> CLUSTERnode       no
> COMPRESSIon       On
> PASSWORDAccess    Generate
> COMMMethod        TCPip
> TCPPort           1500
> TCPServeraddress  192.168.10.8
> TCPWindowsize     63
> TCPBuffSize       32
> SCHEDMODE         Polling
> TCPCLIENTPORT     1503
> INCLUDE    "SYS\Erste Speichergruppe\...\*"
>
> The TCPCLIENTPORT is the same as on the TSM Server.
> To normal delete the date, i would have to set the data expired ...
> how do i do that now ??
> The TSM-Server backups only the normal date .. on schedule why ? ...
> what do i miss again ??
>
> For the technical site:
>           Platform: TDP MSExchg
>    Client OS Level: 5.00
>     Client Version: Version 5, Release 2, Level 2.10
>         TSM SERVER: Storage Management Server for Linux/i386 -
> Version 5, Release 2, Level 2.5
>
>
>
> with regards
> Mark Strasheim