June 13, 2008 at 6:45 am
Not only have I run out of disk space, but it's bad practice to have your backups on the same drive as the databases :sick: But, how do I back up my databases to a different server? I've tried \\ServerA\d$\backup\filename but that errors that the network path cannot be found or access denied. What do you mean 'Access Denied' I'm the dba for heaven sakes.
I really can use some help with this.
Tim
June 13, 2008 at 7:39 am
Whatever NETWORK account is running the the SQL server agent service needs, at minimum, write permissions to the share on the network. If you need to restore from there as well, you'll obviously need read permissions. I'd grant full access for the account at the d$\backup folder level and keep it a hidden share. Also, UNC paths (\\ServerA\d$\backup\filename) are the appropriate (only?) way to go!
-- You can't be late until you show up.
June 13, 2008 at 7:42 am
Honestly, I would get more disk, backup locally and then copy to a remote server.
My method of handling this in the past is to backup (full and logs) to the local disk, copy them to the remote server immediately, and then have tape grab it from the remote server. As soon as a new backup (meaning recovery back to the last full), I remove all older files. That way I have one copy ready for quick recovery from human errors, but a second copy for DR purposes on a remote machine.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 13, 2008 at 7:54 am
Thanks folks. If it's one thing I've learn in more than 30 years in IT is that there are always more than one way to approach everything. 🙂
Tim
June 13, 2008 at 7:54 am
Steve Jones - Editor (6/13/2008)
Honestly, I would get more disk, backup locally and then copy to a remote server.My method of handling this in the past is to backup (full and logs) to the local disk, copy them to the remote server immediately, and then have tape grab it from the remote server. As soon as a new backup (meaning recovery back to the last full), I remove all older files. That way I have one copy ready for quick recovery from human errors, but a second copy for DR purposes on a remote machine.
I totally agree with Steve on all points, especially on adding disk. In the past, I've backed up my data exclusively to a remote server (not recommended, search this site for a whole slew of reasons) and never got bitten by network glitches which would corrupt my files BUT at my new employer, I'm not as confident in the network design and some of the hardware so it's all local, then swept to tape.
FYI - I'm not knocking my new employer. At my last company, we were state of the art with hardware and I knew all the infrastructure guys and their talent. Also, I helped out with a lot of the building of the hardware. Made me real comfortable. Maybe I was lucky with my backup strategy but where I'm at now, I'm not taking any undue risks. Better safe than sorry.
-- You can't be late until you show up.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply