Actually applying workaround for Q323602 did not fixed the problem
completely. The problem was the value for SQLBUFFERSIze - I was too greedy
for performance, set it to maximum (4096) and stability suffered. It
worked but after one day of backups started failing from time to time.
Reducing the valu
Am I missing something!?! AFAIK TSM server support for Linux was
introduced in v5.1.5 for x86 only. Even before we had server on VM but
this is actually ADSM 3.1 and still is at the same functionality level.
Linux for S/390 and zSeries has no TSM server (yes, Linux runs on VM and
we can have a serv
For me it sounds more like workaround the lack of HSM client with purely
manual "backup and delete". We can do the same with archive functionality
but should we.
I do not want to be the HSM "kernel extension" recalling back the files
"migrated" in this manner :-((( It would be some sort of "restore
There were some permission restore issues at this level, I do not remember
what they were. This level is not going to be supported after 4/15.
Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180
-Original Message-
From: Edgardo Moso [mailto:[EMAIL
Folks,
Based on the Expert advice, I followed all instructions to configure and setup TSM
Backup client for NT cluster server.Then, I moved on to setup Web client in Cluster
environment. As the manual says, I used "DSMCUTIL" to install services and not the
setup wizard. Also, I was cautious in
This is about what I would expect. Eventhough you are using the SAN agent,
you could be still using the IP stack internal to the machine to get the
data from the client to the SAN agent. And, if this is TDP for Exchange or
TDP for SQL, there is even more CPU overhead. Without more information, I
Dear TSMers,
I am using backupsets for remote archiving purposes. As you already now we
state "retention period"
while creating them. Is there a method to put them "pending" state and delete
them under my control after this retention period?
Because i feel that they will expire automatically (
we have
H80 120 nodes
30 gbyte database
300 gbyte per night
SSA disks for stotage
100 gbyte storage pool
2 cpu's 2 gbyte ram
2 100 Mbit ethernet adapters
6 3590 drives in a 3494 lib
---
I think the p630 is an excellent option for a TSM server.
-Original Message-
