Veritas-bu

[Veritas-bu] Iron Mountain Vault Report File Issue

2006-05-16 15:28:12
Subject: [Veritas-bu] Iron Mountain Vault Report File Issue
From: Eric.Hillman AT blackrock DOT com (Hillman, Eric)
Date: Tue, 16 May 2006 15:28:12 -0400
------_=_NextPart_001_01C6791E.DED3D32E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We are in the process of switching our rotation procedure from using
some Iron Mountain application to simply uploading the Netbackup Vault
IM report file to inform Iron Mountain of the tapes that are getting
sent to them that day.  One issue that we're seeing is that when Vault
runs, some tapes are still being written to.  If these tapes hold valid
images, Vault tries to eject them, and fails.  The "Picking List for
Robot" vault report shows these tapes as "**Not Ejected**", but the IM
file still adds it to it's list of outgoing tapes.  When the file is
FTP'd, Iron Mountain thinks it's receiving the tape and later generates
an exception email stating that a tape was not received.  Does anyone
know if it's possible to have these "**Not Ejected**" media removed from
the IM report files?  

Thanks!
-Eric

THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, 
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader 
of this message is not the intended recipient, you are hereby notified that any 
dissemination, distribution, copying or use of this message and any attachment 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and permanently delete it from 
your computer and destroy any printout thereof.
------_=_NextPart_001_01C6791E.DED3D32E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7638.1">
<TITLE>Iron Mountain Vault Report File Issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">We are in the process of switching our rot=
ation procedure from using some Iron Mountain application to simply uploadi=
ng the Netbackup Vault IM report file to inform Iron Mountain of the tapes =
that are getting sent to them that day.&nbsp; One issue that we're seeing i=
s that when Vault runs, some tapes are still being written to.&nbsp; If the=
se tapes hold valid images, Vault tries to eject them, and fails.&nbsp; The=
 &quot;Picking List for Robot&quot; vault report shows these tapes as &quot=
;</FONT><FONT SIZE=3D2 FACE=3D"Courier New">**Not Ejected**&quot;</FONT><FO=
NT SIZE=3D2 FACE=3D"Arial">, but the IM file still adds it to it's list of =
outgoing tapes.&nbsp; When the file is FTP'd, Iron Mountain thinks it's rec=
eiving the tape and later generates an exception email stating that a tape =
was not received.&nbsp; Does anyone know if it's possible to have these &qu=
ot;</FONT><FONT SIZE=3D2 FACE=3D"Courier New">**Not Ejected**&quot; media r=
emoved from the</FONT> <FONT SIZE=3D2 FACE=3D"Arial">IM report files</FONT>=
<FONT SIZE=3D2 FACE=3D"Courier New">?&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Thanks!</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">-Eric</FONT>
</P>

</BODY>
</HTML><br>
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILE=
GED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If t=
he reader of this message is not the intended recipient, you are hereby not=
ified that any dissemination, distribution, copying or use of this message =
and any attachment is strictly prohibited. If you have received this messag=
e in error, please notify us immediately by replying to the message and per=
manently delete it from your computer and destroy any printout thereof.
------_=_NextPart_001_01C6791E.DED3D32E--

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] Iron Mountain Vault Report File Issue, Hillman, Eric <=