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
auto-migration.
What the heck is going on. None of my
This is getting even more bizarre - now it shows 47% utilized and 100%
Migratable? All of my other 6.x server show both of these numbers
approximately the same, not such wide swings and crazy numbers.
Sounds like some kind of bug due to the conversion from 5.5 to 6.2.3.100 -
anyone have any
Hi Everyone,
we had a power issues and few vtl were went down, now it has been
powered up, but we are not able to login to vtl console, we checked
the vtl servivces it is running.
any one came across this issue earlier.
regards
Yuvaraj
We have a script used for scheduling backups. It defines a
schedule and then defines an association between the schedule
and a node. We recently started trying to use this script with
a TSM server that obtains policy domain definitions from a
configuration manager. The schedule has to be defined
The configuration refresh is asynchronous in both cases.
Mark Haye (马克海), IBM TSM Server Development, mark.h...@us.ibm.com,
8/321-4403, (520)799-4403, 0N6/9062-2, Tucson
Professional programmer. Closed source. Do not attempt.
ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 05/07/2012
Hi,
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
