Windows 2003 Standard Server with TSM client V5.2.3
I'm looking at any tips to install OFS (Open File Support) also I believe referred to as LVSA. In reading some of the 'readme' files it looks like this isn't supported under the 2003 Windows server platform. I've attempted to install this and when I do I get the following error: ANS3010E - 'The Logical Volume Snapshot Agent failed. I've also read the TSM Client version 5.2.3 does backup opened files without the OFS feature. Has anyone worked on this? Melinda Cooper Senior Information Center Analyst
unsubscribe ADSM-L=20
Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
Restores in test lab
Disaster Recovery test, getting 'Inaccessible boot device' We are preparing for an off-site Disaster recovery drill, in our test lab I've installed two parallel Windows 2000 servers that mirror our production environment along with the TSM client V5.1. In the test lab I've built the operating system with HP SmartStart V7.1 along with Windows 2000 CD. The production servers have TSM V5.1 installed, the dsm.opt file has 'domain-all local' so the system objects and files are being backed up. In our test environment the first portion is to restore the system objects. After the restore is completed then you are required to reboot the machine. Since the servers are on dissimilar hardware we tend to get an 'inaccessible_boot_device' upon reboot. We've been able to accomplish a work around on one server but are stumped on the other one. (Both servers in the test lab are the same model.) Has anyone encountered this type of situation? I've done some research on google but haven't found anything that works. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
Re: Tivoli locking up a Win2k system?
What version of the TSM Client are you using? Is this Windows 2000 with service pack 4? Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Chris Hund [mailto:[EMAIL PROTECTED] Sent: Thursday, August 12, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: Tivoli locking up a Win2k system? Hi all, Has anyone ever come across an issue where the Tivoli client locks up a Win2k system? This is happening fairly regularly with one of the Win2k boxes in our environment. Here are a few small excerpts from the dsmsched.log file during the times the system locks up: --- 07/22/2004 07:06:58 Normal File-- 259,384 \\harr-facet-app\c$\WINNT\Fonts\micross.ttf 07/22/2004 09:16:06 Querying server for next scheduled event. 07/25/2004 02:56:02 Directory-- 0 \\harr-facet-app\c$\Program Files\TriZetto\Facets\311\Customer\Output\Backup-ELIG\ERISCO_8920\log 07/25/2004 23:34:33 Querying server for next scheduled event. 07/26/2004 07:09:48 Normal File--13,072 \\harr-facet-app\c$\WINNT\system32\dmintf.dll [Sent] 07/26/2004 07:09:48 Normal File-- 07/26/2004 09:00:16 Querying server for next scheduled event. 08/12/2004 17:08:20 Normal File-- 105,232 \\harr-facet-app\c$\WINNT\system32\dfssetup.dll [Sent] 08/12/2004 17:38:34 Querying server for next scheduled event. --- Those excerpts from the dsmsched.log file come from four different days ... four different days where the system locked up during a backup. As you can see, there's nothing consistent about where or when the backup is when the system locks up (which is why I'm leaning towards thinking this isn't really a TSM problem). I've talked to IBM Tivoli support. They didn't know what the problem was. I'm hoping someone here has come across this before. Many thanks, Chris Hund IBM Tivoli Administrator, Fiserv Health
Re: TSM Client V5.2.2.10 for Windows 2000/2003
I'm back from class and I've installed TSM V5.2.3 on another 2003 Windows server and the results have been positive. I've done some test restores on a 2000 server that I installed this same version on with good results. The Unix admins don't really want me to install this TSM V5.2.3 since they would prefer what they call a maintenance level, like TSM V5.2.3.X. Do you see any reason why TSM V5.2.3 would not be safe to install? Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Friday, July 23, 2004 1:38 PM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 Just to close the loop with the rest of this list on this: The doc that Melinda and Leif sent me both showed invalid verb received messages, which suggested IC40841. The current APAR description isn't an exact match, but from what I knew about the fix for that APAR, it seemed worth a shot. There were two facets of this APAR to fix. The first facet, which is the pertinent one here, is fixed in 5.2.3.0 (even if the README file doesn't mention IC40841). The second facet (regarding a successful backup message even if the file system processing stopped prematurely), will be fixed in an upcoming interim fix, at which time IC40841 will be shown as fixed. It is my understanding that 5.2.3.0 resolved the problem for Leif (at least initial testing looked promising). If and when Melinda reads this message, perhaps she can indicate her current status as well. But I think this will resolve her problem, too. So for anyone who experiences similar symptoms to those discussed earlier in this thread: try 5.2.3.0. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence.
Re: TSM Client V5.2.2.10 for Windows 2000/2003
I'm currently attending a class, however, I checked my email. As far as I know V5.2.3. seems to work on both Windows 2000/20003. Andrew, will the interim fix be V5.2.3.1? Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Friday, July 23, 2004 1:38 PM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 Just to close the loop with the rest of this list on this: The doc that Melinda and Leif sent me both showed invalid verb received messages, which suggested IC40841. The current APAR description isn't an exact match, but from what I knew about the fix for that APAR, it seemed worth a shot. There were two facets of this APAR to fix. The first facet, which is the pertinent one here, is fixed in 5.2.3.0 (even if the README file doesn't mention IC40841). The second facet (regarding a successful backup message even if the file system processing stopped prematurely), will be fixed in an upcoming interim fix, at which time IC40841 will be shown as fixed. It is my understanding that 5.2.3.0 resolved the problem for Leif (at least initial testing looked promising). If and when Melinda reads this message, perhaps she can indicate her current status as well. But I think this will resolve her problem, too. So for anyone who experiences similar symptoms to those discussed earlier in this thread: try 5.2.3.0. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence.
TSM Client V5.2.2.10 for Windows 2000/2003
We've been working with IBM Support on various issues we've had with this version of the client V5.2.2.10. We are reviewing this newer version and wonder if anyone has had any issues? Currently the majority of our Windows servers have TSM Client V5.1 installed. We realized a few months ago that our system objects were not being backed up and updated our dsm.opt file to 'domain all-local'. In doing this we ran into some issues of getting RC=12 - failure notifications that the backups failed. In reviewing the event log, dsmerror log and adsmsched log file it says that in fact the files were backed up. IBM said that this was resolved with TSM Client V5.2.2.10. I have since been installing mainly Windows 2003 operating systems with this newer version. Periodically we run into the same issue of RC=12 - failure notification that the backup failed, but in fact the files were backed up. IBM has said that the 'best practice' is to have two separate backups one for system objects and the other for files. I have over 80 windows servers and I'd rather upgrade to the newer client than change all the dsm.opt files and install a batch file. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
Re: TSM Client V5.2.2.10 for Windows 2000/2003
This has been very frustrating for us since when you review the log files it says that the system objects and files have successfully been backed up. This is the error code: ANS1026E Session rejected: Communications protocol error. Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ADSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. So at this point I don't know if it's in the dsm.opt file for with the Unix server that has the TSM software. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Kamp, Bruce [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 7:54 AM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 I just started to notice this also on one of my Win2k3 servers. I never heard about splitting the backups before now Also noticed these errors: 07/20/2004 02:34:44 ANS1512E Scheduled event 'WIN_SYS_4' failed. Return code = 12. 07/20/2004 06:44:26 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:44:34 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:44:41 GetDfsEnum(): Server=\\xxx01, NetDfsEnum() returns RC=259. 07/20/2004 06:44:52 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED - Bruce Kamp Senior Server Analyst Memorial Healthcare System E-Mail: [EMAIL PROTECTED] Phone: (954) 987-2020 x4597 Pager: (954) 286-9441 Alphapage: [EMAIL PROTECTED] Fax: (954) 985-1404 - -Original Message- From: Cooper, Melinda [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 10:48 AM To: [EMAIL PROTECTED] Subject: TSM Client V5.2.2.10 for Windows 2000/2003 We've been working with IBM Support on various issues we've had with this version of the client V5.2.2.10. We are reviewing this newer version and wonder if anyone has had any issues? Currently the majority of our Windows servers have TSM Client V5.1 installed. We realized a few months ago that our system objects were not being backed up and updated our dsm.opt file to 'domain all-local'. In doing this we ran into some issues of getting RC=12 - failure notifications that the backups failed. In reviewing the event log, dsmerror log and adsmsched log file it says that in fact the files were backed up. IBM said that this was resolved with TSM Client V5.2.2.10. I have since been installing mainly Windows 2003 operating systems with this newer version. Periodically we run into the same issue of RC=12 - failure notification that the backup failed, but in fact the files were backed up. IBM has said that the 'best practice' is to have two separate backups one for system objects and the other for files. I have over 80 windows servers and I'd rather upgrade to the newer client than change all the dsm.opt files and install a batch file. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
Re: TSM Client V5.2.2.10 for Windows 2000/2003
Have you installed this version on any windows platforms? Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Bos, Karel [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 8:05 AM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 Hi, There is a 5.2.3 windows client available on the ftp site (maintenance dir). Maybe these problems are solved in that version? Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Cooper, Melinda Sent: dinsdag 20 juli 2004 17:00 To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 This has been very frustrating for us since when you review the log files it says that the system objects and files have successfully been backed up. This is the error code: ANS1026E Session rejected: Communications protocol error. Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ADSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. So at this point I don't know if it's in the dsm.opt file for with the Unix server that has the TSM software. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Kamp, Bruce [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 7:54 AM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 I just started to notice this also on one of my Win2k3 servers. I never heard about splitting the backups before now Also noticed these errors: 07/20/2004 02:34:44 ANS1512E Scheduled event 'WIN_SYS_4' failed. Return code = 12. 07/20/2004 06:44:26 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:44:34 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:44:41 GetDfsEnum(): Server=\\xxx01, NetDfsEnum() returns RC=259. 07/20/2004 06:44:52 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED 07/20/2004 06:47:46 VssQuerySystemWriters(): pAsync-QueryStatus() returns hr=E_UNEXPECTED - Bruce Kamp Senior Server Analyst Memorial Healthcare System E-Mail: [EMAIL PROTECTED] Phone: (954) 987-2020 x4597 Pager: (954) 286-9441 Alphapage: [EMAIL PROTECTED] Fax: (954) 985-1404 - -Original Message- From: Cooper, Melinda [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 10:48 AM To: [EMAIL PROTECTED] Subject: TSM Client V5.2.2.10 for Windows 2000/2003 We've been working with IBM Support on various issues we've had with this version of the client V5.2.2.10. We are reviewing this newer version and wonder if anyone has had any issues? Currently the majority of our Windows servers have TSM Client V5.1 installed. We realized a few months ago that our system objects were not being backed up and updated our dsm.opt file to 'domain all-local'. In doing this we ran into some issues of getting RC=12 - failure notifications that the backups failed. In reviewing the event log, dsmerror log and adsmsched log file it says that in fact the files were backed up. IBM said that this was resolved with TSM Client V5.2.2.10. I have since been installing mainly Windows 2003 operating systems with this newer version. Periodically we run into the same issue of RC=12 - failure notification that the backup failed, but in fact the files were backed up. IBM has said that the 'best practice' is to have two separate backups one for system objects and the other for files. I have over 80 windows servers and I'd rather upgrade to the newer client than change all the dsm.opt files and install a batch file. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
Re: TSM Client V5.2.2.10 for Windows 2000/2003
As I mentioned the majority of my Windows 2000 servers have TSM Client V5.1 and have had no problems with backing up 'domain all-local'. Then we started installing V5.2.2 on Windows 2003 and started seeing the 'RC=12 error message'. We scrubbed that version and started installing with V5.2.2.10. We occasionally see this 'RC=12' problem failed back ups even using V5.2.2.10. I was working with IBM Support on these issues and this is the solution that was generated from them: The problem documented in the Apar IC38377 is generated by the TSM Client, then upgrading the TSM Server does not fix the problem, it is fixed if the current Client is upgraded to v5.2.2.10. To split the backups you should modify in the dsm.opt file, the line: Domain All-Local changing it to: Domain C: D: With this change, the current scheduled task will perform the backup of all the information on the C and D disks but not the OS files. Then you can create a command file (for example OSfiles.cmd) in the directory Baclient, with the instructions to backup the System State, System Services and the ASR files: dsmc backup systemstate dsmc backup systemservices dsmc backup asr And also a new scheduled task in the TSM Server must be created to run the command file OSfiles.cmd, this schedule will use ACTION=COMMAND and OBJECTS=OSfiles (-- or the name you chose for the cmd file). Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 8:16 AM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 Hi Melinda, Can you provide more information about the problem? The dsminfo.txt file created by the dsmc query systeminfo command would be helpful (make sure you use the same dsm.opt file as your scheduler uses). You can attach dsminfo.txt in a response. Also, check the server activity log to see what messages are issued therein at the time this problem occurs. What are these messages? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 07/20/2004 07:59:54: This has been very frustrating for us since when you review the log files it says that the system objects and files have successfully been backed up. This is the error code: ANS1026E Session rejected: Communications protocol error. Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ADSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. So at this point I don't know if it's in the dsm.opt file for with the Unix server that has the TSM software.
Re: TSM Client V5.2.2.10 for Windows 2000/2003
I can forward to you the information to your Internet email account. List Serve wouldn't let me include the attachments. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981 -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 8:16 AM To: [EMAIL PROTECTED] Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003 Hi Melinda, Can you provide more information about the problem? The dsminfo.txt file created by the dsmc query systeminfo command would be helpful (make sure you use the same dsm.opt file as your scheduler uses). You can attach dsminfo.txt in a response. Also, check the server activity log to see what messages are issued therein at the time this problem occurs. What are these messages? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 07/20/2004 07:59:54: This has been very frustrating for us since when you review the log files it says that the system objects and files have successfully been backed up. This is the error code: ANS1026E Session rejected: Communications protocol error. Explanation: Communications protocol error. An unexpected communications message was received by the client. System Action: ADSM canceled the current operation. User Response: Verify that your communication path is functioning properly. If the problem continues, have your service representative check for a possible program error. So at this point I don't know if it's in the dsm.opt file for with the Unix server that has the TSM software.
TSM client V5.2.2.10 for Windows 2000/2003
We've been working with IBM Support on various issues we've had with this version of the client V5.2.2.10. We are reviewing this newer version and wonder if anyone has had any issues? Currently the majority of our Windows servers have TSM Client V5.1 installed. We realized a few months ago that our system objects were not being backed up and updated our dsm.opt file to 'domain all-local'. In doing this we ran into some issues of getting RC=12 - failure notifications that the backups failed. In reviewing the event log, dsmerror log and adsmsched log file it says that in fact the files were backed up. IBM said that this was resolved with TSM Client V5.2.2.10. I have since been installing mainly Windows 2003 operating systems with this newer version. Periodically we run into the same issue of RC=12 - failure notification that the backup failed, but in fact the files were backed up. IBM has said that the 'best practice' is to have two separate backups one for system objects and the other for files. I have over 80 windows servers and I'd rather upgrade to the newer client than change all the dsm.opt files and install a batch file. Melinda Cooper Senior Information Center Analyst Work - 425.783.4467 Pager - 425.438.5981
