I've installed operational report on my workstation and configured as
following.
When it was first installed , it would be default use
http://computer/tsmreptweb, but like wise, when I clicked on it, i would
get Page not found.
Anyhow, I configured as below.
Web site virtual directory
C:\PROGRA
I wouldn't say expiration running over 24 hours a cause for alarm per say.
I have seen expiration running over 10 days. This occurred when TSM server
was upgraded to address expiration issue with Windows system objects. Few
years back.
That being said, I would examine past actlog to see if any i
I agree with Richard - look at subfile backups. They have the most
potential for reducing your bandwidth. Also enable compression if
you haven't already done so, and use 'compressalways yes' to avoid
retransmissions in the event that compression expands a file (rare,
but it can happen). OS knob
Orin,
OK, so it's not the same box.
I would still try a move nodedata to a disk storage pool for the purpose
of eliminating the tape and drive performance. Depending on the
occupancy of the TDP node, this could take some time.
I assume that you have installed the same version of Baclient and TDP
If you suspect any corruption to your TSM database, I can't think of a
better first step than to call TSM Support and work with someone there to
isolate the issue. There are switches to the AUDIT DB command that can
greatly reduce the running time, but you have to work through with Support
to iden
On Nov 3, 2006, at 11:21 AM, Murugan, Palani wrote:
...
I want to know how to configure the schedules and option file so that
less data is sent in each packet therefore reducing the bandwidth
usage
but prolonging the backup it's self.
You can "de-tune" the client by doing things like setting a
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
RODOLFICH, NICHOLAS
> I trying to configure Operational Reporting to generate reports
>that land in a particular directory which is the publish location for a
>web server running on the Operational Reporting server. I have s
Hello,
TSM 5.1.6.2 running on AIX 5.1 ML04
I have 3 LTO2 volumes, which belong to a copypool and they currently are in
vault state. Pct Util on 2 of the volumes is 0 and 1 of them is 0.1. When I
query contents on any of these 3 volumes I don't get anything on them.
I would like to use these
I trying to configure Operational Reporting to generate reports
that land in a particular directory which is the publish location for a
web server running on the Operational Reporting server. I have selected
the URL option for the report. When I check the "Create web page with
summary infor
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Orin Rehorst
>Whoa. I left a big detail out. This is a restore to a temporary
Exchange
>server to recover a lost inbox.
>
>I copied a big file between the TSM server and target. It went quickly,
>so I don't think it is a network /
Whoa. I left a big detail out. This is a restore to a temporary Exchange
server to recover a lost inbox.
I copied a big file between the TSM server and target. It went quickly,
so I don't think it is a network / NIC issue.
TIA
Orin Rehorst
-Original Message-
From: Orin Rehorst
Sent: Fri
James,
We did just recently upgrade to TSM 5.3 level 3.1. My lslpp shows the
server at 5.3.3.1.
I will look into the APAR. Thanks.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
James Choate
Sent: Friday, November 03, 2006 11:28 AM
To: ADSM-L@VM
Hi all
I need to configure 3 windows nodes for Incremental backup which is from
site A to a site B where the TSM server is present through WAN.
Since Bandwidth is a constraint through WAN .
I want to know how to configure the schedules and option file so that
less data is sent in eac
I think you probably need to adopt a process of elimination.
Firstly, you say that it backs up at 8MBps. You don't mention whether
you have 100fdx or GB NIC, but at 100fdx this throughput is OK.
Next, are you restoring back to the same server that you have backed up
from.
If so, this more or less
George,
What version of TSM are you running. You said 5.3.?
Have you recently upgraded your TSM server?
We recently ran into a problem with expiration. We were on version
5.3.1.0.
TSM support recommended we upgrade to 5.3.4.0.
Snippet from TSM support
APAR IC46523 about similar behavior
We are trying to restore a filesystem on an Solaris server and are
experiencing the following error messages, over and over:
11/2/2006 6:10:50 PM ANRD afcputil.c(1456): ThreadId Volume 17990 is
not defined for pool -2.
I did some digging and the only related hit I found on the ITSM site
refer
George -
Moving data around within the TSM server storage pools has no effect
upon retention policies. A policy change (retention or versions
reduction could result in a lot of data expiring: your system change
log should reflect such. Or it may simply be the result of an
historic glut of data
To Whom It May Concern:
Starting two days ago our daily inventory expiration job began ran over
24 hours. Previously it ran for 2-4 hours. The number of objects
processed was anywhere from 30,000-700,000 but usually was in the
250,000 range. Now it is processing 4,000,000 objects in about 24 hours
It may be worth turning accounting on, and checking the accounting log
to see where the delay actually resides. Then focusing your attention on
certain components of the infrastructure.
_
Ian Smith
SAN/TSM Specialist
-Original Message-
From: ADSM: Dist Stor
Had a similar problem with our TDP for exchange..I would start looking
at your network adapter. Check duplex settings on adapter.Would stay
away from auto-negotiate...Make sure adapter duplex settings are
consistent with switch port speed and duplex settings...if everything
looks good there, run d
Here are some things you could consider;
http://tsmwiki.com/tsmwiki/RestorePerformance
Matt.
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of Orin Rehorst
> Sent: 03 November 2006 15:03
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Sloo
The system repeats this cycle. It restores about 30 MB in 1 minute 45
seconds. Then "Waiting for TSM server" appears on the client for about
10 seconds.
The restore process initially timed out after 80 MB until I bumped the
dsmserv.opt parms up (commitimeout to 600 and idletimeout to 45).
TIA
Or
On Friday 03 November 2006 14:55, Orin Rehorst wrote:
> TDP for Exchange backs up at 8 MB per second.
>
> It restores at 8 MB in 56 seconds!
>
> What may be wrong?
Maybe the SAN
Maybe the LAN
Maybe the TSM server version
Maybe the TSM client version
Maybe the tape library
Maybe the disk pool
TDP for Exchange backs up at 8 MB per second.
It restores at 8 MB in 56 seconds!
What may be wrong?
Environment: OS Win2003, TSM 5.3.2, IBM tape library 3583 LTO 1.
TIA
Orin Rehorst
Hi Dave,
maybe that helps you also:
http://www.redbooks.ibm.com/redbooks/pdfs/sg246363.pdf
Performance and Tuning Guide DS4000 Family
Then Chapter 5, tuning with typical application
5.4 IBM Tivoli Storage Manager
Timo
Dave Canan schrieb:
For a database LUN, I would choose a segme
25 matches
Mail list logo
