poll - which backup process do you use?

We're reevaluating our backup process in house here and I wanted to
take a poll.  Do most of you more experienced, wiser DBAs out there use


1)  the native sql backup process, either through T-SQL or EM?

OR

2)  A 3rd party tool that integrates into larger backup schemes and
kicks off its own jobs and backups?

We're evaluating a product, and it seems to not offer as much
flexibility...for example, we can only restore a database back to the
original file path and server instance.

Whatever you are evaluating is very limited by the sounds of it. You are
probably better off with native backup, which offers a lot of options.

The only advantage some of the 3rd party backup software offers over the
native stuff, is smaller, faster and encrypted backups.

If storage and backup/restore times aren't a concern to you, it is better to
stick with native backup.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/



<unc27932@yahoo.com> wrote in message
news:1122579145.779386.222990@g44g2000cwa.googlegroups.com...
> We're reevaluating our backup process in house here and I wanted to
> take a poll.  Do most of you more experienced, wiser DBAs out there use
>
>
> 1)  the native sql backup process, either through T-SQL or EM?
>
> OR
>
> 2)  A 3rd party tool that integrates into larger backup schemes and
> kicks off its own jobs and backups?
>
> We're evaluating a product, and it seems to not offer as much
> flexibility...for example, we can only restore a database back to the
> original file path and server instance.
>

Hi,

I will go with SQL Server native TSQL commands to backup database and
transaction log using
BACKUP DATABASE and BACKUP LOG commands.

For huge databases you could look into productions like:-

1. SQL LITE, TIME FINDER etc....

http://www.mssqlxpress.com/ SQL_Lit...uc
t.shtm

Thanks
Hari
SQL Server MVP

<unc27932@yahoo.com> wrote in message
news:1122579145.779386.222990@g44g2000cwa.googlegroups.com...
> We're reevaluating our backup process in house here and I wanted to
> take a poll.  Do most of you more experienced, wiser DBAs out there use
>
>
> 1)  the native sql backup process, either through T-SQL or EM?
>
> OR
>
> 2)  A 3rd party tool that integrates into larger backup schemes and
> kicks off its own jobs and backups?
>
> We're evaluating a product, and it seems to not offer as much
> flexibility...for example, we can only restore a database back to the
> original file path and server instance.
>

1)

Unless someone can convince me to use 2), and that need to be proper argumen
ts which I buy.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
Blog: http:// solidqualitylearning
.com/blogs/tibor/


<unc27932@yahoo.com> wrote in message news:1122579145.779386.222990@g44g2000cwa.googlegroup
s.com...
> We're reevaluating our backup process in house here and I wanted to
> take a poll.  Do most of you more experienced, wiser DBAs out there use
>
>
> 1)  the native sql backup process, either through T-SQL or EM?
>
> OR
>
> 2)  A 3rd party tool that integrates into larger backup schemes and
> kicks off its own jobs and backups?
>
> We're evaluating a product, and it seems to not offer as much
> flexibility...for example, we can only restore a database back to the
> original file path and server instance.
>

I currently use Native SQL since that is supported by Microsoft.

I have some servers where disk space and restore time are a concern, so I am
trying to convince my client to buy copies of SQL Litespeed for its
compression abilities.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.

www.experts-exchange.com - experts compete for points to answer your
questions


<unc27932@yahoo.com> wrote in message
news:1122579145.779386.222990@g44g2000cwa.googlegroups.com...
> We're reevaluating our backup process in house here and I wanted to
> take a poll.  Do most of you more experienced, wiser DBAs out there use
>
>
> 1)  the native sql backup process, either through T-SQL or EM?
>
> OR
>
> 2)  A 3rd party tool that integrates into larger backup schemes and
> kicks off its own jobs and backups?
>
> We're evaluating a product, and it seems to not offer as much
> flexibility...for example, we can only restore a database back to the
> original file path and server instance.
>

The product we're looking at is an agent that integrates with
Commvault.  Maybe others can speak to the quality of this product.  Not
sure.  All I know is in the help file it said:  "The SQL Server
iDataAgent VSS-enabled backup jobs must be restored to the exact
server, database, and file name from which they originated.", which for
us is pretty crappy.  We definitely need the "with move" option and
restore to other instances.

Any other opinions out there?