Has anybody successfully got the v4.1.2 Windows client working with an MSCS
cluster?
When I upgraded the TSM client software on one of our clusters, the Scheduler
services installed with the DSMCUTIL INSTALL /CLUSTERNODE:YES command no longer
start. The problem seems to be to do with the parsing
Tx Nigel
i know this redbook.
but this works only with client version 3.7.X
with client version 4.1.2 the following does'nt work:
-opt.file
clusternode yes
install command:
/group:"Cluster
/clusternode:yes
and the interesting thing is, that ibm wrote in the new readme-file:
if u use /clusternam
With those statements shown below, you shouldn't be getting duplicates.
I'm about out of ideas. It would seems as though a different dsm.opt files
is being used. I would rename (hide) this dsm.opt and see if the client
connects to the server.
On Fri, 5 Jan 2001, Kleynerman, Arthur wrote:
> Clie
How do you achive to use 10 tapes for restore
- do you have 10 different filespaces?
With Regards Stefan Holzwarth
> -Ursprüngliche Nachricht-
> Von: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
> Gesendet am: Freitag, 5. Januar 2001 15:11
> An: [EMAIL PROTECTED]
> Betreff: Re: how to spee
Hello
Do you find the the files that i excluded in dsm.opt correct for a normal
File / Print Server??
exclude.file *:\pagefile.sys
exclude.file *:\WINNT\system32\CPL.CFG
exclude.file *:\...\SYSTEM32\CONFIG\default
exclude.file *:\...\SYSTEM32\CONFIG\default.log
exclude.fi
Have additional SAN-enabled TSM Clients or Agents been released other
than the existing Exchange and NT SAP R/3 TDPs?
Do the SAN-enabled TSM Exchange and NT SAP R/3 TDPs support tape sharing
with 3590E's in 3494's?
Any new TSM SAN client/agent info. (upcoming release dates, implementation
experi
I have just installed the new 4.1.2 client ona a few systems.
The client seems to backup up all files, event if they are previously
backed up.
The clients where upgraded from 3.1.0.8.
The 3.1.0.8-README states:
This version of the client supports ACL's and file properties. If you
are
updati
Hi *SMer,
We are reclaiming OFFSITE-Volumes, when they reach a Reclamation Threshold of 60
Percent.
Therefor following steps are being done:
1) All pertaining OFFSITE Volumes come in from the offsite Location.
2) Following SQL Stmt will be performed for each Volume: (Setting the Access of
the volu
Are you using DRM? If so then you need to let reclamation empty the volumes, then
request from vault tapes that are in a DRM state of vaultretrieve - which will be
empty tapes. Then when there are back then one way to handle is MOVE DRMEDIA xx
wherestate=vaultr tostate=onsiter for each
after a look into the dsmsched.log there are no errors inside. Therefore my question:
How does the Server decide, that a node is missed or failed?
thx Mike
It works the same without DRM. Lower the Reclamation value on the offsite
pool. As a fresh version of the copypool is being created, the old one is
going to empty. When you're thru, send off the new version and bring back
the empties.
At 10:16 AM 1/8/2001 -0500, you wrote:
>Are you using D
Are you you using NT or Windows 2000?
First, I would add an include for the staging directory, ADSM.SYS, so that
the registry and other system objects are processed correctly (this is
important on Windows 2000):
* this should be the last include/exclude statement, i.e., at the bottom of
the list
Hello all,
I have been exporting various client node data from an OS290 V3.1.2.50 to
an AIX 3.1.2.50 environment which has completed without error. However, I have
just ran an incremental backup (with -incrbydate) to test the first backup. For
some reason the client has backed up the whole co
Hi,
Can please someone tell me how to fix this problem
Apparently i have some tapes in 'mountable' state ..,but out of the adsm
library
and i'm unable to change their status..
Please Advise
I was not restoring only one BOX , there were 3 Boxes production and development
and another Sun box, ..Which I restored successfully. Assuming your data is on
multiple volumes, TSM will try to mount all tapes, provided sufficient drives
available ,I configured all available drives from stk971
I just upgraded by cluster servers (15 of them) from 3.7 client to 4.1.2
clients and they worked fine. No problem with scheduler resource service or
backups running. Is your options file set up as "Clusternode=YES" or
"Clusternode YES" (should be the second one)
-Original Message-
From:
Neil,
What version of the TSM server are you running and on what operating
system? I encountered the exact same problem and opened up a record with
TSM support. I was told that the issue was related to the fact that we
were running V3.7.1.0 of the OS/390 TSM server and we needed to be at
3.7.3.
I'm just wondering if anyone has any real life experiences to relate about generating
TSM backupsets under TSM 3.7.3 running on OS/390.
We recently had a server failure that took us awhile to restore, for various reasons.
We are looking at possibly generating backupsets on some sort of regul
Sekar,
We have been running our 4 mammoth drives for 14 months and have not
seen any tape issues. However when we upgraded to mammoth-2 drives we
discovered potential incompatabilities with aix 4.2.1 and/or adsm v3.
Now trying to move quickly to tsm 4.1.
sekar n wrote:
>
> Hi,
> I have a IBM 733
Why are you using the -incrbydate function? That means back up anything
that has changed since that date. Which is what you're seeing, I think.
Try just a straight incremental (dsmc incr) and see what it does.
Nick Cassimatis
[EMAIL PROTECTED]
"I'm one cookie away from happy." - Snoopy (Charle
Hi,
We had this problem, until we figured out that the secret is not in the
windows installer but rather the version of IE you have on your NT client.
Make sure you have the most recent version and you will only need to reboot
once.
Arthur.
-Original Message-
From: Collins, Brenda [mail
Hi!
Most of out NT servers that we are looking to install TSM 4.1 on, do not
have the updated windows installer. As a result, it requires an additional
re-boot prior to installing TSM. Has anyone been successful in scripting
the installation for SMS and getting around any re-boots? If you wou
> I have been exporting various client node data from an OS290 V3.1.2.50 to
>an AIX 3.1.2.50 environment which has completed without error. However, I have
>just ran an incremental backup (with -incrbydate) to test the first backup. For
>some reason the client has backed up the whole contents
When you install this client, it will unpack the installation stuff into a
temporary directory. I think if you install from there you might not need
the windows installer stuff. Not sure of this, but it is something to try.
I think there is a question "do you want to delete the temporary files"
I'm approaching upgrading the 3590 drives in a 3494 to 3590E,
extended length capable, where the server level is 3.1.2.50
in an AIX 4.1 system. What I would like to do is boost the
Atape and Atldd drivers ahead of the hardware upgrade, so as
to have that much work done and assured before the hard
Richard, the answer to your question is no, you don't need to reboot.
However, and I trust you know this, you need to:
1) delete the tape definitions ( # rmdev -dl rmt? , and also lmcp0),
2) install yr Atape atldd drivers, and
3) then run config manager ( # cfgmgr ), config manager will rebuild yr
Greetings...
We have recently upgraded to TSM 4.1 from ADSM 3.1 and have noticed a
severe performance issue.
Specifically when using the AFS/DFS Backup by File client, file processing
is EXTREMELY slow... in the order of 5-10 files per minute! Thankfully,
the old client still works, and still wo
Make sure to mark all of the b written tapes to reado until the data has
expired otherwise you run into problems. I have a doc from IBM regarding
the switchover if you are interested.
Becky Davidson
Data Manager/AIX Administrator
EDS/Earthgrains
voice: 314-259-7589
fax: 314-877-8589
email: [EMAI
I am getting ready to attach a 3494 with some 3590-e1a drives to tsm
4.1.2 on windows 2000. The atape driver that came with the library
shipment last February is for version 4.0.5.0 for windows nt. Do I need
a later driver? I downloaded and tried to install the 4.1.5.0 version
from the ibm ftp sit
IBM Support suggests a reboot.
-Original Message-
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 08, 2001 1:51 PM
To: [EMAIL PROTECTED]
Subject: Atape device driver upgrade require reboot?
I'm approaching upgrading the 3590 drives in a 3494 to 3590E,
extended length
Richard,
I just upgraded the Atape driver to 5.4.2.0 on an AIX 4.3.2 with a 3575 library
and a reboot was not necessary.
Martha
> Date: Mon, 8 Jan 2001 13:51:11 -0500
> From: Richard Sims <[EMAIL PROTECTED]>
> Subject: Atape device driver upgrade require reboot?
> To: [EMAIL PROTECTED]
>
> I'm
Basically if you have schedmode prompted and have a client schedule setup for the
node, then it is missed if server couldn't contact the client within the window of
time set up in the schedule - it is considered MISSED.
(Simplest reason is the client is down, or not fully configured correctly
32 matches
Mail list logo
