Re: [ADSM-L] Windows servers not backing up
2011-01-21 17:05:27
2003: figure out the ping problem and try again. If they cannot talk to each
other backups will not work.
2008r2: Is the firewall on? Is there a rule to let TSM out? Turn on the
firewall logging and view the log at:
C:\Windows\System32\LogFiles\Firewall\pfirewall.log
Use at your own risk on 2008:
netsh advfirewall firewall add rule name="IBM Tivoli Storage Manager CAD"
dir=in program="C:\program files\tivoli\tsm\baclient\dsmcad.exe" action=allow
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Hughes
Sent: Friday, January 21, 2011 2:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Windows servers not backing up
Hello all,
We have two windows clients that are not backing up. The backup
processes are started and it always seems ready to backup, however
in the morning when we check it always shows missed.
dsmerror.log (shows nothing)
01/06/2011 14:59:07 ANS1577I The Windows console event handler
received a 'Ctrl-C' console event.
01/08/2011 13:30:49 ANS1577I The Windows console event handler
received a 'Ctrl-C' console event.
Server 1 (windows 2003) tivoli client 6.2.0.0
Note - I can't ping tsm server nor can our tsm server ping the
client server,
Scheduler shows it ready? However it shows its ready every night but
does not backup
01/19/2011 14:44:23 Scheduler has been started by Dsmcad.
01/19/2011 14:44:23 TSM Backup-Archive Client Version 6, Release 2,
Level 0.0
01/19/2011 14:44:23 Querying server for next scheduled event.
01/19/2011 14:44:23 Node Name: AVARADO
01/19/2011 14:44:23 Session established with server TSM: AIX
01/19/2011 14:44:23 --- SCHEDULEREC QUERY BEGIN
01/19/2011 14:44:23 --- SCHEDULEREC QUERY END
01/19/2011 14:44:23 Next operation scheduled:
01/19/2011 14:44:23
------------------------------------------------------------
01/19/2011 14:44:23 Schedule Name: MIDNIGHT1
01/19/2011 14:44:23 Action: Incremental
01/19/2011 14:44:23 Objects:
01/19/2011 14:44:23 Options:
01/19/2011 14:44:23 Server Window Start: 00:01:00 on 01/20/2011
01/19/2011 14:44:23
------------------------------------------------------------
01/19/2011 14:44:23 Scheduler has been stopped.
dsm.opt
LANG AMENG
DOMAIN ALL-LOCAL
TCPSERVERADDRESS xxxx.xxx.xx.xx
PASSWORDACCESS GENERATE
TCPCLIENTADDRESS xx.x.xxx.xx
NODENAME avarado
Errorlogname c:\progra~1\tivoli\tsm\baclient\dsmerror.log
SCHEDlogname c:\progra~1\tivoli\tsm\baclient\dsmsched.log
Errorlogretention 14
schedlogretention 7
LARGECOMMbuffers yes
changingretries 2
subdir yes
txnbytelimit 25600
tcpb 32
tcpw 63
tcpnodelay yes
schedmode prompted
replace prompt
MANAGEDSERVICES WEBCLIENT SCHEDULE
server 2 (same issue) however TSM server is able to ping client and
client is able to ping tsm server.
Windows 2008 r2 64 bit 6.1.3.0.0
Schedule always seem ready to backup however it never does.
01/19/2011 14:32:50 Node Name: spiros14
01/19/2011 14:32:50 --- SCHEDULEREC QUERY BEGIN
01/19/2011 14:32:50 --- SCHEDULEREC QUERY END
01/19/2011 14:32:50 Next operation scheduled:
01/19/2011 14:32:50
------------------------------------------------------------
01/19/2011 14:32:50 Schedule Name: MIDNIGHT1
01/19/2011 14:32:50 Action: Incremental
01/19/2011 14:32:50 Objects:
01/19/2011 14:32:50 Options:
01/19/2011 14:32:50 Server Window Start: 00:01:00 on 01/20/2011
01/19/2011 14:32:50
------------------------------------------------------------
01/19/2011 14:32:50 Scheduler has been stopped.
LANG AMENG
DOMAIN ALL-LOCAL
TCPSERVERADDRESS xxxx.xxx.xxx.xx
PASSWORDACCESS GENERATE
TCPCLIENTADDRESS xx.xx.xx.xx
NODENAME spiros14
Errorlogname c:\progra~1\tivoli\tsm\baclient\dsmerror.log
SCHEDlogname c:\progra~1\tivoli\tsm\baclient\dsmsched.log
Errorlogretention 14
schedlogretention 7
LARGECOMMbuffers yes
changingretries 2
subdir yes
txnbytelimit 25600
tcpb 32
tcpw 63
tcpnodelay yes
schedmode prompted
replace prompt
*exclude "*:\MSSQL\DATA\MSSQL.1\MSSQL\Data\*.*"
MANAGEDSERVICES WEBCLIENT SCHEDULE
I tried using both the domain for the tsm server address and the
xx.xxx.xxx for the IP address.
Thanks
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
|
|