Hello all,
Since a few days, i have three clients with missed schedule.
To make a debug, I've tried a telnet from the server to the client in
the tcp port 1501 and the connection is established.
I've also tried a "def clientaction client" and in the actlog i have a
lot of this entries:
25.01.20
You need to take a good look at the scheduler session log, for
starters (and also check the dsmerror.log and dsmwebcl.log). A
common cause for missed schedules is that the previously started task
is still running, as for example where a client backup gets longer
and longer each day due to growth.
I *may* have screwed up the math here -- but IF you can drive some number of
LTO4 drives at maximum compression and full rated write speed of 350 MB/Second
for the 800GB per tape, I get 1,322 tape drive days or 3.6 tape drive years for
the first pass. Not counting mount/dismount time. 1,322 tape
Time for me to ask a stupid question.
I have lots of them...
TSM Server 5.4.3 OS is AIX 5.3
I am trying to utilize the Hourly Monitor in Daily Operational Reporting
to notify me if I reach 90% of maxscratch.
Before I went to the reporting utility, I tried to write a select query.
Only pieces of
Earlier today I attempted to create a backup set for a very large
file server. The process generating the backup set was running at
the same time as our daily inventory expiration process. As far as
I can tell, all went well until inventory expiration got to the system
for which the backup set was
Hi ADSMers!
We have problem with backing up one storage (volume) on NAS server
(FAS270). Our TSM is 5.2.9.0 (and yes, out of support).
We have 2 netapp, 2 library (only 1 is used) and 2 physical SAN with
muchos VSAN on them. Our netapp is connected using FC to different
VSAN (fail over). Netapp i
Hello all,
Jeff, Pete, Hans, Charles, Ben & Richard
Thanks for all of your Responses!
We are going try the "memoryefficient backup= yes" in the dsm.sys file
suggestion first to see if that
clears up the issue.
Tim
Nast, Jeff P. wrote:
Or add "memoryefficientbackup yes" in the dsm.sys file.
That's exactly what the problem was. Since we only ever had a 3494 library
before, we never needed the TSM Device driver so it was never installed
before. After installing it, the library was recognized and I was able to
define it to TSM.
John
-John,
-If I'm not mistaken, the TSM device driver m
Deduplication is to be added into TSM 6.1 currently due for release in
4Q '08 according to what
I read. Anyone know of presentation thats available.
regards
Kauffman, Tom wrote:
I *may* have screwed up the math here -- but IF you can drive some number of
LTO4 drives at maximum compression and
None of the 5.1 and 5.2 BA clients are "formally" supported by IBM anymore,
so you should plan on upgrading them soon.
But they all continue to work just fine with 5.4 servers.
(Storage Agents for Lan-Free are the only type of client you need to worry
about.)
On 1/24/08, Mladen Portak <[EMAIL PR
Ooooh, what an INTERESTING problem to have!
I'm not aware of any VTL that even approaches being able to handle this
amount of data.
It's a pretty daunting problem. If you take LTO4 (at 800 GB per cart),
assume with compression and some un-reclaimed space you'll average about 1
TB of valid data pe
.
I assume you have seen this already for the SL500 library:
"StorageTek SL500 and Sun StorEdge L500 Libraries Configuration
Information for IBM Tivoli Storage Manager Server"
http://www-1.ibm.com/support/docview.wss?rs=663&uid=swg21193518
Roger Deschner University of Illinois at Chicago
12 matches
Mail list logo
