ADSM-L

strange expiration process

2015-10-04 17:27:38
Subject: strange expiration process
From: Phillip Guan <pguan AT SANSIA DOT NET>
To: <ADSM-L AT VM.MARIST DOT EDU>
> Hi all,
>
> We have a admin schedule to run at 08:00 each day, after the
> expire_inventory schedule started and finished, there is a EXPIRATION
> running again. We didn't start the EXPIRATION process, canl normal client
> start it? Is it related with "SET MAXSCHEDSESSIONS"?
> Thanks in advance for your help.
>
> tsm: UTSLC01>q event * type=a
>
> Scheduled Start          Actual Start             Schedule Name     Status
> --------------------     --------------------     -------------     ------
--
> -
> -
> 09/25/00   08:00:00      09/25/00   08:00:11      BACKUP_DEVCO-
> Completed
>                                                    NF
> 09/25/00   08:00:00      09/25/00   08:00:11      BACKUP_VOLHI-
> Completed
>                                                    ST
> 09/25/00   08:00:00      09/25/00   08:00:11      DB_BACKUP
> Completed
> 09/25/00   08:00:00      09/25/00   08:00:10      DEL_VOLHIST
> Completed
> 09/25/00   08:00:00      09/25/00   08:00:10      EXPIRE_INVEN-
> Completed
>                                                    TORY
> 09/25/00   10:00:00      09/25/00   10:00:11      RECLAIM_START
> Completed
> 09/25/00   16:00:00                               RECLAIM_STOP      Future
>
> > q act begintime=hh:mm search=expir
> ========================================================================
> 09/22/00   08:00:27      ANR2750I Starting scheduled command
> EXPIRE_INVENTORY (
>                           expire inventory ).
> 09/22/00   08:00:27      ANR2017I Administrator ADMIN issued command:
EXPIRE
>                           INVENTORY
> 09/22/00   08:00:27      ANR0984I Process 40 for EXPIRE INVENTORY started
in
> the
>                           BACKGROUND at 08:00:27.
> 09/22/00   08:00:27      ANR0811I Inventory client file expiration started
> as
>                           process 40.
> 09/22/00   08:00:27      ANR2756I Scheduled command EXPIRE_INVENTORY
started
>                           successfully.
> 09/22/00   08:03:42      ANR0812I Inventory file expiration process 40
> completed:
>                           examined 34605 objects, deleting 4637 backup
> objects, 0
>                           archive objects, 0 DB backup volumes, and 0
> recovery plan
>                           files. 0 errors were encountered.
> 09/22/00   08:03:42      ANR0987I Process 40 for EXPIRE INVENTORY running
in
> the
>                           BACKGROUND processed 4637 items with a
completion
> state
>                           of SUCCESS at 08:03:42.
> 09/22/00   12:23:45      ANR0984I Process 42 for EXPIRATION started in the
>                           BACKGROUND at 12:23:45.
> 09/22/00   12:23:45      ANR0811I Inventory client file expiration started
> as
>                           process 42.
> 09/22/00   13:28:17      ANR0812I Inventory file expiration process 42
> completed:
>                           examined 348513 objects, deleting 317996 backup
> objects,
>                           0 archive objects, 0 DB backup volumes, and 0
> recovery
>                           plan files. 0 errors were encountered.
> 09/22/00   13:28:17      ANR0987I Process 42 for EXPIRATION running in the
>                           BACKGROUND processed 317996 items with a
> completion state
>                           of SUCCESS at 13:28:17.
> ===================================================================
> Best regards,
> Phillip Guan
> Sansia System Solutions
> 3333 Bowers Avenue, Suite 239
> Santa Clara, CA 95054
> Voice: 408.844.8808
> Fax: 408.844.9801
<Prev in Thread] Current Thread [Next in Thread>