December 4, 2011 at 8:43 pm
We are setting up a new server instance with about 50 databases but only 4 of these databases have any data in it.
If there is a need to restore this server, we don't have time to wait for restoring each database one-by-one. So,
1. What is the best way to setup these backups?
2. Is there a datafiles based backup that we can just copy over the files in case of a disaster instead of restoring database by database?
(We use litespeed with other server instances since there are only a few databases for each instance.)
December 4, 2011 at 11:58 pm
aim for uniformity of management and apply the same backup strategy on all your instances.
If you cannot do that, use sqlagent to schedule your backup jobs for the wanted databases.
Double check your "don't need backup" databases are couvered. I would include them in my backup jobs as well. We all know you cannot rely on things you don't control 100%.
How about backup of granted auth,...
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
December 5, 2011 at 12:17 am
We are setting up a new server instance with about 50 databases but only 4 of these databases have any data in it.
I have one question here. If you have only 4 databases with data then why 50 DBs are sitting on that Server? Please free the Server if you don't need these DBs.
Backup Strategy depends upon nature / volume of data. If you provide us more information, we would be able to help you better.
December 5, 2011 at 12:14 pm
ashanair70 (12/4/2011)
We are setting up a new server instance with about 50 databases but only 4 of these databases have any data in it.If there is a need to restore this server, we don't have time to wait for restoring each database one-by-one. So,
1. What is the best way to setup these backups?
2. Is there a datafiles based backup that we can just copy over the files in case of a disaster instead of restoring database by database?
(We use litespeed with other server instances since there are only a few databases for each instance.)
If you don't have time to restore the databases - to me, that would mean implementing a DR/HA strategy that allows for failover without having to restore the databases.
That would be either database mirroring or log shipping - or a SAN based mirroring/replication solution.
If you need to have your system up and available in case of a server crash, and don't want to failover to DR in that situation you may also want to consider building a cluster.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 6, 2011 at 6:32 am
I really don't think this is a good solution for a production system, at all, but if you want very fast restores, you should take a look at something like Virtual Restore[/url] from Red Gate. It mounts a backup file instead of actually doing a restore operation. But... that's a horrificly bad choice for a production system.
I agree with the poster above, you're in a HA situation and you need to approach things differently. Yeah, continue setting up and maintaining your backups, they're a fundamental part of protection, but you need mirroring or replication or something.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply