| Author |
Topic  |
|
|
Rambler
Major Contributor
   
Czech Republic
949 Posts
Status: offline |
Posted - 06/29/2012 : 09:24:15 AM
|
I've asked this already in the licensing thread, but here goes again.
Has any of you guys deployed multiple SC2012 products (including DPM2012) using single SQL instance? If yes, than how are you dealing with SQL HA?
DPM2012 guide specifically says it doesn't support running the DPM database on clustered/mirrored SQL instance. CTP of DPM2012 SP1 says the same, only for SQL Server 2012.
What are the HA options for SQL when: 1) using DPM 2012 2) using single SQL instance for all products
Or are you doomed to the scenario of using one SQL instance (locally on the DPM server) just for DPM and other instance(s) for the other products?
|
|
|
NMDANGE
Honorable But Hopeless Addict
    
USA
2054 Posts
Status: offline |
Posted - 06/29/2012 : 10:13:51 AM
|
As I said in the other thread, I would run SQL on the DPM Server itself. IMO, running SQL on a separate server just makes things that much more complicated if you need to do a restore when that SQL server went down. DPM will not work without a working SQL instance. And if your SQL server dies, how are you going to use DPM to restore it! By having DPM and SQL on the same server, then the only time SQL would be a problem is if the actual DPM server has a problem. Which, if it does, means you can't do restores anyway. Of course you do have a second DPM server in a remote datacenter to do disaster recovery right? 
The rest of the SC 2012 products should be able to share a SQL Server cluster. I've only done Operations Manager and VMM so far, but I have both of those running on a single SQL 2008 cluster. (Along with a whole bunch of other apps) |
Michael D'Angelo (former)MVP-MIIS, Pace University Senior Systems Administrator (Windows) (MS)NMDANGE PhoeniX WorX Systems Administrator. If you play Total Annihilation, please join us. http://www.phoenixworx.org |
 |
|
|
Rambler
Major Contributor
   
Czech Republic
949 Posts
Status: offline |
Posted - 06/29/2012 : 10:24:49 AM
|
Michael, you said quote: IMO, running SQL on a separate server just makes things that much more complicated if you need to do a restore when that SQL server went down. DPM will not work without a working SQL instance. And if your SQL server dies, how are you going to use DPM to restore it!
Isn't that exactly the purpose of SQL cluster? If the SQL server has problems, the passive node kicks in (or you can manually failover).
I guess we can do a deployment similar to yours, but I wanted to go with what seemed the most clean deployment, which in my view is using single clustered SQL instance for all the products. |
Edited by - Rambler on 06/29/2012 10:25:59 AM |
 |
|
|
joe_elway
Honorable But Hopeless Addict
    
Ireland
7397 Posts
Status: offline |
Posted - 06/29/2012 : 11:14:24 AM
|
quote: Originally posted by Rambler Isn't that exactly the purpose of SQL cluster? If the SQL server has problems, the passive node kicks in (or you can manually failover).
No. A SQL cluster is about OS/hardware fault tolerance. If you have a traditional active/passive cluster then you have a single datastore. If that's corrupted then failing over the SQL instance does diddly-squat.
|
Aidan Finn MCSE, MVP (Virtual Machine)
IT Blog: http://www.aidanfinn.com My Photography: http://www.aidanfinnphoto.com/ Books: WS2012 Hyper-V Installation & Config Guide, MSFT Private Cloud Computing Twitter: http://twitter.com/joe_elway |
 |
|
|
Pesos
Honorable But Hopeless Addict
    
USA
3506 Posts
Status: offline |
Posted - 07/01/2012 : 7:36:06 PM
|
| The only SC products we use are DPM and VMM. These are the two that I think make the most sense to have their own SQL datastores. DPM so it can do a restore in case of SQL failure, and VMM so it can function in case of a Hyper-V node/cluster failure...? |
-Wes |
 |
|
|
Rambler
Major Contributor
   
Czech Republic
949 Posts
Status: offline |
Posted - 07/02/2012 : 07:04:54 AM
|
| Wes, then I assume you run VMM on a physical box? |
 |
|
| |
Topic  |
|