hi all,
5.4.1.4 is not the solution (to solve nw performance issue) - our nw
backup is still running about 8h, instead of 2-3h. We got a call open,
just gone up to level 2, and we wait for the recall. IBM hasn't got any
idea until now.
Reading this posting, tt looks like a general problem
On Mar 16, 2008, at 9:51 PM, Avy Wong wrote:
What started my question to ask this forum's expert is suddenly I
was told
that I have to keep track of all the nodes being backed up on tivoli.
I still have to clarify with IBM licensing if this is to do with nodes
currently being backed up on
Richard Thanks...
I did find the following message in the TSM Server log for the clients
that have been failing
with this issue.
ANR0480W for node Sul300 terminated - connection with client severed
03/16/08 04:01:16 ANR0480W Session 73321 for node Sul300 terminated –
connection with -
I thought I'd throw this in too. Baclient ver 5.5 is not explicitly supported
with a 5.3 server.
There are two hotfixes listed for W2k3 clients with VSS errors also. This has
been on list before.
thanks!
lisa
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL
We have a few windows nodes here that have a filespace_type=raw
filesystem. I've never noticed this before and am wondering what that
indicates on a Windows system. Any ideas out there?
--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Services Fx:
This may be a poor man's way of getting the information, but it
works. Do 'q dom' to get the total of registered clients. Than, do
'q node' and scan the list for ones whose last backup date is greater
than '1'.
Keith Arbogast
Indiana University
That should have been 'Days Since Lat Access' greater than '1'. There
is surely a way to do this with a select statement if you have
thousands of clients.
Keith
Hello Paul
I am taking a few guesses here.
A recovery partition.
A dual boot machine and it is an alt os partition
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul
Zarnowski
Sent: Monday, March 17, 2008 11:05 AM
To: ADSM-L@VM.MARIST.EDU
Days Since Last Access is only an indicator that the client has
connected to the server. It does not indicate if any backup data was
actually transferred.
-Bill
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Keith Arbogast
Sent: Monday, March
Hi All,
I wonder, with so many months passing since 5.4 has gone GA, and no
usuable, secure 5.4 client, will IBM be extending support of 5.3?
We are in the process of testing 5.3.5.5, as it fixes the security
issue in dsmcad, and does not have the preformance issues of 5.4.x. And
Len,
Thanks for responding. No, after talking to the user, I've determined this
further information. The D: drive was on an old Compaq RAID-5 disk array,
which failed. The client system is a W2K3 server, and was running TSM
5.1.5.15, which I suspect never supported W2K3. However, the user
My understanding is that RAW refers to an unformatted volume,
particularly in the Windows environment. It will mostly show up with
image backups.
Richard Sims
Yeah, I thought about that, but the TSM server shows that it has over
600,000 files backed up and almost 700GB. So that would seem to indicate
that at some point in time, TSM did not view it as an unformatted volume.
At 12:29 PM 3/17/2008, Richard Sims wrote:
My understanding is that RAW
It sounds like the disk format type might have changed after the failure,
and TSM picked up on this and updated the file space accordingly.
I recommend opening a PMR with IBM support. This needs to go right to
Level 2, and they should be able to help get the file space type
corrected. It would
Andy,
Thanks for responding. I was just coming to the same conclusion. Talking
to the end-user, I discovered that they had not disabled backups after the
disk-array failure. They had also initiated a restore and restored 94 GB
(out of about 700G) before cancelling it. Then, when they
Does anyone know if these issues exist in the 5.5 Clients? It may be
that since 5.5 is GA they will urge us in that direction. I was
planning to go there, but if these kinds of speed and support issues
exist, we may not for some time.
See Ya'
Howard
-Original Message-
From: ADSM:
Steve Roder wrote:
Hi All,
I wonder, with so many months passing since 5.4 has gone GA, and no
usuable, secure 5.4 client, will IBM be extending support of 5.3?
so let's look at that question.
Support means that IBM will fix any problems you have in running the
code. Since apperently,
I will be out of the office starting 03/18/2008 and will not return until
03/24/2008.
I am out of office during this period.
As I have no access to email during this period, please contact the persons
below for urgent server-related matters. You can otherwise contact me at
012-2831882.
IGA SDM
Dave,
it's not only the 5.4 client code! We have to use 5.5-client code and having
the same performance issues.
Client: 5.5.0
Server: 5.4.2
OS: Linux 64-bit
--
Michael Prix
IBM has had several customers reporting this performance issue
after upgrading to level 5.4. APAR IC53531 was
Howard/Paul,
This problem has been reported against the 5.4 AND 5.5 TSM client
levels. It has also been reported against all client platforms EXCEPT
Windows. Paul, I am trying to track down your specific question to see if
this also includes MAC OS 10.x. I believe the answer is yes, but
Steve Roder wrote:
Hi All,
I wonder, with so many months passing since 5.4 has gone GA, and no
usuable, secure 5.4 client, will IBM be extending support of 5.3?
Remco Post [EMAIL PROTECTED] wrote:
so let's look at that question.
Support means that IBM will fix any problems you
Just in case someone else has this problem in the future and searches the
archives of this list, here's the resolution we ended up with. While the
GUI refused to show the backups for the D: drive, the CLI still sees it
just fine and we were able to restore files using the CLI.
So Andy's
What process is it that tells Q DRM which tapes are in vault retrieve
status?
Is it Expiration or Space Reclamation?
The reason I am asking is that we have not had any tapes in vault
retrieve status for a few days.
Regards
Paul Dudley
Senior IT Systems Administrator
ANL IT
Usually it takes both.
Expiration is what causes the %utilization and %reclaimable values for your
tapes to be updated. If you aren't running reclamation, those values won't
change (unless you delete a filespace, that takes effect at once).
When space reclamation kicks in, it will process any
And as to what actually makes a tape change state?
Once an hour TSM runs an internal check. Tapes change from pending to
scratch/empty when their pending period is past and the check is run. You
have no control over it, it depends on the time of day that the TSM Server
was last brought up.
HTH
25 matches
Mail list logo
