Veritas-bu

[Veritas-bu] Backup image size limited to < 1TB?

2003-04-10 14:25:40
Subject: [Veritas-bu] Backup image size limited to < 1TB?
From: Mark.Donaldson AT experianems DOT com (Donaldson, Mark)
Date: Thu, 10 Apr 2003 12:25:40 -0600
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_01C2FF8E.9733F9C0
Content-Type: text/plain

Yeah, I bumped into this in another environment where I have filesystems >
1TB.  NB is limited to a max 1TB/backup image.  The only advice was to break
the backup into sets of less than 1TB.  The problem persists in v4.5.  

I think the limit is mentioned in the release notes but I'm not positive.

-M

-----Original Message-----
From: Brian Chase [mailto:vaxzilla AT jarai DOT org]
Sent: Thursday, April 10, 2003 12:11 PM
To: Veritas Backup
Subject: [Veritas-bu] Backup image size limited to < 1TB?


I just ran into a rather annoying limitation of NetBackup 3.4 on
Solaris.  I'm in the process of archiving a sizable collection of data.
After many hours of running one of the backup jobs I'm running errored
out with "(130) system error occurred".  The log file ends with:

  10:21:15 ERR - Backup exceeds 1 terabytes in size.
  10:23:22 INF - Backup by root on client rossum using class mtx_cl_arch:
    system error occurred.

The data set being archived in question is a relatively small subset of
a much larger (dozens of TB) worth of data that's being archived to
tape.  We do have the option of breaking it down into smaller subsets,
but that means we have to calculate the data sizes in advance to make
sure each backup will be less than a TB in size.  I'd prefer the
system to just take what I damn well please to feed it.

At the very least, since NetBackup seems to track the number based on
the kilobytes in the backup, I'd have expected this sort of limit to be
imposed at the natural limits of a signed or unsigned 32-bit integer,
2^31-1 KB (2TB) or 2^32-1 KB (4TB), as opposed to what appears to be a
somewhat arbitrary 2^30 KB (1TB).

Is there a way around this backup image size limit?

-brian.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

------_=_NextPart_001_01C2FF8E.9733F9C0
Content-Type: text/html
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 =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Backup image size limited to &lt; 1TB?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Yeah, I bumped into this in another environment where =
I have filesystems &gt; 1TB.&nbsp; NB is limited to a max 1TB/backup =
image.&nbsp; The only advice was to break the backup into sets of less =
than 1TB.&nbsp; The problem persists in v4.5.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>I think the limit is mentioned in the release notes =
but I'm not positive.</FONT>
</P>

<P><FONT SIZE=3D2>-M</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Brian Chase [<A =
HREF=3D"mailto:vaxzilla AT jarai DOT org">mailto:vaxzilla AT jarai DOT 
org</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Thursday, April 10, 2003 12:11 PM</FONT>
<BR><FONT SIZE=3D2>To: Veritas Backup</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Backup image size limited to =
&lt; 1TB?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>I just ran into a rather annoying limitation of =
NetBackup 3.4 on</FONT>
<BR><FONT SIZE=3D2>Solaris.&nbsp; I'm in the process of archiving a =
sizable collection of data.</FONT>
<BR><FONT SIZE=3D2>After many hours of running one of the backup jobs =
I'm running errored</FONT>
<BR><FONT SIZE=3D2>out with &quot;(130) system error =
occurred&quot;.&nbsp; The log file ends with:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; 10:21:15 ERR - Backup exceeds 1 terabytes in =
size.</FONT>
<BR><FONT SIZE=3D2>&nbsp; 10:23:22 INF - Backup by root on client =
rossum using class mtx_cl_arch:</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; system error occurred.</FONT>
</P>

<P><FONT SIZE=3D2>The data set being archived in question is a =
relatively small subset of</FONT>
<BR><FONT SIZE=3D2>a much larger (dozens of TB) worth of data that's =
being archived to</FONT>
<BR><FONT SIZE=3D2>tape.&nbsp; We do have the option of breaking it =
down into smaller subsets,</FONT>
<BR><FONT SIZE=3D2>but that means we have to calculate the data sizes =
in advance to make</FONT>
<BR><FONT SIZE=3D2>sure each backup will be less than a TB in =
size.&nbsp; I'd prefer the</FONT>
<BR><FONT SIZE=3D2>system to just take what I damn well please to feed =
it.</FONT>
</P>

<P><FONT SIZE=3D2>At the very least, since NetBackup seems to track the =
number based on</FONT>
<BR><FONT SIZE=3D2>the kilobytes in the backup, I'd have expected this =
sort of limit to be</FONT>
<BR><FONT SIZE=3D2>imposed at the natural limits of a signed or =
unsigned 32-bit integer,</FONT>
<BR><FONT SIZE=3D2>2^31-1 KB (2TB) or 2^32-1 KB (4TB), as opposed to =
what appears to be a</FONT>
<BR><FONT SIZE=3D2>somewhat arbitrary 2^30 KB (1TB).</FONT>
</P>

<P><FONT SIZE=3D2>Is there a way around this backup image size =
limit?</FONT>
</P>

<P><FONT SIZE=3D2>-brian.</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2FF8E.9733F9C0--

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