All,

This may be trivial but the SQL service needs to be running with
a domain account in order to backup to a non-local drive.

That being said, we backup about 8tb of data over the network to
a NAS filer daily. I would NOT attempt this without using LITESPEED(or
some comparable product). It backups up faster and compresses the
backups so we are using only 75% of the disk space. Meaning the 8tb
backup into 2tb of filer disk and across the network in less time than a
standard SQL backup runs to a local drive. LITESPEED has paid for
itself. The savings in DLT tapes alone are 3 times the yearly
maintenance.

We have had only a few sparse issues with backups to the filer
being corrupt and we had the same issues with some standard backups.
Because of the way it backs up the database into memory and compresses
it the only issue I have found is when the process is interrupted by an
outside source then the file would be corrupt. In my experience the
same situation with a standard backup would just delete the file.

You also have the option of attaching directly to the filer if
you are worried about writing over the network. I'm not suggesting
using the filer drives as database drives(our tests on that subjects
didn't bode well for the filer) but it is excellent for writing our
backups out and we have them SNAP-REPLICATED to a filer at our BR
location which plugged that hole also.

Thanks,
Ralph W. Davis
*********************************************************
*** CORPORATE DBA group - Houston ***
*********************************************************

-----Original Message-----
From: Jay Butler
[mailto:mssqldba-ezmlmshield-x60977856.[Email address protected]
Sent: Monday, January 30, 2006 9:51 AM
To: LazyDBA Discussion
Subject: Re: backup over server

Mapped drives belong to the user session. They are not available to the
services.

Even if you could, I would avoid backing up directly to network devices.

I have had bad experiences in the past trying to backup to a NAS. SQL
Server would report that the backups were successful. The files were the

correct size. But, more often than not, the files were corrupt. Restores

would fail at some point because of this.

As Christopher suggests, I would backup locally then copy the files
across the network. You should still use the UNC path for the file
destination.


Jumma Salim wrote:
> Can I make a backup plan to backup to a different server by mapping a
> drive to database server say T drive
>
>
>
> Mapped drive does not show when I make Maintenance plan?
>
>
>
>
>
> If I do through query analyzer it will not do all step that I can
easily
> do in maintenance plan?
>
>
>
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> Website : http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>
> .
>
>


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

Confidentiality Note: The information contained in this message, and any
attachments, may contain confidential and/or privileged material. It is intended
solely for the person or entity to which it is addressed. Any review,
retransmission, dissemination, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and delete
the material from any computer.


MS Sql Server LazyDBA home page