Re: Windows 2000 client error
Thanks Richard! Looks like I am going to have to try the local fix (using the Windows NT Backup utility) which I have never done before and not sure if its possible. It shows the Tivoli Client fix levels but since this is a Windows 2000 Box I believe we are at the highest level 5.3.6.7 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Wednesday, August 17, 2011 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Windows 2000 client error Sounds like IC60649.
Re: Windows 2000 client error
I do not know it is correct or not, but we are running TSM Client 5.4.1.0 with the latest patches on a couple of Windows 2000 servers. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, August 18, 2011 4:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows 2000 client error Thanks Richard! Looks like I am going to have to try the local fix (using the Windows NT Backup utility) which I have never done before and not sure if its possible. It shows the Tivoli Client fix levels but since this is a Windows 2000 Box I believe we are at the highest level 5.3.6.7 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Wednesday, August 17, 2011 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Windows 2000 client error Sounds like IC60649. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Windows 2000 client error
Thanks, That may work but I am not sure if that client level for a windows 2000 server is supported? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Thursday, August 18, 2011 1:53 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Windows 2000 client error I do not know it is correct or not, but we are running TSM Client 5.4.1.0 with the latest patches on a couple of Windows 2000 servers. Grigori G. Solonovitch -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, August 18, 2011 4:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows 2000 client error Thanks Richard! Looks like I am going to have to try the local fix (using the Windows NT Backup utility) which I have never done before and not sure if its possible. It shows the Tivoli Client fix levels but since this is a Windows 2000 Box I believe we are at the highest level 5.3.6.7 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Sims Sent: Wednesday, August 17, 2011 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Windows 2000 client error Sounds like IC60649. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Windows 2000 client error
Hello all, We have a Windows 2000 Client that are constantly failing with the error below. 1st Windows 2000 sp4 Tivoli client 5.3.6.7 8/05/2011 00:33:14 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/06/2011 00:36:54 ANS1802E Incremental backup of '\\Gub7wss1\c$' finished with 1 failure 08/06/2011 00:36:57 ANS5250E An unexpected error was encountered. TSM function name : ProcessRegistryEntry TSM function : Backup of the registry hive 'C:\adsm.sys\W2KReg\REGISTRY\MACHINE\SOFTWARE\Device\HarddiskVolume2\WINNT\system32\config\software' failed. TSM return code : 4323 TSM file : ntreg.cpp (3261) 08/06/2011 00:36:57 ANS1228E Sending of object '\\Gub7wss1\c$\adsm.sys\W2KReg\*' failed 08/06/2011 00:36:57 ANS1929E An error occurred saving the registry key. 08/06/2011 00:37:53 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/07/2011 00:33:31 ANS5250E An unexpected error was encountered. TSM function name : ProcessRegistryEntry TSM function : Backup of the registry hive 'C:\adsm.sys\W2KReg\REGISTRY\MACHINE\SOFTWARE\Device\HarddiskVolume2\WINNT\system32\config\software' failed. TSM return code : 4323 TSM file : ntreg.cpp (3261) 08/07/2011 00:33:31 ANS1228E Sending of object '\\Gub7wss1\c$\adsm.sys\W2KReg\*' failed 08/07/2011 00:33:31 ANS1929E An error occurred saving the registry key. 08/08/2011 00:39:31 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. I tried to rename and delete the C:\adsm.sys file it did not solve the issue anyone had this issue before and was able to solve? Resolving the problem The errors are pointing to a corruption in the 'adsm.sys' folder on the system disk. You can delete the entry listed by the ANS2070E message in the adsm.sys folder and run the backup of the systemstate again which will recreate the 'adsm.sys' folder from scratch. Thanks in advance!
Re: Windows 2000 client error
Sounds like IC60649.
Re: Windows 2000 client
We have been on TSM server 6.n since August 21st 2009, currently at 6.2.2.0. Our oldest clients are at 5.1.5.0; we have several clients at 5.3.2.0 and 5.3.4.0. None of them has had a problem. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ochs, Duane Sent: Friday, January 14, 2011 12:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows 2000 client Good day everyone, My TSM servers are currently at 5.5.4 and I'd like to get migrated to 6.2 this year. I have some W2K clients that cannot be retired at this time and I found that 5.5 clients are the oldest supported by 6.2 Is anyone out there using the TSM 5.3 client on W2k and any version of TSM server 6.* Any helpful ideas would be appreciated. Thanks, Duane Follow Quad/Graphics in social mediahttp://www.qg.com/socialmedia http://facebook.com/quadgraphics http://www.youtube.com/user/QuadGraphicsVideos http://linkedin.com/companies/8199
Re: Windows 2000 client
Hello Duane, There is no problem for running 5.5.3 client on W2K with a 6.x TSM Server. Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Ochs, Duane Envoyé : vendredi 14 janvier 2011 21:37 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Windows 2000 client Good day everyone, My TSM servers are currently at 5.5.4 and I'd like to get migrated to 6.2 this year. I have some W2K clients that cannot be retired at this time and I found that 5.5 clients are the oldest supported by 6.2 Is anyone out there using the TSM 5.3 client on W2k and any version of TSM server 6.* Any helpful ideas would be appreciated. Thanks, Duane Follow Quad/Graphics in social mediahttp://www.qg.com/socialmedia http://facebook.com/quadgraphics http://www.youtube.com/user/QuadGraphicsVideos http://linkedin.com/companies/8199 ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system.
Windows 2000 client
Good day everyone, My TSM servers are currently at 5.5.4 and I'd like to get migrated to 6.2 this year. I have some W2K clients that cannot be retired at this time and I found that 5.5 clients are the oldest supported by 6.2 Is anyone out there using the TSM 5.3 client on W2k and any version of TSM server 6.* Any helpful ideas would be appreciated. Thanks, Duane Follow Quad/Graphics in social mediahttp://www.qg.com/socialmedia http://facebook.com/quadgraphics http://www.youtube.com/user/QuadGraphicsVideos http://linkedin.com/companies/8199
Windows 2000 client
I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Windows 2000 client
Hi Gary! The latest version for Window 2000 is 5.3.6.7 and can be downloaded from IBM: ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches/ client/v5r3/Windows/Win2000/v536/TSM536C_7_X32.exe Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: dinsdag 18 mei 2010 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Windows 2000 client I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Re: Windows 2000 client
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r3/Windows/x32/v536/ should get you where you're going. Be aware that you'll have to type the file name in manually rather than clicking on the link. IBM has, intentionally or accidentally, inserted a single blank space in front of many (most?) of the links on the FTP site, so it's no longer possible to simply click all the way through to what you're looking for anymore. On Tue, May 18, 2010 at 9:21 AM, Lee, Gary D. g...@bsu.edu wrote: I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Windows 2000 client
Off the top of my head, I think 5.3.7.4 was a more recent Windows 2000- safe version that I used to deploy back in the day, but there may have been one or two further Win2K-able releases after that. //David Mc On 18 May 2010, at 14:21, Lee, Gary D. g...@bsu.edu wrote: I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Windows 2000 client
5.4.0.2 was the last release that could be installed on Windows 2000. It works. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ADSM-L Sent: Tuesday, May 18, 2010 6:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows 2000 client Off the top of my head, I think 5.3.7.4 was a more recent Windows 2000- safe version that I used to deploy back in the day, but there may have been one or two further Win2K-able releases after that. //David Mc On 18 May 2010, at 14:21, Lee, Gary D. g...@bsu.edu wrote: I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Windows 2000 client
This is the latest Windows 2000 client ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/client /v5r4/Windows/Win2000/
Re: Re Windows 2000 client reconfiguration
If you use Microsofts RoboCopy utility you can copy data without modifying any of the attributes. The latest version that comes with the Windows 2003 resource kit lets you do all kinds of cool stuff including retaining ownership on the files. It is also an incremental only copy utility so you can start the copy a week ahead of time and then run one last incremental copy the night before. Actually this new version lets you start it in a mode where it is always running and sends changed files from the source to the destination right when they change. Anyway, we use this for our server moves. Tab Trepagnier [EMAIL PROTECTED] wrote:Farren, From our experience, this is the problem: Configure a new server and copy the data across in such a way that it doesn't look like it's changed. Our main file servers have been on five different physical machines in the eight years I've been here. Our attempts to copy data from one file server to another have always caused TSM to grab a new copy of the entire server. One issue is that Microsoft's tools - xcopy, ncopy, and pcopy - all copy permissions but not inheritance. So a folder on the source that inherits certain permissions from its parent will have the same permissions APPLIED on the copy. From Windows' perspective that is an ACL change, so TSM grabs a new copy. Worse, it means that any changes you intend to apply at the top of the directory tree dead-end at that level. You must then force the inheritance down the tree, which means ANOTHER ACL change and another copy of the file server pulled into TSM. If you're going to pull in a copy of the entire server anyway, I would recommend that you get your permissions, inheritance, auditing, etc. as close to perfect as possible BEFORE launching the first post-migration backup. And do as much with groups as possible. Adding just one user ID to the top of a directory tree will provoke a very large backup session. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. ADSM: Dist Stor Manager wrote on 05/12/2005 03:08:20 AM: Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Re Windows 2000 client reconfiguration
Farren, From our experience, this is the problem: Configure a new server and copy the data across in such a way that it doesn't look like it's changed. Our main file servers have been on five different physical machines in the eight years I've been here. Our attempts to copy data from one file server to another have always caused TSM to grab a new copy of the entire server. One issue is that Microsoft's tools - xcopy, ncopy, and pcopy - all copy permissions but not inheritance. So a folder on the source that inherits certain permissions from its parent will have the same permissions APPLIED on the copy. From Windows' perspective that is an ACL change, so TSM grabs a new copy. Worse, it means that any changes you intend to apply at the top of the directory tree dead-end at that level. You must then force the inheritance down the tree, which means ANOTHER ACL change and another copy of the file server pulled into TSM. If you're going to pull in a copy of the entire server anyway, I would recommend that you get your permissions, inheritance, auditing, etc. as close to perfect as possible BEFORE launching the first post-migration backup. And do as much with groups as possible. Adding just one user ID to the top of a directory tree will provoke a very large backup session. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 05/12/2005 03:08:20 AM: Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re Windows 2000 client reconfiguration
Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Re Windows 2000 client reconfiguration
Hi Farren, Been here before ourselves... might be interesting/useful to work out why the TSM client believes the file has changed. Run a backup of the files that you believe it should *not* be backing up but is, but with a trace enabled (hmn, I forget the exact traceflag we used now - might be worth you taking a look at Richard Sims' (not-so!)Quick Facts for the correct one) and this will tell you which attribute it is that it thinks has changed, be it NT permissions, modified date etc... I remember uncovering a somewhat undocumented '-testflag SKIPNTSECURITYCHANGES' during this saga last year which did exactly what the name suggests... Hope that helps point you in the right direction... Rgds, David McClelland Shared Infrastructure Development Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 12 May 2005 09:08 To: ADSM-L@VM.MARIST.EDU Subject: Re Windows 2000 client reconfiguration Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## - Visit our Internet site at http://www.reuters.com To find out more about Reuters Products and Services visit http://www.reuters.com/productinfo Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Re: Re Windows 2000 client reconfiguration
Hi Win200x Server Backup Techs, I'd be interested in info on this too. I just went through this, forced to move NT disks around. Our one big shared network disk on Win2003 Server filled up and first we split off to a 2nd disk, then moved to a much larger single disk chunk again, all on an IBM SAN. I kept the disk id E: the same on the same server name etc, but just couldn't stop Tivoli from backing up the whole thing again and again. After doing our normal 6 week incremental and an image backup in case etc, I created a FLUSH domain with 2 day retention and smaller version settings etc, moved the Win2003 server to that domain, and flushed out the older FULL backups. I then moved it back to the domain it was in. So what flag does the Win200n Tivoli client use to backup a file again, besides update date or archive flag? Thanks.. Charlie Hurtubise Tecsys Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David McClelland Sent: Thursday, May 12, 2005 6:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Re Windows 2000 client reconfiguration Hi Farren, Been here before ourselves... might be interesting/useful to work out why the TSM client believes the file has changed. Run a backup of the files that you believe it should *not* be backing up but is, but with a trace enabled (hmn, I forget the exact traceflag we used now - might be worth you taking a look at Richard Sims' (not-so!)Quick Facts for the correct one) and this will tell you which attribute it is that it thinks has changed, be it NT permissions, modified date etc... I remember uncovering a somewhat undocumented '-testflag SKIPNTSECURITYCHANGES' during this saga last year which did exactly what the name suggests... Hope that helps point you in the right direction... Rgds, David McClelland Shared Infrastructure Development Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 12 May 2005 09:08 To: ADSM-L@VM.MARIST.EDU Subject: Re Windows 2000 client reconfiguration Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## - Visit our Internet site at http://www.reuters.com To find out more about Reuters Products and Services visit http://www.reuters.com/productinfo Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
Re: Windows 2000 client reconfiguration
On May 12, 2005, at 4:08 AM, Farren Minns wrote: ...From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? ... IBM site Technote 1154307 notes that prevailing Windows settings can cause restored objects to inherit parental permissions, to the exclusion of the permissions they had at backup time. This may or may not be a factor. Given that you have both the production and test restoral file systems in place, you have the ideal opportunity to conduct detailed comparisons of the same objects and directories in the two cases, and discern differences, potentially leading to resolution of your issue. It will be valuable to identify restored files which TSM does *not* deem subsequent candidates for backup, as a further source of information. Be sure to reference the client manual's summary of backup criteria. Where TSM 5.3 is used, the new PREview command may be helpful. Richard Simshttp://people.bu.edu/rbs
AW: [ADSM-L] Re Windows 2000 client reconfiguration
Have a look at Performing an incremental, selective, or incremental-by-date backup in manual IBM Tivoli Storage Manager for Windows - Backup-Archive Clients Installation and User's Guide or have a look at Richard Sims marvelous TSM website - topic backup etc. http://people.bu.edu/rbs/ADSM.funcdir HTH Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Charlie Hurtubise Gesendet: Donnerstag, 12. Mai 2005 15:29 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Re Windows 2000 client reconfiguration Hi Win200x Server Backup Techs, I'd be interested in info on this too. I just went through this, forced to move NT disks around. Our one big shared network disk on Win2003 Server filled up and first we split off to a 2nd disk, then moved to a much larger single disk chunk again, all on an IBM SAN. I kept the disk id E: the same on the same server name etc, but just couldn't stop Tivoli from backing up the whole thing again and again. After doing our normal 6 week incremental and an image backup in case etc, I created a FLUSH domain with 2 day retention and smaller version settings etc, moved the Win2003 server to that domain, and flushed out the older FULL backups. I then moved it back to the domain it was in. So what flag does the Win200n Tivoli client use to backup a file again, besides update date or archive flag? Thanks.. Charlie Hurtubise Tecsys Inc.
Slow running Windows 2000 client
Hi all One of our 5.1.6.0 Windows 2000 clients has started running very slowly. The data transfer rate is fine, but the length of time it's taking to check through it's files has increased from approximately two hours to over seven. Any ideas where I can look to see what's happening here? Thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Slow running Windows 2000 client
On May 10, 2005, at 6:11 AM, Farren Minns wrote: Hi all One of our 5.1.6.0 Windows 2000 clients has started running very slowly. The data transfer rate is fine, but the length of time it's taking to check through it's files has increased from approximately two hours to over seven. Any ideas where I can look to see what's happening here? The usual stuff... A large increase in the file system population, lousy directory topology, changes in virus scanning, Windows Event Log issues, disk contention with other applications, swap space added to the same disk or path, etc. If nothing seems out of the ordinary, consider running a chkdsk or the equivalent on the file system, to ferret out any defects contributing to performance drag. Richard Sims
Re: Slow running Windows 2000 client
While there are a lot of potential causes here, the first thing I would check is that some other process hasn't started running during backups. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 5/10/2005 5:11 AM Hi all One of our 5.1.6.0 Windows 2000 clients has started running very slowly. The data transfer rate is fine, but the length of time it's taking to check through it's files has increased from approximately two hours to over seven. Any ideas where I can look to see what's happening here? Thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
INCLUDE directory question for Windows 2000 Client
Hi all TSMers I have a question regarding the 'include' of a specific directory on a Windows 2000 client with a different management class to the standard one. I'm used to doing this on Solaris clients but don't know much about Windows flavours. So far I have created a new management class called '7dayexpire' and made sure that it is active and made sure the client in question is registered to the correct Policy Domain. I have edited the dsm.opt file on the client and added the following line:- INCLUDE E:\home\asouther\backup_040505\* 7dayexpire Now, I assumed that when I backed up this dir the files would get rebound, but they didn't and I can make it work. What am I doing wrong? I assume I'm using the incorrect syntax or something but don't know. Thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: INCLUDE directory question for Windows 2000 Client
On May 5, 2005, at 10:44 AM, Farren Minns wrote: I have edited the dsm.opt file on the client and added the following line:- INCLUDE E:\home\asouther\backup_040505\* 7dayexpire Now, I assumed that when I backed up this dir the files would get rebound, but they didn't and I can make it work. What am I doing wrong? I assume I'm using the incorrect syntax or something but don't know. Rebinding happens when there is cause for the client files to be backed up again. Make it a habit to do 'dsmc query inclexcl' after adjusting Include or Exclude options, to assure that the combination of server and client options yields what you seek - and remember that server options take precedence. You may also have intended to have your Include use \...\* wildcarding instead of \*. Richard Sims
Re: slow running windows 2000 client backup
I tried the trace but didn't get any output from it. Here are the statements I used: testflag instrument:detail testflag instrument:api I see the dsminstr.report file but it has 0 bytes in it. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave Canan Sent: July 12, 2004 5:18 PM To: [EMAIL PROTECTED] Subject: Re: slow running windows 2000 client backup Ralph - I work in IBM TSM performance support. Please get a client instruction trace as Richard suggests for this problem and post it to the listserver. I can take a look at it. At 01:16 PM 7/12/2004 -0400, you wrote: I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. Tried rebooting the client and ran performance monitor. Neither helped or showed any problems. Here is the bad server: 07/11/2004 14:23:08 ANS1898I * Processed 194,500 files * 07/11/2004 14:25:17 ANS1898I * Processed 195,000 files * 07/11/2004 14:34:18 ANS1898I * Processed 195,500 files * 07/11/2004 15:16:52 ANS1898I * Processed 196,000 files * Here is a typical server: 07/04/2004 21:45:02 ANS1898I * Processed 649,000 files * 07/04/2004 21:45:05 ANS1898I * Processed 649,500 files * 07/04/2004 21:45:08 ANS1898I * Processed 650,000 files * 07/04/2004 21:45:10 ANS1898I * Processed 650,500 files * Does anyone have any ideas? The usual questions have been asked (what changed?) but we still come up blank. Thanks, Ralph Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
Re: slow running windows 2000 client backup
It sounds like you may have run the trace using the TSM GUI. This trace is only produced if you are running the TSM command line version of the backup/archive client. Try running the trace again, this time using dsmc.exe instead. Also, Richard mentioned that this is a journal based backup you're attempting, and that you are getting NpOpen timeout errors. Can you send me the jbberror.log file that you have for this client? There were some recent code fixes in this error on the client, that were fixed at level 5.2.2.10. Upgrading to this level may be another thing we want to consider here. Please let me know if you still are having problems getting the trace. At 08:52 AM 7/14/2004 -0400, you wrote: I tried the trace but didn't get any output from it. Here are the statements I used: testflag instrument:detail testflag instrument:api I see the dsminstr.report file but it has 0 bytes in it. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dave Canan Sent: July 12, 2004 5:18 PM To: [EMAIL PROTECTED] Subject: Re: slow running windows 2000 client backup Ralph - I work in IBM TSM performance support. Please get a client instruction trace as Richard suggests for this problem and post it to the listserver. I can take a look at it. At 01:16 PM 7/12/2004 -0400, you wrote: I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. Tried rebooting the client and ran performance monitor. Neither helped or showed any problems. Here is the bad server: 07/11/2004 14:23:08 ANS1898I * Processed 194,500 files * 07/11/2004 14:25:17 ANS1898I * Processed 195,000 files * 07/11/2004 14:34:18 ANS1898I * Processed 195,500 files * 07/11/2004 15:16:52 ANS1898I * Processed 196,000 files * Here is a typical server: 07/04/2004 21:45:02 ANS1898I * Processed 649,000 files * 07/04/2004 21:45:05 ANS1898I * Processed 649,500 files * 07/04/2004 21:45:08 ANS1898I * Processed 650,000 files * 07/04/2004 21:45:10 ANS1898I * Processed 650,500 files * Does anyone have any ideas? The usual questions have been asked (what changed?) but we still come up blank. Thanks, Ralph Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED] Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
AW: slowards running windows 2000 client backup
Does TSM Journal service run flawelessly on the slow machine on all filesystems backed-up? regards juraj -Ursprüngliche Nachricht- Von: Levi, Ralph [mailto:[EMAIL PROTECTED] Gesendet: Montag, 12. Juli 2004 19:17 An: [EMAIL PROTECTED] Betreff: slow running windows 2000 client backup I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. Tried rebooting the client and ran performance monitor. Neither helped or showed any problems. Here is the bad server: 07/11/2004 14:23:08 ANS1898I * Processed 194,500 files * 07/11/2004 14:25:17 ANS1898I * Processed 195,000 files * 07/11/2004 14:34:18 ANS1898I * Processed 195,500 files * 07/11/2004 15:16:52 ANS1898I * Processed 196,000 files * Here is a typical server: 07/04/2004 21:45:02 ANS1898I * Processed 649,000 files * 07/04/2004 21:45:05 ANS1898I * Processed 649,500 files * 07/04/2004 21:45:08 ANS1898I * Processed 650,000 files * 07/04/2004 21:45:10 ANS1898I * Processed 650,500 files * Does anyone have any ideas? The usual questions have been asked (what changed?) but we still come up blank. Thanks, Ralph
Re: slow running windows 2000 client backup
Make sure your network settings are correct. I have had bandwidth problems with our network switch (cisco 6509) with auto negotiation so I had the network guys force the port the 100 full duplex on the switch and set the client to the same setting. Then the bandwidth problems went away, and the client backed up normally. - I ran into a similar problem a while back where a W2K system had the Fibre Channel and Fast Ethernet sharing the same interrupt. Backup was the most demanding workload the node saw, so the problem only manifested during backup. In our case, the server admin swapped the onboard and add-in network card IP addresses, and the problem went away. Unlikely I know, but may be worth checking if you're exhausted the other possibilities. Those postings are good suggestions, based upon real experiences. Alas, the case cited is not in a network phase: it is plowing through the file system looking for candidate objects. The poster indicates having gone through our list of common causes for slow backups, and not having found a match based upon his analysis; so we'll have to await the results from his client trace or other analyses. Richard Sims http://people.bu.edu/rbs
slow running windows 2000 client backup
I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. Tried rebooting the client and ran performance monitor. Neither helped or showed any problems. Here is the bad server: 07/11/2004 14:23:08 ANS1898I * Processed 194,500 files * 07/11/2004 14:25:17 ANS1898I * Processed 195,000 files * 07/11/2004 14:34:18 ANS1898I * Processed 195,500 files * 07/11/2004 15:16:52 ANS1898I * Processed 196,000 files * Here is a typical server: 07/04/2004 21:45:02 ANS1898I * Processed 649,000 files * 07/04/2004 21:45:05 ANS1898I * Processed 649,500 files * 07/04/2004 21:45:08 ANS1898I * Processed 650,000 files * 07/04/2004 21:45:10 ANS1898I * Processed 650,500 files * Does anyone have any ideas? The usual questions have been asked (what changed?) but we still come up blank. Thanks, Ralph
Re: slow running windows 2000 client backup
I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. ... Ralph - Common issues are summarized in the Backup performance entry in http://people.bu.edu/rbs/ADSM.QuickFacts , which is a compilation of all the things that have bitten us in the past. See what else is running: this may be the classic, oft-cited case of a virus-checking program running at the same time. You have the advantage of being able to compare that bad system to one of the others and find just what's different. That system might also be thrashing on paging (too little real memory for its workload). Richard Sims
Re: slow running windows 2000 client backup
Hi Richard, Thanks for your quick response. Unfortunately we reviewed everything that is running on the box and came up with nothing. We also ran performance monitor all night and all we see (especially during the long waits) is that nothing is going on (memory, processing etc). Once we start transmitting data, the stats start fluctuating and look normal (as it should when processes are running). This has us totally stumped... Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: July 12, 2004 1:43 PM To: [EMAIL PROTECTED] Subject: Re: slow running windows 2000 client backup I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. ... Ralph - Common issues are summarized in the Backup performance entry in http://people.bu.edu/rbs/ADSM.QuickFacts , which is a compilation of all the things that have bitten us in the past. See what else is running: this may be the classic, oft-cited case of a virus-checking program running at the same time. You have the advantage of being able to compare that bad system to one of the others and find just what's different. That system might also be thrashing on paging (too little real memory for its workload). Richard Sims
Re: slow running windows 2000 client backup
Thanks for your quick response. Unfortunately we reviewed everything that is running on the box and came up with nothing. We also ran performance monitor all night and all we see (especially during the long waits) is that nothing is going on (memory, processing etc). Once we start transmitting data, the stats start fluctuating and look normal (as it should when processes are running). This has us totally stumped... Hi, Ralph - A good one you have there. You are up to date on W2000 and sounds like you've covered the basics in looksee. The problem smells like a file system or disk problem - perhaps the latter in that the manifestation seems to involve so many files (severe fragmentation may contribute to it). A DOS command which runs through the file system reporting attributes may help reveal there things are mired. A commercial disk analyzer may be of help. Personally, I would pursue a TSM client trace. The latest trace issuance info is in the 4.2 Trace Facility manual. I have notes on Client Tracing in ADSM QuickFacts. You can also take cues from info in IBM's web pages, such as in http://www-1.ibm.com/support/docview.wss?uid=swg21158015 Such a client trace should reveal where the time is being spent. We'd be interested in what's found on this problem. thanks, Richard Sims
Re: slow running windows 2000 client backup
Hi Ralph, Make sure your network settings are correct. I have had bandwidth problems with our network switch (cisco 6509) with auto negotiation so I had the network guys force the port the 100 full duplex on the switch and set the client to the same setting. Then the bandwidth problems went away, and the client backed up normally. Thanks, Matt -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 3:28 PM To: [EMAIL PROTECTED] Subject: Re: slow running windows 2000 client backup Thanks for your quick response. Unfortunately we reviewed everything that is running on the box and came up with nothing. We also ran performance monitor all night and all we see (especially during the long waits) is that nothing is going on (memory, processing etc). Once we start transmitting data, the stats start fluctuating and look normal (as it should when processes are running). This has us totally stumped... Hi, Ralph - A good one you have there. You are up to date on W2000 and sounds like you've covered the basics in looksee. The problem smells like a file system or disk problem - perhaps the latter in that the manifestation seems to involve so many files (severe fragmentation may contribute to it). A DOS command which runs through the file system reporting attributes may help reveal there things are mired. A commercial disk analyzer may be of help. Personally, I would pursue a TSM client trace. The latest trace issuance info is in the 4.2 Trace Facility manual. I have notes on Client Tracing in ADSM QuickFacts. You can also take cues from info in IBM's web pages, such as in http://www-1.ibm.com/support/docview.wss?uid=swg21158015 Such a client trace should reveal where the time is being spent. We'd be interested in what's found on this problem. thanks, Richard Sims
Re: slow running windows 2000 client backup
I ran into a similar problem a while back where a W2K system had the Fibre Channel and Fast Ethernet sharing the same interrupt. Backup was the most demanding workload the node saw, so the problem only manifested during backup. In our case, the server admin swapped the onboard and add-in network card IP addresses, and the problem went away. Unlikely I know, but may be worth checking if you're exhausted the other possibilities. [RC] Richard Sims [EMAIL PROTECTED]To:[EMAIL PROTECTED] Sent by: ADSM: Dist cc: Stor Manager Subject: Re: slow running windows 2000 client backup [EMAIL PROTECTED] 07/12/2004 12:28 PM Please respond to ADSM: Dist Stor Manager |---| | [ ] Secure E-mail | |---| Thanks for your quick response. Unfortunately we reviewed everything that is running on the box and came up with nothing. We also ran performance monitor all night and all we see (especially during the long waits) is that nothing is going on (memory, processing etc). Once we start transmitting data, the stats start fluctuating and look normal (as it should when processes are running). This has us totally stumped... Hi, Ralph - A good one you have there. You are up to date on W2000 and sounds like you've covered the basics in looksee. The problem smells like a file system or disk problem - perhaps the latter in that the manifestation seems to involve so many files (severe fragmentation may contribute to it). A DOS command which runs through the file system reporting attributes may help reveal there things are mired. A commercial disk analyzer may be of help. Personally, I would pursue a TSM client trace. The latest trace issuance info is in the 4.2 Trace Facility manual. I have notes on Client Tracing in ADSM QuickFacts. You can also take cues from info in IBM's web pages, such as in http://www-1.ibm.com/support/docview.wss?uid=swg21158015 Such a client trace should reveal where the time is being spent. We'd be interested in what's found on this problem. thanks, Richard Sims == IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. ==
Re: slow running windows 2000 client backup
Ralph - I work in IBM TSM performance support. Please get a client instruction trace as Richard suggests for this problem and post it to the listserver. I can take a look at it. At 01:16 PM 7/12/2004 -0400, you wrote: I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7 who's incremental backup never ends. Using the timestamps next to message: ANS1898I , it is taking between 5 minutes and 1 hour to parse through 500 files. I have 100+ other servers that take about 2/100 of a second to pass through 500 files. Tried rebooting the client and ran performance monitor. Neither helped or showed any problems. Here is the bad server: 07/11/2004 14:23:08 ANS1898I * Processed 194,500 files * 07/11/2004 14:25:17 ANS1898I * Processed 195,000 files * 07/11/2004 14:34:18 ANS1898I * Processed 195,500 files * 07/11/2004 15:16:52 ANS1898I * Processed 196,000 files * Here is a typical server: 07/04/2004 21:45:02 ANS1898I * Processed 649,000 files * 07/04/2004 21:45:05 ANS1898I * Processed 649,500 files * 07/04/2004 21:45:08 ANS1898I * Processed 650,000 files * 07/04/2004 21:45:10 ANS1898I * Processed 650,500 files * Does anyone have any ideas? The usual questions have been asked (what changed?) but we still come up blank. Thanks, Ralph Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
Re: slow running windows 2000 client backup
You mention a windows 2000 clients is it one client or multiple
clients?
You also mentioned asking about what changed, but it isn't clear whether
coming up blank means nothing changed, or nothing changed that you think
would cause this problem. The implicit question is: was the client
performance always this bad? Or was it okay before, but recently starting
having problems? If the latter, when did the problems start? You might
revisit the question of what changed around that timeframe, regardless of
the significance of the change.
Other things to look at:
- What does the client options file look like?
- Provide output from dsmc show options. Make sure to use the same
dsm.opt file as the scheduler uses.
- Provide output from dsmc query inclexcl Make sure to use the same
dsm.opt file as the scheduler uses.
- While the backup is running, what does a QUERY SESSION from the TSM
admin CLI show for this node's sessions?
- What else is running on the client machine while the backup is running?
- If this is the only machine having the problem (or one of relatively few
machines having the problem), compare it to a machine that runs fine: what
are the differences between the two machines? Consider installed hardware,
installed software, activity on each machine, location on the network,
etc.
- How long does it take for the dir command to traverse the file
system(s)? A simple script like this might be useful:
REM *** BEGIN T.CMD ***
@echo off
:TRAVERSE_DRIVE
if {%1} == {} goto :END
echo %time% - Traversing %1
dir %1\ /w/s nul
shift
goto :TRAVERSE_DRIVE
:END
echo %time% - Done
REM *** END T.CMD ***
Invoke the script and pass in your drive letters, i.e.:
t c: e: f:
- Are you backing up any network shares?
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/12/2004
10:16:54:
I have a windows 2000 clients (v5 sp 4 build 2195) running tsm 5.1.7
who's incremental backup never ends. Using the timestamps next to
message: ANS1898I , it is taking between 5 minutes and 1 hour to parse
through 500 files. I have 100+ other servers that take about 2/100 of a
second to pass through 500 files.
Tried rebooting the client and ran performance monitor. Neither helped
or showed any problems.
Here is the bad server:
07/11/2004 14:23:08 ANS1898I * Processed 194,500 files *
07/11/2004 14:25:17 ANS1898I * Processed 195,000 files *
07/11/2004 14:34:18 ANS1898I * Processed 195,500 files *
07/11/2004 15:16:52 ANS1898I * Processed 196,000 files *
Here is a typical server:
07/04/2004 21:45:02 ANS1898I * Processed 649,000 files *
07/04/2004 21:45:05 ANS1898I * Processed 649,500 files *
07/04/2004 21:45:08 ANS1898I * Processed 650,000 files *
07/04/2004 21:45:10 ANS1898I * Processed 650,500 files *
Does anyone have any ideas? The usual questions have been asked (what
changed?) but we still come up blank.
Thanks,
Ralph
Windows 2000 client include/exclude
I tried to backup only a few file with a server-scheduled backup from a Windows 2000 client. For LINUX or Solaris clients I managed this with include/exclude-Files without problems. For Windows-clients the scheduled backup (or dsmc incremental) seems to backup nearly the whole C:-partition. The result of dsmc query inclexcl is just what I want (see below). Why is my inclexcl-file not taken into consideration for backup? Regards, Joern Gehm --- This is what we are running: TSM Server 4.1.5 under AIX 4.3 (ADSM1.rrz.Uni-Koeln.DE) TSM Client 5.1.5 Windows 2000 (rzk-opac1.rrz.Uni-Koeln.DE) dsm.opt: - PASSWORDACCESS GENERATE TCPSERVERADDRESSADSM1.rrz.Uni-Koeln.DE domain -systemobject inclexcl c:\Programme\Tivoli\TSM\baclient\inexcl.txt == inexcl.txt: - EXCLUDE.DIR C:\ EXCLUDE.DIR \\rzk-opac1\c$\ INCLUDE.FILE \\rzk-opac1\c$\Dokumente und Einstellungen\a0019\Eigene Dateien\* Include.File \\rzk-opac1\c$\Dokumente und Einstellungen\a0019\Datei.bmp == (see output of 'dsmc query inclexcl' at the end) Begin of dsm.log after scheduled backup : --- 25.03.2003 13:09:23 --- ANFANG DER PLANUNGSPROTOKOLLOBJEKTE DAILY.13 25.03.2003 13:00:00 25.03.2003 13:09:24 Teilsicherung von Datentr\344ger '\\RZK-OPAC1\C$' 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\ [Gesendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\Dokumente u nd Einstellungen [Gesendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\INSTALL [Ge sendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\Programme [ Gesendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\RECYCLER [G esendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\SYSTEM [Ges endet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\System Volu me Information [Gesendet] 25.03.2003 13:09:25 Verzeichnis-- 0 \\rzk-opac1\c$\WINNT [Gese ndet] 25.03.2003 13:09:25 Normale Datei-- 0 \\rzk-opac1\c$\AUTOEXEC.B AT [Gesendet] 25.03.2003 13:09:25 Normale Datei-- 0 \\rzk-opac1\c$\CONFIG.SYS [Gesendet] 25.03.2003 13:09:25 Normale Datei-- 0 \\rzk-opac1\c$\IO.SYS [Ge sendet] 25.03.2003 13:09:25 Normale Datei-- 0 \\rzk-opac1\c$\MSDOS.SYS [Gesendet] 25.03.2003 13:09:25 Normale Datei-- 172.237 \\rzk-opac1\c$\NSM_Custom er_Presentation.PRZ [Gesendet] . . . == dsmc query inclexcl: - Tivoli Storage Manager Befehlszeilenschnittstelle des Clients fr Sichern/Archivieren - Version 5, Release 1, Stufe 5.0 (C) Copyright IBM Corporation 1990, 2002. Alle Rechte vorbehalten. Knotenname: RZK-OPAC1 Sitzung hergestellt mit Server ADSM1: AIX-RS/6000 Server-Version 4, Release 1, Stufe 5.0 Server-Datum/-Zeit: 25.03.2003 11:09:20 Letzter Zugriff: 25.03.2003 11:09:01 *** DATEI EINSCHLUSS/AUSSCHLUSS *** Modus Funktion Muster (bereinst. oben-unten) Quellendatei - --- Excl Directory c:\ c:\Programme\Tivoli\TSM\baclient\inexcl.txt Excl Directory C:\ c:\Programme\Tivoli\TSM\baclient\inexcl.txt Excl All C:\WINNT\System32\NtmsData\...\* Operating System Excl All C:\WINNT\System32\inetsrv\metabase.xml Operating System Excl All C:\WINNT\System32\inetsrv\metabase.bin Operating System Excl All C:\WINNT\System32\inetsrv\mbschema.xml Operating System Excl All C:\WINNT\System32\DTCLog\MSDTC.LOG Operating System Excl All C:\WINNT\schedlgu.txt Operating System Excl All C:\WINNT\registration\*.clbOperating System Excl All C:\WINNT\netlogon.chg Operating System Excl All C:\WINNT\debug\* Operating System Excl All C:\WINNT\csc\...\* Operating System Excl All C:\DOKUME~1\ADMINI~1\LOKALE~1\Temp\...\* Operating System Excl All C:\Dokumente und Einstellungen\Administrator\...\index.dat Operating System Excl All C:\adsm.sys\...\* Operating System Excl All *\Pagefile.sys Operating System Excl All *\hiberfil.sys Operating System Excl All *\...\*.crmlog Operating System Incl File c:\Dokumente und Einstellungen\a0019\Datei.bmp c:\Programme\Tivoli\TSM\baclient\inexcl.txt Incl File c:\Dokumente und Einstellungen\a0019\Eigene Dateien\* c:\Programme\Tivoli\TSM\baclient\inexcl.txt Keine DFS-Include/Exclude-Anweisungen definiert. === -- __ Joern Gehm E-Mail: [EMAIL PROTECTED] Tel: (0221) 478-5350 , FAX: -5568
Problem backing up Windows 2000 Client
Environment: TSM Server: 5.1.1.6 on AIX 4.3.3 ML10 Client: 5.1.5.9 Win 2k SP2 I get the following error in the dsmerror.log: 01/29/2003 20:23:55 fioScanDirEntry(): Can't map object 'C:\WINNT\?' into the local ANSI codepage, skipping ... 01/29/2003 21:31:19 ANS1512E Scheduled event 'API_FILE_SYSTEM_BACKUP' failed. Return code = 12. I get the following error in the dsmsched.log: 01/29/2003 20:14:25 ANS1228E Sending of object 'C:' failed 01/29/2003 20:14:25 ANS1931E An error saving one or more eventlogs. Has anybody seen this before? Thanks, -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 ---
Windows 2000 Client
Has anyone tried the new version yet 5.1.5.9 ?? Greg
Re: Windows 2000 Client
I just installed this morning. Have not finished testing yet. Will let you know if I find anything good or bad! -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: Heinz, Greg [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 12:56 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Client Has anyone tried the new version yet 5.1.5.9 ?? Greg
Re: Windows 2000 Client
yes, since 2 days on 2 clients, René LAMBELET NESTEC SA GLOBE - Global Business Excellence Central Support Center Information Technology Av. Nestlé 55 CH-1800 Vevey (Switzerland) tél +41 (0)21 924 35 43 fax +41 (0)21 703 30 17 local UBS-Nestec, Bussigny mailto:[EMAIL PROTECTED] This message is intended only for the use of the addressee and may contain information that is privileged and confidential. -Original Message- From: Heinz, Greg [mailto:[EMAIL PROTECTED]] Sent: Tuesday,28. January 2003 18:56 To: [EMAIL PROTECTED] Subject: Windows 2000 Client Has anyone tried the new version yet 5.1.5.9 ?? Greg
Re: PRESCHEDULECMD - Windows 2000 Client
1. Try running the preschedule command manually, to see if works. you might need to add a pause statement to keep the command window on the screen long enough to read any messages. 2. Make sure that the scheduler is running under an account that has enough rights and permissions to carry out the command. The default system account probably doesn't. -Original Message- From: Jack Musselman [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, December 26, 2001 4:15 PM To: [EMAIL PROTECTED] Subject:PRESCHEDULECMD - Windows 2000 Client Hello, I am trying to use the preschedulecmd client option to stop my R/3 instance prior to doing an offline backup. My server is on an AIX platform running version 4.2.1.7 and the client is TSM 4.2.1.18. I have configured the client acceptor to start the client scheduler. I have a define schedule that performs the backup properly, but the preschedulecmd and postschedulecmd do not function properly. I'm seeing a return code 1 in the dsmsched.log. Has anyone experience a problem like this? Any recommendations are welcome. Thanks in advance! Jack
PRESCHEDULECMD - Windows 2000 Client
Hello, I am trying to use the preschedulecmd client option to stop my R/3 instance prior to doing an offline backup. My server is on an AIX platform running version 4.2.1.7 and the client is TSM 4.2.1.18. I have configured the client acceptor to start the client scheduler. I have a define schedule that performs the backup properly, but the preschedulecmd and postschedulecmd do not function properly. I'm seeing a return code 1 in the dsmsched.log. Has anyone experience a problem like this? Any recommendations are welcome. Thanks in advance! Jack
Re: Recover Windows 2000 Client
I have successfully recovered a win2k server using client 4.2 we are currently in the process of testing the recovery of an AD server. I followed the procedure that was listed in the redbook for w2k recovery. T -Original Message- From: Joe Spade [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 08, 2001 7:52 AM To: [EMAIL PROTECTED] Subject:Recover Windows 2000 Client We decided to do a test on the recovery of a windows 2000 client. We made sure a backup was done of all local files and of the system files. We then trashed the drive, restored the os and installed the TSM client software. At this point we recovered the local files, then recovered the system files. After the system files were done, we were requested to do a restart. The client came up fine, everything looks ok. But, when we went into My Network Place an error 29 - unspecified error pops up. You get the same thing when you go into Control Panel. You click on ok and try to do a properties on local network connection and you get another unspecified error and you cannot continue. You are returned to the main network screen. Any ideas on what we did wrong or are we missing part of the recovery procedure. Any ideas would be greatly appreciated. Joe Spade R L Carriers, Inc. [EMAIL PROTECTED] 937-382-1494
Recover Windows 2000 Client
We decided to do a test on the recovery of a windows 2000 client. We made sure a backup was done of all local files and of the system files. We then trashed the drive, restored the os and installed the TSM client software. At this point we recovered the local files, then recovered the system files. After the system files were done, we were requested to do a restart. The client came up fine, everything looks ok. But, when we went into My Network Place an error 29 - unspecified error pops up. You get the same thing when you go into Control Panel. You click on ok and try to do a properties on local network connection and you get another unspecified error and you cannot continue. You are returned to the main network screen. Any ideas on what we did wrong or are we missing part of the recovery procedure. Any ideas would be greatly appreciated. Joe Spade R L Carriers, Inc. [EMAIL PROTECTED] 937-382-1494
Re: Recover Windows 2000 Client
We tested disaster recovery with Windows 2000 and TSM client version 4.1.2.14 I think, and ended up using NT Backup to backup the system state to a local file before the TSM backup ran. When we do a restore, we restore all the files using TSM and the system state using NT Backup. We had numerous problems restoring the system state with TSM and TSM support told us that 'bare metal recovery is not supported'. They supported restoring the files, and restoring the system state, but not 'bare metal recovery'. Go figure... Mark -Original Message- From: Joe Spade [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 08, 2001 8:52 AM To: [EMAIL PROTECTED] Subject: Recover Windows 2000 Client We decided to do a test on the recovery of a windows 2000 client. We made sure a backup was done of all local files and of the system files. We then trashed the drive, restored the os and installed the TSM client software. At this point we recovered the local files, then recovered the system files. After the system files were done, we were requested to do a restart. The client came up fine, everything looks ok. But, when we went into My Network Place an error 29 - unspecified error pops up. You get the same thing when you go into Control Panel. You click on ok and try to do a properties on local network connection and you get another unspecified error and you cannot continue. You are returned to the main network screen. Any ideas on what we did wrong or are we missing part of the recovery procedure. Any ideas would be greatly appreciated. Joe Spade R L Carriers, Inc. [EMAIL PROTECTED] 937-382-1494 Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Restoring Win2K profiles with 4.1.2 (was: Windows 2000 Client R edPiece available)
+ Consumer Warning: This information applies to restoring USER PROFILES on Win2K PRO systems. It does not normally apply to Win2K SERVER. Unless you know what a USER PROFILE IS, and you are interested in Win2K PRO bare metal restores, don't read it, it will just give you a headache + Hi Tim, We just tested a bare-metal restore for WIn2k Pro with the 4.1.2 client. We ran the registry (system object) backup manually. We found that the logged on user profile is indeed saved in a subdirectory of adsm.sys, and called NTUSER.DAT, as you said. We were able to recover the profile by just dragging NTUSER.DAT from adsm.sys to the appropriate place for that user's profile in Documents and Settings/userxx subdirectory. There is one trick to it, though: You must copy the NTUSER.DAT from adsm.sys to the Documents and Settings\userxx directory BEFORE that user ever logs on again after the bare metal restore. If there is not an NTUSER.DAT file in that directory, then WIn2K creates a NEW profile when the user logs on, which will be the directory called "userxx.domainname" or "userxx.domainname.00n", and it will be a copy of the default profile. (There may not be an NTUSER.DAT in that directory if the user always backed up while logged on; or it may be an old copy if the user backed up some time previously while logged off. Personally I would compare the time stamps and don't try to recreate the profile if there is a recent NTUSER.DAT copy in Documents and Settings.) If you get a new profile created under "userxx.domainname", you either have to log on again as administrator and copy the NTUSER.DAT file from adsm.sys to the NEW directory (AND copy the user's shortcuts from the old DESKTOP directory, plus other stuff like that). Or it is actually easier, In my opinion, to go into the registry and point the user's profile back to the old profile directory. Anyway, the way to do it right is (1) do the bare-metal restore while logged on as Administrator, not as userxx, and (2) after the bare-metal restore, copy NTUSER.DAT from adsm.sys to the Documents and Settings directory BEFORE you ever log on again as userxx. If you DON"T get the right profile when userxx logs on, look in Documents and Settings to see if you have gotten a bogus new profile created instead, and work at cleaning it up. None of the above will make much sense to someone else util they sit down and LOOK at what is in adsm.sys and in the Documents and Settings directory. MANY THANKS, Tim, for spotting this conflict in the Redpiece, you saved us a BUNCH of time and confusion... Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Rushforth, Tim [SMTP:[EMAIL PROTECTED]] Sent: Thursday, January 25, 2001 11:23 AM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 Client RedPiece available The RedPiece states: "Backups taken while a user is logged on locally at the system console will fail for the user profile file ntuser.dat for the current logged on user. Restoration of the user's profile from that backup session will not be possible." If the system ojbect is backed up when a user is logged on locally, the user's ntuser.dat (and usrclass.dat) is placed in the staging directory. Can we not copy this file manually as was recommeneded in the NT4 Redbook? Also, the restore procedure recommended here is: - restore the boot/system partition - restore system object - reboot - restore other drives - reboot Is there any reason why the other drives should not be restored along with the boot/system partition? This not only saves one reboot, but also may prevent the same tape(s) from being mounted and searched again. Thanks, Tim Rushforth City of Winnipeg -Original Message- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 4:12 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Client RedPiece available The RedPiece "Deploying the Tivoli Storage Manager Client for Windows 2000" (SG24-6141-00) is now available at http://www.redbooks.ibm.com - Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development
Re: Windows 2000 Client RedPiece available
The RedPiece states: "Backups taken while a user is logged on locally at the system console will fail for the user profile file ntuser.dat for the current logged on user. Restoration of the user's profile from that backup session will not be possible." If the system ojbect is backed up when a user is logged on locally, the user's ntuser.dat (and usrclass.dat) is placed in the staging directory. Can we not copy this file manually as was recommeneded in the NT4 Redbook? Also, the restore procedure recommended here is: - restore the boot/system partition - restore system object - reboot - restore other drives - reboot Is there any reason why the other drives should not be restored along with the boot/system partition? This not only saves one reboot, but also may prevent the same tape(s) from being mounted and searched again. Thanks, Tim Rushforth City of Winnipeg -Original Message- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 4:12 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Client RedPiece available The RedPiece "Deploying the Tivoli Storage Manager Client for Windows 2000" (SG24-6141-00) is now available at http://www.redbooks.ibm.com - Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development
Windows 2000 Client RedPiece available
The RedPiece "Deploying the Tivoli Storage Manager Client for Windows 2000" (SG24-6141-00) is now available at http://www.redbooks.ibm.com - Jim J.P. (Jim) Smith Tivoli Storage Manager - Software Development
