Link to home
Start Free TrialLog in
Avatar of WvrLthr
WvrLthrFlag for United States of America

asked on

Help a novice DBA with unc path

Hello All,

I understand SQL Server architecture and we are currently running on SQL Server 2005.  The trick is that there is very little DBA work here,  so the knowledge/skills get very rusty.  We are moving to SQL Server 2008 R2 on VMWare and want to have a common set of disk on the vcenter server for our servers to use for backup, so I need a unc path.

In researching, it seemed like unc is not an option.  However, when I play with a maintenance plan, it seems to work fine.

My question to you is what am I missing?  Am I going to hit a brick wall down the road during a process?  
-restore or restoring to another server
-keeping a couple full backups and their associated diffs and trans logs
-scheduling backups on SQL Server Agent
-something I am not thinking of

I have attached a screen shot of how I had the maintenance plan set up and it works fine when I run it from SQL Server Agent.

I appreciate your advice and time,

Jeremy
sqlbak.docx
Avatar of lcohan
lcohan
Flag of Canada image

You should be able to backup SQL db's to UNC path as long as the user running the command has sufficient rights to that path:
"A UNC name has the form \\Systemname\ShareName\Path\FileName. "


"Backing Up to a File on a Network Share"
http://msdn.microsoft.com/en-us/library/ms179313.aspx#NetworkShare
Avatar of WvrLthr

ASKER

lcohan,

Thanks for the reply.  I took a look at the link and it helped break some things loose for me.  I ran it past my boss who is the windows network/domain guru here and it seemed to match up.




I am pretty confident, but one final picky question.  

In my example, I did not specify the full name of the device, for example,  \\vcenter\sqlbak\productiondb.bak.  I just have the path as \\vcenter\sqlbak\.  When I run the backup it creates the file name based on the name of the database which is what I prefer.  

So many posts on the internet talk about having the full file name specified by defining a backup device and media sets.  Your reply was "You should be able to backup SQL db's..."  Is it correct that we should also be able to do all the other tasks I listed and any I am not thinking about?  I don't want to find a place where not putting the full file name specified in the backup maintenance plan messes something up down the road.  


I know this is picky and I appreciate your patience, but this has ramifications on how we divide up the disk so we don't want to have to undo something several months down the line.

Thanks,

Jeremy
ASKER CERTIFIED SOLUTION
Avatar of lcohan
lcohan
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of WvrLthr

ASKER

I will assume you have done restores successfully from a unc path and close the case.  Thanks.
Avatar of WvrLthr

ASKER

Didn't specifically address that restores have/will work using unc, but it seems pretty likely that they do.
Restore works like a charm indeed - in SSMS you paste in the UNC full path \\vcenter\sqlbak\productiondb.bak like you put it in the SQL script restore command as you can't navigate(browse) to it from SMMS restore UI.