Sunday, May 5, 2013

[SQL Server] Backup and recovery for the accidental DBA

[SQL Server] Backup and recovery for the accidental DBA

Backup and recovery for the accidental DBA

Posted: 05 May 2013 04:39 AM PDT

Hello - I am not a DBA, let's start with that...but I have acquired the task of backup up a db and copying it to a different server. I've been reading the BOLs on backup (haven't even GOTTEN to recovery) and I am confused by the plethora of info. So, here's the story - we have a db which was upgraded and moved to a different server (server B). I managed to create a linked server where it used to live (server A) so that reporting which pointed to tables on that db would still be able to access those tables. We found out the hard way that you can't use functions across linked servers (well, you CAN, but it's difficult) - anyway, we had a "reporting" version of that db which has not been updated since January, so we did a temporary measure of pointing the functions to that reporting version on server a and the tables to the actual tables on server b. So...the next step is to create a backup of the db on server b and restore a copy on server a which will run as a scheduled job every night. That way, we have our reporting version which is only 24-hours old. I'm reading about the back-ups, and I don't know if I should be doing a copy-only or what. I don't want to just execute the backup task in ssms without a better idea of what I'm doing and if anything I do can hurt the production db on server b. Seems like a backup would be just a read of the db, but some of the verbiage in the BOL makes me question that. Also - do I have to have the logs, as well?Sorry for the total ignorance...this greatness has been thrust upon me, as it were. I appreciate any guidance/input/knowledge sharing! Even a plain and simple tutorial to read would be tremendously helpful.Thank you --Donna
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog