Re: Cleaning up "system state" backups

2013-09-17 Thread Andrew Raibeck
Hi Zoltan, For the tlmagent.exe file, a couple of things: 1. The TLMAGENT.EXE file: Check installed services to see if any ILMT services are hanging around, and remove the service. If the OS is Windows Vista or later, it could be a residual service. You can also examine the subkeys in HKLM\SYSTEM

Cleaning up "system state" backups

2013-09-17 Thread Zoltan Forray
I am constantly seeing message where Windows clients are running "system state/writer" backups and the process tries to backup files that are missing but some list is telling it to back it up. For example: 9/17/2013 12:04:56 AM ANE4251W (Session: 12574, Node: MAGIDATA) System Writer file '\\magi

Re: ANS1227E error

2013-09-17 Thread Del Hoobler
Hi Robert, It's entirely possible that the Exchange Writer reset itself after some particular sync point. I know that it has become more resilient over the past few releases and service packs. Again, that is something that Microsoft would need to share with us. Thanks, Del -

Re: ANS1227E error

2013-09-17 Thread Robert Ouzen
Hi Del Thanks for the answer ... But so strange I had a scheduler plan to 15:00 (incremental backup) , run fine. At 14:00 when I checked it was in Failed status and Retryable error After the backup it check the Microsoft Exchange Writers again , and surprise was in status Stable and no error

Re: TSM version 6.3 SQL statement is failing

2013-09-17 Thread Grigori Solonovitch
Thank you very much Rick. Now it looks much better - no errors. I hope script shows me skipped backups as before. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.

Re: TSM version 6.3 SQL statement is failing

2013-09-17 Thread Richard Rhodes
I believe that the problem is in the where clause where you cast to "days". I don't believe you can do that in db2. To fix my scripts I had to change that "days" to "hours / 24". Rick From: Grigori Solonovitch To: ADSM-L@VM.MARIST.EDU Date: 09/17/2013 02:42 AM Subject:TSM v

Re: ANS1227E error

2013-09-17 Thread Del Hoobler
Hi Robert, If you restart the Exchange Services, it should resolve it. I do not know of another way. You could ask Microsoft about this since it is the Microsoft VSS Writer that is getting into this state. Thanks, Del "ADSM: Dist Stor Manage

Re: Windows Clients and Non-Supported OS Levels

2013-09-17 Thread Grigori Solonovitch
I have found a few Windows 2003 Servers with TSM 6.4.0 Clients on our TSM Server. Fast restore test using WEB Client shows everything is fine. Are you sure "unsupported" means "not working"? Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -

Re: Windows Clients and Non-Supported OS Levels

2013-09-17 Thread Steven Harris
Of course those of us with long memories will remember that *exactly the same thing* happened with Windows 2000 and 5.4 client. In that case you didn't realize there was a problem until you tried a restore. Have they tried one Zoltan? Regards Steve Steven Harris TSM Admin Canberra Australia

Re: ANS1227E error

2013-09-17 Thread Robert Ouzen
Hi Del O.K , by the way sometimes I notice checking the vssadmin list writers command. The Microsoft Exchange Writer is in Failed stage Writer name: 'Microsoft Exchange Writer' Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7} Writer Instance Id: {05177631-6de6-4ae5-98a4-012f82486cc7