Veritas-bu

[Veritas-bu] cannot write to TIR file: (ERR = 28)

2004-02-27 14:02:26
Subject: [Veritas-bu] cannot write to TIR file: (ERR = 28)
From: Keath.Marx AT anthem DOT com (Marx, Keath)
Date: Fri, 27 Feb 2004 14:02:26 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3FD64.3D5BC64C
Content-Type: text/plain

It is curious because I do have them excluded.  I am trying to exclude them
by Class and schedu;e

                -----Original Message-----
                From: veritas-bu-admin AT mailman.eng.auburn DOT edu@AICI On 
Behalf
Of "len boyle" <len.boyle AT sas DOT com>
                Sent: Friday, February 27, 2004 12:37 PM
                To: Marx, Keath; "'\"Dan Otto\"
<Dan.Otto AT veritas DOT com>@AICI'"; veritas-bu AT mailman.eng.auburn DOT edu
                Subject: Re: [Veritas-bu] cannot write to TIR file: (ERR =
28)


                 Keath 
                 
                Are you using an Exchange backup agent to backup up  the
exchange data bases. 
                 
                If you are then you have to exclude the files which  make up
the exchange data base from the normal backup.
                 
                If you are not then you have to shutdown the   exchange data
base at the start of the backup and then start it up after  the backup
finishes. This down time is the reason that folks spend the big  bucks for
the backup agent which allows one to backup the data base files that  are in
use. 
                You can not use an open file manager to do this  work as
there is more to the work then the otm or vsp software can handle. Also  the
exchange software can get quite  upset when it finds other  software
touching it's files. The is more so with exchange  2000 which has a virtual
filesystem which is used  for speeding  up the transfer of file handles
between exchange processes. 
                 
                len 
                 


CONFIDENTIALITY 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 or otherwise protected by law.  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.
------_=_NextPart_001_01C3FD64.3D5BC64C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2657.7=
3">
<TITLE>RE: [Veritas-bu] cannot write to TIR file: (ERR =3D 28)</TITLE>
</HEAD>
<BODY>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">It is cur=
ious because I do have them excluded.&nbsp; I am trying to exclude them b=
y</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Class and schedu=
;e</FONT></P>
<UL><UL>
<P ALIGN=3DLEFT><FONT SIZE=3D2 FACE=3D"Tahoma">-----Original Message-----=
<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> veritas-bu-admin AT mailman.eng.auburn DOT 
edu@AICI</FONT=
><B></B><B> <FONT SIZE=3D2 FACE=3D"Tahoma">On Behalf Of</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Tahoma">&quot;len boyle&quot; &lt;len.boyle AT sas DOT 
com&gt;<=
BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Friday, February 27, 2004 12:37 PM<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> Marx, Keath; &quot;'\&quot;Dan Otto\&quot; &lt;Dan.Ott=
o AT veritas DOT com&gt;@AICI'&quot;; veritas-bu AT mailman.eng.auburn DOT 
edu<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> Re: [Veritas-bu] cannot write to TIR file: (ERR=
 =3D 28)</FONT></P>
<BR>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">&nbsp;K=
eath </FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" FACE=3D"Tms Rmn">&nbsp;</FONT></P=
>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">Are you=
 using an Exchange backup agent to backup up&nbsp; the exchange data base=
s. </FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" FACE=3D"Tms Rmn">&nbsp;</FONT></P=
>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">If you =
are then you have to exclude the files which&nbsp; make up the exchange d=
ata base from the normal backup.</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" FACE=3D"Tms Rmn">&nbsp;</FONT></P=
>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">If you =
are not then you have to shutdown the&nbsp;&nbsp; exchange data base at t=
he start of the backup and then&nbsp;start it up after&nbsp; the backup f=
inishes. This down time is the reason that folks spend&nbsp;the big&nbsp;=
 bucks for the backup agent which allows one to backup the data base file=
s that&nbsp; are in use. </FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">You can=
 not use an open file manager to do this&nbsp; work as there is more to t=
he work then the otm or vsp software can handle. Also&nbsp; the exchange =
software can&nbsp;get quite&nbsp; upset when it finds other&nbsp; softwar=
e touching it's files. The is more so with exchange&nbsp; 2000&nbsp;which=
&nbsp;has a virtual filesystem which is used&nbsp; for speeding&nbsp; up =
the transfer of file handles between exchange processes. </FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" FACE=3D"Tms Rmn">&nbsp;</FONT></P=
>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tms Rmn">len</FO=
NT><FONT COLOR=3D"#000000" FACE=3D"Tms Rmn">&nbsp;</FONT></P>

<P ALIGN=3DLEFT>&nbsp;</P>
</UL></UL>
</BODY>
</HTML>

<BR>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,=20
is for the sole use of the intended recipient(s) and may contain confiden=
tial
and privileged information or otherwise be protected by law.  Any unautho=
rized
review, use, disclosure or distribution is prohibited.  If you are not th=
e
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.


------_=_NextPart_001_01C3FD64.3D5BC64C--

<Prev in Thread] Current Thread [Next in Thread>