if you lmcpd is running, you won't see a /dev/lmcp# on a sun box as you
would on an aix box...
under sun just simply use the name that is in the /etc/ibmatl.conf
tsmatl05 149.183.246.88 tsmsrv10
so here I just use tsmatl05
zdec23@tsmsrv10/export/home/zdec23 > mtlib -l tsmatl05 -qL | more
All,
Has anyone seen this error in the DSMERROR.LOG on a Windows NT 4.0 client
version 4.2.1.20?
"fioScanDirEntry(): Can't map object 'C:\WINNT\?' into the local
ANSI codepage, skipping ..."
What does this mean?
Bruce E. Lowrie
Sr. Systems Analyst
Information Technology Services
Storage
Hello all,
I have got report from another site
that this problem, as well as
5.1.1.0 / NT2000 / ANR1134W Migration terminated for s torage pool
DISKPOOL -
is reproducable when installing TSM 5.1.1. on Windows 2000 GERMAN,
and seems to be limited to it.
Installing TSM on US NT2000 on same
So, the key is having the VOLHIST file saved, somewhere else, so it can be
reloaded to the rebuilt source server so he can find his DB backup !
Also sounds like doing a RECONCILE on a regular basis, is a good idea !
How often do you run RECONCILE ?
Thanks for enlightening me
For
I played around with this a lot in the past but don't have a large use for
it currently.
To do a recovery, you get a basic environment up and running with your
definitions over to your remote server and then just do a dsmserv restore db
as normal using the device class of the remote server and the
I got the same story from Veritas regarding what used to be called OTG
DiskXtender. They vehemently denied pulling TSM support for the product and
were in fact, quite interested in selling us some more licenses. They have
an agreement with IBM that IBM would get the source code should Veritas
de
Changes introduced in end of May actually revert back to point-based
pricing. Thus your prices should be per box, i.e. Tier 1, Tier 2, Tier 3.
NT with 1-4 processors is Tier 1, with 5 or more is Tier 2, etc.
While the price for TDP for MS SQL is close to one you have to pay for
Tier 1, the price
Good Day TSMers,
Has anyone seen problems in autostarting the TSM Scheduler on NT 4.00? It
starts fine manually but is not starting automatically on boot up (although
it is configured to do so).
TSM Server: 4.1.5.2 on AIX 4.3
TSM Backup client 4.2.2 on NT 4.00 SP 6.
There are two scheduler serv
Zoltan
We have a setup as you describe.
Your devconfig will have the TARGET SERVER as a device-class:
DEFINE DEVCLASS DEFAULT_SERVER_DEV DEVTYPE=SERVER MAXC...
DEFINE SERVER LAMPS_VBB44_S1 COMMMETHOD=TCPIP HLADDRESS=..
The volhist will show your Database-backup pointing to the right
ser
