Hi Steve,
That status is not quite correct.
IBM has the APIs, that's true. IBM also has them implemented
and working successfully in the lab.
IBM is working directly with NetApp on some special details
about how we support SnapDiff (and NDMP) with CDOT.
And so, at this point, I cannot give a
We have 2 TSM 6.3.5 servers running on zLinux. Is this something we could
leverage?
__
Andrew Galloway
Operational Systems Continuity Analyst
SSC RCMP Technology Directorate
CIO Building C1035
R.C.M.P. Headquarters
1200 Vanier Parkway
Ottawa ON
K1A 0R2
Hi Steve,
No firm diagnosis or solution, but this could be something going on during
snapshot cleanup, when the volumes are being unmounted if you are using the
HOTADD transport. One possibility (but by no means the only one) is:
kb.vmware.com/kb/2010953
One way to try to isolate this is to
NetApp snapdiff support for filers configured to run in c-mode was added
in ONTAP 8.2, so any future TSM client support would
require this version of ONTAP.
As you probably know, ONTAP 8.2 is the last version of ONTAP which will
include legacy 7-mode support, future versions
starting with 8.3
I've been in meetings/training this week about AIX LPM and other stuff related
with LPARS. We got talking about our TSM servers, and the IBM leader mentioned
a presentation given a while ago at a IBM conference about using LARGE PAGES
(16MB) with TSM to prevent lock contention. This is
I am in the process of planning and implementing of IBM TSM 7.1,I need a
documentt that can help me to use it as reference in my planning which
point out all data needed to each backup client as (Name, IP, backup
policy, OS, Archives, Daily change rate, Versions existing, Retention
policy,
We've been using them on RHEL x86_64 via Linux's anonhugepages mechanism
for a while now. I'm not sure that they improve performance but they
certainly haven't hurt anything that I can tell.
On Wed, Mar 11, 2015 at 11:15:30AM +, Rhodes, Richard L. wrote:
I've been in meetings/training this
One last post...
Rocket Servergraph has been expanded to report of lots of stuff other
than TSM including Oracle and Protectier. I'm replacing a poorly
configured Bocada system (ie its not Bocada's fault) with it on one of
my customers, at least I've recommended it but someone has to provide
the
Yep implemented this on my new v6 servers. Seems to work as
advertised. They aren't CPU stressed enough yet to see any real
difference though.
Regards
Steve
Steven Harris
TSM Admin, Canberra Australia.
On 11/03/2015 10:15 PM, Rhodes, Richard L. wrote:
I've been in meetings/training this
We have implemented large pages on our v6 servers (now v7 servers). I agree it
seems to work as suggested by the presentation. It requires some tuning to
begin with to get the ideal number. It does mean that the memory reserved for
large pages is not available for other processes so like so
10 matches
Mail list logo
