| Author |
Question for ocpguy
|
|
| Pavlov 2001-08-08, 9:16 pm |
| Hey - I noticed that you have your MCP in SQL 2000. Quick question - is it possible to do a SQL backup across the network to a mapped drive location? I was able to do it with SQL 7 and we just upgraded our DB to 2000 and all the maintenance plans that were built in 7 still work and are sending the .BAKs and .TRNs across to another machine, and subsequently to 2 different tapes, but it doesn't appear that I can create a new maintenance plan in SQL 2000 by directing the device to a mapped network drive.
Any thoughts? | |
| ocpguy 2001-08-08, 11:00 pm |
| quote:
Hey - I noticed that you have your MCP in SQL 2000. Quick question - is it possible to do a SQL backup across the network to a mapped drive location? I was able to do it with SQL 7 and we just upgraded our DB to 2000 and all the maintenance plans that were built in 7 still work and are sending the .BAKs and .TRNs across to another machine, and subsequently to 2 different tapes, but it doesn't appear that I can create a new maintenance plan in SQL 2000 by directing the device to a mapped network drive.
I don't need an MCP to answer this.
Did you say you are backing up directly to tape over the network or over the network to a share then to a tape? Neither SQL 7 or 2000 support backing up to tape drives that aren't local. The only thing I can think of that would do this would be an external 3rd party tool that includes a SQL Agent like BackupExec by Seagate... but then it does a COMPLETE backup of the server's contents.
A more practical solution would be to put this on a network share and then maybe on a tape or optical device. Is this what you say you are presently doing?
Next you CANNOT use a mapped network drive letter. You CAN use a UNC name like '\\serverx\disk1\bk\backup8_7_
01.dmp' BUT...
You have to change the registry on the destination server so that it removes security from the drive share you send it to. (not recommended)
-or-
You can change the localsystem account to a user that has permissions on the drive you need to access. (The MSSQLSERVER service is not an authenticated network account.)
Hope that helps! =) | |
| ocpguy 2001-08-09, 3:28 pm |
| Pavlov,
Did my answer help? or at least point you in the right direction? 
The whole gist of it... was that you have to make sure that you are using UNC (not a drive letter) and make sure your MSSQLSERVER service is running on a user account that has the appropriate network priveleges to access the share you want.
-ocpguy | |
| Pavlov 2001-08-09, 5:05 pm |
| Thanks for the input - I am using UNC to send across to another networked device. It was my belief that this might be the case. However, after looking through some MS documentation, it also looks like SQL2000 took that ability away - I guess I need to spend some time and focus on the problem. In the meantime, the current fix plan is to upgrade the base version of Backup Exec and then load the new SQL2000 agent for BE. | |
| ocpguy 2001-08-09, 11:41 pm |
| Pavlov...
check out the books online, msdn and google.com with your search phrase... msdn is a great resource
I learn lots of great best practices everyday from the internet....
I don't believe that SQL 2000 has taken the ability to backup over the network away....
However, I do not have that much exp with the maintenance plan... we were a small SQL shop... more databases on the Oracle side...
Good luck!
Ocpguy | |
| Pavlov 2001-08-10, 7:13 pm |
| Thanks - I live on the internet searching for this kind o' stuff. My MSDN has finally shipped (after being on backorder for 4 wks) and should arrive Tuesday.
I think I've actually narrowed the problem down to my backup software. I need to upgrade my backup software to the current version and then upgrade the SQL Agent for SQL 2000. That will be tested next week and rolled into my Production environment in 2 weeks. Many of my key developers are on vacation and if the backup software does something unexpected I want my team all in-house to minimize live Production down-time.
Thanks for your help along the way on this. |
|
|
|