TSM Client doesn´t see local drives.

Hinerakatauri1979

ADSM.ORG Member
Joined
Jul 23, 2009
Messages
10
Reaction score
1
Points
0
PREDATAR Control23

Hi,

I´ve got a problem where my tsm client doesn´t see local drives.
I even cannot reach the network path from tsm. But for explorer its reachable. Also MS Backup sees the drives fine.

I reinstalled client and even upgraded to version 5.5.2.2 but nothing helped. Optfile hasn´t changed and it used to work just fine. Also no new policy implemented or patches that could cause this problem.
 
PREDATAR Control23

What do you mean by "I even cannot reach the network path from tsm"?

Are the drives local or mapped drives?
 
PREDATAR Control23

Its not a opt file issue, I have exact same optfile as on another server with same hardware/sofware configuration.
 
PREDATAR Control23

for those who think its the optfile, here it is.

NODENAME name
CLUSTERNODE NO
PASSWORDACCESS GENERATE
COMMMETHOD TCPIP
ENABLELANFREE NO
TCPSERVERADDRESS **.**.*.**
TCPPORT 15001
TCPWINDOWSIZE 63
TCPBUFFSIZE 32
TXNBYTELIMIT 204800
TCPNODELAY YES
RESOURCEUTILIZATION 2
MANAGEDSERVICES WEBCLIENT SCHEDULE
HTTPPORT 1581
SCHEDMODE POLLING
ERRORLOGNAME C:\TSM\Logs\dsmerror.log
ERRORLOGRETENTION 14
SCHEDLOGNAME C:\TSM\Logs\dsmsched.log
SCHEDLOGRETENTION 7
BACKUPREGISTRY YES
QUIET
SNAPSHOTPROVIDERFS VSS

COMPRESSION YES
COMPRESSALWAYS NO

include.fs c: fileleveltype=dynamic
include.fs d: fileleveltype=dynamic
 
PREDATAR Control23

add virtual mountpoint since you are using include.fs, I'm guessing this is a flavor of UNIX OS - I had that problem too on a UNIX server.
 
PREDATAR Control23

I added Domain ALL-LOCAL.

and its not a Unix server, its a windows 2003 sp2.

Here´s the last log file.



09/17/2009 21:04:45 Server Window Start: 21:00:00 on 09/17/2009
09/17/2009 21:04:45 ------------------------------------------------------------
09/17/2009 21:04:45
Executing scheduled command now.
09/17/2009 21:04:45 --- SCHEDULEREC OBJECT BEGIN DHVWIN01D_I2100 09/17/2009 21:00:00
09/17/2009 21:04:46 Incremental backup of volume 'SYSTEMSTATE'
09/17/2009 21:04:48 ANS1959I Removing previous incomplete group '\System State\0\SystemState' Id:0-786582272
09/17/2009 21:04:48 Performing a full, TSM backup of object 'COM+ REGDB Writer' component 'COM+ REGDB' using shadow copy.
09/17/2009 21:04:48 Performing a full, TSM backup of object 'Registry Writer' component 'Registry' using shadow copy.
09/17/2009 21:04:48 Performing a full, TSM backup of object 'Event Log Writer' component 'Event Logs' using shadow copy.
09/17/2009 21:06:17 ANS1999E Incremental processing of 'DHNL001SB022\SystemState\NULL\System State\SystemState' stopped.
09/17/2009 21:06:21 ANS5280E Object enumeration from a file set or file list failed.
09/17/2009 21:06:21 --- SCHEDULEREC STATUS BEGIN
09/17/2009 21:06:21 Total number of objects inspected: 10
09/17/2009 21:06:21 Total number of objects backed up: 0
09/17/2009 21:06:21 Total number of objects updated: 0
09/17/2009 21:06:21 Total number of objects rebound: 0
09/17/2009 21:06:21 Total number of objects deleted: 0
09/17/2009 21:06:21 Total number of objects expired: 0
09/17/2009 21:06:21 Total number of objects failed: 0
09/17/2009 21:06:21 Total number of subfile objects: 0
09/17/2009 21:06:21 Total number of bytes transferred: 10.11 KB
09/17/2009 21:06:21 Data transfer time: 0.00 sec
09/17/2009 21:06:21 Network data transfer rate: 0.00 KB/sec
09/17/2009 21:06:21 Aggregate data transfer rate: 0.10 KB/sec
09/17/2009 21:06:21 Objects compressed by: 0%
09/17/2009 21:06:21 Subfile objects reduced by: 0%
09/17/2009 21:06:21 Elapsed processing time: 00:01:35
09/17/2009 21:06:21 --- SCHEDULEREC STATUS END
09/17/2009 21:06:22 --- SCHEDULEREC OBJECT END DHVWIN01D_I2100 09/17/2009 21:00:00
09/17/2009 21:06:22 ANS1512E Scheduled event 'DHVWIN01D_I2100' failed. Return code = 12.
09/17/2009 21:06:22 Sending results for scheduled event 'DHVWIN01D_I2100'.
09/17/2009 21:06:22 Results sent to server for scheduled event 'DHVWIN01D_I2100'.
 
PREDATAR Control23

Can you try excluding the system state ('DOMAIN C: D: -SYSTEMSTATE') and trying the scheduled backup? It looks like the job is stopping during the systemstate backup (ANS5280E) and not processing the local drives.
 
PREDATAR Control23

Ok, I Have excluded the systemstate.

Manual backup gives me the following error.


tsm> incr
ANS1149E No domain is available for incremental backup. The domain may be empty
or all file systems in the domain are excluded.
tsm>

this in in my optfile:

DOMAIN -SYSTEMSTATE
INCLUDE.FS "c:" fileleveltype=dynamic
INCLUDE.FS "d:" fileleveltype=dynamic
 
Last edited:
PREDATAR Control23

Since this is a Windows server get rid of the

INCLUDE.FS just use INCLUDE.BACKUP

Or, I found this on another post...

"open the client gui, utilities, setup wizard, choose open file support, then choose "help me configure open file support" then choose to Remove the TSM logical volume snapshot agent. It will ask you to reboot the machine but if you wait it does not seem to be an issue "
 
PREDATAR Control23

Ok, Problem solved. There was a regkey that prevented the local system account to see All Local Drives..

Removed that key and everything works again. No idea how the key was added.
 
PREDATAR Control23

Similar issue ....

When we take a scheduled backup it is completing successfully ....even the actlog says it processed, backed up etc

but when we are trying to take a manual backup by logging in to the client server

say: dsmc incr

it is failing with no domain found.

Why scheduled backup running fine and why not manual backup( no domain issue)

tsm> incr
ANS1149E No domain is available for incremental backup. The domain may be empty
or all file systems in the domain are excluded.
tsm>

we tried different parameter values to domain parameter like C: , ALL-LOCAL -systemstate etc but no luck

checked the DRM and nodrives values in regedit ....they are good

what else can be the issue ..... i dont think a permission issue
Can anyone throw some light on it?
 
PREDATAR Control23

what was the registry key you removed to enable the local system account to see all local drives?
This is a really old post, who knows if the original posters still visit. You should start your own thread and explain the symptoms of your exact problem. Windows and Spectrum Protect changed a lot in 10 years. Even the product name is different as it's no longer called TSM.
 
Top