TSM client issue (some local disk missing)

slartibartfast

Newcomer
Joined
Jun 19, 2020
Messages
2
Reaction score
0
Points
0
Hi!

Server 2016. Standard client 7 Release 1 Level 6.2l.
But unexpected issue - client doesn't see some local disks. Only C, D and L.
It's not a network shares. I found old post here where guy fixed similar issue with changing some registry key.
Buy key not specified. Who can help with this?
Thanks in advance.
 
Yes, of course.
It's pretty simple...

NODENAME SOMESERVER
TCPSERVERADDRESS SOMEIP
TCPPORT 1500

*** Client network config ***
TCPCLIENTPORT 1501
HTTPPORT 1581
WEBPORTS 1591,1571
TCPWINDOWSIZE 63

*** Logging ***
SCHEDLOGNAME "C:\TSM\Log\TSMClientSchedule-BAC.log"
SCHEDLOGRETENTION 14 D
ERRORLOGNAME "C:\TSM\Log\TSMClientSchedule-BAC-error.log"
ERRORLOGRETENTION 14 D
DATEFORMAT 3

*** Scheduling ***
SCHEDMODE PROMPTED
MANAGEDSERVICES WEBCLIENT SCHEDULE

*** Cluster ***
*CLUSTERNODE YES
*CLUSTERDISKSONLY YES

*** Misc ***
AUTODEPLOY NOREBOOT
PASSWORDACCESS GENERATE

*** Client performance ***
*RESOURCEUTILIZATION 4
*DEDUPLICATION YES
*COMPRESSION OFF
*CHANGINGRETRIES 1

*** Include / exclude list ***
INCLUDE "?:\...\*" FIL-STD-D
INCLUDE.SYSTEMSTATE ALL SYSTEMSTATE
INCLUDE.BACKUP "j:\...\*" FIL-STD-D
DIRMC FIL-STD-D
DOMAIN ALL-LOCAL
DOMAIN "SYSTEMSTATE"
 
Hi,
Your opt file looks fine.

Are there any settings from option sets?

From the client, you can issue dsmc q opt and dsmc q incl

If you are familiar with trace files:

dsmc i -traceflags=service tracefile=c:\temp\trace.txt

Just when the client has listed the drives it will backup, you can stop and look through the output file and see if anything looks weird.

When you do changes to the dsm.opt file, you need to restart the tsm client scheduler.
If you can try, reboot the host. SP detect alot of issues, but it is not the root cause.
 
Back
Top