Thursday, March 29, 2012

Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenance
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
.BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) to
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than one
.BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
ChrisChris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but based
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKUP
> DATABASE...) file and you attempt to do a RESTORE command you are going to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>> I am trying to decide if we should use Microsoft Backup (Database
>> Maintenance
>> Plans) or use Veritas. We already own Veritas, and the SQL clients.
>> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
>> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
>> to
>> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
>> Upside: using standard Microsoft tools. Downside: Need to store more than
>> one
>> .BAK on the SAN for safety.
>> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
>> tools. Veritas SQL client will backup directly to tape. No space on the
>> SAN
>> is required.
>>
>> I am looking for a pros and cons of each to help me make my decision
>> thank you
>> Chris
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenance
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
..BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) to
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than one
..BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
Chris
Chris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris
|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but based
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKUP
> DATABASE...) file and you attempt to do a RESTORE command you are going to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenanc
e
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
.BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) t
o
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than on
e
.BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
ChrisChris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but bas
ed
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKU
P
> DATABASE...) file and you attempt to do a RESTORE command you are going
to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Strategy

I am a newbie to SQL.
I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
sure our databases are backed up in the event of a data loss or a crash?
Thanks,
Rich
The easiest way is to create a maintenance plan using the SQL Enterprise
Manager.
Or you can create jobs that use T-SQL statement to backup the databases.
Always make sure that the backup's are stored on offline storage, eg another
server or tapes.
The best way depends or your businessneeds and databasesize.
Robert Hartskeerl, MCTS
http://hartskeerl.nl/blogs/robert/
"Rikellent" wrote:

> I am a newbie to SQL.
> I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
> sure our databases are backed up in the event of a data loss or a crash?
> Thanks,
> Rich
|||Hello,
You could use the maintenence wizard to create a backup plan and schedule
it. But I had lot of issues with maintenanceplans and so i went for TSQL
backup
script and schedule it using SQL Server agent.
Take a look into the below article:-
http://www.microsoft.com/india/msdn/articles/185.aspx
Thanks
Hari
"Rikellent" <Rikellent@.discussions.microsoft.com> wrote in message
news:BB10385E-8923-4AF7-B5B8-75F7B44CD993@.microsoft.com...
>I am a newbie to SQL.
> I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
> sure our databases are backed up in the event of a data loss or a crash?
> Thanks,
> Rich

Backup strategy

Hello,
I manage a SQL Server that requires frequent backups to insure not
much data is lost in the event of a failure. Here is how backups are
performed currently:
Sunday, 1:00am
== * Full database backup of ALL databases
* Transaction log backup WITH INIT
Mon-Sat, 1:00am
== * Differential database backup of ALL databases
Daily, Hourly
== * Transaction log backup
I am currently having 2 problems. The first problem is that sometimes
on Sunday mornings when the job attempts to backup the transactions
logs WITH INIT the job will fail because the Daily, Hourly process is
also backing up at the same time. The second problem is that the
transaction log backups seem to grow larger and larger and take longer
and longer to complete. Is it really necessary to store the entire
week of transaction log backups when I'll always have a differential I
can apply for each day? The only purpose of the transaction log
backups is to insure we can restore to the latest point in time before
a failure occurs. There isn't a need to revert back to more than the
previous day's transaction log backup.
Is what I'm doing the best way? How can this be improved upon?
Thank you in advance for your time and efforts.
ShawnHi,
> Is it really necessary to store the entire
> week of transaction log backups when I'll always have a differential I
> can apply for each day? The only purpose of the transaction log
> backups is to insure we can restore to the latest point in time before
> a failure occurs. There isn't a need to revert back to more than the
> previous day's transaction log backup.
Based on these requirements you do not need an entire week of transaction
log backups. You just need the transaction log backups taken after your last
differential backup.
But most important, test your strategy restoring your database to another
database server using this combination of full, differential and transaction
log backups.
Hope this helps,
Ben Nevarez
"ITistic" wrote:
> Hello,
> I manage a SQL Server that requires frequent backups to insure not
> much data is lost in the event of a failure. Here is how backups are
> performed currently:
> Sunday, 1:00am
> ==> * Full database backup of ALL databases
> * Transaction log backup WITH INIT
> Mon-Sat, 1:00am
> ==> * Differential database backup of ALL databases
> Daily, Hourly
> ==> * Transaction log backup
> I am currently having 2 problems. The first problem is that sometimes
> on Sunday mornings when the job attempts to backup the transactions
> logs WITH INIT the job will fail because the Daily, Hourly process is
> also backing up at the same time. The second problem is that the
> transaction log backups seem to grow larger and larger and take longer
> and longer to complete. Is it really necessary to store the entire
> week of transaction log backups when I'll always have a differential I
> can apply for each day? The only purpose of the transaction log
> backups is to insure we can restore to the latest point in time before
> a failure occurs. There isn't a need to revert back to more than the
> previous day's transaction log backup.
> Is what I'm doing the best way? How can this be improved upon?
> Thank you in advance for your time and efforts.
> Shawn
>

Backup strategy

