Re: [ADSM-L] Update Schedule failed
2013-05-02 10:45:02
The dsmsched.log only shows the regular server incremental backup scheduled at
01:59. The TDPschedule log had 'no schedule returned'. Now that I have
updated the schedules with 'exp=never' and restarted the services I see the
scheduled start times on all three servers - 22:00 for incrementals, 17:00 for
the full that will run tonight. I've been puzzling over this for about 2 weeks
and never noticed that backups were running with expired schedules.
My current Exchange server schedules are
tsm: CH2UPTSM3>q ev * * n=ch2wpexch*
Scheduled Start Actual Start Schedule Name Node Name
Status
-------------------- -------------------- -------------
------------- ---------
05/02/13 01:59:00 05/02/13 01:59:19 WIN_0200 CH2WPEXCH1
Completed
05/02/13 01:59:00 05/02/13 01:59:20 WIN_0200 CH2WPEXCH2
Completed
05/02/13 01:59:00 05/02/13 01:59:21 WIN_0200 CH2WPEXCH3
Completed
05/02/13 17:00:00 FULL
CH2WPEXCH3-E- Future
XCH
05/02/13 22:00:00 INCR
CH2WPEXCH1-E- Future
XCH
05/02/13 22:00:00 INCR
CH2WPEXCH2-E- Future
XCH
Tomorrow's results will let me know if the fix worked.
Thanks again,
Jim Schneider
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rick Harderwijk
Sent: Thursday, May 02, 2013 9:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Update Schedule failed
I must agree with Jim on the fact that it's a bit strange backups where still
running even though the schedule has expired. The backups must be managed by a
different schedule than the one Jim was trying to edit. The dsmsched.log should
be able to provide more info as well.
Cheers
Rick
On May 2, 2013 4:02 PM, "Carlo Zanelli" <carlo.zanelli AT gmail DOT com> wrote:
> You are welcome,
>
> Bear in mind that starting from now probably your will have two daily
> backup jobs.
> To look at all the scheduled associated for that node you can use
>
> q sched * * no=CH2WPEXCH1-EXCH
>
> Have a nice day.
>
>
> On Thu, May 2, 2013 at 2:48 PM, Schneider, Jim <jschneider AT ussco DOT com>
> wrote:
>
> > Carlo,
> >
> > Thanks - I'd missed that, and have updated all Exchange schedules (3
> full,
> > 3 incremental) to non-expiring. I don't understand show the backups
> > have been running consistently with expired schedules. I'll check
> > tomorrow to see if this fixed the problem.
> >
> > Thank you,
> > Jim Schneider
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of Carlo Zanelli
> > Sent: Thursday, May 02, 2013 8:38 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Update Schedule failed
> >
> > Jim,
> >
> > it looks like this schedule is not more used.
> >
> > Expiration: 02/17/13 23:59:59
> >
> > Hope this helps.
> >
> >
> > On Thu, May 2, 2013 at 2:29 PM, Schneider, Jim
> > <jschneider AT ussco DOT com>
> > wrote:
> >
> > > TSM 6.2.2.0 on AIX 6.1
> > > TSM 6.3.0.0 on Windows 2008 R2
> > >
> > > My attempt to change a schedule start time has failed. I have a
> > > cmd schedule that runs Exchange backups. Originally scheduled for
> > > 17:00 I find I cannot change the start time to 22:00.
> > >
> > > These commands show that the schedule time was changed to 22:00.
> > > update schedule exch1 incr scheds=e startt=22:00 update schedule
> > > exch1 incr startt=22:00
> > >
> > > It looks like it should work.
> > >
> > > >q sched exch1 incr f=d
> > >
> > > Policy Domain Name: EXCH1
> > > Schedule Name: INCR
> > > Description: daily incremental exchange backup
> > > Action: Command
> > > Subaction:
> > > Options:
> > > Objects: c:\excincr.cmd
> > > Priority: 5
> > > Start Date/Time: 01/14/12 22:00:00
> > > Duration: 1 Hour(s)
> > > Schedule Style: Enhanced
> > > Period:
> > > Day of Week: Sun,Mon,Tue,Thu,Fri,Sat
> > > Month: Any
> > > Day of Month: Any
> > > Week of Month: Any
> > > Expiration: 02/17/13 23:59:59
> > > Last Update by (administrator): SCHNEIJ
> > > Last Update Date/Time: 04/30/13 09:24:48
> > > Managing profile:
> > >
> > > >q assoc exch1 incr
> > >
> > > Policy Domain Name Schedule Name
> > > Associated Nodes
> > > ------------------------------ ------------------------------
> > > ----------------
> > > EXCH1 INCR
> > > CH2WPEXCH1-EXCH
> > >
> > > >q proxy target=ch2wpexch1
> > >
> > > Target Node Agent Node
> > > --------------- ----------
> > > CH2WPEXCH1-EXCH CH2WPEXCH1
> > >
> > > But the darn schedule still runs at 17:00, the previous start time.
> > > I have restarted the acceptor, scheduler, and TDP for Exchange
> > > services on the client.
> > >
> > > What am I doing wrong/what have I missed?
> > >
> > > Thank you in advance,
> > > Jim Schneider
> > >
> > > ******************************************************************
> > > **** Information contained in this e-mail message and in any
> > > attachments thereto is confidential. If you are not the intended
> > > recipient, please destroy this message, delete any copies held on
> > > your systems, notify the sender immediately, and refrain from
> > > using or disclosing all or any part of its content to any other
> > > person.
> > >
> >
> >
> >
> > --
> > Eng. Carlo Zanelli
> > EMC Ireland, Co. Cork
> > Mobile: +353-(0)864569250, +39-3491419132
> >
> > ********************************************************************
> > ** Information contained in this e-mail message and in any
> > attachments thereto is confidential. If you are not the intended
> > recipient, please destroy this message, delete any copies held on
> > your systems, notify the sender immediately, and refrain from using
> > or disclosing all or any part
> of
> > its content to any other person.
> >
>
>
>
> --
> Eng. Carlo Zanelli
> EMC Ireland, Co. Cork
> Mobile: +353-(0)864569250, +39-3491419132
>
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [ADSM-L] TSM server 6.3 issue(ANR0171I, ANR0162W, ANR1820E-error code, pragati
- Re: [ADSM-L] TSM server 6.3 issue(ANR0171I, ANR0162W, ANR1820E-error code, gopi muppidi
- [ADSM-L] Update Schedule failed, Schneider, Jim
- Re: [ADSM-L] Update Schedule failed, Carlo Zanelli
- Re: [ADSM-L] Update Schedule failed, Schneider, Jim
- Re: [ADSM-L] Update Schedule failed, Carlo Zanelli
- Re: [ADSM-L] Update Schedule failed, Rick Harderwijk
- Re: [ADSM-L] Update Schedule failed,
Schneider, Jim <=
- Re: [ADSM-L] Update Schedule failed - resolved, Schneider, Jim
- Re: [ADSM-L] Update Schedule failed - resolved, Carlo Zanelli
- Re: [ADSM-L] Update Schedule failed, gopi muppidi
[ADSM-L] TSM server 6.3 issue(ANR0171I, ANR0162W, ANR1820E-error code, pragati
Re: [ADSM-L] TSM server 6.3 issue(ANR0171I, ANR0162W, ANR1820E-error code, Zoltan Forray
|
|
|