Failed TSM Backup - Cannot fix it!

[fpoe]

Hi all,

I've had a TSM backup fail many many times.

- Running version 6.1.3.3 TSM Client (Previously was running lower level, didn't work still)
- Tried reinstalling the client, removing the services, reconfiguring from scratch to no avail. Error is shown below.
- Event log is clean.
- Win2003 X86 server

07/26/2010 19:05:16 ANS1228E Sending of object '\\Server1\c$' failed
07/26/2010 19:05:16 ANS1063E The specified path is not a valid file system or logical volume name.

The manual incremental has run before. Any ideas?

 

[moon-buddy]

What is server1? Is this the BIOS name of the server being backed up?

 

[dms19]

set the nodename in the dsm.opt file

 

[fpoe]

- Server1 is the nodename in TSM and is set in the dsm.opt
- Ports are all open. Communication doesn't seem to be an issue. The sched log updates with the schedule. Password set properly as well
- Server pulling sched using client acceptor.

Willing to try anything at this point before PMR.

 

[moon-buddy]

Have you tried to use another nodename?

Normally, you use the BIOS name as the nodename. When you change the nodename, you need to update the TSM services are these are bound to the nodename.

 

[fpoe]

The nodename currently matches the server's workstation name in the domain. Queried all services using dsmcutil and they all look good and use the proper node name.
- I've even tried renaming the file spaces to no avail.

 

[moon-buddy]

What Windows version are you running on? Post dsm.opt.

 

[fpoe]

Server 2003, 32-bit.

 

[zamby]

security related?

If you log in with admin account, the manual backups work, but the scheduled backups don't. Are scheduled TSM services starting with SYSTEM account?

 

[dms19]

The dsierror.log/dsmerror.log or system event log show anything of use?

Clearly the C drive is available and formatted, correct? There has to be something in the services or opt file thats fooling TSM.

 

[fpoe]

Looks like the manual backups are also failing now. When I try to start the GUI, it takes forever to load and usually stalls on "Starting dsmagent..."

- dsmerror.log only has those entries relating to the following:
"07/26/2010 19:05:16 ANS1063E The specified path is not a valid file system or logical volume name."

Looks like it's also a terminal server.

C is formatted and available as it is the system partition. The server seems to operate without any issues at all. The backups just seem to be stubborn as heck.

Backups are scheduled with the system account. Should have access to the system partition at very least.

 

[dms19]

can you post up the contents of the dsm.opt file? Could be an issue with your domain statement

MS Event logs show no issue with the disk?

 

[zamby]

Start from CLI

Turn off all TSM services and run a dsmc. Post output.

 

[fpoe]

Interesting. I log in with the console session and the GUI opens very snappy and the backup starts right away.

I'm going to uninstall, remove the services and start from scratch using the console session and see if it runs overnight.

Nothing wrong with disk. No errors, bad blocks, etc.

 

[dms19]

tip - instead of removing the services with the GUI use the dsmcutil function to ensure things get cleared out properly

 

[fpoe]

tip - instead of removing the services with the GUI use the dsmcutil function to ensure things get cleared out properly

Yeah I've made it a habit now to install and remove services uses dmscutil. It seems the newer client (6.2+) doesn't make them properly in the GUI. Well for me anyway, I could be doing something wrong.

I doubt it though after admin of 500+ nodes.

 

[fpoe]

Looks like it began to process systemstate then died. Excluded systemstate to see if that helps.

Manual backup still runs from both GUI and dsmc.

 

[dms19]

are you sure its not something in the dsm.opt? Can you copy and paste it in?

 

[fpoe]

Disguised IP. I don't actually have X.X.X.X in the address.

Trying memory efficient as well to give it a go.

If I would have made a syntax error, when I launched the CLI or GUI it would have detected it and barfed out an error as well.

Fairly standard dsm.opt. Been changing everything via GUI just incase it was something I was typing.

------------------

NODENAME Server1
TCPSERVERADDRESS X.X.X.X
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
EXCLUDE.BACKUP "*:\...\EA DATA. SF"
EXCLUDE.BACKUP "*:\IBMBIO.COM"
EXCLUDE.BACKUP "*:\IBMDOS.COM"
EXCLUDE.BACKUP "*:\IO.SYS"
EXCLUDE.BACKUP "*:\...\system32\config\...\*"
EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
EXCLUDE.ARCHIVE "*:\IO.SYS"
EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
EXCLUDE.DIR "*:\System Volume Information"
EXCLUDE.DIR "*:\...\Temporary Internet Files"
EXCLUDE.DIR "*:\Recycled"
EXCLUDE.DIR "*:\Recycler"
EXCLUDE.DIR "*:\$Recycle.Bin"
ERRORLOGRETENTION 30 D
MANAGEDSERVICES WEBCLIENT SCHEDULE
PASSWORDACCESS GENERATE
SCHEDLOGRETENTION 30 D
MEMORYEFFICIENTBACKUP YES
DOMAIN "\\Server1\c$"
DOMAIN "\\Server1\d$"

 

[Mita201]

what user runs client acceptor service?
maybe should try using C: and D: in Domain statements instead of \\Server1\C$