Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Other SQL Server Topics / July 2005

Tip: Looking for answers? Try searching our database.

backup location

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Damn fool - 30 Jul 2005 18:40 GMT
Hi again,

I am able to schedule a backup and default it to the server. However, is
there an option or a way to locate the backup somewhere else on the network?

regards,

gilbert
Greg D. Moore (Strider) - 30 Jul 2005 19:04 GMT
> Hi again,
>
> I am able to schedule a backup and default it to the server. However, is
> there an option or a way to locate the backup somewhere else on the network?

Yes.  You need to use a UNC and make sure the SQL Agent has rights on the
server you're writing to.

We use a snap server for this quite a bit.

> regards,
>
> gilbert
Simon Hayes - 30 Jul 2005 19:08 GMT
> Hi again,
>
[quoted text clipped - 5 lines]
>
> gilbert

Provided that the MSSQL service account is a domain account with write
access to \\server\share, then you can use a command like this:

backup database SomeDB to disk = '\\server\share\folder\somedb.bak'

See BACKUP and "Setting Up Windows Service Accounts" in Books Online. Note
that according to this white paper, MS do not recommend backing up to a
network drive because of the possible performance and connectivity issues:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx

In fact, if your database is quite small, then backing up to a network drive
is probably fine (you can always back it up again if the job fails), but if
you have large databases or if the backup job is critical, then it might be
safer to back up to a local drive first, and then copy the file to a network
location.

Simon
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.