fidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
From: Lindsay Morris
To: ADSM-L@VM.MARIST.EDU
Date: 11/02/2011 09:22 PM
Subject:Re: [ADSM-L] Ang: Re: Help tracking down spurious "Failed
12"
Sent by:"ADSM: Dist Stor
ADSM: Dist Stor Manager" wrote on 2011-08-25
> 09:26:24:
>
> > From: Jimou
> > To: ADSM-L@vm.marist.edu
> > Date: 2011-08-26 12:15
> > Subject: Ang: Re: Help tracking down spurious "Failed 12"
> > Sent by: "ADSM: Dist Stor Manager"
> >
&g
u
> To: ADSM-L@vm.marist.edu
> Date: 2011-08-26 12:15
> Subject: Ang: Re: Help tracking down spurious "Failed 12"
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi
> I wonder why we can have a RC =12 for a skipped file in use,
> cause there http://www.dsi.up
Hi
I wonder why we can have a RC =12 for a skipped file in use,
cause there
http://www.dsi.upmc.fr/dsi/doc/stockage/clients-tsm/tsmwin/ans60012.htm
i see that it should be RC=4
But i also have a RC=12 and the only message i got is "in used file".
Someone could explain to me why it is not a RC=4
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.
>
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, a
8:32
> Subject: Ang: Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down
> spurious "Failed 12" errors
> Sent by: "ADSM: Dist Stor Manager"
>
> The most common reason I see Failed 12 at our customers is when
> parts of the systemstate backup fails.
>
> I
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&#
> "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 retur
1-08-17
04:40:50:
> From: "Davis, Adrian"
> 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"
>
> When using "query event" to check my scheduled ba
"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 c
[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 1
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 n
Joni,
I made a mistake, yours is Window 2000. You can try submitting a PMR
to ask for support. Richard Sim pointed this out for me. Thanks Richard.
"Windows NT 5.0" (WinNT 5.0)The actual, official
designation of
Windows 2000, as shows up
e snapshot operation for 'C:' failed with
error code: 653.
01/06/2008 20:03:23 ANS1228E Sending of object '\\hmpg4001\c$' failed
My feeling this 'failed 12' error is yelling more of the snapshot error
here.
Go google ANS1327W & ANS1228E and see what other advises out there
********
Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]
"Avy Wong" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
01/07/2008 09:5
The dsmerror/dsmsched.log files are the first place to go look what exactly
the Failed 12 error is. Sometimes it will say 'snapshot error', sometimes
is 'Microsoft Volume Shadow Copy error', etc., At times you can do ' q
actlog=-24 search=nodename' , to look dee
e enemy of excellence.
"ADSM: Dist Stor Manager" wrote on 01/07/2008
07:23:05 AM:
> Hello everyone,
>
> I was just wondering if anyone would happen to know what the failed 12
> error message means? And where can I find more information on why the
> client failed w
09:27 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
[ADSM-L] failed 12 error message
Hello everyone,
I was just wondering if anyone would happen to know what the failed 12
error message means? And where can I find more information on why the
cli
Hello everyone,
I was just wondering if anyone would happen to know what the failed 12
error message means? And where can I find more information on why the
client failed with this error?
Scheduled Start Actual Start Schedule Name Node
Name Status
behalf of Smith, Timothy J
Sent: Wed 5/30/2007 09:57
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Failed 12 errors
I am having a problem on Windows 2003 servers running the TSM 5.3.4.0
that gets the failed 12 errors on the backups.
05/30/2007 09:09:38 ANS5250E An unexpected error was encountered
I am having a problem on Windows 2003 servers running the TSM 5.3.4.0
that gets the failed 12 errors on the backups.
05/30/2007 09:09:38 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for cal
On Apr 25, 2007, at 1:35 PM, Gill, Geoffrey L. wrote:
I wanted to verify what folks thought this message means. It looks
to me
like it is a memory resource problem on the client node. What have
folks
recommended to resolve this type of issue?
04/24/2007 23:16:29 ANSE ntrc.cpp(928): Received
I wanted to verify what folks thought this message means. It looks to me
like it is a memory resource problem on the client node. What have folks
recommended to resolve this type of issue?
04/24/2007 23:16:29 ANSE ntrc.cpp(928): Received Win32 RC 1450
(0x05aa) from FileRead(): ReadFi
ltant
From: ADSM: Dist Stor Manager on behalf of Gill, Geoffrey L.
Sent: Wed 2/14/2007 4:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Another Failed 12
I was wondering if anyone knows if this would cause a failed 12 report.
Makes sense to me that it would NOT, b
: Another Failed 12
I was wondering if anyone knows if this would cause a failed 12 report.
Makes sense to me that it would NOT, but my common sense gets the best
of me most of the time. This file is larger than the disk pool allows
and needs to go to tape, which reports happened, but I just don&#
I was wondering if anyone knows if this would cause a failed 12 report.
Makes sense to me that it would NOT, but my common sense gets the best
of me most of the time. This file is larger than the disk pool allows
and needs to go to tape, which reports happened, but I just don't see
how that
excellence.
"ADSM: Dist Stor Manager" wrote on 01/16/2007
04:23:25 PM:
> I don't know what anyone else feels about the Failed 12 reports but to
> me there are too many ways for this to be reported with little to no
> information as to what is really wrong. Here is another
e with the failed 12 though is the real issue here. I find it
hard to believe that it is related to the ANS0106E message, although I
have been known to be wrong before. Once they update the software to fix
the message error I'll have to see if that fixes the Failed 12 too. In
the mean time I wa
Geoff -
The ANS0106E message usually indicates a missing piece in an install
or upgrade operation, and is struggling to fully operate. Your
posting doesn't indicate if you've sought that message on the TSM
Support Page (http://www-306.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageM
ackup my harddrive? How do I put it in reverse?" - ??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gill,
Geoffrey L.
Sent: Tuesday, January 16, 2007 6:23 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Failed 12 report
I don't know what anyone els
I don't know what anyone else feels about the Failed 12 reports but to
me there are too many ways for this to be reported with little to no
information as to what is really wrong. Here is another in cases I have
seen. This node has been backing up just fine for months. It seems like
the upda
of excellence.
"ADSM: Dist Stor Manager" wrote on 11/15/2006
01:12:49 PM:
> The client software was updated on the node that has been reporting
> Failed 12 to 5.3.4. It looks like there is a little more info here to go
> on but the backup is still failing. The disk has abo
The client software was updated on the node that has been reporting
Failed 12 to 5.3.4. It looks like there is a little more info here to go
on but the backup is still failing. The disk has about 180GB of data on
it but it typically stops after backing up about 50GB. Previously it
looked like the
Yet another follow-up to this. A manual backup of the specific file
where the backup stopped the past 2 nights and failed did run
successfully but later a manual backup of the entire drive failed with
the exact same error as the automated nightly backup.
ANR0444W Protocol error on session 97442 fo
> From what I understand, the TSM Ping is a rudimentary keep-alive
>function: for something that simple to have a problem, I would
>suspect networking problems of some kind, where neither the TSM
>client nor server would have knowledge of what the problem was for
>them to log an explanation.
The
On Nov 9, 2006, at 10:45 AM, Gill, Geoffrey L. wrote:
11/07/2006 22:42:41 ANR0444W Protocol error on session 85395 for node
SQL03
(WinNT) - out-of-sequence verb (type Ping)
received.(SESSION: 85395)
Well, that's an interesting one, Geoff...I haven'
> Obviously, you need to look in the server Activity Log for the
>reason, as the TSM server is "the remote host".
Not sure why I left this out of the initial posting since I had it
copied out to include. This is the only thing I can find in the activity
log that coincides with the backup. With all
On Nov 8, 2006, at 6:48 PM, Gill, Geoffrey L. wrote:
11/07/2006 22:41:52 ANS1005E TCP/IP read error on socket = 624,
errno =
10054, reason : 'An existing connection was forcibly closed by the
remote host.'.
Obviously, you need to look in the server Activity Log for the
reason, as the TSM serve
I'm trying to chase down some errors on these Failed 12 reports we've
been getting. Seems like we have an awful lot of these for what look
like different problems. In order to get something more in the log I had
them turn of quiet on this node. The message in the sched.log looks lik
Been through this message before but on Windows servers. This one is on
an HP-UX box running a 5.1.6.2 version of the client. The TSM server is
at 5.3.3.0. The TSM server logs show nothing pointing to anything more
specific than what is in the client logs. Does this look like anything
anyone has se
41 matches
Mail list logo
