Shouldn't it be:
upd sched standard 2100_something dur=59 duru=minutes period=1 peru=hours
???
On Nov 19, 2007 11:14 PM, Mcnutt, Larry E. <larry.mcnutt AT timken DOT com>
wrote:
> Avy,
>
> Something like the following is what you could do to change it to run
> hourly. This assumes that it can complete in less than an hour,
> otherwise sometimes you will get a "missed" backup for those times that
> run longer than an hour.
>
> Update schedule standard 2100_something duration=15 durunits=minutes
> perunits=hours
>
> Larry McNutt
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Avy Wong
> Sent: Monday, November 19, 2007 3:57 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: scheduling
>
> Hello,
>
> Can you tell me how to update the schedule to run a backup every
> hour
> ? thanks for your help.
>
> From the client side:
>
> Schedule name: 2100_somename
> Description:
> Schedule Style: Classic
> Action: Incremental
> Options: -subdir=yes
> Objects:
> Priority:5
> Next Execution: 23 Hours and 17 Minutes ( <-- I would like this to
> change
> to 60 minutes )
> Duration: 1Hour
> Period: 1 Day
> Day of Week: Any
> Month:
> Day of Month:
> Week of Month:
> Expire: Never
>
> From the server side:
>
> Policy Domain Name: STANDARD
> Schedule Name: 2100_somename
> Description:
> Action: Incremental
> Options: -subdir=yes
> Objects:
> Priority: 5
> Start Date/Time: 11/19/2007 14:39:41
> Duration: 1 Hour(s) ( <-- this is just the open
> window
> allowed)
> Schedule Style: Classic
> Period: 1 Day(s)
> Day of Week: Any
> Month:
> Day of Month:
> Week of Month:
> Expiration:
> ast Update by (administrator): WONGAV
> Last Update Date/Time: 11/19/2007 14:50:35
> Associated Nodes: SomeNode
> Managing profile:
>
> Avy Wong
> Business Continuity Administrator
> Mohegan Sun
> 1 Mohegan Sun Blvd
> Uncasville, CT 06382
> (860)862-8164
> (cell) (860)961-6976
>
> -----------------------------------------
> This message and any attachments are intended for the individual or
> entity named above. If you are not the intended recipient, please
> do not forward, copy, print, use or disclose this communication to
> others; also please notify the sender by replying to this message,
> and then delete it from your system. The Timken Company / The
> Timken Corporation
--
Warm regards,
Michael Green
|