It's available !
2012/11/27 Remco Post r.p...@plcs.nl
24 hours, not 24 minutes... be more patient :)
On 27 nov. 2012, at 16:34, Dolinski, Peter S dolin...@u.washington.edu
wrote:
I don't see any TSM6.4 folder there.
Regards,
Peter
(206) 616-0787
-Original
Robert,
This latest information makes me wonder: What exactly is making you think
that directories are not being bound to the correct management class? So
far, we have not changed anything; but we have demonstrated that TSM is
indeed binding directories correctly to MGLAW.
Notes:
1. With
I think q actlog begindate=today-ndays msgno=4968 is more efficient.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, November 27, 2012 5:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Who is performing Client
Hello all,
I started the installation of TSM Client version 6.4 on one of our new Windows
Server 2012 servers and went to do other things while waiting on the
installation to finish.
When I went back to the server after about ~5 minutes I realized that the TSM
Client installation hade
You could start by getting a list of nodes that are set to either
COMPRESSION=CLIENT or YES and those with DEDUPLICATION=CLIENTORSERVER. The
default is SERVERONLY. Those would be good candidates to start with. You
can't do client-side dedup without setting the node attribute.
Bill
When the pin is
Thanks for all the replies. The PVU table for this appliance is at this URL,
but it does not describe which client is needed. I finally received an IBM
verified answer on this: only need the TSM BA client; no need for the TSM for
DB product.
Anyone doing non-TSM replication to their DR site, e.g. ProcTier IP
replication? If so, I would be interested in talking to you about how you do
DR recovery, especially how you sync up what tapes got replicated vs what your
recovered TSM DB knows.
David Ehresman
University of Louisville
I had heard that a late 6.3 version client would force a reboot, apparently
following the prerequisite MS packages.
A co-worker had installed 6.3.x on a file server (Win Server 2008) and didn't
know it was going to boot while he went for a coffee refill during the install.
He had several
I have had reboot requests when upgrading Windows servers. I circumvent them
by copying dscenu.txt from the install directory to the baclient directory.
Jim Schneider
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Maurice van 't Loo
Sent:
Thank you all for your sage advice.
I am able to find the servers that are using compression, unfortunately though,
some of my client Admins have let it slip that they are not always using
compression when they are setting up encryption, despite our best efforts to
guide them that way.
Anyone
Also 6.3 clients can cause a reboot during installation. I'm not sure why.
I see it with approx. 1 of 10 installs where the prerequisite needs to be
installed om servers who are in use. Never seen the reboot on new and clean
windows installs, so I assume it has something to do with other software
I am not aware of any way to detect client based encryption via a server-based
query. However, you can see this from a client-side CLI query (DSMC Q BACKUP),
so there must be information somewhere that reflects this.
For anyone considering SUR pricing (capacity-based), you might consider
Hi, David.
You can create a replication statistics file from the PTManager
Replication menu. Open that with Open/ApacheOpen/LibreOffice Calc,
and compare source time for last sync point against the
last_write_date from the VOLUMES table in TSM. Any volumes with
last_write_date later than the
13 matches
Mail list logo
