MS SQL Server - SQL 2K Backup.....

Author

SQL 2K Backup.....

Govardhan Smith

2005-07-11, 8:23 pm

I have SQL Server 2K. I have database maintenance plan for full,
differential and transactional backups. I am writing all these backups to a
mapped network drive.

What is the industry standard way of doing this? Is it abnormal to write the
backups to a network drive? I am writing to a different hardisk other than
the SQL Server installed computer, because in case of any computer problem
my backup will not be much helpful if I can not boot SQL Server computer.

Some one here arguing that we should write to the local hard disk first and
then copy the same to network later.

Any comments and thoughts?

Thanks,

Smith

Ravi

2005-07-11, 8:23 pm

Network backup is taking more time than local backup. The longer backup
process run it will hold more resources in the server. if you backup locally
and then copy to the network will reduce the overhead of sql server.

Backup to the tape is the good options. I would say it the industry
standard.
--
Thanks & Rate the Postings.
-Ravi-

"Govardhan Smith" wrote:

> I have SQL Server 2K. I have database maintenance plan for full,
> differential and transactional backups. I am writing all these backups to a
> mapped network drive.
>
> What is the industry standard way of doing this? Is it abnormal to write the
> backups to a network drive? I am writing to a different hardisk other than
> the SQL Server installed computer, because in case of any computer problem
> my backup will not be much helpful if I can not boot SQL Server computer.
>
> Some one here arguing that we should write to the local hard disk first and
> then copy the same to network later.
>
> Any comments and thoughts?
>
> Thanks,
>
> Smith
>
>
>

Mike John

2005-07-11, 8:23 pm

Thre is no real "standard" you will come across, but many reccomendations
depending on your recovery needs, time you can suffer being down for, disc
space availability, db size etc etc.

Personally I go for:

DB files raid 10
Log files raid 1

Regular DB backups and log file backups to a set of spindles different to
BOTH the above,
Copy the backup files off to tape for rotation into firesafe and offsite
storage

But it all depends on what you need and what you can afford in both money
and exposure to data loss.

If you post some more details doubtless you will get other suggestions.

Mike John

"Govardhan Smith" <Gov_Smith@hotmail.com> wrote in message
news:eDacdglhFHA.576@tk2msftngp13.phx.gbl...
>I have SQL Server 2K. I have database maintenance plan for full,
> differential and transactional backups. I am writing all these backups to
> a
> mapped network drive.
>
> What is the industry standard way of doing this? Is it abnormal to write
> the
> backups to a network drive? I am writing to a different hardisk other than
> the SQL Server installed computer, because in case of any computer problem
> my backup will not be much helpful if I can not boot SQL Server computer.
>
> Some one here arguing that we should write to the local hard disk first
> and
> then copy the same to network later.
>
> Any comments and thoughts?
>
> Thanks,
>
> Smith
>
>

Andrew J. Kelly

2005-07-11, 8:23 pm

That is a common approach for backups. Just make sure you use UNC pathing
and not a mapped drive. You may also consider one of the 3rd party backup
utilities that do compression on the fly so the amount of data sent across
the network is minimized.

--
Andrew J. Kelly SQL MVP

"Govardhan Smith" <Gov_Smith@hotmail.com> wrote in message
news:eDacdglhFHA.576@tk2msftngp13.phx.gbl...
>I have SQL Server 2K. I have database maintenance plan for full,
> differential and transactional backups. I am writing all these backups to
> a
> mapped network drive.
>
> What is the industry standard way of doing this? Is it abnormal to write
> the
> backups to a network drive? I am writing to a different hardisk other than
> the SQL Server installed computer, because in case of any computer problem
> my backup will not be much helpful if I can not boot SQL Server computer.
>
> Some one here arguing that we should write to the local hard disk first
> and
> then copy the same to network later.
>
> Any comments and thoughts?
>
> Thanks,
>
> Smith
>
>

David Portas

2005-07-11, 8:23 pm

However you do your backups make sure you regularly take a copy to be put
into secure storage, preferably away from your site. That's primarily where
tapes are useful. A backup on the network is useless if your hardware is
stolen or goes up in flames.

--
David Portas
SQL Server MVP
--

Tibor Karaszi

2005-07-12, 3:23 am

I sometimes do the backup locally and immediately copy the file (using another jobstep or similar)
to another machine.

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

"Govardhan Smith" <Gov_Smith@hotmail.com> wrote in message
news:eDacdglhFHA.576@tk2msftngp13.phx.gbl...
>I have SQL Server 2K. I have database maintenance plan for full,
> differential and transactional backups. I am writing all these backups to a
> mapped network drive.
>
> What is the industry standard way of doing this? Is it abnormal to write the
> backups to a network drive? I am writing to a different hardisk other than
> the SQL Server installed computer, because in case of any computer problem
> my backup will not be much helpful if I can not boot SQL Server computer.
>
> Some one here arguing that we should write to the local hard disk first and
> then copy the same to network later.
>
> Any comments and thoughts?
>
> Thanks,
>
> Smith
>
>

Sponsored Links