TSM server is 4.1.3.0 on Windows NT 4.0.
Does anyone know what is causing these, whether they are serious (our DBAs
do not trust the backups that produce them,) and what I can do to prevent
them?
Thanks.
Allan Kelly.
x27;s InoculateIT) and here is his response:
Hi - I work with Allan Kelly who started this thread. I know next to
nothing about TSM, but am fairly well versed with Windows NT / 2000 / XP and
I wanted to clear up a misconception I saw here. Specifically, the idea of
"accessing a file and then
stymied.
Any useful suggestion are most urgently needed.
Thanks.
Allan Kelly.
The select @@servername returned lowercase pc1162. The DBA had some
difficulty changing it to uppercase due to replication subscriptions or some
such, but after he did up date it, it now works. Does this mean that TDP
SQL cannot handle mixed case server names? (That last question is just for
in
Thanks for the response, Del.
The query command immediately followed several full backups of the pubs
database. The TSM node name is PC1162_SQL and the server name is PC1162
which is also what SQL 7 knows the server as. The result of q filespace
follows:
tsm: TSM_HOST1>q fi pc1162*
Node Name
ideas what might be causing this?
Thanks.
Allan Kelly.
