he STGPOOL to see what
happens.
Best Regards,
=Adrian=
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Tailor, Mahesh C.
Sent: 09 October 2013 15:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] File Pool
Rick,
We predefine all our
or Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Wednesday, October 09, 2013 9:55 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] File Pool
Rick,
This is a FILE pool not a library. When a new volume is defined, I don't ever
see SCRATCH status as Yes.
For
T.EDU
Subject: Re: [ADSM-L] File Pool
Hi,
check q vol f=d to see if it is in rw access.
if it is different then rw, you can use update vol acc=readw.
I also would check actl to see how these vols have been processed/used by TSM
Thank you
Chavdar
On 10/9/2013 00:13, Tailor, Mahesh C. wrote:
>
: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] File Pool
Hi,
check q vol f=d to see if it is in rw access.
if it is different then rw, you can use update vol acc=readw.
I also would check actl to see how these vols have been processed/used by TSM
Thank you
Chavdar
On 10/9/2013 00:13, Tailor, Mahesh C
13, Tailor, Mahesh C. wrote:
> Hello.
>
> TSM 6.3.2.200 on AIX 7.1 fp6
>
> We have a filepool that has 276 (214GB) volumes defined for a total of approx
> 60TB. The occupancy is as follows.
>
> select sum(physical_mb) from occupancy
>
Hello.
TSM 6.3.2.200 on AIX 7.1 fp6
We have a filepool that has 276 (214GB) volumes defined for a total of approx
60TB. The occupancy is as follows.
select sum(physical_mb) from occupancy
Unnamed[1]
--
45079209.31
There are/were a bunch of APAR's with backupset restores failures. Is one of
them the cause of this failure?
http://www-01.ibm.com/support/docview.wss?uid=swg21426379
From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Andrew
Raibeck [sto
: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Tuesday, November 27, 2012 10:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] netezza nzbackup connector for TSM
What I have been told by the IBM partner is that in addition to the TSM
connector that is
hat you refer to the
greatest $ amt of the 2.
Thanks,
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Tailor, Mahesh C.
Sent: Monday, 26 November, 2012 5:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: netezza nzbackup connector for TSM
Hello.
On
Hello.
On a similar thread: we are in the process of acquiring Netezza and will need
to back it up to TSM. We were told of the TSM Connector. In trying to make
sure we are in TSM license compliance, we were told that we would need to
license both the TSM for BA client and the TSM for DB clien
This is from TSM L2 supportbottom line, restart TSM. No attempt to figure
out why I cannot define the drives/paths even though AIX sees the drives
through itdt.
=== SNIP ===
itdt -f /dev/smc0 inventory >inv.out
from inv.out, you can see all drives ( at beginning of the output ) which are
Drew,
Thanks for the reply.
- Yes, this is happening with all drives. The RMT1 was just and example that
the drives are accessible.
- We are adding drives one at a time having to go through this process. At one
time we had add sixty drives discovered at the AIX layer (rmt0-rmt59), started
up
Hello.
I have a PMR on this, but not making much progress on it so thought I would
send this out on the User List to see if anyone else encountered this issue and
can suggest a fix.
Here's what I have:
TSM 6.2.3.100
AIX 7.1 (oslevel: 7100-00-04-1140)
IBM FC 5729 8-Gbps FC adapters
SAN Switch:
Hopefully, this does not post several time...if it does apologies in advance.
(My email address changed.)
Assuming you have the TS1130's in a 3584: you can create virtual libraries and
assign slots and drives to each library. We did this to avoid having a single
point of failure in the TSM l
14 matches
Mail list logo
