Tech Support > Operating Systems > UNIX / Variants > StorEdge Enterprise Backup vs Veritas NetBackup
StorEdge Enterprise Backup vs Veritas NetBackup
Posted by Julian Regel on July 12th, 2003


Hi.

I have been tasked with investigating a backup/restore solution that will
be used to backup a Sun 3310 NAS with up to 1.3TB data. At the moment, the
L25 tape library with SDLT320 drive(s) looks like it will be the right
hardware for us, but I am interested in opinions with regards to software.

At the moment, we backup our Sun servers (An E450, E3000 and V880) using
ufsdump. I am keen to keep doing this for the operating system using local
DDS4 drives as it will make system restore in the event of a disaster much
quicker (or that's my understanding at least). Over time we intend to
migrate much of our "non-operating system" data off the servers and onto
the NAS.

Question is, Sun are selling both StorEdge Enterprise Backup (formally
Solstice Backup (a rebadged Legato Networker?)) and Veritas NetBackup. Are
they equivalent products? Is one aimed at the lowend and another at the
high end? What are the pros and cons of each?

Any help appreciated.

JR

Posted by Len Philpot on July 13th, 2003


In comp.unix.admin "Michael wrote:
This used to be an issue with us and SBU, but it's not anymore. When the
index format changed between versions 5.x and 6, the indexes shrank
quite a bit. I used to run nsrck regularly to reclaim space, but now it
stays at 100% used (i.e., no gaps in the data, a good thing). Usage in
the index filesystem dropped by close to 50% with the change.


You're right about the time - With ~90 clients, some with few and some
with many (xxx,xxx) files, it generally took us about 6 hours to check
them all. With the new format, it's much more efficient. In general,
we've been advised by Sun not to run index utilities as a maintenance
tool, but rather only as needed as a repair tool. These days, the
indexes pretty much take care of themselves. However, nsrck can be
interrupted without harm. In fact, until I upped the data size and file
handles limit with ulimit, it would regularly die about halfway through,
but without any damage.


SBU (Legato) has two levels of indexing (catalogs): The media index
contain what savesets (typically filesystems) are on what media and the
file index contains what files are in a given saveset. When the Browse
Policy is passed, the file indexes expire and its' no longer possible to
browse for files during a restore. However, you can still recover entire
filesystems and (I think) even a given file if you know the file's
location. When the Retention Policy is passed, nothing changes except
the saveset it considered Recyclable. When all savesets on a given media
pass the Retention Policy, that media is recyclable and will be
automatically reused if physically available. However, the media index
entry for that volume (tape) and saveset remain intact until the media
is relabeled (erased). To get the file index back for an expired volume,
you have to scan it in, which is generally about a 3-4 hour process for
a DLT7000 volume.

For simplicity, we generally set both policies to the same value.


I understand your point, but see above re: media index and scanning. The
data will stay on the tape and even if the indexes are deleted, scanning
it in will rebuild all that. Still, having backups on more than one
media never hurts. In fact, before I upgrade Solaris and Veritas Volume
Manager next week on our production server, I'll run backups on both DLT
and 8mm Mammoth tape.

--

-- Len Philpot ><> --
-- len@philpot.org http://philpot.org/ --
-- lphilpot01@yahoo.com (alternate email) --