Re: strange expiration process
Hi Richard and Maria, Thanks for your info. I believe I should set it EXPInterval to 0 to eliminate the problem. Phillip tsm: UTSLC01>q option Server Option Option Setting Server Option Option Setting - - --- - CommTimeOut 500 IdleTimeOut 15 BufPoolSize 2048 LogPoolSize 512 DateFormat1 (mm/dd/) TimeFormat1 (hh:mm:ss) NumberFormat 1 (1,000.00) MessageFormat 1 Language en_USMaxSessions 25 ExpInterval 24 ExpQuiet No EventServerLoggi- Yes MirrorRead DB Normal ng MirrorRead LOGNormal MirrorWrite DB Sequential MirrorWrite LOG Parallel TxnGroupMax 40 MoveBatchSize 40 MoveSizeThresh500 StatusMsgCnt 10 RestoreInterval 1,440 UseLargeBuffers Yes DisableScheds No NOBUFPREfetch No AuditStorage Yes REQSYSauthoutfile Yes SELFTUNEBUFpools- No ize SELFTUNETXNsize No DBPAGEShadow No DBPAGESHADOWFile dbpgshdw.bdt QueryAuth None LogWarnFullPerCe- 90 ThroughPutDataTh- 0 nt reshold ThroughPutTimeTh- 0 reshold TCPPort 1500 HTTPPort 1580 HTTPSPort 1543 TCPWindowsize 0 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Sims Sent: Monday, September 25, 2000 12:26 PM To: [EMAIL PROTECTED] Subject: Re: strange expiration process >We didn't set the EXPInterval, I think it is 0, am I right? The Force is not that strong in this advisor, Phillip: you'll have to do a Query OPTions in your server and tell me. According to the server Admin Ref, the default is 24 (hours) these days. Richard
Re: strange expiration process
>We didn't set the EXPInterval, I think it is 0, am I right? The Force is not that strong in this advisor, Phillip: you'll have to do a Query OPTions in your server and tell me. According to the server Admin Ref, the default is 24 (hours) these days. Richard
Re: strange expiration process
Hi Richard, We didn't set the EXPInterval, I think it is 0, am I right? Phillip -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Sims Sent: Monday, September 25, 2000 11:53 AM To: [EMAIL PROTECTED] Subject: Re: strange expiration process >there is a EXPIRATION running again. We didn't start the EXPIRATION process But what about your EXPInterval server option? Richard Sims, BU
Re: strange expiration process
You need to define the server option EXPINTERVAL to 0 A value of 0 means that expiration must be started with the EXPIRE INVENTORY command. The default is 24. otherwise the expiration will start every 24 hours after the server is initialized. Regards Maria - Original Message - From: Phillip Guan <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 25, 2000 8:35 PM Subject: strange expiration process > 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 > Bowers Avenue, Suite 239 > Santa Clara, CA 95054 > Voice: 408.844.8808 > Fax: 408.844.9801
Re: strange expiration process
>there is a EXPIRATION running again. We didn't start the EXPIRATION process But what about your EXPInterval server option? Richard Sims, BU
strange expiration process
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 Bowers Avenue, Suite 239 Santa Clara, CA 95054 Voice: 408.844.8808 Fax: 408.844.9801
