<div>
You could make your server a VM and use Hyper-V Live Migration or VMWare VMotion - the VM itself does not need to be cluster-aware for these.<br />
<br />
Alternatively, you can make the services (not the server) highly available by using a second server hosting a DC (built-in replication), DFS for your file servers accesibly through a single UNC using DFS replication to keep the shares up to date, and SQL server replication.
</div>


<div>
I honestly have not messed with VM at all... and I am a little weary diving right in trying to implement that at this point in time.<br />
<br />
I am mainly concerned with making the services highly available and redundant. &nbsp;I was planning on building a hardware clone box to our current DC &amp;&nbsp;FS. &nbsp;So I would be able to do what I want to do through the built in Server DFS? &nbsp;Also, you do not need clustering for the SQL replication? &nbsp;DFS will take care of a SQL database as well?
</div>


<div>
Thank you guys. &nbsp;That answers the majority of my questions. &nbsp;The install of Server 2008 Standard is an OEM install key. &nbsp;I built the hardware custom, so that answers that. &nbsp;Our SQL instance runs in tangent with a proprietary program that interfaces with the SQL DB. &nbsp;I have contacted them and they are open to allowing me to have a replicated instance.<br />
<br />
No one may be able to answer this question here, but will having the Quickbooks company files on the DFS share be problematic? &nbsp;I would assume not... But I have come to the conclusion that Quickbooks was coded by Satan...
</div>


<div>
The challenge with DFS replication of Quickbooks is that you can't replicate the file until it is closed by everyone, so you may not have a very up to date copy. If things really go south, you can hopefully still access the files on the old server and copy them over. That usually isn't too much of a problem, though. This weekend I am going to do maintenance on my SAN in the primary datacenter, so I am going to flip everyone over the to DR file server by changing the DFS namespace. DFS replication handles file changes, and I just tell people that the database files are unavailable for a while. 
</div>


<div>
Following Links Help you<br />
<br />
<br />
<a href="http://www.directionsonmicrosoft.com/sample/DOMIS/update/2008/10oct/1008lws.htm" rel="ugc">http://www.directionsonmicrosoft.com/sample/DOMIS/update/2008/10oct/1008lws.htm</a><br />
<br />
<a href="http://www.microsoft.com/windowserver2008/howtobuy/licensing/" rel="ugc">http://www.microsoft.com/windowserver2008/howtobuy/licensing/</a><br />

</div>


<div>
I applogize <br />
Hi Accidently wrong Answer or link posted <br />

</div>


<div>
Ok, so I have conferred with my third party software provider and I cannot do a basic transaction replication with our particular SQL database as it does not have all of the primary keys in place in order to do this. &nbsp;Their tech suggested that I look into transaction log backups in order to keep short-time frame replication (15-30 minute range).<br />
<br />
My question now is, what is the best way to go about this? &nbsp;I am not very familiar with SQL and feel like I am working in the dark here. &nbsp;He said I &nbsp;would need to build some scripts to automate this, but that he could not help me anymore than pointing me in the right direction (our service agreement does not cover this sort of thing...)<br />
<br />
Need some direction here please!
</div>


<div>
<div class="content wysiwyg-content">
We are looking to try and increase our redundancy with our main dataserver. &nbsp;This server is running Windows Server 2008 R2 Standard x64. &nbsp;It is our current domain controller, as well as file server. &nbsp;It houses multiple Quickbooks company files, and an SQL Server 2008 R2 instance and database.<br />
<br />
I would like to know what is the most efficient way to replicate the ENTIRE server in a real time way &nbsp;for failover reasons.<br />
<br />
It is my understanding that Server 2008 Standard does not support clustering at all? &nbsp;Is this true? &nbsp;If so, would the built in replication services be able to handle what I am looking for?<br />
<br />
Any information would be extremely valuable.
</div>
</div>


We are looking to try and increase our redundancy with our main dataserver.  This server is running Windows Server 2008 R2 Standard x64.  It is our current domain controller, as well as file server.  It houses multiple Quickbooks company files, and an SQL Server 2008 R2 instance and database.

I would like to know what is the most efficient way to replicate the ENTIRE server in a real time way  for failover reasons.

It is my understanding that Server 2008 Standard does not support clustering at all?  Is this true?  If so, would the built in replication services be able to handle what I am looking for?

Any information would be extremely valuable.

Server Duplication &amp; Failover - Server 2008 R2 Standard

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.

Microsoft SQL Server 2008

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Server Duplication &amp; Failover - Server 2008 R2 Standard

Server Duplication & Failover - Server 2008 R2 Standard