From: "bob chronister" 

indeed, works well with exchange. standard backup going way back in NT is
related to veritas (name change though).

"Peter Sawatzki"  wrote in message
news:MPG.18895beaec2d2b1b9896d9{at}news.barkto.com...
> I'm using their backup agent for Exchange 2000 and it is excellect too
> (like their open files agent).
>
> I think the standard backup in Win2000 is made by Veritas too.
>
> Peter
>
> In article , bobnt{at}mindspring.com says...
> > don't pay any attention to george :-). when sql was written, there was
> > several under the counter issues that had to be solved. one of these was
the
> > ability to backup busy files. veritas takes avantage of these methods to
> > backup the database. the same basic issues are found in all databases.
> > veritas IMO, does an excellent job of allowing busy databse files to be
> > copied onto tape.
> >
> > "Ellen K."  wrote in message
> > news:78ns1voe76m972n6g6hlh51mf3ef641mam{at}4ax.com...
> > > Has anyone used Veritas BackupExec with SQL Server 2000?   The network
> > > guy on the recordings database project says we should use this instead
> > > of the built-in backup utility and pointed me to the below.   He says
we
> > > spent $50K setting things up so everything would get backed up to one
> > > special backup server, therefore he doesn't want me to use the
built-in
> > > one and doesn't wanna give me a dedicated tape device for this box or
> > > let me back up to some other box.
> > >
> > > Based on the below this looks like it does everything the built-in one
> > > does, but I'd like to know whether anyone can vouch that it really
does,
> > > and also whether I can make the things it does part of a larger
> > > maintenance routine... what I wanna do every night is (in this order):
> > > -backup the transaction log (with automatic truncation)
> > > -backup the database (maybe just differential, then a full backup once
a
> > > week)
> > > -run my purge routine (delete rows representing
"orders" that never
> > > became sales after 30 days)
> > > -run my archive routine (remove recordings 120 days old from the
> > > database and save them as binary files on another server, but keeping
> > > each one's row and adding the new location to a path field
> > > -backup (and truncate) the transaction log again
> > > -go delete some files on another server  (On the belt-and-suspenders
> > > theory, we decided to save each day's recordings on another server in
> > > addition to writing them to the database, then delete them after the
> > > nightly backup.)
> > >
> > > From
> > >
> >
http://eval.veritas.com/downloads/pro/backup_exec/be_win_8_6_datasheet_us.pd
> > f
> > > >
> > > >Agent for Microsoft SQL Server - ensures that your
business-critical
> > > >OLTP, OLAP and e-business data are protected in case of
> > > >application/hardware-based corruption or loss. It
provides SQL Server
> > 6.5, 7
> > > >and SQL Server 2000 users granular protection down to
the individual
> > table
> > > >space or filegroup. Execute differential backups as well as
Transaction
> > Log
> > > >backups with automatic truncation. Restore options include
redirection to
> > > >another SQL Server and the ability to perform
"rollback restores,"

--- BBBS/NT v4.01 Flag-4