Anil,
I fully agree with you that a TSM server acting as a library manager
would have been much easier to implement and maintain, unfortunately
legal and security issues are refraining us to do so ! (plus the fact
that we also plan to dedicate a future partition of the library to some
non-TSM
Pierre,
Many thanks for your valuable help : I tried to open a call by IBM Switzerland
and they could not provide me half of the information you gave me ... Seems
that this kind of operation is not that usual here !
Regarding what you asked in point 1 : yes, no other way to do, as the library
Hello,
if you activate ALMS, then the already defined logical libraries will be
preserved with all information and setups, like size, drives, cartridges
...
How ever you should stop the activities on our TSM Server regarding
libraries.
After activation, which may take 1-3 min per Frame, you
Hi Joseph,
Here too, many thanks for the hints.
But I'm lost now, as both Pierre and yourself are giving me conflictual
opinions on how ALMS will affect the already existing partitions in my library
... On one hand I'm supposed to loose all of the existing setup, and on the
other one
Hi Arnaud,
Josef can be right, as I didn't try to keep any previous configuration during
my tests, making a scratch install.
Anyway, what I've seen during all my testing, is that, if you loose
configuration, you have to rebuild all from scratch...
As there are no configuration backups...
I'm not familiar with celerra, but on Netapp, TSM ignores the snapshot
directories unless they are specifically mapped.
Are you sure the data that is being reported by TSM:q fi and the nas
command are not snapshots? Maybe there is something special about the data
on vol0 that is excluding it?
I keep getting this error when trying to backup a 6 GB (there about)
file:
ANSE ntrc.cpp(928): Received Win32 RC 1450 (0x05aa) from
FileRead(): ReadFile '\\nodename\c$\archives\SUN06082008.TGZ'. Error
desription: Insufficient system resources exist to complete the
requested service.
ADSM QuickFacts has info on this, referring you to IBM Technote 1116532.
Richard Sims
could always try the client option(MEMORYEFFICIENTBACKUP YES)
Might be running out of memory on the local machine.
Jim
- Original Message -
From: Howard Coles [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, June 13, 2008 3:57 PM
Subject: [ADSM-L] TSM Client can't handle
Hello Everyone,
I am having problem with tapes not being dismounted. We have a VTL
and when it tries to replicate to another VTL it fails because a virtual
tape in still in a virtual drive. When I do a Q MO the tape is in the
drive sitting idle. Is there a way to have TSM automatically
Lepre, James wrote:
Hello Everyone,
I am having problem with tapes not being dismounted. We have a VTL
and when it tries to replicate to another VTL it fails because a virtual
tape in still in a virtual drive. When I do a Q MO the tape is in the
drive sitting idle. Is there a way to have
I have seen this when there is not enough space in the server
diskpool...
-Jeff Nast
Senior Systems Administrator
SMDC Health Systems
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Howard Coles
Sent: Friday, June 13, 2008 9:57 AM
To:
Checked that, was my first inclination, as I too have seen that. But,
I've got more than enough room there.
The server shows plenty of storage to handle the received file. I found
the technote previously mentioned, and it does indeed address the
problem.
The box has about 6 GB of RAM free, and
Also, check this which has Microsoft info. This fixed a problem I
encountered last week after an application upgrade on the client
machine - that changed some Windows system parameters.
Sounds very much like yours, message info is nearly identical.
Bruce E. Lowrie
Sr. Infrastructure Analyst
Information Technology Services
Storage Output
*E-Mail: [EMAIL PROTECTED]
*Voice: (989) 496-6404
7 Fax: (989) 496-8232
*Post: 2200 W. Salzburg Rd.
*Post: Mail: CO2200
*Post: Midland, MI 48686-0994
Just to clarify what might be a common misconception:
The RC 1450 is not a typical out of memory error such as when the
application has exceeded 32-bit Windows 2 GB virtual memory limit. Rather,
it indicates that some kernel resource is exhausted, over which TSM has no
control. In some cases,
16 matches
Mail list logo