I have to build a backup method for my factory.
I have sql server 2000 and I have to save a DB that is used from 8.00
to 20.00.
Now I have a complete backup that run every night and a differential at
12.30 every day.
The complete have the name of the day, so I have seven different files
for every day of the week. Also the differential one.
I have not log backups.
So, if I'd like to make more backup in the working time (when users use
DB) I have to increase differential backups (with time of backup in the
name of file) or I have to add log backups?
If I make log backups, I have to create one day file (with no
overwrite) or I have to create in a day many files with day of week and
time of backup in the name of file?
In this scenario, I have to use NO_TRUNCATE or TRUNCATE for log
backups?
Thanks to all.If you don't want log backups then set the recovery model to simple - that
will truncate the log on every backup.
Include the date rather than the day in the backup files.
mydb_full_yyyymmdd_hhmmss.bak
mydb_diff_yyyymmdd_hhmmss.bak
If you want to include log backups then do the same
mydb_log_yyyymmdd_hhmmss.bak
You can now add diff backups whenever you wish.
From what you say you might want to consider log backups though.
Have a look at this sp
It will take full, diff and log backups for all databases on the server and
delete old files - you can control what it does from a table in the admin
database.
http://www.nigelrivett.net/SQLAdmin/BackupAllDatabases.html
There is also an sp there to do the restores including the log sequence and
latest full/diff.
"giminera@.libero.it" wrote:
> I have to build a backup method for my factory.
> I have sql server 2000 and I have to save a DB that is used from 8.00
> to 20.00.
> Now I have a complete backup that run every night and a differential at
> 12.30 every day.
> The complete have the name of the day, so I have seven different files
> for every day of the week. Also the differential one.
> I have not log backups.
> So, if I'd like to make more backup in the working time (when users use
> DB) I have to increase differential backups (with time of backup in the
> name of file) or I have to add log backups?
> If I make log backups, I have to create one day file (with no
> overwrite) or I have to create in a day many files with day of week and
> time of backup in the name of file?
> In this scenario, I have to use NO_TRUNCATE or TRUNCATE for log
> backups?
> Thanks to all.
>|||giminera@.libero.it wrote:
> I have to build a backup method for my factory.
> I have sql server 2000 and I have to save a DB that is used from 8.00
> to 20.00.
> Now I have a complete backup that run every night and a differential at
> 12.30 every day.
> The complete have the name of the day, so I have seven different files
> for every day of the week. Also the differential one.
> I have not log backups.
> So, if I'd like to make more backup in the working time (when users use
> DB) I have to increase differential backups (with time of backup in the
> name of file) or I have to add log backups?
> If I make log backups, I have to create one day file (with no
> overwrite) or I have to create in a day many files with day of week and
> time of backup in the name of file?
> In this scenario, I have to use NO_TRUNCATE or TRUNCATE for log
> backups?
> Thanks to all.
>
I have a script that you can schedule to run at frequent intervals (I
run it every 5 minutes) that will automatically handle full backups and
t-log backups for you, for all databases on the server.
http://realsqlguy.com/twiki/bin/view/RealSQLGuy/AutomaticBackupOfAllDatabases
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||A transaction log backup is actually recommended for your scenario.
Just a follow up question on this one. I have a full database backup and
log shipping configured. I want to include a differential backup so as to
make restoration a lot easy for the server since I am looking at around 50
databases on single server. Will the differential backup work with my
existing plan?
"Nigel Rivett" wrote:
> If you don't want log backups then set the recovery model to simple - that
> will truncate the log on every backup.
> Include the date rather than the day in the backup files.
> mydb_full_yyyymmdd_hhmmss.bak
> mydb_diff_yyyymmdd_hhmmss.bak
> If you want to include log backups then do the same
> mydb_log_yyyymmdd_hhmmss.bak
> You can now add diff backups whenever you wish.
> From what you say you might want to consider log backups though.
> Have a look at this sp
> It will take full, diff and log backups for all databases on the server and
> delete old files - you can control what it does from a table in the admin
> database.
> http://www.nigelrivett.net/SQLAdmin/BackupAllDatabases.html
> There is also an sp there to do the restores including the log sequence and
> latest full/diff.
>
>
>
> "giminera@.libero.it" wrote:
> > I have to build a backup method for my factory.
> > I have sql server 2000 and I have to save a DB that is used from 8.00
> > to 20.00.
> > Now I have a complete backup that run every night and a differential at
> > 12.30 every day.
> > The complete have the name of the day, so I have seven different files
> > for every day of the week. Also the differential one.
> > I have not log backups.
> > So, if I'd like to make more backup in the working time (when users use
> > DB) I have to increase differential backups (with time of backup in the
> > name of file) or I have to add log backups?
> > If I make log backups, I have to create one day file (with no
> > overwrite) or I have to create in a day many files with day of week and
> > time of backup in the name of file?
> > In this scenario, I have to use NO_TRUNCATE or TRUNCATE for log
> > backups?
> > Thanks to all.
> >
> >

Backup Strategy

My client has about 2TB data, are there any recommended
backup strategy? Does SAN / NAS helps?Hi,
The best method for 2 TB database will be,
1. Perform a Diffrential Backup daily once
2. Perform a Transaction Log backup every 30 Minutes (U can change based on
daily growth)
Since the volume is very huge ideal way to keep the backup devices will be
either SAN or NAS.
Thanks
Hari
MCDBA
"Peter Wong" <anonymous@.discussions.microsoft.com> wrote in message
news:0a8d01c3d9a9$d97e0140$a101280a@.phx.gbl...
> My client has about 2TB data, are there any recommended
> backup strategy? Does SAN / NAS helps?|||You might also take a look at filegroup backups, which are intended for very
large databases. These are doc'd in books on line... You might have to move
data around into new filegroups to implement this, but it would allow you to
back up part of the database each night...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Peter Wong" <anonymous@.discussions.microsoft.com> wrote in message
news:0a8d01c3d9a9$d97e0140$a101280a@.phx.gbl...
> My client has about 2TB data, are there any recommended
> backup strategy? Does SAN / NAS helps?sql