ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [ADSM-L] System State Backup Error

2013-06-10 15:17:44
Subject: Re: [ADSM-L] System State Backup Error
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 10 Jun 2013 15:15:00 -0400 
Hi Andy,

The MOMLog.evt file is a different story: the problem was that the 64-bit
version of Microsoft Operations Manager specified a relative path (with
parent known to MOM but not external programs) rather than a
fully-qualified path (which an external program like TSM would need to know
to find the file). This situation is described in detail in APAR IC68676;
further, it applies only to Windows 2003 x64.

In the subject case, an entire drive cannot be accounted for in a
non-cluster environment, and that is why the system state backup does not
complete, as opposed to just skipping a file on a drive that otherwise
exists.

- Andy

____________________________________________________________________________

Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
storman AT us.ibm DOT com

IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

Online documentation:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
Documentation Central/page/Tivoli Storage Manager
Product Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
+Storage+Manager/page/Home

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2013-06-10
15:01:42:

> From: "Huebner, Andy" <andy.huebner AT ALCON DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 2013-06-10 15:04
> Subject: Re: System State Backup Error
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> We had a similar problem in the past that turned out to be a bad
> path put into the registry by a program.  The referenced file was
> added to the system backup, but the path was wrong.  You might
> search the registry for the file and see if it is a bad path.
>
> This is the error we saw when backing up the OS:
> 12/23/2010 04:27:50 ANS5250E An unexpected error was encountered.
>    TSM function name : objEnumAuditFileSub
>    TSM function      : GetBestVolumeMatch() for file 'Config\MOMLog.evt
> ' failed.
>    TSM return code   : 105
>    TSM file          : objenum.cpp (1345)
>
>
> Maybe this will help.
>
>
> Andy Huebner
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Jeanne Bruno
> Sent: Monday, June 10, 2013 12:40 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] System State Backup Error
>
> Hello.   has anyone come across this error for a drive that doesn't
exist?
>
> We have a server (Windows 2008 R2).  Not a Cluster.
> We do a SystemState backup on Sundays on it via TSM.
> And it fails with this error:
>
> DSMError.log
> 06/09/2013 18:01:19 ANS5250E An unexpected error was encountered.
>    TSM function name : AddFileToRequest
>    TSM function      : GetVolumeNameForVolumeMountPoint() for drive
> 'f:\' returned 2
>    TSM return code   : 109
>    TSM file          : vssreq.cpp (5144)
> 06/09/2013 18:01:45 ANS5250E An unexpected error was encountered.
>    TSM function name : objEnumAuditFileSub
>    TSM function      : GetBestVolumeMatch() for file '\\finland\f$
> \truecrypt-x64.sys
> ' failed.
>    TSM return code   : 105
>    TSM file          : objenum.cpp (1557)
> 06/09/2013 18:01:45 ANS5250E An unexpected error was encountered.
>    TSM function name : BaHandleSystemPostSnapshotCmd
>    TSM function      : objEnumAuditFileSub() failed
>    TSM return code   : 105
>    TSM file          : backsnap.cpp (3264)
> 06/09/2013 18:01:45 ANS5250E An unexpected error was encountered.
>    TSM function name : baHandleSnapshot
>    TSM function      : BaHandleSystemPostSnapshotCmd() failed.
>    TSM return code   : 105
>    TSM file          : backsnap.cpp (4167)
> 06/09/2013 18:01:45 ANS1327W The snapshot operation for 'FINLAND
> \SystemState\NULL\System State\SystemState' failed with error code: 105.
> 06/09/2013 18:01:45 ANS1228E Sending of object '' failed
> 06/09/2013 18:01:45 ANS4006E Error processing '': directory path not
found
> 06/09/2013 18:01:50 ANS1512E Scheduled event 'SQLDB_SUN_2K9' failed.
> Return code = 12.
>
> DSMSched.log:
> 06/09/2013 18:00:42 --- SCHEDULEREC QUERY BEGIN
> 06/09/2013 18:00:42 --- SCHEDULEREC QUERY END
> 06/09/2013 18:00:42 Next operation scheduled:
> 06/09/2013 18:00:42
> ------------------------------------------------------------
> 06/09/2013 18:00:42 Schedule Name:         SQLDB_SUN_2K9
> 06/09/2013 18:00:42 Action:                Incremental
> 06/09/2013 18:00:42 Objects:
> 06/09/2013 18:00:42 Options:               -domain="all-local -c: -
> d: -e: -g: -h: -q:"
> 06/09/2013 18:00:42 Server Window Start:   18:00:00 on 06/09/2013
> 06/09/2013 18:00:42
> ------------------------------------------------------------
> 06/09/2013 18:00:42
> Executing scheduled command now.
> 06/09/2013 18:00:43
> Executing Operating System command or script:
>    svcstop > svcstop.log
> 06/09/2013 18:00:57 --- SCHEDULEREC OBJECT BEGIN SQLDB_SUN_2K9 06/
> 09/2013 18:00:00
> 06/09/2013 18:00:57 Incremental backup of volume 'SYSTEMSTATE'
> 06/09/2013 18:01:22 ANS1959I Removing previous incomplete group
> '\System State\0\SystemState' Id:0-970590733
> 06/09/2013 18:01:23 Backing up object 'COM+ REGDB Writer' component
> 'COM+ REGDB' using shadow copy.
> 06/09/2013 18:01:23 Backing up object 'Performance Counters Writer'
> component 'Performance Counters' using shadow copy.
> 06/09/2013 18:01:23 Backing up object 'Registry Writer' component
> 'Registry' using shadow copy.
> 06/09/2013 18:01:23 Backing up object 'System Writer' component
> 'System Files' using shadow copy.
> 06/09/2013 18:01:24 Backing up object 'Task Scheduler Writer'
> component 'Tasks Store' using shadow copy.
> 06/09/2013 18:01:24 Backing up object 'VSS Metadata Store Writer'
> component 'VSS Express Writer Metadata Store' using shadow copy.
> 06/09/2013 18:01:24 Backing up object 'WMI Writer' component
> 'Windows Managment Instrumentation' using shadow copy.
> 06/09/2013 18:01:45 ANS1228E Sending of object '' failed
> 06/09/2013 18:01:45 ANS4006E Error processing '': directory path not
found
> 06/09/2013 18:01:50 --- SCHEDULEREC STATUS BEGIN
> 06/09/2013 18:01:50 --- SCHEDULEREC OBJECT END SQLDB_SUN_2K9 06/09/
> 2013 18:00:00
> 06/09/2013 18:01:50
> Executing Operating System command or script:
>    svcstart > svcstart.log
> 06/09/2013 18:01:50 ANS1512E Scheduled event 'SQLDB_SUN_2K9' failed.
> Return code = 12.
> 06/09/2013 18:01:50 Sending results for scheduled event 'SQLDB_SUN_2K9'.
> 06/09/2013 18:01:50 Results sent to server for scheduled event
> 'SQLDB_SUN_2K9'.
>
> First, there is no F:\ on the server.
> When I do the 'vssadmin list writers'.....none of the writers show an
error.
> When I google:   TSM function      :
> GetVolumeNameForVolumeMountPoint() for drive 'f:\' returned 2
> It talks about Cluster and the active/passive node.  This server is
> not a cluster.
>
> Any help is much appreciated.  Thanks.
> ____________________
> Jeannie Bruno
> Senior Systems Analyst
> jbruno AT cenhud DOT com<mailto:jbruno AT cenhud DOT com>
> Central Hudson Gas & Electric
> (845) 486-5780
>
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [ADSM-L] System State Backup Error, Jeanne Bruno
Next by Date:  Re: [ADSM-L] System State Backup Error, Jeanne Bruno
Previous by Thread:  Re: [ADSM-L] System State Backup Error, Huebner, Andy
Next by Thread:  Re: [ADSM-L] System State Backup Error, Arbogast, Warren K
Indexes:  [Date] [Thread] [Top] [All Lists]