Sql 2008 R2 Database Backup
We purchased a backup system for all our servers, where it backs up every 15 or 30 minutes.
If there is a total server failure the system allows it to be virtualized so the users can keep working after the virtualized server comes up and stays up until the real server is fixed. I have questioned them on the SQL server because I wasn't sure if it was backing up correctly.
They assured me it is. When I go to the BDR or Shadow protect server ( which is the system we bought) I can go to an server and look at the backups. For SQL I see all the drives, folders, etc. It basically takes a copy of everything every 30 minutes. In my SQLDATA folder I see all the databases and log files that are just copied over. There is no .bak on anything so I know its just a copy. We do not have enterprise edition so is this okay? I know I need to restore to find out and that is my next question. How would I restore these, Just drop the database and attach the one I moved over from the backup. Would this be the proper way to test?
If there is a total server failure the system allows it to be virtualized so the users can keep working after the virtualized server comes up and stays up until the real server is fixed. I have questioned them on the SQL server because I wasn't sure if it was backing up correctly.
They assured me it is. When I go to the BDR or Shadow protect server ( which is the system we bought) I can go to an server and look at the backups. For SQL I see all the drives, folders, etc. It basically takes a copy of everything every 30 minutes. In my SQLDATA folder I see all the databases and log files that are just copied over. There is no .bak on anything so I know its just a copy. We do not have enterprise edition so is this okay? I know I need to restore to find out and that is my next question. How would I restore these, Just drop the database and attach the one I moved over from the backup. Would this be the proper way to test?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
TempDBA
One more point, when you are copying the files to the same drive where the original exists, you can't copy it with the same name. So, rename the file and copy and create database with attach.
Well I have one more point to!
Either do this on off hours, or on a separate server.
Marten
Either do this on off hours, or on a separate server.
Marten
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also, ask your ops guys to give you access to the documentation for whatever backup solution they are using. If it has a module that can specifically and correctly back up SQL Server files, it should be documented how you go about verifying backups and how you do recoveries.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all the info. Some pertained to me more than others hence the different points.
I appreciate it
I appreciate it