data that is locked in a transaction is not migratable. It may even (from what
I see) already be copied to the next stg, but since the transaction isn't
complete yet on writing to disk, it can't be deleted from disk yet. I've seen
this on 5.5 as well.
On 7 mei 2012, at 14:42, Zoltan Forray/AC/VCU wrote:
> Well, it did it again.
> Over the weekend, things got all hung up due to nodes not being able to
> backup to the disk LZ (all the tape drives were busy). Q STG showed 22%
> migratable but 100% utilized so the hi/lo values never kicked in for
> What the heck is going on. None of my other 126.96.36.199 servers behave like
> this. Just this one that was upgraded from 5.5.............
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT 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
> From: Jo Lay <jolay AT US.IBM DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 05/04/2012 05:27 PM
> Subject: Re: [ADSM-L] Upgrading to 6.3: can I restore my 6.2.3 DB
> after installation
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> You will have to install the 6.2.3 first on your 64 bits system and then
> restore DB. Then , upgrade to 6.3.1. Please make sure you save a copy of
> volume history file for 6.2.3.
> We changed format of the volume history file with 6.3. The volume history
> file in 6.3 can not be used to restore DB into 6.2 or 6.1.
> Jo Lay
> Tivoli Storage Products, IBM Software Group
> jolay AT us.ibm DOT com
> Phone: 408-997-7999
Met vriendelijke groeten/Kind Regards,
r.post AT plcs DOT nl
+31 6 248 21 622