Backup Central

Anyone else seeing:

ANR8503E A failure occurred in writing to volume

when writing to a FILE class storage pool volume defined on a Windows
share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
and the TSM server. Strangely enough, there are no entries in either
the sharing system's event log or the TSM server's event log. The
volume is changed to readonly by TSM after the error, and the writing
process (MOVE DATA) dies.

I found a reference to someone else having this problem about a year
ago, but I never saw an answer. Maybe more people have inflicted this
pain on themselves by now?

We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
little dubious.

Steve

--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com

You've checked the actlog around the time the error occurred?

You're sure that the volume was not full and no more scratch volumes
could be assigned (maxscratch)? You also checked that the Windows volume
had sufficient space for the volume (initially only the space for the
data in the volume is assigned and the volume will grow as data is
assigned to the volume)?

Met vriendelijke groet, with kind regards,

Richard van Denzel.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Steve Stackwick
Sent: 07 August 2008 19:41
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] ANR8503E

Anyone else seeing:

ANR8503E A failure occurred in writing to volume

when writing to a FILE class storage pool volume defined on a Windows
share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
and the TSM server. Strangely enough, there are no entries in either
the sharing system's event log or the TSM server's event log. The
volume is changed to readonly by TSM after the error, and the writing
process (MOVE DATA) dies.

I found a reference to someone else having this problem about a year
ago, but I never saw an answer. Maybe more people have inflicted this
pain on themselves by now?

We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
little dubious.

Steve

--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com

On Thu, Aug 7, 2008 at 2:36 PM, Richard van Denzel <RvanDenzel < at > sltn.nl> wrote:
You've checked the actlog around the time the error occurred?

Nuthin but the ANR8503E and the message that the volume is being set
to readonly.

You're sure that the volume was not full and no more scratch volumes
could be assigned (maxscratch)?

Actually, some of the volumes were empty, others were filling.

You also checked that the Windows volume
had sufficient space for the volume (initially only the space for the
data in the volume is assigned and the volume will grow as data is
assigned to the volume)?

Not sure what you mean, exactly, but probably I wasn't clear in the
OP. These are predefined FILE class volumes of 200GB.

An addtional note that just occurred to me, though. We've had this
problem periodically, a volume every month or so. No biggie, we just
changed it back to READWRITE and moved on. Now we've moved the server
and shares a half-mile farther apart (as the crow flies-- as the wire
crawls may be considerably farther), so latency must have something to
do with this issue.

Thanks for the reply!


Met vriendelijke groet, with kind regards,

Richard van Denzel.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Steve Stackwick
Sent: 07 August 2008 19:41
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] ANR8503E

Anyone else seeing:

ANR8503E A failure occurred in writing to volume

when writing to a FILE class storage pool volume defined on a Windows
share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
and the TSM server. Strangely enough, there are no entries in either
the sharing system's event log or the TSM server's event log. The
volume is changed to readonly by TSM after the error, and the writing
process (MOVE DATA) dies.

I found a reference to someone else having this problem about a year
ago, but I never saw an answer. Maybe more people have inflicted this
pain on themselves by now?

We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
little dubious.

Steve

--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com




--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com

What kind of storage is the FILECLASS on and how is it connected to the
server (SCSI, SAS, FC)? I also know a case where latency might be an
issue on a lightpath FC of 30km.

Met vriendelijke groet, with kind regards,

Richard van Denzel.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Steve Stackwick
Sent: 07 August 2008 20:47
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] ANR8503E

On Thu, Aug 7, 2008 at 2:36 PM, Richard van Denzel <RvanDenzel < at > sltn.nl>
wrote:
You've checked the actlog around the time the error occurred?

Nuthin but the ANR8503E and the message that the volume is being set
to readonly.

You're sure that the volume was not full and no more scratch volumes
could be assigned (maxscratch)?

Actually, some of the volumes were empty, others were filling.

You also checked that the Windows volume
had sufficient space for the volume (initially only the space for the
data in the volume is assigned and the volume will grow as data is
assigned to the volume)?

Not sure what you mean, exactly, but probably I wasn't clear in the
OP. These are predefined FILE class volumes of 200GB.

An addtional note that just occurred to me, though. We've had this
problem periodically, a volume every month or so. No biggie, we just
changed it back to READWRITE and moved on. Now we've moved the server
and shares a half-mile farther apart (as the crow flies-- as the wire
crawls may be considerably farther), so latency must have something to
do with this issue.

Thanks for the reply!


Met vriendelijke groet, with kind regards,

Richard van Denzel.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf
Of
Steve Stackwick
Sent: 07 August 2008 19:41
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] ANR8503E

Anyone else seeing:

ANR8503E A failure occurred in writing to volume

when writing to a FILE class storage pool volume defined on a Windows
share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
and the TSM server. Strangely enough, there are no entries in either
the sharing system's event log or the TSM server's event log. The
volume is changed to readonly by TSM after the error, and the writing
process (MOVE DATA) dies.

I found a reference to someone else having this problem about a year
ago, but I never saw an answer. Maybe more people have inflicted this
pain on themselves by now?

We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
little dubious.

Steve

--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com




--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com

On Thu, Aug 7, 2008 at 2:50 PM, Richard van Denzel <RvanDenzel < at > sltn.nl> wrote:
What kind of storage is the FILECLASS on and how is it connected to the
server (SCSI, SAS, FC)? I also know a case where latency might be an
issue on a lightpath FC of 30km.

The storage is a FC-attached EMC CX700 to a W2K3 SP2 HP w/ Emulex
HBAs. But we're not nearly 30km, more like 1, and the speed is not bad
when it's working (30MB/s).

Thanks, Richard!

Steve


Met vriendelijke groet, with kind regards,

Richard van Denzel.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Steve Stackwick
Sent: 07 August 2008 20:47
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] ANR8503E

On Thu, Aug 7, 2008 at 2:36 PM, Richard van Denzel <RvanDenzel < at > sltn.nl>
wrote:
You've checked the actlog around the time the error occurred?

Nuthin but the ANR8503E and the message that the volume is being set
to readonly.

You're sure that the volume was not full and no more scratch volumes
could be assigned (maxscratch)?

Actually, some of the volumes were empty, others were filling.

You also checked that the Windows volume
had sufficient space for the volume (initially only the space for the
data in the volume is assigned and the volume will grow as data is
assigned to the volume)?

Not sure what you mean, exactly, but probably I wasn't clear in the
OP. These are predefined FILE class volumes of 200GB.

An addtional note that just occurred to me, though. We've had this
problem periodically, a volume every month or so. No biggie, we just
changed it back to READWRITE and moved on. Now we've moved the server
and shares a half-mile farther apart (as the crow flies-- as the wire
crawls may be considerably farther), so latency must have something to
do with this issue.

Thanks for the reply!


Met vriendelijke groet, with kind regards,

Richard van Denzel.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf
Of
Steve Stackwick
Sent: 07 August 2008 19:41
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] ANR8503E

Anyone else seeing:

ANR8503E A failure occurred in writing to volume

when writing to a FILE class storage pool volume defined on a Windows
share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
and the TSM server. Strangely enough, there are no entries in either
the sharing system's event log or the TSM server's event log. The
volume is changed to readonly by TSM after the error, and the writing
process (MOVE DATA) dies.

I found a reference to someone else having this problem about a year
ago, but I never saw an answer. Maybe more people have inflicted this
pain on themselves by now?

We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
little dubious.

Steve

--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com




--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com




--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick < at > jasi.com