Re: Updated VS Backed Up
Ok, as I said I was a little bit tired after an 14 hour shift.. Your question was Does anyone know how to get a testflag into a client option set? tsm: def clientopt test TRACEFLAGS -testflags=DISABLEATTRIBUPDATE ANR2050I DEFINE CLIENTOPT: Option TRACEFLAGS defined in optionset TEST. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: den 13 augusti 2008 16:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Updated VS Backed Up Skipntpermissions addresses a different issue. DISABLEATTRIBUPDATE addresses permissions that are saved in the TSM DB I believe as opposed to the ntfs security which stores the metadata in the storagepool. Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/12/2008 06:29 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Updated VS Backed Up Hi, Check 'Skipntpermissions' in the client manual. There could be a traceclass too but I am too tired to look.. Thanks Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: den 13 augusti 2008 00:14 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Updated VS Backed Up testflag DISABLEATTRIBUPDATE I read this tsmblog article: http://tsmblog.org/serendipity/index.php?/archives/81-UPDATED-vs-BACKED- UP.html I remember reading about this testflag on the IBM Support site and I thought I remember reading about it on adsm-l somewhere, but searching Google or IBM for DISABLEATTRIBUPDATE doesn't return anything anymore. Anyway, for posterity: By default TSM will not keep a history of permission changes, which doesn't make sense to me! In the past I've had to do complete system restores after a virus messed up permissions. This testflag in the dsm.opt file will disable that and backup the file for any change (including permission changes) Does anyone know how to get a testflag into a client option set? (My last resort will be to try adding -testflags=DISABLEATTRIBUPDATE to the options of all my schedules) Regards, Shawn Shawn Drew This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Migrating from old server to new server.
Hi, Whenever I have to move or add a server to our ITSM landscape, I use the enterprise config option. Simply add the new server to the config manager, activate my sync all important stuff policy (admins, scripts, domains and all things I want available on all my servers), deactivated this policy (without deleting the just sync stuff) and put the new ITSM server in my sync stuff enterprise config manager policy. One place to update admin passwords, generic scripts and more gooddies. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: woensdag 13 augustus 2008 17:25 To: ADSM-L@VM.MARIST.EDU Subject: Re: Migrating from old server to new server. Take a look at the export commands (and Import if appropriate) tsm: TSMhelp export EXPORT Commands EXPORT Commands Use the EXPORT commands to copy information from a Tivoli Storage Manager server to sequential removable media. The following is a list of EXPORT commands for Tivoli Storage Manager: EXPORT ADMIN (Export Administrator Information) EXPORT NODE (Export Client Node Information) EXPORT POLICY (Export Policy Information) EXPORT SERVER (Export Server Information) Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/13/2008 11:15 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Migrating from old server to new server. Is there anyway to move, copy, or migrate all definitions from old TSM server to a new TSM server? I want to basically to see if it is possible to transfer everything over to the new server domains, management classes, device classes everything. Dave Hensley Although this e-mail and any attachments are believed to be free of any virus or other defect which might affect any computer system, it is the responsibility of the recipient to check that it is virus-free and the sender accepts no responsibility or liability for any loss, injury, damage, cost or expense arising in any way from receipt or use thereof by the recipient. The information contained in this electronic mail message is confidential information and intended only for the use of the individual or entity named above, and may be privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, please contact the sender immediately, delete this material from your computer and destroy all related paper media. Please note that the documents transmitted are not intended to be binding until a hard copy has been manually signed by all parties. Thank you. This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n
Re: TSM Server on AIX cluster
Mario, You may consider the implication of a future upgrade to TSM V6 which is running DB2. Do you really think that Oracle and DB2 will co-exist on the same box? Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: Wednesday, August 13, 2008 5:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server on AIX cluster We've been running for many years with an Oracle / TSM / AIX configuration like the one you mention. We put the TSM server on one AIX node and the TSM client on the other AIX node. Works fast and reliably and TSM never put much load on the server processor nor did it ever interfere with any Oracle processes or database disk operations even with both the TSM database, logs and storage pools in the same raid array as the Oracle DBs. This configuration backups up about 700Gbytes a night from the Oracle 10G databases, both hot and cold user managed backups, in addition to another 100 MS servers. Larry Mario Behring [EMAIL PROTECTED] OO.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU [ADSM-L] TSM Server on AIX cluster 08/13/2008 09:42 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi all, I have the following scenario: * 2 p520 RISC machines running AIX and connected in cluster (not hacmp). Both have Oracle 10G. * a DS 4000 storage connected * a LTO3 tape unit connectedThis is a very small TSM installation, only the machines above will have the TSM client installed initially. Where is the best place to have the TSM Server installed? On both nodes, on one of the nodes or on a different machine? Also, should the TSM client be installed on both nodes? Any help is appreciated. Mario IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
SV: TSM Server on AIX cluster
Hi Mario, I agree with everyone else. Try to keep the TSM Server on another box then the Oracle machines. You can easy get away with a cheap Linux or Windows box that can take care of the TSM Server. Thanks Christian Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Strand, Neil B. [EMAIL PROTECTED] Skickat: den 14 augusti 2008 13:27 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: TSM Server on AIX cluster Mario, You may consider the implication of a future upgrade to TSM V6 which is running DB2. Do you really think that Oracle and DB2 will co-exist on the same box? Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Peifer Sent: Wednesday, August 13, 2008 5:14 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server on AIX cluster We've been running for many years with an Oracle / TSM / AIX configuration like the one you mention. We put the TSM server on one AIX node and the TSM client on the other AIX node. Works fast and reliably and TSM never put much load on the server processor nor did it ever interfere with any Oracle processes or database disk operations even with both the TSM database, logs and storage pools in the same raid array as the Oracle DBs. This configuration backups up about 700Gbytes a night from the Oracle 10G databases, both hot and cold user managed backups, in addition to another 100 MS servers. Larry Mario Behring [EMAIL PROTECTED] OO.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU [ADSM-L] TSM Server on AIX cluster 08/13/2008 09:42 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi all, I have the following scenario: * 2 p520 RISC machines running AIX and connected in cluster (not hacmp). Both have Oracle 10G. * a DS 4000 storage connected * a LTO3 tape unit connectedThis is a very small TSM installation, only the machines above will have the TSM client installed initially. Where is the best place to have the TSM Server installed? On both nodes, on one of the nodes or on a different machine? Also, should the TSM client be installed on both nodes? Any help is appreciated. Mario IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
TSM version 6.x?
I remember some discussions about some new features that might be included in TSM 6.x whenever it comes out. Wasn't one of those possible features something to do with data de-duplication? We are in the very very early stages of looking at de-dup products and if TSM can do what we need then it might make in the list. It would be a year or more before we implemented anything any way. thanks David Tyree Interface Analyst South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Windows client failing more VSS request issues
Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Re: DSMC return codes broken in 5.4?
Hi Andrew, Is there a query to check how much data was migrated from disk to tape every night? We copy from disk to remote tape and something of the data from disk spills into local tape. I am looking for a query to tell me how of the data is spilled into local tape? I can search the actlog but I'm looking to write a report that would outline an estimate for over a month Thanks Please let me know -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: 2008, August, 13 12:14 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DSMC return codes broken in 5.4? First, run the query outside of a script to confirm the behavior, like this: dsmc q b c:\file.txt echo %errorlevel% If the errorlevel is 8, that would confirm that the script is not at issue. Next check your dsmerror.log for any warning messages that coincide with the time you ran the query. If I were a betting man, my money would say you are hitting the infamous ANS1009W DRM registry problem. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.html 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 ADSM-L@VM.MARIST.EDU wrote on 08/12/2008 03:11:06 PM: I have a script that was tested in 5.3, but has been moved to a 5.4 client on windows. Where 'dsmc q backup c:\file.txt' would return 0 if there was a backup and 8 if there was not, it just returns 8. Anyone seen this weirdness? +- +- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +- +- ___ This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.
Re: Windows client failing more VSS request issues
Hate to be an old patoot, did you reboot to see if you could reproduce have you applied the VSS hotfix for win2k3? I don't usually have the recurring error on our systems afterwards. On one I did, and also applied the 5.5.1.0 client code too, and haven't had the issue since. thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
SV: Windows client failing more VSS request issues
Hi Tim Have you check the event log in Windows and also try VSSAdmin to see if VSS Works OK. I'm suggesting that you look on MS Website. This page can help you to test your MS Volume Shadow Copy Services and see if it works OK. http://technet.microsoft.com/en-us/library/cc754968.aspx Cheers Christian Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Timothy Hughes [EMAIL PROTECTED] Skickat: den 14 augusti 2008 16:36 Till: ADSM-L@VM.MARIST.EDU Ämne: Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Re: TSM version 6.x?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tyree, David I remember some discussions about some new features that might be included in TSM 6.x whenever it comes out. Wasn't one of those possible features something to do with data de-duplication? We are in the very very early stages of looking at de-dup products and if TSM can do what we need then it might make in the list. It would be a year or more before we implemented anything any way. Dedupe will be in TSM 6.1, but initially only for file-based device class storage pools. Tape and disk-based storage pools are being looked into, but nothing concrete has been planned yet. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com
Re: TSM version 6.x?
Dedup for devclass file storage pools only may not be correct - -- Original message from Mark Stapleton [EMAIL PROTECTED]: -- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tyree, David I remember some discussions about some new features that might be included in TSM 6.x whenever it comes out. Wasn't one of those possible features something to do with data de-duplication? We are in the very very early stages of looking at de-dup products and if TSM can do what we need then it might make in the list. It would be a year or more before we implemented anything any way. Dedupe will be in TSM 6.1, but initially only for file-based device class storage pools. Tape and disk-based storage pools are being looked into, but nothing concrete has been planned yet. -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com
Re: Windows client failing more VSS request issues
Lisa Thanks, I'll have talk to the user about rebooting and applying VSS hotfixes for win2k3 I don't which ones to apply. If those don't work I will apply the 5.5.1.0 code. Thanks again Tim Laughlin, Lisa wrote: Hate to be an old patoot, did you reboot to see if you could reproduce have you applied the VSS hotfix for win2k3? I don't usually have the recurring error on our systems afterwards. On one I did, and also applied the 5.5.1.0 client code too, and haven't had the issue since. thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Total amount of data migrated
Here is a hairy unix command that gets the information from the actlog and
outputs in gigabytes: (Just use begindate, enddate, endtime, enddate
options to set the time frame.
dsmadmc -se=tsmserver -tab q act begind=-1 msgno=0986 s='migration' |
grep bytes | sed 's/^.*total of //' | sed 's/ bytes.*$//' | tr -d ',' |
awk '{sum=$0 + sum} END {print sum/1024/1024/1024}'
Also works for backup stg processes
d -se=tsmserver -tab q act begind=-1 msgno=0986 s='backup storage' |
grep bytes | sed 's/^.*total of //' | sed 's/ bytes.*$//' | tr -d ',' |
awk '{sum=$0 + sum} END {print sum/1024/1024/1024}'
Regards,
Shawn
Shawn Drew
Internet
[EMAIL PROTECTED]
Sent by: ADSM-L@VM.MARIST.EDU
08/14/2008 10:47 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] DSMC return codes broken in 5.4?
Hi Andrew,
Is there a query to check how much data was migrated from disk to tape
every night?
We copy from disk to remote tape and something of the data from disk
spills into local tape.
I am looking for a query to tell me how of the data is spilled into
local tape? I can search the actlog but I'm looking to write a report
that would outline an estimate for over a month
Thanks
Please let me know
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: 2008, August, 13 12:14 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] DSMC return codes broken in 5.4?
First, run the query outside of a script to confirm the behavior, like
this:
dsmc q b c:\file.txt
echo %errorlevel%
If the errorlevel is 8, that would confirm that the script is not at
issue.
Next check your dsmerror.log for any warning messages that coincide with
the time you ran the query. If I were a betting man, my money would say
you are hitting the infamous ANS1009W DRM registry problem.
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail:
[EMAIL PROTECTED]
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html
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 ADSM-L@VM.MARIST.EDU wrote on 08/12/2008
03:11:06 PM:
I have a script that was tested in 5.3, but has been moved to a 5.4
client on windows. Where 'dsmc q backup c:\file.txt' would return 0 if
there was a backup and 8 if there was not, it just returns 8.
Anyone seen this weirdness?
+-
+-
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+-
+-
___
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations.
Any distribution, use or copying of this e-mail or the information it
contains by other than an intended recipient is unauthorized.
If you received this e-mail in error, please advise me (by return e-mail
or otherwise) immediately.
Ce courrier électronique est confidentiel et protégé. L'expéditeur ne
renonce pas aux droits et obligations qui s'y rapportent.
Toute diffusion, utilisation ou copie de ce message ou des renseignements
qu'il contient par une personne autre que le (les) destinataire(s)
désigné(s) est interdite.
Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser
immédiatement, par retour de courrier électronique ou par un autre moyen.
This message and any attachments (the message) is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: DSMC return codes broken in 5.4?
How about a select into the summary table: Select entity, sum(bytes)/1024/1024/1024 as 'GB Migrated' from summary where activity='MIGRATION' and start_time'2008-08-13 22:00' and end_time'2008-08-14 06:00' group by entity Orville Lantto -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Killam, Perpetua Sent: Thursday, August 14, 2008 9:48 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DSMC return codes broken in 5.4? Hi Andrew, Is there a query to check how much data was migrated from disk to tape every night? We copy from disk to remote tape and something of the data from disk spills into local tape. I am looking for a query to tell me how of the data is spilled into local tape? I can search the actlog but I'm looking to write a report that would outline an estimate for over a month Thanks Please let me know -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: 2008, August, 13 12:14 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DSMC return codes broken in 5.4? First, run the query outside of a script to confirm the behavior, like this: dsmc q b c:\file.txt echo %errorlevel% If the errorlevel is 8, that would confirm that the script is not at issue. Next check your dsmerror.log for any warning messages that coincide with the time you ran the query. If I were a betting man, my money would say you are hitting the infamous ANS1009W DRM registry problem. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.html 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 ADSM-L@VM.MARIST.EDU wrote on 08/12/2008 03:11:06 PM: I have a script that was tested in 5.3, but has been moved to a 5.4 client on windows. Where 'dsmc q backup c:\file.txt' would return 0 if there was a backup and 8 if there was not, it just returns 8. Anyone seen this weirdness? +- +- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +- +- ___ This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Re: Windows client failing more VSS request issues
You'll have to request it from MS-- it's name is below- if you search for the KB you should be able to find it. Get the one for x64 while you're at it too, if you have any 64 bit servers WindowsServer2003-KB934016-x86-ENU.exe thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 10:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows client failing more VSS request issues Lisa Thanks, I'll have talk to the user about rebooting and applying VSS hotfixes for win2k3 I don't which ones to apply. If those don't work I will apply the 5.5.1.0 code. Thanks again Tim Laughlin, Lisa wrote: Hate to be an old patoot, did you reboot to see if you could reproduce have you applied the VSS hotfix for win2k3? I don't usually have the recurring error on our systems afterwards. On one I did, and also applied the 5.5.1.0 client code too, and haven't had the issue since. thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Different nodes backing up under same name
I have a situation that I can't quite get my head around. It may not be do-able, however I thought I would ask.. I have a department that wishes to back all of their Windows lab machines under the name of their main server. It already works, as the NODENAME of each lab machine has been changed to the main server name, and the passwords are consistent. The filespace names are unique on the main server, so that is working as well. The main problem I am having is trying to schedule mess. They are behind a firewall, so they are trying to use polling, however when they attempt to run the polled schedule, the server tells them that the schedule has already run (because one of the other clients ran it first). Is there even a way to do this with the scheduler, or should I have each client run a windows schedule instead? Thanks in advance for any advice. Bob
Re: SV: Windows client failing more VSS request issues
There is a thread on another forum about this: Yes - there is a strong potential the Dll files in the registry have become corrupt or removed. Since Vss issues are Microsoft issues - have your SA re-apply SP2 from CD, then re-register the necessary Dll files associated with System state writers - also = run a Ntbackup against system state. If all works then its a TSM issue. If you execute vssadmin list writers from the C prompt and it returns nothing - then you have to re-registry ALL the DLLs associated with system state. The same thread then mentions the procedure used to resolve their problem: According to Microsoft Premier Support this is the correct procedure to follow when re-registering the Volume Shadow Copy service DLL's. Open a command prompt session CD to Windows\System32 Net stop vss Net stop swprv regsvr32 ole32.dll regsvr32 vss_ps.dll Vssvc /Register regsvr32 /i swprv.dll regsvr32 /i eventcls.dll regsvr32 es.dll regsvr32 stdprov.dll regsvr32 vssui.dll regsvr32 msxml.dll regsvr32 msxml3.dll regsvr32 msxml4.dll Reboot your server. After reboot, open a command prompt and run: vssadmin list writers Ensure that all your writers are displayed w/o errors. Jeff Hi Tim Have you check the event log in Windows and also try VSSAdmin to see if VSS Works OK. I'm suggesting that you look on MS Website. This page can help you to test your MS Volume Shadow Copy Services and see if it works OK. http://technet.microsoft.com/en-us/library/cc754968.aspx Cheers Christian Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Timothy Hughes [EMAIL PROTECTED] Skickat: den 14 augusti 2008 16:36 Till: ADSM-L@VM.MARIST.EDU Ämne: Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Re: SV: Windows client failing more VSS request issues
Hi Christian,
Thanks for your Reply and the link also, I did do a vssadmin list
writers not sure if part of the MS VSS test and it showed the
following. I am going to check with the Client about the VSS Hotfixes
that was suggested.
Thanks again!
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {12a259f2-0085-43d6-bc40-a52d4642841f}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b3fe7d96-bedd-47b8-94a9-6b3df02abf9e}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {847be3ca-37c6-49d1-b94d-75b685d41fd0}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {a42a078c-427f-49ee-ae88-f12054acd26c}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f9eaec31-24e6-454f-bcee-92fc2dee87ba}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Service Writer'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {6017d216-3f66-472e-a5ca-c47d20b8e67b}
State: [1] Stable
Last error: Non-retryable error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {6df2eeb9-6756-4f24-a07f-13397244fcb8}
State: [1] Stable
Last error: No error
Christian Svensson wrote:
Hi Tim
Have you check the event log in Windows and also try VSSAdmin to see if VSS
Works OK.
I'm suggesting that you look on MS Website.
This page can help you to test your MS Volume Shadow Copy Services and see if
it works OK.
http://technet.microsoft.com/en-us/library/cc754968.aspx
Cheers
Christian
Från: ADSM: Dist Stor Manager [EMAIL PROTECTED] för Timothy Hughes [EMAIL
PROTECTED]
Skickat: den 14 augusti 2008 16:36
Till: ADSM-L@VM.MARIST.EDU
Ämne: Windows client failing more VSS request issues
Hello all,
We have a Windows 2003 client that failing with the following message in
the client error.log. Has anyone had this problem
with a 5.5.0.2 Windows Client?
'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error
code: 4353.
08/14/2008 00:16:43 ANS1228E Sending of object
'NOGICIANP2\SystemState\NULL\System State\SystemState' failed
08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS
request. For more information, see the TSM client error log.
08/14/2008 00:16:43 ANS1375E The snapshot operation failed.
08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS
request. For more information, see the TSM client error log.
08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return
code = 12.
08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System
State\0\SystemState' Id:0-836409676
08/14/2008 10:06:00 ANS2054E Operating system error 13: d.
08/14/2008 10:06:00 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Unable to lock local repository
TSM return code : 101
TSM file : vssback.cpp (6353)
08/14/2008 10:06:00 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Verifying Local Backups Failed!
TSM return code : 101
TSM file : vssback.cpp (5725)
08/14/2008 10:06:02 VssRequestor::checkWriterStatus:
VssRequestor::checkWriterStatus() failed with
hr=VSS_E_WRITERERROR_NONRETRYABLE
08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services
writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not
valid for the current operation or cannot be determined. The last error
reported is '800423f4'.
Also,
When I ran a Manual backup of the System State and recieved the following
Ans5258e - And error occured Initializing a VSS request
Ans1375E - The snapshot operation failed
TSM Server 5.5.0.3
Aix 5.3
Windows 2003 sp1 Client/TSM Client 5.5.0.2
Thanks for any help, comments, suggestions in advance!
Re: Windows client failing more VSS request issues
Thanks..Again Lisa for your help! Laughlin, Lisa wrote: You'll have to request it from MS-- it's name is below- if you search for the KB you should be able to find it. Get the one for x64 while you're at it too, if you have any 64 bit servers WindowsServer2003-KB934016-x86-ENU.exe thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 10:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows client failing more VSS request issues Lisa Thanks, I'll have talk to the user about rebooting and applying VSS hotfixes for win2k3 I don't which ones to apply. If those don't work I will apply the 5.5.1.0 code. Thanks again Tim Laughlin, Lisa wrote: Hate to be an old patoot, did you reboot to see if you could reproduce have you applied the VSS hotfix for win2k3? I don't usually have the recurring error on our systems afterwards. On one I did, and also applied the 5.5.1.0 client code too, and haven't had the issue since. thanks! lisa -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Thursday, August 14, 2008 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows client failing more VSS request issues Hello all, We have a Windows 2003 client that failing with the following message in the client error.log. Has anyone had this problem with a 5.5.0.2 Windows Client? 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed with error code: 4353. 08/14/2008 00:16:43 ANS1228E Sending of object 'NOGICIANP2\SystemState\NULL\System State\SystemState' failed 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1375E The snapshot operation failed. 08/14/2008 00:16:43 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log. 08/14/2008 00:16:43 ANS1512E Scheduled event 'MIDNIGHT' failed. Return code = 12. 08/14/2008 10:06:00 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0-836409676 08/14/2008 10:06:00 ANS2054E Operating system error 13: d. 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Unable to lock local repository TSM return code : 101 TSM file : vssback.cpp (6353) 08/14/2008 10:06:00 ANS5250E An unexpected error was encountered. TSM function name : verifyLocalBackups() TSM function : Verifying Local Backups Failed! TSM return code : 101 TSM file : vssback.cpp (5725) 08/14/2008 10:06:02 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE 08/14/2008 10:06:02 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'. Also, When I ran a Manual backup of the System State and recieved the following Ans5258e - And error occured Initializing a VSS request Ans1375E - The snapshot operation failed TSM Server 5.5.0.3 Aix 5.3 Windows 2003 sp1 Client/TSM Client 5.5.0.2 Thanks for any help, comments, suggestions in advance!
Re: Updated VS Backed Up
Unfortunately that didn't work when I tried a backup. Anyone else with an idea on how to get a testflag into a client option set? Invalid trace flag: TESTFLAGS=DISABLEATTRIBUPDATE Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/14/2008 02:37 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Updated VS Backed Up Ok, as I said I was a little bit tired after an 14 hour shift.. Your question was Does anyone know how to get a testflag into a client option set? tsm: def clientopt test TRACEFLAGS -testflags=DISABLEATTRIBUPDATE ANR2050I DEFINE CLIENTOPT: Option TRACEFLAGS defined in optionset TEST. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: den 13 augusti 2008 16:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Updated VS Backed Up Skipntpermissions addresses a different issue. DISABLEATTRIBUPDATE addresses permissions that are saved in the TSM DB I believe as opposed to the ntfs security which stores the metadata in the storagepool. Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/12/2008 06:29 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Updated VS Backed Up Hi, Check 'Skipntpermissions' in the client manual. There could be a traceclass too but I am too tired to look.. Thanks Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Drew Sent: den 13 augusti 2008 00:14 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Updated VS Backed Up testflag DISABLEATTRIBUPDATE I read this tsmblog article: http://tsmblog.org/serendipity/index.php?/archives/81-UPDATED-vs-BACKED- UP.html I remember reading about this testflag on the IBM Support site and I thought I remember reading about it on adsm-l somewhere, but searching Google or IBM for DISABLEATTRIBUPDATE doesn't return anything anymore. Anyway, for posterity: By default TSM will not keep a history of permission changes, which doesn't make sense to me! In the past I've had to do complete system restores after a virus messed up permissions. This testflag in the dsm.opt file will disable that and backup the file for any change (including permission changes) Does anyone know how to get a testflag into a client option set? (My last resort will be to try adding -testflags=DISABLEATTRIBUPDATE to the options of all my schedules) Regards, Shawn Shawn Drew This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Different nodes backing up under same name
I don't think there is a way to get around the schedule already running issue with a single system name for multiple servers. I'm surprised the TSM server doesn't balk about multiple backups running with the same node name at the same time. Scheduling a dsmc backup inc through windows scheduler would be one way to eliminate that. But they would all try to run at the same time, then they would run at the same time. Doesn't each successive backup expire the data from the other systems ? Or does it ignore it because it's a different filespace ? Sounds messy. But could be a very interesting licensing loophole ;-) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth Sent: Thursday, August 14, 2008 12:36 PM To: ADSM-L@VM.MARIST.EDU Subject: Different nodes backing up under same name I have a situation that I can't quite get my head around. It may not be do-able, however I thought I would ask.. I have a department that wishes to back all of their Windows lab machines under the name of their main server. It already works, as the NODENAME of each lab machine has been changed to the main server name, and the passwords are consistent. The filespace names are unique on the main server, so that is working as well. The main problem I am having is trying to schedule mess. They are behind a firewall, so they are trying to use polling, however when they attempt to run the polled schedule, the server tells them that the schedule has already run (because one of the other clients ran it first). Is there even a way to do this with the scheduler, or should I have each client run a windows schedule instead? Thanks in advance for any advice. Bob
Re: Updated VS Backed Up
On Aug 14, 2008, at 2:53 PM, Shawn Drew wrote: Unfortunately that didn't work when I tried a backup. Anyone else with an idea on how to get a testflag into a client option set? Invalid trace flag: TESTFLAGS=DISABLEATTRIBUPDATE With no information anywhere as to the existence or effects of such a testflag, it is not worth pursuing. Richard Sims
Re: Different nodes backing up under same name
Your posting doesn't mention potential use of client-node proxy. Did you review and discard that facility as not suitable for some reason? Richard Sims
Re: Different nodes backing up under same name
On Thu, Aug 14, 2008 at 02:16:55PM -0500, Ochs, Duane wrote: I don't think there is a way to get around the schedule already running issue with a single system name for multiple servers. I'm surprised the TSM server doesn't balk about multiple backups running with the same node name at the same time. I think it is because the systems seem to 'poll' at slightly different rates, so some win, some loose. Scheduling a dsmc backup inc through windows scheduler would be one way to eliminate that. That is what I figured, but I don't have any control over the systems, they are in a different department than ours, so I wanted to make it as simple as possible for the administrator to deal with. But they would all try to run at the same time, then they would run at the same time. Sure, it has happened before, and I have seen the messages about 'multiple schedulers running', it is rare however. Doesn't each successive backup expire the data from the other systems ? Or does it ignore it because it's a different filespace ? It seems to ignore it. Sounds messy. But could be a very interesting licensing loophole ;-) We are trying to do it for accounting reasons. These are 'customers' and we bill by 'client node' with a minimum charge per month. We consider these desktop machines for purposes of licensing. (however, don't get me started on the Tivoli License Nightmare (TM)) Bob
Re: Different nodes backing up under same name
On Thu, Aug 14, 2008 at 03:30:12PM -0400, Richard Sims wrote: Your posting doesn't mention potential use of client-node proxy. Did you review and discard that facility as not suitable for some reason? When I looked at it, it didn't seem to apply to this situation, or maybe too complicated for the remote administrator. I will look at this application again and see if I can understand it better. Thanks for the advice. Bob
Fw: Updated VS Backed Up
The error you're getting is about what's after the '=' and not the line itself. It's not liking the testflag that you're indicating. Does that syntax work correctly from a command line? Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 08/14/2008 04:29 PM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 08/14/2008 02:53:30 PM: [image removed] Re: Updated VS Backed Up Shawn Drew to: ADSM-L 08/14/2008 02:55 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager. Unfortunately that didn't work when I tried a backup. Anyone else with an idea on how to get a testflag into a client option set? Invalid trace flag: TESTFLAGS=DISABLEATTRIBUPDATE Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED]
Re: Fw: Updated VS Backed Up
This works from the command line: dsmc i -testflags=DISABLEATTRIBUPDATE Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 08/14/2008 04:31 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Fw: Updated VS Backed Up The error you're getting is about what's after the '=' and not the line itself. It's not liking the testflag that you're indicating. Does that syntax work correctly from a command line? Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 08/14/2008 04:29 PM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 08/14/2008 02:53:30 PM: [image removed] Re: Updated VS Backed Up Shawn Drew to: ADSM-L 08/14/2008 02:55 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager. Unfortunately that didn't work when I tried a backup. Anyone else with an idea on how to get a testflag into a client option set? Invalid trace flag: TESTFLAGS=DISABLEATTRIBUPDATE Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: Different nodes backing up under same name
Bob, We have some situations where we want to do something similar. What I have found to be the simplest is to set up each machine as if they were going to be backed up individually, with dsm.opt files that reference their unique machine names. This opt file is used for the dsmcad and scheduler services. Then I create a 2nd opt file on each machine that uses the common nodename I want all the data stored under. Then rather than scheduling an incremental backup, I create a schedule(s) that are defined as command action, with the object pointing to a simple batch file that I have copied to each machine. This script runs the dsmc i command using the -optfile=2nd optfile parameter. This way each machine is easily scheduled but the data all gets backed up under the common nodename. I have examples if you want to email me offline. Steve Schaub Systems Engineer, Windows Blue Cross Blue Shield of Tennessee -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth Sent: Thursday, August 14, 2008 1:36 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Different nodes backing up under same name I have a situation that I can't quite get my head around. It may not be do-able, however I thought I would ask.. I have a department that wishes to back all of their Windows lab machines under the name of their main server. It already works, as the NODENAME of each lab machine has been changed to the main server name, and the passwords are consistent. The filespace names are unique on the main server, so that is working as well. The main problem I am having is trying to schedule mess. They are behind a firewall, so they are trying to use polling, however when they attempt to run the polled schedule, the server tells them that the schedule has already run (because one of the other clients ran it first). Is there even a way to do this with the scheduler, or should I have each client run a windows schedule instead? Thanks in advance for any advice. Bob Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
