Probably a few months later, any how
Have you tried increasing the resources on your expire inventory command?
Secondly I'd advise against the upgrade of TSM 6.1.3 to 6.1.4. Too many bugs.
I would advise going straight to TSM6.2.1
Pretty stable so far. And the upgrade process is not that bad as well compared
to doing an upgrade from TSM5.5 to TSM6.1
Zoltan Forray/AC/VCU wrote:
> No, you didn't miss any responses. I haven't seen any, either.
>
> It did finally finish - after running for 7-days. I guess it will take
> many such passes to catch up since obviously it can only run
> one-at-a-time.
>
>
>
> From:
> "Clark, Margaret" <MClark < at > SDDPC.ORG>
> To:
> ADSM-L < at > VM.MARIST.EDU
> Date:
> 08/25/2010 02:50 PM
> Subject:
> Re: [ADSM-L] Expiration question
> Sent by:
> "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>
>
>
>
> A bit late, but I don't recall any previous responses to this... It will
> do no good to cancel a running expiration process. When you start again,
> expiration picks up exactly where it left off. Trying to cancel it just
> prolongs the agony.
> No idea about the retries, sorry.
> - Margaret Clark
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf
> Of
> Zoltan Forray/AC/VCU
> Sent: Monday, August 23, 2010 7:32 AM
> To: ADSM-L < at > VM.MARIST.EDU
> Subject: [ADSM-L] Expiration question
>
> I have 2-issues with expiration processing.
>
> First, on my 5.5.4.2 server - we stopped expiration for more than a week,
> to perform recovery of a large SAN failure.
>
> Now, expiration has been running since 08/17 and still running. Expired
> over 24M objects out of 29M examined. Didn't know if I should be
> concerned. It seems to be working OK and the numbers keep changing so it
> isn't stuck. Didn't know if I should fully cancel it (vs cancel
> expiration) and restart or just leave it along. Never had an expire run
> so long!
>
> Second, I am mildly concerned about the expiration processing/messages
> from my 6.1.3.4 server:
>
> 355 Expiration Processed 69 nodes, examined 734917 objects,
> deleting 733029 backup objects, 0 archive objects, 0 DB backup volumes, 0
> recovery plan files; 1087 objects have been retried and 801 errors
> encountered.
>
> Why the errors and so many? I don't recall any errors from expiration
> from any of the 5.5.x servers? What about the "retried"? Retried what?
>
>
>
> Speaking of 6.1, anyone have any issues upgrading 6.1.3.x to 6.1.4.1? I
> realize there are some big changes in 6.1.4.x and am concerned about
> effecting my only 6.1 production server but I am seeing a lot of problems
> purportedly fixed in 6.1.4.1.
>
> I was never able to upgrade a test 6.1.x server to 6.2.x. Things got so
> farged up I had to have it wiped and rebuilt (couldn't upgrade to 6.2 and
> couldn't remove it successfully).
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray < at > vcu.edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
+----------------------------------------------------------------------
|This was sent by rennad AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
|
