Help tracking down spurious Failed 12 errors
When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council’s systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Help tracking down spurious Failed 12 errors
Do a q act s=clientname for the backup times in question. You may see something there. Also, check the windows event log if the clients are windows. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Wednesday, August 17, 2011 4:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help tracking down spurious Failed 12 errors When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council's systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. When you looked through your dsmerror.log and dsmsched.log, you couldnt see any failed files at all? Nor any issues with backuping specific filespaces (such as parts of systemstate). Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Lee, Gary D. g...@bsu.edu Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 12:42 Ärende: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Do a q act s=clientname for the backup times in question. You may see something there. Also, check the windows event log if the clients are windows. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Wednesday, August 17, 2011 4:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help tracking down spurious Failed 12 errors When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council's systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Help tracking down spurious Failed 12 errors
Does the TSM client dsmsched.log indicate that the backups actually ran (or attempted to run)? If not, check the TSM server activity log for the duration of the backup window for messages related to this node and scheduled event. If the dsmsched.log error shows that the backup ran, check it as well as the dsmerror.log again. I never say never, but I am very hard pressed to think that the RC 12's are begin generated with no error whatsoever being identified in the dsmerror.log file, if not dsmsched.log. Especially check the ending statistics for the backup where it shows whether the backup completed successfully. If it says it completed successfully, then check your system for another scheduler, in case there are multiple schedulers and a different scheduler is having the problem. What is the scheduled action? Is it INCREMENTAL? Or something else? For example, if the scheduled action is COMMAND and it launches some script to perform the backup, then note that if the script does not exit with return code 0, the event will be treated as failed and the return code shown by QUERY EVENT will be that from the script (which would be a 12 in this case). If you use a PRESCHEDULECMD option as well, and the PRESCHEDULECMD operation does not end with return code 0, then this will also cause the backup to fail; in this case, though, the scheduled operation will not run. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2011-08-17 04:40:50: From: Davis, Adrian adrian.da...@lewisham.gov.uk To: ADSM-L@vm.marist.edu Date: 2011-08-17 04:44 Subject: Help tracking down spurious Failed 12 errors Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council’s systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. In the cases you mention, I would expect the return code to be 4, not 12, provided that there are no other warnings or errors that would cause a higher return code. RC 4 is very specific: except for some skipped files, the backup was otherwise successful. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2011-08-17 06:06:29: From: Daniel Sparrman daniel.sparr...@exist.se To: ADSM-L@vm.marist.edu Date: 2011-08-17 07:04 Subject: Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. When you looked through your dsmerror.log and dsmsched.log, you couldnt see any failed files at all? Nor any issues with backuping specific filespaces (such as parts of systemstate). Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Lee, Gary D. g...@bsu.edu Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 12:42 Ärende: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Do a q act s=clientname for the backup times in question. You may see something there. Also, check the windows event log if the clients are windows. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Wednesday, August 17, 2011 4:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help tracking down spurious Failed 12 errors When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council's systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
The most common reason I see Failed 12 at our customers is when parts of the systemstate backup fails. I just checked a customer TSM server and they had several Windows boxes failing with Failed 12. When going through the activity log, there isnt an actually error, but I can see that it's backing up 6 parts of the systemstate object. The result from the backup says 4 objects where successfully backed up, and 2 objects failed. Unfortunately, the activity log doesnt tell me which part of the systemstate backup that failed, only that it tried backing them up. I have no access atm to the dsmerror.log / dsmsched.log so I cannot tell you what kind of error (if any) to look for. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Andrew Raibeck stor...@us.ibm.com Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 14:10 Ärende: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. In the cases you mention, I would expect the return code to be 4, not 12, provided that there are no other warnings or errors that would cause a higher return code. RC 4 is very specific: except for some skipped files, the backup was otherwise successful. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2011-08-17 06:06:29: From: Daniel Sparrman daniel.sparr...@exist.se To: ADSM-L@vm.marist.edu Date: 2011-08-17 07:04 Subject: Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. When you looked through your dsmerror.log and dsmsched.log, you couldnt see any failed files at all? Nor any issues with backuping specific filespaces (such as parts of systemstate). Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Lee, Gary D. g...@bsu.edu Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 12:42 Ärende: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Do a q act s=clientname for the backup times in question. You may see something there. Also, check the windows event log if the clients are windows. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Davis, Adrian Sent: Wednesday, August 17, 2011 4:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Help tracking down spurious Failed 12 errors When using query event to check my scheduled backups, I seem to be getting Failed 12 errors for a couple of backups which appear to have been successful (This occurs every day for the same servers). I've checked the client schedule and error logs - but there is no record of an error and all messages are what I would expect to see for a successful backup. Any ideas where else I should look? Many Thanks, =Adrian= DISCLAIMER This message is confidential and intended solely for the use of the individual or entity it is addressed to. If you have received it in error, please contact the sender and delete the e-mail. Please note that we may monitor and check emails to safeguard the Council network from viruses, hoax messages or other abuse of the Council's systems. To see the full version of this disclaimer please visit the following address: http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm For advice and assistance about online security and protection from internet threats visit the Get Safe Online website at http://www.getsafeonline.org
Re: Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
Hi Daniel, Ah, yes. In the case of system state backup, if you are using client versions 5.5 or older, or you are using version 6.1.3.0 or older, then yes, a skipped system state file will cause the return code 12. This is because it is not simply a case of a single file being missed; rather, the entire system state backup is no good because a missing system state file means the system state is not integral. This is a situation the Windows system owner needs to correct. Ideally the missing file will be reinstated or the system state metadata corrected to no longer include that file if it does not belong on the system. Having said that, we have seen a large number of cases with missing system state files that resulted in some code changes. Starting with version 6.1.3.1 and higher, as well as 6.2.0.0 and higher, TSM has been modified to tolerate missing System Writer files (System Writer is the largest portion of the system state and is the usual source of missing files). You will still get an error message that says the file is missing, but the system state backup should otherwise continue, and the RC will be 8 (assuming there are no further, more severe errors that occurred during the backup). References: Missing system writer files: http://www.ibm.com/support/docview.wss?uid=swg21419884 http://www.ibm.com/support/docview.wss?uid=swg1IC65828 Other similar issues: Missing Windows Deployment Service (WDS) directory: http://www.ibm.com/support/docview.wss?uid=swg1IC67043 Missing event log file (Windows 2003 x64 only): http://www.ibm.com/support/docview.wss?uid=swg1IC68676 Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2011-08-17 07:34:11: From: Daniel Sparrman daniel.sparr...@exist.se To: ADSM-L@vm.marist.edu Date: 2011-08-17 08:32 Subject: Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu The most common reason I see Failed 12 at our customers is when parts of the systemstate backup fails. I just checked a customer TSM server and they had several Windows boxes failing with Failed 12. When going through the activity log, there isnt an actually error, but I can see that it's backing up 6 parts of the systemstate object. The result from the backup says 4 objects where successfully backed up, and 2 objects failed. Unfortunately, the activity log doesnt tell me which part of the systemstate backup that failed, only that it tried backing them up. I have no access atm to the dsmerror.log / dsmsched.log so I cannot tell you what kind of error (if any) to look for. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Andrew Raibeck stor...@us.ibm.com Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 14:10 Ärende: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. In the cases you mention, I would expect the return code to be 4, not 12, provided that there are no other warnings or errors that would cause a higher return code. RC 4 is very specific: except for some skipped files, the backup was otherwise successful. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/ Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2011-08-17 06:06:29: From: Daniel Sparrman daniel.sparr...@exist.se To: ADSM-L@vm.marist.edu Date: 2011-08-17 07:04 Subject: Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Failed 12 is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have access to the file. When you looked through your dsmerror.log and dsmsched.log, you couldnt see any failed files at all? Nor any issues with backuping specific
Re: Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
On Aug 17, 2011, at 7:34 AM, Daniel Sparrman wrote: ... I have no access to the dsmerror.log / dsmsched.log so I cannot tell you what kind of error (if any) to look for. This is a common situation in most most sites, where the TSM administrator is not afforded access to client systems, and yet is usually the only person with the knowledge to make sense of TSM processing issues. Sites might consider instituting a standard client schedule model where a POSTSchedulecmd transmits a copy of the dsmerror.log and dsierror.log to a central location which allows such review by the TSM specialist. Conveyance might be via scp, NFS, or even a 'dsmc archive' with a modest retention period and Set Access permission. This should be an easy sell in most environments, given that logs are typically ignored by client administrators, and yet often reveal files which everyone thinks are being backed up but never are (as in Linux LANG/locale conflicts). Richard Sims
Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors
I fully agree with you Richard, and we do have a central log storage at this customer. However, in this case it's a simple matter of only being able to access the TSM server via remote HTTP (i'm not onsite) ;) Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Richard Sims r...@bu.edu Sänt av: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Datum: 08/17/2011 14:59 Ärende: Re: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious Failed 12 errors On Aug 17, 2011, at 7:34 AM, Daniel Sparrman wrote: ... I have no access to the dsmerror.log / dsmsched.log so I cannot tell you what kind of error (if any) to look for. This is a common situation in most most sites, where the TSM administrator is not afforded access to client systems, and yet is usually the only person with the knowledge to make sense of TSM processing issues. Sites might consider instituting a standard client schedule model where a POSTSchedulecmd transmits a copy of the dsmerror.log and dsierror.log to a central location which allows such review by the TSM specialist. Conveyance might be via scp, NFS, or even a 'dsmc archive' with a modest retention period and Set Access permission. This should be an easy sell in most environments, given that logs are typically ignored by client administrators, and yet often reveal files which everyone thinks are being backed up but never are (as in Linux LANG/locale conflicts). Richard Sims
TSM 6.2 / Amazon S3
I understand that it does not exist natively. Is there a way to do it via a storage gateway? Other solution? Thanks again. Eric No, this doesn't exist natively. If you were interested in doing this with TSM, take a look at Riverbed Whitewater. Using it as a primary storage pool doesn't seem to be a best practice, however. Regards, Shawn Shawn Drew Internet ethomp...@itlifeline.net Sent by: ADSM-L@VM.MARIST.EDU 08/16/2011 02:38 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] TSM 6.2 / Amazon S3
Re: TSM 6.2 / Amazon S3
On 08/17/2011 12:21 PM, Eric Thompson wrote: I understand that it does not exist natively. Is there a way to do it via a storage gateway? Other solution? Well, there are a variety of Make a filesystem based on S3 projects, for any platform you care to name. You could put FILE devclasses on any of those. The notion makes me shudder, though. - Allen S. Rout
Re: TSM 6.2 / Amazon S3
That is why I mentioned Riverbed Whitewater.It allows you to connect TSM to a number of cloud services using the file device class. Regards, Shawn Shawn Drew Internet ethomp...@itlifeline.net Sent by: ADSM-L@VM.MARIST.EDU 08/17/2011 12:21 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] TSM 6.2 / Amazon S3 I understand that it does not exist natively. Is there a way to do it via a storage gateway? Other solution? Thanks again. Eric No, this doesn't exist natively. If you were interested in doing this with TSM, take a look at Riverbed Whitewater. Using it as a primary storage pool doesn't seem to be a best practice, however. Regards, Shawn Shawn Drew Internet ethomp...@itlifeline.net Sent by: ADSM-L@VM.MARIST.EDU 08/16/2011 02:38 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] TSM 6.2 / Amazon S3 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.
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.
Anyone using Power Mobility for TSM environment?
Hello TSMers, Is anyone using AIX power mobility for their TSM environment with hba's for disk and all tsm traffic using the network to a NFS(Dat Domain appliance)? We currently have our tsm server on it's own P550, physical server and have embraced virtualization and would like to put a new server in a virtualized environment. We recently created a new TSM server to test the new DB2 version of TSM 6.2.3.0 and also to provide some relief for our current TSM production environment. The new server is AIX oslevel 7.1 and we just installed TSM 6.2.3.0 on it. Thank You, Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
unsubscribe
Chris Anderson Enterprise BAR Senior Engineer ACS Inc. - A Xerox Company Office: 214.841.8158 Mobile: 469.834.8037
Re: Anyone using Power Mobility for TSM environment?
I think you may be the first shop to attempt this. Good luck! On 8/17/11, Nancy L Leugemors leugemors.na...@healthnow.org wrote: Hello TSMers, Is anyone using AIX power mobility for their TSM environment with hba's for disk and all tsm traffic using the network to a NFS(Dat Domain appliance)? We currently have our tsm server on it's own P550, physical server and have embraced virtualization and would like to put a new server in a virtualized environment. We recently created a new TSM server to test the new DB2 version of TSM 6.2.3.0 and also to provide some relief for our current TSM production environment. The new server is AIX oslevel 7.1 and we just installed TSM 6.2.3.0 on it. Thank You, Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- Sent from my mobile device Thank you, Bob Molerio Systems Administrator New York University ITS Computer Facilities Services/Infrastructure Level C-2 75 Third Avenue New York NY 10003-5527 email:robert.mole...@nyu.edu robert.mole...@nyu.edu
