Veritas-bu

[Veritas-bu] VTL vs. Disk based backups

2005-11-30 15:27:32
Subject: [Veritas-bu] VTL vs. Disk based backups
From: pkeating AT bank-banque-canada DOT ca (Paul Keating)
Date: Wed, 30 Nov 2005 15:27:32 -0500
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5F5EC.7E1E1BF7
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I haven't looked at any options yet, and may be accused of being a
shill, but I attended a falconstor presentation a couple weeks ago, and
was pretty impressed.
=20
no proprietary hardware.....image install off of CD onto pre-tested
intel platforms, and attaches to your existing disk storage....pretty
slick.
=20
few pitfalls.....search the archives for falconstore from last Monday,
IIRC.
=20
We're using DSSU now for a few ultra slow clients (10mb/s + encryption
links.) that can't stream a tape drive, and it seems ok....occasionally
have backups fail because the disks don't get purged, and no room left
for backups.
=20
people tell me that you can' send many backups to a disk storage unit
becuase performance will suffer due to disk thrashing.....I have been
running 5 jobs to a single harddrive, but the throughput is so slow off
the network for the thrashing to be inconsequential. The engineer from
falconstor says it's all on how you setup the disks...said he knows of
at least one site sending 800+ streams to a single VTL.
=20
I've heard that a particular backup software provider, with whom you may
be familiar, has several falconstore boxes in use in there own
environment.
=20
EMC is either a partner or OEM reseller (can't remember which) of
falconstor as well....but apparantly the OEM version is a little behind
in features compared to the more "raw" version you can get from a
"partner"

        -----Original Message-----
        From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Hindle,
Greg
        Sent: November 30, 2005 3:13 PM
        To: veritas-bu AT mailman.eng.auburn DOT edu
        Subject: [Veritas-bu] VTL vs. Disk based backups
=09
=09

        We are looking at VTL technologies with EMC being the front
leader. We are looking at upgrading to netbackup 6.0 Solaris 10 soon. My
backup partner in crime disagree with the direction we should go. I
think we should go with disk based backups and my partner want to go
with VTL. Now since we do not have this in yet it is hard to look at
both and "see" what is better. SO has anyone here also researching this
subject and have their own opinion? We are a Netapp/EMC shop so the back
disk is not the show stopper but the future of both technologies. Any
care to share their views?=20

=09
        Greg=20

        >>> This e-mail and any attachments are confidential, may
contain legal, professional or other privileged information, and are
intended solely for the addressee.  If you are not the intended
recipient, do not use the information in this e-mail in any way, delete
this e-mail and notify the sender. CEG-IP1


------_=_NextPart_001_01C5F5EC.7E1E1BF7
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>I=20
haven't looked at any options yet, and may be accused of being a shill, =
but I=20
attended a falconstor presentation a couple weeks ago, and was pretty=20
impressed.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>no=20
proprietary hardware.....image install off of CD onto pre-tested intel=20
platforms, and attaches to your existing disk storage....pretty=20
slick.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>few=20
pitfalls.....search the archives for falconstore from last Monday,=20
IIRC.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>We're=20
using DSSU now for a few ultra slow clients (10mb/s + encryption links.) =
that=20
can't stream a tape drive, and it seems ok....occasionally have backups =
fail=20
because the disks don't get purged, and no room left for=20
backups.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>people=20
tell me that you can' send many backups to a disk storage unit becuase=20
performance will suffer due to disk thrashing.....I have been running 5 =
jobs to=20
a single harddrive, but the throughput is so slow off the network for =
the=20
thrashing to be inconsequential. The engineer from falconstor says it's =
all on=20
how you setup the disks...said he knows of at least one site sending =
800+=20
streams to a single VTL.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>I've=20
heard that a particular backup software provider, with whom&nbsp;you may =

be&nbsp;familiar, has several falconstore boxes in use in there own=20
environment.</FONT></SPAN></DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D784172020-30112005><FONT face=3DArial color=3D#800000 =
size=3D2>EMC is=20
either a partner or OEM reseller (can't remember which)&nbsp;of =
falconstor as=20
well....but apparantly the OEM version is a little behind in features =
compared=20
to the more "raw" version you can get from a =
"partner"</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  veritas-bu-admin AT mailman.eng.auburn DOT edu=20
  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Hindle,=20
  Greg<BR><B>Sent:</B> November 30, 2005 3:13 PM<BR><B>To:</B>=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] VTL =
vs. Disk=20
  based backups<BR><BR></FONT></DIV><!-- Converted from text/rtf format =
-->
  <P><FONT face=3DArial size=3D2>We are looking at VTL technologies with =
EMC being=20
  the front leader. We are looking at upgrading to netbackup 6.0 Solaris =
10=20
  soon. My backup partner in crime disagree with the direction we should =
go. I=20
  think we should go with disk based backups and my partner want to go =
with VTL.=20
  Now since we do not have this in yet it is hard to look at both and =
"see" what=20
  is better. SO has anyone here also researching this subject and have =
their own=20
  opinion? We are a Netapp/EMC shop so the back disk is not the show =
stopper but=20
  the future of both technologies. Any care to share their views? =
</FONT></P>
  <P><FONT face=3DArial></FONT> <BR><FONT face=3DArial =
size=3D2>Greg</FONT> </P><PRE>&gt;&gt;&gt; This e-mail and any =
attachments are confidential, may contain legal, professional or other =
privileged information, and are intended solely for the addressee.  If =
you are not the intended recipient, do not use the information in this =
e-mail in any way, delete this e-mail and notify the sender. CEG-IP1
</PRE></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C5F5EC.7E1E1BF7--

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