Re: [ADSM-L] Update Schedule failed
2013-05-02 09:49:37
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.
|
<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
|
|
|