Assuming it is in a filling state, check out the Filling section here to see
why a filling tape might not be used
http://people.bu.edu/rbs/ADSM.QuickFacts
-Original Message-
From: ADSM-L@VM.MARIST.EDU [mailto:ADSM-L@VM.MARIST.EDU]
Sent: Monday, June 08, 2015 1:38 PM
To:
That was it, forgot status.
Fixing now.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of white
jeff
Sent: Monday, June 08, 2015 1:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] server out of storage space when really not missing
vmware
Gary
That depends on the volume status.
If FILLING, then it is eligible to be written to. Example a volume in
FILLING status which is 75% utilised has 25% free space. Therefore a
candidate for wring to.
If FULL, the volume was 100% full at one stage. The volume remains in that
state until all
My question here is that 59 out of 195 volumes in the pool are less than 75%
utilized.
Shouldn't tsm fil them before declaring itself out of space?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David
Ehresman
Sent: Monday, June 08, 2015
Tsm server 6.2.5
TDP for vmware 6.4
I have the vmware data pool defined as a sequencial file pool, to facilitate
migration.
However, last night the server claimed it was out of data storage space, but
there is 18% of a 14 tb pool free.
I checked, and the only limit reached was maxscratch.
Is
Maxscratch defines how many scratch volumes you can have in a storagepool.
When you reach maxscratch, assuming you do not have volumes predefined, you are
by definition out of data storage space regardless of how much space is in your
filesystem.
-Original Message-
From: ADSM: Dist
Hi all,
one of my customers has decided to implement User virtual harddisks on his
windows terminal server. All very well, but I only have 2 problems:
- for some reason TSM insists on making a back-up of the mounted VHD’s,
exclude.fs C:\Users\*, specific domain statements (domain C: D: E:) ,
